Summary of the invention
The invention provides a kind of data transmission method, solve under certain Un UL/DL sub-frame configuration, lack the problem of the sequential relationship mechanism of Un UL Grant and corresponding PUSCH resource.
A kind of data transmission method, in TDD network, comprising:
Fixed timing relationship is set up between the sub-frame of uplink shared by the descending sub frame shared by Un UL Grant and the PUSCH resource of distributing, described fixed timing relationship and network side are to back haul link uplink and downlink sub-frame configuration one_to_one corresponding, and the fixed timing relationship of any one or multiple described back haul link uplink and downlink sub-frame configuration and correspondence thereof forms transmitting uplink data time-scale;
According to the uplink and downlink sub-frame configuration of network side to back haul link, access side obtains corresponding fixed timing relationship from described transmitting uplink data time-scale, and according to this fixed timing relationship after downlink subframes in return link receives Un UL Grant, corresponding back haul link sub-frame of uplink uses the PUSCH resource of distribution carry out transmitting uplink data to network side.
Further, described Un UL Grant uses descending control information format 0 (DCI format 0) carrying, configures instruction by network side to access side.
Further, described network side is the combination of appointing one or more of following network element:
ENB, RN, cell cooperative entity (MCE), gateway (GW), mobile management (MME), Evolved UTRAN (EUTRAN), operational administrative and safeguard (OAM) manager.
Further, described access side is RN or highest version user terminal, and described highest version user terminal is specially R10 and more highest version user terminal.
Further, the configuration of described network side to back haul link uplink and downlink subframe is specially, in the back haul link uplink and downlink sub-frame configuration set of TDD system agreement, network side configuration instruction access side performs a kind of back haul link uplink and downlink sub-frame configuration in this set, and the uplink and downlink subframe that described back haul link uplink and downlink sub-frame configuration specifies is as back haul link uplink and downlink subframe.
Further, described access side obtains corresponding fixed timing relationship according to back haul link uplink and downlink sub-frame configuration, and according to this fixed timing relationship after downlink subframes in return link receives Un UL Grant, corresponding back haul link sub-frame of uplink uses the PUSCH resource of distribution carry out transmitting uplink data to network side and comprise:
Network side to access side configuration instruction Un UL Grant, distributes UnPUSCH resource on downlink subframes in return link;
Access side, according to described fixed timing relationship, uses the PUSCH resource bearing upstream data distributed to carry out uplink to eNB at corresponding back haul link sub-frame of uplink.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#1, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #4 subframe is downlink subframes in return link, #8 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction Un UL Grant information in downlink subframes in return link #4 subframe, and access side uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #8 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#1, namely configuring #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction Un UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#2, namely configuration #4 subframe and #9 subframe are downlink subframes in return link, #8 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction Un UL Grant information in downlink subframes in return link #4 subframe, and access side uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #8 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#3, namely configuration #4 subframe and #9 are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction Un UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#4, namely configuration #4 subframe and #9 subframe are downlink subframes in return link, #8 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates Un ULGrant information to the configuration of access side in downlink subframes in return link #4 subframe, access side uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #8 subframe, and/or, network side indicates Un UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#2, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#1, namely configuring #3 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#2, namely configuration #3 subframe and #8 subframe are as downlink subframes in return link, #2 subframe is as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Confguration#3, namely configuration #4 subframe and #8 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#4, namely configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#5, namely configuration #3 subframe and #4 are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#6, namely configuration #3 subframe and #8 are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#7, namely configuration #3 subframe and #9 subframe are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link ULGrant information in downlink subframes in return link #3 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#8, namely configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#9, namely configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#10, namely configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#11, namely configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#12, namely configuring #3 subframe and #4 subframe and #9 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#13, namely configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#14, namely configuring #3 subframe and #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#15, namely configuring #3 subframe and #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#16, namely configuration #3 subframe and #8 subframe are downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to the configuration of access side on downlink subframes in return link #8, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to the configuration of access side on downlink subframes in return link #3, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#17, namely configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side on downlink subframes in return link #8, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to the configuration of access side on downlink subframes in return link #3, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#18, namely configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side on downlink subframes in return link #8, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to the configuration of access side on downlink subframes in return link #3, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#19, namely configuring #3 subframe and #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side on downlink subframes in return link #8, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to the configuration of access side on downlink subframes in return link #3, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#3, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#1, namely configuring #8 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#2, namely #7 subframe is configured as downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #7 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#3, namely #9 subframe is configured as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#4, namely #9 subframe is configured as downlink subframes in return link, using #4 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#5, namely configuration #7 subframe and #8 are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#6, namely configuration #8 subframe and #9 are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#7, namely configuration #7 subframe and #9 subframe are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information on downlink subframes in return link and #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#8, namely configuration #7 subframe and #8 subframe are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#9, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#10, namely configuration #7 subframe and #9 subframe are downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#11, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#12, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#13, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#14, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe; Or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#15, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#16, namely configuration #7 subframe and #8 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #7 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#17, namely configuration #7 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #7 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#18, namely configuration #7 subframe and #8 subframe are downlink subframes in return link, #3 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #7 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#19, namely configuration #7 subframe and #9 subframe are downlink subframes in return link, #3 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #7 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#20, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #3 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#21, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#22, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#23, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#24, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#4, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#1, namely configuring #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#2, namely configuration #4 subframe and #8 subframe are as downlink subframes in return link, #2 subframe is as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#3, namely configuration #7 subframe and #8 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#4, namely configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#5, namely configuration #4 subframe and #9 are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#6, namely configuration #7 subframe and #9 are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#7, namely configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#8, namely configuring #4 subframe and #7 subframe and #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#9, namely configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#10, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#11, namely configuring #4 subframe and #7 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#12, namely configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#13, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#14, namely configuring #4 subframe and #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#15, namely configuring #4 subframe and #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#16, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#17, namely configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#18, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#19, namely configuring #4 subframe and #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link ULGrant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#6, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #9 subframe is downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side is to access side configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe.
Further, the fixed timing relationship of described any one or multiple described back haul link uplink and downlink sub-frame configuration and correspondence thereof forms transmitting uplink data time-scale and is specially:
Using described sub-Configuration#0 to sub-Configuration#4 as list item, construct described transmitting uplink data time-scale.
Further, the fixed timing relationship of described any one or multiple described back haul link uplink and downlink sub-frame configuration and correspondence thereof forms transmitting uplink data time-scale and is specially:
Using described sub-Configuration#1, sub-Configuration#7, sub-Configuration#12, sub-Configuration#15, sub-Configuration#16, sub-Configuration#18 and sub-Configuration#19 as list item, for described list item redistributes sequence number, and described list item is used to construct described transmitting uplink data time-scale.
Further, the fixed timing relationship of described any one or multiple described back haul link uplink and downlink sub-frame configuration and correspondence thereof forms transmitting uplink data time-scale and is specially: using described sub-Configuration#3, sub-Configuration#8, sub-Configuration#13, sub-Configuration#15 and sub-Configuration#22 as list item, for described list item redistributes sequence number, and described list item is used to construct described transmitting uplink data time-scale.
Further, the fixed timing relationship of described any one or multiple described back haul link uplink and downlink sub-frame configuration and correspondence thereof forms transmitting uplink data time-scale and is specially:
Using described sub-Configuration#1, sub-Configuration#6, sub-Configuration#7, sub-Configuration#13, sub-Configuration#15, sub-Configuration#16, sub-Configuration#18 and sub-Configuration#19 as list item, for described list item redistributes sequence number, and described list item is used to construct described transmitting uplink data time-scale.
Present invention also offers a kind of data transmission system, in TDD network, this system comprises network equipment and access side device;
Described network equipment, for setting up fixed timing relationship between the sub-frame of uplink shared by the descending sub frame shared by Un UL Grant and the PUSCH resource of distributing, described fixed timing relationship and network side, to back haul link uplink and downlink sub-frame configuration one_to_one corresponding, use the fixed timing relationship of any one or multiple described back haul link uplink and downlink sub-frame configuration and correspondence thereof to form transmitting uplink data time-scale;
Described access side device, for according to the uplink and downlink sub-frame configuration of network side to back haul link, corresponding fixed timing relationship is obtained from described transmitting uplink data time-scale, and according to this fixed timing relationship after downlink subframes in return link receives Un UL Grant, corresponding back haul link sub-frame of uplink uses the PUSCH resource of distribution carry out transmitting uplink data to described network equipment.
Further, described Un UL Grant uses DCI format 0 to carry, and configures instruction by described network equipment to described access side device.
Further, described access side device equipment is RN or highest version user terminal, and described highest version user terminal is specially R10 and more highest version user terminal.
Further, described network equipment is the combination of appointing one or more of following network element:
ENB, RN, MCE, GW, MME, EUTRAN, OAM manager.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#1, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #4 subframe is downlink subframes in return link, #8 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction Un UL Grant information in downlink subframes in return link #4 subframe, and access side device uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #8 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#1, namely configuring #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction Un UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#2, namely configuration #4 subframe and #9 subframe are downlink subframes in return link, #8 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction Un UL Grant information in downlink subframes in return link #4 subframe, and access side device uses distributed UnPUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #8 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#3, namely configuration #4 subframe and #9 are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction Un UL Grant information in downlink subframes in return link #4 subframe, and access side device uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#4, namely configuration #4 subframe and #9 subframe are downlink subframes in return link, #8 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates Un ULGrant information to access side device configuration in downlink subframes in return link #4 subframe, access side device uses distributed UnPUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #8 subframe, and/or, network side indicates Un UL Grant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#2, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#1, namely configuring #3 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#2, namely configuration #3 subframe and #8 subframe are as downlink subframes in return link, #2 subframe is as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#3, namely configuration #4 subframe and #8 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#4, namely configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#5, namely configuration #3 subframe and #4 are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #3 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#6, namely configuration #3 subframe and #8 are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #3 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#7, namely configuration #3 subframe and #9 subframe are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#8, namely configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#9, namely configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#10, namely configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#11, namely configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#12, namely configuring #3 subframe and #4 subframe and #9 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#13, namely configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#14, namely configuring #3 subframe and #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#15, namely configuring #3 subframe and #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #3 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #7 subframe; Or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#16, namely configuration #3 subframe and #8 subframe are downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration on downlink subframes in return link #8, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to access side device configuration on downlink subframes in return link #3, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#17, namely configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration on downlink subframes in return link #8, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to access side device configuration on downlink subframes in return link #3, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#18, namely configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration on downlink subframes in return link #8, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to access side device configuration on downlink subframes in return link #3, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#19, namely configuring #3 subframe and #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration on downlink subframes in return link #8, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link ULGrant information to access side device configuration on downlink subframes in return link #3, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#3, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#1, namely configuring #8 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#2, namely #7 subframe is configured as downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #7 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#3, namely #9 subframe is configured as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#4, namely #9 subframe is configured as downlink subframes in return link, using #4 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#5, namely configuration #7 subframe and #8 are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#6, namely configuration #8 subframe and #9 are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#7, namely configuration #7 subframe and #9 subframe are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information on downlink subframes in return link and #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#8, namely configuration #7 subframe and #8 subframe are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#9, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#10, namely configuration #7 subframe and #9 subframe are downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#11, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#12, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#13, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#14, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe; Or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#15, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link ULGrant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#16, namely configuration #7 subframe and #8 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #7 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link ULGrant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#17, namely configuration #7 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #7 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link ULGrant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#18, namely configuration #7 subframe and #8 subframe are downlink subframes in return link, #3 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #7 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, and/or, network side indicates back haul link ULGrant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#19, namely configuration #7 subframe and #9 subframe are downlink subframes in return link, #3 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #7 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, and/or, network side indicates back haul link ULGrant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#20, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #3 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, and/or, network side indicates back haul link ULGrant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#21, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link ULGrant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#22, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#23, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, and/or, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#24, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#4, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#1, namely configuring #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#2, namely configuration #4 subframe and #8 subframe are as downlink subframes in return link, #2 subframe is as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#3, namely configuration #7 subframe and #8 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#4, namely configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#5, namely configuration #4 subframe and #9 are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#6, namely configuration #7 subframe and #9 are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#7, namely configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#8, namely configuring #4 subframe and #7 subframe and #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#9, namely configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#10, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#11, namely configuring #4 subframe and #7 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#12, namely configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#13, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#14, namely configuring #4 subframe and #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; Or,
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#15, namely configuring #4 subframe and #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; Or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#16, namely configuration #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link ULGrant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#17, namely configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#18, namely configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe, or,
Network side configuration adopts on back haul link, descending sub frame configuration sub-Configuration#19, namely configuring #4 subframe and #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #8 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, and/or, network side indicates back haul link UL Grant information to access side device configuration in downlink subframes in return link #9 subframe, access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe.
Further, when described back haul link uplink and downlink sub-frame configuration is TDD UL/DLConfiguration#6, described fixed timing relationship is:
Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#0, namely configuring #9 subframe is downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side is to access side device configuration instruction back haul link UL Grant information in downlink subframes in return link #9 subframe, and access side device uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe.
The invention provides a kind of data transmission method, fixed timing relationship is set up between the sub-frame of uplink shared by the descending sub frame shared by back haul link ascending resource mandate (Un ULGrant) and the PUSCH resource of distributing, described fixed timing relationship and network side are on back haul link, descending sub frame configuration one_to_one corresponding, on any one or multiple described back haul link, the fixed timing relationship of descending sub frame configuration and correspondence thereof forms transmitting uplink data time-scale, according to upper to back haul link of network side, descending sub frame configures, access side obtains corresponding fixed timing relationship from described transmitting uplink data time-scale, and according to this fixed timing relationship after downlink subframes in return link receives Un UL Grant, corresponding back haul link sub-frame of uplink use the PUSCH resource of distribution carry out transmitting uplink data to network side, solve the problem of the sequential relationship not having Un UL Grant and corresponding PUSCH resource.
Embodiment
At present, under certain Un UL/DL sub-frame configuration, for Un UL Grant between eNB and RN and corresponding PUSCH resource, still lack the mechanism that one is determined sequential relationship between the two, transmitting uplink data cannot be carried out.Therefore need the sequential relationship to Backhaul Link ascending resource authorizes between corresponding transmitting uplink data to define, thus ensure effective transmission of Backhaul Link upstream data.In addition, when network side and highest version user terminal carry out transmitting uplink data, also need to determine the sequential relationship between ULGrant and corresponding PUSCH resource.
The embodiment provides a kind of data transmission method, side Network Based is the Un UL/DL subframe of back haul link configuration, for the time order relation that Un UL Grant and corresponding PUSCH resource distribution between network side to access side are determined, achieve access side direction network side transmit ascending data.Access side mainly comprises RN or highest version user terminal, and this highest version user terminal is specially R10 and more highest version user terminal.Both to realize principle identical, in embodiments of the invention, be all described for RN.
In a tdd system, system can configure at Backhaul Link and use TDD UL-DLConfiguration#1, #2, #3, any one in #4, #6, due under each UL-DL Configuration, in radio frames, the configuration of UL, DL subframe is different, therefore needs the sequential relationship between UL Grant and the PUSCH in the corresponding situation of difference specification.Meanwhile, due to Un subframe and the time-division property of Uu subframe and some restrictive conditions to Un sub-frame configuration, as #0,1,5,6 subframes can not be configured to UnDL subframe, and the Un subframe that system can configure has limited combined situation.Embodiments of the invention are according to the concrete configuration situation of Un subframe, be defined in the sequential relationship between Un UL Grant and Un PUSCH resource under this Un sub-frame configuration accordingly, form the sequential relationship table of back haul link transmitting uplink data, the sub-frame interval k value namely carried between the Un DL subframe of UL Grant and the Un UL subframe at corresponding Un PUSCH resource place is shown.According to Un sub-frame configuration and corresponding k value table, network side indicates UnUL Grant in Un DL#n subframe to RN configuration, after being included as the UnPUSCH resource indication information of RN distribution in UL Grant information, RN uses distributed UnPUSCH resource bearing upstream data to carry out transmitting uplink data to network side on corresponding Un UL subframe #n+k.Network side comprises the combination of appointing one or more of following network element:
ENB, RN, MCE, GW, MME, EUTRAN, OAM manager.
In the examples below, take eNB as network equipment for example is described.
Below in conjunction with accompanying drawing, embodiments of the invention one are described.
In the embodiment of the present invention, under this configuration of TDD UL-DL Configuration#1, the Un sub-frame configuration that network side instruction RN specifically uses.
When system adopts TDD UL-DL Configuration#1, the configurable #3 subframe of system, #4 subframe, #8 subframe, #9 subframe are as Un subframe, and the sequential relationship table of the Un subframe that concrete configuration uses and corresponding Backhaul Link transmitting uplink data is as shown in table 2.Wherein D represents that corresponding subframe is descending sub frame, U represents that corresponding subframe is sub-frame of uplink, S represents special subframe, to the different Un sub-frame configuration situations of Configuration#1, carry out difference with son configuration (sub-Configuration) to represent, and provide the sequential relationship table example of corresponding back haul link transmitting uplink data.Numerical value k (k is positive integer) given in corresponding subframe (subframe#0-#9) represents that RN should carry out uplink according to distributed UnPUSCH resource to eNB in #n+k subframe when subframe #n carries Un ULGrant information.
Concrete Un sub-Configuration is as shown in table 2, for TDD UL-DL Configuration#1, can need to select the different corresponding subframes of Un UL/DL subframe proportional arrangement as Un subframe according to system, sub-Configurations#0-#4 corresponding back haul link transmitting uplink data sequential relationship table is as shown in table 2.The preferred embodiment of table 2 for obtaining according to different Un sub-frame configuration, in table 2, any one or more sub-Configuration and corresponding k value definition can form TDD UL-DLConfiguration#1 back haul link transmitting uplink data sequential relationship.
Table 2 k for TDD Configurations#1
Below each sub-Confguration is described.
1、sub-Configuration#0
When system configuration #4 subframe is Un descending sub frame, when #8 subframe is Un sub-frame of uplink, i.e. sub-Configuration#0, TDD UL-DL Configuration#1 back haul link transmitting uplink data sequential relationship is: eNB indicates Un UL Grant at subframe #4 to RN configuration, the Un PUSCH resource indication information that RN distributes is included as in UL Grant information, RN defines according to the k value of sub-Configuration#0 in back haul link transmitting uplink data sequential relationship, i.e. k=4, #8 subframe use distributed Un PUSCH resource bearing upstream data carry out transmitting uplink data to eNB.
Sub-Configuration#0 and corresponding back haul link transmitting uplink data sequential relationship are as shown in Figure 2.
2、sub-Configuration#1
When system configuration #9 subframe is Un descending sub frame, when the #3 subframe of next frame is Un sub-frame of uplink, i.e. sub-Configuration#1, TDD UL-DL Configuration#1 back haul link transmitting uplink data sequential relationship is: eNB indicates Un UL Grant at subframe #9 to RN configuration, the Un PUSCH resource indication information that RN distributes is included as in UL Grant information, RN defines according to the k value of sub-Configuration#1 in back haul link transmitting uplink data sequential relationship, i.e. k=4, the #3 subframe of next frame use distributed Un PUSCH resource bearing upstream data carry out transmitting uplink data to eNB.
3、sub-Configuration#2
When system configuration #4 subframe and #9 are Un descending sub frame, #8 subframe is Un sub-frame of uplink, i.e. sub-Configuration#2, TDD UL-DL Configuration#1 back haul link transmitting uplink data sequential relationship is: eNB indicates Un UL Grant at subframe #4 to RN configuration, the Un PUSCH resource indication information that RN distributes is included as in UL Grant information, RN defines according to the k value of sub-Configuration#2 in back haul link transmitting uplink data sequential relationship, i.e. k=4, #8 subframe use distributed Un PUSCH resource bearing upstream data carry out transmitting uplink data to eNB.
4、sub-Configuration#3
When system configuration #4 subframe and #9 are Un descending sub frame, when #3 subframe is Un sub-frame of uplink, i.e. sub-Configuration#3, TDD UL-DL Confguration#1 back haul link transmitting uplink data sequential relationship is: eNB indicates Un UL Grant at subframe #9 to RN configuration, the Un PUSCH resource indication information that RN distributes is included as in UL Grant information, RN defines according to the k value of sub-Configuration#3 in back haul link transmitting uplink data sequential relationship, i.e. k=4, the #3 subframe of next frame use distributed Un PUSCH resource bearing upstream data carry out transmitting uplink data to eNB.
5、sub-Configuration#4
When system configuration #4 subframe and #9 are Un descending sub frame, #3 subframe and #8 are Un sub-frame of uplink, i.e. sub-Configuration#4, TDD UL-DL Configuration#1 back haul link transmitting uplink data sequential relationship is: eNB indicates Un UL Grant at subframe #4 to RN configuration, the Un PUSCH resource indication information that RN distributes is included as in UL Grant information, RN defines according to the k value of sub-Configuration#4 in back haul link transmitting uplink data sequential relationship, i.e. k=4, #8 subframe use distributed Un PUSCH resource bearing upstream data carry out transmitting uplink data to eNB.And/or, eNB indicates Un UL Grant at subframe #9 to RN configuration, the Un PUSCH resource indication information that RN distributes is included as in UL Grant information, RN defines according to the k value of sub-Configuration#4 in back haul link transmitting uplink data sequential relationship, i.e. k=4, the #3 subframe of next frame uses distributed Un PUSCH resource bearing upstream data carry out transmitting uplink data to eNB.
Preferably, the sub-Configuration#0 to sub-Configuration#4 in the embodiment of the present invention can be used to construct transmitting uplink data time-scale, as shown in table 3.
The corresponding transmitting uplink data time-scale of table 3TDD UL/DL Configuration#1
Below embodiments of the invention two are described.
In the embodiment of the present invention, under this configuration of TDD UL-DL Configuration#2, the Un sub-frame configuration that network side instruction RN specifically uses.
When system adopts TDD UL-DL Configuration#2, the configurable #2 subframe of system, #3 subframe, #4 subframe, #7 subframe, #8 subframe, #9 subframe are as Un subframe, and the sequential relationship table of the Un subframe that concrete configuration uses and corresponding back haul link transmitting uplink data is as shown in table 4.Wherein D represents that corresponding subframe is descending sub frame, U represents that corresponding subframe is sub-frame of uplink, S represents special subframe, to the different Un sub-frame configuration situations of Configuration#2, carry out difference with sub-Configuration to represent, and provide the sequential relationship table example of corresponding back haul link transmitting uplink data.Numerical value k (k is positive integer) given in corresponding subframe (subframe#0-#9) represents that RN should carry out uplink according to distributed Un PUSCH resource to eNB in #n+k subframe when subframe #n carries Un ULGrant information.
As shown in table 4, for TDD UL-DL Configuration#2, can need to select the different corresponding subframes of Un UL/DL subframe proportional arrangement as Un subframe according to system, sub-Configurations#0-#19 corresponding back haul link transmitting uplink data sequential relationship table is as shown in table 4.The preferred embodiment of table 4 for obtaining according to different Un sub-frame configuration, in table 4, any one or more sub-Configurations and corresponding k value definition can form TDD UL-DL Configuration#2 back haul link transmitting uplink data sequential relationship.
Table 4 k for TDD Configurations#2
Wherein, sub-Configuration#0 and sub-Configuration#1 is the combination of a sub-frame of uplink and a descending sub frame.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#0, configuration #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#1, configuration #3 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #3 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #7 subframe.
Sub-Configuration#2 to sub-Configuration#7 is the combination of a sub-frame of uplink and two descending sub frames.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#2, configuration #3 subframe and #8 subframe are as downlink subframes in return link, #2 subframe is as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.As shown in Figure 3.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#3, configuration #4 subframe and #8 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#4, configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#5, configuration #3 subframe and #4 are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #3 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #7 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#6, configuration #3 subframe and #8 are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #3 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #7 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#7, configuration #3 subframe and #9 subframe are as downlink subframes in return link, using #7 subframe as back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #3 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #7 subframe.
Sub-Configuration#8 to sub-Configuration#13 is the combination of 3 descending sub frames and a sub-frame of uplink.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#8, configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#9, configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#10, configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#11, configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #3 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #7 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#12, configuring #3 subframe and #4 subframe and #9 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #3 subframe subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #7 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#13, configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #3 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #7 subframe.
Sub-Configuration#14 and sub-Configuration#15 is the combination of 4 descending sub frames and a sub-frame of uplink.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#14, configuration #3 subframe and #4 subframe and #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#15, configuration #3 subframe and #4 subframe and #8 subframe and #9 subframe are downlink subframes in return link, #7 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #3 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #7 subframe.
Network side configuration adopts on back haul link, during descending sub frame configuration sub-Configuration#16, configuration #3 subframe and #8 subframe are downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration on downlink subframes in return link #8, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to RN configuration on downlink subframes in return link #3, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, i.e. k=4.
Sub-Configuration#17 and sub-Configuration#18 is the combination of 3 descending sub frames and two sub-frame of uplink.
Network side configuration adopts on back haul link, during descending sub frame configuration sub-Configuration#17, configuring #3 subframe and #4 subframe and #8 subframe is downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration on downlink subframes in return link #8, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to RN configuration on downlink subframes in return link #3, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, i.e. k=4.
Network side configuration adopts on back haul link, during descending sub frame configuration sub-Configuration#18, configuring #3 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration on downlink subframes in return link #8, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to RN configuration on downlink subframes in return link #3, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, i.e. k=4.
Network side configuration adopts on back haul link, during descending sub frame configuration sub-Configuration#19, configuration #3 subframe and #4 subframe and #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #7 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration on downlink subframes in return link #8, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #2, and/or, network side indicates back haul link UL Grant information to RN configuration on downlink subframes in return link #3, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB on back haul link sub-frame of uplink #7, i.e. k=4.
Preferably, using described sub-Configuration#1, sub-Configuration#7, sub-Configuration#12, sub-Configuration#15, sub-Configuration#16, sub-Configuration#18 and sub-Configuration#19 as list item, for these list items redistribute sequence number, and use these list items to construct described transmitting uplink data time-scale, to lay equal stress on new layout sub-Configuration sequence number, as shown in table 5.
The corresponding transmitting uplink data time-scale of table 5TDD UL/DL Configuration#2
Below in conjunction with accompanying drawing, embodiments of the invention three are described.
In the embodiment of the present invention, under this configuration of TDD UL-DL Configuration#3, the Un sub-frame configuration that network side instruction RN specifically uses.
When system adopts TDD UL-DL Configuration#3, the configurable #2 subframe of system, #3 subframe, #4 subframe, #7 subframe, #8 subframe, #9 subframe are as Un subframe, and the sequential relationship table of the Un subframe that concrete configuration uses and corresponding back haul link transmitting uplink data is as shown in table 6.Wherein D represents that corresponding subframe is descending sub frame, U represents that corresponding subframe is sub-frame of uplink, S represents special subframe, to the different Un sub-frame configuration situations of Configuration#3, carry out difference with sub-Configuration to represent, and provide the sequential relationship table example of corresponding back haul link transmitting uplink data.Numerical value k (k is positive integer) given in corresponding subframe (subframe#0-#9) represents that RN should carry out uplink according to distributed UnPUSCH resource to eNB in #n+k subframe when subframe #n carries Un ULGrant information.
As shown in table 6, for TDD UL-DL Configuration#3, can need to select the different corresponding subframes of Un UL/DL subframe proportional arrangement as Un subframe according to system, sub-Configurations#0-#24 corresponding back haul link transmitting uplink data sequential relationship table is as shown in table 6.The preferred embodiment of table 6 for obtaining according to different Un sub-frame configuration, in table 6, any one or more sub-Configurations and corresponding k value definition can form TDD UL-DL Configuration#3 back haul link transmitting uplink data sequential relationship.
Table 6 k for TDD Configurations#3
Wherein, sub-Configuration#0 to sub-Configuration#4 is the combination of a sub-frame of uplink and a descending sub frame.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#0, configuration #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#1, configuration #8 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#2, configuration #7 subframe is as downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #7 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=6 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#3, configuration #9 subframe is as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#4, configuration #9 subframe is as downlink subframes in return link, using #4 subframe as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #4 subframe.
Sub-Configuration#5 to sub-Configuration#11 is the combination of a sub-frame of uplink and two descending sub frames.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#5, configuration #7 subframe and #8 are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
Sub-Configuration#6 using #8 subframe and #9 subframe as Un descending sub frame, using the #2 subframe of next frame as Un sub-frame of uplink, i.e. k=4.Network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration#6, namely configuration #8 subframe and #9 are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side is to RN configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#7, configuration #7 subframe and #9 subframe are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration on downlink subframes in return link and #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#8, configuration #7 subframe and #8 subframe are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#9, configuration #8 subframe and #9 subframe are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#10, configuration #7 subframe and #9 subframe are downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #4 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#11, configuration #8 subframe and #9 subframe are downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #4 subframe.
Sub-Configuration#12 to sub-Configuration#14 is the combination of 3 descending sub frames and a sub-frame of uplink.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#12, configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#13, configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#14, configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #4 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #4 subframe.
Sub-Configuration#15 to sub-Configuration#21 is the combination of two descending sub frames and two sub-frame of uplink.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#15, configuration #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side is to RN configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; And/or, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#15, configuration #7 subframe and #8 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side is to RN configuration instruction back haul link ULGrant information in downlink subframes in return link #7 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; And/or, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#15, configuration #7 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #3 subframe are back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #7 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #2 subframe; And/or, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#18, configuration #7 subframe and #8 subframe are Un descending sub frame, and the #3 subframe of next frame and #4 subframe are Un sub-frame of uplink.Concrete, network side is to RN configuration instruction back haul link UL Grant information in downlink subframes in return link #7 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; And/or, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=6 in back haul link sub-frame of uplink #4 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#19, configuration #7 subframe and #9 subframe are Un descending sub frame, the #3 subframe of next frame and #4 subframe are Un sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #7 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=6 in back haul link sub-frame of uplink #3 subframe; And/or, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #4 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#20, configuration #8 subframe and #9 subframe are Un descending sub frame, the #3 subframe of next frame and #4 subframe are Un sub-frame of uplink, network side is to RN configuration instruction back haul link ULGrant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; And/or, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #4 subframe.
During sub-Configuration#21, configuration #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe and #4 subframe are back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #8 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, i.e. k=4, and/or, network side indicates back haul link UL Grant information to the configuration of access side in downlink subframes in return link #9 subframe, access side uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe, i.e. k=5.
Sub-Configuration#22 to sub-Configuration#24 is the combination of 3 descending sub frames and two sub-frame of uplink.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#22, configuring #7 subframe and #8 subframe and #9 subframe is Un descending sub frame, and the #2 subframe of next frame and #3 subframe are Un sub-frame of uplink, i.e. k=4.Concrete, network side is to RN configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; And/or, network side is to RN configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe.As shown in Figure 4.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#23, configuring #7 subframe and #8 subframe and #9 subframe is Un descending sub frame, and the #3 subframe of next frame and #4 subframe are Un sub-frame of uplink, i.e. k=5.Concrete, network side is to RN configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe; And/or, network side is to RN configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #4 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#24, configuring #7 subframe and #8 subframe and #9 subframe is Un descending sub frame, and the #2 subframe of next frame and #4 subframe are Un sub-frame of uplink.Concrete, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe; And/or, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=5 in back haul link sub-frame of uplink #4 subframe.
With embodiments of the invention one and embodiments of the invention two in like manner, in embodiments of the present invention, Un UL Grant is issued to RN at Un sub-frame of uplink network side, RN is after receiving this Un UL Grant, according to the sub-Configuration of its instruction, the PUSCH resource of distributing is used to send upstream data at corresponding Un sub-frame of uplink.
Preferably, using described sub-Configuration #3, sub-Configuration #8, sub-Configuration#13, sub-Configuration#15 and sub-Configuration#22 as list item, for these list items redistribute sequence number, and use these list items to construct described transmitting uplink data time-scale, as shown in table 7.
The corresponding transmitting uplink data time-scale of table 7 TDD UL/DL Configuration#3
Below in conjunction with accompanying drawing, embodiments of the invention four are described.
In the embodiment of the present invention, under this configuration of TDD UL-DL Configuration#4, the Un sub-frame configuration that network side instruction RN specifically uses.
When system adopts TDD UL-DL Configuration#4, the configurable #2 subframe of system, #3 subframe, #4 subframe, #7 subframe, #8 subframe, #9 subframe are as Un subframe, and the sequential relationship table of the Un subframe that concrete configuration uses and corresponding back haul link transmitting uplink data is as shown in table 8.Wherein D represents that corresponding subframe is descending sub frame, U represents that corresponding subframe is sub-frame of uplink, S represents special subframe, to the different Un sub-frame configuration situations of Configuration#4, carry out difference with sub-Configuration to represent, and provide the sequential relationship table example of corresponding back haul link transmitting uplink data.Numerical value k (k is positive integer) given in corresponding subframe (subframe#0-#9) represents that RN should carry out uplink according to distributed Un PUSCH resource to eNB in #n+k subframe when subframe #n carries Un ULGrant information.
As shown in table 8, for TDD UL-DL Configuration#4, can need to select the different corresponding subframes of Un UL/DL subframe proportional arrangement as shown in table 8 as Un subframe sub-Configurations#0-#19 corresponding back haul link transmitting uplink data sequential relationship table according to system.The preferred embodiment of table 8 for obtaining according to different Un sub-frame configuration, in table 8, any one or more sub-Confgurations and corresponding k value definition can form TDD UL-DL Configuration#4 back haul link transmitting uplink data sequential relationship.
Table 8 k for TDD Configurations#4
Wherein, sub-Configuration#0 and sub-Configuration#1 is the combination of a sub-frame of uplink and a descending sub frame.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#0, configuration #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#1, configuration #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
Sub-Configuration#2 to sub-Configuration#7 is the combination of a sub-frame of uplink and two descending sub frames.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#2, configuration #4 subframe and #8 subframe are as downlink subframes in return link, #2 subframe is as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#3, configuration #7 subframe and #8 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe, i.e. k=4, as shown in Figure 5.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#4, configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #2 subframe as back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#5, configuration #4 subframe and #9 are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#6, configuration #7 subframe and #9 are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#7, configuration #8 subframe and #9 subframe are as downlink subframes in return link, using #3 subframe as back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
Sub-Configuration#8 to sub-Configuration#13 is the combination of 3 descending sub frames and a sub-frame of uplink, i.e. k=4.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#8, configuring #4 subframe and #7 subframe and #8 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#9, configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#10, configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#11, configuring #4 subframe and #7 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#12, configuring #4 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#13, configuring #7 subframe and #8 subframe and #9 subframe is downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link ULGrant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
Sub-Configuration#14 and sub-Configuration#15 is the combination of 4 descending sub frames and two sub-frame of uplink.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#14, configuration #4 subframe and #7 subframe and #8 subframe and #9 subframe are downlink subframes in return link, #2 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #8 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #2 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#15, configuration #4 subframe and #7 subframe and #8 subframe and #9 subframe are downlink subframes in return link, #3 subframe is back haul link sub-frame of uplink, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#16, configuration #8 subframe and #9 subframe are Un descending sub frame, and the #2 subframe of next frame and #3 subframe are Un sub-frame of uplink.Concrete, network side is to RN configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; And/or, network side indicates back haul link UL Grant information to RN configuration in downlink subframes in return link #9 subframe, RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB, i.e. k=4 in back haul link sub-frame of uplink #3 subframe.
Sub-Configuration#17 and sub-Configuration#18 is the combination of 3 descending sub frames and two sub-frame of uplink.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#17, configuring #4 subframe and #8 subframe and #9 subframe is Un descending sub frame, and the #2 subframe of next frame and #3 subframe are Un sub-frame of uplink, i.e. k=4.Concrete, network side is to RN configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; And/or, network side is to RN configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe to configure sub-Configuration#18, configuring #7 subframe and #8 subframe and #9 subframe is Un descending sub frame, and the #2 subframe of next frame and #3 subframe are Un sub-frame of uplink, i.e. k=4.Concrete, network side is to RN configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; And/or, network side is to RN configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe.
When network side configuration adopts back haul link uplink and downlink subframe configuration sub-Configuration 19, configuration #4 subframe and #7 subframe and #8 subframe and #9 subframe are Un descending sub frame, and the #2 subframe of next frame and #3 subframe are Un sub-frame of uplink, i.e. k=4.Network side is to RN configuration instruction back haul link UL Grant information in downlink subframes in return link #8 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #2 subframe; And/or, network side is to RN configuration instruction back haul link ULGrant information in downlink subframes in return link #9 subframe, and RN uses distributed back haul link PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link sub-frame of uplink #3 subframe.
With embodiments of the invention one and embodiments of the invention two in like manner, in embodiments of the present invention, Un UL Grant is issued to RN at Un sub-frame of uplink network side, RN is after receiving this Un UL Grant, according to the sub-Configuration of its instruction, the PUSCH resource of distributing is used to send upstream data at corresponding Un sub-frame of uplink.
Preferably, using described sub-Configuration #1, sub-Configuration #6, sub-Configuration #7, sub-Configuration #13, sub-Configuration #15, sub-Configuration#16, sub-Configuration#18 and sub-Configuration#19 as list item, for these list items redistribute sequence number, and use these list items to construct described transmitting uplink data time-scale, as shown in table 9.
The corresponding transmitting uplink data time-scale of table 9 TDD UL/DL Configuration#4
Below in conjunction with accompanying drawing, embodiments of the invention five are described.
In the embodiment of the present invention, under this configuration of TDD UL-DL Configuration#6, the Un sub-frame configuration that network side instruction RN specifically uses.
When system adopts TDD UL-DL Configuration#6, the configurable #4 subframe of system and #9 subframe are as Un subframe, and the sequential relationship table of the Un subframe that concrete configuration uses and corresponding back haul link transmitting uplink data is as shown in table 10.Wherein D represents that corresponding subframe is descending sub frame, U represents that corresponding subframe is sub-frame of uplink, S represents special subframe, to the different Un sub-frame configuration situations of Configuration#4, carry out difference with sub-Configuration to represent, and provide the sequential relationship table example of corresponding back haul link transmitting uplink data.Numerical value k (k is positive integer) given in corresponding subframe (subframe#0-#9) represents that RN should carry out uplink according to distributed Un PUSCH resource to eNB in #n+k subframe when subframe #n carries Un UL Grant information.
As shown in table 10, for TDD UL-DL Configuration#6, can need to select the different corresponding subframes of Un UL/DL subframe proportional arrangement as shown in table 10 as Un subframe sub-Configurations#0 corresponding back haul link transmitting uplink data sequential relationship table according to system.The preferred embodiment of table 10 for obtaining according to different Un sub-frame configuration, in table 10, any one or more sub-Configurations and corresponding k value definition can form TDD UL-DL Configuration#6 back haul link transmitting uplink data sequential relationship.
Table 10 k for TDD Configurations#6
Sub-Configuration#0 is the combination of 1 descending sub frame and 1 sub-frame of uplink, and with #9 subframe for Un descending sub frame, the #4 subframe of next frame is Un sub-frame of uplink, i.e. k=5.Network side is to RN configuration instruction Un UL Grant information in the descending #9 subframe of back haul link, and RN uses distributed Un PUSCH resource bearing upstream data to carry out transmitting uplink data to eNB in back haul link up #4 subframe.As shown in Figure 6.Table 10 is the transmitting uplink data time-scale under this configuration of TDD Configurations#6.
The data transmission method that embodiments of the invention provide, fixed timing relationship is set up between the sub-frame of uplink shared by the descending sub frame shared by Un UL Grant and the PUSCH resource of distributing, described fixed timing relationship and network side are on back haul link, descending sub frame configuration one_to_one corresponding, on any one or multiple described back haul link, the fixed timing relationship of descending sub frame configuration and correspondence thereof forms transmitting uplink data time-scale, according to upper to back haul link of network side, descending sub frame configures, access side obtains corresponding fixed timing relationship from described transmitting uplink data time-scale, and according to this fixed timing relationship after downlink subframes in return link receives Un UL Grant, corresponding back haul link sub-frame of uplink use the PUSCH resource of distribution carry out transmitting uplink data to network side, solve the problem of the sequential relationship not having Un UL Grant and corresponding PUSCH resource.By setting up back haul link transmitting uplink data sequential relationship, according to the Un subframe situation of system actual disposition, eNB configures the Un UL Grant of instruction on Un DL subframe #n to RN configuration instruction ascending resource, RN is according to corresponding back haul link transmitting uplink data sequential relationship, the PUSCH resource of distributing is used to carry out transmitting uplink data to eNB on Un UL subframe #n+k, for TDD UL/DL Configurations#1, #2, #3, #4, the corresponding transmitting uplink data sequential relationship of #6 specification, achieve the effective transmitting uplink data of back haul link, reduce system resource configuration indication signaling expense.
Embodiments of the invention additionally provide a kind of data transmission system, and in TDD network, this system comprises network equipment and access side device;
Described network equipment, for setting up fixed timing relationship between the sub-frame of uplink shared by the descending sub frame shared by Un UL Grant and the PUSCH resource of distributing, described fixed timing relationship and network side, to back haul link uplink and downlink sub-frame configuration one_to_one corresponding, use the fixed timing relationship of any one or multiple described back haul link uplink and downlink sub-frame configuration and correspondence thereof to form transmitting uplink data time-scale;
Described access side device, for according to the uplink and downlink sub-frame configuration of network side to back haul link, corresponding fixed timing relationship is obtained from described transmitting uplink data time-scale, and according to this fixed timing relationship after downlink subframes in return link receives Un UL Grant, corresponding back haul link sub-frame of uplink uses the PUSCH resource of distribution carry out transmitting uplink data to described network equipment.
Further, described Un UL Grant uses DCI format 0 to carry, and configures instruction by described network equipment to described access side device.
Further, described access side device equipment is RN or highest version user terminal, and described highest version user terminal is specially R10 and more highest version user terminal.
Further, described network equipment is the combination of appointing one or more of following network element:
ENB, RN, MCE, GW, MME, EUTRAN, OAM manager.
The fixed timing relationship that this data transmission system uses when carrying out transfer of data, specifically see embodiments of the invention one to five, is not repeated.
The data transmission system that embodiments of the invention provide, can combine with the data transmission method that embodiments of the invention provide, fixed timing relationship is set up between the sub-frame of uplink shared by the descending sub frame shared by Un UL Grant and the PUSCH resource of distributing, described fixed timing relationship and network side are on back haul link, descending sub frame configuration one_to_one corresponding, on any one or multiple described back haul link, the fixed timing relationship of descending sub frame configuration and correspondence thereof forms transmitting uplink data time-scale, according to upper to back haul link of network side, descending sub frame configures, access side obtains corresponding fixed timing relationship from described transmitting uplink data time-scale, and according to this fixed timing relationship after downlink subframes in return link receives UnUL Grant, corresponding back haul link sub-frame of uplink use the PUSCH resource of distribution carry out transmitting uplink data to network side, solve the problem of the sequential relationship not having Un UL Grant and corresponding PUSCH resource.
One of ordinary skill in the art will appreciate that all or part of step of above-described embodiment can use computer program flow process to realize, described computer program can be stored in a computer-readable recording medium, described computer program (as system, unit, device etc.) on corresponding hardware platform performs, when performing, step comprising embodiment of the method one or a combination set of.
Alternatively, all or part of step of above-described embodiment also can use integrated circuit to realize, and these steps can be made into integrated circuit modules one by one respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
Each device/functional module/functional unit in above-described embodiment can adopt general calculation element to realize, and they can concentrate on single calculation element, also can be distributed on network that multiple calculation element forms.
Each device/functional module/functional unit in above-described embodiment using the form of software function module realize and as independently production marketing or use time, can be stored in a computer read/write memory medium.The above-mentioned computer read/write memory medium mentioned can be read-only memory, disk or CD etc.
Anyly be familiar with those skilled in the art in the technical scope that the present invention discloses, change can be expected easily or replace, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range described in claim.