CN101873631A - Processing method and system for uplink data retransmission - Google Patents
Processing method and system for uplink data retransmission Download PDFInfo
- Publication number
- CN101873631A CN101873631A CN200910083052A CN200910083052A CN101873631A CN 101873631 A CN101873631 A CN 101873631A CN 200910083052 A CN200910083052 A CN 200910083052A CN 200910083052 A CN200910083052 A CN 200910083052A CN 101873631 A CN101873631 A CN 101873631A
- Authority
- CN
- China
- Prior art keywords
- service enb
- uplink
- enb
- data
- uplink scheduling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a processing method and a processing system for uplink data retransmission. In the scheme of the invention, a plurality of eNBs collaborate to perform CoMP uplink transmission and UE performs the uplink data retransmission according to the instruction of the eNB when the uplink data retransmission is needed; when receiving uplink scheduling information related to the retransmission transmitted by the serving eNB, the non-serving eNB receives the retransmission uplink data of the UE and transmits the data to the serving eNB; and when not receiving the uplink scheduling information related to the retransmission transmitted by the serving eNB, the non-serving eNB does not perform the operation related to the uplink data retransmission. The method has the advantages of making the behaviors of the serving eNB and the non-serving eNB clear, smoothly receiving the retransmission uplink data, solving the problem of the uplink data retransmission during the CoMP uplink transmission of the plurality of collaborative eNBs well, and adapting to the various special uplink data transmission scenes, along with no need of alteration of the uplink data transmission behavior on the UE side, easy implementation, and less required alteration of the LTE system.
Description
Technical field
The present invention relates to wireless communication technology, be meant a kind of especially based on many base stations (eNB, EvolvedNodeB) processing method and the system of the uplink data retransmission of collaborative associating multiple spot processing (CoMP, Coordinated Multiple Point).
Background technology
3G (Third Generation) Moblie Long Term Evolution (LTE, Long Term Evolution) Evolved UTRAN (E-UTRAN of system, Evolved Universal Terrestrial Radio Access Network) in, by eNB is each user terminal (UE, User Equipment) Resources allocation, the data of uplink downlink are transmitted by the up-downgoing shared channel.The access technology that E-UTRAN adopts is OFDM (OFDM, Orthogonal Frequency Division Multiplexing) technology, the RRM of E-UTRAN system is compared with second generation mobile communication system, characteristics with big bandwidth, process of many time, the Radio Resource of E-UTRAN system occurs with time and frequency bidimensional, and the number of users that can carry increases greatly.
For being positioned at the UE that eNB covers the edge, may receive wireless signal simultaneously near several adjacent eNB, the wireless signal of this UE emission also can be received by near a plurality of eNB.In this case, can coordinate a plurality of eNB carries out receiving uniting of up-downgoing wireless signal and uniting transmission, so-called CoMP technology that Here it is to this UE simultaneously.Utilize CoMP technology and relevant signal processing technology, can carry out data diversity and spatial reuse, obtain the gain of wireless signal, improve the reliability and the data throughout of transmission of wireless signals the up-downgoing wireless signal.
A plurality of neighbor cells of CoMP participating may belong to same eNB control, also may belong to different e NB (Inter eNB) control.When CoMP occurs in different e NB, UE is the down control channel (PDCCH of an eNB therein only, Physical Downlink Control Channel) goes up the instruction of reception up-downgoing scheduling of resource, also only upload and mix automatic repeat requests (HARQ to same eNB, Hybrid ARQ, Hybrid Automatic Repeat Request) feedback information and other measurement report information, this eNB is called service eNB (Serving eNB), and the eNB of other CoMP participatings is called non-service eNB (Non-Serving eNB) or cooperation eNB (Collaborative eNB).Under the situation of a plurality of eNB CoMP participatings, for reaching the purpose that the up-downgoing data aggregate sends, unites reception, service eNB need send to non-service eNB by the X2 interface between eNB with the scheduling of resource instruction, from but not service eNB can on identical time, frequency resource, send downlink data or receive upstream data with service eNB from UE to UE, as shown in Figure 1.
The E-UTRAN system supports the HARQ function, mode that HARQ adopts that N road concurrent process is stopped etc. at layer 1, be between the physical layer peer-entities transmission block (TB, Transport Block) to be sent and retransmits, improve the reliability that transmission block successfully sends with this.These HARQ processes and HARQ entity are associated.Transmitting uplink data for the LTE system, the ascending HARQ course number is 8, adopts synchronous transmission mechanism, that is to say that the transmission of an ascending HARQ course or re-transmission occur in fixed time, receiving terminal, be eNB known transmission moment of taking place in advance, do not need additionally to identify the HARQ process number.
UE goes up at the HARQ of eNB feedback channel (PHICH, Physical HARQ Indicator Channel) and receives the HARQ feedback information, as ACK or NACK.For a concrete ascending HARQ course, if the HARQ feedback information of receiving is NACK, and on PDCCH, do not detect uplink scheduling permission (UL Grant), then this ascending HARQ course will belong to the automatic non-self-adapting data retransmission of the moment of this ascending HARQ course at the next one, shown in Fig. 2 A; If detect the uplink scheduling permission on PDCCH, then this ascending HARQ course will belong to the moment automatic adaptive data retransmission of this ascending HARQ course at the next one.Perhaps, New Data Flag (the NDI that ascending HARQ course comprises in also can permitting according to the uplink scheduling that eNB issues on PDCCH, New Data Indication) determines that transmitting new data still is the re-transmission legacy data, during data re-transmission, this ascending HARQ course will belong to the moment automatic adaptive data retransmission of this ascending HARQ course at the next one, shown in Fig. 2 B.
A plurality of eNB are collaborative to carry out under the situation of CoMP uplink, and UE only receives the HARQ feedback information on the PHICH of service eNB usually, and determines whether to carry out data re-transmission according to the HARQ feedback information of receiving.When carrying out uplink data retransmission as for needs, whether non-service eNB participates in uplink data retransmission and how to participate in uplink data retransmission, does not provide clearly to describe in existing scheme.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of processing method and system of uplink data retransmission, the concrete processing of non-service eNB that clear and definite a plurality of eNB are collaborative when carrying out uplink data retransmission under the situation of CoMP uplink.
For achieving the above object, technical scheme of the present invention is achieved in that
A kind of processing method of uplink data retransmission, the collaborative associating multiple spot of a plurality of base station eNB is handled the CoMP uplink, and in the time of need carrying out uplink data retransmission, this method comprises: user terminal UE carries out uplink data retransmission according to the indication that service eNB sends; Non-service eNB receive that service eNB sends when retransmitting relevant uplink scheduling information, the re-transmission upstream data of reception UE, and send to service eNB; Do not receive that service eNB sends when retransmitting relevant uplink scheduling information, do not carry out the operation relevant with uplink data retransmission.
The indication that described UE sends according to service eNB is carried out further comprising before the uplink data retransmission: service eNB sends NACK or uplink scheduling permission to UE, does not send the uplink scheduling information relevant with re-transmission to non-service eNB; The indication that described UE sends according to service eNB is carried out further comprising after the uplink data retransmission: service eNB receives the re-transmission upstream data from UE.
The indication that described UE sends according to service eNB is carried out further comprising before the uplink data retransmission: service eNB sends and retransmits relevant uplink scheduling information to non-service eNB, sends uplink scheduling to UE and permits; Described UE carries out uplink data retransmission according to the indication that service eNB sends, and is specially: the uplink scheduling permission that UE sends according to service eNB is carried out self adaptation to upstream data and is retransmitted; The indication that described UE sends according to service eNB is carried out further comprising after the uplink data retransmission: service eNB receives the re-transmission upstream data from UE and non-service eNB.
The described uplink scheduling information relevant with re-transmission comprises at least: the UE data re-transmission time; Described non-service eNB receives the re-transmission upstream data of UE, is specially: when non-service eNB arrived in the described UE data re-transmission time, receive the re-transmission upstream data of UE.
Described needs carry out further comprising before the uplink data retransmission: service eNB sends uplink scheduling information to non-service eNB, and this uplink scheduling information comprises semi-persistent scheduling SPS configuration or Transmission Time Interval TTI configuration.
When described uplink scheduling information comprises the SPS configuration, comprise SPS and the SPS cycle of whether starting in the described SPS configuration; Described with retransmit relevant uplink scheduling information in UE data re-transmission time of comprising do not conflict with the UE data upload time of described each SPS on the cycle.
When comprising the TTI configuration in the described uplink scheduling information, further comprise the TTI configuration in the described uplink scheduling information relevant with re-transmission.
The indication that described UE sends according to service eNB is carried out further comprising before the uplink data retransmission: when service eNB sends NACK to UE, do not send the uplink scheduling information relevant with re-transmission to non-service eNB; Described UE carries out uplink data retransmission according to the indication that service eNB sends, and is specially: the NACK that UE sends according to service eNB carries out non-self-adapting to upstream data and retransmits; The indication that described UE sends according to service eNB is carried out further comprising after the uplink data retransmission: service eNB receives the re-transmission upstream data from UE;
The indication that described UE sends according to service eNB is carried out further comprising before the uplink data retransmission: when service eNB sends the uplink scheduling information relevant with re-transmission to non-service eNB, send the uplink scheduling permission to UE; Described UE carries out uplink data retransmission according to the indication that service eNB sends, and is specially: the uplink scheduling permission that UE sends according to service eNB is carried out self adaptation to upstream data and is retransmitted; The indication that described UE sends according to service eNB is carried out further comprising after the uplink data retransmission: service eNB receives the re-transmission upstream data from UE and non-service eNB.
A kind of treatment system of uplink data retransmission, this system comprises: UE, service eNB and at least one non-service eNB, the collaborative associating multiple spot of service eNB and non-service eNB is handled the CoMP uplink, in the time of need carrying out uplink data retransmission, described UE is used for according to the indication of service eNB upstream data being retransmitted; Described service eNB is used to indicate UE to carry out uplink data retransmission or indication UE carries out uplink data retransmission and sends the uplink scheduling information relevant with re-transmission to non-service eNB; Described non-service eNB be used to receive from service eNB with retransmit relevant uplink scheduling information after, reception is from the re-transmission upstream data of UE and be sent to service eNB.
Described service eNB is further used for: receive the re-transmission upstream data from UE or UE and non-service eNB.
Among the present invention program, a plurality of eNB are collaborative to carry out the CoMP uplink, and in the time of need 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, the re-transmission upstream data of reception 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 with uplink data retransmission, the behavior of clear and definite service eNB and non-service eNB, can finish the reception that retransmits upstream data smoothly, and not need the upstream data transmission behavior of UE side is made amendment.
The various technical schemes that provide among the present invention all can solve the uplink data retransmission problem when a plurality of eNB are collaborative to carry out the CoMP uplink well, various HARQ feedbacks and HARQ sequence problem when a plurality of eNB are collaborative to carry out uplink data retransmission have been avoided dexterously, be easy to realize, can adapt to various special upstream datas and transmit scene, as SPS, TTI binding etc., seldom to the change of LTE system requirements.
Description of drawings
Fig. 1 utilizes the CoMP technology to carry out the schematic network structure of a plurality of eNB Combined Treatment;
Fig. 2 A is that the non-self-adapting of LTE system ascending HARQ retransmits schematic diagram;
Fig. 2 B is that the self adaptation of LTE system ascending HARQ retransmits schematic diagram;
Fig. 3 is implementation one specific embodiment schematic flow sheet among the present invention;
Fig. 4 is implementation two specific embodiments one flow process schematic diagram among the present invention;
Fig. 5 is implementation two specific embodiments two flow process schematic diagrames among the present invention;
Fig. 6 is implementation two specific embodiments three schematic flow sheets among the present invention;
Fig. 7 is implementation three specific embodiment schematic flow sheets among the present invention;
Fig. 8 is the collaborative uplink data retransmission system architecture schematic diagram that carries out the CoMP uplink of a plurality of eNB among the present invention.
Embodiment
Among the present invention, a plurality of eNB are collaborative to carry out the CoMP uplink, and in the time of need 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, the re-transmission upstream data of reception 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 with uplink data retransmission.Based on above scheme, specific implementation of the present invention mainly can be divided into three kinds of implementations.
Implementation one
A plurality of eNB are collaborative to carry out the CoMP uplink, and in the time of need 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 the reception and the processing of upstream data.Non-service eNB does not need to know has uplink data retransmission to take place, and does not also need to participate in to retransmit the reception of upstream data and to the forwarding of service eNB.At this moment, be equivalent to CoMP and temporarily be cancelled, have only service eNB to receive and retransmit upstream data, the upstream data that is in single eNB receives scene.Uplink data retransmission finishes, when preparing to receive the upstream data of next new biography, service eNB sends uplink scheduling information to non-service eNB, non-service eNB is in the collaborative upstream data that carries out CoMP of many eNB and receives scene according to the reception and the processing of the upstream data of the uplink scheduling information participation new biography of receiving.
This implementation is easy to realize, requirement is not changed by existing LTE system.Consider that CoMP itself just can reduce the uplink data retransmission odds greatly; Consider simultaneously if the first new upstream data of catching line data, i.e. transmission for the first time adopts CoMP bust this still, the gain that the receive diversity of so non-service eNB can provide uplink data retransmission may be very limited, therefore, cancellation CoMP will be a kind of rational selection when uplink data retransmission.
Fig. 3 is implementation one specific embodiment schematic flow sheet among the present invention, and as shown in Figure 3, the specific implementation process may further comprise the steps:
Step 101: service eNB sends to non-service eNB with uplink scheduling information by the X2 interface between eNB after being ready to uplink data scheduling, comprises information such as UE data upload time, uplink scheduling licensed content in this uplink scheduling information.
After non-service eNB is received uplink scheduling information, determine that according to the UE data upload time that comprises in this uplink scheduling information the head of reception UE catches the time of line data, and determine that according to uplink scheduling information UE head catches the employed frequency resource of line data.
Step 102: service eNB issues the uplink scheduling permission that head catches line data to UE on PDCCH.
After step 103:UE detects the uplink scheduling permission, when the UE data upload time arrives at Uplink Shared Channel (UL-SCH, UpLink Shared Channel) go up transmission head and catch line data, service eNB and the non-service eNB common head that receives UE on identical running time-frequency resource catches line data.
Step 104: non-service eNB is caught line data with the head of the UE that receives and is forwarded to service eNB by X2 interface, at the service eNB place head of UE is caught line data and carries out combined decoding.
Step 105: successfully do not receive if the head of UE catches line data, service eNB will send HARQ feedback information NACK or uplink scheduling permission 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 take place, therefore, non-service eNB does not participate in retransmitting the reception of upstream data.
After step 106:UE detects NACK or uplink scheduling permission, will carry out uplink data retransmission, and retransmit upstream data and receive separately and handle by service eNB according to NACK or uplink scheduling permission.
Still receive unsuccessfully if retransmit upstream data, then repeating step 105 and step 106 successfully receive or reach the number of retransmissions upper limit until corresponding upstream data.In this process, receive and handle the re-transmission upstream data of UE all the time alone by service eNB.
Implementation two
A plurality of eNB are collaborative to carry out the CoMP uplink, in the time of need carrying out uplink data retransmission, uplink data retransmission service eNB and UE, and non-service eNB and UE between carry out, promptly non-service eNB participates in the reception and the processing of re-transmission upstream data.Service eNB need be notified the time that non-service eNB carries out uplink data retransmission, modulation and the coded message (MCS that uplink data retransmission adopted, Modulation and CodingScheme) information such as, but, it is that head catches line data or re-transmission upstream data that non-service eNB is not distinguished the upstream data of receiving, fully to catch line data identical with reception head for its processing mode.
Because the communication between service eNB and the non-service eNB needs the time, non-service eNB participates in uplink data retransmission may satisfy the sequential requirement that the ascending HARQ non-self-adapting retransmits, therefore, can only consider under this implementation that self adaptation retransmits, that is to say, service eNB need be indicated UE that upstream data is carried out self adaptation and retransmit by issue the uplink scheduling permission to UE on PDCCH.
Fig. 4 is implementation two specific embodiments one flow process schematic diagram among the present invention, and as shown in Figure 4, the specific implementation process may further comprise the steps:
Step 201: service eNB sends to non-service eNB with uplink scheduling information by the X2 interface between eNB after being ready to uplink data scheduling, comprises information such as UE data upload time, uplink scheduling licensed content in this uplink scheduling information.
After non-service eNB is received uplink scheduling information, determine that according to the UE data upload time that comprises in this uplink scheduling information the head of reception UE catches the time of line data, and determine that according to uplink scheduling information UE head catches the employed frequency resource of line data.
Step 202: service eNB issues the uplink scheduling permission that head catches line data to UE on PDCCH.
After step 203:UE detects the uplink scheduling permission, send head when the UE data upload time arrives and catch line data on UL-SCH, service eNB is caught line data with non-service eNB common head that receives UE on identical running time-frequency resource.
Step 204: non-service eNB is caught line data with the head of the UE that receives and is forwarded to service eNB by X2 interface, at the service eNB place head of UE is caught line data and carries out combined decoding.
Step 205: successfully receive if the head of UE catches line data, service eNB sends the uplink scheduling information relevant with re-transmission to non-service eNB, comprises information such as UE data re-transmission time, uplink scheduling licensed content, MCS in this uplink scheduling information.
Non-service eNB receive with retransmit relevant uplink scheduling information after, determine the time of the re-transmission upstream data of reception UE according to the UE data re-transmission time that comprises in this uplink scheduling information, determine that according to uplink scheduling information UE head catches the employed frequency resource of line data, determine to retransmit the MCS that upstream data adopted according to the MCS that comprises in this uplink scheduling information.
In the subsequent treatment, for non-service eNB, it is that head catches line data or re-transmission upstream data that the upstream data of receiving is not needed to distinguish, receive upstream data from UE in the UE data re-transmission time, non-service eNB is identical with the first processing of catching data to the processing of the upstream data received.
Step 206: service eNB issues the uplink scheduling permission on PDCCH, require UE to carry out uplink data retransmission.
After step 207:UE detects the uplink scheduling permission, the UE data re-transmission time is carried out uplink data retransmission when arriving, on UL-SCH, corresponding upstream data is carried out self adaptation and retransmit, service eNB and non-service eNB common re-transmission upstream data that receives UE on identical running time-frequency resource.
Step 208: non-service eNB is forwarded to service eNB with the re-transmission upstream data of the UE that receives by X2 interface, and the re-transmission upstream data at the service eNB place to UE carries out combined decoding.Non-service eNB can be caught line data according to the MCS counterweight and carry out rectification before service eNB sends the re-transmission upstream data.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 that head catches line data or re-transmission upstream data that non-service eNB does not need to distinguish to the upstream data of receiving, receive upstream data from UE in the UE data re-transmission time, non-service eNB is identical with the first processing of catching data to the processing of the upstream data received.
Still receive unsuccessfully if retransmit upstream data, repeating step 205～step 208 then successfully receives or reaches the number of retransmissions upper limit until corresponding upstream data.
Fig. 5 is implementation two specific embodiments two flow process schematic diagrames among the present invention, as shown in Figure 5, in the present embodiment, adopt semi-persistent scheduling (SPS when carrying out the CoMP uplink in that a plurality of eNB are collaborative, Semi-Persistent Scheduling), the specific implementation process may further comprise the steps:
Step 301: service eNB sends to non-service eNB with uplink scheduling information by the X2 interface between eNB after being ready to uplink data scheduling, comprises information such as uplink scheduling licensed content, SPS configuration in this uplink scheduling information.SPS is used for scheduling of resource and is periodic transfer of data.Comprise SPS and the SPS cycle of whether starting in the described SPS configuration.
After non-service eNB is received uplink scheduling information, obtain the SPS cycle according to the SPS configuration that comprises in this uplink scheduling information, and obtain the UE data upload time of each SPS on the cycle, be the time that head that non-service eNB receives UE catches line data, and determine that according to uplink scheduling information UE head catches the employed frequency resource of line data according to SPS configuration.
Step 302: service eNB issues the SPS uplink scheduling permission (SPS UL Grant) that head catches line data to UE on PDCCH.
After step 303:UE detects the permission of SPS uplink scheduling, send head when the UE data upload time in current SPS cycle arrives and catch line data on UL-SCH, service eNB is caught line data with non-service eNB common head that receives UE on identical running time-frequency resource.
Step 304: non-service eNB is caught line data with the head of the UE that receives and is forwarded to service eNB by X2 interface, at the service eNB place head of UE is caught line data and carries out combined decoding.
Step 305: successfully receive if the head of UE catches line data, service eNB sends the uplink scheduling information relevant with re-transmission to non-service eNB, comprises information such as UE data re-transmission time, uplink scheduling licensed content, MCS in this uplink scheduling information.Service eNB during the time, need make UE data re-transmission time and the UE data upload time of SPS on the cycle not conflict in definite UE data re-transmission.
Non-service eNB receive with retransmit relevant uplink scheduling information after, determine the time of the re-transmission upstream data of reception UE according to the UE data re-transmission time that comprises in this uplink scheduling information, determine that according to uplink scheduling information UE head catches the employed frequency resource of line data, determine to retransmit the MCS that upstream data adopted according to the MCS that comprises in this uplink scheduling information.
In the subsequent treatment, for non-service eNB, the processing and the first dynamic dispatching of catching line data of the upstream data received are handled identical, received upstream data from UE in the UE data re-transmission time.Since the SPS configuration is arranged, in the UE data upload time of SPS on the cycle, the upstream data of non-service eNB automatic reception UE, and be forwarded to service eNB.
Step 306: service eNB issues the uplink scheduling permission on PDCCH, require UE to carry out uplink data retransmission.
After step 307:UE detects the uplink scheduling permission, the UE data re-transmission time is carried out uplink data retransmission when arriving, on UL-SCH, corresponding upstream data is carried out self adaptation and retransmit, service eNB and non-service eNB common re-transmission upstream data that receives UE on identical running time-frequency resource.
Step 308: non-service eNB is forwarded to service eNB with the re-transmission upstream data of the UE that receives by X2 interface, and the re-transmission upstream data at the service eNB place to UE carries out combined decoding.
For non-service eNB, the processing and the first dynamic dispatching of catching line data of the upstream data received are handled identical, receive in the UE data re-transmission time and to transmit from the upstream data of UE and to service eNB.
Still receive unsuccessfully if retransmit upstream data, repeating step 305～step 308 then successfully receives or reaches the number of retransmissions upper limit until corresponding upstream data.
Fig. 6 is implementation two specific embodiments three schematic flow sheets among the present invention, as shown in Figure 6, in the present embodiment, adopt Transmission Time Interval binding (TTIBundling when carrying out the CoMP uplink in that a plurality of eNB are collaborative, Transmission Time Interval Bundling), the specific implementation process may further comprise the steps:
Step 401: service eNB sends to non-service eNB with uplink scheduling information by the X2 interface between eNB after being ready to uplink data scheduling, comprises information such as UE data upload time, uplink scheduling licensed content, TTI configuration in this uplink scheduling information.
After non-service eNB is received uplink scheduling information, determine that according to the UE data upload time that comprises in this uplink scheduling information the head of reception UE catches the time of line data, dispose the relevant information of obtaining TTI according to the TTI that comprises in this uplink scheduling information, and determine that according to uplink scheduling information UE head catches the employed frequency resource of line data.
Step 402: service eNB issues the TTI uplink scheduling permission (TTI UL Grant) that head catches line data to UE on PDCCH.
After step 403:UE detects the permission of TTI uplink scheduling, send head when the UE data upload time arrives and catch line data on UL-SCH, service eNB is caught line data with non-service eNB common head that receives UE on identical running time-frequency resource.
Step 404: non-service eNB is caught line data with the head of the UE that receives and is forwarded to service eNB by X2 interface, at the service eNB place head of UE is caught line data and carries out combined decoding.
Step 405: successfully receive if the head of UE catches line data, service eNB sends the uplink scheduling information relevant with re-transmission to non-service eNB, comprises 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 the TTI configuration, then with in retransmitting relevant uplink scheduling information also need comprise the TTI configuration.The TTI configuration is only just used when non-service eNB receives the wave point data.
Non-service eNB receive with retransmit relevant uplink scheduling information after, determine the time of the re-transmission upstream data of reception UE according to the UE data re-transmission time that comprises in this uplink scheduling information, determine that according to uplink scheduling information UE head catches the employed frequency resource of line data, determine to retransmit the MCS that upstream data adopted according to the MCS that comprises in this uplink scheduling information.
Step 406: service eNB issues the uplink scheduling permission on PDCCH, require UE to carry out uplink data retransmission.
After step 407:UE detects the uplink scheduling permission, the UE data re-transmission time is carried out uplink data retransmission when arriving, on UL-SCH, corresponding upstream data is carried out self adaptation and retransmit, service eNB and non-service eNB common re-transmission upstream data that receives UE on identical running time-frequency resource.
Step 408: non-service eNB is forwarded to service eNB with the re-transmission upstream data of the UE that receives by X2 interface, and the re-transmission upstream data at the service eNB place to UE carries out combined decoding.
For non-service eNB, identical to the processing of the upstream data received with the first processing of catching line data, receive in the UE data re-transmission time and to transmit from the upstream data of UE and to service eNB.
Still receive unsuccessfully if retransmit upstream data, repeating step 405～step 408 then successfully receives or reaches the number of retransmissions upper limit until corresponding upstream data.
Implementation three
When service eNB utilized NACK indication UE that upstream data is carried out the non-self-adapting re-transmission, non-service eNB did not participate in retransmitting the reception of upstream data; Service eNB utilizes uplink scheduling permission indication UE that upstream data is carried out self adaptation when retransmitting, and non-service eNB participates in retransmitting the reception of upstream data, and to catch line data identical with reception head fully for its processing mode.Service eNB need notify non-service eNB to carry out the time of uplink data retransmission, the information such as MCS that uplink data retransmission adopted.Service eNB utilizes NACK or uplink scheduling permission to determine that UE carries out the non-self-adapting re-transmission to upstream data or self adaptation retransmits in the implementation three.
Fig. 7 is implementation three specific embodiment schematic flow sheets among the present invention, and as shown in Figure 7, the specific implementation process may further comprise the steps:
Step 501: service eNB sends to non-service eNB with uplink scheduling information by the X2 interface between eNB after being ready to uplink data scheduling, comprises information such as UE data upload time, uplink scheduling licensed content in this uplink scheduling information.
After non-service eNB is received uplink scheduling information, determine that according to the UE data upload time that comprises in this uplink scheduling information the head of reception UE catches the time of line data, and determine that according to uplink scheduling information UE head catches the employed frequency resource of line data.
Step 502: service eNB issues the uplink scheduling permission that head catches line data to UE on PDCCH.
After step 503:UE detects the uplink scheduling permission, send head when the UE data upload time arrives and catch line data on UL-SCH, service eNB is caught line data with non-service eNB common head that receives UE on identical running time-frequency resource.
Step 504: non-service eNB is caught line data with the head of the UE that receives and is forwarded to service eNB by X2 interface, at the service eNB place head of UE is caught line data and carries out combined decoding.
Step 505: successfully do not receive if the head of UE catches line data, service eNB will send NACK to UE, require UE to carry out uplink data retransmission.Retransmit because service eNB requires UE that upstream data is carried out non-self-adapting, therefore, service eNB does not notify non-service eNB to have uplink data retransmission to be about to take place, and like this, non-service eNB will not participate in retransmitting the reception of upstream data.
After step 506:UE detects NACK, according to NACK upstream data is carried out non-self-adapting and retransmit, retransmit upstream data and receive separately and handle by service eNB.
Step 507: if the re-transmission upstream data of UE successfully receives yet, the service eNB decision carries out to upstream data that non-self-adapting retransmits or self adaptation retransmits, and below is example with the self adaptation re-transmission.Service eNB sends the uplink scheduling information relevant with re-transmission to non-service eNB, comprises information such as UE data re-transmission time, uplink scheduling licensed content, MCS in this uplink scheduling information.
Non-service eNB receive with retransmit relevant uplink scheduling information after, determine the time of the re-transmission upstream data of reception UE according to the UE data re-transmission time that comprises in this uplink scheduling information, determine that according to uplink scheduling information UE head catches the employed frequency resource of line data, determine to retransmit the MCS that upstream data adopted according to the MCS that comprises in this uplink scheduling information.
Step 508: service eNB issues the uplink scheduling permission on PDCCH, require UE to carry out uplink data retransmission.
After step 509:UE detects the uplink scheduling permission, the UE data re-transmission time is carried out uplink data retransmission when arriving, on UL-SCH, corresponding upstream data is carried out self adaptation and retransmit, service eNB and non-service eNB common re-transmission upstream data that receives UE on identical running time-frequency resource.
Step 510: non-service eNB is forwarded to service eNB with the re-transmission upstream data of the UE that receives by X2 interface, and the re-transmission upstream data at the service eNB place to UE carries out combined decoding.
It is that head catches line data or re-transmission upstream data that non-service eNB does not need to distinguish to the upstream data of receiving, receive upstream data from UE in the UE data re-transmission time, non-service eNB is identical with the first processing of catching data to the processing of the upstream data received.
Still receive unsuccessfully if retransmit upstream data, repeating step 507～step 510 then successfully receives or reaches the number of retransmissions upper limit until corresponding upstream data.
Implementation one and implementation three are equally applicable to upstream data transmission scenes such as SPS, TTI binding, and specific implementation is basic identical, does not repeat them here.
For the various embodiments described above, for simple description, so it all is expressed as a series of combination of actions, but those skilled in the art should know, the present invention is not subjected 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 the CoMP uplink of a plurality of eNB among the present invention, as shown in Figure 8, this system comprises UE, service eNB and at least one non-service eNB, and the collaborative associating multiple spot of service eNB and non-service eNB is handled the CoMP uplink
UE is used for according to the indication of service eNB upstream data being retransmitted; Service eNB is used to indicate UE to carry out uplink data retransmission or indication UE carries out uplink data retransmission and sends the uplink scheduling information relevant with re-transmission to non-service eNB; Non-service eNB be used to receive from service eNB with retransmit relevant uplink scheduling information after, reception is 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 is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.
Claims (10)
1. the processing method of a uplink data retransmission, the collaborative associating multiple spot of a plurality of base station eNB is handled the CoMP uplink, in the time of need carrying out uplink data retransmission, it is characterized in that this method comprises:
User terminal UE carries out uplink data retransmission according to the indication that service eNB sends;
Non-service eNB receive that service eNB sends when retransmitting relevant uplink scheduling information, the re-transmission upstream data of reception UE, and send to service eNB; Do not receive that service eNB sends when retransmitting relevant uplink scheduling information, do not carry out the operation relevant with uplink data retransmission.
2. method according to claim 1 is characterized in that,
The indication that described UE sends according to service eNB is carried out further comprising before the uplink data retransmission: service eNB sends NACK or uplink scheduling permission to UE, does not send the uplink scheduling information relevant with re-transmission to non-service eNB;
The indication that described UE sends according to service eNB is carried out further comprising after the uplink data retransmission: service eNB receives the re-transmission upstream data from UE.
3. method according to claim 1 is characterized in that,
The indication that described UE sends according to service eNB is carried out further comprising before the uplink data retransmission: service eNB sends and retransmits relevant uplink scheduling information to non-service eNB, sends uplink scheduling to UE and permits;
Described UE carries out uplink data retransmission according to the indication that service eNB sends, and is specially: the uplink scheduling permission that UE sends according to service eNB is carried out self adaptation to upstream data and is retransmitted;
The indication that described UE sends according to service eNB is carried out further comprising after the uplink data retransmission: service eNB receives the re-transmission upstream data from UE and non-service eNB.
4. method according to claim 3 is characterized in that,
The described uplink scheduling information relevant with re-transmission comprises at least: the UE data re-transmission time;
Described non-service eNB receives the re-transmission upstream data of UE, is specially: when non-service eNB arrived in the described UE data re-transmission time, receive the re-transmission upstream data of UE.
5. according to claim 3 or 4 described methods, it is characterized in that, described needs carry out further comprising before the uplink data retransmission: service eNB sends uplink scheduling information to non-service eNB, and this uplink scheduling information comprises semi-persistent scheduling SPS configuration or Transmission Time Interval TTI configuration.
6. method according to claim 5 is characterized in that,
When described uplink scheduling information comprises the SPS configuration, comprise SPS and the SPS cycle of whether starting in the described SPS configuration;
Described with retransmit relevant uplink scheduling information in UE data re-transmission time of comprising do not conflict with the UE data upload time of described each SPS on the cycle.
7. method according to claim 5 is characterized in that, when comprising the TTI configuration in the described uplink scheduling information, further comprises the TTI configuration in the described uplink scheduling information relevant with re-transmission.
8. method according to claim 1 is characterized in that,
The indication that described UE sends according to service eNB is carried out further comprising before the uplink data retransmission: when service eNB sends NACK to UE, do not send the uplink scheduling information relevant with re-transmission to non-service eNB; Described UE carries out uplink data retransmission according to the indication that service eNB sends, and is specially: the NACK that UE sends according to service eNB carries out non-self-adapting to upstream data and retransmits; The indication that described UE sends according to service eNB is carried out further comprising after the uplink data retransmission: service eNB receives the re-transmission upstream data from UE;
The indication that described UE sends according to service eNB is carried out further comprising before the uplink data retransmission: when service eNB sends the uplink scheduling information relevant with re-transmission to non-service eNB, send the uplink scheduling permission to UE; Described UE carries out uplink data retransmission according to the indication that service eNB sends, and is specially: the uplink scheduling permission that UE sends according to service eNB is carried out self adaptation to upstream data and is retransmitted; The indication that described UE sends according to service eNB is carried out further comprising after the uplink data retransmission: service eNB receives the re-transmission upstream data from UE and non-service eNB.
9. the treatment system of a uplink data retransmission, this system comprises: UE, service eNB and at least one non-service eNB, the collaborative associating multiple spot of service eNB and non-service eNB is handled the CoMP uplink, in the time of need carrying out uplink data retransmission, it is characterized in that,
Described UE is used for according to the indication of service eNB upstream data being retransmitted;
Described service eNB is used to indicate UE to carry out uplink data retransmission or indication UE carries out uplink data retransmission and sends the uplink scheduling information relevant with re-transmission to non-service eNB;
Described non-service eNB be used to receive from service eNB with retransmit relevant uplink scheduling information after, reception is from the re-transmission upstream data of UE and be sent to service eNB.
10. system according to claim 9 is characterized in that, described service eNB is further used for: receive the re-transmission upstream data from UE or UE and non-service eNB.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910083052.9A CN101873631B (en) | 2009-04-27 | 2009-04-27 | Processing method and system for uplink data retransmission |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910083052.9A CN101873631B (en) | 2009-04-27 | 2009-04-27 | Processing method and system for uplink data retransmission |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101873631A true CN101873631A (en) | 2010-10-27 |
| CN101873631B CN101873631B (en) | 2014-04-30 |
Family
ID=42998240
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910083052.9A Expired - Fee Related CN101873631B (en) | 2009-04-27 | 2009-04-27 | Processing method and system for uplink data retransmission |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101873631B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012094928A1 (en) * | 2011-01-10 | 2012-07-19 | 中兴通讯股份有限公司 | Method and device for transmitting uplink coordinated data |
| WO2014071581A1 (en) * | 2012-11-07 | 2014-05-15 | 华为技术有限公司 | Semi-persistent scheduling method and base station |
| CN103974338A (en) * | 2013-02-01 | 2014-08-06 | 华为技术有限公司 | Method for transmitting data, user equipment and base stations |
| CN104025694A (en) * | 2012-12-24 | 2014-09-03 | 华为技术有限公司 | Communication processing method, device and system for uplink and downlink separation |
| WO2015018009A1 (en) * | 2013-08-07 | 2015-02-12 | 华为技术有限公司 | Method for automatic retransmission, user equipment, and base station |
| WO2016062074A1 (en) * | 2014-10-24 | 2016-04-28 | 华为技术有限公司 | Method and base station for cell uplink coordination |
| WO2017070904A1 (en) * | 2015-10-29 | 2017-05-04 | 华为技术有限公司 | Multi-cell uplink cooperative communication method and base station |
| CN109905849A (en) * | 2014-08-19 | 2019-06-18 | 高通股份有限公司 | Multicast is carried out to business using multi-connection |
| WO2019114730A1 (en) * | 2017-12-13 | 2019-06-20 | 华为技术有限公司 | Data receiving and transmission method and device, and communication system |
| CN110198546A (en) * | 2018-02-27 | 2019-09-03 | 上海华为技术有限公司 | A kind of dispatching method and the network equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101132260A (en) * | 2006-08-22 | 2008-02-27 | 中兴通讯股份有限公司 | Retransmission control method for reinforcing uplink asynchronous mixed automatic retransmission request |
| WO2008041824A2 (en) * | 2006-10-02 | 2008-04-10 | Lg Electronics Inc. | Methods for retransmitting data in the multi-carrier system |
| CN101212285A (en) * | 2007-12-25 | 2008-07-02 | 中国人民解放军理工大学 | Opportunity synergy based automatic retransmission request method |
| CN101404566A (en) * | 2008-11-05 | 2009-04-08 | 中国科学院计算技术研究所 | Method and system for implementing mixed automatic retransmission request mechanism in LTE system |
-
2009
- 2009-04-27 CN CN200910083052.9A patent/CN101873631B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101132260A (en) * | 2006-08-22 | 2008-02-27 | 中兴通讯股份有限公司 | Retransmission control method for reinforcing uplink asynchronous mixed automatic retransmission request |
| WO2008041824A2 (en) * | 2006-10-02 | 2008-04-10 | Lg Electronics Inc. | Methods for retransmitting data in the multi-carrier system |
| CN101212285A (en) * | 2007-12-25 | 2008-07-02 | 中国人民解放军理工大学 | Opportunity synergy based automatic retransmission request method |
| CN101404566A (en) * | 2008-11-05 | 2009-04-08 | 中国科学院计算技术研究所 | Method and system for implementing mixed automatic retransmission request mechanism in LTE system |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012094928A1 (en) * | 2011-01-10 | 2012-07-19 | 中兴通讯股份有限公司 | Method and device for transmitting uplink coordinated data |
| CN104255075B (en) * | 2012-11-07 | 2018-10-30 | 华为技术有限公司 | The method of semi-persistent scheduling and base station |
| WO2014071581A1 (en) * | 2012-11-07 | 2014-05-15 | 华为技术有限公司 | Semi-persistent scheduling method and base station |
| CN104255075A (en) * | 2012-11-07 | 2014-12-31 | 华为技术有限公司 | Semi-persistent scheduling method and base station |
| CN104025694A (en) * | 2012-12-24 | 2014-09-03 | 华为技术有限公司 | Communication processing method, device and system for uplink and downlink separation |
| WO2014117751A1 (en) * | 2013-02-01 | 2014-08-07 | 华为技术有限公司 | Data transmission method, user equipment, and base station |
| CN103974338A (en) * | 2013-02-01 | 2014-08-06 | 华为技术有限公司 | Method for transmitting data, user equipment and base stations |
| WO2015018009A1 (en) * | 2013-08-07 | 2015-02-12 | 华为技术有限公司 | Method for automatic retransmission, user equipment, and base station |
| US11323851B2 (en) | 2014-08-19 | 2022-05-03 | Qualcomm Incorporated | Multicasting traffic using multi-connectivity |
| CN109905849A (en) * | 2014-08-19 | 2019-06-18 | 高通股份有限公司 | Multicast is carried out to business using multi-connection |
| CN109905849B (en) * | 2014-08-19 | 2021-10-29 | 高通股份有限公司 | Multicasting traffic using multiple connections |
| WO2016062074A1 (en) * | 2014-10-24 | 2016-04-28 | 华为技术有限公司 | Method and base station for cell uplink coordination |
| US10148323B2 (en) | 2014-10-24 | 2018-12-04 | Huawei Technologies Co., Ltd. | Uplink inter-cell coordination method and base station |
| WO2017070904A1 (en) * | 2015-10-29 | 2017-05-04 | 华为技术有限公司 | Multi-cell uplink cooperative communication method and base station |
| US10645717B2 (en) | 2015-10-29 | 2020-05-05 | Huawei Technologies Co., Ltd. | Multi-cell uplink coordinated communication method and base station |
| CN107926025A (en) * | 2015-10-29 | 2018-04-17 | 华为技术有限公司 | A kind of method of uplink coordinated communication of multiple cell and base station |
| WO2019114730A1 (en) * | 2017-12-13 | 2019-06-20 | 华为技术有限公司 | Data receiving and transmission method and device, and communication system |
| CN109921884A (en) * | 2017-12-13 | 2019-06-21 | 华为技术有限公司 | The method, apparatus and communication system of data transmit-receive |
| CN109921884B (en) * | 2017-12-13 | 2022-04-12 | 华为技术有限公司 | Data receiving and transmitting method, device and communication system |
| CN110198546A (en) * | 2018-02-27 | 2019-09-03 | 上海华为技术有限公司 | A kind of dispatching method and the network equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101873631B (en) | 2014-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101873631B (en) | Processing method and system for uplink data retransmission | |
| US10887874B2 (en) | HARQ protocol | |
| KR101343899B1 (en) | Method, system and equipment for processing information | |
| CN101488832B (en) | Channel detecting and processing method, terminal and base station | |
| CN101932027B (en) | Multiple carrier dispatching method and system | |
| CN108604946A (en) | efficient HARQ feedback | |
| CN110235398A (en) | Method for partial retransmission | |
| US20100118803A1 (en) | Base station apparatus, mobile station, radio communication system, and communication control method | |
| CN102281646B (en) | Method and apparatus for transmitting uplink data | |
| CN105634688B (en) | Method and device for realizing data transmission | |
| CN105356967A (en) | Data processing method, base station and terminal | |
| CN107113077B (en) | For the method for uplink transmission in unlicensed frequency band and use the equipment of this method | |
| KR101927017B1 (en) | RLC data packet offloading method and base station | |
| CN102783206A (en) | Mobile terminal device, wireless base station device, and wireless communication method | |
| CN102056228A (en) | Uplink hybrid automatic repeat request response information and indication bond transmission method and base station | |
| CN103248464A (en) | Uplink data transmission method and device | |
| CN109155704A (en) | The triggering of short delay Fast retransmission | |
| CN101932111B (en) | Method and system for resource scheduling between enhanced base stations | |
| JP2009232132A (en) | Mobile station and base station device | |
| CN101931960B (en) | Method for avoid uplink transmission conflict, system and device | |
| CN103583011A (en) | Method,apparatus and system for coordinated multiple point retransmission | |
| JP5061128B2 (en) | Base station apparatus, mobile station, radio communication system, and communication control method | |
| CN107409325A (en) | User terminal, wireless communication system and wireless communications method | |
| CN102118782A (en) | Uplink transmission method, system and equipment | |
| CN102035632B (en) | Data transmission method and system in wireless relay scene |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20101027 Assignee: SHENZHEN ZTE MICROELECTRONICS TECHNOLOGY CO., LTD. Assignor: ZTE Corporation Contract record no.: 2015440020319 Denomination of invention: Processing method and system for uplink data retransmission Granted publication date: 20140430 License type: Common License Record date: 20151123 |
|
| LICC | Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140430 Termination date: 20200427 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |