[go: up one dir, main page]

CN1667993A - A method for controlling transmit frequency of status report - Google Patents

A method for controlling transmit frequency of status report Download PDF

Info

Publication number
CN1667993A
CN1667993A CN 200410064316 CN200410064316A CN1667993A CN 1667993 A CN1667993 A CN 1667993A CN 200410064316 CN200410064316 CN 200410064316 CN 200410064316 A CN200410064316 A CN 200410064316A CN 1667993 A CN1667993 A CN 1667993A
Authority
CN
China
Prior art keywords
nack
pdu
status report
counter
condition
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
Application number
CN 200410064316
Other languages
Chinese (zh)
Other versions
CN100359842C (en
Inventor
杨学志
丁颖哲
许炳
曲秉玉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CNB2004100643163A priority Critical patent/CN100359842C/en
Publication of CN1667993A publication Critical patent/CN1667993A/en
Application granted granted Critical
Publication of CN100359842C publication Critical patent/CN100359842C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method for controlling transmit frequency of status report, which sets transmitting conditions for the status report sent from the receiving entity to the transmitting entity, containing NACK; before transmitting the status report containing NACK from the receiving entity to the transmitting entity, aiming at each PDU which is not correctly received by receiving entities in the investigation scope of the status report, judge if it meets the preset transmitting condition of NACK currently, if it does not meet, the PDU's NACK will not be contained in the status report; or the PDU's NACK is allowed to be contained in the status report. The invention solves the problems about redundant PDU and status report transmission in existing technology. On the precondition of not influencing the transmission of status report containing NACK, the invention restricts the transmission of status report containing NACK, reduces the transmission of redundant status report and retransmission of redundant PDU, improves the usage of communication link.

Description

A kind of method of state of a control report transmission frequency
Technical field
The present invention relates to data cell status report technical field, relate to the method for state of a control report transmission frequency in the automatic repeat requests mechanism of wireless communication system or rather.
Background technology
Universal mobile telecommunications system (UMTS) is to adopt the 3-G (Generation Three mobile communication system) of Wideband Code Division Multiple Access (WCDMA) (WCDMA) air interface technologies, is also referred to as the WCDMA system usually.
The wave point of WCDMA is divided into physical layer, data link layer and network layer.Transparent mode (TM), Unacknowledged Mode (UM) and three kinds of patterns of affirmation mode (AM) are supported in Radio Link control (RLC) in the data link layer, realize functions such as segmentation, cascade, filling, error control, flow control, repeatability detection.Wherein, RLC AM entity comprises sending entity and receiving entity, and the data cell that sending entity and receiving entity send network layer is handled, and the data cell after will handling sends to network layer again.The functional mode of the RLC AM entity of being made up of sending entity and receiving entity is referring to Fig. 1, and corresponding processing procedure is then referring to Fig. 2.Wherein, sending entity carries out the data cell processing by following steps:
Step 201, sending entity at first carry out segmentation/cascade to this protocol processing unit (PDU) and handle when receiving the RLC Service Data Unit (SDU) that network layer sends.
According to actual needs, sending entity also may need the RLC PDU after segmentation/cascade processing is filled processing.
Step 202, assembling acknowledged mode data (AMD) PDU, and the AMD PDU after will assembling sends to transmission buffer.
Transmission buffer in step 203, the sending entity is dispatched the AMD PDU that self preserves.
If step 204, the PDU that is dispatched to can send, then the rule according to the network layer configuration is provided with poll bits, and the AMD PDU after will handling then submits to bottom and sends to receiving entity.
In step 204, the AMD PDU for new assembling also will be provided with the sequence number territory, afterwards AMD PDU is encrypted.
Receiving entity carries out data cell by following steps to be handled:
Step 205, receiving entity are decrypted the AMD PDU that correctly receives, and the data that deciphering obtains are put into reception buffer.
Step 206, this AMD PDU is resolved, judging the RLC SDU that can recombinate out, if the RLC SDU that can recombinate out complete, the operation of then recombinating, and the RLCSDU that reorganization obtains is submitted to high level.
In above-mentioned steps 206, receiving entity is before resolving the AMD PDU after the deciphering, also need value according to poll bits among the AMD PDU, and the status report mechanism that in receiving entity, disposes of network layer, judge whether the transmission of current AMD PDU is accurate, also be, judge whether and to send the status report that is used for data retransmission to sending entity, if desired, then receiving entity is assembled corresponding status report, and this status report is sent to bottom.Bottom then sends to this status report the re-transmission buffer in the sending entity, the AMD PDU that re-transmission buffer then retransmits according to the status report buffer memory needs of receiving.In this case, the AMD PDU of transmission buffer scheduling not only has the AMD PDU of new assembling in the above-mentioned steps 203, also comprises being kept at waiting for the AMDPDU that retransmits in the re-transmission buffer.The mechanism of this retransmission of data units is called automatic repeat requests (ARQ) mechanism.
What comprise in the status report that receiving entity is assembled is positive acknowledgement (ACK) information and Negative Acknowledgement (NACK) information, and the status report that is used for data retransmission comprises NACK, is used for determining that the status report that AMDPDU is correctly received then comprises ACK.In above-mentioned whole communication process from the sending entity to the receiving entity, if sending entity is received the status report that comprises NACK, the status report that also promptly is used for data retransmission then retransmits transmission and PDU wrong or that be dropped occurs, to guarantee the correct transmission of data cell.Certainly, if sending entity is received the status report that comprises ACK, can confirm that then corresponding PDU has correctly been transmitted.
But can occurring at present receiving entity usually, to send repeatedly at same PDU and the affirmation information that comprises to sending entity be the status report of NACK, and sending entity repeatedly retransmits same PDU to receiving entity.That is to say, can cause system need transmit a lot of redundant datas usually at present, and this has obviously wasted data transmission resources, and receiving entity and sending entity all to be wasted the more time on transmission of redundant data.
In addition,, also to wait for the report of receiving entity return state because sending entity is after sending to receiving entity with PDU, if comprise in the status report that receiving entity returns be NACK, then this sending entity also should send this PDU once more to receiving entity.The stand-by period of sending entity in whole process is time delay.If sending entity is received the status report of a plurality of NACK of comprising that receiving entity returns, then sending entity all is being a time delay at this PDU from what send for the first time that PDU once retransmits PDU to the end during this period of time, obviously, the time of this section time delay is longer, taken the resource of sending entity, and also can the work of sending entity have been affected.Prior art does not address this problem at present yet.
The problems referred to above are not only in the ARQ mechanism that appears at the WCDMA system, also appear in the ARQ mechanism of TD SDMA (TD-SCDMA) system and CDMA2000.For WCDMA and TD-SCDMA system, ARQ mechanism is in the affirmation pattern (AM) of rlc protocol; For the CDMA2000 system, ARQ mechanism then is in the ARQ sublayer of link access control (LAC) agreement.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of method of state of a control report transmission frequency, transmits redundant status report and data cell to avoid system.
For reaching above purpose, technical scheme of the present invention is achieved in that a kind of method of report data location mode, be applicable to the communication system that comprises sending entity and receiving entity, and adopt automatic retransmission mechanism to communicate between sending entity and the receiving entity, this method may further comprise the steps:
A. for being detected, each does not have the correct protocol Data Unit PDU that receives to set Negative Acknowledgement NACK transmission condition;
B. receiving entity is at every turn before the sending entity status report, at each PDU that is not correctly received in this status report investigation scope by this receiving entity, judge that the current NACK that sets for this PDU that whether meets sends condition, if do not meet, then in status report, do not comprise the NACK of this PDU; Otherwise permission comprises the NACK of this PDU in status report;
C. receiving entity sends to sending entity with this status report.
Whether among the described step a, described transmission condition enactment: at first judging current is to send the NACK status report for the first time at PDU if being, if then meet NACK and send condition; Otherwise, further judge whether to exist corresponding and be in the NACK timing device of normal operating conditions with this PDU, if exist, then do not meet NACK and send condition, otherwise, meet NACK and send condition.
Described step c may further include: the NACK of the corresponding PDU of each NACK in the report of receiving entity difference init state sends condition.
Among the step c, described initialization NACK transmission condition is: if the current existence NACK timing device corresponding with described PDU then directly starts this timing device; Otherwise,, and start this timing device for this PDU sets a NACK timing device.
Among the described step a, described is that same NACK sends condition for each is detected the NACK transmission condition that does not have the correct PDU that receives to set;
Among the step a, described NACK sends condition enactment and is: judge whether to exist the NACK timing device that is in normal operating conditions, if exist, then do not meet NACK and send condition; Otherwise, meet NACK and send condition;
Described step c further comprises: initialization NACK sends condition;
Described initialization NACK transmission condition is: if currently have a described NACK timing device, then directly start this timing device; Otherwise, set a NACK timing device and startup.
Described NACK timing device is the NACK timer;
Among the step a, described NACK timing device is in normal operating conditions and is: the NACK timer has started and is not overtime as yet.
Described NACK timing device is a counter;
Among the step a, described NACK timing device is in normal operating conditions and is: counter is in count status.
This method may further include: the upper and lower bound of rolling counters forward scope is set, and the initial value that counter is set is the upper limit of count range, and counter is set to: every certain time interval, counter subtracts one with current count value;
Among the step a, described counter is in count status and is: the current numerical value of counter is greater than the lower limit of count range;
Among the step c, described initialization NACK sends condition and further comprises: the initial value of counter is set to the upper limit of count range.
Described every certain time interval, counter subtracts one with current count value and is: whenever receive mac state indication MAC_Status_Ind that medium access control system MAC sends once, counter subtracts one with current count value.
This method can further include: the upper and lower bound of rolling counters forward scope is set, and the initial value that counter is set is the lower limit of count range, and counter is set to: every certain time interval, counter adds one with current count value;
Among the step a, described counter is in count status and is: the current numerical value of counter is less than the upper limit of rolling counters forward scope;
Among the step c, described initialization NACK sends condition and further comprises: the initial value of counter is set to the lower limit of count range.
Described every certain time interval, counter adds one with current count value and is: whenever receive MAC_Status_Ind that MAC sends once, counter adds one with current count value.
Described automatic repeat requests mechanism can be arranged in the affirmation Mode A M of Wideband Code Division Multiple Access (WCDMA) WCDMA or TD SDMA TD-SCDMA system Radio Link control rlc protocol.
Described automatic repeat requests mechanism can also be arranged in the automatic repeat requests ARQ sublayer of the link access control LAC of CDMA2000 system agreement.
The present invention program is by being provided with the condition that sends the status report that comprises NACK, under the prerequisite that does not influence the status report transmission that comprises ACK, limited the transmission of the status report that comprises NACK, reduced the transmission of redundant state report, and and then reduced redundant re-transmission PDU, improved the utilance of communication link.
Description of drawings
Fig. 1 is the functional mode schematic diagram of RLC AM entity in the prior art;
Fig. 2 sends to PDU for sending entity in the prior art realization flow schematic diagram of receiving entity;
Fig. 3 is the realization flow figure of a kind of embodiment of the present invention program.
Embodiment
Obtain by analysis, the problem of redundant data transmissions why can occur, mainly contain the reason of two aspects.On the one hand be that sending entity needs a loop time (RTT) could obtain the information whether this receiving entity correctly receives PDU after sending a PDU at least because all there is time-delay in the transmission of PDU and status report in the communication system.Because therefore the situation in the following step can appear in the existence of time-delay:
Steps A, sending entity send PDU for the first time, and mistake has appearred in this PDU in transmission course, promptly do not send to receiving entity;
Step B, receiving entity detect this PDU and lose, and send the status report that comprises NACK to sending entity;
After step C, sending entity are received status report at this PDU, for the second time this PDU is transferred to receiving entity, promptly retransmits this PDU;
Step D, owing to there is time-delay, before receiving the PDU that sending entity retransmits, receiving entity sends the status report that comprises NACK to transmit leg once more;
Step e, after send status report once more, receiving entity has received that sending entity retransmits the PDU of coming, and sends the status report that comprises ACK to sending entity afterwards;
Step F, owing to there is time-delay, before receiving the status report that comprises ACK that receiving entity sends, sending entity is at first received the status report that comprises NACK that receiving entity sends in step D, therefore transmit this PDU to receiving entity for the third time.
Obviously, said process has caused the transmission of redundant data.
The reason on the other hand that redundant data transmissions occurs is: for adapting to different business needs, RLC supports the trigger mechanism of various states inquiry and status report.Status poll mechanism allows receiving entity to carry out status poll neatly according to different mechanism, the trigger mechanism of status report allows receiving entity according to different mechanism configuration status accounting neatly, for sending entity, only need get final product according to the PDU that the Information Selection needs in the status report retransmit.But, if receiving entity sends status report at same PDU according to multiple different mechanism, the situation that receiving entity continuous status report in the short time interval then may occur, this will cause the frequency of status report arrival sending entity higher, retransmit thereby redundant PDUs may occur, and then the waste interface-free resources.
Timer (Timer_Poll_Prohibit) is forbidden in timer Status Disable timer (Timer_Status_Prohibit) and the inquiry that defines in the agreement at present, can be by certain period of time be set, the transmission frequency of status report is limited in certain scope.With Timer_Status_Prohibit is example, this timer only just is activated when having used the status report prohibiting function, if Timer_Status_Prohibit is in normal operating conditions, then receiving entity can not send the status report that comprises NACK or ACK.After the status report transmission of receiving entity, start this timer, and before this timer expiry, can not send the new state report of NACK or ACK at STATUS PDU.Though can the transmission frequency of status report be limited in certain scope by certain period of time is set, in other words, though by the transmission frequency that bigger Timer_Status_Prohibit and Timer_Poll_Prohibit can the state of a control reports is set, and reduce or eliminate the transmission of redundant data, but there is defective in this method.This is because ARQ mechanism requires different for the transmission frequency of ACK and NACK: the frequency of ACK is high more, the sending entity PDU of buffer memory in the buffer of clear to send in time just then, thus can reduce send window blocking probability, improve the utilance of link and reduce demand internal memory; Because the problem that the redundant data unit transmits, the frequency that sends NACK can not be too high.That is to say that existing technical scheme can not satisfy the requirement of ACK and NACK simultaneously, and can not stop the problem that the redundant data unit transmits well.
In order not influence the transmission frequency of the status report that comprises ACK as far as possible, can reduce the transmission frequency of the status report that comprises NACK again, the present invention program mainly is on the basis of existing technology, for being detected, each does not have the correct PDU that receives that a NACK transmission condition is set, like this, receiving entity is before status report, at first at not being received the correct PDU that receives of entity, judge that current whether meeting at the set NACK of this PDU sends condition, if do not meet, then in status report, do not comprise NACK at this PDU; Otherwise, allow in this status report, to comprise NACK, and send condition for this PDU resets NACK at this PDU.
Among the present invention program, can be detected at each does not have the PDU that correctly receives that NACK transmission condition is set, certainly, different at the NACK transmission condition possibility of different PDU; Can be detected at all does not have the correct PDU that receives that same NACK transmission condition is set yet, and, all are detected does not have the corresponding same NACK of the correct PDU that receives to send condition yet.
At first each being detected the situation that does not have the correct PDU that receives that NACK transmission condition is set below is elaborated.Referring to Fig. 3, present embodiment to be being set to example to PDU (n), and set timing device is timer, and corresponding solution may further comprise the steps:
Step 301,, each does not have the correct PDU that receives that NACK is set to send condition for being detected.
Set NACK transmission condition is: if current be to send the NACK status report for the first time at certain PDU, the NACK at this PDU then can be set in status report; If sent the NACK status report at this PDU before, in other words, the current NACK status report that needs to send is not for the first time, then also need to judge whether to exist corresponding and be in the NACK timing device of normal operating conditions with this PDU, if there is such timing device, the NACK at this PDU can not be set in status report then; Otherwise, the NACK at this PDU can be set in status report.
In the present embodiment, this timing device is timer, and timing device is in running order to be that timer is activated and not overtime as yet.
Step 302~303, receiving entity at first judge whether and need send NACK at PDU (n) when the needs status report, if, then enter step 304, otherwise, step 307 entered.
Step 304, receiving entity judge further whether this NACK is to send for the first time, if then determine to meet NACK and send condition, and enter step 306; Otherwise, enter step 305.
Step 305, receiving entity judge currently whether exist corresponding with this PDU and be in the NACK timer of normal operating conditions, if exist, then determine not meet NACK and send condition, and enter step 307; Otherwise, determine to meet NACK and send condition, and enter step 306.
Step 306, in status report, add NACK, enter step 307 afterwards at this PDU (n).
Step 307, receiving entity are handled next PDU.
In step 307,, then continue to handle next PDU, otherwise receiving entity sends to sending entity with current status report if receiving entity determines can also comprise in the status report NACK at other PDU.
By above step, can realize purpose of the present invention.
In addition, receiving entity is being handled status report, when also this status report being sent to sending entity, also should reinitialized the timer at the pairing PDU of other NACK in this PDU (n) and this status report.Certainly, receiving entity also can reinitialize corresponding timer immediately after these NACK are added status report.For the initialization timing device, if the current existence NACK timer corresponding with this PDU then directly starts this timer and get final product; Otherwise,, and start this timer for this PDU sets a NACK timer.
That is to say, such scheme is at first set NACK transmission condition for detecting the PDU that goes wrong, receiving entity is to the sending entity status report time, then at first there is not the correct PDU that receives at being detected, judge whether to satisfy the NACK that sets and send condition, if satisfy, then allow in status report, to increase NACK at this PDU; Otherwise, in this status report, do not comprise NACK at this PDU.That is to say,, then in this timer time,, can not send this NACK to sending entity even receiving entity has triggered the NACK at this PDU again if receiving entity has started timer at certain PDU.Only there be not the timer corresponding with PDU, and the timer corresponding with PDU arranged but this timer is not activated or the situation of timer expiry under, receiving entity could comprise the NACK at this PDU in status report, and this status report is sent to sending entity.
Certainly, can also be set to counter by timing device, and this counter is set to count according to certain time interval.Because sending to RLC at interval with regular time, MAC is used to notify RLC can send to the data rate of MAC, also be, RLC can send to the quantity of the PDU of MAC within a certain period of time, therefore, the mac state indication (MAC_Status_Ind) that can this counter is set to send according to MAC is counted.The upper and lower bound of rolling counters forward scope also will be set, and wherein, the initial value of counter is set to the upper limit of count range.And counter is after startup, and every certain time interval, the count value that is about to self subtracts one.For situation about counting according to MAC_Status_Ind, then for whenever receiving MAC_Status_Ind that MAC sends once, then the count value with self subtracts one.
By such setting, receiving entity is when status report, there be the counter corresponding if detect with certain PDU, need also then to judge whether at the pairing counter of this PDU be the lower limit of count range, if, then in this status report, comprise NACK at this PDU, otherwise, NACK in this status report, do not comprised at this PDU.
Above-mentioned is the upper limit that the initial value of rolling counters forward scope is set to count range, similarly, can also initial value be set to the lower limit of count range, then counter is after startup, whenever receive that MAC_Status_Ind that MAC sends once, then adds one with current count value.Like this, receiving entity is when status report, there be the counter corresponding if detect with certain PDU, then also need to judge at certain and be detected whether the pairing counter of PDU that does not have correct reception is the count range upper limit that is provided with, if, then in status report, comprise NACK at this PDU, otherwise, NACK comprised in the report of not being at state at this PDU.
For timing device is the situation of counter, and same, reinitializing counter can be when status report is sent to sending entity, also can be when NACK is included in status report.In addition, reinitializing counter is the initial value of resetting counter.For the count initialized device, if the current existence counter corresponding with this PDU then directly starts this counter and get final product; Otherwise,, and start this counter for this PDU sets a counter.
Above-mentioned is to be detected at each not have the correct PDU that receives that NACK transmission condition is set, there is not the correct PDU that receives that NACK transmission condition is set for being detected at all, also be second kind of processing mode of the present invention program, with the main distinction of above-mentioned processing procedure be following some:
1) this processing procedure is to be detected at all not have the correct PDU that receives that NACK transmission condition is set.Set NACK transmission condition is: judge whether to exist the NACK timing device that is in normal operating conditions, if then do not meet NACK and send condition; Otherwise, meet NACK and send condition.
2) this processing procedure when determining to send NACK at PDU (n), directly judges whether to exist the NACK timing device that is in normal operating conditions at receiving entity, if then determine not meet NACK and send condition; Otherwise, determine to meet NACK and send condition.
By the above-mentioned second way, if being detected at all, receiving entity do not have the correct PDU that receives to start timing device, then at this timing device in the time, even receiving entity has triggered again at the NACK of certain PDU wherein, can not send NACK to sending entity at this PDU.Only the NACK timing device is being set not, and have corresponding NACK timing device but this timing device is not activated or the situation of timer expiry under, receiving entity could comprise the NACK at this PDU in status report, and this status report is sent to sending entity.Certainly, the timing device in this processing mode can be timer equally, also can be counter, can also be that other can realize device regularly.
The above only is the present invention program's preferred embodiment, not in order to limit protection scope of the present invention.

Claims (10)

1, a kind of method of state of a control report transmission frequency is applicable to the communication system that comprises sending entity and receiving entity, and adopts automatic retransmission mechanism to communicate between sending entity and the receiving entity, it is characterized in that this method may further comprise the steps:
A. for being detected, each does not have the correct protocol Data Unit PDU that receives to set Negative Acknowledgement NACK transmission condition;
B. receiving entity is at every turn before the sending entity status report, at each PDU that is not correctly received in this status report investigation scope by this receiving entity, judge that the current NACK that sets for this PDU that whether meets sends condition, if do not meet, then in status report, do not comprise the NACK of this PDU; Otherwise permission comprises the NACK of this PDU in status report;
C. receiving entity sends to sending entity with this status report.
2, whether method according to claim 1, and described transmission condition enactment is: at first judging current is to send the NACK status report for the first time at PDU if is characterized in that among the described step a, if then meet NACK and send condition; Otherwise, further judge whether to exist corresponding and be in the NACK timing device of normal operating conditions with this PDU, if exist, then do not meet NACK and send condition, otherwise, meet NACK and send condition;
Described step c further comprises: the NACK of the corresponding PDU of each NACK in the report of receiving entity difference init state sends condition;
Described initialization NACK transmission condition is: if the current existence NACK timing device corresponding with described PDU then directly starts this timing device; Otherwise, for this PDU sets a NACK timing device and startup.
3, method according to claim 1 is characterized in that among the described step a, and described is that same NACK sends condition for each is detected the NACK transmission condition that does not have the correct PDU that receives to set;
Among the step a, described NACK sends condition enactment and is: judge whether to exist the NACK timing device that is in normal operating conditions, if exist, then do not meet NACK and send condition; Otherwise, meet NACK and send condition;
Described step c further comprises: initialization NACK sends condition;
Described initialization NACK transmission condition is: if currently have a described NACK timing device, then directly start this timing device; Otherwise, set a NACK timing device and startup.
According to claim 2 or 3 described methods, it is characterized in that 4, described NACK timing device is the NACK timer;
Among the step a, described NACK timing device is in normal operating conditions and is: the NACK timer has started and is not overtime as yet.
According to claim 2 or 3 described methods, it is characterized in that 5, described NACK timing device is a counter;
Among the step a, described NACK timing device is in normal operating conditions and is: counter is in count status.
6, method according to claim 5, it is characterized in that, this method further comprises: the upper and lower bound that the rolling counters forward scope is set, the initial value that counter is set is the upper limit of count range, and counter is set to: every certain time interval, counter subtracts one with current count value;
Among the step a, described counter is in count status and is: the current numerical value of counter is greater than the lower limit of count range;
Among the step c, described initialization NACK sends condition and further comprises: the initial value of counter is set to the upper limit of count range.
7, method according to claim 6, it is characterized in that, described every certain time interval, counter subtracts one with current count value and is: whenever receive mac state indication MAC_Status_Ind that medium access control system MAC sends once, counter subtracts one with current count value.
8, method according to claim 5, it is characterized in that, this method further comprises: the upper and lower bound that the rolling counters forward scope is set, the initial value that counter is set is the lower limit of count range, and counter is set to: every certain time interval, counter adds one with current count value;
Among the step a, described counter is in count status and is: the current numerical value of counter is less than the upper limit of rolling counters forward scope;
Among the step c, described initialization NACK sends condition and further comprises: the initial value of counter is set to the lower limit of count range.
9, method according to claim 8 is characterized in that, and is described every certain time interval, and counter adds one with current count value and is: whenever receive MAC_Status_Ind that MAC sends once, counter adds one with current count value.
10, method according to claim 1 is characterized in that, described automatic repeat requests mechanism is arranged in the affirmation Mode A M of Wideband Code Division Multiple Access (WCDMA) WCDMA or TD SDMA TD-SCDMA system Radio Link control rlc protocol; Or be arranged in the automatic repeat requests ARQ sublayer of the link access control LAC of CDMA 2000 systems agreement.
CNB2004100643163A 2004-03-12 2004-08-20 A method for controlling transmit frequency of status report Expired - Fee Related CN100359842C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2004100643163A CN100359842C (en) 2004-03-12 2004-08-20 A method for controlling transmit frequency of status report

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN200410008822.0 2004-03-12
CN200410008822 2004-03-12
CNB2004100643163A CN100359842C (en) 2004-03-12 2004-08-20 A method for controlling transmit frequency of status report

