WO2008000181A1 - Procédés et systèmes de retransmission sur couche de transport - Google Patents
Procédés et systèmes de retransmission sur couche de transport Download PDFInfo
- Publication number
- WO2008000181A1 WO2008000181A1 PCT/CN2007/070140 CN2007070140W WO2008000181A1 WO 2008000181 A1 WO2008000181 A1 WO 2008000181A1 CN 2007070140 W CN2007070140 W CN 2007070140W WO 2008000181 A1 WO2008000181 A1 WO 2008000181A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- receiving end
- data block
- timer
- control message
- receiving
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
- H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
- H04L1/1678—Details of the supervisory signal the supervisory signal being transmitted together with control information where the control information is for timing, e.g. time stamps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1803—Stop-and-wait protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1809—Selective-repeat protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1874—Buffer management
Definitions
- the present invention relates to the field of network communication technologies, and in particular, to a transport layer retransmission method and system.
- the AM service two types of PDUs, that is, control PDUs and service PDUs, are transmitted between the transmitting entity and the receiving entity.
- the specific implementation process of the AM service is: the sending entity divides the SDUs received from the upper layer into RLC PDUs of appropriate size, or connects different SDUs into one RLC service PDU, and then attaches an RLC header to the RLC service PDU, and RLC Service PDU
- the control PDU here includes: some PDUs for receiving services generated by the RLC entity itself
- the receiving entity receives the PDU from the MAC sublayer
- the receiving entity may request the transmitting entity to resend the PDU by sending an erroneous reception confirmation to the transmitting side.
- the receiving end trigger status report is based on the detection of the RLC PDU received or not received, that is, the receiving end is correctly receiving the RLC PDU.
- the sending window of the sender is updated and moved according to the timer, that is, the RLC PDU waiting to be retransmitted in the sender buffer.
- the sender If the retransmission is not required within a certain period of time, the sender considers that the RLC PDUs waiting to be retransmitted have been correctly received by the receiving end, and the transmitting end deletes the RLC that it has confirmed that it has been correctly received by the receiving end. PDU.
- the sender can also use the HARQ (Hybrid Automatic Repeat) to trigger the local ACK to delete the RLC PDU in its cache.
- HARQ Hybrid Automatic Repeat
- the specific implementation method is as follows: After receiving the ACK acknowledgement from the receiving end, the HARQ of the sending end sends a local ACK indication to the ARQ to delete the SDU after waiting for a period of time to prevent the NACK -> ACK phenomenon.
- the transmit window of the sender and the receive window of the receiver are likely to be out of synchronization, resulting in data loss.
- the detection method and detection time of the phenomenon are different. Therefore, the HARQ at the transmitting end
- the waiting time is not easy to control, and the phenomenon of deleting the RLC PDU before detecting the NACK -> ACK and DTX-> ACK phenomenon occurs, resulting in data loss.
- An embodiment of the present invention provides a transport layer retransmission method and system, which can obtain data that has been correctly received by a receiving end in a buffer of a transmitting end by using an acknowledgment of correct receiving data between the peer entities. Delete in time, and avoid data loss.
- a transport layer retransmission method provided by an embodiment of the present invention includes:
- the transmitting end receives the control message sent by the receiving end, where the control message carries the data block information correctly received by the receiving end;
- the sender deletes the data block stored in the buffer and received by the receiver correctly according to the received control message.
- Embodiments of the present invention also provide A transmission layer retransmission system includes: a sending end and a receiving end, wherein the sending end is provided with a deleting module, and the receiving end is provided with a sending module;
- a sending module configured to send the data block information correctly received by the receiving end to the sending end by using a control message
- the delete module is configured to delete the data block stored in the sender buffer and received correctly by the receiver according to the control message received by the sender.
- the transmitting end of the embodiment of the present invention deletes the buffered data block that has been correctly received by the receiving end by using the display signaling sent by the receiving end, thereby avoiding the sending end and the receiving end.
- the phenomenon of data loss and loss is avoided. Therefore, the phenomenon of data loss is avoided. Therefore, the technical solution provided by the present invention improves the buffer utilization of the transmitting end and improves the implementation process of the transport layer retransmission in the evolved mobile access network system.
- FIG. 1 is a flow chart of a method for retransmission of a transport layer according to an embodiment of the present invention.
- the data block that is buffered in the transmitting end and has been correctly received by the receiving end is deleted by explicit signaling sent by the receiving end.
- the data block deleted by the transmitting end may be any data block correctly received by the receiving end described in the explicit signaling, or may be a data block partially received by the receiving end as described in the explicit signaling.
- the data block here is RLC PDU or SDU
- explicit signaling is a control message, such as a status report. That is, the receiving end triggers and generates a control message such as a status report according to a predetermined triggering principle, and sends the status report to the sending end, and the sending end caches the status message according to the received control message, such as the status report.
- the RLC PDU or SDU correctly received by the receiving end is deleted.
- a status report is taken as an example for explanation.
- the principle of the triggering status report of the receiving end in the system is completely different.
- the receiving end is detecting the RLC PDU.
- the status report of the receiving end is for receiving the RLC PDU with the receiving abnormality. Therefore, the status report in the prior art may be referred to as a status report based on the receiving abnormality.
- the predetermined triggering principle is not only for the receiving abnormal phenomenon, that is, the status report of the receiving end in the embodiment of the present invention. Mainly for receiving the correct data block, therefore, the state in the embodiment of the present invention includes a status report that can be referred to as receiving based on the correct.
- the main information included in the status report sent by the receiving end in the embodiment of the present invention is: information of the RLC PDU or SDU that the receiving end has correctly received, such as the RLC PDU that the receiving end has correctly received.
- the status report may also include information of RLC PDUs or SDUs that are not correctly received.
- the receiving end in the embodiment of the present invention may periodically send a status report to the sending end according to a predetermined time interval, or may send a status report to the sending end after receiving the polling indication information sent by the sending end.
- the present invention can also set a predetermined condition in the receiving end in advance, so that after receiving the polling indication information sent by the transmitting end, the receiving end determines whether the predetermined condition is satisfied. If the receiving end determines that the predetermined condition is satisfied, triggering and generating a status report.
- the status report here contains the information of the data that has been correctly received. If the receiving end determines that the predetermined condition is not satisfied, the triggering and the generation of the status report are not performed. At this time, the receiving end may receive the next polling indication information. Then, the processing of the trigger status report is performed, and the receiving end may further determine whether the predetermined condition is satisfied, and until the predetermined condition is satisfied, the receiving end performs the processing of the trigger status report.
- the receiving end and the transmitting end can be controlled by using a timer, a counter, a sliding receiving window, and the like.
- the sending of the status report in order to avoid the phenomenon that the receiving end reports the air interface resource, the redundant retransmission status report, etc., the receiving end and the transmitting end can be controlled by using a timer, a counter, a sliding receiving window, and the like. The sending of the status report.
- the sending end sends the polling indication information in multiple manners, for example, the sending end sends the polling indication information to the receiving end according to a certain time interval, and the data stored by the sending end in the cache. When the amount reaches a certain amount, it sends a polling indication message to the receiving end, and so on.
- the transmitting end sends the polling indication information according to the amount of data stored in the cache, it avoids that the sender accumulates a large number of data blocks such as RLC PDUs or SDUs in the cache because the status report is not received for a long time.
- the transmission of the new data block is stopped, and the polling indication information is sent to the receiving end.
- the sender receives the status report based on the correct reception and deletes the delay. After the data block stored in the memory, the transmission process of the new data block can be restored, so that the amount of data stored in the buffer of the sender is effectively controlled.
- the sending end may separately send the polling indication information to the receiving end, that is, the sending end sends the polling indication information through the signaling specially set for the polling indication information; the sending end may also carry the polling indication information in the user.
- Data such as service PDU
- the sending end is sent to the receiving end; the sending end may also carry the polling indication information in the existing signaling and send it to the receiving end, where the signaling is physical layer control signaling, MAC layer control signaling, and the like.
- the content in the status report correctly received in the embodiment of the present invention may be: a maximum data block that is continuously received correctly, such as an RLC PDU or an SDU.
- the serial number can also be: Bitmap information of the receiving block receiving the data block.
- the transmitting end can determine the data block correctly received by the receiving end and the data block that is not correctly received by the receiving end by using the above sequence number or bitmap information.
- the transmitting end can not only receive the status report but also The data block stored in the sender buffer and correctly received by the receiver is deleted according to the information in the status report, and the retransmission process of the data block that is not correctly received may also be triggered.
- the transport layer, RLC is described in the following embodiment.
- the specific implementation process of the receiving end triggering according to the timer and generating the status report includes the following steps:
- Step 1 The receiving end establishes an RLC entity, and starts a first timer, and the first timer starts timing.
- the receiving end determines whether it receives the polling indication sent by the transmitting end, and whether the current timing of the timer reaches Max_Status_Duration
- step 3 the receiving end determines whether the current timing value of the timer is less than Min_Stat US _D U rati 0 n , if the current timing value of Timer_Status is less than Min_Status_Duration, then to step 5, the receiving end waits for Min_Status_Duration and Timer_Status
- the receiver triggers and generates a status report, such as receiving a type
- the status report fills in a status report, and the receiver sends the status report to the sender. At the same time, the receiver restarts the timer Timer_Status and the timer Timer_Status restarts.
- step 3 if the current timing value of Timer_Status is not less than Min_Status_Duration, then to step 4, the receiving end triggers and generates a status report. If the receiving end selects a status report filling method to generate a status report, the receiving end will state the status. The report is sent to the sender. At the same time, the receiver restarts the timer Timer_Status and the timer Timer_Status restarts.
- the specific implementation process of triggering and generating a status report at the receiving end ends.
- step 2 if the receiving end is always within the maximum time interval
- the polling indication sent by the sender is not received, that is, the current timing value of the timer Timer_Status reaches Max_Status_Duration
- step 4 the receiver triggers and generates a status report, such as receiving a type
- the status report fills in a status report, and the receiver sends the status report to the sender. At the same time, the receiver restarts the timer Timer_Status and the timer Timer_Status restarts.
- the specific implementation process of the receiving end triggering according to the counter and generating the status report includes the following steps:
- Step 1 The receiver establishes RLC
- the counter is incremented by one each time a new block is received at the receiving end.
- Min_R ev _Dat The maximum number of received data blocks that the receiver triggers and generates a status report is Ma X _R ev _Dat .
- step 2 the receiving end determines whether it receives the polling indication sent by the transmitting end, and the counter
- step 3 the receiving end determines whether the current count value of the counter Rev_Dat is less than Min_R ev _Dat
- the receiver After the difference between the number of Min_Rev_Dat and the current count value of Rev_Dat, the data is sent to step 4, the receiver triggers and generates a status report, such as the receiver selects a type.
- the status report filling method generates a status report, and the receiving end sends the status report to the sending end, and at the same time, the receiving end restarts the counter, counting
- the device restarts counting.
- the specific implementation process of triggering and generating a status report at the receiving end ends.
- step 3 if the current count value of Rev_Dat is not less than Min_Rev_Dat, the receiver triggers and generates a status report, such as the receiver selects a type
- the status report fills in a status report, and the receiver sends the status report to the sender. At the same time, the receiver restarts the counter Rev_Dat.
- step 2 if the number of new data blocks received by the receiver reaches Ma X _R ev _Dat
- step 4 the receiving end has not received the polling indication sent by the sending end, to step 4.
- step 4 the receiver triggers and generates a status report, such as receiving a type
- the status report fills in a status report, and the receiver sends the status report to the sender. At the same time, the receiver restarts Rev_Dat.
- Embodiment 3 the sender deletes the data stored in the cache
- the specific implementation process of sending a polling indication to the receiving end according to the timer includes the following steps:
- Step 1 The sender establishes an RLC entity and starts a timer. The timer starts timing.
- the time interval at which the sending end sends the polling indication information is the timer duration of the timer.
- the maximum number of data blocks stored in the sender buffer is a predetermined number.
- step 2 the sender judges whether the timer is
- the timeout the number of data blocks in the transmission window, that is, the number of data blocks in the sender's buffer, reaches a predetermined number. If the timer expires, regardless of whether the number of data blocks in the transmission window reaches a predetermined number, go to step 3.
- the sending end sends a polling indication to the receiving end, so that the receiving end sends a status report to it, and if the sending end detects that the timer Timer_Poll is timing, the transmitting end restarts the timer Timer_Poll, and the timer Timer_Poll restarts timing.
- the transmitting end continues to send a new data block to the receiving end.
- step 2 [55] In step 2
- step 4 Regardless of whether the timer expires or not, as long as the number of data blocks in the transmission window reaches a predetermined number, then step 4 is reached.
- the transmitting end suspends the transmission process of the new data block. Then, the transmitting end continues to determine whether the timer expires until the timer expires, and the sending end sends a polling indication to the receiving end, so that the receiving end sends a status report to the receiving end. The specific implementation process of sending the polling indication to the receiving end is terminated.
- the sending end deletes the data block that has been correctly received by the receiving end according to the content in the status report, for example, the data block between the two serial numbers in the status report indicates that the receiving end has been correctly received, at this time, the transmitting end Data blocks within the two serial numbers of their cache should be deleted. Data blocks other than the two sequence numbers indicate data blocks that have not been correctly received by the receiving end.
- the sender After deleting the buffered data block, the sender needs to detect whether the sending process of the new data block is suspended. If the sending process is suspended and the number of data blocks stored in the buffer is less than a predetermined number, the transmitting end restores the new one.
- the sender continues to send a new data block to the receiving end; if the sending process is suspended, and the data stored in the buffer If the number of blocks is not less than the predetermined number, the transmitting end does not resume the transmission process of the new data block; if the transmission process is not suspended, the transmitting end continues the transmission process of the new data block.
- Embodiment 4 the sender deletes the data stored in the cache
- the specific implementation process of sending a polling indication to the receiving end according to the counter includes the following steps:
- Step 1 the sender establishes RLC
- the sender increments one counter each time a data block is sent, and one counter is decremented by one for each data block deleted in the sender buffer.
- the sender determines whether the number of data blocks buffered reaches a predetermined maximum value and a predetermined alert value. If the predetermined maximum value is reached, regardless of whether the number of data blocks in the cache reaches a predetermined alert value, go to step 3.
- the transmitting end sends a polling indication to the receiving end, so that the receiving end sends a status report thereto, and at the same time, the counter continues to count the new data block sent by the transmitting end.
- the sender continues to send a new data block to the receiver.
- step 2 if the number of data blocks in the sender's buffer reaches the predetermined alert value, go to step 4.
- step 4 the sender hangs the transmission process of the new data block.
- the status report of the information the sending end deletes the data block that has been correctly received by the receiving end according to the content in the status report, for example, the data block between the two serial numbers in the status report indicates that the receiving end has been correctly received, at this time, the transmitting end
- the data block within the two serial numbers of its cache should be deleted.
- the counter value should be reduced by the corresponding amount.
- the data blocks other than the two sequence numbers in the status report indicate that the data blocks have not been correctly received by the receiving end.
- the transmitting end resumes the transmission process of the new data block, and the transmitting end continues to send the new data block to the receiving end; if the sending process is suspended, and the number of data blocks stored in the buffer is not less than the predetermined alert value , the transmitting end does not resume the transmission process of the new data block; if the sending process is not suspended, the transmitting end continues the transmission process of the new data block.
- the transmitting end may adopt Embodiment 3 and Embodiment 4
- HARQ can trigger ARQ retransmission, and ARQ can trigger ARQ itself.
- the two ARQ retransmissions triggered by different reasons affect each other. That is, the ARQ entity at the receiving end does not know whether the missing PDU has been triggered by the HARQ. If the ARQ entity triggers the status report for the missing PDU, Causes redundant retransmission of data blocks.
- the error probability is very low. Therefore, the sender does not need to add an additional mechanism for detection.
- the receiving end there is a timer-controlled reception status report, and then the missing SN
- Method 2 Use a timer to control redundant ARQ retransmission of data blocks.
- the status report but its trigger is controlled by a timer, and the validity of this status report is guaranteed for a predetermined period of time.
- This timer needs to be the timer of the receiver itself, Timer-Status.
- the timer Timer_MisPDU starts timing.
- the sequence number of the data block that is received by the receiving end is not consecutive.
- the first timer is the timeout state of the two timers Timer-Status, if the receiving end
- Timeout that is, when the receiver needs to send a status report, or the timer Timer_Status
- the receiving end triggers and generates a status report.
- the contents of the status report mainly include:
- the SN of the data block is smaller than the missing data block number N
- the embodiment of the present invention does not exclude the case where the receiving end reports the missing data block sequence number in the status report, and does not exclude the case where the correctly received data block and the missing data block sequence number are reported.
- step 2 if the timer Timer_Status expires or resets, the timer Timer_MisPDU has not timed out until the timer Timer_MisPDU times out, to step 4
- the receiver triggers and generates a status report.
- the contents of the status report mainly include:
- the slave PDU is N
- the receipt of the identified missing data block begins with the reception of those data blocks between the next discrete data block.
- the receiver then sends the status report to the sender.
- Receiver restart timer Timer_Status.
- the receiver stops the timer Timer_MisPDU.
- step 2 if the timer Timer_MisPDU times out before the Timer_Status expires or resets, go to step 5.
- the receiving end triggers and generates a status report.
- the content in the status report mainly includes: the receiving status of all the data blocks before the next lost data block number, where the next missing data block number is: PDU SN is N The next missing block number after the identified missing block.
- the receiver then sends a status report to the sender.
- the receiver restarts the timer Timer_Status.
- the receiver stops the timer Timer_MisPDU.
- step 3 If the timeout occurs, the content of the status report in step 3 is: The sequence number is 1, 2
- step 4 The reception of the data block. If the timer Timer_Status controlled by the receiving RLC entity times out first, then when the timer Timer_MisPDU times out, step 4
- the contents of the status report are: Serial number 3, 4, 5, 6, 7
- the entity-controlled timer Timer_Status expires, then the content of the status report in step 5 is: The reception of the data block of sequence number 1, 2, 3, 4, 5, 6, and 7.
- the timer duration of the timer Timer_MisPDU ⁇ the timer duration of the timer Timer_Status.
- the receiver can be based on the Timer_MisPDU.
- a status report is triggered each time a lost data block is detected.
- Method 3 When the HARQ of the receiving end triggers the corresponding status report, the status report records the HARQ TB arrival time and other information, and the HARQ of the receiving end will be HARQ TB.
- the ARQ entity is notified to the receiving end, and the ARQ entity determines whether the sequence number of the missing PDU/SDU is SN according to the received HARQ TB arrival time and other information.
- Method 4 The problem of redundant retransmission is solved by the sender.
- the receiver triggers and generates a status
- the sender limits the retransmission process of the data block, that is, the sender cannot continuously perform the same PDU.
- This control can be done by a timer or counter. That is to say, the transmitting end does not retransmit the same data block within a predetermined time interval, or in the predetermined number of retransmitted data blocks, the same data block cannot be retransmitted.
- the system for transmitting layer retransmission includes: a sending end and a receiving end, wherein the sending end is provided with a deleting module and a polling module, and the receiving end is provided with a sending module.
- the polling module in the sender is mainly used to send polling indication information to the receiver.
- the polling module may periodically send polling indication information to the receiving end according to a predetermined time interval, or may send polling indication information to the receiving end when the number of data blocks in the sending window exceeds a predetermined value. Specifically as described in the above method
- the sending module of the receiving end is mainly configured to receive the polling indication information at the receiving end, and after the predetermined condition is satisfied, generate a control message, and transmit the control message to the sending end.
- the deleting module in the sending end can delete the data block stored in the sending end buffer and correctly received by the receiving end according to the control message received by the sending end.
- the sending module of the receiving end can control the sending of the status report by using a timer, a counter, a sliding receiving window, etc., to avoid the phenomenon that the receiving end reports the air status resource too frequently, which is as in the above method. description.
- the sending end deletes the buffered data block that has been correctly received by the receiving end by using the display signaling sent by the receiving end, thereby avoiding the loss of transmission and reception between the transmitting end and the receiving end.
- the phenomenon of steps therefore, avoids the phenomenon of data loss; the transmitting end and the receiving end control the transmission of the status report by using a timer, a counter, a sliding receiving window, etc., thereby avoiding the wasteful transmission of the status report by the receiving end and wasted
- the phenomenon of the air interface resource enables the data block stored in the buffer of the sender to be correctly received by the receiver to be deleted in time, thereby avoiding the phenomenon that the data storage in the sender cache is excessive and the storage resources of the sender are wasted;
- the way to solve the low-level retransmission of the transport layer The HARQ-triggered retransmission and the transport layer high-level retransmission conflicts between the ARQ retransmissions triggered by the ARQ's own error detection, so that the status report is not repeatedly transmitted, and the status report and the redundant retransmission of the data block are avoided; Embodiments of the invention also avoid ignoring DTX false positives ACK
- the technical solution provided by the present invention realizes the transmission layer retransmission in the mobile access network system that provides system transmission reliability, improves air interface resource utilization, improves transmission buffer utilization, and improves evolution.
- the purpose of the realization process is to realize the transmission layer retransmission in the mobile access network system that provides system transmission reliability, improves air interface resource utilization, improves transmission buffer utilization, and improves evolution.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
L'invention concerne un procédé est un système de retransmission sur couche de transport, où un récepteur émet l'information de blocs de données reçue avec précision vers un émetteur par le biais d'un message de commande dans un système réseau d'accès mobile en évolution; l'émetteur efface, selon le message de commandes reçues, les blocs de données mémorisées dans sa mémoire tampon et reçus avec succès par le récepteur. L'émetteur peut émettre une information d'indication d'invitation à émettre au récepteur qui génère à son tour un message de commandes et le transmet à l'émetteur après réception de l'information d'indication d'invitation à émettre, une fois que la condition prédéterminée est remplie.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2006100944263A CN101047484B (zh) | 2006-06-21 | 2006-06-21 | 一种传输层重传方法和系统 |
CN200610094426.3 | 2006-06-21 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008000181A1 true WO2008000181A1 (fr) | 2008-01-03 |
Family
ID=38771746
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2007/070140 WO2008000181A1 (fr) | 2006-06-21 | 2007-06-20 | Procédés et systèmes de retransmission sur couche de transport |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101047484B (fr) |
WO (1) | WO2008000181A1 (fr) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110167146A (zh) * | 2018-02-12 | 2019-08-23 | 维沃移动通信有限公司 | 一种sdu的处理方法和通信设备 |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8341485B2 (en) * | 2010-09-14 | 2012-12-25 | Intel Corporation | Increasing hybrid automatic repeat request (HARQ) throughput |
CN103023625B (zh) * | 2011-09-21 | 2017-09-19 | 中兴通讯股份有限公司 | 触发构造自动重传请求状态报告的方法及装置 |
CN102917127B (zh) * | 2012-10-15 | 2014-07-16 | 北京推博信息技术有限公司 | 一种音频传输方法及系统 |
CN103944691B (zh) * | 2013-01-17 | 2019-01-15 | 中兴通讯股份有限公司 | 一种协同业务传输中的数据重传方法及接入网网关 |
WO2014205720A1 (fr) * | 2013-06-27 | 2014-12-31 | 华为技术有限公司 | Procédé et appareil d'émission de données |
CN104639298B (zh) * | 2013-11-08 | 2019-11-22 | 腾讯科技(深圳)有限公司 | 一种数据传输方法、装置及系统 |
CN105846968A (zh) * | 2015-01-14 | 2016-08-10 | 中兴通讯股份有限公司 | 一种实现重传的方法和装置、发送设备和接收设备 |
CN105245317A (zh) * | 2015-10-20 | 2016-01-13 | 北京小鸟听听科技有限公司 | 一种数据传输方法、发送端、接收端和数据传输系统 |
CN108476097B (zh) * | 2016-09-18 | 2021-08-03 | 深圳市大疆创新科技有限公司 | 数据重传方法和装置 |
CN107920095A (zh) * | 2016-10-08 | 2018-04-17 | 阿里巴巴集团控股有限公司 | 一种在p2p环境下发送方以及接收方流量限制的方法、装置 |
CN106888428B (zh) * | 2017-03-27 | 2020-02-11 | 北京大学 | 基于蓝牙的智能终端与医疗可穿戴设备间的数据传输方法 |
CN107168663A (zh) * | 2017-03-30 | 2017-09-15 | 联想(北京)有限公司 | 信息处理方法及电子设备 |
CN109391376B (zh) * | 2017-08-09 | 2020-12-01 | 华为技术有限公司 | 状态报告的发送方法、设备及系统 |
CN109428684B (zh) * | 2017-08-30 | 2020-11-27 | 中国移动通信有限公司研究院 | 一种数据传输方法、rlc实体及pdcp实体 |
CN110099448B (zh) * | 2018-01-31 | 2023-01-13 | 华为技术有限公司 | 通信的方法和装置 |
KR20210122824A (ko) * | 2019-02-15 | 2021-10-12 | 소니그룹주식회사 | 편광 보고를 위한 방법들, 관련된 무선 디바이스들 및 관련된 네트워크 노드들 |
CN111180031B (zh) * | 2019-12-31 | 2023-07-28 | 贵州精准健康数据有限公司 | 数据管理系统及方法 |
CN112291047A (zh) * | 2020-11-16 | 2021-01-29 | 北京升哲科技有限公司 | 传输确认方法、装置、设备及存储介质 |
CN113286000A (zh) * | 2021-05-21 | 2021-08-20 | 国网河北省电力有限公司 | 应用在电力单向传输系统中的数据收发方法及装置 |
CN113452486B (zh) * | 2021-08-31 | 2021-11-23 | 腾讯科技(深圳)有限公司 | 车辆信息的上传方法、装置、设备和存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1149919A (zh) * | 1995-03-30 | 1997-05-14 | 摩托罗拉公司 | 利用多次重发定时器经不可靠通信信道的远程过程调用的方法和系统 |
CN1339749A (zh) * | 2000-08-18 | 2002-03-13 | 清华大学 | 一种将tcp用于不可靠传输网络的局域重传方法 |
CN1390017A (zh) * | 2002-07-24 | 2003-01-08 | 清华大学 | 提高信元传输可靠性的网络传输方法和通信实现系统 |
CN1414761A (zh) * | 2002-02-27 | 2003-04-30 | 华为技术有限公司 | 通信系统中多优先级缓冲可靠传输方法 |
CN1533083A (zh) * | 2003-03-25 | 2004-09-29 | 株式会社Ntt都科摩 | 通信设备,传输控制方法,和程序产品 |
-
2006
- 2006-06-21 CN CN2006100944263A patent/CN101047484B/zh not_active Expired - Fee Related
-
2007
- 2007-06-20 WO PCT/CN2007/070140 patent/WO2008000181A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1149919A (zh) * | 1995-03-30 | 1997-05-14 | 摩托罗拉公司 | 利用多次重发定时器经不可靠通信信道的远程过程调用的方法和系统 |
CN1339749A (zh) * | 2000-08-18 | 2002-03-13 | 清华大学 | 一种将tcp用于不可靠传输网络的局域重传方法 |
CN1414761A (zh) * | 2002-02-27 | 2003-04-30 | 华为技术有限公司 | 通信系统中多优先级缓冲可靠传输方法 |
CN1390017A (zh) * | 2002-07-24 | 2003-01-08 | 清华大学 | 提高信元传输可靠性的网络传输方法和通信实现系统 |
CN1533083A (zh) * | 2003-03-25 | 2004-09-29 | 株式会社Ntt都科摩 | 通信设备,传输控制方法,和程序产品 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110167146A (zh) * | 2018-02-12 | 2019-08-23 | 维沃移动通信有限公司 | 一种sdu的处理方法和通信设备 |
Also Published As
Publication number | Publication date |
---|---|
CN101047484B (zh) | 2010-10-13 |
CN101047484A (zh) | 2007-10-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2008000181A1 (fr) | Procédés et systèmes de retransmission sur couche de transport | |
JP5357295B2 (ja) | 無線通信システムにおけるエラー制御メッセージを処理するための方法及び装置 | |
JP6419245B2 (ja) | 通信システムにおける方法および装置 | |
EP1169804B1 (fr) | Protocole de commande de liaison radio flexible | |
US5432798A (en) | Data communication method and system | |
US8989059B2 (en) | Method for triggering a status report of automatic repeat request | |
CN103138905B (zh) | Rlc数据包传输的确认方法及rlc am实体发送方 | |
JP5390022B2 (ja) | ステータスレポートのトリガー方法及び装置 | |
EP3580873B1 (fr) | Technique de surveillance d'une radiocommunication | |
EP2611057A1 (fr) | Système de communication mobile et dispositif de station mobile | |
CN101217350B (zh) | 协议数据单元的检测上报方法、系统及接收端 | |
WO2010069206A1 (fr) | Procédé de transmission pour rapport d'état de message dans la couche de commande de liaison radio, et système correspondant | |
US8738984B2 (en) | Apparatus for processing retransmission failure in radio link control (RLC) layer | |
WO2008034374A1 (fr) | Procédé, système et appareil de transmission de commande de liaison radio | |
CN107800515A (zh) | 一种用于无线链路层的数据传输方法和系统 | |
WO2006021159A1 (fr) | Procede de commande de frequence de transmission de rapports de statut | |
JPH10190635A (ja) | 誤り再送を行う通信システム、その通信制御装置および誤り再送方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07721759 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07721759 Country of ref document: EP Kind code of ref document: A1 |