US20090175175A1 - Radio link control reset using radio resource control signaling - Google Patents

Radio link control reset using radio resource control signaling Download PDF

Info

Publication number
US20090175175A1
US20090175175A1 US12/346,443 US34644308A US2009175175A1 US 20090175175 A1 US20090175175 A1 US 20090175175A1 US 34644308 A US34644308 A US 34644308A US 2009175175 A1 US2009175175 A1 US 2009175175A1
Authority
US
United States
Prior art keywords
radio link
reset
entity
link control
rlc
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.)
Abandoned
Application number
US12/346,443
Inventor
Shankar Somasundaram
Rajat P. Mukherjee
Mohammed Sammour
Stephen E. Terry
Jin Wang
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.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
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
Priority to US1904908P priority Critical
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Priority to US12/346,443 priority patent/US20090175175A1/en
Assigned to INTERDIGITAL PATENT HOLDINGS, INC. reassignment INTERDIGITAL PATENT HOLDINGS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MUKHERJEE, RAJAT P., SAMMOUR, MOHAMMED, SOMASUNDARAM, SHANKAR, TERRY, STEPHEN E., WANG, JIN
Publication of US20090175175A1 publication Critical patent/US20090175175A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/0406Wireless resource allocation involving control information exchange between nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. van Duuren system ; ARQ protocols
    • H04L1/1829Arrangements specific to the receiver end
    • H04L1/1835Buffer management
    • H04L1/1838Buffer management for semi-reliable protocols, e.g. for less sensitive applications such as streaming video
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/32Packet discarding or delaying
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/04Error control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. van Duuren system ; ARQ protocols
    • H04L1/1829Arrangements specific to the receiver end
    • H04L1/1848Time-out mechanisms

Abstract

A method and apparatus are disclosed wherein a reset procedure for a RLC is implemented by RRC signaling. Triggers for the initiation and execution of the disclosed reset method are also disclosed.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application claims the benefit of U.S. provisional application No. 61/019,049 filed on Jan. 4, 2008, which is incorporated by reference as if fully set forth.
  • FIELD OF INVENTION
  • This application is related to wireless communications.
  • BACKGROUND
  • Current efforts for the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) and LTE-Advanced wireless communication programs are to bring new technology, new architecture and new methods in the new LTE settings and configurations in order to provide improved spectral efficiency and reduced latency. As a result, the radio resources would be better utilized to bring faster user experiences and richer applications and services with less cost.
  • As part of this effort, 3GPP is defining new procedures for the Radio Resource Control (RRC) and Radio Link Control (RLC) layers to help meet these goals. In the prior art (e.g., Universal Mobile Telecommunication System (UMTS) specifications), an RLC entity of a transmitter did not request a reset after reaching a maximum allowed number of RLC retransmissions. Instead, the RLC entity would attempt to keep the call alive and initiate its own reset without the RRC being aware. To do so, the RLC entity would continue retransmissions and then continue with the reset procedure until the RLC was able to recover or until the maximum number of retransmission for RLC reset was reached. When the RLC failed, the RRC would initiate a radio link failure (RLF) recovery procedure, but would put the transmitter into IDLE mode rather than attempting a RRC connection re-establishment.
  • Current LTE proposals allow a RLC entity to reset using RLC control protocol data units (PDUs). However, this procedure can be complex. Accordingly, there exists a need for an improved method and apparatus for resetting the RLC entity.
  • SUMMARY
  • A method and apparatus are disclosed wherein a reset procedure for a radio link control is implemented by radio resource control signaling. Triggers for the initiation and execution of the disclosed reset method are also disclosed.
  • A wireless transmit/receive unit (WTRU) detects a number of retransmissions exceeding a maximum number of allowed retransmissions as an indication of radio link failure and sends a radio link control reset request within a radio resource control message from a radio resource control entity to a peer radio link control entity at a base station.
  • Alternatively, a wireless transmit/receive unit (WTRU) receives a request for radio link control reset. A processor at the WTRU comprises a radio resource control (RRC) entity and a radio link control (RLC) entity. The RRC entity receives the request for a radio link control reset in a radio resource control message, The RLC entity reassembles radio link control service data units (SDUs) from any protocol data units (PDUs) that are received out of sequence at a receiving side of the RLC entity. The reassembled SDUs are delivered in sequence to a packet data convergence protocol entity. At the receiving side of the RLC entity, any remaining PDUs that are not able to be reassembled are discarded. At a transmitting side of the RLC entity, all SDUs and PDUs stored in transmit buffers are discarded.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • A more detailed understanding may be had from the following description, given by way of example and to be understood in conjunction with the accompanying drawings wherein:
  • FIG. 1 is a functional block diagram of a transmitter and receiver configured to perform a RLC reset;
  • FIG. 2 is a functional block diagram of a transmitter processor and a receiver processor configured to perform a RLC reset; and
  • FIG. 3 is signal diagram for a Protocol Reset signal.
  • DETAILED DESCRIPTION
  • When referred to hereafter, the terminology “wireless transmit/receive unit (WTRU)” includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of user device capable of operating in a wireless environment. When referred to hereafter, the terminology “base station” includes but is not limited to a Node-B, an evolved Node-B, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment.
  • It should be noted that the disclosed RLC ‘Reset’ procedure may be referred to by other names such as RLC ‘Re-establishment’ or RLC ‘Re-configuration’. As such, the disclosed method and apparatus applies even when the procedures proposed herein are described using other names or terms in the 3GPP standards specifications.
  • FIG. 1 is a functional block diagram of a transmitter and receiver 110, 120 configured to perform the disclosed method. In addition to components included in a typical transmitter/receiver (i.e., a WTRU or base station), the transmitter 110 and the receiver 120 includes: processors 115, 125 configured to perform a reset of an RLC entity using RRC signaling; receivers 116, 126 in communication with processors 115, 125; transmitters 117, 127 in communication with processors 115, 125; and antennas 118, 128 in communication with receivers 116, 126 and transmitters 117, 127 to facilitate the transmission and reception of wireless data. Additionally, the receiver 116, the transmitter 117 and the antenna 118 may be a single receiver, transmitter and antenna, or may include a plurality of individual receivers, transmitters and antennas, respectively. The transmitter 110 may be a WTRU transmitting to a base station receiver 120. Alternatively, the transmitter 110 may be a base station transmitting to a WTRU receiver 120.
  • FIG. 2 shows a signaling diagram for the transmitter 110 and the receiver 120, in which the processor 115 comprises a radio link control layer (RLC) entity 221, a radio resource control layer (RRC) entity 222, a packet data convergence protocol layer (PDCP) entity 223, and the processor 125 comprises an RLC entity 231, a RRC entity 232, and a PDCP entity 233. While a single RLC entity 221 is shown for the processor 115, and a single RLC entity 231 is shown for the processor 125, there may be multiple RLC entities, including a transmitting Unacknowledged Mode (UM) RLC entity, a receiving UM RLC entity, a transmitting Transparent Mode (TM) RLC entity, a receiving TM RLC entity, and an Acknowledged Mode (AM) RLC entity. A single RLC entity 221, 231 is shown for purpose of simplifying the description herein and is not meant to represent a limitation to the disclosed method and apparatus. It should be noted that the inter-layer entity activity disclosed below for the Radio Resource Control (RRC) and RLC may be accomplished by defining new primitives or information elements between the layers.
  • Upon detecting an RLC Reset trigger as an indication of RLC failure, the RLC entity 221 included in transmitter processor 115 sends a RLC reset request indication 201 to the RRC entity 222 indicating that a RLC Reset is desired (i.e., that both the peer RLC entity 231 and the RLC entity 221 itself should be reset). An example of an RLC Reset trigger may be, for an AM RLC entity 221, that the maximum number of retransmissions allowed has been reached. Other examples of triggers include a Service Data Unit (SDU) discard not being configured for an event, RLC Status PDUs indicating erroneous sequence numbers; unrecoverable errors; and any other event or trigger that requires the RLC to be reset.
  • The RLC Reset request indication 201 that is forwarded to the RRC entity 222 may include one or more of the following types of request information in the form of an information element (IE) or a single or multiple bit value. A cause value may be included to indicate the reason for the RLC Reset request indication 201. For example, if the trigger is the maximum number of retransmissions being reached, the RLC reset request indication 201 includes an indication of this to the RRC entity 222. Status information may also be included in the RLC Reset request indication 201 indicating the last sequence number (SN) correctly received for the RLC entity 221 requesting the RLC Reset. The RLC Reset request indication 201 may also include an identification of the RLC entity 221 to be reset (e.g., the RLC entity identification may be according to the logical channel instance associated with the RLC entity or the radio bearer associated with the RLC entity), or alternatively, a new RLC entity ID may be defined and indicated for explicitly identifying the RLC entity.
  • After forwarding the RLC request indication 201 to the RRC entity 222, the RLC entity 221 may perform one or more of the following:
      • 1. Start a timer T101 that may be specific to each RLC entity 221 or common to each RLC entity 221.
      • 2. Suspend transmission of any protocol data units (PDUs) on the RLC entity 221 being reset.
      • 3. Flush the buffer of any SDUs sent before the RLC reset.
      • 4. Suspend reception of any PDUs on the RLC entity 221, which may occur via discarding any received PDUs for such entity.
      • 5. Increment/Decrement a counter C101 that keeps a count of the number of reset requests. This counter may be specific to each RLC entity.
      • 6. Reset the RLC entity 221 to initially configured parameters (e.g., the sequence number (SN) may be reset back to zero). Alternatively, the RLC entity 221 may take this reset action on the expiration of the timer T101.
      • 7. Wait for an indication 202 from the RRC entity 222 before starting any of the above procedures. The indication 202 from the RRC entity 222 may take the form of an acknowledgment of the reset request indication 201 and/or confirmation of the reset procedures being initiated by the RRC entity 222.
  • The RRC entity 222, upon receiving an RLC reset indication 201 that an RLC reset is required, may send an RRC message 203 to the peer RRC entity 232 indicating a reset of RLC is required. The parameters for the RLC reset may be included in any RRC message 203 (e.g., a RRC CONNECTION RE-ESTABLISHMENT message or a RRC CONNECTION RECONFIGURATION message) or in a new RRC message dedicated for reset procedures, such as a PROTOCOL RESET message as will be described further below. In order to transmit the RLC Reset request information, a new IE, such as an RLC Reset IE or a Protocol Reset Indicator Information Element (IE), may be used for indicating the reset request of the RLC entity 221. This IE may be carried in any RRC message 203 or in a specific message dedicated for reset procedures. An example of the RLC Reset IE parameters is presented in Table 1 below.
  • TABLE 1 Type and Information Multi Reference Semantics Information for <1 to protocol entity Number of for reset entities requesting Reset> > Protocol Boolean Identifies whether the entity entity being reset is a PDCP entity or requesting an RLC entity. This may not be reset necessary if the reset indicator IE is defined specifically for RLC or PDCP. >> Identity Integer Identification of the RLC entity being reset. This may be either the logical channel instance mapped to the RLC entity, or the RB ID mapped to the entity or some other ID. This information may be implied by the presence of some other information in a parent field in the information tree. >>> RSN Integer The Reset sequence number (RSN) identifies if this is the first reset request for this entity or a retransmission. Alternatively, the RSN may be defined for the entire RRC message instead of on a per- entity basis >>> Cause Integer Indicates the reason for reset request >>> Reset Boolean Identifies if the RLC entity is to configuration be reset to default/initial configurations or some different configuration >>>> If RLC entity is to be reset to a Parameters for configuration different from reset initial/default.
  • The individual IEs described in TABLE 1 are optional and the information contained in them may be passed in a different manner. The RRC message 203 indicating the reset may be any indication of a reset. For example, the RRC message 203 may include, but is not limited to, a bit, or a few bits, that may be passed in any RRC message to more detailed IEs (e.g., see Protocol Reset Indicator IE) to dedicated messages. The indications in the RRC message 203 may be explicit or implicit and may also include RLC and/or PDCP status. For an implicit indication, a separately sent RRC message that does not contain the reset IEs may indicate that a reset is required merely by the RRC message name according to a prearranged definition.
  • The RRC message 203 indicating the RLC reset request to the peer RRC entity 232 may include an explicit or implicit indication of the time of the reset/activation of reset. Alternatively this may be accomplished on a Transmission Time Interval (TTI) or a System Frame Number (SFN) basis. As an example, a synchronization may be achieved by alignment of the RLC reset with the SFN or a number of TTIs relative to the last TTI in which the RRC message 203 was transmitted/received.
  • In the event that the RLC entity 221 to be reset is the same RLC entity that would initiate an RRC message 203 indicating the reset, the RRC entity 222 may transmit the message indicating the reset over a radio bearer (RB), which is mapped to a different RLC entity of transmitter 110. Alternatively, a new RB and associated RLC entity may be configured. Alternatively, the RRC message 203 containing the RLC reset IE can be transmitted on a Signaling RB (SRB). This SRB may be dedicated to the reset of RLC and some other purposes (e.g., a reset of PDCP). It is preferable that the SRB be mapped to a RLC UM entity to avoid the possibility of this SRB being reset.
  • The RRC entity 222 may ensure that the RRC message 203 for RLC Reset will fit inside a single RLC PDU. The RRC entity 222 may aggregate multiple reset requests from different RLC entities 221 into a single message 203. If the transmitting RRC entity 222 receives a reset request for a transmitting RLC entity 221 for which a reset procedure is ongoing it may ignore the request. The transmitting RRC entity 222 may acknowledge a reset request from the transmitting RLC layer/entity in an acknowledgment signal 202.
  • The transmitting RRC entity 222 may send a pending RLC Reset indication 204 to the PDCP entity 223. This may trigger the generation of a PDCP status PDU at the transmitter 110.
  • After transmission of the RRC message 203 indicating the RLC Reset request, the RRC entity 222 may perform one or more of the following:
      • 1. Start a timer T102 timer that may determine the time the transmitting RRC entity 222 may wait for an RLC Reset acknowledgment 213 before initiating further action;
      • 2. Increment/Decrement a counter C102 that keeps a count of the number of RLC reset requests via the RRC messages 203. This counter may be specific to each RLC entity 221 and may be used to indicate the RSN for the RLC Reset request. The RRC entity 222 may use a RRC Transaction Identifier to distinguish re-transmissions of the same reset request; and
      • 3. Provide an indication 205 to the RLC entity 221 that the RLC Reset procedure has been initiated.
        If the timer T102 described above expires, the RRC entity 222 may implement one of the following:
      • 1. Retransmit the RLC Reset request in another RRC message 203;
      • 2. Send a new RLC Reset request, with possibly a reference to a different RLC entity to be reset;
      • 3. Increment/Decrement the counter C102 and restart the timer T102; and
      • 4. Provide an indication of timer T102 expiration to the RLC entity 221.
  • If the counter C102 reaches a pre-determined value (e.g. a configured/pre-determined value for the maximum number of reset requests) the RRC entity 221 may initiate a different set of procedures. For example, the RRC entity 222 may initiate RRC RECONFIGURATION procedures or Radio Link Failure procedures or Physical Channel Reconfiguration procedures or some other recovery procedure.
  • The RRC entity 222 may use Hybrid Automatic Repeat Request (HARQ) assistance to retransmit the RRC message 203 that contains the reset indicator. For example, a HARQ entity 224 may indicate to the RRC entity 222 that delivery of the RRC PDU that contains the RLC reset has failed, and subsequently the RRC 222 retransmits the PDU.
  • At the receiver 115, upon receipt of the RRC message 203 with the RLC Reset request, the RRC entity 232 implements one or more of the following actions:
      • 1. Send an RRC message acknowledgment 213 to acknowledge receipt of the reset request back to the transmitter RRC entity 222. The receiver RRC entity 232 may pass the RLC Reset request to the receiver RLC entity 231; alternatively, the acknowledgment 213 may be sent after waiting for a reset confirmation from the RLC entity 231;
      • 2. Stop the transmission/reception of any PDUs on the RBs configured for the RLC entity 231;
      • 3. Instruct the RLC entity 231 to flush the RLC data buffer; and
      • 4. Pass the RLC Reset request to the RLC entity 231 as indication 211 and to the PDCP entity 233 as indication 214, along with any associated reset parameters.
  • In the event that the RLC entity 231 that is to be reset is the same RLC entity that is to initiate the RRC message 213 indicating the RLC Reset acknowledgment, the receiver RRC entity 222 may transmit the message indicating the reset acknowledgment over a RB which is mapped to a different RLC entity. Alternatively, a new RB and associated RLC entity may be configured.
  • In another alternative, the RRC message 213 comprising the RLC Reset acknowledgment IE can be transmitted on a Signaling RB (SRB). This SRB may be dedicated to the reset acknowledgment of RLC and some other purposes (e.g., reset acknowledgment of PDCP). This SRB may be mapped to a UM RLC entity to avoid the possibility of this SRB being reset.
  • The RRC entity 232 may ensure that the RRC message 213 for reset acknowledgment will fit inside a single RLC PDU. The RRC entity 232 may aggregate multiple reset acknowledgments for different RLC entities 231 into a single message.
  • The RRC procedure may use HARQ assistance to retransmit the RRC message that contains the reset acknowledgment indicator. For example, a HARQ entity 234 may indicate to the RRC 232 that delivery of the RRC PDU that contains the RLC reset acknowledgment has failed, and subsequently the RRC entity 232 retransmits the PDU.
  • The RRC entity 232, upon receiving an RLC reset indication 212 that an RLC reset has occurred, may send an RRC message 213 to the peer RRC entity 222 indicating acknowledgment of the RLC reset. The parameters for the RLC reset acknowledgment may be included in any RRC message 213 (e.g., a RRC CONNECTION REESTABLISHMENT COMPLETE message or a RRC CONNECTION RECONFIGURATION COMPLETE message) or in a new RRC message dedicated for reset procedures, such as a PROTOCOL RESET ACKNOWLEDGE message as will be described further below. In order to transmit the RLC Reset acknowledgment information, a new IE, such as an RLC Reset Acknowledgment IE or a Protocol Reset ACK IE, may be used for indicating the reset of the RLC entity 231. This IE may be carried in any RRC message 213 or in a specific message dedicated for RLC reset procedures. An example of the RLC Reset Acknowledgment IE parameters is presented in TABLE 2 below.
  • TABLE 2 Type and Information Multi Reference Semantics Information for <1 to Number of protocol entity entities for Reset reset being being acked> acknowledged > Protocol entity Boolean Identifies whether the entity for reset being being reset acknowledged is a acknowledged PDCP entity or an RLC entity. This may not be necessary if the reset acknowledge indicator IE is defined specifically for RLC or PDCP. >> Identity Integer Identification of the RLC entity being reset acknowledged. This may be either the logical channel instance mapped to the RLC entity, or the RB ID mapped to the entity or some other ID. This information may be implied by the presence of some other information in a parent field in the information tree. >>> RSN Integer The Reset SN identifies the corresponding reset request that is being acked. This shall be the same as the RSN in the corresponding reset request.
  • It should be understood that the individual RLC Reset Acknowledge IE parameters described above are optional and the information contained in the IE may be passed in a different manner.
  • When the RLC entity 231 at the receiver receives a command from the RRC entity 232 to reset, the RLC entity 231 may implement one or more of the following:
      • 1. Reset some or all the RLC state variables for that entity to their initial/default values or to the value (if any) configured in the reset request;
      • 2. Reset configurable parameters to their configured values or to a new value (if any) received in the reset request;
      • 3. Stop and/or restart any or all timers associated with that RLC entity 231;
      • 4. In the receiving side of the RLC entity 231, if possible, reassemble RLC SDUs from the PDUs that are received out of sequence and deliver them to the upper layer entities (e.g., PDCP entity 233); discard any remaining PDUs that could not be reassembled into RLC SDUs;
      • 5. In the transmitting side of the RLC entity 231, discard all RLC PDUs from the PDU (re)transmit buffer of the RLC entity 231;
      • 6. In the transmitting side of the RLC entity 231, discard all RLC SDUs from the SDU transmit buffer of the RLC entity 231, and notify the upper layer entities (e.g., PDCP entity 233) of the discarded SDU(s). After receiving such notification, the upper layer (e.g., PDCP entity 233) may re-submit (i.e., effectively retransmit) those SDUs for transmission to the RLC entity 231 below it, following the completion of the RLC reset. In another alternative, in the transmitting side of the RLC entity 231, the RLC SDUs are not discarded from the SDU transmit buffer of the RLC entity 231 when reset occurs;
      • 7. In the transmitting side of the RLC entity 231, notify the upper layers (e.g., PDCP entity 233) of all SDUs whose reception have not been acknowledged (confirmed) by the peer RLC entity 221 (via RLC STATUS PDUs). After receiving such notification, the upper layer entity (e.g., PDCP entity 233) may re-submit (i.e., effectively retransmit) those SDUs for transmission to the RLC entity 231 below it, following the completion of the RLC reset;
      • 8. Confirm completion of the reset procedures to the RRC with indication 212; and
      • 9. Indicate the completion of reset to upper layer entities (e.g., PDCP entity 233 with indication 215).
  • The PDCP entity 233 may use an indication of the RLC reset (received via RRC indication 214 or RLC indication 215) to generate a PDCP Status PDU.
  • The RLC entity 231 reset may be synchronized with the RRC procedure (i.e., the RRC message 203 and/or message 213). The RRC procedure may include an explicit or implicit indication of the time of the reset/activation of reset. Alternatively this may be accomplished on a TTI or SFN basis. As an example, the synchronization between the RRC procedure and the RLC reset could also be aligned with the SFN or a number of TTI's relative to the last TTI in which the RRC message 203 and/or RRC message 213 was received.
  • Upon reception of the acknowledgment of the RLC reset via RRC message 213 from the receiver RRC entity 232, the transmitter RRC entity 222 implements one or more of the following:
      • 1. Stop timer T102;
      • 2. Reset the counter C102 to its initial value or zero; and
      • 3. Confirm the acknowledgment RRC message 213 to the RLC entity 221 with indication 205 and to the PDCP entity 223 with indication 206.
  • The RLC entity 221, upon receiving acknowledgment of the reset request via the RRC indication 205, implements one or more of the following:
      • 1. Stop timer T101;
      • 2. Reset counter C101 to zero;
      • 3. Reset some or all the RLC state variables for that entity to their initial/default values or to the value (if any) configured in the reset request;
      • 4. Reset configurable parameters to their configured values or to a new value (if any) received in the reset request;
      • 5. Stop and/or restart any or all timers associated with that RLC entity 221;
      • 6. In the receiving side of the RLC entity 221, if possible reassemble RLC SDUs from the PDUs that are received out of sequence and deliver them in sequence to the PDCP entity 223; discard any remaining PDUs that could not be reassembled into RLC SDUs;
      • 7. In the transmitting side of the RLC entity 221, discard all RLC PDUs from the PDU (re)transmit buffer of the RLC entity 221;
      • 8. In the transmitting side of the RLC entity 221, discard all RLC SDUs from the SDU transmit buffer of the RLC entity 221, and notify the upper layers (e.g., PDCP 223) of the discarded SDU(s). After receiving such notification, the upper layer (e.g., PDCP 223) may re-submit (i.e. effectively retransmit) those SDUs for transmission to the RLC entity 221 below it, following the completion of the RLC reset. In another less preferred alternative: In the transmitting side of the RLC entity, do not discard RLC SDUs from the SDU transmit buffer of the RLC entity 221(when reset occurs);
      • 9. In the transmitting side of the RLC entity 221, notify the upper layers (e.g., PDCP 223) of all SDUs whose reception have not been acknowledged (confirmed) by the peer RLC entity (via RLC STATUS PDUs). After receiving such notification, the upper layer (e.g., PDCP 223) may re-submit (i.e. effectively retransmit) those SDUs for transmission to the RLC entity 221 below it, following the completion of the RLC reset;
      • 10. Confirm completion of the reset procedures to the RRC entity 222; and
      • 11. Indicate the completion of reset to upper layers (e.g. PDCP 223).
  • The PDCP entity 223 may use the acknowledgment of the RLC reset (received via RRC indication 206 or RLC indication 208) to generate a PDCP Status PDU.
  • The RLC 221 reset may be synchronized with the RRC procedure (i.e., the RRC message 203 and/or message 213). The RRC procedure may include an explicit or implicit indication of the time of the reset/activation of reset. Alternatively this may be accomplished on a TTI or SFN basis. As an example the synchronization between the RRC procedure and the RLC 221 reset could also be aligned with the SFN or a number of TTI's relative to the last TTI in which the RRC message 203, and/or RRC message 213 was received.
  • In accordance with the method disclosed above for RLC reset accomplished via RRC, the following is a summary of the RRC signaling for the RRC messages 203 and 213 in terms of a Protocol Reset procedure, shown in FIG. 3.
  • The transmitting RRC entity 222 may initiate this Protocol Reset procedure whenever the RLC entity 221 in the transmitter 110 indicates the need for resetting a RLC entity.
  • Upon initiation of the procedure the transmitting RRC entity 222:
      • 1> Initiates transmission of a PROTOCOL RESET REQUEST message 301
      • 1> Indicates initiation of the procedure to the RLC (optional)
      • 1> Start Timer T102 when lower layers indicate successful transmission of the message
  • Upon expiration of the timer T102 the transmitting RRC entity 222:
      • 1> Re-Initiates transmission of the PROTOCOL RESET REQUEST message 301
      • 1> Re-Starts Timer T102 when lower layers indicate successful transmission of the message
  • The transmitting RRC entity 222 takes the following actions when it initiates the transmission of a PROTOCOL RESET REQUEST message 301:
      • 1> if this is a new reset request
        • 2> Initialize a new instance of the counter C102 and increment it by one
      • 1> If this is a reset request that is being re-transmitted
        • 2> increment the counter C102 by one
  • The transmitting RRC entity 222 sets the contents of the PROTOCOL RESET message 301 as follows:
    • 0> If C102 counter is <=MaxNumberofResetReTransmissions+1
      • 1> Identify the RLC entities to be reset in the PROTOCOL RESET REQUEST message 301 and set the Transaction Identifier in the message to be equal to the value of the C102 counter
    • 0> else
      • 1> Declare RL failure and start the RL failure handling procedure.
      • 2> Try to re-establish the connection by sending the RRC re-establishment request
  • Upon receiving a PROTOCOL RESET REQUEST message 301 the RRC entity 232:
      • 1> Initiates transmission of the PROTOCOL RESET ACKNOWLEDGE message 302
      • 1> Passes the reset request to the RLC entity 231
      • 1> Starts timer T103 when lower layers indicate successful transmission of the message (optional)
  • The RRC entity 232 sets the contents of the PROTOCOL RESET ACKNOWLEDGE message 302 as follows:
      • 1> Set the Transaction Identifier value of the message to the corresponding Transaction Identifier in the PROTOCOL RESET REQUEST message 301 being acknowledged
  • Upon receiving a PROTOCOL RESET ACKNOWLEDGE 302, the RRC entity 222:
      • 1> Stops timer T102
      • 1> Resets counter C102 to zero
      • 1> Initiates transmission of the PROTOCOL RESET COMPLETE message 303 (optional)
      • 1> Indicate receipt of the acknowledgment to the lower layers (e.g. RLC)
  • The following is a summary of the messages depicted in FIG. 3.
  • The PROTOCOL RESET REQUEST message 301 is used for requesting a reset of a lower-layer protocol entity:
    • Signaling radio bearer: SRB 1 or SRB 2
    • RLC-SAP: AM or UM
    • Logical channel: DCCH
    • Direction: UE->E-UTRAN, EUTRAN->UE
  • Name Need Type/reference Message Type MP <ref> Transaction identifier MP Integer [0 . . . 3] Protocol Reset Indicator IE MP
  • The PROTOCOL RESET ACKNOWLEDGMENT message 302 is used for acknowledging a reset of a lower-layer protocol entity:
    • Signaling radio bearer: SRB 1 or SRB 2
    • RLC-SAP: AM or UM
    • Logical channel: DCCH
    • Direction: UE->E-UTRAN, EUTRAN->UE
  • Name Need Type/reference Message Type MP <ref> Transaction identifier MP Integer [0 . . . 3] Protocol Reset Ack IE MP
  • The PROTOCOL RESET COMPLETE message 303 is used for completing a reset of a lower-layer protocol entity (optional):
    • Signaling radio bearer: SRB 1 or SRB 2
    • RLC-SAP: AM or UM
    • Logical channel: DCCH
    • Direction: UE->E-UTRAN, EUTRAN->UE
  • Name Need Type/reference Message Type MP <ref> Transaction identifier MP Integer [0 . . . 3]
  • The disclosed methods and apparatuses are applicable to any wireless communication devices and systems, including those related to 3GPP LTE and/or HSPA enhancements (e.g. WCDMA evolution Rel-7, Rel-8, etc).
  • Although the features and elements are described in particular combinations, each feature or element can be used alone without the other features and elements or in various combinations with or without other features and elements. The methods or flow charts provided may be implemented in a computer program, software, or firmware tangibly embodied in a computer-readable storage medium for execution by a general purpose computer or a processor. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
  • A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer. The WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) or Ultra Wide Band (UWB) module.

Claims (19)

1. A method implemented by a wireless transmit/receive unit (WTRU) for resetting a base station radio link control entity, comprising:
detecting a number of retransmissions exceeding a maximum number of allowed retransmissions as an indication of radio link failure; and
sending from a radio resource control entity a radio resource control message to a base station, which includes a radio link control reset request.
2. The method according to claim 1, wherein the radio link control reset request includes an information element that identifies a radio link entity requesting radio link control reset request.
3. The method according to claim 1, wherein the radio link control reset request includes an information element that identifies a radio link entity to be reset.
4. The method according to claim 1, wherein the radio link control reset request includes an information element that identifies a reset sequence number that indicates whether the radio link control reset request is a first request or a request retransmission.
5. The method according to claim 1, wherein the radio link control reset request includes an information element that identifies a cause for the radio link reset request.
6. The method according to claim 1, wherein the radio link control reset request includes an information element that identifies configuration parameters for the radio link control reset.
7. A method implemented by a wireless transmit/receive unit (WTRU) for resetting a radio link control (RLC) entity, comprising:
receiving a request for a RLC reset in a radio resource control message;
reassembling RLC service data units (SDUs) from any protocol data units (PDUs) that are received out of sequence at a receiving side of the RLC entity;
discarding at the receiving side of the RLC entity any remaining PDUs that are not able to be reassembled;
discarding at a transmitting side of the RLC entity all SDUs and PDUs stored in transmit buffers;
stopping and resetting all timers associated with the RLC entity; and
resetting all state variables associated with the RLC entity to initial values.
8. The method according to claim 7, further comprising sending a RLC reset acknowledgment.
9. The method according to claim 7, wherein the radio link control entity is an acknowledgment mode type of radio link control entity.
10. A wireless transmit/receive unit (WTRU), comprising:
a processor comprising:
a radio link control entity configured to detect a number of retransmissions exceeding a maximum number of allowed retransmissions as an indication of radio link failure; and
a radio resource control entity configured to send a radio link control reset request message to a base station, the message triggered by a radio link control reset indication received from the radio link control entity.
11. The WTRU according to claim 10, wherein the radio resource control entity is further configured to define an information element (IE) that identifies a radio link entity requesting radio link control reset request, and the radio link control reset request message contains the IE.
12. The WTRU according to claim 10, wherein the radio resource control entity is further configured to define an information element (IE) that identifies a radio link entity to be reset, and the radio link control reset request message contains the IE.
13. The WTRU according to claim 10, wherein the radio resource control entity is further configured to define an information element (IE) that identifies a reset sequence number that indicates whether the radio link control reset request is a first request or a request retransmission, and the radio link control reset request message contains the IE.
14. The WTRU according to claim 10, wherein the radio resource control entity is further configured to define an information element (IE) that identifies a cause for the radio link reset request, and the radio link control reset request message contains the IE.
15. The WTRU according to claim 10, wherein the radio resource control entity is further configured to define an information element (IE) that identifies configuration parameters for the radio link control reset, and the radio link control reset request message contains the IE.
16. A wireless transmit/receive unit (WTRU), comprising:
a processor comprising:
a radio resource control entity configured to receive a request for a radio link control reset in a radio resource control message; and
a radio link control entity configured to reassemble radio link control service data units (SDUs) from any protocol data units (PDUs) that are received out of sequence at a receiving side of the RLC entity; to deliver reassembled SDUs in sequence to a packet data convergence protocol entity; to discard at the receiving side of the radio link control entity any remaining PDUs that are not able to be reassembled; to discard at a transmitting side of the radio link control entity all SDUs and PDUs stored in transmit buffers; to stop and reset all timers associated with the radio link control entity; and to reset all state variables associated with the radio link control entity to initial values.
17. The WTRU according to claim 16, wherein the radio resource control entity is further configured to send a radio link control reset acknowledgment for acknowledging the received radio link control reset request.
18. The WTRU according to claim 16, wherein the radio resource control entity is further configured to send a radio link control reset acknowledgment upon the radio link control entity having completed a reset as according to the received reset request.
19. The WTRU according to claim 16, wherein the radio link control entity is an acknowledgment mode type of radio link control entity.
US12/346,443 2008-01-04 2008-12-30 Radio link control reset using radio resource control signaling Abandoned US20090175175A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US1904908P true 2008-01-04 2008-01-04
US12/346,443 US20090175175A1 (en) 2008-01-04 2008-12-30 Radio link control reset using radio resource control signaling

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US12/346,443 US20090175175A1 (en) 2008-01-04 2008-12-30 Radio link control reset using radio resource control signaling
US13/293,528 US8693479B2 (en) 2008-01-04 2011-11-10 Radio link control reset using radio resource control signaling
US14/179,280 US9167564B2 (en) 2008-01-04 2014-02-12 Radio link control reset using radio resource control signaling
US14/791,642 US9596674B2 (en) 2008-01-04 2015-07-06 Radio link control reset using radio resource control signaling

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/293,528 Division US8693479B2 (en) 2008-01-04 2011-11-10 Radio link control reset using radio resource control signaling

Publications (1)

Publication Number Publication Date
US20090175175A1 true US20090175175A1 (en) 2009-07-09

Family

ID=40677621

Family Applications (4)

Application Number Title Priority Date Filing Date
US12/346,443 Abandoned US20090175175A1 (en) 2008-01-04 2008-12-30 Radio link control reset using radio resource control signaling
US13/293,528 Active 2029-02-02 US8693479B2 (en) 2008-01-04 2011-11-10 Radio link control reset using radio resource control signaling
US14/179,280 Expired - Fee Related US9167564B2 (en) 2008-01-04 2014-02-12 Radio link control reset using radio resource control signaling
US14/791,642 Active US9596674B2 (en) 2008-01-04 2015-07-06 Radio link control reset using radio resource control signaling

Family Applications After (3)

Application Number Title Priority Date Filing Date
US13/293,528 Active 2029-02-02 US8693479B2 (en) 2008-01-04 2011-11-10 Radio link control reset using radio resource control signaling
US14/179,280 Expired - Fee Related US9167564B2 (en) 2008-01-04 2014-02-12 Radio link control reset using radio resource control signaling
US14/791,642 Active US9596674B2 (en) 2008-01-04 2015-07-06 Radio link control reset using radio resource control signaling

Country Status (10)

Country Link
US (4) US20090175175A1 (en)
EP (1) EP2241045B1 (en)
JP (4) JP5150734B2 (en)
KR (4) KR101661830B1 (en)
CN (2) CN107070607A (en)
CA (1) CA2711241C (en)
NO (1) NO2241045T3 (en)
SG (1) SG187407A1 (en)
TW (2) TWI536788B (en)
WO (1) WO2009088903A2 (en)

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090204862A1 (en) * 2008-02-01 2009-08-13 Lg Electronics Inc. Method of an uplink harq operation at an expiry of time alignment timer
US20090207739A1 (en) * 2008-02-01 2009-08-20 Sung-Duck Chun Mobile communication system and method for transmitting pdcp status report thereof
US20090215456A1 (en) * 2008-02-01 2009-08-27 Lg Electronics Inc. Method for sending rlc pdu and allocating radio resource in mobile communications system and rlc entity of mobile communications
US20090239563A1 (en) * 2008-03-20 2009-09-24 Ou Meng-Hui Method and Apparatus for Improving RRC Connection Procedure
US20090285111A1 (en) * 2008-05-19 2009-11-19 Ou Meng-Hui Method of connection re-establishment and related communication device
US20090312007A1 (en) * 2008-03-21 2009-12-17 Nokia Corporation Re-establishment of a rlc entity
US20100173626A1 (en) * 2009-01-06 2010-07-08 Qualcomm Incorporated Adaptation of handover parameters
US20100240359A1 (en) * 2009-03-22 2010-09-23 Chih-Hsiang Wu Method of Handling Radio link Failure in a Wireless Communication System and Related Communication Device
US20100240357A1 (en) * 2009-03-22 2010-09-23 Chih-Hsiang Wu Method of Handling Radio link Failure Detection in a Wireless Communication System and Related Communication Device
US20100296454A1 (en) * 2008-02-01 2010-11-25 Sung-Jun Park Method of downlink harq operation at an expiry of time alignment timer
US20110206019A1 (en) * 2008-11-13 2011-08-25 Hengxing Zhai Synchronization Scheduling Method
US20130003542A1 (en) * 2011-07-01 2013-01-03 Qualcomm Incorporated Methods and apparatus for enhanced ul rlc flow control for mrab calls
WO2014025755A1 (en) * 2012-08-06 2014-02-13 Qualcomm Incorporated Method and apparatus for enhancing data retransmission to improve call performance
WO2014035906A1 (en) * 2012-08-31 2014-03-06 Marvell World Trade Ltd. Method and apparatus for detecting and processing a retransmitted data packet in a wireless network
US20140274083A1 (en) * 2013-03-13 2014-09-18 Qualcomm Incorporated Method and apparatus for improving re-transmission of reconfiguration messages
US20140293897A1 (en) * 2013-04-01 2014-10-02 Innovative Sonic Corporation Method and apparatus for adding serving cells in a wireless communication system
US8873535B2 (en) 2011-09-26 2014-10-28 Qualcomm Incorporated Systems, methods and apparatus for retransmitting protocol data units in wireless communications
US9232482B2 (en) 2011-07-01 2016-01-05 QUALOCOMM Incorporated Systems, methods and apparatus for managing multiple radio access bearer communications
CN105577330A (en) * 2014-10-08 2016-05-11 展讯通信(上海)有限公司 Data retransmission system, data retransmission method and mobile terminal
US20160373962A1 (en) * 2013-10-17 2016-12-22 Zte Corporation Data package shunting transmission method and system, and computer stoarge medium
US9591593B2 (en) 2011-07-22 2017-03-07 Qualcomm Incorporated Systems, methods and apparatus for radio uplink power control
US9590792B2 (en) 2013-04-01 2017-03-07 Marvell World Trade Ltd. Termination of wireless communication uplink periods to facilitate reception of other wireless communications
US9686046B2 (en) 2011-09-13 2017-06-20 Qualcomm Incorporated Systems, methods and apparatus for wireless condition based multiple radio access bearer communications
US9930569B2 (en) 2011-08-04 2018-03-27 Qualcomm Incorporated Systems, methods and apparatus for wireless condition based multiple radio access bearer communications
US10219162B1 (en) 2013-12-19 2019-02-26 Marvell International Ltd. Interference suppression or cancellation in collocated receivers
CN109428687A (en) * 2017-07-21 2019-03-05 华为技术有限公司 The method and apparatus for triggering Radio Link Failure RLF

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090175175A1 (en) 2008-01-04 2009-07-09 Interdigital Patent Holdings, Inc. Radio link control reset using radio resource control signaling
CN102104892B (en) * 2009-12-22 2015-06-03 中兴通讯股份有限公司 Method for detecting radio link failure
CN102668433B (en) * 2010-02-11 2014-04-23 上海贝尔股份有限公司 Method and equipment for detecting and processing wireless link failure
EP2632226A1 (en) * 2010-10-21 2013-08-28 Nec Corporation Wireless communication system, method for controlling same, base station, method for controlling same, and computer-readable medium
US9088976B2 (en) * 2012-04-29 2015-07-21 Blackberry Limited Provisioning radio resources in a radio access network
JP6425707B2 (en) * 2014-03-19 2018-11-21 株式会社Nttドコモ User apparatus and uplink data transmission method
US20150304061A1 (en) * 2014-04-21 2015-10-22 Qualcomm Incorporated Synchronization at a radio link control (rlc) layer entity
WO2016021820A1 (en) * 2014-08-08 2016-02-11 Lg Electronics Inc. Method for processing a packet data convergence protocol re-ordering function at a user equipment in a dual connectivity system and device therefor
US10009925B2 (en) 2014-10-03 2018-06-26 Qualcomm Incorporated Physical layer procedures for LTE in unlicensed spectrum
WO2019153285A1 (en) * 2018-02-09 2019-08-15 Oppo广东移动通信有限公司 Configuration method for rlc entity, and related device

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030092458A1 (en) * 2001-11-13 2003-05-15 Lee-Chee Kuo Robust RLC reset procedure in a wireless communication system
US20030157927A1 (en) * 2002-02-16 2003-08-21 Lg Electronics Inc. Method for relocating SRNS in a mobile communication system
US20030206534A1 (en) * 2002-05-03 2003-11-06 Wu Frank Chih-Hsiang Scheme to handle radio link control service data units upon reception of a radio link control reset or reset acknowledge protocol data unit in a wireless communication system
US20030210714A1 (en) * 2002-05-10 2003-11-13 Chih-Hsiang Wu Method for avoiding loss of pdcp pdus in a wireless communications system
US20040203623A1 (en) * 2002-05-03 2004-10-14 Wu Frank Chih-Hsiang Scheme to retransmit radio resource control messages during a radio link control reset in a wireless communication system
US20040208160A1 (en) * 2003-03-31 2004-10-21 Dragan Petrovic Method of retransmission protocol reset synchronisation
US20050054298A1 (en) * 2003-09-10 2005-03-10 Rex Huan-Yueh Chen Handling of an unrecoverable error on a dedicated channel
US6904016B2 (en) * 2001-11-16 2005-06-07 Asustek Computer Inc. Processing unexpected transmission interruptions in a wireless communications system
US20060234706A1 (en) * 2002-11-05 2006-10-19 Pontus Wallentin Collective notification of node reset to subset of connections in radio access network
US20080095116A1 (en) * 2006-10-19 2008-04-24 Samsung Electronics Co., Ltd. Method and apparatus for performing handover using packet data convergence protocol (pdcp) reordering in mobile communication system
US20080123655A1 (en) * 2006-11-15 2008-05-29 Samsung Electronics Co., Ltd. Apparatus and method for transmitting/receiving ciphered packet in mobile communication system
US20080148136A1 (en) * 2006-12-13 2008-06-19 Samsung Electronics Co., Ltd Apparatus and method for transmitting/receiving data in a mobile communication system
US20080188224A1 (en) * 2007-02-02 2008-08-07 Interdigital Technology Corporation Method and apparatus for controlling a handover between utra r6 cells and r7 cells
US20080225817A1 (en) * 2004-12-24 2008-09-18 Ntt Docomo, Inc. Receiving Apparatus, Transmitting Apparatus, Communication System and Communication Method
US20090264127A1 (en) * 2005-10-04 2009-10-22 Sung-Duck Chun Optimized am rlc re-set mechanism