Publications (2)

Publication Number Publication Date
CN1667993A true CN1667993A (en) 2005-09-14
CN100359842C CN100359842C (en) 2008-01-02

Family

ID=35038892

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2004100643163A Expired - Fee Related CN100359842C (en) 2004-03-12 2004-08-20 A method for controlling transmit frequency of status report

Country Status (1)

Country Link
CN (1) CN100359842C (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009023986A1 (en) * 2007-08-20 2009-02-26 Alcatel Shanghai Bell Co., Ltd. The method and the device for triggered repeat in the multicast system
CN101291199B (en) * 2007-04-20 2011-03-09 大唐移动通信设备有限公司 Method and apparatus for detecting correctness of feedback message in hybrid automatic retransmission request
CN101453311B (en) * 2007-11-29 2011-12-28 中兴通讯股份有限公司 Triggering method for automatic retransmission request status report
CN103138905A (en) * 2011-11-24 2013-06-05 华为技术有限公司 Radio link control (RLC) data package transmission confirmation method and RLC acknowledge mode (AM) entity sender
WO2019024837A1 (en) * 2017-08-02 2019-02-07 华为技术有限公司 Counting method and communication device

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5636230A (en) * 1994-05-31 1997-06-03 Motorola, Inc. Method for eliminating a receiving data unit as a source of excessive resend requests
JP3087886B2 (en) * 1995-10-24 2000-09-11 株式会社エヌ・ティ・ティ・ドコモ Retransmission control method for CDMA mobile communication
EP1263160A1 (en) * 2001-06-01 2002-12-04 Telefonaktiebolaget Lm Ericsson Method and transmitter for an efficient packet data transfer in a transmission protocol with repeat requests
CN1192647C (en) * 2001-09-06 2005-03-09 华为技术有限公司 Self-adapting method for mobile communication transmitting signals

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101291199B (en) * 2007-04-20 2011-03-09 大唐移动通信设备有限公司 Method and apparatus for detecting correctness of feedback message in hybrid automatic retransmission request
WO2009023986A1 (en) * 2007-08-20 2009-02-26 Alcatel Shanghai Bell Co., Ltd. The method and the device for triggered repeat in the multicast system
US8667356B2 (en) 2007-08-20 2014-03-04 Alcatel Lucent Method for triggering retransmission in a multicast system and apparatus implementing the method
CN101453311B (en) * 2007-11-29 2011-12-28 中兴通讯股份有限公司 Triggering method for automatic retransmission request status report
CN103138905A (en) * 2011-11-24 2013-06-05 华为技术有限公司 Radio link control (RLC) data package transmission confirmation method and RLC acknowledge mode (AM) entity sender
CN103138905B (en) * 2011-11-24 2016-08-03 华为技术有限公司 The confirmation method of RLC packet transmission and RLC AM entity sender
CN105897385A (en) * 2011-11-24 2016-08-24 华为技术有限公司 Method for acknowledging transmission of RLC (Radio Link Control) data packet and RLC AM (Acknowledge Mode) entity sender
WO2019024837A1 (en) * 2017-08-02 2019-02-07 华为技术有限公司 Counting method and communication device
US11258545B2 (en) 2017-08-02 2022-02-22 Huawei Technologies Co., Ltd. Counting method and communications apparatus

Also Published As

Publication number Publication date
CN100359842C (en) 2008-01-02

Similar Documents

Publication Publication Date Title
CN1135774C (en) Method and apparatus for discarding packets in a data network having automatic repeat request
EP1976176B1 (en) A method and apparatus for data retransmission
CN1279772C (en) Device and method for retransmitting data in mobile communication system
CN101888291B (en) Method and apparatus for implementing a data lifespan timer for enhanced dedicated channel transmissions
EP1512243B1 (en) Rlp retransmission for cdma communication systems
CN1367964A (en) Error control method and apparatus
US20070168826A1 (en) Method and system for implementing h-arq-assisted arq operation
CN1768498A (en) Avoiding stall conditions and sequence number ambiguity in an automatic repeat request protocol
CN1642067A (en) Data transmission method and data transmission apparatus
CN101047484A (en) Transmission layer retransmission method and system
CN101814982A (en) Method and system for implementing H-ARQ-assisted arq operation
CN1496157A (en) Data retransmission control method for mobile communication system
CN1918825A (en) Transmitting and receiving control protocol data unit having processing time information
CN1154305C (en) Method and device for promoting quick sliding of radio link control layer data transmission window
CN101047481A (en) Automatic retransmission requiring distribution feedback method in radio communication system
CN1245041C (en) Method for Avoiding Pause Using the Receive State of HARQ Process
CN101076962A (en) Data unit sender control method
CN101064589A (en) State reporting method for automatic retransmission request
CN101076017A (en) Method and apparatus for rlc protocol error handling in a wireless communications system
CN1719762A (en) Data retransmission method based on high-speed down link data packet access technique
CN1667993A (en) A method for controlling transmit frequency of status report
CN1667991A (en) A data unit retransmission method
EP1863212A2 (en) Dual receiving window method and apparatus for automatic retransmission request
CN101277174A (en) Method and apparatus for data retransmission based on service quality as well as radio communication system
CN1949697A (en) Data transmission method for ensuring receiver and transmitter data identification

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
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20080102

Termination date: 20150820

EXPY Termination of patent right or utility model