Embodiment
In the present invention, multiple eNB are collaborative carries out CoMP uplink, and in the time of need to carrying out uplink data retransmission, UE carries out uplink data retransmission according to the indication of service eNB; Non-service eNB receive that service eNB sends when retransmitting relevant uplink scheduling information, receive the re-transmission upstream data of UE, and send to service eNB; Non-service eNB do not receive that service eNB sends when retransmitting relevant uplink scheduling information, do not carry out the operation relevant to uplink data retransmission.Based on above scheme, specific implementation of the present invention mainly can be divided into three kinds of implementations.
Implementation one
Multiple eNB are collaborative carries out CoMP uplink, and in the time of need to carrying out uplink data retransmission, uplink data retransmission is only carried out between service eNB and UE, and non-service eNB does not participate in retransmitting reception and the processing of upstream data.Non-service eNB does not need to know has uplink data retransmission to occur, and does not also need to participate in retransmitting the reception of upstream data and the forwarding to service eNB.Now, be equivalent to CoMP and be temporarily cancelled, only have service eNB to receive and retransmit upstream data, the upstream data in single eNB receives scene.Uplink data retransmission finishes, while preparing to receive the upstream data of next new biography, service eNB sends uplink scheduling information to non-service eNB, non-service eNB participates in reception and the processing of the upstream data of new biography according to the uplink scheduling information of receiving, in the collaborative upstream data that carries out CoMP of many eNB, receive scene.
This implementation is easy to realize, and existing LTE system is not changed to requirement.Consider that CoMP itself just can reduce uplink data retransmission odds greatly; Consider if the first new upstream data that passes upstream data, i.e. transmission for the first time adopts still bust this of CoMP simultaneously, the gain that the receive diversity of so non-service eNB can provide uplink data retransmission may be very limited, therefore, when uplink data retransmission, cancelling CoMP will be a kind of reasonably selection.
Fig. 3 is implementation one specific embodiment schematic flow sheet in the present invention, and as shown in Figure 3, specific implementation process comprises the following steps:
Step 101: service eNB, after being ready to uplink data scheduling, sends to non-service eNB by uplink scheduling information by the X2 interface between eNB, comprises the information such as UE data upload time, uplink scheduling licensed content in this uplink scheduling information.
Non-service eNB is received after uplink scheduling information, determines that the head that receives UE passes the time of upstream data, and determine according to uplink scheduling information the frequency resource that the first biography of UE upstream data is used according to the UE data upload time comprising in this uplink scheduling information.
Step 102: service eNB issues the first uplink scheduling license that passes upstream data to UE on PDCCH.
Step 103:UE detects after uplink scheduling license, the UE data upload time arrive time at Uplink Shared Channel (UL-SCH, UpLink Shared Channel) the upper head biography upstream data that sends, service eNB and the non-service eNB common head that receives UE on identical running time-frequency resource passes upstream data.
Step 104: non-service eNB passes upstream data by the head of the UE receiving and is forwarded to service eNB by X2 interface, passes upstream data at service eNB place to the head of UE and carries out combined decoding.
Step 105: if the head of UE passes the unsuccessful reception of upstream data, service eNB will send HARQ feedback information NACK or uplink scheduling license to UE, require UE to carry out uplink data retransmission, service eNB does not notify non-service eNB to have uplink data retransmission to be about to occur, therefore, non-service eNB does not participate in retransmitting the reception of upstream data.
Step 106:UE detects after NACK or uplink scheduling license, will carry out uplink data retransmission according to NACK or uplink scheduling license, retransmits upstream data and is received and process separately by service eNB.
If retransmit upstream data, still receive unsuccessfully, repeating step 105 and step 106, until corresponding upstream data successfully receives or reaches the number of retransmissions upper limit.In this process, by service eNB, receive alone and process all the time the re-transmission upstream data of UE.
Implementation two
Multiple eNB are collaborative carries out CoMP uplink, and in the time of need to carrying out uplink data retransmission, uplink data retransmission is carried out between service eNB and UE and non-service eNB and UE, and non-service eNB participates in retransmitting reception and the processing of upstream data.Service eNB need to be notified the time that non-service eNB carries out uplink data retransmission, modulation and the coded message (MCS that uplink data retransmission adopts, Modulation and CodingScheme) etc. information, but, it is first biography upstream data or re-transmission upstream data that non-service eNB is not distinguished the upstream data of receiving, its processing mode is completely identical with the first biography of reception upstream data.
Because the communication between service eNB and non-service eNB needs the time, non-service eNB participates in uplink data retransmission may meet the sequential requirement that ascending HARQ non-self-adapting retransmits, therefore, under this implementation, can only consider adaptive retransmission, that is to say, service eNB need to, by issue uplink scheduling license to UE on PDCCH, indicate UE to carry out adaptive retransmission to upstream data.
Fig. 4 is implementation two specific embodiment one schematic flow sheets in the present invention, and as shown in Figure 4, specific implementation process comprises the following steps:
Step 201: service eNB, after being ready to uplink data scheduling, sends to non-service eNB by uplink scheduling information by the X2 interface between eNB, comprises the information such as UE data upload time, uplink scheduling licensed content in this uplink scheduling information.
Non-service eNB is received after uplink scheduling information, determines that the head that receives UE passes the time of upstream data, and determine according to uplink scheduling information the frequency resource that the first biography of UE upstream data is used according to the UE data upload time comprising in this uplink scheduling information.
Step 202: service eNB issues the first uplink scheduling license that passes upstream data to UE on PDCCH.
Step 203:UE detects after uplink scheduling license, sends the first upstream data that passes when the UE data upload time arrives on UL-SCH, and service eNB and the non-service eNB common head that receives UE on identical running time-frequency resource passes upstream data.
Step 204: non-service eNB passes upstream data by the head of the UE receiving and is forwarded to service eNB by X2 interface, passes upstream data at service eNB place to the head of UE and carries out combined decoding.
Step 205: if the head of UE passes the unsuccessful reception of upstream data, service eNB sends and retransmits relevant uplink scheduling information to non-service eNB, comprises the information such as UE data re-transmission time, uplink scheduling licensed content, MCS in this uplink scheduling information.
Non-service eNB is received and is retransmitted after relevant uplink scheduling information, according to the UE data re-transmission time comprising in this uplink scheduling information, determine the time of the re-transmission upstream data that receives UE, according to uplink scheduling information, determine the first frequency resource that upstream data is used, the MCS adopting according to the definite re-transmission of the MCS comprising in this uplink scheduling information upstream data of passing of UE.
In subsequent treatment, for non-service eNB, it is first upstream data or the re-transmission upstream data of passing that the upstream data of receiving is not needed to distinguish, in the UE data re-transmission time, receive the upstream data from UE, non-service eNB is identical with the processing of first biography uploading data to the processing of the upstream data of receiving.
Step 206: service eNB issues uplink scheduling license on PDCCH, requires UE to carry out uplink data retransmission.
Step 207:UE detects after uplink scheduling license, the UE data re-transmission time is carried out uplink data retransmission while arriving, on UL-SCH, corresponding upstream data is carried out to adaptive retransmission, service eNB and non-service eNB be the common re-transmission upstream data that receives UE on identical running time-frequency resource.
Step 208: non-service eNB is forwarded to service eNB by the re-transmission upstream data of the UE receiving by X2 interface, the re-transmission upstream data at service eNB place to UE carries out combined decoding.Non-service eNB can pass upstream data according to MCS counterweight and carry out rectification before sending re-transmission upstream data to service eNB.It is relevant with the specific implementation of LTE system whether non-service eNB carries out rectification to the re-transmission upstream data of receiving.
It is first upstream data or the re-transmission upstream data of passing that non-service eNB does not need to distinguish to the upstream data of receiving, in the UE data re-transmission time, receive the upstream data from UE, non-service eNB is identical with the processing of first biography uploading data to the processing of the upstream data of receiving.
If retransmit upstream data, still receive unsuccessfully, repeating step 205~step 208, until corresponding upstream data successfully receives or reaches the number of retransmissions upper limit.
Fig. 5 is implementation two specific embodiment two schematic flow sheets in the present invention, as shown in Figure 5, in the present embodiment, adopt semi-persistent scheduling (SPS while carrying out CoMP uplink multiple eNB are collaborative, Semi-Persistent Scheduling), specific implementation process comprises the following steps:
Step 301: service eNB, after being ready to uplink data scheduling, sends to non-service eNB by uplink scheduling information by the X2 interface between eNB, comprises the information such as uplink scheduling licensed content, SPS configuration in this uplink scheduling information.SPS is periodic transfer of data for scheduling of resource.In described SPS configuration, comprise SPS and the SPS cycle of whether starting.
Non-service eNB is received after uplink scheduling information, according to the SPS configuration comprising in this uplink scheduling information, obtain the SPS cycle, and according to SPS configuration, obtain UE data upload time on each SPS cycle, head that non-service eNB receives UE and pass time of upstream data, and according to uplink scheduling information, determine that UE is first and pass the frequency resource that upstream data is used.
Step 302: service eNB issues the first SPS uplink scheduling license (SPS UL Grant) that passes upstream data to UE on PDCCH.
Step 303:UE detects after the license of SPS uplink scheduling, sends the first upstream data that passes when the UE data upload time in current SPS cycle arrives on UL-SCH, and service eNB and the non-service eNB common head that receives UE on identical running time-frequency resource passes upstream data.
Step 304: non-service eNB passes upstream data by the head of the UE receiving and is forwarded to service eNB by X2 interface, passes upstream data at service eNB place to the head of UE and carries out combined decoding.
Step 305: if the head of UE passes the unsuccessful reception of upstream data, service eNB sends and retransmits relevant uplink scheduling information to non-service eNB, comprises the information such as UE data re-transmission time, uplink scheduling licensed content, MCS in this uplink scheduling information.Service eNB, when definite UE data re-transmission time, need to make UE data re-transmission time and the UE data upload time on the SPS cycle not conflict.
Non-service eNB is received and is retransmitted after relevant uplink scheduling information, according to the UE data re-transmission time comprising in this uplink scheduling information, determine the time of the re-transmission upstream data that receives UE, according to uplink scheduling information, determine the first frequency resource that upstream data is used, the MCS adopting according to the definite re-transmission of the MCS comprising in this uplink scheduling information upstream data of passing of UE.
In subsequent treatment, for non-service eNB, identical to the dynamic dispatching processing of the processing of the upstream data of receiving and first biography upstream data, in the UE data re-transmission time, receive the upstream data from UE.Owing to there being SPS configuration, the UE data upload time on the SPS cycle, the upstream data of non-service eNB automatic reception UE, and be forwarded to service eNB.
Step 306: service eNB issues uplink scheduling license on PDCCH, requires UE to carry out uplink data retransmission.
Step 307:UE detects after uplink scheduling license, the UE data re-transmission time is carried out uplink data retransmission while arriving, on UL-SCH, corresponding upstream data is carried out to adaptive retransmission, service eNB and non-service eNB be the common re-transmission upstream data that receives UE on identical running time-frequency resource.
Step 308: non-service eNB is forwarded to service eNB by the re-transmission upstream data of the UE receiving by X2 interface, the re-transmission upstream data at service eNB place to UE carries out combined decoding.
For non-service eNB, identical to the dynamic dispatching processing of the processing of the upstream data of receiving and first biography upstream data, in the UE data re-transmission time, receive and forward from the upstream data of UE and to service eNB.
If retransmit upstream data, still receive unsuccessfully, repeating step 305~step 308, until corresponding upstream data successfully receives or reaches the number of retransmissions upper limit.
Fig. 6 is implementation two specific embodiment three schematic flow sheets in the present invention, as shown in Figure 6, in the present embodiment, adopt Transmission Time Interval binding (TTIBundling while carrying out CoMP uplink multiple eNB are collaborative, Transmission Time Interval Bundling), specific implementation process comprises the following steps:
Step 401: service eNB, after being ready to uplink data scheduling, sends to non-service eNB by uplink scheduling information by the X2 interface between eNB, comprises the information such as UE data upload time, uplink scheduling licensed content, TTI configuration in this uplink scheduling information.
Non-service eNB is received after uplink scheduling information, according to the UE data upload time comprising in this uplink scheduling information, determine that the head of reception UE passes the time of upstream data, according to the TTI configuration comprising in this uplink scheduling information, obtain the relevant information of TTI, and determine according to uplink scheduling information the frequency resource that the first biography of UE upstream data is used.
Step 402: service eNB issues the first TTI uplink scheduling license (TTI UL Grant) that passes upstream data to UE on PDCCH.
Step 403:UE detects after the license of TTI uplink scheduling, sends the first upstream data that passes when the UE data upload time arrives on UL-SCH, and service eNB and the non-service eNB common head that receives UE on identical running time-frequency resource passes upstream data.
Step 404: non-service eNB passes upstream data by the head of the UE receiving and is forwarded to service eNB by X2 interface, passes upstream data at service eNB place to the head of UE and carries out combined decoding.
Step 405: if the head of UE passes the unsuccessful reception of upstream data, service eNB sends and retransmits relevant uplink scheduling information to non-service eNB, comprises the information such as UE data re-transmission time, uplink scheduling licensed content, MCS in this uplink scheduling information.If non-service eNB is not stored TTI configuration, to retransmitting relevant uplink scheduling information also need to comprise TTI configuration.TTI configuration is only just used when non-service eNB receives wave point data.
Non-service eNB is received and is retransmitted after relevant uplink scheduling information, according to the UE data re-transmission time comprising in this uplink scheduling information, determine the time of the re-transmission upstream data that receives UE, according to uplink scheduling information, determine the first frequency resource that upstream data is used, the MCS adopting according to the definite re-transmission of the MCS comprising in this uplink scheduling information upstream data of passing of UE.
Step 406: service eNB issues uplink scheduling license on PDCCH, requires UE to carry out uplink data retransmission.
Step 407:UE detects after uplink scheduling license, the UE data re-transmission time is carried out uplink data retransmission while arriving, on UL-SCH, corresponding upstream data is carried out to adaptive retransmission, service eNB and non-service eNB be the common re-transmission upstream data that receives UE on identical running time-frequency resource.
Step 408: non-service eNB is forwarded to service eNB by the re-transmission upstream data of the UE receiving by X2 interface, the re-transmission upstream data at service eNB place to UE carries out combined decoding.
For non-service eNB, identical with the processing of first biography upstream data to the processing of the upstream data of receiving, in the UE data re-transmission time, receive and forward from the upstream data of UE and to service eNB.
If retransmit upstream data, still receive unsuccessfully, repeating step 405~step 408, until corresponding upstream data successfully receives or reaches the number of retransmissions upper limit.
Implementation three
When service eNB utilizes NACK indication UE to carry out non-self-adapting re-transmission to upstream data, non-service eNB does not participate in retransmitting the reception of upstream data; Service eNB utilizes uplink scheduling to permit that, when indication UE carries out adaptive retransmission to upstream data, non-service eNB participation retransmits the reception of upstream data, and its processing mode is completely identical with the first biography of reception upstream data.Service eNB need to be notified the information such as the time that non-service eNB carries out uplink data retransmission, the MCS that uplink data retransmission adopts.In implementation three, service eNB utilizes NACK or uplink scheduling license to determine that UE carries out non-self-adapting re-transmission or adaptive retransmission to upstream data.
Fig. 7 is implementation three specific embodiment schematic flow sheets in the present invention, and as shown in Figure 7, specific implementation process comprises the following steps:
Step 501: service eNB, after being ready to uplink data scheduling, sends to non-service eNB by uplink scheduling information by the X2 interface between eNB, comprises the information such as UE data upload time, uplink scheduling licensed content in this uplink scheduling information.
Non-service eNB is received after uplink scheduling information, determines that the head that receives UE passes the time of upstream data, and determine according to uplink scheduling information the frequency resource that the first biography of UE upstream data is used according to the UE data upload time comprising in this uplink scheduling information.
Step 502: service eNB issues the first uplink scheduling license that passes upstream data to UE on PDCCH.
Step 503:UE detects after uplink scheduling license, sends the first upstream data that passes when the UE data upload time arrives on UL-SCH, and service eNB and the non-service eNB common head that receives UE on identical running time-frequency resource passes upstream data.
Step 504: non-service eNB passes upstream data by the head of the UE receiving and is forwarded to service eNB by X2 interface, passes upstream data at service eNB place to the head of UE and carries out combined decoding.
Step 505: if the head of UE passes the unsuccessful reception of upstream data, service eNB will send NACK to UE, requires UE to carry out uplink data retransmission.Because service eNB requires UE, upstream data is carried out to non-self-adapting re-transmission, therefore, service eNB does not notify non-service eNB to have uplink data retransmission to be about to occur, and like this, non-service eNB will not participate in retransmitting the reception of upstream data.
Step 506:UE detects after NACK, according to NACK, upstream data is carried out to non-self-adapting re-transmission, retransmits upstream data and is received and process separately by service eNB.
Step 507: if the still unsuccessful reception of the re-transmission upstream data of UE, service eNB determine upstream data is carried out to non-self-adapting re-transmission or adaptive retransmission, below take adaptive retransmission as example.Service eNB sends and retransmits relevant uplink scheduling information to non-service eNB, comprises the information such as UE data re-transmission time, uplink scheduling licensed content, MCS in this uplink scheduling information.
Non-service eNB is received and is retransmitted after relevant uplink scheduling information, according to the UE data re-transmission time comprising in this uplink scheduling information, determine the time of the re-transmission upstream data that receives UE, according to uplink scheduling information, determine the first frequency resource that upstream data is used, the MCS adopting according to the definite re-transmission of the MCS comprising in this uplink scheduling information upstream data of passing of UE.
Step 508: service eNB issues uplink scheduling license on PDCCH, requires UE to carry out uplink data retransmission.
Step 509:UE detects after uplink scheduling license, the UE data re-transmission time is carried out uplink data retransmission while arriving, on UL-SCH, corresponding upstream data is carried out to adaptive retransmission, service eNB and non-service eNB be the common re-transmission upstream data that receives UE on identical running time-frequency resource.
Step 510: non-service eNB is forwarded to service eNB by the re-transmission upstream data of the UE receiving by X2 interface, the re-transmission upstream data at service eNB place to UE carries out combined decoding.
It is first upstream data or the re-transmission upstream data of passing that non-service eNB does not need to distinguish to the upstream data of receiving, in the UE data re-transmission time, receive the upstream data from UE, non-service eNB is identical with the processing of first biography uploading data to the processing of the upstream data of receiving.
If retransmit upstream data, still receive unsuccessfully, repeating step 507~step 510, until corresponding upstream data successfully receives or reaches the number of retransmissions upper limit.
Implementation one and implementation three are equally applicable to the upstream datas such as SPS, TTI binding and transmit scene, and specific implementation is basic identical, does not repeat them here.
For the various embodiments described above, for simple description, therefore it is all expressed as to a series of combination of actions, but those skilled in the art should know, the present invention is not subject to the restriction of described sequence of movement, because according to the present invention, some step can adopt other orders or carry out simultaneously.
Fig. 8 is the collaborative uplink data retransmission system architecture schematic diagram that carries out CoMP uplink of multiple eNB in the present invention, as shown in Figure 8, this system comprises UE, service eNB and at least one non-service eNB, and service eNB and non-service eNB are worked in coordination with associating Multipoint process CoMP uplink
UE is for retransmitting upstream data according to the indication of service eNB; Service eNB is used to indicate UE and carries out uplink data retransmission or indicate UE to carry out uplink data retransmission and send and retransmit relevant uplink scheduling information to non-service eNB; Non-service eNB for receive from service eNB to retransmit after relevant uplink scheduling information, receive from the re-transmission upstream data of UE and be sent to service eNB.Service eNB is further used for receiving the re-transmission upstream data from UE or UE and non-service eNB.
The above, be only preferred embodiment of the present invention, is not intended to limit protection scope of the present invention.