CN1977497A - Lossless radio link control entity (RLC) re-establishment avoiding service data unit (SDU) duplication - Google Patents
Lossless radio link control entity (RLC) re-establishment avoiding service data unit (SDU) duplication Download PDFInfo
- Publication number
- CN1977497A CN1977497A CNA2004800429810A CN200480042981A CN1977497A CN 1977497 A CN1977497 A CN 1977497A CN A2004800429810 A CNA2004800429810 A CN A2004800429810A CN 200480042981 A CN200480042981 A CN 200480042981A CN 1977497 A CN1977497 A CN 1977497A
- Authority
- CN
- China
- Prior art keywords
- rlc
- sdu
- node
- peer node
- sequence
- 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
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/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1832—Details of sliding window management
-
- 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/187—Details of sliding window management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
- Gyroscopes (AREA)
- Crystals, And After-Treatments Of Crystals (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
- Communication Control (AREA)
Abstract
A node implementing an RLC (Radio Link Control) entity and being for use in a mobile communications system transmits a sequence of RLC SDUs (SDU = Service Data Unit) towards a peer node. As a result of re-establishment of an RLC entity not all SDUs may have been received. The peer notifies the node which is the next SDU that the peer expects to receive (by transmitting the next SDU number to the node). The node resumes transmission from that SDU onwards. This may or may not lead to re-transmission of SDUs transmitted before the RLC re-establishment. As an alternative, the peer does not notify the node of the next SDU that it expects to receive, but instead the node retransmits any unacknowledged SDUs, together with the SDU number of the first retransmitted SDU. The peer then discards any duplicate SDUs. Both variants enable lossless data transfer wbilst avoiding duplication.
Description
The present invention relates to mobile communication, particularly the RLC (Radio Link control) that for example needs because RLC PDU (control of RLC=Radio Link, PDU=protocol Data Unit) length changes rebuilds.
In the past, once do not need to change PDU length especially.Yet, occurred recently for the needs that change PDU length.For example, the maximum throughput on HS-DSCH (high speed descending sharing channel) is subjected to the restriction of RLC PDU length.Utilization bigger PDU length on HS-DSCH can improve throughput.Yet, when switching to normal DCH (dedicated channel) or FACH (forward access channel), will preferably use the RLC PDU length of 320 bits that use now.
Similar situation may take place for current enhanced uplink by 3GPP (third generation partner plan) exploitation, use the PDU length littler (the RLC PDU of 320 bits has provided the minimum data rates of the 160kbit/s with the 2ms Transmission Time Interval that is considered to be used for enhanced uplink, and this may cause the coverage deficiency) although replace expectation in this case in order to have bigger coverage than standard 320 bits.
Therefore, for ongoing connection the needs of RLC PDU length have appearred changing, especially when switching between HS-DSCH, DCH (or FACH) and enhancing special uplink channel.
According to 3GPP R-99/4/5, for ongoing connection, promptly for existing radio bearer, RLCPDU length can be reconfigured.When being reconfigured, PDU length rebuilds rlc protocol.
The inventor has realized that the program of current use may cause loss of data.
When reconfiguring RLC PDU length with R-99/4/5, because only can have a PDU length at AM RLC preset time (AM=answer-mode), so be reconstituted in the RLC entity (or a plurality of RLC entity) among UE (subscriber equipment, for example mobile phone) and the RNC (radio network controller).The RLC sequence number is started from scratch after rebuilding.
The inventor has realized that and has occurred and the relevant problem of those RLC PDU that had sent before rebuilding but also be not identified.Because transmitter is not also received any ACK (affirmation) for these PDU, whether in peer-entities, be not received (SDU=service data unit) so know the SDU that in PDU, comprises.
About the relation between SDU and the PDU, will recognize from higher level to receive SDU.The length of SDU may change, yet all PDU have identical length (although can change the length of PDU, then having changed length for all PDU).RLC is with the SDU segmentation and/or be cascaded into PDU, and PDU sends by aerial just, even in this manual the SDU of transmission/reception has been carried out reference.If sent/received all PDU of the segmentation that comprises that SDU, then can think to send/received this SDU.
Transmitter can be segmented into unacknowledged SDU new PDU (having zero-based SN (sequence number)) again.This will mean that in fact received those SDU before rebuilding (but also not being identified) have been received twice in peer-entities, thereby cause the reception of duplicating of SDU.Selectively, transmitter can abandon unacknowledged SDU (supposing that in fact they are received before rebuilding) and they do not retransmitted after rebuilding.This will be avoided SDU anyly duplicates reception, can cause loss of data (if before rebuilding all received words of not all unacknowledged SDU) but replace.
In other words, can not when rebuilding, RLC guarantee simultaneously also that so far lossless data transmits and duplicating of SDU avoided.
Note, in the system of current enforcement, when rebuilding, be discarded in any unacknowledged RLC PDU in transmitter and the receiver, promptly have the risk of obliterated data.
The purpose of preferred embodiment at least of the present invention is to overcome this problem.
In first aspect, the invention provides a kind of method of implementing the RLC entity and being used for the node of mobile communication system of operating, this method comprises:
Send the sequence of RLC SDU to peer node; And
Result as the reconstruction of RLC entity:
Receive request from peer node at least one the RLC SDU that retransmits described sequence; And
Retransmit described at least one RLC SDU of described sequence to peer node.
This first aspect relates to the function that sends the node (for example RNC or UE) of SDU to peer node (for example another among RNC and the UE), and promptly it relates generally to " transmitting terminal " of the combination of node/peer node.
In the preferred embodiment of this aspect, node receives the request that counterweight is returned not a SDU who is received by peer node from peer node, and node is retransmitted this SDU and any follow-up SDU then.
In an embodiment of the present invention, peer node checks which SDU is the next SDU that will send.May be received by all SDU that node sends, in this case without any need for repeating transmission by peer node.In this case, the next SDU that send is the SDU that node does not also have transmission, so in this case, (not retransmitting SDU) continues to send simply after rebuilding.Just, when node when peer node receives request to next SDU, whether any SDU that has sent needs retransmitted in the node inspection.
In closely-related second aspect, the invention provides a kind of method of implementing the RLC entity and being used for the node of mobile communication system of operating, this method comprises:
Receive the sequence of RLC SDU from peer node; And
Result as the reconstruction of RLC entity:
The request peer node is retransmitted at least one RLC SDU of described sequence; And
Receive the RLC SDU of described at least one repeating transmission from peer node.
Second aspect relates to the function that receives the node (for example RNC or UE) of SDU from peer node (for example another RNC and the UE), and promptly it relates to " receiving terminal " of the combination of node/peer node, and therefore can be counted as replenishing of first aspect.
In the preferred embodiment of this aspect, node sends the request of the SDU that request repeat also do not receive by node to peer node, and peer node is retransmitted this SDU and any follow-up SDU then.
The present invention also provides the combination of first and second aspects, must be exchanged in an aspect therein although will be understood that term " node " and " peer node ".In other words, the function of " transmitting terminal " and " receiving terminal " has been described in this combination.
When sending/receive according to first and second aspects when retransmitting the request of one or more SDU, similar possible be that " transmitting terminal " retransmits all unacknowledged SDU and allow " receiving terminal " to know to have retransmitted which SDU.Then " receiving terminal " can be discerned any SDU that duplicates and abandon them.
Therefore, with first and second aspect the closely-related third aspect, the invention provides a kind of method of implementing the RLC entity and being used for the node of mobile communication system of operating, this method comprises:
Send the sequence of RLC SDU to peer node; And
Result as the reconstruction of RLC entity:
Identification nodes is not also received at least one RLC SDU of affirmation;
Retransmit described at least one RLC SDU to peer node; And
Send the sign of at least one just retransmitted RLC SDU to peer node.
Once more, the third aspect relates to the function that sends the node (for example RNC or UE) of SDU to peer node (for example among RNC and the UE another), and promptly it relates generally to " transmitting terminal " of the combination of node/peer node.
In the preferred embodiment of this aspect, any unacknowledged SDU of node identification and retransmit them.
It also notifies peer node retransmitting which SDU, so that peer node can abandon any SDU that duplicates.
Fourth aspect (it can be counted as replenishing of the third aspect), the invention provides a kind of method of implementing the RLC entity and being used for the node of mobile communication system of operating, this method comprises:
Receive the sequence of RLC SDU from peer node; And
Result as the reconstruction of RLC entity:
Receive the RLC SDU of at least one repeating transmission of described sequence from peer node; And
Receive the sign of at least one just retransmitted RLC SDU from peer node.
Once more, fourth aspect relates to the function that receives the node (for example RNC or UE) of SDU from peer node (for example another RNC and the UE), and promptly it relates to " receiving terminal " of the combination of node/peer node.
In the preferred embodiment of this aspect, the sign (peer node is designated it unconfirmed) of the SDU that node receive to be retransmitted from peer node and the SDU of repeating transmission is so that node can abandon any SDU that duplicates.
The present invention also provides the combination of third and fourth aspect, must be exchanged once more in an aspect therein although will be understood that term " node " and " peer node ".In other words, the function of " transmitting terminal " and " receiving terminal " has also been described in this combination.
Stated preferable feature in the dependent claims.The device aspect corresponding with method disclosed herein aspect also is provided, and vice versa.
Only also preferred embodiments more of the present invention are described with reference to the accompanying drawings now by example, wherein:
Single description of drawings according to the feature of the method for the embodiment of the invention.
According to embodiments of the invention, imagination SDU with sequence number (SDU number), preferably number by PDCP (packet data convergence protocol) sequence number.The counter that transmitter and receiver all keep the SDU for each transmission and reception to increase progressively.In case the counter in transmitter and receiver by synchronously, does not just need to send sequence number.
Referring now to accompanying drawing first embodiment is described.At first will consider downlink transfer, promptly send SDU to UE from RNC.Therefore, the left part of accompanying drawing illustrates the SDU that is sent by (will by) RNC, and the right part of accompanying drawing illustrates the SDU that is received by (will by) UE.RNC is to the SDU numbering of each transmission, and UE is to the SDU numbering of each reception.These are illustrated in the accompanying drawings.The frame table of each numbering shows a PDU among the figure.In this example, several PDU are gathered to form a SDU, and still in fact segmentation, a complete SDU or the several SDU of a SDU can be included among the PDU, and this depends on the length of SDU and PDU.Frame table with asterisk (*) mark shows the PDU that is sent out/receives, and does not have the frame table of asterisk to show also the PDU that is not sent out/receives.When having received all PDU of the segmentation that comprises SDU, the SDU that just thought transmission (reception).
In this example, sent PDU 10 to 17.In the PDU that sends, do not receive PDU 13.Transmitter received for up to the affirmation of the PDU that comprises PDU 9.Because receiver has received all PDU (PDU 10-12) of the segmentation that comprises SDU 4, so that SDU 4 has been sent to is more high-rise.
At first consider situation about transmitting according to the order of sequence by receiver.Though SDU 6 is intactly received, owing to also there be not (intactly) to receive SDU 5, so that it is not sent to is more high-rise.
When (for example needing owing to PDU length changes) rebuild in the RNC request, it will begin to send from which SDU number after reconstruction to the UE indication for it.In reconfiguring message, particularly RRC (Radio Resource control) reconfigures message (for example radio bearer reconfigures message), and this can finish easily.This message comprises and is set to 4 SN, so that rebuild first SDU that back RNC will send to UE indication SDU 4.
If the SDU that comprises in message number has received and has sent to more high-rise SDU number less than UE, so UE just know a plurality of SDU that after reconstruction, send be duplicate and should be left in the basket.In this example, RNC segmentation SDU 4 and forward in PDU again after reconstruction with the zero-based new PDU length of RLC sequence number.Because UE know it received SDU 4 and it is sent to more high-rise, so it can abandon this SDU that receives as the result who retransmits.
On the other hand, be higher than the SDU that is sent to the highest more high-rise SDU number with not abandoning any that receive as the result who retransmits and SN.For SDU 5 and forward and the describing love affairs condition is such.By this way, can realize simultaneously that lossless data transmits and copy detection/duplicate and avoid.
In modification, if configuration does not transmit according to the order of sequence, so because SDU 6 is intactly received, so SDU 6 may be transmitted to more high-rise when rebuilding.In this case, one receives after reconstruction, and UE also will abandon this SDU.In order to make UE can accomplish this point, to it provide storage (recently) send more high-rise SDU number memory device to.
Under the situation of up link, the situation of function and down link is similar: (RRC reconfigures full message to UE reconfiguring full message, for example radio bearer reconfigures full message) in comprise SDU number that will begin SDU that (again) send after the reconstruction, and be performed with the downlink scenario corresponding step.
Attention is not having under the situation of the present invention, and UE will not know that the SDU 4 that sends is copies of the SDU that received after reconstruction, and therefore with it to twice of more high-rise transmission.
Now second embodiment will be described with reference to the accompanying drawings still.When transmitter in first embodiment is retransmitted any unacknowledged SDU and send SDU number (being SDU4 in this example) of first SDU that its retransmits, possible according to second embodiment is that receiver should begin (again) transmission forward from which SDU to the transmitter indication.Receiver will check whether receive until have all SDU of the highest SDU number SDU.If do not receive until and comprise and will asks all SDU of the SDU of high numbering, receiver never the SDU of the lowest number of reception sends forward.In this example, receiver will should send forward from SDU 5 to the transmitter indication.(RNC is a transmitter for the situation of down link, UE is a receiver), this indication can be contained in and reconfigures in the full message, and (UE is a transmitter for the situation of up link, RNC is a receiver), this indication can be contained in and reconfigures in the message.
If SDU 5 has been received by UE on the other hand, UE just will ask to begin forward to send from SDU 7, therefore will be less than retransmitting in this situation.
In other words, in this embodiment, receiver is to transmitter indication first SDU that the receiver expectation receives after reconstruction.Transmitter continues forward to send from that SDU after reconstruction then.This may cause or may not cause retransmitting any SDU that has sent.
According to these two embodiment, might change RLC PDU length (perhaps because other reason is rebuild RLC, for example as the result of rlc protocol mistake, such as the RLC irrecoverable error), keep lossless data to transmit simultaneously and duplicate and avoid.
Note, top embodiment relate to occur in RNC and with UE that RNC is associated between process, i.e. the process of being controlled by single RNC.
Also note, may not mean quoting of " reconstruction of RLC entity " and must rebuild complete RLC entity.The length of PDU might be for example only changed, the sender side of RNC and the receiver-side of UE may be only rebuild in this case for down link.
Though preferred embodiment has been described the present invention as described above, should be appreciated that these embodiment only are illustrative, and claims are not limited to these embodiment.In view of the disclosure, those skilled in the art can make the modification in the scope that is considered to fall into appended claims and substitute.Each feature disclosed in this manual or explanation can be in the present invention combined, no matter be individually or with any suitable combination of any further feature of or explanation disclosed at this.
Claims (40)
1, a kind of operation is implemented RLC (Radio Link control) entity and is used for the method for the node of mobile communication system, and this method comprises:
Send the sequence of RLC SDU (control of RLC=Radio Link, SDU=service data unit) to peer node; And
Result as the reconstruction of RLC entity:
Receive request from peer node at least one the RLC SDU that retransmits described sequence; And
Retransmit described at least one RLC SDU of described sequence to peer node.
2, method according to claim 1 wherein needs the RLC reconstruction because RLC PDU (control of RLC=Radio Link, PDU=protocol Data Unit) length changes.
3, method according to claim 1 is wherein rebuild owing to the rlc protocol mistake needs RLC.
4, according to any one described method in the claim 1 to 3, wherein said request comprises the SDU sequence number of described at least one RLC SDU of described sequence, and which (which) RLC SDU node discerned based on described SDU sequence number and needed retransmitted.
5, method according to claim 4, wherein node is retransmitted all RLC SDU after its SDU sequence number is included in that RLC SDU in the described request and that comprise that RLC SDU.
6, according to any one described method in the claim 1 to 5, wherein node comprises RNC (radio network controller), and peer node comprises UE (subscriber equipment).
7, method according to claim 6 wherein reconfigures at RRC (Radio Resource control) and receives described request in the full message.
8, according to any one described method in the claim 1 to 5, wherein node comprises UE, and peer node comprises RNC.
9, method according to claim 8 wherein reconfigures at RRC and receives described request in the message.
10, a kind of method of implementing the RLC entity and being used for the node of mobile communication system of operating, this method comprises:
Receive the sequence of RLC SDU from peer node; And
Result as the reconstruction of RLC entity:
The request peer node is retransmitted at least one RLC SDU of described sequence; And
Receive the RLC SDU of described at least one repeating transmission from peer node.
11, method according to claim 10 wherein needs RLC to rebuild owing to RLC PDU length changes.
12, method according to claim 10 is wherein rebuild owing to the rlc protocol mistake needs RLC.
13, according to any one described method in the claim 10 to 12, first RLC SDU that further comprises definite described sequence that does not also receive, at least one the RLC SDU that wherein asks peer node to retransmit described sequence comprise first RLC SDU of the described sequence that the repeating transmission of request peer node does not also receive.
14,, further comprise being discarded in the RLC SDU that retransmits those repeating transmission of having received before according to any one described method in the claim 10 to 13.
15,, further comprise abandoning the RLC SDU that is transmitted to those more high-rise repeating transmission according to any one described method in the claim 10 to 13.
16, according to any one described method in the claim 10 to 15, wherein node comprises RNC, and peer node comprises UE.
17, method according to claim 16 wherein reconfigures at RRC and sends described request in the message.
18, according to any one described method in the claim 10 to 15, wherein node comprises UE, and peer node comprises RNC.
19, method according to claim 18 wherein reconfigures at RRC and sends described request in the full message.
20, a kind of method comprises:
The method that combines with method according to claim 6 or 7 according to claim 18 or 19; Perhaps
Combine with method according to claim 16 or 17 according to Claim 8 or 9 method.
21, a kind of method of implementing the RLC entity and being used for the node of mobile communication system of operating, this method comprises:
Send the sequence of RLC SDU to peer node; And
Result as the reconstruction of RLC entity:
Identification nodes is not also received at least one RLC SDU of affirmation;
Retransmit described at least one RLC SDU to peer node; And
Send the sign of at least one just retransmitted RLC SDU to peer node.
22, method according to claim 21 wherein needs RLC to rebuild owing to RLC PDU length changes.
23, method according to claim 21 is wherein rebuild owing to the rlc protocol mistake needs RLC.
24, according to any one described method in the claim 21 to 23, wherein send described sign and comprise the SDU sequence number that sends described at least one RLC SDU to peer node, peer node can use the SDU sequence number to determine whether the RLC SDU of described at least one repeating transmission has been received device and has received as the transmission result of RLCSDU sequence thus.
25, method according to claim 24, wherein said sign comprise the SDU sequence number of the RLCSDU of first repeating transmission.
26, according to any one described method in the claim 21 to 25, wherein node comprises RNC, and peer node comprises UE.
27, method according to claim 26 wherein reconfigures at RRC and sends described sign in the message.
28, according to any one described method in the claim 21 to 25, wherein node comprises UE, and peer node comprises RNC.
29, method according to claim 28 wherein reconfigures at RRC and sends described sign in the full message.
30, a kind of method of implementing the RLC entity and being used for the node of mobile communication system of operating, this method comprises:
Receive the sequence of RLC SDU from peer node; And
Result as the reconstruction of RLC entity:
Receive the RLC SDU of at least one repeating transmission of described sequence from peer node; And
Receive the sign of at least one just retransmitted RLC SDU from peer node.
31, method according to claim 30 wherein needs RLC to rebuild owing to RLC PDU length changes.
32, method according to claim 30 is wherein rebuild owing to the rlc protocol mistake needs RLC.
33,, comprise that further whether the RLC SDU that uses the SDU sequence number to determine described at least one repeating transmission is received as the transmission result of RLC SDU sequence by node according to any one described method in the claim 30 to 32.
34,, further comprise being discarded in the RLC SDU that retransmits those repeating transmission of having received before according to any one described method in the claim 30 to 33.
35,, further comprise abandoning the RLC SDU that is transmitted to those more high-rise repeating transmission according to any one described method in claim 30 or 33.
36, according to any one described method in the claim 30 to 35, wherein node comprises RNC, and peer node comprises UE.
37, method according to claim 36 wherein reconfigures at RRC and receives described sign in the full message.
38, according to any one described method in the claim 30 to 35, wherein node comprises UE, and peer node comprises RNC.
39,, wherein reconfigure and receive described sign in the message at RRC according to the described method of claim 38.
40, a kind of method comprises:
The method that combines with method according to claim 26 or 27 according to claim 38 or 39; Perhaps
The method that combines with method according to claim 28 or 29 according to claim 36 or 37.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/EP2004/050737 WO2005109778A1 (en) | 2004-05-07 | 2004-05-07 | Lossless radio link control entity (rlc) re-establishment avoiding service data unit (sdu) duplication |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1977497A true CN1977497A (en) | 2007-06-06 |
| CN1977497B CN1977497B (en) | 2010-05-12 |
Family
ID=34957663
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2004800429810A Expired - Fee Related CN1977497B (en) | 2004-05-07 | 2004-05-07 | Lossless radio link control entity (RLC) re-establishment avoiding service data unit (SDU) duplication |
Country Status (8)
| Country | Link |
|---|---|
| US (1) | US7881204B2 (en) |
| EP (1) | EP1751928B1 (en) |
| CN (1) | CN1977497B (en) |
| AT (1) | ATE500670T1 (en) |
| AU (1) | AU2004319437B2 (en) |
| DE (1) | DE602004031676D1 (en) |
| TW (1) | TWI367042B (en) |
| WO (1) | WO2005109778A1 (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010142122A1 (en) * | 2009-06-12 | 2010-12-16 | 中兴通讯股份有限公司 | Radio link data transmission method and radio communication network node |
| CN101933280A (en) * | 2008-02-01 | 2010-12-29 | Lg电子株式会社 | Be used to send the mobile communication system and the method for PDCP status report |
| US8396037B2 (en) | 2008-06-23 | 2013-03-12 | Htc Corporation | Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof |
| WO2015123883A1 (en) * | 2014-02-24 | 2015-08-27 | Qualcomm Incorporated | Radio link control entity re-establishment |
| CN106470497A (en) * | 2015-08-17 | 2017-03-01 | 中国移动通信集团公司 | A kind of data transmission method, wireless spread-spectrum technology send and receiving entity |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006203265A (en) * | 2004-12-24 | 2006-08-03 | Ntt Docomo Inc | Receiver, transmitter, communication system and method |
| US8379646B2 (en) * | 2006-07-31 | 2013-02-19 | Lg Electronics Inc. | Method of processing control information in a mobile communication system |
| US7979767B2 (en) * | 2007-02-09 | 2011-07-12 | Motorola Mobility, Inc. | Automatic repeat request (ARQ) reset method |
| US8031689B2 (en) | 2007-05-18 | 2011-10-04 | Innovative Sonic Limited | Method and related apparatus for handling re-establishment of radio link control entity in a wireless communications system |
| CA2718083A1 (en) * | 2008-03-21 | 2009-09-24 | Nokia Corporation | Re-establishment of a rlc entity |
| US8509180B2 (en) | 2008-05-02 | 2013-08-13 | Qualcomm Incorporated | Method and apparatus for efficient handover in LTE |
| WO2010016150A1 (en) * | 2008-08-08 | 2010-02-11 | 富士通株式会社 | Wireless device, communication method, and communication program |
| US9119190B2 (en) | 2012-08-06 | 2015-08-25 | Qualcomm Incorporated | Method and apparatus for enhancing data retransmission to improve call performance |
| US9220042B2 (en) | 2013-06-25 | 2015-12-22 | Freescale Semiconductor, Inc. | Wireless communication apparatus and method |
| KR102176923B1 (en) | 2013-12-04 | 2020-11-10 | 삼성전자 주식회사 | Method and apparatus for improving the quality of call services in mobile communication systems |
| CN116567716A (en) | 2017-03-23 | 2023-08-08 | 三星电子株式会社 | Method and apparatus for processing data for packet replication |
| KR102357594B1 (en) * | 2017-03-23 | 2022-02-04 | 삼성전자 주식회사 | Method and apparatus for processing data for packet duplication |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5826198A (en) * | 1992-01-13 | 1998-10-20 | Microcom Systems, Inc. | Transmission of data over a radio frequency channel |
| US5784362A (en) * | 1995-04-17 | 1998-07-21 | Telefonaktiebolaget Lm Ericsson | Temporary frame identification for ARQ in a reservation-slotted-ALOHA type of protocol |
| EP1056258A1 (en) | 1999-05-27 | 2000-11-29 | TELEFONAKTIEBOLAGET L M ERICSSON (publ) | Data unit sending means and control method in wireless networks |
| US20020071407A1 (en) * | 2000-07-08 | 2002-06-13 | Samsung Electronics Co., Ltd. | HARQ method in a CDMA mobile communication system |
| EP2288202B1 (en) * | 2000-10-07 | 2015-04-08 | LG Electronics Inc. | Method for transmitting data from RLC layer in radio communication system |
| US7318187B2 (en) * | 2003-08-21 | 2008-01-08 | Qualcomm Incorporated | Outer coding methods for broadcast/multicast content and related apparatus |
-
2004
- 2004-05-07 AT AT04741531T patent/ATE500670T1/en not_active IP Right Cessation
- 2004-05-07 AU AU2004319437A patent/AU2004319437B2/en not_active Ceased
- 2004-05-07 US US11/579,790 patent/US7881204B2/en active Active
- 2004-05-07 WO PCT/EP2004/050737 patent/WO2005109778A1/en active Application Filing
- 2004-05-07 CN CN2004800429810A patent/CN1977497B/en not_active Expired - Fee Related
- 2004-05-07 DE DE602004031676T patent/DE602004031676D1/en not_active Expired - Lifetime
- 2004-05-07 EP EP04741531A patent/EP1751928B1/en not_active Expired - Lifetime
-
2005
- 2005-05-03 TW TW094114310A patent/TWI367042B/en not_active IP Right Cessation
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101933280A (en) * | 2008-02-01 | 2010-12-29 | Lg电子株式会社 | Be used to send the mobile communication system and the method for PDCP status report |
| CN103428896B (en) * | 2008-06-23 | 2016-08-10 | 宏达国际电子股份有限公司 | Evolved universal terrestrial radio access network, its communication method, and user equipment |
| US8396037B2 (en) | 2008-06-23 | 2013-03-12 | Htc Corporation | Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof |
| TWI408984B (en) * | 2008-06-23 | 2013-09-11 | Htc Corp | Method used in evolved mobile telecommunications system, method used in user equipment, evolved mobile telecommunications system, and user equipment |
| US8798093B2 (en) | 2008-06-23 | 2014-08-05 | Htc Corporation | Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof |
| US8964699B2 (en) | 2008-06-23 | 2015-02-24 | Htc Corporation | Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof |
| US9191982B2 (en) | 2008-06-23 | 2015-11-17 | Htc Corporation | Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof |
| CN101616411B (en) * | 2008-06-23 | 2016-08-03 | 宏达国际电子股份有限公司 | Evolved universal terrestrial radio access network, its communication method, and user equipment |
| CN103458402B (en) * | 2008-06-23 | 2017-04-12 | 宏达国际电子股份有限公司 | Evolved universal terrestrial radio access network, its communication method, and user equipment |
| WO2010142122A1 (en) * | 2009-06-12 | 2010-12-16 | 中兴通讯股份有限公司 | Radio link data transmission method and radio communication network node |
| WO2015123883A1 (en) * | 2014-02-24 | 2015-08-27 | Qualcomm Incorporated | Radio link control entity re-establishment |
| CN106470497A (en) * | 2015-08-17 | 2017-03-01 | 中国移动通信集团公司 | A kind of data transmission method, wireless spread-spectrum technology send and receiving entity |
| CN106470497B (en) * | 2015-08-17 | 2019-10-29 | 中国移动通信集团公司 | A kind of data transmission method, wireless spread-spectrum technology is sent and receiving entity |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1977497B (en) | 2010-05-12 |
| WO2005109778A1 (en) | 2005-11-17 |
| ATE500670T1 (en) | 2011-03-15 |
| DE602004031676D1 (en) | 2011-04-14 |
| TW200623907A (en) | 2006-07-01 |
| US7881204B2 (en) | 2011-02-01 |
| US20080192671A1 (en) | 2008-08-14 |
| AU2004319437B2 (en) | 2009-03-05 |
| AU2004319437A1 (en) | 2005-11-17 |
| AU2004319437A2 (en) | 2005-11-17 |
| EP1751928A1 (en) | 2007-02-14 |
| EP1751928B1 (en) | 2011-03-02 |
| TWI367042B (en) | 2012-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7940771B2 (en) | Apparatus and method for requesting packet retransmission in a wireless communication system | |
| CN101960767B (en) | Method and apparatus for link control in a wireless communication system | |
| KR101051595B1 (en) | RLC window size reorganization | |
| CN1864363B (en) | Medium access control priority-based scheduling for data units in a data flow | |
| CN1977497A (en) | Lossless radio link control entity (RLC) re-establishment avoiding service data unit (SDU) duplication | |
| CN101030842B (en) | Method and apparatus for rearranging data in mobile telecommunication system | |
| CN1613233A (en) | Method and system of retransmission | |
| KR101224334B1 (en) | Apparatus and method of harq assisted arq operation for high rate data transmission | |
| CN101627611B (en) | Method for transmitting control information in mobile communication system | |
| EP1396119A1 (en) | Method and system of retransmission | |
| CN1187929A (en) | Temporary frame identification used for ARQ in reserved time slot ALOHA type protocol | |
| CN101079814A (en) | Method and apparatus for handling packet data in a wireless communications system | |
| CN1689260A (en) | Data transmission method and system for multiple HARQ processes | |
| CN1695336A (en) | System and method for handling erroneous data, splitting packets and partially processing them in a packet switched communication system | |
| JP2005318211A (en) | Control station device and base station device | |
| CN1859073A (en) | Dow data repeating method in radio communication system | |
| CN1783876A (en) | System and method for realizing packet data polymerized protocol function | |
| CN1889414A (en) | Method for transmitting status PDU based on missing PDU detection mechanism | |
| KR20030004618A (en) | Apparatus and method for retransmitting packet data in high speed downlink packet access system | |
| CN1921481A (en) | User protocol depot and method for realizing nondestructive transfer | |
| CN1640010A (en) | Method and system of load control | |
| CN1875557A (en) | Updating next-expected TSN and receiver window to avoid stall conditions | |
| CN1863030A (en) | Method for controlling pocket data transmission rate in mobile communication network and system thereof | |
| WO2020032626A1 (en) | Operation of automatic repeat request | |
| JP4778071B2 (en) | Wireless communication system, wireless base station, and wireless communication method |
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: 20100512 Termination date: 20170507 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |