US8498284B2 - Method and apparatus for enhancing RLC for flexible RLC PDU size - Google Patents

Method and apparatus for enhancing RLC for flexible RLC PDU size Download PDF

Info

Publication number
US8498284B2
US8498284B2 US12/025,381 US2538108A US8498284B2 US 8498284 B2 US8498284 B2 US 8498284B2 US 2538108 A US2538108 A US 2538108A US 8498284 B2 US8498284 B2 US 8498284B2
Authority
US
United States
Prior art keywords
rlc
pdu
size
window
bytes
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.)
Active, expires
Application number
US12/025,381
Other languages
English (en)
Other versions
US20080212561A1 (en
Inventor
Diana Pani
James M. Miller
Paul Marinier
Stephen E. Terry
Sudheer A. Grandhi
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 Technology Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Technology Corp filed Critical InterDigital Technology Corp
Priority to US12/025,381 priority Critical patent/US8498284B2/en
Assigned to INTERDIGITAL TECHNOLOGY CORPORATION reassignment INTERDIGITAL TECHNOLOGY CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TERRY, STEPHEN E., GRANDHI, SUDHEER A., MILLER, JAMES M., MARINIER, PAUL, PANI, DIANA
Publication of US20080212561A1 publication Critical patent/US20080212561A1/en
Priority to US13/920,202 priority patent/US9554398B2/en
Application granted granted Critical
Publication of US8498284B2 publication Critical patent/US8498284B2/en
Priority to US15/375,357 priority patent/US9936423B2/en
Assigned to INTERDIGITAL PATENT HOLDINGS, INC. reassignment INTERDIGITAL PATENT HOLDINGS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INTERDIGITAL TECHNOLOGY CORPORATION
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/25—Flow control; Congestion control with rate being modified by the source upon detecting a change of network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
    • H04L47/365—Dynamic adaptation of the packet size
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access
    • H04W74/06—Scheduled access using polling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/22—Traffic shaping
    • H04L47/225—Determination of shaping rate, e.g. using a moving window
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • This application is related to wireless communications.
  • the Layer 2 radio interface protocols include medium access control (MAC) and radio link control (RLC) protocols.
  • MAC medium access control
  • RLC radio link control
  • the RLC protocol in Layer 2 has a big impact on the latency and throughput of data.
  • the RLC protocol in 3GPP legacy systems, including Release 6 and earlier, is physically located in the radio network controller (RNC) node.
  • RNC radio network controller
  • AM acknowledged mode
  • UM unacknowledged mode
  • TM transparent mode
  • AM acknowledge mode
  • UM unacknowledged mode
  • TM transparent mode
  • AM acknowledge mode
  • UM unacknowledged mode
  • TM transparent mode
  • the RLC protocol is bi-directional, such that status and control information is sent from Rx RLC entity to Tx RLC entity.
  • TM and UM operation which includes the transmission of some control plane radio resource control (RRC) signaling data
  • RRC radio resource control
  • the RLC protocol is unidirectional, such that the Tx RLC entity and Rx RLC entity are independent with no status and control information exchanged.
  • RRC radio resource control
  • some of the functions such as HARQ assisted ARQ and error detection and recovery are typically used only in AM operation.
  • the RLC PDU sizes are determined by the RRC layer based on the long term quality of service (QoS) requirements of the application data carried by the RLC logical channels.
  • QoS quality of service
  • the RLC layer is configured on a semi-static basis by the RRC layer with predetermined RLC PDU sizes.
  • the RLC PDU size is fixed on a semi-static basis by upper layers and sequence numbers (SNs) are assigned to the RLC PDUs.
  • AM data RLC PDUs are numbered by modulo integer sequence numbers (SNs) cycling through the field 0 to 4095.
  • the RLC PDU types are DATA, CONTROL and STATUS.
  • the DATA PDU is used to transfer user data, piggybacked STATUS information and the polling bit when RLC is operating in AM, where the polling bit is used to request a status report from the receiver.
  • the CONTROL PDU is used for RLC RESET and RESET acknowledgement (ACK) commands.
  • the STATUS PDU is used to exchange status information between two RLC entities operating in AM and can include super-fields (SUFIs) of different types including, for example, the Window Size SUFI and the Move Receiving Window (MRW) SUFI.
  • SUFIs super-fields
  • MMW Move Receiving Window
  • a transmission window refers to the group of PDUs that are being processed for transmission or are being transmitted currently.
  • the reception window generally refers to the group of PDUs being received or processed at the receiver.
  • the transmission or reception window size typically refers to a number of PDUs that are being transmitted or received, respectively, by the system.
  • the transmission and reception window sizes need to be managed using flow control in order not to overload the system and incur undesirable packet loss rates. Generally speaking, once a PDU has been successfully received at the receiver, a new PDU may be added to the transmission and/or reception window.
  • An RLC transmission window is composed of a lower bound and an upper bound.
  • the lower bound consists of the SN of the PDU with lowest SN transmitted and the upper bound consists of the SN of the PDU with the highest SN transmitted.
  • the RLC is configured with a maximum transmission window size, such that the maximum number of PDUs transmitted from the lower bound to the upper bound should not exceed the maximum window size.
  • the RLC reception window is similarly configured.
  • the lower bound of the RLC reception window is the SN following that of the last in-sequence PDU received and the upper bound is the SN of the PDU with the highest sequence number received.
  • the reception window also has maximum window size, where the maximum expected PDU SN is equal to the lower bound SN plus the maximum configured window size.
  • the transmission and reception windows are managed using transmission and reception state variables, respectively, as described hereinafter.
  • RNC/Node B flow control refers to the procedures to minimize the downlink data buffered in the Node B.
  • data destined for a UE flows from the Core Network (CN) through a source radio network controller (SRNC) and a Node B, and a drift radio network controller (DRNC) in a drift situation where the UE is handed off to a cell with a different radio network subsystem (RNS).
  • SRNC source radio network controller
  • DRNC drift radio network controller
  • the Node B grants allocation credits to the SRNC, and DRNC under drift, allowing the SRNC to send an equivalent number of PDUs to the Node B, such that the RNC can not send more PDUs until more credits are granted.
  • RLC flow control refers to the managing of packet transfer, including window size, between the Tx RLC entity and the Rx RLC entity.
  • RLC status reporting allows the receiver to report status information to the transmitter when polled by the transmitter.
  • RLC protocol parameters for flow control are signaled by upper layers to the RLC layer, including the following parameters:
  • RLC layer along with various RLC state variables for flow control in order to configure transmission and reception window size.
  • RLC state variables depend on SNs.
  • RLC transmitter state variables are affected by SNs:
  • VT(S), VT(A), VT(MS), VR(R), VR(H) and VR(MR) depend on one or more SNs.
  • the following RLC receiver state variables are also affected by SNs:
  • RLC radio link control
  • HSPA+ high speed packet access evolution
  • LTE long term evolution
  • RLC packet data unit (PDU) size is allowed
  • RLC PDU sizes are not fixed, radio network controller (RNC)/Node B flow control, RLC flow control, status reporting and polling mechanisms do not only depend on sequence numbers (SNs) or number of PDUs, but are configured to use byte count abased methods.
  • SNs sequence numbers
  • PDUs byte count abased methods.
  • the proposed byte count based methods for the RLC apply to both uplink and downlink communications.
  • FIG. 1 shows a structure of a super-field (SUFI) in an RLC STATUS packet data unit (PDU);
  • SUFI super-field
  • PDU packet data unit
  • FIG. 2 shows a flow diagram of a RNC/Node B flow control using a byte-based credit allocation in accordance with the teaching herein;
  • FIG. 3 shows a flow diagram of an RLC transmission (Tx) window update in accordance with the teaching herein;
  • FIG. 4 shows a flow diagram of an RLC reception (Rx) window update in accordance with the teaching herein;
  • FIG. 5 shows a flow diagram for enhanced octet-based RLC PDU creation in accordance with the teachings herein.
  • wireless transmit/receive unit 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.
  • base station includes but is not limited to a Node-B, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment.
  • RLC radio link control
  • PDU packet data unit
  • the proposed enhancements enable efficient operation of RLC functions when RLC PDU size is flexible, improving legacy RLC functions based on sequence numbers (SNs) that were designed for fixed RLC PDU size.
  • the proposed RLC enhancements apply to both uplink (UE to Universal Terrestrial Radio Access Network (UTRAN)) and downlink (UTRAN to UE) communications, and may be used in any wireless communication system including, but not limited to, high speed packet access evolution (HSPA+), long term evolution (LTE) and wideband code division multiple access (WCDMA) systems.
  • HSPA+ high speed packet access evolution
  • LTE long term evolution
  • WCDMA wideband code division multiple access
  • UTRAN is equivalent to evolution UTRAN (E-UTRAN).
  • the proposed RLC enhancements may be used in architecture where the RLC operates either fully in the Node B, or partially in the RNC and partially in the Node-B.
  • the proposed RLC enhancements are principally described herein with reference to HSPA+. Many functions and parameters are based on functions and parameters for HSDPA and HSUPA and may be understood in conjunction with 3GPP technical specifications (TSs) including the 3GPP RLC Protocol Specification for Release 7 (see 3GPP TS 25.322 V. 7.2.0) which is incorporated herein. It is assumed that the RLC can be configured by the higher layers to support flexible PDU size with a specified maximum RLC PDU payload size. It also assumed that the maximum RLC PDU size may be inferred from the specified maximum RLC PDU payload size. Alternatively, the maximum RLC PDU size may be directly specified. Also, the terms bytes and octets are used interchangeably, as well as terms transmitter and sender.
  • One or more of the following metrics may be used, alone or in combination, for defining and managing window size when flexible RLC PDU size is configured by the RRC:
  • the metric(s) used for window definition are signaled and negotiated during RRC setup, configuration and reconfiguration procedures for the radio bearer.
  • the metric(s) for window size listed hereinbefore may be applied in all messaging that updates the window for flow control during a connection.
  • the window size metrics may be included in the Window Size super-field (SUFI) and Move Receiving Window (MRW) SUFI in RLC CONTROL or STATUS PDUs.
  • SUFI Window Size super-field
  • MMW Move Receiving Window
  • any one or more of the following information may be provided by the RRC to the RLC to signal the use of flexible RLC PDU size:
  • a Window Size Super Field used by the receiver to configure the window size of the transmitter, is configured to provide an octet quantity.
  • This enhancement is used when flexible RLC PDU size mode is set by RRC as described above, and may be specified in two ways:
  • Enhancements to RNC/Node B flow control are described herein for the case where the RLC entity is retained in the RNC. However, similar enhancements may be defined where the RLC entity is in the RNC and the Node B.
  • a data MAC (MAC-d) entity may be retained in the RNC to receive RLC PDUs and forward them to the high speed MAC (MAC-hs) entity in the NodeB after applying appropriate header information.
  • the Node B sends capacity allocation frames to a serving RNC (SRNC), and possibly control RNC (CRNC), indicating the maximum PDU size and number of PDUs that can be sent. Additionally, parameters can be sent so that the allocation is periodic for a fixed number of periods or for an indefinite period of time.
  • SRNC serving RNC
  • CRNC control RNC
  • the number of MAC PDUs sent from the RNC to the Node B and the corresponding time interval for transmission is regulated by a flow control algorithm, which is based upon a credit allocation scheme. Credits represent the number of MAC-d PDUs that may be transmitted.
  • the RNC requests credits and the Node B grants them along with a specified time interval for transmission.
  • the MAC-d PDU size is therefore also variable. Thus, it is insufficient to specify the number of credits in terms of the number of MAC-d PDUs.
  • One possibility is to eliminate RNC/Node B flow control, however, this would require relying on user data protocols such as transport control protocol (TCP) to do the flow control for the network, and additionally handle the interaction between the TCP window and the RLC window.
  • TCP transport control protocol
  • the credit allocation can be specified in bytes instead of in number of PDUs, which can be done in two ways.
  • a new field may be added to existing frames to specify the number of bytes of credits instead of the number of PDUs.
  • an indication can be signaled at radio bearer setup or reconfiguration, or in each applicable control frame using an existing control frame or a new control frame, which indicates that the allocation is actually a byte allocation by multiplying the credit by the maximum PDU size in bytes producing a byte total. Accordingly, the maximum number of PDUs that can be transferred from the RNC to the Node B would not equal the signaled credit in terms of a number of PDUs, but would be limited by the total number of bytes in the PDUs.
  • the RNC may optionally maintain a mapping of the PDU SN to its length in bytes. Once the RNC receives the credit allocation from the Node B, it is allowed to transmit as many PDUs as it can without violating the byte length constraint specified by the new byte-length based credit allocation.
  • FIG. 2 shows a flow diagram of a RNC/Node B flow control using a byte-based credit allocation.
  • a Node B signals a credit allocation in bytes (step 205 ).
  • An RNC receives the credit allocation in bytes (step 210 ).
  • the RNC maintains a mapping of PDU SN to PDU length in bytes (step 220 ), and transmits PDUs without exceeding the received credit allocation (step 220 ).
  • RLC flow control is achieved by advancing the RLC Tx window when the PDU at the lower end of the utilized transmission (Tx) window is positively acknowledged, and thus received correctly, while still staying within the limits imposed by the maximum window size.
  • the PDU at the lower end of the Tx window is defined as the PDU following the last in-sequence PDU acknowledged. For the case when flexible RLC PDU size is configured, appropriate steps should be taken so that the maximum window size limit is not violated.
  • the Tx window size is specified in terms of bytes.
  • FIG. 3 shows a flow diagram for a method for updating an RLC transmission (Tx) window 300 .
  • an RLC Tx operation is executed (step 305 ).
  • An RLC Tx operation may be, for example, the reception of status and control information form the RLC receiver.
  • the RLC Tx entity decides whether or not to remove one or more PDUs from the utilized Tx window and increase the lower end the utilized Tx window (step 310 ).
  • One or more PDUs may be removed if:
  • the RLC Tx entity determines if the WL quantity is less than the maximum window size TxWMAX (step 320 ). If WL is not less than TxWMAX, then the next one or more PDUs are not transmitted and the upper end of the window is not increased (step 325 ). If WL is less than TxWMAX, then the next one or more PDUs are transmitted and the upper end of the window is increased (step 330 ).
  • FIG. 4 shows a flow diagram of a method for updating an RLC reception (Rx) window 400 in accordance with the teachings herein.
  • Rx RLC reception
  • An RLC Rx operation is executed (step 405 ).
  • An RLC Rx operation may be, for example, the reception of a new PDU.
  • the RLC Rx entity decides whether or not to increase the lower end the Rx window (step 410 ).
  • the RLC Rx entity may increase the lower end of its Rx window and thereby decrease RxWUTIL if:
  • the RLC Rx entity determines if the WL quantity is less than the maximum window size RxWMAX (step 420 ). If WL is not less than RxWMAX, then the next PDU(s) are not received and the upper end of the Rx window is not increased (step 425 ). If WL is less than RxWMAX, then the next PDU(s) are received, without discarding the PDU with a SN following that of the highest received SN, and the upper end of the Rx window is increased ( 430 ).
  • AM data RLC PDUs are numbered by modulo integer sequence numbers (SN) cycling through a field.
  • SN modulo integer sequence numbers
  • this field ranges from 0 to 4095, although a different maximum value may be configured by the RRC or other upper layers.
  • arithmetic operations on VT(S), VT(A), VT(MS), VR(R), VR(H) and VR(MR) are affected by the SN modulus.
  • a parameter or state variable Maximum_Tx_Window_Size in octets may be maintained by the RLC transmitter. This parameter is initially set equal to the protocol parameter Configured_Tx_Window_Size in octets sent by the upper layers, and may be updated later to an octet quantity indicated by the Window Size SUFI in a RLC STATUS PDU.
  • the state variable VT(WS) may be derived from the Maximum_Tx_Window_Size in octets, and may be set equal to the largest non-negative integer not greater than 4095 (or a maximum value configured by RRC/upper layers), such that the octet length of the window bounded by VT(A) and VT(A)+VT(WS) does not exceed the Maximum_Tx_Window_Size in octets.
  • the state variable VT(WS) is updated when the Maximum_Tx_Window_Size in octets is updated.
  • the state variable VT(WS) may be derived as the largest non-negative integer not greater than 4095 (or a maximum value configured by RRC/upper layers), such that the octet length of the window bounded by VT(A) and VT(A)+VT(WS) does not exceed:
  • the state variable VR(MR) is a SN derived from the Configured_Rx_Window_Size in octets sent by upper layers, such that the length in octets of the window bounded by VR(R) and VR(MR) is as large as possible but not exceeding the Configured_Rx_Window_Size in octets.
  • FIG. 5 shows a flow diagram for a method for enhanced octet-based RLC PDU creation 500 for both uplink and downlink, based on the following parameters:
  • X Min ⁇ Current_Credit, Available_Data, Leftover_Window ⁇ Equation (3)
  • N Floor ⁇ X /Maximum_RLC_PDU_size ⁇ Equation (4)
  • L X mod Maximum_RLC_PDU_size Equation (5) where the function Min ⁇ • ⁇ returns the minimum value from the set, the function Floor ⁇ • ⁇ returns the nearest lower integer value, and a mod b is the modulo b division of a.
  • N RLC PDUs of size Maximum_RLC_PDU_size are generated (step 505 ).
  • one additional RLC PDU may be created for the TTI. It is determined if X is equal to the Leftover_Window or Current_Credit parameters (step 510 ). If so, it is determined if L is greater than the Minimum_RLC_PDU_size parameter or if X is equal to the Available_Data ( 515 ). If L is greater than the Minimum_RLC_PDU_size, or if X is equal to the Available_Data, then an RLC PDU of length L is generated ( 520 ). Also, if X is not equal to Leftover_Window or Current_Credit, then an RLC PDU of length L is generated ( 520 ).
  • an RLC PDU of Minimum_RLC_PDU_size may be created.
  • the generated RLC PDU(s) are stored in a buffer for transmission ( 525 ).
  • the method 500 may be repeated every TTI, or alternatively when data is available or requested by lower layers ( 530 ).
  • Min ⁇ Current_Credit, Available_Data, Leftover_Window ⁇ Available_Data
  • another RLC PDU may also be generated in the same period of size equal to Min ⁇ Current_Credit, Leftover_Window, Available_Data ⁇ mod Maximum_RLC_PDU_size.
  • Min ⁇ Current_Credit, Available_Data, Leftover_Window ⁇ Leftover_Window
  • another RLC PDU may also be generated in the same period of size equal to Min ⁇ Current_Credit, Leftover_Window, Available_Data ⁇ mod Maximum_RLC_PDU_size, if and only if this PDU's length is greater than Minimum_RLC_PDU_size.
  • Variable size RLC PDU creation may also be applied without the Minimum_RLC_PDU_size and/or the Maximum_RLC_PDU_size limitations.
  • a RLC PDU of size X can be created in a system where parameters minimum_RLC_PDU_size and maximum_RLC_PDU_size are not defined.
  • the current state variables used for fixed RLC PDU size are maintained and can be used simultaneously with a set of new variables that deal with the byte count of flexible RLC PDUs. More specifically, some of the values maintained in terms of number of PDUs and processed as in the non-enhanced RLC may include:
  • VT(WS) is maintained in terms of maximum number of PDUs and it is originally configured by higher layers based on the Configured_Tx_Window_size parameter provided in number of PDUs. This value can correspond to the maximum number of PDUs allowed for the window, and/or the maximum number of PDUs limited by the number of bits used for the sequence number. For example, if 12 bits are used then up to 2 12 or 4096 PDUs can be supported.
  • the VT(WS) can be prohibited from being updated by the receiver using the WINDOW SUFI.
  • the other receiver state variables may also be maintained and processed according to 3GPP legacy standards.
  • variables dealing with the byte count for the transmitter and receiver are also maintained and processed.
  • Some variables that can be used are listed below, and are assumed to be maintained in terms of bytes. The names of these variables are used for description purposes but may be given any name.
  • the variables include:
  • the combination of the old and new state variables will allow the RLC to control the Tx and Rx windows in terms of maximum amount of bytes allowed and also in terms of maximum number of PDUs allowed (limited by the number of sequence numbers available for transmission).
  • the transmitter has to ensure that the SN of the AMD PDU is less than the maximum send variable VT(MS).
  • the SN of retransmitted AMD PDU might be greater than VT(MS) if the window size has been updated by the receiver using WINDOW SUFI.
  • the transmitter can also check that the Tx window utilization up to the AMD PDU to be retransmitted does not exceed the maximum window size in bytes using state variable VT(WS)_bytes.
  • the state variable Window_utilization is the total size of transmitted RLC PDUs in the retransmission buffer. Therefore, when this condition is checked the utilization up to the retransmitted SN has to be calculated independently. If Window_utilization is less than VT(WS)_bytes, then the condition will be met automatically, however if window_utilization is greater than VT(WS)_bytes, the buffer utilization up to the AMD PDU has to be calculated in order to ensure that it will not exceed VT(WS)_bytes. So optionally, the buffer utilization is calculated if the window_utilization exceeds the state variable VT(WS)_bytes.
  • the AMD PDU transmission procedure can be modified in the following way to account for fixed and flexible RLC PDU sizes, as signaled by upper layers:
  • One of the conditions to allow the transmission of an AMD PDU is that the AMD PDU SN is less than the state variable VT(MS).
  • VT(MS) the state variable
  • an additional condition to check that the window utilization for the transmitted or retransmitted PDU does not exceed maximum window size in bytes should also be verified.
  • the lower layers include the MAC layer and physical layer.
  • the sender may:
  • Timer_Poll a timer for tracking AMD PDU containing a poll as indicated by lower layers, is configured, then start the timer Timer_Poll (see, for example, 3GPP TS 25.322 V7.1.0 subclause 9.5).
  • the procedure associated with the reception of an AMD PDU by the receiver is updated to include and update of the receiver state variables associated with the byte count for flexible RLC PDU size.
  • the enhanced procedure is defined as follows. Upon reception of an AMD PDU, the receiver shall:
  • the receiver upon reception of an AMD PDU with SN outside the interval VR(R) ⁇ SN ⁇ VR(MR), the receiver shall:
  • the receiver upon reception of a new AMD PDU whose size added to RxWUTIL exceeds RxWMAX (where RxWMAX ⁇ RxWUTIL+new received AMD PDU size or RxN) or upon reception of an AMD PDU with SN outside the interval VR(R) ⁇ SN ⁇ VR(MR), the receiver shall:
  • RLC status reports containing acknowledgment information to support ARQ may be triggered in various scenarios by the RLC Tx and RLC Rx entities.
  • the RLC Tx and RLC Rx entities can maintain a mapping of RLC PDU SN to the corresponding PDU length in bytes. This allows the calculation and maintenance of the length of the used flow control window in bytes or other byte-based metrics as described above.
  • the transmitter may have a PDU count polling mechanism and/or a byte count polling mechanism, such that the transmitter polls the receiver every Poll_Bytes bytes.
  • the polling parameter provided by higher layers is called Poll_Bytes.
  • the RLC transmitter may trigger a status report by setting the polling bit in certain PDUs as follows:
  • setting a polling bit refers to a polling request, such that a polling request may consist of POLL SUFI PDU, or it may consist of the setting of a polling bit in an AMD RLC PDU.
  • the total number of bytes transmitted in PDUs may refer to the size of the PDUs transmitted for the first time. Alternatively, it can refer to the size of all PDUs transmitted, including retransmissions.
  • the counted total number of bytes transmitted may only count the first transmission of the RLC acknowledged mode data (AMD) PDU, the RLC AMD PDU segment or a portion of an RLC SDU, where retransmissions of these data portions may not be counted.
  • AMD RLC acknowledged mode data
  • Protocol parameters Poll_PDU and Poll_SDU are signaled by upper layers, such as the RRC, to the RLC layer to indicate a PDU count interval.
  • protocol parameter Poll_Bytes in octets can be signaled and configured by higher layers. Polling procedures in an RLC transmitter may include the following:
  • the Poll_Octets counter may optionally count a total number of bytes of a first transmission of each RLC acknowledged mode data (AMD) PDU.
  • the Poll_Octets counter may optionally count only RLC data PDUs, such that RLC control PDUs are not counted.
  • the RLC transmitter sets the polling bit in the PDU (or optionally, the next PDU) that makes the Poll_Octets counter exceed the threshold of Poll_Bytes, and resets the Poll_Octets counter.
  • the Poll_Octets counter may also be reset if the polling bit is set due to other polling conditions such as the reception of a Poll_PDU.
  • Flexible RLC PDU size mode is set by the RRC layer, and window-based polling is configured by upper layers, protocol parameter Poll_Window is signaled by upper layers to the RLC to inform the transmitter to poll the receiver.
  • Poll_Window can be given in terms of a percentage window or in terms of number of bytes.
  • the utilized_window represents the utilized buffer by the data remaining in the transmission buffer. If the Poll_Window is given in terms of number of bytes, K is equivalent to the utilized_window. Therefore, the transmitter will trigger a polling request if the utilized_window exceeds the number of bytes Poll_window signaled by the network.
  • the RLC transmitter can trigger a status report by setting the polling bit when the used/utilized Tx window size is above a certain system configured threshold in terms of a number of bytes or a percentage of the maximum window size.
  • the RLC receiver can trigger a status report when the used/utilized Rx window size is above a certain system configured threshold in terms of a number of bytes or a percentage of the maximum window size.
  • Poll_Window indicates when the transmitter shall poll the receiver in the case where “window-based polling” is configured by upper layers.
  • a poll is triggered for each AMD PDU when: the value J is greater than parameter Poll_Window, where J is the transmission window percentage defined as:
  • a poll is also triggered for each AMD PDU when the value of K is greater than parameter Poll_Window, where K is defined as:
  • ROM read only memory
  • RAM random access memory
  • 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.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • 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.
  • WLAN wireless local area network
  • UWB Ultra Wide Band

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Environmental & Geological Engineering (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
US12/025,381 2007-02-02 2008-02-04 Method and apparatus for enhancing RLC for flexible RLC PDU size Active 2031-05-14 US8498284B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US12/025,381 US8498284B2 (en) 2007-02-02 2008-02-04 Method and apparatus for enhancing RLC for flexible RLC PDU size
US13/920,202 US9554398B2 (en) 2007-02-02 2013-06-18 Method and apparatus for enhancing RLC for flexible RLC PDU size
US15/375,357 US9936423B2 (en) 2007-02-02 2016-12-12 Method and apparatus for enhancing RLC for flexible RLC PDU size

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US88783107P 2007-02-02 2007-02-02
US89547107P 2007-03-18 2007-03-18
US91372807P 2007-04-24 2007-04-24
US12/025,381 US8498284B2 (en) 2007-02-02 2008-02-04 Method and apparatus for enhancing RLC for flexible RLC PDU size

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/920,202 Continuation US9554398B2 (en) 2007-02-02 2013-06-18 Method and apparatus for enhancing RLC for flexible RLC PDU size

Publications (2)

Publication Number Publication Date
US20080212561A1 US20080212561A1 (en) 2008-09-04
US8498284B2 true US8498284B2 (en) 2013-07-30

Family

ID=39620177

Family Applications (3)

Application Number Title Priority Date Filing Date
US12/025,381 Active 2031-05-14 US8498284B2 (en) 2007-02-02 2008-02-04 Method and apparatus for enhancing RLC for flexible RLC PDU size
US13/920,202 Active 2028-08-29 US9554398B2 (en) 2007-02-02 2013-06-18 Method and apparatus for enhancing RLC for flexible RLC PDU size
US15/375,357 Active US9936423B2 (en) 2007-02-02 2016-12-12 Method and apparatus for enhancing RLC for flexible RLC PDU size

Family Applications After (2)

Application Number Title Priority Date Filing Date
US13/920,202 Active 2028-08-29 US9554398B2 (en) 2007-02-02 2013-06-18 Method and apparatus for enhancing RLC for flexible RLC PDU size
US15/375,357 Active US9936423B2 (en) 2007-02-02 2016-12-12 Method and apparatus for enhancing RLC for flexible RLC PDU size

Country Status (16)

Country Link
US (3) US8498284B2 (enrdf_load_stackoverflow)
EP (2) EP2429235B1 (enrdf_load_stackoverflow)
JP (3) JP5258791B2 (enrdf_load_stackoverflow)
KR (4) KR20140015620A (enrdf_load_stackoverflow)
CN (2) CN101675627A (enrdf_load_stackoverflow)
AR (1) AR065158A1 (enrdf_load_stackoverflow)
AU (1) AU2008214378B2 (enrdf_load_stackoverflow)
BR (1) BRPI0806396B1 (enrdf_load_stackoverflow)
CA (1) CA2677112C (enrdf_load_stackoverflow)
IL (1) IL200075A (enrdf_load_stackoverflow)
MX (1) MX2009008015A (enrdf_load_stackoverflow)
MY (1) MY154157A (enrdf_load_stackoverflow)
RU (1) RU2455776C2 (enrdf_load_stackoverflow)
SG (1) SG178738A1 (enrdf_load_stackoverflow)
TW (3) TWI499259B (enrdf_load_stackoverflow)
WO (1) WO2008097544A2 (enrdf_load_stackoverflow)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130088959A1 (en) * 2011-10-06 2013-04-11 International Business Machines Corporation Credit-based network congestion management
US8798080B2 (en) 2011-05-14 2014-08-05 International Business Machines Corporation Distributed fabric protocol (DFP) switching network architecture
US8797843B2 (en) 2011-09-12 2014-08-05 International Business Machines Corporation High availability distributed fabric protocol (DFP) switching network architecture
US8824485B2 (en) 2011-05-13 2014-09-02 International Business Machines Corporation Efficient software-based private VLAN solution for distributed virtual switches
US8856801B2 (en) 2011-05-14 2014-10-07 International Business Machines Corporation Techniques for executing normally interruptible threads in a non-preemptive manner
US8948003B2 (en) 2011-06-17 2015-02-03 International Business Machines Corporation Fault tolerant communication in a TRILL network
US9059922B2 (en) 2011-10-06 2015-06-16 International Business Machines Corporation Network traffic distribution
US9392515B2 (en) * 2010-02-12 2016-07-12 Interdigital Technology Corporation Data split between multiple sites
US20170019807A1 (en) * 2007-09-11 2017-01-19 Optis Cellular Technology, Llc Method for transmitting status report of pdcp layer in mobile telecommunications system and receiver of mobile telecommunications
US9585008B2 (en) 2013-04-19 2017-02-28 Qualcomm Incorporated Apparatus and methods for signaling out-of-standard capability in wireless communication networks
US9699779B2 (en) 2012-08-23 2017-07-04 Interdigital Patent Holdings, Inc. Physical layer operation for multi-layer operation in a wireless system
US9705803B1 (en) 2015-06-10 2017-07-11 Sprint Communications Company L.P. Negotiated radio link properties among wireless access nodes
US9763282B2 (en) 2012-08-23 2017-09-12 Interdigital Patent Holdings, Inc. Operating with multiple schedulers in a wireless system
US10298509B2 (en) * 2016-03-17 2019-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Managing a sequence number range for radio link control entities in a radio access network during an on-going connection
US10560944B2 (en) 2010-12-03 2020-02-11 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for performing multi-radio access technology carrier aggregation
US11838849B2 (en) 2011-07-29 2023-12-05 Interdigital Patent Holdings, Inc. Methods and apparatus for radio resources management in multi-radio access technology wireless systems

Families Citing this family (81)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
NZ529698A (en) 2001-04-23 2005-04-29 Drykor Ltd Apparatus for conditioning air
MX2009008015A (es) 2007-02-02 2009-09-04 Interdigital Tech Corp Metodo y aparato para mejorar rlc para tamaño de pdu de rlc flexible.
ATE504187T1 (de) 2007-02-06 2011-04-15 Ericsson Telefon Ab L M Flexible funkverbindungssteuerpaketdateneinheitslänge
US8619752B2 (en) * 2007-03-16 2013-12-31 Qualcomm Incorporated Method and apparatus for polling in a wireless communication system
US8687495B2 (en) * 2007-03-16 2014-04-01 Qualcomm Incorporated Method and apparatus for polling in a wireless communication system
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
KR101341515B1 (ko) 2007-06-18 2013-12-16 엘지전자 주식회사 무선 통신 시스템에서의 반복 전송 정보 갱신 방법
KR101486352B1 (ko) 2007-06-18 2015-01-26 엘지전자 주식회사 무선 통신 시스템의 단말에서의 상향링크 동기 상태 제어방법
KR101470637B1 (ko) * 2007-06-18 2014-12-08 엘지전자 주식회사 이동통신 시스템에서의 무선자원 향상 방법, 상태정보 보고방법 및 수신장치
WO2008156314A2 (en) 2007-06-20 2008-12-24 Lg Electronics Inc. Effective system information reception method
KR101490253B1 (ko) 2007-08-10 2015-02-05 엘지전자 주식회사 무선 통신 시스템에서의 제어정보 전송 및 수신 방법
KR101479341B1 (ko) * 2007-08-10 2015-01-05 엘지전자 주식회사 Ｍｂｍｓ 서비스를 제공하는 무선 통신 시스템에서효율적인 수신 방법
KR20090016419A (ko) 2007-08-10 2009-02-13 엘지전자 주식회사 동적 무선자원 할당방법에서 ｈａｒｑ를 제어하는 방법
KR101514841B1 (ko) 2007-08-10 2015-04-23 엘지전자 주식회사 효율적인 랜덤 액세스 재시도를 수행하는 방법
US8488523B2 (en) 2007-08-14 2013-07-16 Lg Electronics Inc. Method of transmitting and processing data block of specific protocol layer in wireless communication system
KR100937432B1 (ko) 2007-09-13 2010-01-18 엘지전자 주식회사 무선 통신 시스템에서의 무선자원 할당 방법
KR101461970B1 (ko) 2007-09-13 2014-11-14 엘지전자 주식회사 무선 통신 시스템에서의 폴링 과정 수행 방법
KR101513033B1 (ko) 2007-09-18 2015-04-17 엘지전자 주식회사 다중 계층 구조에서 ＱｏＳ를 보장하기 위한 방법
KR101591824B1 (ko) * 2007-09-18 2016-02-04 엘지전자 주식회사 무선 통신 시스템에서의 폴링 과정 수행 방법
KR101396062B1 (ko) 2007-09-18 2014-05-26 엘지전자 주식회사 헤더 지시자를 이용한 효율적인 데이터 블록 전송방법
KR101435844B1 (ko) 2007-09-18 2014-08-29 엘지전자 주식회사 무선 통신 시스템에서의 데이터 블록 전송 방법
WO2009038377A2 (en) 2007-09-20 2009-03-26 Lg Electronics Inc. Method of effectively transmitting radio resource allocation request in mobile communication system
KR20090041323A (ko) 2007-10-23 2009-04-28 엘지전자 주식회사 데이터 블록 구성함에 있어서 단말의 식별 정보를 효과적으로 전송하는 방법
KR101487557B1 (ko) 2007-10-23 2015-01-29 엘지전자 주식회사 공통제어채널의 데이터를 전송하는 방법
WO2009057941A2 (en) * 2007-10-29 2009-05-07 Lg Electronics Inc. A method for repairing an error depending on a radion bearer type
EP2218042B1 (en) 2007-11-14 2020-01-01 Varcode Ltd. A system and method for quality management utilizing barcode indicators
US8401017B2 (en) * 2008-01-03 2013-03-19 Sunplus Mmobile Inc. Wireless communication network using an enhanced RLC status PDU format
EP3998724B1 (en) 2008-01-08 2023-09-06 Unwired Planet International Limited Method and arrangement in a wireless communication network for requesting a status report
WO2009096746A2 (en) * 2008-02-01 2009-08-06 Lg Electronics Inc. Method for sending rlc pdu and allocating radio resource in mobile communications system and rlc entity of mobile communications
KR101531419B1 (ko) 2008-02-01 2015-06-24 엘지전자 주식회사 시간동기 타이머의 만료 시 상향링크 ｈａｒｑ의 동작 방법
KR101375936B1 (ko) 2008-02-01 2014-03-18 엘지전자 주식회사 시간동기 타이머의 만료 시 하향링크 ｈａｒｑ의 동작 방법
WO2009116788A1 (en) 2008-03-17 2009-09-24 Lg Electronics Inc. Method of transmitting rlc data
KR101163275B1 (ko) 2008-03-17 2012-07-05 엘지전자 주식회사 Ｐｄｃｐ 상태 보고 전송 방법
US8031600B2 (en) * 2008-05-20 2011-10-04 Htc Corporation Method and related apparatus for performing status report procedure in a wireless communication system
EP2600651B1 (en) 2008-08-01 2016-09-07 NEC Corporation Mobile communication system, control device, base station device, system control method and device control method for data communication using fixed or variable length data size
US9137160B2 (en) 2009-01-29 2015-09-15 Qualcomm Incorporated Method and apparatus for accomodating a receiver buffer to prevent data overflow
US8473802B2 (en) * 2009-06-30 2013-06-25 Samsung Electronics Co., Ltd. Technique for advanced ARQ buffer management in wireless communication system
WO2011125002A1 (en) * 2010-04-09 2011-10-13 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic adaptation of downlink rlc pdu size
US8891356B2 (en) 2010-06-28 2014-11-18 Qualcomm Incorporated System and method for multi-point HSDPA communication utilizing a multi-link RLC sublayer
US20120163205A1 (en) * 2010-06-28 2012-06-28 Qualcomm Incorporated System and method for flow control in a multi-point hsdpa communication network
US8989140B2 (en) 2010-06-28 2015-03-24 Qualcomm Incorporated System and method for mobility in a multi-point HSDPA communication network
US8989004B2 (en) 2010-11-08 2015-03-24 Qualcomm Incorporated System and method for multi-point HSDPA communication utilizing a multi-link PDCP sublayer
WO2012071283A1 (en) * 2010-11-22 2012-05-31 Michael Luna Aligning data transfer to optimize connections established for transmission over a wireless network
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
US9055464B2 (en) 2011-07-07 2015-06-09 Optis Cellular Technology, Llc RLC Data transmission control based on UE memory capacity
US9591593B2 (en) 2011-07-22 2017-03-07 Qualcomm Incorporated Systems, methods and apparatus for radio uplink power control
US8737211B2 (en) 2011-08-03 2014-05-27 Qualcomm Incorporated Methods and apparatuses for network configuration of user equipment communication modes in multiflow systems
US9125098B2 (en) 2011-08-03 2015-09-01 Qualcomm Incorporated Method and apparatus for flow congestion control in multiflow networks
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
TWI511588B (zh) * 2011-11-07 2015-12-01 Acer Inc 最佳化通訊協定之視窗大小伸縮以在無線網路系統內傳送資料之方法
CN105897385A (zh) * 2011-11-24 2016-08-24 华为技术有限公司 Rlc数据包传输的确认方法及rlc am实体发送方
GB2491050B (en) * 2012-07-12 2014-12-10 Broadcom Corp Wireless communication system and method
EP2888907A4 (en) * 2012-08-21 2016-06-01 Nokia Technologies Oy METHOD AND APPARATUS FOR WIRELESS COMMUNICATION IN A HETEROGENEOUS NETWORK
DE102013223303B4 (de) 2012-11-19 2023-08-17 Avago Technologies International Sales Pte. Ltd. System und Verfahren für eine Gutpunkt basierte Verbindungspegelflusssteuerung
EP2916572B1 (en) * 2012-11-29 2019-01-09 Huawei Technologies Co., Ltd. Method, apparatus and system for controlling data transmission
CN104641719B (zh) * 2013-05-20 2018-07-03 华为技术有限公司 一种确认报文发送方法及其设备
US9838158B2 (en) 2013-07-17 2017-12-05 Lg Electronics Inc. Method for reporting a radio link control re-transmission failure and a device therefor
US20150085749A1 (en) * 2013-09-26 2015-03-26 Qualcomm Incorporated Mechanism to exchange proprietary signaling messages between a ue and a network
HUE042235T2 (hu) * 2014-01-30 2019-06-28 Intel Ip Corp MTC UE és eljárás fedettség javításra rádiókapcsolat vezérlési konfiguráció használatával
CN105007137B (zh) * 2014-04-23 2018-10-23 电信科学技术研究院 一种rlc层的数据包处理方法和rlc实体
CN105264830B (zh) * 2014-05-09 2020-01-03 华为技术有限公司 数据包的处理方法、终端、基站及系统
EP3372008B1 (en) * 2015-11-06 2023-01-11 Nokia Technologies Oy Flow control feedback from user equipment receiving a split bearer
CN105939282B (zh) * 2016-02-04 2019-09-06 杭州迪普科技股份有限公司 分组大小的调整方法及装置
US20210194639A1 (en) * 2016-03-18 2021-06-24 Qualcomm Incorporated Flexibly determining a reordering value for radio link control protocol data unit retransmissions
CN107787009B (zh) * 2016-08-26 2022-09-27 中兴通讯股份有限公司 拥塞处理方法、装置及系统
WO2018126362A1 (zh) 2017-01-04 2018-07-12 广东欧珀移动通信有限公司 Rlc层状态报告控制pdu的传输方法及相关设备
CN109417716A (zh) 2017-06-16 2019-03-01 联发科技（新加坡）私人有限公司 移动通信中处理数据重复的方法和装置
CN109729554B (zh) * 2017-10-30 2022-03-01 展讯通信（上海）有限公司 上行增强数据传输方法、装置及用户设备
DE112017008245T5 (de) 2017-11-30 2020-09-03 Intel IP Corporation Verfahren und Vorrichtungen für Schmalbandkommunikationen
US11265112B2 (en) * 2017-11-30 2022-03-01 Intel Corporation Enhanced polling procedures
JP7032545B2 (ja) 2018-01-04 2022-03-08 エルジー エレクトロニクス インコーポレイティド 通信装置、処理装置及びデータユニットを送信する方法
CN110958647A (zh) * 2018-09-27 2020-04-03 电信科学技术研究院有限公司 一种数据传输方法及装置
CN110971352B (zh) * 2018-09-30 2021-01-26 大唐移动通信设备有限公司 一种上行增强rlc分片的harq重传处理方法及装置
CN111526599B (zh) * 2019-02-01 2022-05-31 华为技术有限公司 一种无线资源控制rrc消息发送方法及装置
US11909535B2 (en) * 2019-10-24 2024-02-20 Qualcomm Incorporated Operating in a radio link control acknowledged mode using a multicast or broadcast radio bearer
US11330668B2 (en) 2019-11-22 2022-05-10 Apple Inc. 5G NR FR2 beam management enhancements
CN113630785B (zh) * 2020-05-08 2024-04-05 大唐移动通信设备有限公司 无线链路控制层传输窗大小自适应调整方法及装置
CN112399471B (zh) * 2020-10-23 2023-02-10 紫光展锐(重庆)科技有限公司 一种数据缓存的方法及相关装置

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020015385A1 (en) * 2000-07-01 2002-02-07 Lg Electronics Inc. Method for confirming receipt of protocol data
US20030099305A1 (en) 2001-11-24 2003-05-29 Lg Electronics Inc. System and method for polling a protocol data unit of a transmission buffer
US20040047331A1 (en) * 2002-09-07 2004-03-11 Lg Electronics Inc. Data transfer controlling method in mobile communication system
US20040208160A1 (en) * 2003-03-31 2004-10-21 Dragan Petrovic Method of retransmission protocol reset synchronisation
US6845100B1 (en) * 2000-08-28 2005-01-18 Nokia Mobile Phones Ltd. Basic QoS mechanisms for wireless transmission of IP traffic
WO2005048517A1 (en) 2003-11-12 2005-05-26 Philips Intellectual Property & Standards Gmbh Data packet transmission
US6901065B1 (en) * 1999-10-19 2005-05-31 Telefonaktiebolaget Lm Ericsson (Publ) Packet transmission in a UMTS network
US20050190698A1 (en) 2004-02-27 2005-09-01 Mitsubishi Denki Kabushiki Kaisha Method and device for a dynamic ARQ window management
US20060045032A1 (en) 2004-08-25 2006-03-02 Fujitsu Limited Transmission time measurement method, transmission control method and mobile communication system provided with a transmission time measurement function
US20060050723A1 (en) * 2004-09-06 2006-03-09 Ling Yu Radio system, base station, controller, and method of controlling data transmission
US20060140158A1 (en) * 2000-01-14 2006-06-29 Interdigital Technology Corporation Wireless communication system with selectively sized data transport blocks
US20060223585A1 (en) * 2005-04-01 2006-10-05 Ipwireless, Inc. Flow control in a cellular communication system
US20100054139A1 (en) * 2005-03-29 2010-03-04 Lg Electronics Inc. Method and apparatus of controlling transmission of data block
US20100062777A1 (en) * 2006-11-28 2010-03-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and A System for Down Link Control in a Cellular Telephony System
RU2392752C2 (ru) 2006-01-05 2010-06-20 ЭлДжи ЭЛЕКТРОНИКС ИНК. Способ передачи данных и способ повторной передачи данных
US20110093754A1 (en) 2006-01-05 2011-04-21 Sung Duck Chun Data transmission method and data re-transmission method

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5400322A (en) * 1993-08-20 1995-03-21 Amati Communications Corp. Updating of bit allocations in a multicarrier modulation transmission system
US6307835B1 (en) * 1998-07-10 2001-10-23 Stmicroelectronics, Inc. Method and apparatus for controlling data flow in data communication networks
US6810031B1 (en) * 2000-02-29 2004-10-26 Celox Networks, Inc. Method and device for distributing bandwidth
WO2002060098A2 (en) * 2001-01-25 2002-08-01 Crescent Networks, Inc. Dual use rate policer and re-marking logic
US7193966B2 (en) * 2001-06-25 2007-03-20 Telefonakitebolaget Lm Ericsson (Publ) Triggered packet data rate change in a communication system
US7006526B1 (en) * 2001-07-31 2006-02-28 Cisco Technology, Inc. Mechanisms for avoiding problems associated with network address protocol translation
US7355971B2 (en) * 2001-10-22 2008-04-08 Intel Corporation Determining packet size in networking
KR100434054B1 (ko) * 2002-04-26 2004-06-04 엘지전자 주식회사 래디오 링크 콘트롤의 폴링방법
US7227856B2 (en) 2002-08-13 2007-06-05 Innovative Sonic Limited Method for handling timers after an RLC reset or re-establishment in a wireless communications system
US20040076182A1 (en) 2002-10-17 2004-04-22 Chih-Hsiang Wu Method for handeling a triggered reset when an RLC is stopped in a wireless communications system
FR2847091B1 (fr) * 2002-11-08 2005-02-04 Nortel Networks Ltd Procede de transmission de donnees en mode acquitte entre une unite emettrice et une unite receptrice, et unite de transmission mettant en oeuvre un tel procede
EP1573935B1 (en) * 2002-12-20 2008-12-10 Interdigital Technology Corporation Scheduling data transmission by medium access control (mac) layer in a mobile network
US6920121B2 (en) 2003-03-17 2005-07-19 Qprs Limited Quality packet radio service for a general packet radio system
CN1567766A (zh) * 2003-06-12 2005-01-19 中兴通讯股份有限公司 无线链路层发送窗口的控制方法
US7525961B2 (en) * 2004-01-14 2009-04-28 Adc Dsl Systems, Inc. Auto-adaptation to packet size on a physical medium
US7558243B2 (en) * 2004-09-15 2009-07-07 Innovative Sonic Limited Enhanced polling method for preventing deadlock in a wireless communications system
CN100370707C (zh) * 2004-11-05 2008-02-20 华为技术有限公司 增强型上行专用物理信道功率控制方法及装置
WO2006118426A1 (en) * 2005-05-03 2006-11-09 Lg Electronics Inc. Changing a radio access configuration between a terminal and a network
US7639613B1 (en) * 2005-06-24 2009-12-29 Packeteer, Inc. Adaptive, flow-based network traffic measurement and monitoring system
US20060291395A1 (en) 2005-06-28 2006-12-28 Nokia Corporation Packet transmission control method and apparatus
WO2007032649A1 (en) * 2005-09-15 2007-03-22 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving status report comprising received status of packet data in a mobile communication system
US7660250B2 (en) * 2005-11-08 2010-02-09 Arris Group, Inc. Method and system for regulating traffic in a network device
US7738495B2 (en) * 2006-01-23 2010-06-15 Cisco Technology, Inc. Method of determining a maximum transmission unit value of a network path using transport layer feedback
US8077611B2 (en) * 2006-07-27 2011-12-13 Cisco Technology, Inc. Multilevel coupled policer
MX2009008015A (es) 2007-02-02 2009-09-04 Interdigital Tech Corp Metodo y aparato para mejorar rlc para tamaño de pdu de rlc flexible.

Patent Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6901065B1 (en) * 1999-10-19 2005-05-31 Telefonaktiebolaget Lm Ericsson (Publ) Packet transmission in a UMTS network
US20060140158A1 (en) * 2000-01-14 2006-06-29 Interdigital Technology Corporation Wireless communication system with selectively sized data transport blocks
US20020015385A1 (en) * 2000-07-01 2002-02-07 Lg Electronics Inc. Method for confirming receipt of protocol data
US6845100B1 (en) * 2000-08-28 2005-01-18 Nokia Mobile Phones Ltd. Basic QoS mechanisms for wireless transmission of IP traffic
US20030099305A1 (en) 2001-11-24 2003-05-29 Lg Electronics Inc. System and method for polling a protocol data unit of a transmission buffer
RU2280958C2 (ru) 2001-11-24 2006-07-27 Эл Джи Электроникс Инк. Система и способ опроса блока протокольных данных буфера передачи
US20040047331A1 (en) * 2002-09-07 2004-03-11 Lg Electronics Inc. Data transfer controlling method in mobile communication system
US20040208160A1 (en) * 2003-03-31 2004-10-21 Dragan Petrovic Method of retransmission protocol reset synchronisation
WO2005048517A1 (en) 2003-11-12 2005-05-26 Philips Intellectual Property & Standards Gmbh Data packet transmission
US20050190698A1 (en) 2004-02-27 2005-09-01 Mitsubishi Denki Kabushiki Kaisha Method and device for a dynamic ARQ window management
JP2005278167A (ja) 2004-02-27 2005-10-06 Mitsubishi Electric Information Technology Centre Europa Bv 動的ａｒｑウィンドウ管理方法およびデバイス
JP2006067099A (ja) 2004-08-25 2006-03-09 Fujitsu Ltd 伝送時間測定方法、伝送制御方法及び伝送時間測定機能を備えた移動通信システム
US20060045032A1 (en) 2004-08-25 2006-03-02 Fujitsu Limited Transmission time measurement method, transmission control method and mobile communication system provided with a transmission time measurement function
US20060050723A1 (en) * 2004-09-06 2006-03-09 Ling Yu Radio system, base station, controller, and method of controlling data transmission
US20100054139A1 (en) * 2005-03-29 2010-03-04 Lg Electronics Inc. Method and apparatus of controlling transmission of data block
US20060223585A1 (en) * 2005-04-01 2006-10-05 Ipwireless, Inc. Flow control in a cellular communication system
RU2392752C2 (ru) 2006-01-05 2010-06-20 ЭлДжи ЭЛЕКТРОНИКС ИНК. Способ передачи данных и способ повторной передачи данных
US20110093754A1 (en) 2006-01-05 2011-04-21 Sung Duck Chun Data transmission method and data re-transmission method
US20100062777A1 (en) * 2006-11-28 2010-03-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and A System for Down Link Control in a Cellular Telephony System

Non-Patent Citations (41)

* Cited by examiner, † Cited by third party
Title
"Universal Mobile Telecommunications System (UMTS); Radio Link Control (RLC) protocol specification (3GPP TS 25.322 V7.3.0 Release 7)," ETSI TS 125 322 V7.3.0 (Jun. 2007).
3rd Generation Partnership Project (3GPP), R2-063042, "Summary document on proposal of changes for the HSPA Evolution TR", Nokia, 3GPP TSG-RAN-WG2 Meeting #55, Seoul, Korea, Oct. 9-13, 2006, 2 pages.
European Patent Application No. 08725182: Communication pursuant to Article 94(3) EPC, dated Nov. 5, 2010, pp. 1-5.
Nokia, Summary Document on Proposal of Changes for the HSPA Evolution TR, 3GPP TSG-RAN-WG2 Meeting #55, Oct. 13, 2006 (See IDS filed Nov. 16, 2012). *
Third Generation Partnership Project TSG-RAN WG3 Meeting #56, 3GPP TS 25.425 CR 118, R3-071227, May 2007.
Third Generation Partnership Project TSG-RAN WG3 Meeting #56, 3GPP TS 25.435 CR 170, R3-071226, May 2007.
Third Generation Partnership Project TSG-RAN2 Meeting #56bis, Change Request 3GPP TS 25.322 V7.2.0, Sorento, Italy, Jan. 15-19, 2007, R2-070034.
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; High Speed Downlink Packet Access: Iub/Iur protocol aspects (Release 5)", 3GPP TS 25.877 V5.1.0 (Jun. 2002).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Medium Access Control (MAC) Protocol Specification (Release 6", 3GPP TS 25.321 V6.11.0 (Dec. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Medium Access Control (MAC) Protocol Specification (Release 6", 3GPP TS 25.321 V6.14.0 (Sep. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Medium Access Control (MAC) Protocol Specification (Release 6)", 3GPP TS 25.321 V6.6.0 (Sep. 2005).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Medium Access Control (MAC) Protocol Specification (Release 7)", 3GPP TS 25.321 V7.3.0 (Dec. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Medium Access Control (MAC) Protocol Specification (Release 7)", 3GPP TS 25.321 V7.7.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Medium Access Control (MAC) Protocol Specification (Release 8)", 3GPP TS 25.321 V8.0.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 6)", 3GPP TS 25.301 V6.2.0 (Mar. 2005).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 6)", 3GPP TS 25.301 V6.4.0 (Sep. 2005).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 6)", 3GPP TS 25.301 V6.5.0 (Sep. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 7)", 3GPP TS 25.301 V7.0.0 (Mar. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 7)", 3GPP TS 25.301 V7.3.0 (Sep. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 8)", 3GPP TS 25.301 V8.0.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Link Control (RLC) Protocol Specification (Release 7)", 3GPP TS 25.322 V7.1.0 (Jun. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Link Control (RLC) Protocol Specification (Release 7)", 3GPP TS 25.322 V7.2.0 (Sep. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Link Control (RLC) Protocol Specification (Release 7)", 3GPP TS 25.322 V7.5.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Link Control (RLC) Protocol Specification (Release 8)", 3GPP TS 25.322 V8.0.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 1999)", 3GPP TS 25.331 V3.21.0 (Dec. 2004).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 4)", 3GPP TS 25.331 V4.17.0 (Mar. 2005).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 4)", 3GPP TS 25.331 V4.18.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 5)", 3GPP TS 25.331 V5.19.0 (Dec. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 5)", 3GPP TS 25.331 V5.21.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 6)", 3GPP TS 25.331 V6.12.0 (Dec. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 6)", 3GPP TS 25.331 V6.16.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 7)", 3GPP TS 25.331 V7.3.0 (Dec. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 7)", 3GPP TS 25.331 V7.7.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Radio Resource Control (RRC) Protocol Specification (Release 8)", 3GPP TS 25.331 V8.1.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; RRC Protocol Specification (Release 1999)", 3GPP TS 25.331 V3.5.0 (Dec. 2000).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; UTRAN Iub Interface User Plane Protocols for Common Transport Channel data streams (Release 7)", 3GPP TS 25.435 V7.3.0 (Dec. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; UTRAN Iub Interface User Plane Protocols for Common Transport Channel data streams (Release 7)", 3GPP TS 25.435 V7.5.0 (Jun. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; UTRAN Iub Interface User Plane Protocols for Common Transport Channel data streams (Release 7)", 3GPP TS 25.435 V7.7.0 (Dec. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; UTRAN Iur interface user plane protocols for Common Transport Channel data streams (Release 7)", 3GPP TS 25.425 V7.3.0 (Dec. 2006).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; UTRAN Iur interface user plane protocols for Common Transport Channel data streams (Release 7)", 3GPP TS 25.425 V7.5.0 (Sep. 2007).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; UTRAN Iur interface user plane protocols for Common Transport Channel data streams (Release 7)", 3GPP TS 25.425 V7.6.0 (Dec. 2007).

Cited By (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10306489B2 (en) 2007-09-11 2019-05-28 Optis Cellular Technology, Llc Method for transmitting status report of PDCP layer in mobile telecommunications system and receiver of mobile telecommunications
US11310681B2 (en) 2007-09-11 2022-04-19 Optis Cellular Technology, Llc Transmitting and receiving a PDCP layer status report in a mobile telecommunications system
US10848987B2 (en) 2007-09-11 2020-11-24 Optis Cellular Technology, Llc Transmitting and receiving a PDCP layer status report in a mobile telecommunications system
US9942781B2 (en) * 2007-09-11 2018-04-10 Optis Cellular Technology, Llc Method for transmitting status report of PDCP layer in mobile telecommunications system and receiver of mobile telecommunications
US20170019807A1 (en) * 2007-09-11 2017-01-19 Optis Cellular Technology, Llc Method for transmitting status report of pdcp layer in mobile telecommunications system and receiver of mobile telecommunications
US9973322B2 (en) 2010-02-12 2018-05-15 Interdigital Technology Corporation Data split between multiple sites
US9392515B2 (en) * 2010-02-12 2016-07-12 Interdigital Technology Corporation Data split between multiple sites
US11871391B2 (en) 2010-12-03 2024-01-09 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for performing multi-radio access technology carrier aggregation
US11363597B2 (en) 2010-12-03 2022-06-14 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for performing multi-radio access technology carrier aggregation
US10560944B2 (en) 2010-12-03 2020-02-11 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for performing multi-radio access technology carrier aggregation
US8824485B2 (en) 2011-05-13 2014-09-02 International Business Machines Corporation Efficient software-based private VLAN solution for distributed virtual switches
US8798080B2 (en) 2011-05-14 2014-08-05 International Business Machines Corporation Distributed fabric protocol (DFP) switching network architecture
US8856801B2 (en) 2011-05-14 2014-10-07 International Business Machines Corporation Techniques for executing normally interruptible threads in a non-preemptive manner
US8948004B2 (en) 2011-06-17 2015-02-03 International Business Machines Corporation Fault tolerant communication in a trill network
US8948003B2 (en) 2011-06-17 2015-02-03 International Business Machines Corporation Fault tolerant communication in a TRILL network
US12167316B2 (en) 2011-07-29 2024-12-10 Interdigital Patent Holdings, Inc. Methods and apparatus for radio resources management in multi-radio access technology wireless systems
US11838849B2 (en) 2011-07-29 2023-12-05 Interdigital Patent Holdings, Inc. Methods and apparatus for radio resources management in multi-radio access technology wireless systems
US8797843B2 (en) 2011-09-12 2014-08-05 International Business Machines Corporation High availability distributed fabric protocol (DFP) switching network architecture
US20130088959A1 (en) * 2011-10-06 2013-04-11 International Business Machines Corporation Credit-based network congestion management
US8750129B2 (en) * 2011-10-06 2014-06-10 International Business Machines Corporation Credit-based network congestion management
US9065745B2 (en) 2011-10-06 2015-06-23 International Business Machines Corporation Network traffic distribution
US8942094B2 (en) 2011-10-06 2015-01-27 International Business Machines Corporation Credit-based network congestion management
US9059922B2 (en) 2011-10-06 2015-06-16 International Business Machines Corporation Network traffic distribution
US11184942B2 (en) 2012-08-23 2021-11-23 Interdigital Patent Holdings, Inc. Operating with multiple schedulers in a wireless system
US10349463B2 (en) 2012-08-23 2019-07-09 Interdigital Patent Holdings, Inc. Operating with multiple schedulers in a wireless system
US10973019B2 (en) 2012-08-23 2021-04-06 Interdigital Patent Holdings, Inc. Physical layer operation for multi-layer operation in a wireless system
US9699779B2 (en) 2012-08-23 2017-07-04 Interdigital Patent Holdings, Inc. Physical layer operation for multi-layer operation in a wireless system
US11716781B2 (en) 2012-08-23 2023-08-01 Interdigital Patent Holdings, Inc. Operating with multiple schedulers in a wireless system
US9788358B2 (en) 2012-08-23 2017-10-10 Interdigital Patent Holdings, Inc. Operating with multiple schedulers in a wireless system
US9763282B2 (en) 2012-08-23 2017-09-12 Interdigital Patent Holdings, Inc. Operating with multiple schedulers in a wireless system
US9585008B2 (en) 2013-04-19 2017-02-28 Qualcomm Incorporated Apparatus and methods for signaling out-of-standard capability in wireless communication networks
US9705803B1 (en) 2015-06-10 2017-07-11 Sprint Communications Company L.P. Negotiated radio link properties among wireless access nodes
US10298509B2 (en) * 2016-03-17 2019-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Managing a sequence number range for radio link control entities in a radio access network during an on-going connection

Also Published As

Publication number Publication date
JP5258791B2 (ja) 2013-08-07
US20080212561A1 (en) 2008-09-04
AU2008214378A1 (en) 2008-08-14
US20130279490A1 (en) 2013-10-24
WO2008097544A3 (en) 2008-12-11
TW201203980A (en) 2012-01-16
TWI452885B (zh) 2014-09-11
KR20130044362A (ko) 2013-05-02
EP2429235A1 (en) 2012-03-14
KR20090121299A (ko) 2009-11-25
CN103281250B (zh) 2017-08-11
JP2014187709A (ja) 2014-10-02
JP2013168993A (ja) 2013-08-29
BRPI0806396B1 (pt) 2020-04-28
IL200075A0 (en) 2010-04-15
EP2115952A2 (en) 2009-11-11
BRPI0806396A2 (pt) 2011-09-06
TW200835272A (en) 2008-08-16
AR065158A1 (es) 2009-05-20
KR101548061B1 (ko) 2015-08-27
US9554398B2 (en) 2017-01-24
TW201503650A (zh) 2015-01-16
MX2009008015A (es) 2009-09-04
JP5555791B2 (ja) 2014-07-23
TWI499259B (zh) 2015-09-01
RU2455776C2 (ru) 2012-07-10
WO2008097544A2 (en) 2008-08-14
CN103281250A (zh) 2013-09-04
KR20140015620A (ko) 2014-02-06
IL200075A (en) 2013-06-27
MY154157A (en) 2015-05-15
AU2008214378B2 (en) 2011-06-02
JP5833707B2 (ja) 2015-12-16
US9936423B2 (en) 2018-04-03
EP2429235B1 (en) 2018-07-25
SG178738A1 (en) 2012-03-29
RU2009132954A (ru) 2011-03-10
CN101675627A (zh) 2010-03-17
US20170094560A1 (en) 2017-03-30
CA2677112A1 (en) 2008-08-14
KR101430067B1 (ko) 2014-08-14
JP2010518699A (ja) 2010-05-27
KR20100016449A (ko) 2010-02-12
CA2677112C (en) 2016-10-18

Similar Documents

Publication Publication Date Title
US9936423B2 (en) Method and apparatus for enhancing RLC for flexible RLC PDU size
CN103490853B (zh) 一种用于产生和传送rlc pdu的方法和无线发射/接收单元
US8332702B2 (en) Method and apparatus for hybrid automatic repeat request transmission
US20080165805A1 (en) Node b based segmentation/concatenation
US20100008269A1 (en) Method for transmitting control information in a mobile communication system
HK1140873A (en) Method and apparatus for enhancing rlc for flexible rlc pdu size

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERDIGITAL TECHNOLOGY CORPORATION, DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PANI, DIANA;MILLER, JAMES M.;MARINIER, PAUL;AND OTHERS;REEL/FRAME:021044/0232;SIGNING DATES FROM 20080417 TO 20080514

Owner name: INTERDIGITAL TECHNOLOGY CORPORATION, DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PANI, DIANA;MILLER, JAMES M.;MARINIER, PAUL;AND OTHERS;SIGNING DATES FROM 20080417 TO 20080514;REEL/FRAME:021044/0232

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12

AS Assignment

Owner name: INTERDIGITAL PATENT HOLDINGS, INC., DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERDIGITAL TECHNOLOGY CORPORATION;REEL/FRAME:070837/0530

Effective date: 20241218