CN101064589A - State reporting method for automatic retransmission request - Google Patents
State reporting method for automatic retransmission request Download PDFInfo
- Publication number
- CN101064589A CN101064589A CN 200610011850 CN200610011850A CN101064589A CN 101064589 A CN101064589 A CN 101064589A CN 200610011850 CN200610011850 CN 200610011850 CN 200610011850 A CN200610011850 A CN 200610011850A CN 101064589 A CN101064589 A CN 101064589A
- Authority
- CN
- China
- Prior art keywords
- automatic repeat
- repeat requests
- entity
- nack message
- requests entity
- 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
- 238000000034 method Methods 0.000 title claims abstract description 70
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims abstract 40
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims abstract 40
- 230000008859 change Effects 0.000 claims description 105
- 238000012545 processing Methods 0.000 claims description 21
- 230000007246 mechanism Effects 0.000 claims description 16
- 230000008569 process Effects 0.000 abstract description 14
- 230000005540 biological transmission Effects 0.000 abstract description 7
- 238000001514 detection method Methods 0.000 description 7
- 230000008713 feedback mechanism Effects 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 3
- 238000003672 processing method Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- GOLXNESZZPUPJE-UHFFFAOYSA-N spiromesifen Chemical compound CC1=CC(C)=CC(C)=C1C(C(O1)=O)=C(OC(=O)CC(C)(C)C)C11CCCC1 GOLXNESZZPUPJE-UHFFFAOYSA-N 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Abstract
The invention discloses a state report method of retransmitting request automatically, the receiving end retransmits request automatically are following: for the protocol data unit which needs feedback ACK message received by the receiving end retransmitting request automatically entity, the hybrid retransmitting request automatically entity feedbacks the ACK message; for the protocol data unit which needs feedback NACK message not received by the receiving end retransmitting request automatically entity, if the hybrid retransmitting request automatically entity does not feedback the NACK message to the protocol data unit, then said receiving end retransmits request automatically entity feedbacks said NACK message to said protocol data unit. The invention solves problem that sending end retransmits request automatically entity may receive the repeated state report in two directions for the same protocol data unit and the same transmission, unnecessary command cost and process cost can be avoided, and the performance of system is increased.
Description
Technical field
The present invention relates to the digital mobile communication technical field, particularly the method for reporting status of automatic repeat requests in the wireless communication system.
Background technology
Automatic repeat requests (ARQ) entity of 3-G (Generation Three mobile communication system) is positioned at the wireless chain control layer of radio network controller, and its feedback mechanism is: receiving terminal has periodicity, protocol Data Unit (PDU) loss detection, detects three kinds of triggering modes in turn to transmitting terminal responsive state report.Acknowledge message in the status report (ACK) or non-acknowledge message (NACK) data packet format have bitmap (BITMAP), tabulation (LIST), tabulation (RLIST) three kinds, and the content of feedback is based on ARQ protocol Data Unit PDU.Have and forbid that detection, disable period detect two kinds of mechanism that reduce the status report frequencies in turn in turn.Mix automatic repeat requests (HARQ) entity and be positioned at the media access control layer and the physical layer of base station, its feedback mechanism is: receiving terminal is to transmitting terminal response confirmation message (ACK) or non-acknowledge message (NACK).Whether do not transmit successful feedback mechanism between the mixing of receiving terminal or transmitting terminal automatic repeat requests entity HARQ and the automatic repeat requests entity A RQ.
The automatic repeat requests entity A RQ of third generation Mobile Communication letter long evolving system is positioned at the wireless chain control layer of base station, mixes media access control layer and physical layer that automatic repeat requests entity HARQ is positioned at the base station, and they are positioned at same network node.For the feedback mechanism of ARQ entity, prior art is: the mechanism that combines based on the feedback of the feedback of transmitting terminal HARQ entity and/or receiving terminal ARQ entity.Transmitting terminal HARQ entity is received the NACK message of receiving terminal HARQ entity, at first carries out to mix automatically to retransmit, after the failure maximum retransmission, to transmitting terminal ARQ feedback NACK message.Transmitting terminal HARQ entity is received the ACK message of receiving terminal HARQ entity, before default timer expiry, if do not receive the NACK-＞ACK mistake Indication message of receiving terminal HARQ entity, then behind the timer expiry to transmitting terminal ARQ entity feeding back ACK message; If received NACK-＞ACK mistake Indication message before the timer expiry, then to transmitting terminal ARQ entity feedback NACK message.Respectively to transmitting terminal ARQ entity feeding back ACK or NACK message, the feedback of receiving terminal ARQ entity can be based on the error detection mechanism of ARQ entity and/or the feedback information of receiving terminal HARQ entity according to the situation that receives successfully or fail for the ARQ entity of receiving terminal.Concrete mechanism for receiving terminal ARQ entity feeding back ACK message or NACK message does not also have scheme now.The problem that needs of existing scheme solve is: because transmitting terminal ARQ entity is from transmitting terminal HARQ entity and receiving terminal ARQ entity both direction receiving feedback information, may receive for same ARQ PDU and once transmit the status report that repeats together, cause unnecessary signaling consumption and processing expenditure.
Summary of the invention
Technical problem to be solved by this invention provides a kind of method for reporting status of automatic repeat requests, solve since transmitting terminal ARQ entity from transmitting terminal HARQ entity and receiving terminal ARQ entity both direction receiving feedback information, repeat mode report be may receive, unnecessary signaling consumption and processing expenditure caused for the same once transmission of same ARQ PDU.
For achieving the above object, the invention provides a kind of method for reporting status of automatic repeat requests, its characteristics are, the automatic repeat requests entity of receiving terminal carries out following processing: for the correct need feeding back ACK protocol of messages data cell that receives of the automatic repeat requests entity of receiving terminal, only carried out the feedback of ACK message by the automatic repeat requests entity of mixing; The need of failing correctly to receive for the automatic repeat requests entity of receiving terminal feed back NACK protocol of messages data cell, the described feedback NACK protocol of messages data cell that needs is not fed back if mix automatic repeat requests entity, then carried out the feedback of the NACK message of described protocol Data Unit by the automatic repeat requests entity of described receiving terminal.
Above-mentioned method, its characteristics are, the automatic repeat requests entity of receiving terminal is judged in the following manner needs feedback NACK protocol of messages data cell whether fed back NACK message by the automatic repeat requests entity of described mixing: receiving terminal mixes automatic repeat requests entity and returns after NACK message reaches maximum times mixing automatic repeat requests entity to transmitting terminal, sends out notification message corresponding to the automatic repeat requests entity of receiving terminal; The automatic repeat requests entity of receiving terminal is judged the numbering whether the corresponding protocols data cell is provided in the described notification message, be the NACK message that the automatic repeat requests entity of then described receiving terminal refuses to feed back to the automatic repeat requests entity of transmitting terminal described protocol Data Unit, otherwise the automatic repeat requests entity of receiving terminal allow to feed back to the automatic repeat requests entity of transmitting terminal the NACK message of described protocol Data Unit.
Above-mentioned method, its characteristics are, the automatic repeat requests entity of receiving terminal feeds back the NACK message of described protocol Data Unit by allowing redundant mode, describedly allow redundant mode to comprise: the automatic repeat requests entity of receiving terminal at detected each lose or wrong protocol Data Unit immediately to the automatic repeat requests entity feedback of transmitting terminal NACK message, judge by corresponding mechanism and handle redundant NACK message by the automatic repeat requests entity of transmitting terminal.
Above-mentioned method, its characteristics are, the automatic repeat requests entity of receiving terminal feeds back the NACK message of described protocol Data Unit by the timer mode, described timer mode comprises: the automatic repeat requests entity of receiving terminal at detected each lose or wrong protocol Data Unit is provided with corresponding timer, if before timer expiry, received the corresponding protocol data cell, then do not feed back NACK message; If do not receive the corresponding protocol data cell before the timer expiry, then behind timer expiry, feed back NACK message.
Above-mentioned method, its characteristics are that the automatic repeat requests entity of receiving terminal feeds back the NACK message of described protocol Data Unit in the following manner: the automatic repeat requests entity of receiving terminal has the protocol Data Unit of described notification message all not feed back NACK message for correspondence.
Above-mentioned method, its characteristics are, also comprise: if the automatic repeat requests entity of receiving terminal is not received described notification message, and when detecting the protocol Data Unit of losing, then think the situation that automatic repeat requests omission has taken place to mix, the automatic repeat requests entity of receiving terminal is immediately to the automatic repeat requests entity feedback of transmitting terminal NACK message;
Above-mentioned method, its characteristics are, also comprise: the automatic repeat requests entity of receiving terminal is abandoned for the protocol Data Unit of received repetition.
Above-mentioned method, its characteristics are, the automatic repeat requests entity of transmitting terminal carries out following processing: the automatic repeat requests entity of transmitting terminal receives transmitting terminal when mixing the NACK message of the NACK message of automatic repeat requests entity feedback or the automatic repeat requests entity feedback of receiving terminal, retransmits relevant protocol Data Unit.
Above-mentioned method, its characteristics are, the automatic repeat requests entity of transmitting terminal carries out following processing: the automatic repeat requests entity of transmitting terminal receives transmitting terminal when mixing the NACK message of automatic repeat requests entity, each protocol Data Unit related at this NACK message is provided with timer respectively, and retransmits described protocol Data Unit; If before timer expiry, receive the NACK message of the automatic repeat requests entity of receiving terminal, think that then redundant NACK message is abandoned at described protocol Data Unit; If behind timer expiry, receive described NACK message, then think not to be redundant NACK message, and retransmit described protocol Data Unit.
Above-mentioned method, its characteristics are, the automatic repeat requests entity of transmitting terminal carries out following processing: the automatic repeat requests entity of transmitting terminal mixes automatic repeat requests entity feedback direction and the automatic repeat requests entity feedback of receiving terminal direction is provided with a counter respectively at each protocol Data Unit at transmitting terminal, the initial value of counter all is made as 0, the automatic repeat requests entity of transmitting terminal is whenever received NACK message one time, and the Counter Value of correspondence is added 1; After the automatic repeat requests entity of transmitting terminal receives that transmitting terminal mixes the NACK message of automatic repeat requests entity, retransmit each related protocol Data Unit of this NACK message; If then receive the NACK message of the automatic repeat requests entity of receiving terminal at described protocol Data Unit, the automatic repeat requests entity of transmitting terminal compares the Counter Value of this direction and the Counter Value of other direction, if equate then abandon the NACK message of the automatic repeat requests entity of receiving terminal direction, otherwise retransmit described protocol Data Unit.
Above-mentioned method, its characteristics are that the processing that the automatic repeat requests entity of transmitting terminal carries out further comprises the steps:
Step 410: the automatic repeat requests entity of transmitting terminal sends protocol Data Unit in the sliding window mode;
Step 420: the automatic repeat requests entity of transmitting terminal judges whether to receive the NACK message that transmitting terminal mixes automatic repeat requests entity, changes step 430 if receive; Otherwise change step 440;
Step 430: relevant described protocol Data Unit is provided with timer respectively; The Counter Value of this direction correspondence adds 1 respectively, and retransmits described protocol Data Unit, changes step 480;
Step 440: judge whether to receive the NACK message of the automatic repeat requests entity of receiving terminal,, otherwise change step 460 if receive commentaries on classics step 450;
Step 450: the Counter Value of this directional correlation protocol Data Unit correspondence adds 1 respectively, and retransmits described protocol Data Unit; Change step 410;
Step 460: judge whether to receive the ACK message that transmitting terminal mixes automatic repeat requests entity,, otherwise change step 410 if receive commentaries on classics step 470;
Step 470: the related protocol data cell is established timer respectively, keep described protocol Data Unit before the timer expiry; Behind timer expiry, determine whether to abandon described data cell again, change step 410;
Step 480: judge whether to receive the NACK message of the automatic repeat requests entity of receiving terminal,, otherwise change step 460 if receive commentaries on classics step 490 to the same protocol data cell;
Step 490: the Counter Value of this directional correlation protocol Data Unit correspondence adds 1 respectively, and the Counter Value corresponding with other direction relatively, changes step 500;
Step 500: whether the timer of judging correspondence when receiving NACK message is overtime, if overtime commentaries on classics step 520, otherwise would change step 510;
Step 510: judge that whether Counter Value equates,, change step 520, if equate then change step 530 if unequal;
Step 520: retransmit the related protocol data cell; Change step 410;
Step 530: think redundant NACK message, abandon described NACK message, change step 410.
Above-mentioned method, its characteristics are that the automatic repeat requests entity of transmitting terminal also carries out following processing: the automatic repeat requests entity of transmitting terminal receives after transmitting terminal mixes the ACK message of automatic repeat requests entity, continues to send new data cell to slide the window mode; And timer is set at each related data cell of this ACK message; Before timer expiry, keep described data cell; Behind timer expiry, judge whether to abandon described data cell in conjunction with actual conditions; If then receive the NACK message of the automatic repeat requests entity of receiving terminal, then retransmit described data cell at same data cell.
Above-mentioned method, its characteristics are that described actual conditions is: whether all data cells of forming service data unit have received all that transmitting terminal mixes the ACK message of automatic repeat requests entity.
Technique effect of the present invention is:
The invention solves transmitting terminal ARQ entity may feed back the same once status report problem of the repetition of transmission that receive on the directions for same ARQ PDU at two, has avoided unnecessary signaling consumption and processing expenditure, has improved the performance of system.
Description of drawings
Fig. 1 is the message flow chart of a kind of embodiment of the present invention;
Fig. 2 to Fig. 5 is the flow chart of 4 kinds of embodiment of transmitting terminal ARQ entity handles flow process of the present invention;
Fig. 6 to Fig. 8 is the flow chart of 3 kinds of embodiment of receiving terminal ARQ entity handles flow process of the present invention;
Embodiment
The invention discloses a kind of ARQ entity state method for reporting based on NACK, main contents are: receiving terminal ARQ entity is for the ARQ PDU of correct reception feeding back ACK message not, because transmitting terminal ARQ entity has received ACK message based on the feedback of transmitting terminal HARQ entity, solved transmitting terminal ARQ entity and may receive that same ARQ PDU is with the repeat ACK message problem of once transmitting.For NACK message,, need to rely in addition the error detection and the treatment mechanism of receiving terminal ARQ entity because the limitation of the treatment mechanism of HARQ entity own can not detect and/or handle all error situations.Receiving terminal ARQ entity only feeds back the NACK message that the HARQ entity does not have those ARQ PDU of feedback, do not need all are lost or receive wrong ARQ PDU to transmitting terminal ARQ entity feedback NACK message, because the HARQ entity has fed back the NACK message of some of them ARQ PDU, solved transmitting terminal ARQ entity and may receive that same ARQ PDU is with the repetition NACK message problem of once transmitting.
Receiving terminal ARQ entity judges that ARQ PDU that the HARQ entity fed back NACK message is based on following scheme: receiving terminal HARQ entity is after returning the NACK maximum times to transmitting terminal HARQ entity, send out notification message corresponding to receiving terminal ARQ entity, the content of notification message is divided into two kinds of situations: a kind of situation can provide the ARQ PDU that is comprised numbering for the HARQ entity; Another kind of situation can't provide the ARQ PDU that is comprised numbering for the HARQ entity.For the former, receiving terminal ARQ entity does not feed back the NACK message of described ARQ PDU to transmitting terminal ARQ entity; For the latter, receiving terminal ARQ entity has three kinds of processing methods:
Receiving terminal ARQ entity handles method one allows redundant NACK message.Receiving terminal ARQ entity at detected each lose or wrong ARQ PDU immediately to transmitting terminal ARQ entity feedback NACK message, judge by corresponding mechanism and handle redundant NACK message by transmitting terminal ARQ entity.
Receiving terminal ARQ entity handles method two, the timer mode.Receiving terminal ARQ entity at detected each lose or wrong ARQ PDU does not feed back NACK message immediately, but corresponding timer is set, if before timer expiry, received corresponding ARQ PDU, then do not feed back NACK message; If do not receive corresponding ARQ PDU before the timer expiry, then feed back NACK message behind the timer expiry.This scheme can be avoided most of redundant NACK message problem, but because a spot of redundant NACK message may appear in the error that timer is provided with, transmitting terminal ARQ entity can select relative measures further to protect; Perhaps do not take relevant safeguard measure, allow a spot of redundant NACK message and redundant ARQPDU to retransmit phenomenon.
Receiving terminal ARQ entity handles method three, not feedback system.Receiving terminal ARQ entity is lost or wrong ARQ PDU does not feed back NACK message for detected.
When the selected safeguard measure of transmitting terminal ARQ entity lost efficacy or do not take under the situation of safeguard measure, receiving terminal ARQ entity is abandoned for the ARQ PDU of received repetition.
If receiving terminal ARQ entity is not received the corresponding notification message of receiving terminal HARQ entity, and when detecting the ARQ PDU that loses, be illustrated as the situation of HARQ omission, immediately to transmitting terminal ARQ entity feedback NACK message.
Transmitting terminal HARQ entity and receiving terminal ARQ entity have three kinds of situations at same ARQ PDU with once transmitting to transmitting terminal ARQ entity feedback: after transmitting terminal ARQ entity is received the NACK message of transmitting terminal HARQ entity, then received the NACK message of receiving terminal ARQ entity, the latter shows as once redundant NACK message; After transmitting terminal ARQ entity is received the ACK message of transmitting terminal HARQ entity, then received the NACK message of receiving terminal ARQ entity, should be as the criterion with the latter; Transmitting terminal ARQ entity is not received the NACK message or the ACK message of transmitting terminal HARQ entity, has received the NACK message of receiving terminal ARQ entity.Produce the former of above-mentioned phenomenon because the limitation of the delay of receiving terminal ARQ entity timer step-up error, wireless transmission process or mistake, HARQ entity error detection mechanism etc.Transmitting terminal ARQ entity has four kinds of processing methods:
Transmitting terminal ARQ entity handles method one allows small amount of redundancy NACK message and redundant ARQ PDU to retransmit.When transmitting terminal ARQ entity receives the NACK message of the NACK message of transmitting terminal HARQ entity feedback or receiving terminal ARQ entity feedback, retransmit relevant ARQ PDU.
Transmitting terminal ARQ entity handles method two, the timer mode.When transmitting terminal ARQ entity received transmitting terminal HARQ entity NACK message, each ARQ PDU related at this NACK message was provided with timer respectively, and retransmitted described ARQ PDU.If before timer expiry, receive the NACK message of receiving terminal ARQ entity, think that redundant NACK message is abandoned at described ARQ PDU; If behind timer expiry, receive above-mentioned message, think not to be redundant NACK message, retransmit described ARQPDU.
Transmitting terminal ARQ entity handles method three, the counter mode.Transmitting terminal ARQ entity is provided with a counter at each ARQ PDU respectively in transmitting terminal HARQ entity feedback direction and receiving terminal ARQ entity feedback direction, the initial value of counter all is made as 0, transmitting terminal ARQ entity is whenever received NACK message one time, and the Counter Value of correspondence is added 1.After transmitting terminal ARQ entity is received the NACK message of transmitting terminal HARQ entity, retransmit each related ARQ PDU of this NACK message.If then receive the NACK message of receiving terminal ARQ entity, with the Counter Value of the Counter Value of this direction and other direction relatively,, otherwise retransmit described ARQ PDU if equate then abandon the NACK message of receiving terminal ARQ entity direction at described ARQ PDU.
Transmitting terminal ARQ entity handles method four, the timer mode that combines with counter.The same method two of the setting principle of timer, the setting of counter and calculating principle are with method three.When transmitting terminal ARQ entity is received the NACK message of transmitting terminal HARQ entity, retransmit each related ARQ PDU of this NACK message.If before timer expiry, received the NACK message of receiving terminal ARQ entity, then press the processing scheme of method three for same ARQ PDU; If behind timer expiry, receive above-mentioned message, then retransmit described ARQ PDU.
In four kinds of schemes of above-mentioned transmitting terminal, after transmitting terminal ARQ entity receives the ACK message of transmitting terminal HARQ entity, continue to send new ARQ PDU to slide the window mode; And timer is set at each related ARQ PDU of this ACK message; Before timer expiry, can not abandon described ARQ PDU; Whether can abandon described ARQ PDU in conjunction with other condition judgment behind timer expiry, all ARQ PDU that for example form certain ARQ SDU (service data unit) have all received the ACK message of transmitting terminal HARQ entity.If then receive the NACK message of receiving terminal ARQ entity, then retransmit described ARQ PDU at same ARQ PDU.
Receiving terminal method one can make up respectively with transmitting terminal method two, three, four; The receiving terminal method two can make up respectively with transmitting terminal method one, two, three, four; Receiving terminal method three can make up with transmitting terminal method one.Combinations thereof can form 8 kinds of solutions, although these schemes still may exist redundant feedback and the redundant phenomenon of retransmitting, but unnecessary feedback of receiving terminal ARQ Rx and/or the unnecessary repeating transmission of transmitting terminal ARQ Tx have been avoided to a great extent, reduce the probability of redundant phenomenon, improved the efficient and the reliability of ARQ entity.Receiving terminal ARQ entity also has the corresponding protection measure for the ARQ PDU of received redundancy.Transmitting terminal ARQ entity also can be according to mechanism such as timer or sliding windows initiatively to receiving terminal ARQ entity requests status report, and this situation also can adopt similar mechanism to avoid redundant feedback information and redundant retransmission of information.
Fig. 1 has illustrated a kind of message flow of embodiment, and wherein ARQ Tx represents transmitting terminal ARQ entity, and HARQ Tx represents transmitting terminal HARQ entity; ARQ Rx represents receiving terminal ARQ entity, and HARQ Rx represents receiving terminal HARQ entity.Implementation step is as follows:
NACK scene 1:HARQ Rx sends NACK Notify notification message to ARQRx after HARQ Tx transmission NACK message reaches maximum times; HARQ Tx sends NACK message to ARQ Tx after receiving the NACK message of HARQ Rx and retransmitting the failure maximum times.ARQ Rx may take place to ARQ Tx feedback NACK message, ARQ Tx and ARQ Rx adopt corresponding mechanism processing redundant information in the summary of the invention respectively.
NACK scene 2:HARQ Rx detects NACK-＞ACK error message, sends the NACKNotify notification message to ARQ Rx, sends NACK-＞ACK mistake Indication message to HARQ Tx; HARQ Tx sends NACK message to ARQ Tx after receiving this message.ARQ Rx may take place to ARQ Tx feedback NACK message, ARQ Tx and ARQ Rx adopt corresponding mechanism processing redundant information in the summary of the invention respectively.
NACK scene 3: for the situation of nd mistake of HARQ Rx or information drop-out, ARQ Rx sends NACK message according to ARQ error detection mechanism detected error situation or ARQ PDU loss situation to ARQ Tx.Abnormal conditions may appear in this scene: ARQ Tx receives the ACK message of HARQ Tx for certain ARQ PDU earlier, has then received the NACK message that ARQ Rx once transmits together for same ARQ PDU.ARQ Tx and ARQ Rx adopt corresponding mechanism processing redundant information in the summary of the invention respectively.
The ACK scene: HARQ Tx receives the ACK message of HARQ Rx, does not receive NACK-＞ACK mistake Indication message of HARQ Rx before NACK-＞ACK error detection timer expiry, sends ACK message to ARQ Tx behind timer expiry.
Fig. 2 to Fig. 5 is the flow chart of 4 kinds of embodiment of transmitting terminal ARQ entity handles flow process of the present invention.Alignment processing flow process when receiving related news is the Event triggered mode, because the actual triggering difference on opportunity of receiving related news, each embodiment is the corresponding a lot of different flow processs of possibility all, provide a kind of situation at each embodiment herein.
Be the embodiment 1 of transmitting terminal ARQ entity handles flow process of the present invention with reference to figure 2, embodiment 1 is corresponding to above-mentioned transmitting terminal ARQ entity handles method one, and step is as follows:
Step 110: send ARQ PDU in the sliding window mode; Change step 120;
Step 120: receive the NACK message of HARQ Tx or the NACK message of ARQ Rx? change step 130 if receive; Otherwise change step 140;
Step 130: retransmit relevant ARQ PDU, change step 110;
Step 140: the ACK message that receives HARQ Tx? change step 150 if receive; Otherwise change step 110;
Step 150: the ARQ PDU that receives ACK message is provided with the protection timer, can not abandons described ARQ PDU before the timer expiry; Whether can abandon described ARQ PDU in conjunction with other condition judgment behind timer expiry, all ARQ PDU that for example form certain ARQ SDU have all received the ACK message of transmitting terminal HARQ entity; Change step 110;
With reference to figure 3, be the embodiment 2 of transmitting terminal ARQ entity handles flow process of the present invention.
Embodiment 2 is corresponding to above-mentioned transmitting terminal ARQ entity handles method two, and step is as follows:
Step 210: send ARQ PDU in the sliding window mode; Change step 220;
Step 220: the NACK message that receives HARQ Tx? change step 230 if receive; Otherwise change step 240;
Step 230: relevant ARQ PDU is established timer respectively, and retransmit; Change step 280;
Step 240: the NACK message that receives ARQ Rx? change step 250 if receive; Otherwise change step 260;
Step 250: retransmit relevant ARQ PDU; Change step 210;
Step 260: the ACK message that receives HARQ Tx? change step 270 if receive; Otherwise change step 210;
Step 270: relevant ARQ PDU is established timer respectively, can not abandon described ARQ PDU before the timer expiry; Whether can abandon described ARQ PDU in conjunction with other condition judgment behind timer expiry, all ARQ PDU that for example form certain ARQ SDU have all received the ACK message of transmitting terminal HARQ entity; Change step 210;
Step 280: receive the NACK message of ARQ Rx to identical ARQ PDU? change step 290 if receive; Otherwise change step 260;
Step 290: when receiving ARQ Rx, if corresponding timer expiry changes step 295 to the NACK message of identical ARQ PDU; Otherwise change step 300;
Step 295: retransmit relevant ARQ PDU; Change step 210;
Step 300: think redundant NACK message, abandon it; Change step 210;
With reference to figure 4, be the embodiment 3 of transmitting terminal ARQ entity handles flow process of the present invention.
Step 310: send ARQ PDU in the sliding window mode; Change step 320;
Step 320: the NACK message that receives HARQ Tx? change step 330 if receive; Otherwise change step 340;
Step 330: the Counter Value of this directional correlation ARQ PDU correspondence adds 1 respectively, and retransmits; Change step 380;
Step 340: the NACK message that receives ARQ Rx? change step 350 if receive; Otherwise change step 360;
Step 350: the Counter Value of this directional correlation ARQ PDU correspondence adds 1 respectively, and retransmits; Change step 310;
Step 360: the ACK message that receives HARQ Tx; Change step 370 if receive; Otherwise change step 310;
Step 370: relevant ARQ PDU is established timer respectively, can not abandon described ARQ PDU before the timer expiry; Whether can abandon described ARQ PDU in conjunction with other condition judgment behind timer expiry, all ARQ PDU that for example form certain ARQ SDU have all received the ACK message of transmitting terminal HARQ entity; Change step 310;
Step 380: receive the NACK message of ARQ Rx to identical ARQ PDU? change step 385 if receive; Otherwise change step 360;
Step 385: the Counter Value of this directional correlation ARQ PDU correspondence adds 1 respectively, and the Counter Value corresponding with other direction relatively, changes step 390;
Does step 390: Counter Value equate? if unequal, change step 395; Otherwise change step 400;
Step 395: retransmit relevant ARQ PDU; Change step 310;
Step 400: think redundant NACK message, abandon it; Change step 310;
With reference to figure 5, be the embodiment 4 of transmitting terminal ARQ entity handles flow process of the present invention.
Embodiment 4 is corresponding to above-mentioned transmitting terminal ARQ entity handles method four, and step is as follows:
Step 410: send ARQ PDU in the sliding window mode; Change step 420;
Step 420: the NACK message that receives HARQ Tx? change step 430 if receive; Otherwise change step 440;
Step 430: relevant ARQ PDU is provided with timer respectively; The Counter Value of this direction correspondence adds 1 respectively; And retransmit; Change step 480;
Step 440: the NACK message that receives ARQ Rx? change step 450 if receive; Otherwise change step 460;
Step 450: the Counter Value of this directional correlation ARQ PDU correspondence adds 1 respectively, and retransmits; Change step 410;
Step 460: the ACK message that receives HARQ Tx? change step 470 if receive; Otherwise change step 410;
Step 470: relevant ARQ PDU is established timer respectively, can not abandon described ARQ PDU before the timer expiry; Whether can abandon described ARQ PDU in conjunction with other condition judgment behind timer expiry, all ARQ PDU that for example form certain ARQ SDU have all received the ACK message of transmitting terminal HARQ entity; Change step 410;
Step 480: receive the NACK message of ARQ Rx to identical ARQ PDU? change step 490 if receive; Otherwise change step 460;
Step 490: the Counter Value of this directional correlation ARQ PDU correspondence adds 1 respectively, and the Counter Value corresponding with other direction relatively, changes step 500;
Step 500: the timer expiry of correspondence when receiving NACK message? if overtime commentaries on classics step 520; Otherwise change step 510;
Does step 510: Counter Value equate? if unequal, change step 520; Otherwise change step 530;
Step 520: retransmit relevant ARQ PDU; Change step 410;
Step 530: think redundant NACK message, abandon it; Change step 410;
Fig. 6 to Fig. 8 is the flow chart of 3 kinds of embodiment of receiving terminal ARQ entity handles flow process of the present invention.
With reference to figure 6, the flow process of a kind of embodiment 1 of receiving terminal ARQ entity embodiment has been described.
Receiving terminal embodiment 1 is corresponding to receiving terminal ARQ entity handles method one, and step is as follows:
Step 610: receiving terminal ARQ entity receives ARQ PDU; Change step 620;
Step 620: the NACK Notify message that receives HARQ Rx? if receive, change step 630; Otherwise change step 650;
Does step 630:NACK Notify message comprise ARQ PDU numbering? if comprise, change step 640; Otherwise change step 660;
Step 640: do not feed back NACK message to ARQ Tx for described ARQ PDU; Change step 610;
Step 650: detect ARQ PDU and lose or mistake? if detect, change step 660; Otherwise change step 610;
Step 660: feed back NACK message to ARQ Tx for detected described ARQ PDU; Change step 610;
With reference to figure 7, the flow process of a kind of embodiment 2 of receiving terminal ARQ entity embodiment has been described.
Receiving terminal embodiment 2 is corresponding to receiving terminal ARQ entity handles method two, and step is as follows:
Step 710: receiving terminal ARQ entity receives ARQ PDU; Change step 720;
Step 720: the NACK Notify message that receives HARQ Rx? if receive, change step 730; Otherwise change step 770;
Does step 730:NACK Notify message comprise ARQ PDU numbering? if comprise, change step 740; Otherwise change step 750;
Step 740: do not feed back NACK message to ARQ Tx for described ARQ PDU; Change step 710;
Step 750: lose or wrong ARQ PDU is provided with timer respectively for detected; Change step 760;
Step 760: receive described ARQ PDU before the timer expiry? if receive, change step 740; Otherwise change step 780;
Step 770: detect ARQ PDU and lose or mistake? if detect, change step 780; Otherwise change step 710;
Step 780: feed back NACK message to ARQ Tx for described ARQ PDU; Change step 710;
With reference to figure 8, the flow process of a kind of embodiment 3 of receiving terminal ARQ entity embodiment has been described.
Receiving terminal embodiment 3 is corresponding to receiving terminal ARQ entity handles method three, and step is as follows:
Step 810: receiving terminal ARQ entity receives ARQ PDU; Change step 820;
Step 820: the NACK Notify message that receives HARQ Rx? if receive, change step 830; Otherwise change step 840;
Step 830: do not feed back NACK message to ARQ Tx for described ARQ PDU; Change step 810;
Step 840: detect ARQ PDU and lose or mistake? if detect, change step 850; Otherwise change step 810;
Step 850: feed back NACK message to ARQ Tx for detected described ARQ PDU; Change step 810;
The invention solves transmitting terminal ARQ entity may feed back the same once status report problem of the repetition of transmission that receive on the directions for same ARQ PDU at two, has avoided unnecessary signaling consumption and processing expenditure, has improved the performance of system.
The above is preferred embodiment of the present invention only, is not to be used for limiting practical range of the present invention; Every according to equivalence variation and modification that the present invention did, all contained by claim of the present invention.
Claims (13)
1, a kind of method for reporting status of automatic repeat requests, it is characterized in that, the automatic repeat requests entity of receiving terminal carries out following processing: for the correct need feeding back ACK protocol of messages data cell that receives of the automatic repeat requests entity of receiving terminal, only carried out the feedback of ACK message by the automatic repeat requests entity of mixing; The need of failing correctly to receive for the automatic repeat requests entity of receiving terminal feed back NACK protocol of messages data cell, the described feedback NACK protocol of messages data cell that needs is not fed back if mix automatic repeat requests entity, then carried out the feedback of the NACK message of described protocol Data Unit by the automatic repeat requests entity of described receiving terminal.
2, method according to claim 1 is characterized in that, the automatic repeat requests entity of receiving terminal is judged in the following manner needs feedback NACK protocol of messages data cell whether to be fed back NACK message by the automatic repeat requests entity of described mixing:
Receiving terminal mixes automatic repeat requests entity and returns after NACK message reaches maximum times mixing automatic repeat requests entity to transmitting terminal, sends out notification message corresponding to the automatic repeat requests entity of receiving terminal; The automatic repeat requests entity of receiving terminal is judged the numbering whether the corresponding protocols data cell is provided in the described notification message, be the NACK message that the automatic repeat requests entity of then described receiving terminal refuses to feed back to the automatic repeat requests entity of transmitting terminal described protocol Data Unit, otherwise the automatic repeat requests entity of receiving terminal allow to feed back to the automatic repeat requests entity of transmitting terminal the NACK message of described protocol Data Unit.
3, method according to claim 2 is characterized in that, the automatic repeat requests entity of receiving terminal feeds back the NACK message of described protocol Data Unit by allowing redundant mode, and the mode of described permission redundancy comprises:
The automatic repeat requests entity of receiving terminal at detected each lose or wrong protocol Data Unit immediately to the automatic repeat requests entity feedback of transmitting terminal NACK message, judge by corresponding mechanism and handle redundant NACK message by the automatic repeat requests entity of transmitting terminal.
4, method according to claim 2 is characterized in that, the automatic repeat requests entity of receiving terminal feeds back the NACK message of described protocol Data Unit by the timer mode, and described timer mode comprises:
The automatic repeat requests entity of receiving terminal at detected each lose or wrong protocol Data Unit is provided with corresponding timer, if before timer expiry, received the corresponding protocol data cell, then do not feed back NACK message; If do not receive the corresponding protocol data cell before the timer expiry, then behind timer expiry, feed back NACK message.
5, method according to claim 2, it is characterized in that the automatic repeat requests entity of receiving terminal feeds back the NACK message of described protocol Data Unit in the following manner: the automatic repeat requests entity of receiving terminal has the protocol Data Unit of described notification message all not feed back NACK message for correspondence.
6, according to claim 3,4 or 5 described methods, it is characterized in that, also comprise:
If the automatic repeat requests entity of receiving terminal is not received described notification message, and when detecting the protocol Data Unit of losing, then think the situation that automatic repeat requests omission has taken place to mix, the automatic repeat requests entity of receiving terminal is immediately to the automatic repeat requests entity feedback of transmitting terminal NACK message;
7, method according to claim 6 is characterized in that, also comprises: the automatic repeat requests entity of receiving terminal is abandoned for the protocol Data Unit of received repetition.
8, according to claim 4 or 5 described methods, it is characterized in that, the automatic repeat requests entity of transmitting terminal carries out following processing: the automatic repeat requests entity of transmitting terminal receives transmitting terminal when mixing the NACK message of the NACK message of automatic repeat requests entity feedback or the automatic repeat requests entity feedback of receiving terminal, retransmits relevant protocol Data Unit.
9, according to claim 3 or 4 described methods, it is characterized in that, the automatic repeat requests entity of transmitting terminal carries out following processing: the automatic repeat requests entity of transmitting terminal receives transmitting terminal when mixing the NACK message of automatic repeat requests entity, each protocol Data Unit related at this NACK message is provided with timer respectively, and retransmits described protocol Data Unit; If before timer expiry, receive the NACK message of the automatic repeat requests entity of receiving terminal, think that then redundant NACK message is abandoned at described protocol Data Unit; If behind timer expiry, receive described NACK message, then think not to be redundant NACK message, and retransmit described protocol Data Unit.
10, according to claim 3 or 4 described methods, it is characterized in that, the automatic repeat requests entity of transmitting terminal carries out following processing: the automatic repeat requests entity of transmitting terminal mixes automatic repeat requests entity feedback direction and the automatic repeat requests entity feedback of receiving terminal direction is provided with a counter respectively at each protocol Data Unit at transmitting terminal, the initial value of counter all is made as 0, the automatic repeat requests entity of transmitting terminal is whenever received NACK message one time, and the Counter Value of correspondence is added 1; After the automatic repeat requests entity of transmitting terminal receives that transmitting terminal mixes the NACK message of automatic repeat requests entity, retransmit each related protocol Data Unit of this NACK message; If then receive the NACK message of the automatic repeat requests entity of receiving terminal at described protocol Data Unit, the automatic repeat requests entity of transmitting terminal compares the Counter Value of this direction and the Counter Value of other direction, if equate then abandon the NACK message of the automatic repeat requests entity of receiving terminal direction, otherwise retransmit described protocol Data Unit.
According to claim 3 or 4 described methods, it is characterized in that 11, the processing that the automatic repeat requests entity of transmitting terminal carries out further comprises the steps:
Step 410: the automatic repeat requests entity of transmitting terminal sends protocol Data Unit in the sliding window mode;
Step 420: the automatic repeat requests entity of transmitting terminal judges whether to receive the NACK message that transmitting terminal mixes automatic repeat requests entity, changes step 430 if receive; Otherwise change step 440;
Step 430: relevant described protocol Data Unit is provided with timer respectively; The Counter Value of this direction correspondence adds 1 respectively, and retransmits described protocol Data Unit, changes step 480;
Step 440: judge whether to receive the NACK message of the automatic repeat requests entity of receiving terminal,, otherwise change step 460 if receive commentaries on classics step 450;
Step 450: the Counter Value of this directional correlation protocol Data Unit correspondence adds 1 respectively, and retransmits described protocol Data Unit; Change step 410;
Step 460: judge whether to receive the ACK message that transmitting terminal mixes automatic repeat requests entity,, otherwise change step 410 if receive commentaries on classics step 470;
Step 470: the related protocol data cell is established timer respectively, keep described protocol Data Unit before the timer expiry; Behind timer expiry, determine whether to abandon described data cell again, change step 410;
Step 480: judge whether to receive the NACK message of the automatic repeat requests entity of receiving terminal,, otherwise change step 460 if receive commentaries on classics step 490 to the same protocol data cell;
Step 490: the Counter Value of this directional correlation protocol Data Unit correspondence adds 1 respectively, and the Counter Value corresponding with other direction relatively, changes step 500;
Step 500: whether the timer of judging correspondence when receiving NACK message is overtime, if overtime commentaries on classics step 520, otherwise would change step 510;
Step 510: judge that whether Counter Value equates,, change step 520, if equate then change step 530 if unequal;
Step 520: retransmit the related protocol data cell; Change step 410;
Step 530: think redundant NACK message, abandon described NACK message, change step 410.
12, method according to claim 9, it is characterized in that, the automatic repeat requests entity of transmitting terminal also carries out following processing: the automatic repeat requests entity of transmitting terminal receives after transmitting terminal mixes the ACK message of automatic repeat requests entity, continues to send new data cell to slide the window mode; And timer is set at each related data cell of this ACK message; Before timer expiry, keep described data cell; Behind timer expiry, judge whether to abandon described data cell in conjunction with actual conditions; If then receive the NACK message of the automatic repeat requests entity of receiving terminal, then retransmit described data cell at same data cell.
13, method according to claim 12 is characterized in that, described actual conditions is: whether all data cells of forming service data unit have received all that transmitting terminal mixes the ACK message of automatic repeat requests entity.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100118507A CN101064589B (en) | 2006-04-30 | 2006-04-30 | State reporting method for automatic retransmission request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100118507A CN101064589B (en) | 2006-04-30 | 2006-04-30 | State reporting method for automatic retransmission request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101064589A true CN101064589A (en) | 2007-10-31 |
| CN101064589B CN101064589B (en) | 2011-11-30 |
Family
ID=38965345
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2006100118507A Expired - Fee Related CN101064589B (en) | 2006-04-30 | 2006-04-30 | State reporting method for automatic retransmission request |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101064589B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010148748A1 (en) * | 2009-06-25 | 2010-12-29 | 中兴通讯股份有限公司 | Fast retransmission method and device in radio link control layer acknowledged mode |
| CN103199924A (en) * | 2011-12-20 | 2013-07-10 | Ruag瑞士股份公司 | Method for optical data transmission from low earth orbit to earth and corresponding communication system |
| WO2016026128A1 (en) * | 2014-08-21 | 2016-02-25 | SZ DJI Technology Co., Ltd. | Unmanned aerial vehicle communications methods and systems |
| CN106301703A (en) * | 2015-05-15 | 2017-01-04 | 中兴通讯股份有限公司 | HARQ sending, receiving method, device and node |
| WO2017035727A1 (en) * | 2015-08-31 | 2017-03-09 | Qualcomm Incorporated | Broadcast automatic repeat request |
| CN107710721A (en) * | 2015-08-21 | 2018-02-16 | 华为技术有限公司 | A kind of information processing method, device and system |
| CN114666024A (en) * | 2022-03-11 | 2022-06-24 | 成都中科微信息技术研究院有限公司 | Reverse signaling retransmission method and communication system based on DVB protocol |
| WO2022236476A1 (en) * | 2021-05-08 | 2022-11-17 | Nokia Shanghai Bell Co., Ltd. | Indicating missed negative acknowledgements |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| ES2340467T3 (en) * | 2002-01-03 | 2010-06-04 | Innovative Sonic Limited | MECHANISM TO AVOID TIMER-BASED INTERRUPTIONS, FOR A HIGH SPEED WIRELESS COMMUNICATION SYSTEM. |
| WO2003096567A1 (en) * | 2002-05-10 | 2003-11-20 | Interdigital Technology Corporation | Method for monitoring transmission sequence numbers assigned to protocol data units to detect and correct transmission errors |
| US20060062173A1 (en) * | 2004-09-17 | 2006-03-23 | Lucent Technologies, Inc. | Hybrid automatic repeat request operation during soft hand offs in a wireless system |
-
2006
- 2006-04-30 CN CN2006100118507A patent/CN101064589B/en not_active Expired - Fee Related
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101931516B (en) * | 2009-06-25 | 2013-03-20 | 中兴通讯股份有限公司 | Quick-retransmission method and device in wireless chain control layer determination mode |
| WO2010148748A1 (en) * | 2009-06-25 | 2010-12-29 | 中兴通讯股份有限公司 | Fast retransmission method and device in radio link control layer acknowledged mode |
| CN103199924A (en) * | 2011-12-20 | 2013-07-10 | Ruag瑞士股份公司 | Method for optical data transmission from low earth orbit to earth and corresponding communication system |
| US10366548B2 (en) | 2014-08-21 | 2019-07-30 | SZ DJI Technology Co., Ltd. | Unmanned aerial vehicle communications methods and systems |
| WO2016026128A1 (en) * | 2014-08-21 | 2016-02-25 | SZ DJI Technology Co., Ltd. | Unmanned aerial vehicle communications methods and systems |
| CN106301703B (en) * | 2015-05-15 | 2020-04-07 | 中兴通讯股份有限公司 | HARQ (hybrid automatic repeat request) sending and receiving methods, devices and nodes |
| CN106301703A (en) * | 2015-05-15 | 2017-01-04 | 中兴通讯股份有限公司 | HARQ sending, receiving method, device and node |
| CN107710721A (en) * | 2015-08-21 | 2018-02-16 | 华为技术有限公司 | A kind of information processing method, device and system |
| CN107710721B (en) * | 2015-08-21 | 2020-02-14 | 华为技术有限公司 | Information processing method, device and system |
| US10666398B2 (en) | 2015-08-21 | 2020-05-26 | Huawei Technologies Co., Ltd. | Information processing method, apparatus, and system |
| WO2017035727A1 (en) * | 2015-08-31 | 2017-03-09 | Qualcomm Incorporated | Broadcast automatic repeat request |
| WO2022236476A1 (en) * | 2021-05-08 | 2022-11-17 | Nokia Shanghai Bell Co., Ltd. | Indicating missed negative acknowledgements |
| CN114666024A (en) * | 2022-03-11 | 2022-06-24 | 成都中科微信息技术研究院有限公司 | Reverse signaling retransmission method and communication system based on DVB protocol |
| CN114666024B (en) * | 2022-03-11 | 2024-04-30 | 成都中科微信息技术研究院有限公司 | Reverse command retransmission method and communication system based on DVB protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101064589B (en) | 2011-11-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101064589A (en) | State reporting method for automatic retransmission request | |
| CN101068137A (en) | Apparatus and method for operating automatic repeat request in a broadband wireless access communication system | |
| CN1949698A (en) | Automatic retransmission method, transmitter and receiver for use in LTE technology | |
| CN101047484A (en) | Transmission layer retransmission method and system | |
| JP2021013158A (en) | Method and apparatus for indicating time gap for device-to-device communication in wireless communication system | |
| CN1140968C (en) | Repeated distribution control method and system for multi-place distribution sending service | |
| TWI489816B (en) | Method performed by a wireless transmit/receive unit (wtru) and wtru | |
| US8281200B2 (en) | Method and device for retransmitting data | |
| CN1918841A (en) | Identification and re-transmission of missing parts | |
| CN1702993A (en) | Wireless communication apparatus | |
| CN101047481A (en) | Automatic retransmission requiring distribution feedback method in radio communication system | |
| EP2241126B1 (en) | Method of exchanging data between a base station and a mobile station. | |
| CN1976272A (en) | Method and apparatus for controlling reliability of feedback signal in a mobile communication system | |
| US20100325504A1 (en) | Method for transmitting/receiving broadcast or multicast service and terminal thereof | |
| CN1922813A (en) | A method for data repair in a system capable of handling multicast and broadcast transmissions | |
| CN1917416A (en) | Mixing automatic retransmission method in accessing down going packet in high speed and multiple carriers | |
| CN1692568A (en) | Method for moving a receive window in a radio access network | |
| CN1836401A (en) | Feedback signalling for multicast data transmission | |
| CN101030840A (en) | Data transmission with re-transmission demand and method for presenting receiving-end state report | |
| CN101034959A (en) | Mixed automatic retransferring method and its device and system | |
| CN101060386A (en) | Hybrid automatic forward request entity and its data block submission method | |
| CN101060388A (en) | Hybrid data automatic forward method and device | |
| TW201703451A (en) | Method and apparatus for handling status information in a telecommunication system | |
| CN1951135A (en) | Control station apparatus, base station apparatus, receiving method, transmitting method and communicating method | |
| JP5690480B2 (en) | Base station, user terminal, and method for realizing single cell enhanced MBMS |
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 | ||
| ASS | Succession or assignment of patent right |
Owner name: JIANGSU GULF ELECTRICAL TECHNOLOGY CO., LTD. Free format text: FORMER OWNER: ZTE CORPORATION Effective date: 20141127 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518057 SHENZHEN, GUANGDONG PROVINCE TO: 226000 NANTONG, JIANGSU PROVINCE |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20141127 Address after: 226000 Jiangsu Province, Nantong City Chongchuan District Chongchuan Road No. 1 building new office 406, 408, 409. Patentee after: JIANGSU GULF ELECTRICAL TECHNOLOGY CO., LTD. Address before: 518057 Nanshan District, Guangdong high tech Industrial Park, science and Technology Industrial Park, ZTE building, block A, layer 6, layer Patentee before: ZTE Corporation |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: State reporting method for automatic retransmission request Effective date of registration: 20171101 Granted publication date: 20111130 Pledgee: Nantong Productivity Promotion Center Pledgor: JIANGSU GULF ELECTRICAL TECHNOLOGY CO., LTD. Registration number: 2017980000443 |
|
| PC01 | Cancellation of the registration of the contract for pledge of patent right | ||
| PC01 | Cancellation of the registration of the contract for pledge of patent right |
Date of cancellation: 20181012 Granted publication date: 20111130 Pledgee: Nantong Productivity Promotion Center Pledgor: JIANGSU GULF ELECTRICAL TECHNOLOGY CO., LTD. Registration number: 2017980000443 |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20111130 Termination date: 20190430 |