Family Cites Families (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0146536A1 (en) * 1983-05-27 1985-07-03 BILLET, Philippe Combined shaving cream tank-brush
FI106504B (en) * 1998-10-06 2001-02-15 Nokia Networks Oy The data segmentation method in a telecommunications system
JP3769153B2 (en) 1999-09-14 2006-04-19 ホシデン株式会社 Multi-directional input device
WO2003028304A1 (en) * 2001-09-27 2003-04-03 Broadcom Corporation Highly integrated media access control
KR100535295B1 (en) * 2002-05-06 2005-12-09 아스텍 컴퓨터 인코퍼레이티드 Method for handling abnormal cases for acknowledged mode transmission and unacknowledged mode transmission, and receiver therefor
EP2846592B1 (en) 2002-05-09 2016-06-08 Microsoft Technology Licensing, LLC HSDPA CQI, ACK, NACK power offset known in node B and in SRNC
CA2485559C (en) * 2002-05-10 2011-04-26 Interdigital Technology Corporation System for permitting control of the purging of a node b by the serving radio network controller
TWI317588B (en) * 2002-08-09 2009-11-21 Interdigital Tech Corp Method for sharing memory of wireless transmit receive unit and wireless transmit receive unit
EP1408658A3 (en) * 2002-08-13 2009-07-29 Innovative Sonic Limited Handling of an unrecoverable error on a dedicated channel of a radio link
US8694869B2 (en) * 2003-08-21 2014-04-08 QUALCIMM Incorporated Methods for forward error correction coding above a radio link control layer and related apparatus
US7983716B2 (en) 2003-09-30 2011-07-19 Interdigital Technology Corporation Centralized radio network controller
CN1879339B (en) * 2003-11-12 2010-08-18 Koninkl Philips Electronics Nv Data packet transmission
KR20050118591A (en) * 2004-06-14 2005-12-19 엘지전자 주식회사 Method for handling radio link control date in mobile communication system
US7391758B2 (en) * 2004-09-29 2008-06-24 Intel Corporation UMTS radio link control with full concatenation
EP1708413A1 (en) * 2005-03-29 2006-10-04 Lg Electronics Inc. Multimedia broadcast/multicast service (MBMS) cells reconfigurations
JP4577505B2 (en) 2005-03-31 2010-11-10 日本電気株式会社 Method for contention relief between downlink RRC message and inter-cell movement of mobile station in mobile communication system
US7761767B2 (en) * 2005-10-21 2010-07-20 Interdigital Technology Corporation Method and apparatus for retransmission management for reliable hybrid ARQ process
US20070291695A1 (en) * 2006-05-01 2007-12-20 Interdigital Technology Corporation Method and apparatus for facilitating lossless handover in 3gpp long term evolution systems
WO2007126192A1 (en) * 2006-05-02 2007-11-08 Lg Electronics Inc. Data transmission method in mobile communications system
EP1868311B1 (en) * 2006-06-16 2012-02-01 Panasonic Corporation Avoidance of retransmission requests in a packet retransmission scheme
KR100996069B1 (en) * 2006-11-27 2010-11-22 삼성전자주식회사 Method and apparatus for data transmission of radio link control layer in mobile telecommunication
JP5663168B2 (en) * 2006-12-15 2015-02-04 テレフオンアクチーボラゲット エル エム エリクソン(パブル) Single-bit segmentation indicator
JP4997294B2 (en) * 2007-03-16 2012-08-08 インターデイジタル テクノロジー コーポレーション Radio communication method and radio communication apparatus for supporting reconfiguration of radio link control parameters
US8068501B2 (en) * 2007-03-30 2011-11-29 Tektronix, Inc. System and method for real-time correlation of AAL2 and AAL5 messages for calls in UTRAN
KR100978320B1 (en) * 2007-04-19 2010-08-26 이노베이티브 소닉 리미티드 Method and apparatus for improving reordering functionality in a wireless communications system
US9307464B2 (en) 2007-06-21 2016-04-05 Sony Corporation Cellular communication system, apparatus and method for handover
US8270369B1 (en) * 2007-11-16 2012-09-18 Marvell International Ltd. Service data unit discard system for radio access networks
US20090175175A1 (en) 2008-01-04 2009-07-09 Interdigital Patent Holdings, Inc. Radio link control reset using radio resource control signaling
KR101488015B1 (en) * 2008-01-25 2015-01-29 엘지전자 주식회사 Method for Performing Handover Procedure and Creating Data
US8228938B2 (en) * 2009-02-02 2012-07-24 Samsung Electronics Co., Ltd. Method and apparatus for preventing a miss-detection of duplicated packets and an out-of-sequence delivery to the higher layer in unacknowledged mode operation
US8743896B2 (en) * 2009-03-16 2014-06-03 Htc Corporation Method and related communication device for radio link control reconfiguration in a wireless communications system
EP2622774A1 (en) * 2010-10-01 2013-08-07 InterDigital Patent Holdings, Inc. Mac and rlc architecture and procedures to enable reception from multiple transmission points
US9516524B2 (en) * 2011-10-25 2016-12-06 Mediatek, Inc. Transmitter assisted quality of service measurement
KR20140133345A (en) * 2013-05-10 2014-11-19 주식회사 팬택 Method and apparatus of transmitting data in wireless communication system supporting dual connectivity

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030092458A1 (en) * 2001-11-13 2003-05-15 Lee-Chee Kuo Robust RLC reset procedure in a wireless communication system
US6904016B2 (en) * 2001-11-16 2005-06-07 Asustek Computer Inc. Processing unexpected transmission interruptions in a wireless communications system
US20030157927A1 (en) * 2002-02-16 2003-08-21 Lg Electronics Inc. Method for relocating SRNS in a mobile communication system
US20040203623A1 (en) * 2002-05-03 2004-10-14 Wu Frank Chih-Hsiang Scheme to retransmit radio resource control messages during a radio link control reset in a wireless communication system
US20030206534A1 (en) * 2002-05-03 2003-11-06 Wu Frank Chih-Hsiang Scheme to handle radio link control service data units upon reception of a radio link control reset or reset acknowledge protocol data unit in a wireless communication system
US20030210714A1 (en) * 2002-05-10 2003-11-13 Chih-Hsiang Wu Method for avoiding loss of pdcp pdus in a wireless communications system
US20060234706A1 (en) * 2002-11-05 2006-10-19 Pontus Wallentin Collective notification of node reset to subset of connections in radio access network
US20040208160A1 (en) * 2003-03-31 2004-10-21 Dragan Petrovic Method of retransmission protocol reset synchronisation
US20050054298A1 (en) * 2003-09-10 2005-03-10 Rex Huan-Yueh Chen Handling of an unrecoverable error on a dedicated channel
US20080225817A1 (en) * 2004-12-24 2008-09-18 Ntt Docomo, Inc. Receiving Apparatus, Transmitting Apparatus, Communication System and Communication Method
US20090264127A1 (en) * 2005-10-04 2009-10-22 Sung-Duck Chun Optimized am rlc re-set mechanism
US20080095116A1 (en) * 2006-10-19 2008-04-24 Samsung Electronics Co., Ltd. Method and apparatus for performing handover using packet data convergence protocol (pdcp) reordering in mobile communication system
US20080123655A1 (en) * 2006-11-15 2008-05-29 Samsung Electronics Co., Ltd. Apparatus and method for transmitting/receiving ciphered packet in mobile communication system
US20080148136A1 (en) * 2006-12-13 2008-06-19 Samsung Electronics Co., Ltd Apparatus and method for transmitting/receiving data in a mobile communication system
US20080188224A1 (en) * 2007-02-02 2008-08-07 Interdigital Technology Corporation Method and apparatus for controlling a handover between utra r6 cells and r7 cells

Cited By (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100296454A1 (en) * 2008-02-01 2010-11-25 Sung-Jun Park Method of downlink harq operation at an expiry of time alignment timer
US20090207739A1 (en) * 2008-02-01 2009-08-20 Sung-Duck Chun Mobile communication system and method for transmitting pdcp status report thereof
US20090215456A1 (en) * 2008-02-01 2009-08-27 Lg Electronics Inc. Method for sending rlc pdu and allocating radio resource in mobile communications system and rlc entity of mobile communications
US9049018B2 (en) 2008-02-01 2015-06-02 Lg Electronics Inc. Method of an uplink HARQ operation at an expiry of time alignment timer
US8812925B2 (en) 2008-02-01 2014-08-19 Lg Electronics Inc. Method of an uplink harq operation at an expiry of time alignment timer
US8312336B2 (en) 2008-02-01 2012-11-13 Lg Electronics Inc. Method of an uplink HARQ operation at an expiry of time alignment timer
US20090204862A1 (en) * 2008-02-01 2009-08-13 Lg Electronics Inc. Method of an uplink harq operation at an expiry of time alignment timer
US9425926B2 (en) 2008-02-01 2016-08-23 Lg Electronics Inc. Method of an uplink HARQ operation at an expiry of time alignment timer
US8243657B2 (en) 2008-02-01 2012-08-14 Lg Electronics Inc. Method of downlink HARQ operation at an expiry of time alignment timer
US9008004B2 (en) 2008-02-01 2015-04-14 Lg Electronics Inc. Method for sending RLC PDU and allocating radio resource in mobile communications system and RLC entity of mobile communications
US9215742B2 (en) * 2008-03-20 2015-12-15 Innovative Sonic Limited Method and apparatus for improving RRC connection procedure
US9173242B2 (en) * 2008-03-20 2015-10-27 Innovative Sonic Limiited Method and apparatus for improving RRC connection procedure
US20090239563A1 (en) * 2008-03-20 2009-09-24 Ou Meng-Hui Method and Apparatus for Improving RRC Connection Procedure
US20120244866A1 (en) * 2008-03-20 2012-09-27 Innovative Sonic Limited Method and apparatus for improving rrc connection procedure
US8200226B2 (en) * 2008-03-20 2012-06-12 Innovative Sonic Limited Method and apparatus for improving RRC connection procedure
US20120243508A1 (en) * 2008-03-20 2012-09-27 Innovative Sonic Limited Method and apparatus for improving rrc connection procedure
US20090312007A1 (en) * 2008-03-21 2009-12-17 Nokia Corporation Re-establishment of a rlc entity
US8553569B2 (en) * 2008-05-19 2013-10-08 Innovative Sonic Limited Method of connection re-establishment and related communication device
US20090285111A1 (en) * 2008-05-19 2009-11-19 Ou Meng-Hui Method of connection re-establishment and related communication device
US20110206019A1 (en) * 2008-11-13 2011-08-25 Hengxing Zhai Synchronization Scheduling Method
US9107133B2 (en) 2009-01-06 2015-08-11 Qualcomm Incorporated Adaptation of handover parameters
US20100173633A1 (en) * 2009-01-06 2010-07-08 Qualcomm Incorporated Handover failure messaging schemes
US8929894B2 (en) * 2009-01-06 2015-01-06 Qualcomm Incorporated Handover failure messaging schemes
US20100173626A1 (en) * 2009-01-06 2010-07-08 Qualcomm Incorporated Adaptation of handover parameters
US9326213B2 (en) 2009-01-06 2016-04-26 Qualcomm Incorporated Adaptation of handover parameters
US8700029B2 (en) 2009-03-22 2014-04-15 Htc Corporation Method of handling radio link failure detection in a wireless communication system and related communication device
US20100240359A1 (en) * 2009-03-22 2010-09-23 Chih-Hsiang Wu Method of Handling Radio link Failure in a Wireless Communication System and Related Communication Device
US20100240357A1 (en) * 2009-03-22 2010-09-23 Chih-Hsiang Wu Method of Handling Radio link Failure Detection in a Wireless Communication System and Related Communication Device
US20130003542A1 (en) * 2011-07-01 2013-01-03 Qualcomm Incorporated Methods and apparatus for enhanced ul rlc flow control for mrab calls
US9232482B2 (en) 2011-07-01 2016-01-05 QUALOCOMM Incorporated Systems, methods and apparatus for managing multiple radio access bearer communications
US9167472B2 (en) * 2011-07-01 2015-10-20 Qualcomm Incorporated Methods and apparatus for enhanced UL RLC flow control for MRAB calls
US9591593B2 (en) 2011-07-22 2017-03-07 Qualcomm Incorporated Systems, methods and apparatus for radio uplink power control
US9930569B2 (en) 2011-08-04 2018-03-27 Qualcomm Incorporated Systems, methods and apparatus for wireless condition based multiple radio access bearer communications
US9686046B2 (en) 2011-09-13 2017-06-20 Qualcomm Incorporated Systems, methods and apparatus for wireless condition based multiple radio access bearer communications
US8873535B2 (en) 2011-09-26 2014-10-28 Qualcomm Incorporated Systems, methods and apparatus for retransmitting protocol data units in wireless communications
CN104662832A (en) * 2012-08-06 2015-05-27 高通股份有限公司 Method and apparatus for enhancing data retransmission to improve call performance
US9119190B2 (en) 2012-08-06 2015-08-25 Qualcomm Incorporated Method and apparatus for enhancing data retransmission to improve call performance
WO2014025755A1 (en) * 2012-08-06 2014-02-13 Qualcomm Incorporated Method and apparatus for enhancing data retransmission to improve call performance
WO2014035906A1 (en) * 2012-08-31 2014-03-06 Marvell World Trade Ltd. Method and apparatus for detecting and processing a retransmitted data packet in a wireless network
US9674730B2 (en) 2012-08-31 2017-06-06 Marvell World Trade Ltd. Method and apparatus for detecting and processing a retransmitted data packet in a wireless network
US20140274083A1 (en) * 2013-03-13 2014-09-18 Qualcomm Incorporated Method and apparatus for improving re-transmission of reconfiguration messages
US9071433B2 (en) * 2013-03-13 2015-06-30 Qualcomm Incorporated Method and apparatus for improving re-transmission of reconfiguration messages
CN105009495A (en) * 2013-03-13 2015-10-28 高通股份有限公司 Method and apparatus for improving re-transmission of reconfiguration messages
US20140293897A1 (en) * 2013-04-01 2014-10-02 Innovative Sonic Corporation Method and apparatus for adding serving cells in a wireless communication system
US9992693B2 (en) * 2013-04-01 2018-06-05 Innovative Sonic Corporation Method and apparatus for adding serving cells in a wireless communication system
US10212721B2 (en) 2013-04-01 2019-02-19 Marvell World Trade Ltd. Termination of wireless communication uplink periods to facilitate reception of other wireless communications
US9590792B2 (en) 2013-04-01 2017-03-07 Marvell World Trade Ltd. Termination of wireless communication uplink periods to facilitate reception of other wireless communications
US20160373962A1 (en) * 2013-10-17 2016-12-22 Zte Corporation Data package shunting transmission method and system, and computer stoarge medium
US10219162B1 (en) 2013-12-19 2019-02-26 Marvell International Ltd. Interference suppression or cancellation in collocated receivers
CN105577330A (en) * 2014-10-08 2016-05-11 展讯通信(上海)有限公司 Data retransmission system, data retransmission method and mobile terminal
CN109428687A (en) * 2017-07-21 2019-03-05 华为技术有限公司 The method and apparatus for triggering Radio Link Failure RLF

Also Published As

Publication number Publication date
TW201524173A (en) 2015-06-16
JP5883918B2 (en) 2016-03-15
CA2711241A1 (en) 2009-07-16
US20140161074A1 (en) 2014-06-12
KR101241056B1 (en) 2013-03-19
US20120093110A1 (en) 2012-04-19
KR20140101883A (en) 2014-08-20
SG187407A1 (en) 2013-02-28
EP2241045B1 (en) 2017-09-27
WO2009088903A2 (en) 2009-07-16
TW200931924A (en) 2009-07-16
KR101661830B1 (en) 2016-09-30
JP2013102442A (en) 2013-05-23
JP2015092723A (en) 2015-05-14
KR20100108444A (en) 2010-10-06
JP2016106489A (en) 2016-06-16
EP2241045A2 (en) 2010-10-20
US9596674B2 (en) 2017-03-14
CN101919195A (en) 2010-12-15
WO2009088903A3 (en) 2009-10-15
KR20140059282A (en) 2014-05-15
TWI470986B (en) 2015-01-21
TWI536788B (en) 2016-06-01
CN107070607A (en) 2017-08-18
US20150312896A1 (en) 2015-10-29
CA2711241C (en) 2014-10-14
JP2011509051A (en) 2011-03-17
KR20100106572A (en) 2010-10-01
US9167564B2 (en) 2015-10-20
JP5676549B2 (en) 2015-02-25
KR101571643B1 (en) 2015-11-24
JP5150734B2 (en) 2013-02-27
JP6189982B2 (en) 2017-08-30
US8693479B2 (en) 2014-04-08
NO2241045T3 (en) 2018-02-24

Similar Documents

Publication Publication Date Title
KR101122316B1 (en) Operation of control protocol data units in packet data convergence protocol
EP2137867B1 (en) Method and apparatus for reordering data in an evolved high speed packet access system
US9674874B2 (en) MAC reset and reconfiguration
AU2008214411B2 (en) Method and apparatus for controlling a handover between UTRA R6 cells and R7 cells
JP5357295B2 (en) Method and apparatus for processing error control messages in a wireless communication system
CN201444640U (en) Wireless transmitting/receiving unit used for executing reconstruction of Packet Data Convergence Protocol (PDCP)
EP1966925B1 (en) Method and apparatus for data security and automatic repeat request implementation in a wireless communication system
EP1263160A1 (en) Method and transmitter for an efficient packet data transfer in a transmission protocol with repeat requests
CN105721120B (en) Method and apparatus for triggering radio link control, RLC, re-establishment
JP2010541485A (en) PDCP discarding method and apparatus
EP2188952B1 (en) Method for transmitting status report of pdcp layer in mobile telecommunications system and receiver of mobile telecommunications
US20080043619A1 (en) Method and apparatus for controlling arq and harq transmissions and retransmissions in a wireless communication system
CN1285225C (en) Method for transmitting datum from radio chain-circuit control layer in radio communication system
US8891356B2 (en) System and method for multi-point HSDPA communication utilizing a multi-link RLC sublayer
KR20100053625A (en) Layer 2 tunneling of data during handover in a wireless communication system
US7817669B2 (en) Method and apparatus for supporting RLC re-segmentation
US9706418B2 (en) Retransmission of protocol data unit via alternate transmission path for dual connectivity wireless network
US8315242B2 (en) Method and apparatus for handling timers during reestablishing transmitting sides in wireless communications systems
TWI462626B (en) Wireless communication method and apparatus for supporting reconfiguration of radio link control parameters
EP1993226B1 (en) Method and related apparatus for handling re-establishment of radio link control entity in a wireless communications system
US7895494B2 (en) Method and system for implementing H-ARQ-assisted ARQ operation
TWM355514U (en) Apparatus for supporting configuration and control of the RLC and PDCP sub-layers
JP2009522873A (en) Method and system for H-ARQ assisted ARQ operation
EP2572466B1 (en) Method to control multiple radio access bearers in a wireless device
CN201378833Y (en) Wireless transmitting and receiving unit (WTRU)

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERDIGITAL PATENT HOLDINGS, INC., DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SOMASUNDARAM, SHANKAR;MUKHERJEE, RAJAT P.;SAMMOUR, MOHAMMED;AND OTHERS;REEL/FRAME:022366/0285;SIGNING DATES FROM 20090212 TO 20090225

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION