[go: up one dir, main page]

WO2020093230A1 - Délivrance d'unités de données de protocole (pdu) non ordonnées de protocole de convergence de données par paquets (pdcp) à un pdcp - Google Patents

Délivrance d'unités de données de protocole (pdu) non ordonnées de protocole de convergence de données par paquets (pdcp) à un pdcp Download PDF

Info

Publication number
WO2020093230A1
WO2020093230A1 PCT/CN2018/114114 CN2018114114W WO2020093230A1 WO 2020093230 A1 WO2020093230 A1 WO 2020093230A1 CN 2018114114 W CN2018114114 W CN 2018114114W WO 2020093230 A1 WO2020093230 A1 WO 2020093230A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
pdcp
pdus
sublayer
decoded
Prior art date
Application number
PCT/CN2018/114114
Other languages
English (en)
Inventor
Xiaojian LONG
Saket BATHWAL
Peng Wu
Shailesh Maheshwari
Gang Xiao
Rudhir Upretee
Arun Prasanth Balasubramanian
Ashwin Raman
Vinay Rajkumar PATIL
Qi Fu
Xing Chen
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2018/114114 priority Critical patent/WO2020093230A1/fr
Priority to PCT/CN2019/114269 priority patent/WO2020093915A1/fr
Publication of WO2020093230A1 publication Critical patent/WO2020093230A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • 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/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • the technology discussed below relates generally to wireless communication systems, and more particularly, to processing of Packet Data Convergence Protocol (PDCP) protocol data units (PDUs) .
  • PDCP Packet Data Convergence Protocol
  • PDUs protocol data units
  • the Packet Data Convergence Protocol (PDCP) sublayer is located in the radio protocol stack in both the Long Term Evolution (LTE) and New Radio (NR) air interface on top of the Radio Link Control (RLC) sublayer.
  • the PDCP sublayer provides various services, such as transfer of user and control plane data, header compression, ciphering, and integrity protection.
  • the RLC sublayer provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to hybrid automatic repeat request (HARQ) and automatic repeat request (ARQ) .
  • HARQ hybrid automatic repeat request
  • ARQ automatic repeat request
  • the RLC sublayer delivers data packets (e.g., protocol data units (PDUs) ) to the PDCP sublayer after RLC reordering and reassembling of PDCP PDUs to ensure that the PDCP sublayer receives PDUs in order.
  • data packets e.g., protocol data units (PDUs)
  • PDUs protocol data units
  • PDCP reordering may be enabled to allow out-of-order delivery of PDCP PDUs from the NR RLC sublayer to the NR PDCP sublayer.
  • the NR PDCP reordering window advances before the LTE RLC sublayer completes HARQ/ARQ, complete PDCP PDUs sitting in the LTE RLC buffer may be discarded.
  • the UE may be simultaneously connected to both a eUTRAN (LTE) base station and a NR base station to receive data packets from both the LTE base station and the NR base station.
  • LTE eUTRAN
  • NR NR base station
  • the UE may receive Radio Link Control (RLC) protocol data units (PDUs) and Packet Data Convergence Protocol (PDCP) PDUs from the LTE base station, and RLC PDUs and PDCP PDUs from the NR base station.
  • RLC Radio Link Control
  • PDUs Packet Data Convergence Protocol
  • PDCP PDUs Packet Data Convergence Protocol
  • Each of the LTE RLC PDUs may be mapped to a subset of the LTE PDCP PDUs
  • each of the NR RLC PDUs may be mapped to a subset of the NR PDCP PDUs.
  • a PDCP reordering timer may be initialized.
  • the subsets of the LTE PDCP PDUs mapped to decoded LTE RLC PDUs may be delivered from the RLC sublayer to the PDCP sublayer without reordering thereof.
  • the PDCP reordering timer expires, any LTE PDCP PDUs mapped to remaining undecoded LTE RLC PDUs may be discarded.
  • FIG. 1 is a schematic illustration of a wireless communication system.
  • FIG. 2 is a conceptual illustration of an example of a radio access network.
  • FIG. 3 is a diagram illustrating an example of a radio protocol architecture for the user and control plane.
  • FIG. 4 is a diagram illustrating an example of a format of a Packet Data Convergence Protocol (PDCP) Packet Data Unit (PDU) .
  • PDCP Packet Data Convergence Protocol
  • PDU Packet Data Unit
  • FIG. 5 is a diagram illustrating an example of a format of a Radio Link Control (RLC) Unacknowledged Mode Data (UMD) Packet Data Unit (PDU) .
  • RLC Radio Link Control
  • UMD Unacknowledged Mode Data
  • PDU Packet Data Unit
  • FIG. 6 is a diagram illustrating an example of a format of a Radio Link Control (RLC) Acknowledged Mode Data (AMD) Packet Data Unit (PDU) .
  • RLC Radio Link Control
  • AMD Acknowledged Mode Data
  • PDU Packet Data Unit
  • FIG. 7 is a diagram illustrating an example of packets received by a user equipment implementing dual connectivity.
  • FIG. 8 is a block diagram illustrating an example of a hardware implementation for a user equipment employing a processing system.
  • FIG. 9 is a diagram illustrating an RLC sublayer and a PDCP sublayer within a user equipment (UE) implementing dual connectivity.
  • FIG. 10 is a flow chart of a method of delivering out-of-order PDCP PDUs to the PDCP sublayer.
  • Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations.
  • devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments.
  • transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) .
  • innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitution.
  • the various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards.
  • the wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106.
  • the UE 106 may be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.
  • the RAN 104 may implement any suitable radio access technology (RAT) or RATs to provide radio access to the UE 106.
  • the RAN 104 may operate according to 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G.
  • 3GPP 3rd Generation Partnership Project
  • NR New Radio
  • the RAN 104 may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE.
  • the 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN.
  • the RAN 104 may operate according to both the LTE and 5G NR standards.
  • 3GPP 3rd Generation Partnership Project
  • 5G New Radio
  • eUTRAN Evolved Universal Terrestrial Radio Access Network
  • NG-RAN next-generation RAN
  • the RAN 104 may operate according to both the LTE and 5G NR standards.
  • many other examples may be utilized within
  • the RAN 104 includes a plurality of base stations 108.
  • a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE.
  • a base station may variously be referred to by those skilled in the art as a base transceiver station (BTS) , a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , an access point (AP) , a Node B (NB) , an eNode B (eNB) , a gNode B (gNB) , or some other suitable terminology.
  • BTS basic service set
  • ESS extended service set
  • AP access point
  • NB Node B
  • eNB eNode B
  • gNB gNode B
  • the RAN 104 operates according to both the LTE and 5G NR standards
  • one of the base stations 108 may
  • the radio access network 104 is further illustrated supporting wireless communication for multiple mobile apparatuses.
  • a mobile apparatus may be referred to as user equipment (UE) 106 in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS) , a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT) , a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.
  • a UE 106 may be an apparatus that provides a user with access to network services.
  • the UE 106 may be an Evolved-Universal Terrestrial Radio Access Network –New Radio dual connectivity (EN-DC) UE that is capable of simultaneously connecting to an LTE base station and a NR base station to receive data packets from both the LTE base station and the NR base station.
  • EN-DC Evolved-Universal Terrestrial Radio Access Network –New Radio dual connectivity
  • a “mobile” apparatus need not necessarily have a capability to move, and may be stationary.
  • the term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies.
  • UEs may include a number of hardware structural components sized, shaped, and arranged to help in communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other.
  • a mobile apparatus examples include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC) , a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA) , and a broad array of embedded systems, e.g., corresponding to an “Internet of Things” (IoT) .
  • IoT Internet of Things
  • a mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player) , a camera, a game console, etc.
  • GPS global positioning system
  • a mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc.
  • a mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid) , lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc.
  • a mobile apparatus may provide for connected medicine or telemedicine support, i.e., health care at a distance.
  • Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data.
  • Wireless communication between a RAN 104 and a UE 106 may be described as utilizing an air interface.
  • Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmission.
  • DL downlink
  • the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108) .
  • Another way to describe this scheme may be to use the term broadcast channel multiplexing.
  • Uplink Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions.
  • UL uplink
  • the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE 106) .
  • a scheduling entity e.g., a base station 108 allocates resources for communication among some or all devices and equipment within its service area or cell.
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UEs 106, which may be scheduled entities, may utilize resources allocated by the scheduling entity 108.
  • Base stations 108 are not the only entities that may function as scheduling entities. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs) .
  • a scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106.
  • the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108.
  • the scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., a grant) , synchronization or timing information, or other control information from another entity in the wireless communication network such as the scheduling entity 108.
  • the uplink and/or downlink control information and/or traffic information may be time-divided into frames, subframes, slots, and/or symbols.
  • a symbol may refer to a unit of time that, in an orthogonal frequency division multiplexed (OFDM) waveform, carries one resource element (RE) per sub-carrier.
  • a slot may carry 7 or 14 OFDM symbols.
  • a subframe may refer to a duration of 1ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame.
  • OFDM orthogonal frequency division multiplexed
  • a slot may carry 7 or 14 OFDM symbols.
  • a subframe may refer to a duration of 1ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame.
  • these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and various time divisions of the waveform may have any suitable duration.
  • base stations 108 may include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system.
  • the backhaul 120 may provide a link between a base station 108 and the core network 102.
  • a backhaul network may provide interconnection between the respective base stations 108.
  • Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.
  • the core network 102 may be a part of the wireless communication system 100, and may be independent of the radio access technology used in the RAN 104.
  • the core network 102 may be configured according to 5G standards (e.g., 5GC) .
  • the core network 102 may be configured according to a 4G evolved packet core (EPC) , or any other suitable standard or configuration.
  • 5G standards e.g., 5GC
  • EPC 4G evolved packet core
  • FIG. 2 a schematic illustration of a RAN 200 is provided.
  • the RAN 200 may be the same as the RAN 104 described above and illustrated in FIG. 1.
  • the geographic area covered by the RAN 200 may be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station.
  • FIG. 2 illustrates macrocells 202, 204, and 206, and a small cell 208, each of which may include one or more sectors (not shown) .
  • a sector is a sub-area of a cell. All sectors within one cell are served by the same base station.
  • a radio link within a sector can be identified by a single logical identification belonging to that sector.
  • the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.
  • two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206.
  • a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables.
  • the cells 202, 204, and 126 may be referred to as macrocells, as the base stations 210, 212, and 214 support cells having a large size.
  • a base station 218 is shown in the small cell 208 (e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc. ) which may overlap with one or more macrocells.
  • the cell 208 may be referred to as a small cell, as the base station 218 supports a cell having a relatively small size. Cell sizing can be done according to system design as well as component constraints.
  • the radio access network 200 may include any number of wireless base stations and cells. Further, a relay node may be deployed to extend the size or coverage area of a given cell.
  • the base stations 210, 212, 214, 218 provide wireless access points to a core network for any number of mobile apparatuses. In some examples, the base stations 210, 212, 214, and/or 218 may be the same as the base station/scheduling entity 108 described above and illustrated in FIG. 1.
  • the cells may include UEs that may be in communication with one or more sectors of each cell.
  • each base station 210, 212, 214, and 218 may be configured to provide an access point to a core network 102 (see FIG. 1) for all the UEs in the respective cells.
  • UEs 222 and 224 may be in communication with base station 210; UEs 226 and 228 may be in communication with base station 212; UEs 230 and 232 may be in communication with base station 214 by way of RRH 216; and UE 234 may be in communication with base station 218.
  • the UEs 222, 224, 226, 228, 230, 232, 234, 238, 240, and/or 242 may be the same as the UE/scheduled entity 106 described above and illustrated in FIG. 1.
  • an unmanned aerial vehicle (UAV) 220 which may be a drone or quadcopter, can be a mobile network node and may be configured to function as a UE.
  • the UAV 220 may operate within cell 202 by communicating with base station 210.
  • sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station.
  • two or more UEs e.g., UEs 226 and 228, may communicate with each other using peer to peer (P2P) or sidelink signals 227 without relaying that communication through a base station (e.g., base station 212) .
  • P2P peer to peer
  • UE 238 is illustrated communicating with UEs 240 and 242.
  • the UE 238 may function as a scheduling entity or a primary sidelink device
  • UEs 240 and 242 may function as a scheduled entity or a non-primary (e.g., secondary) sidelink device.
  • a UE may function as a scheduling entity in a device-to-device (D2D) , peer-to-peer (P2P) , or vehicle-to-vehicle (V2V) network, and/or in a mesh network.
  • D2D device-to-device
  • P2P peer-to-peer
  • V2V vehicle-to-vehicle
  • UEs 240 and 242 may optionally communicate directly with one another in addition to communicating with the scheduling entity 238.
  • a scheduling entity and one or more scheduled entities may communicate utilizing the scheduled resources.
  • the sidelink signals 227 include sidelink traffic and sidelink control.
  • Sidelink control information may in some examples include a request signal, such as a request-to-send (RTS) , a source transmit signal (STS) , and/or a direction selection signal (DSS) .
  • the request signal may provide for a scheduled entity to request a duration of time to keep a sidelink channel available for a sidelink signal.
  • Sidelink control information may further include a response signal, such as a clear-to- send (CTS) and/or a destination receive signal (DRS) .
  • CTS clear-to- send
  • DRS destination receive signal
  • the response signal may provide for the scheduled entity to indicate the availability of the sidelink channel, e.g., for a requested duration of time.
  • An exchange of request and response signals (e.g., handshake) may enable different scheduled entities performing sidelink communications to negotiate the availability of the sidelink channel prior to communication of the sidelink traffic information.
  • the ability for a UE to communicate while moving, independent of its location is referred to as mobility.
  • the various physical channels between the UE and the radio access network are generally set up, maintained, and released under the control of an access and mobility management function (AMF, not illustrated, part of the core network 102 in FIG. 1) , which may include a security context management function (SCMF) that manages the security context for both the control plane and the user plane functionality, and a security anchor function (SEAF) that performs authentication.
  • AMF access and mobility management function
  • SCMF security context management function
  • SEAF security anchor function
  • a radio access network 200 may utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE’s connection from one radio channel to another) .
  • a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells.
  • the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell.
  • UE 224 illustrated as a vehicle, although any suitable form of UE may be used
  • the UE 224 may transmit a reporting message to its serving base station 210 indicating this condition.
  • the UE 224 may receive a handover command, and the UE may undergo a handover to the cell 206.
  • UL reference signals from each UE may be utilized by the network to select a serving cell for each UE.
  • the base stations 210, 212, and 214/216 may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs) , unified Secondary Synchronization Signals (SSSs) and unified Physical Broadcast Channels (PBCH) ) .
  • PSSs Primary Synchronization Signals
  • SSSs unified Secondary Synchronization Signals
  • PBCH Physical Broadcast Channels
  • the UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit an uplink pilot or reference signal.
  • the uplink pilot signal transmitted by a UE may be concurrently received by two or more cells (e.g., base stations 210 and 214/216) within the radio access network 200.
  • Each of the cells may measure a strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214/216 and/or a central node within the core network) may determine a serving cell for the UE 224.
  • the radio access network e.g., one or more of the base stations 210 and 214/216 and/or a central node within the core network
  • the network may continue to monitor the uplink pilot signal transmitted by the UE 224.
  • the network 200 may handover the UE 224 from the serving cell to the neighboring cell, with or without informing the UE 224.
  • the synchronization signal transmitted by the base stations 210, 212, and 214/216 may be unified, the synchronization signal may not identify a particular cell, but rather may identify a zone of multiple cells operating on the same frequency and/or with the same timing.
  • the use of zones in 5G networks or other next generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network may be reduced.
  • the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum.
  • Licensed spectrum provides for exclusive use of a portion of the spectrum, generally by virtue of a mobile network operator purchasing a license from a government regulatory body.
  • Unlicensed spectrum provides for shared use of a portion of the spectrum without need for a government-granted license. While compliance with some technical rules is generally still required to access unlicensed spectrum, generally, any operator or device may gain access.
  • Shared spectrum may fall between licensed and unlicensed spectrum, wherein technical rules or limitations may be required to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple RATs.
  • the holder of a license for a portion of licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, e.g., with suitable licensee-determined conditions to gain access.
  • LSA licensed shared access
  • channel coding may be used. That is, wireless communication may generally utilize a suitable error correcting block code.
  • an information message or sequence is split up into code blocks (CBs) , and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. Exploitation of this redundancy in the encoded information message can improve the reliability of the message, enabling correction for any bit errors that may occur due to the noise.
  • LDPC quasi-cyclic low-density parity check
  • PBCH physical broadcast channel
  • scheduling entities 108 and scheduled entities 106 may include suitable hardware and capabilities (e.g., an encoder, a decoder, and/or a CODEC) to utilize one or more of these channel codes for wireless communication.
  • suitable hardware and capabilities e.g., an encoder, a decoder, and/or a CODEC
  • the air interface in the radio access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices.
  • 5G NR specifications provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and for multiplexing for DL transmissions from base station 210 to one or more UEs 222 and 224, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) .
  • OFDM orthogonal frequency division multiplexing
  • CP cyclic prefix
  • 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA) ) .
  • DFT-s-OFDM discrete Fourier transform-spread-OFDM
  • SC-FDMA single-carrier FDMA
  • multiplexing and multiple access are not limited to the above schemes, and may be provided utilizing time division multiple access (TDMA) , code division multiple access (CDMA) , frequency division multiple access (FDMA) , sparse code multiple access (SCMA) , resource spread multiple access (RSMA) , or other suitable multiple access schemes.
  • multiplexing DL transmissions from the base station 210 to UEs 222 and 224 may be provided utilizing time division multiplexing (TDM) , code division multiplexing (CDM) , frequency division multiplexing (FDM) , orthogonal frequency division multiplexing (OFDM) , sparse code multiplexing (SCM) , or other suitable multiplexing schemes.
  • the air interface in the radio access network 200 may further utilize one or more duplexing algorithms.
  • Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions.
  • Full duplex means both endpoints can simultaneously communicate with one another.
  • Half duplex means only one endpoint can send information to the other at a time.
  • a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancellation technologies.
  • Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD) .
  • FDD frequency division duplex
  • TDD time division duplex
  • transmissions in different directions operate at different carrier frequencies.
  • TDD transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g.,
  • the radio protocol architecture for a radio access network may take on various forms depending on the particular application.
  • An example for an LTE or NR radio access network will now be presented with reference to FIG. 3.
  • FIG. 3 is a conceptual diagram illustrating an example of the radio protocol architecture for the user and control planes.
  • the radio protocol architecture for the UE and the base station includes three layers: Layer 1, Layer 2, and Layer 3.
  • Layer 1 is the lowest layer and implements various physical layer signal processing functions. Layer 1 will be referred to herein as the physical layer 306.
  • Layer 2 (L2 layer) 308 is above the physical layer 306 and is responsible for the link between the UE and base station over the physical layer 306.
  • the L2 layer 308 includes a media access control (MAC) sublayer 310, a radio link control (RLC) sublayer 312, and a packet data convergence protocol (PDCP) 314 sublayer, which are terminated at the base station on the network side.
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • the UE may have several upper layers above the L2 layer 308 including a network layer (e.g., IP layer) that is terminated at the Packet Data Network (PDN) gateway on the network side, and an application layer that is terminated at the other end of the connection (e.g., far end UE, server, etc. ) .
  • IP layer e.g., IP layer
  • PDN Packet Data Network
  • the PDCP sublayer 314 provides multiplexing between different radio bearers and logical channels.
  • the PDCP sublayer 314 also provides header compression for upper layer data packets to reduce radio transmission overhead, security by ciphering the data packets, and handover support for UEs between base stations.
  • the RLC sublayer 312 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to hybrid automatic repeat request (HARQ) and automatic repeat request (ARQ) .
  • HARQ hybrid automatic repeat request
  • ARQ automatic repeat request
  • the MAC sublayer 310 provides multiplexing between logical and transport channels.
  • the MAC sublayer 310 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs.
  • the MAC sublayer 310 is also responsible for HARQ operations.
  • the physical layer 306 is responsible for transmitting and receiving data on physical channels (e.g., within slots) .
  • the radio protocol architecture for the UE and base station is substantially the same for the physical layer 306 and the L2 layer 308 with the exception that there is no header compression function for the control plane.
  • the control plane also includes a radio resource control (RRC) sublayer 316 in Layer 3.
  • RRC sublayer 316 is responsible for obtaining radio resources (i.e., radio bearers) and for configuring the lower layers using RRC signaling between the base station and the UE.
  • packets received by a sublayer from another sublayer may be referred to as Service Data Units (SDUs)
  • packets output from a sublayer to another sublayer may be referred to as Protocol Data Units (PDUs)
  • SDUs Service Data Units
  • PDUs Protocol Data Units
  • packets received by the PDCP sublayer 314 from an upper layer may be referred to as PDCP SDUs
  • PDCP PDUs or RLC SDUs packets received from the PDCP sublayer 314 from the RLC sublayer.
  • the PDCP PDU format 400 includes a header 402 and body 404.
  • the header 402 includes a D/C field 406 and SN field 408.
  • the D/C field 406 is located within a first octet 412a and may include, for example, a single bit for indicating whether the PCDP PDU contains user plane data or control plane data.
  • the SN field 408 occupies the remainder of the first octet 412a, along with a second octet 412b.
  • the SN field 408 contains the sequence number (SN) of the PDCP PDU.
  • the SN may contain 7 bits or 12 bits.
  • the body 404 contains uncompressed or compressed user or control plane data 410 and may include one or more octets (only one octet 412c of which is shown for simplicity) .
  • UMD Unacknowledged Mode Data
  • PDU Packet Data Unit
  • FIG. 5 An example of an RLC Unacknowledged Mode Data (UMD) Packet Data Unit (PDU) format is illustrated in FIG. 5.
  • UMD may be used, for example, to transmit delay sensitive packets, such as VoIP packets.
  • the receiving device does not acknowledge reception of data packets to the transmitting device (e.g., the receiving device does not transmit ACK/NACK to the transmitting device) .
  • the RLC UMD PDU format 500 includes a header 502 and a body 504.
  • the header 502 occupies a first octet 512a that includes a Framing Information (FI) field 506, Extension bit (E) field 508 and SN field 510.
  • the FI field 506 indicates whether the RLC PDU is segmented at the beginning and/or end of the data field.
  • the E field 508 indicates whether a data field or a set of E field and Length Indicator (LI) fields follow the SN field 510.
  • the SN field 510 occupies the remainder of the first octet 512a.
  • the SN field 510 contains the sequence number (SN) of the RLC PDU.
  • the SN may contain 5 bits or 10 bits.
  • the header 502 is one byte long, as shown in FIG. 5.
  • the header 502 is two bytes long and the SN extends through the second octet with the first three bits of the header 502 being reserved.
  • the body 504 contains uncompressed or compressed user or control plane data 512 and may include one or more octets (only one octet 512b of which is shown for simplicity) .
  • the RLC AMD PDU format 600 includes a header 602 and a body 604.
  • the header 602 occupies the first two octets 620a and 620b and includes a D/C field 606, a re-segmentation flag (RF) field 608, a polling bit (P) field 610, a Framing Information (FI) field 612, an Extension bit (E) field 614 and SN field 616.
  • RF re-segmentation flag
  • P polling bit
  • FI Framing Information
  • E Extension bit
  • the D/C field 606 indicates whether the RLC PDU contains user plane data or control plane data.
  • the RF field 608 indicates whether the RLC PDU is an AMD PDU or an AMD PDU segment.
  • the P field 610 indicates whether the transmitting device is requesting the status of previously transmitted RLC PDUs from the receiving device.
  • the FI field 612 indicates whether the RLC PDU is segmented at the beginning and/or end of the data field.
  • the E field 614 indicates whether a data field or a set of E field and Length Indicator (LI) fields follow the SN field 616.
  • the SN field 616 occupies the remainder of the first octet 620a and the entirety of the second octet 620b.
  • the SN field 616 contains the sequence number (SN) of the RLC PDU. In some examples, the SN may contain 10 bits.
  • the body 604 contains uncompressed or compressed user or control plane data 618 and may include one or more octets (only one octet 620c of which is shown for simplicity) .
  • FIG. 7 is a diagram illustrating an example of packets received by a user equipment (UE) implementing EN-DC (eUTRAN-NR dual connectivity) .
  • the UE receives a first set of packets 700 from a first base station supporting a first radio access technology (RAT) and a second set of packets 708 from a second base station supporting a second RAT.
  • the first RAT may be, for example, a eUTRAN (LTE) RAT
  • the second RAT may be, for example, a NR RAT.
  • the first set of packets 700 includes a plurality of LTE RLC PDUs 702, a plurality of PDCP PDUs 704, and a plurality of Internet Protocol (IP) packets 706.
  • the second set of packets 708 includes a plurality of NR RLC PDUs 710, a plurality of PDCP PDUs 712, and a plurality of IP packets 714.
  • Each of the plurality of LTE RLC PDUs 702 includes a respective sequence number (SN) assigned by the LTE RAT and each of the NR RLC PDUs 710 includes a respective SN separately assigned by the NR RAT.
  • SN sequence number
  • the LTE RLC PDUs 702 are illustrated in FIG.
  • the PDCP PDUs 704 and 712 each include a respective SN that is assigned independent of the RATs (e.g., the PDCP PDU SNs are collectively assigned by both RATs) .
  • PDCP PDUs 704 transmitted by the LTE base station are assigned SNs 0–29
  • PDCP PDUs 712 transmitted by the NR base station are assigned SNs 30–49.
  • Each of the RLC PDUs 702 and 710 are mapped to a respective subset of the PDCP PDUs 704 and 712, where the subsets are non-overlapping.
  • each of the plurality of LTE RLC PDUs 702 is mapped to a respective subset of the PDCP PDUs 704.
  • LTE RLC PDU 0 is mapped to PDCP PDUs 0–4
  • LTE RLC PDU 1 is mapped to PDCP PDUs 5–9
  • LTE RLC PDU 2 is mapped to PDCP PDUs 10–14, and so on.
  • each of the plurality of NR RLC PDUs 710 is mapped to a respective subset of the PDCP PDUs 712.
  • NR RLC PDU 0 is mapped to PDCP PDU 30
  • NR RLC PDU 1 is mapped to PDCP PDU 31
  • NR RLC PDU 2 is mapped to PDCP PDU 32, and so on.
  • the RLC sublayer delivers the PDCP PDUs 704 to the PDCP sublayer after reordering and reassembling thereof as there is no PDCP reordering performed in the PDCP sublayer. For example, if the RLC sublayer detects an out-of-order decoded LTE RLC PDU 702, the RLC sublayer may buffer all of the PDCP PDUs 704 received since the last in-order decoded LTE RLC PDU and initialize an RLC reordering timer. Within the RLC reordering timer period, a HARQ process may be conducted to recover the missing LTE RLC PDUs.
  • the RLC sublayer may generate and transmit an RLC status PDU to the LTE base station to initiate an ARQ process for retransmission of the missing LTE RLC PDUs.
  • the RLC status PDU may include acknowledgement information (e.g., ACK/NACK) for one or more LTE RLC PDUs 702.
  • the RLC sublayer maintains the received LTE PDCP PDUs 704 in the RLC buffer until the missing LTE RLC PDUs 702 are recovered. In some examples, it may take X ms to recover the missing LTE RLC PDUs 702 via ARQ.
  • the RLC sublayer may buffer PDCP PDUs 0–29 and initiate the RLC reordering timer to begin HARQ.
  • the RLC sublayer may generate and transmit an RLC status PDU to initiate ARQ retransmission of LTE RLC PDUs 0 and 1.
  • the RLC sublayer may then deliver the LTE PDCP PDUs 0–29 from the RLC buffer to the PDCP sublayer once the LTE RLC PDUs 0 and 1 are recovered.
  • PDCP reordering in the PDCP sublayer may be enabled to allow out-of-order delivery of PDCP PDUs from the NR RLC sublayer to the NR PDCP sublayer. For example, if the NR link is experiencing a low BLER, and therefore, NR RLC PDUs 710 are able to be properly decoded, the RLC sublayer may deliver NR PDCP PDUs 712 to the PDCP sublayer regardless of whether any LTE PDCP PDUs 704 remain buffered in the RLC buffer.
  • the RLC sublayer may deliver PDCP PDUs 30–49 to the PDCP sublayer upon decoding of NR RLC PDUs 0–19.
  • the PDCP sublayer may initiate a PDCP reordering timer.
  • the PDCP reordering timer expires before the RLC sublayer completes ARQ of the missing LTE RLC PDUs
  • all of the PDCP PDUs e.g., PDCP PDUs 0–29
  • the LTE RLC buffer may be discarded, even though some of the PDCP PDUs (e.g., PDCP PDUs 10–29) may be mapped to complete (decoded) LTE RLC PDUs (e.g., LTE RLC PDUs 2–5) .
  • discarding of PDCP PDUs 0–29 may occur if the PDCP reordering timer ⁇ (LTE RLC reordering timer + X) , where X refers to the amount of time to complete ARQ (e.g., the amount of time needed to recover the missing LTE RLC PDUs via ARQ) .
  • the RLC sublayer may deliver out-of-order LTE PDCP PDUs 704 to the PDCP sublayer after successfully decoding the corresponding LTE RLC PDUs 702 mapped to those PDCP PDUs.
  • the RLC sublayer may deliver PDCP PDUs 10–29 to the PDCP sublayer.
  • the RLC sublayer may only buffer PDCP PDUs 0–9 until completion of ARQ.
  • the RLC sublayer may discard PDCP PDUs 0–9.
  • the RLC sublayer may deliver out-of-order LTE PDCP PDUs to the PDCP sublayer after expiration of the RLC reordering timer.
  • FIG. 8 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary user equipment (UE) 800 employing a processing system 814.
  • the UE 800 may correspond to any of the UEs shown and described above in reference to FIGs. 1 and/or 2.
  • the UE 800 may be implemented with a processing system 814 that includes one or more processors 804.
  • processors 804 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • the UE 800 may be configured to perform any one or more of the functions described herein. That is, the processor 804, as utilized in a UE 800, may be used to implement any one or more of the processes described below and illustrated in FIG. 10.
  • the processing system 814 may be implemented with a bus architecture, represented generally by the bus 802.
  • the bus 802 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 814 and the overall design constraints.
  • the bus 802 communicatively couples together various circuits including one or more processors (represented generally by the processor 804) , a memory 805, and computer-readable media (represented generally by the computer-readable medium 806) .
  • the bus 802 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 808 provides an interface between the bus 802 and a transceiver 810.
  • the transceiver 810 provides a means for communicating with various other apparatus over a transmission medium (e.g., air) .
  • a transmission medium e.g., air
  • a user interface 812 e.g., keypad, display, speaker, microphone, joystick
  • the processor 804 is responsible for managing the bus 802 and general processing, including the execution of software stored on the computer-readable medium 806.
  • the software when executed by the processor 804, causes the processing system 814 to perform the various functions described below for any particular apparatus.
  • the computer-readable medium 806 and the memory 805 may also be used for storing data that is manipulated by the processor 804 when executing software.
  • One or more processors 804 in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software may reside on the computer-readable medium 806.
  • the computer-readable medium 806 may be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip) , an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (e.g., a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer.
  • a magnetic storage device e.g., hard disk, floppy disk, magnetic strip
  • an optical disk e.g.
  • the computer-readable medium 806 may reside in the processing system 814, external to the processing system 814, or distributed across multiple entities including the processing system 814.
  • the computer-readable medium 806 may be embodied in a computer program product.
  • a computer program product may include a computer-readable medium in packaging materials.
  • the processor 804 may include circuitry configured for various functions.
  • the processor 804 may include communication circuitry 842.
  • the communication circuitry 842 may include one or more hardware components that provide the physical structure that performs various processes related to wireless communication (e.g., signal reception and/or signal transmission) as described herein.
  • the communication circuitry 842 may further be configured to execute communication software 852 included on the computer-readable medium 806 to implement one or more functions described herein.
  • the processor 804 may also include signal processing circuitry 844.
  • the signal processing circuitry 844 may include one or more hardware components that provide the physical structure that performs various processes related to signal processing (e.g., processing a received signal and/or processing a signal for transmission) as described herein.
  • the signal processing circuitry 844 may further be configured to execute signal processing software 854 included on the computer-readable medium 806 to implement one or more functions described herein.
  • the processor 804 may further include Radio Link Control (RLC) processing circuitry 846 configured to provide an RLC sublayer in the radio protocol architecture and Packet Data Convergence Protocol (PDCP) processing circuitry 848 configured to provide a PDCP sublayer in the radio protocol architecture.
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • the RLC processing circuitry 846 may be configured to receive RLC Protocol Data Units (PDUs) , Packet Data Convergence Protocol (PDCP) PDUs and Internet Protocol (IP) packets from a lower layer in the radio protocol architecture and to process the received RLC PDUs.
  • the PDCP processing circuitry 848 may be configured to receive PDCP PDUs and IP packets from the RLC processing circuitry 846 and to process the PDCP PDUs.
  • the RLC processing circuitry 846 and PDCP processing circuitry 848 may each be configured to implement dual connectivity during a session to receive data packets from different base stations, each supporting a different radio access technology (RAT) .
  • the RLC processing circuitry 846 may be configured to receive a plurality of (or group of) first RLC PDUs and a plurality of (or group of) first PDCP PDUs from a first base station supporting a first RAT, and a plurality of (or group of) second RLC PDUs and a plurality of (or group of) second PDCP PDUs from a second base station supporting a second RAT.
  • the first RAT may include a eUTRAN LTE RAT
  • the second RAT may include a NR RAT.
  • Each of the first RLC PDUs in the group of first RLC PDUs may include a respective first RLC sequence number assigned by the first RAT
  • each of the second RLC PDUs in the group of second RLC PDUs may include a respective second RLC sequence number assigned by the second RAT
  • each of the first and second PDCP PDUs in the groups of first and second PDCP PDUs may include a respective PDCP sequence number assigned independently of (or collectively between) the first and second RAT.
  • the PDCP sequence numbers assigned to the PDCP PDUs in the group of first PDCP PDUs may include a first set of sequential sequence numbers and the PDCP sequence numbers assigned to the PDCP PDUs in the group of second PDCP PDUs may include a second set of sequential sequence numbers immediately following the first set of sequential sequence numbers.
  • the group of first PDCP PDUs may be assigned sequence numbers 0–29, while the group of second PDCP PDUs may be assigned sequence numbers 30–49.
  • Each of the first RLC PDUs may further be mapped to a respective subset of the first PDCP PDUs, and each of the second RLC PDUs may be mapped to a respective subset of the second PDCP PDUs.
  • the RLC processing circuitry 846 when operating in an acknowledged mode (AM) , may further be configured to attempt to decode each of the first RLC PDUs, and upon successfully decoding each of the first RLC PDUs, decode and deliver the PDCP PDUs mapped to the successfully decoded first RLC PDUs to the PDCP processing circuitry 848.
  • the RLC processing circuitry 846 may further be configured to attempt to decode each of the second RLC PDUs, and upon successfully decoding each of the second RLC PDUs, decode and deliver the PDCP PDUs mapped to the successfully decoded second RLC PDUs to the PDCP processing circuitry 848.
  • the RLC processing circuitry 846 may decode and deliver PDCP PDUs to the PDCP processing circuitry 848 as soon as the corresponding RLC PDUs mapped to those PDCP PDUs have been decoded, regardless of the sequence number order.
  • both first PDCP PDUs and second PDCP PDUs may be delivered out-of-order to the PDCP processing circuitry 848.
  • the RLC processing circuitry 846 may further be configured to detect an out-of-order decoded first RLC PDU in the group of first RLC PDUs. For example, the RLC processing circuitry 846 may detect that the first RLC PDU having a sequence number of 1 was decoded, but the first RLC PDU having a sequence number of 0 has yet to be decoded. Upon detecting the out-of-order decoded first RLC PDU, the RLC processing circuitry 846 may further be configured to buffer the first PDCP PDUs mapped to the undecoded first RLC PDU (s) in an RLC buffer 815 maintained, for example, in memory 805.
  • the RLC processing circuitry 846 may initialize an RLC reordering timer 816 maintained, for example, in memory 805.
  • the RLC reordering timer 816 may be initialized with an amount of time sufficient to complete a hybrid automatic repeat request (HARQ) process for the undecoded first RLC PDU (s) .
  • HARQ hybrid automatic repeat request
  • the RLC processing circuitry 846 may terminate the RLC reordering timer 816 and decode and deliver the corresponding first PDCP PDUs mapped to the now decoded RLC PDU (s) . However, upon expiration of the RLC reordering timer 816, if the undecoded first RLC PDU (s) remain undecoded, the RLC processing circuitry 846 may generate and transmit an RLC status PDU including acknowledgement information (e.g., ACK/NACK) for the group of first RLC PDUs.
  • the RLC status PDU may include, for example, a NACK for the undecoded first RLC PDUs to initialize a retransmission (e.g., ARQ) procedure to recover the missing (undecoded) first RLC PDUs.
  • the PDCP processing circuitry 848 may further be configured to detect an out-of-order decoded PDCP PDU (e.g., when one or more of the RLC PDUs remains undecoded) .
  • the PDCP processing circuitry 848 may then be configured to initialize a PDCP reordering timer 818 maintained, for example, in memory 805 upon detecting the out-of-order PDCP PDU.
  • the PDCP processing circuitry 848 may be configured to initialize the PDCP reordering timer 818 after the RLC processing circuitry 846 delivers PDCP PDUs mapped to an out-of-order decoded RLC PDU (e.g., either an out-of-order decoded first RLC PDU or an out-of- order decoded second RLC PDU) .
  • the PDCP reordering timer 818 may be initialized substantially simultaneously to the RLC reordering timer 816.
  • the PDCP processing circuitry 848 may terminate the PDCP reordering timer 818.
  • the PDCP processing circuitry 848 may instruct the RLC processing circuitry 846 to discard any first PDCP PDUs remaining in the RLC buffer 815.
  • the PDCP reordering timer 818 may expire prior to completion of the ARQ process.
  • the number of dropped (discarded) PDCP PDUs is limited only to those mapped to RLC PDUs that failed to be decoded at the expiration of the PDCP reordering timer.
  • the RLC processing circuitry 846 may further be configured to initialize the RLC reordering timer upon detecting an out-of-order decoded first RLC PDU in the group of first RLC PDUs and to buffer all of the first PDCP PDUs mapped to first RLC PDUs received since the last in-order decoded first RLC PDU in the RLC buffer 815.
  • the RLC processing circuitry 846 may terminate the RLC reordering timer 816 and decode and deliver all of the first PDCP PDUs in the RLC buffer 815.
  • the RLC processing circuitry 846 may decode and deliver any buffered first PDCP PDUs mapped to decoded first RLC PDUs and discard any buffered first PDCP PDUs mapped to the undecoded first RLC PDU (s) .
  • the PDCP processing circuitry 848 may initiate the PDCP reordering timer 818 upon receipt of the first out-of-order second PDCP PDU.
  • the PDCP reordering timer 818 may be longer than the RLC reordering timer 816, and therefore, the PDCP reordering timer 818 may not be utilized in determining to drop (discard) first PDCP PDUs mapped to RLC PDUs that failed to be decoded at the expiration of the RLC reordering timer 816.
  • the RLC processing circuitry 846 may further be configured to execute RLC processing software 856 included on the computer-readable medium 806 to implement one or more functions described herein.
  • the PDCP processing circuitry 848 may further be configured to execute PDCP processing software 858 included on the computer-readable medium 806 to implement one or more functions described herein.
  • the circuitry included in the processor 804 is provided as non-limiting examples. Other means for carrying out the described functions exists and is included within various aspects of the present disclosure.
  • FIG. 9 is a diagram illustrating an RLC sublayer 902 and a PDCP sublayer 912 within a user equipment (UE) implementing dual connectivity.
  • the RLC sublayer 902 may correspond to, for example, the RLC processing circuitry 846 and RLC processing software 856 shown and described above in connection with FIG. 8.
  • the PDCP sublayer 912 may correspond to, for example, the PDCP processing circuitry 948 and PDCP processing software 958 shown and described above in connection with FIG. 8.
  • the RLC sublayer 902 includes an LTE RLC sublayer 904 configured to receive LTE PDUs 920 (e.g., LTE RLC and PDCP PDUs) from a lower layer and to process the LTE RLC PDUs.
  • LTE PDUs 920 e.g., LTE RLC and PDCP PDUs
  • the RLC sublayer 902 further includes a NR RLC sublayer 906 configured to receive NR PDUs 922 (e.g., NR RLC and PDCP PDUs) from a lower layer and to process the NR RLC PDUs.
  • NR PDUs 922 e.g., NR RLC and PDCP PDUs
  • the PDCP sublayer 912 includes an LTE PDCP sublayer 914 configured to receive and process LTE PDCP PDUs 924 from the LTE RLC sublayer 904 and a NR PDCP sublayer 916 configured to receive and process NR PDCP PDUs 926 from the NR RLC sublayer 906.
  • the LTE RLC sublayer 904 may be configured to attempt to decode each of the LTE RLC PDUs, and upon successfully decoding each of the LTE RLC PDUs, decode and deliver the LTE PDCP PDUs 924 mapped to the successfully decoded LTE RLC PDUs to the LTE PDCP sublayer 914.
  • the NR RLC sublayer 906 may be configured to attempt to decode each of the NR RLC PDUs, and upon successfully decoding each of the NR RLC PDUs, decode and deliver the NR PDCP PDUs 926 mapped to the successfully decoded NR RLC PDUs to the NR PDCP sublayer 916.
  • the LTE RLC sublayer 904 may further be configured to detect an out-of-order decoded LTE RLC PDU as a result of undecoded LTE RLC PDU (s) and to buffer the LTE PDCP PDUs mapped to the undecoded LTE RLC PDU (s) in an RLC buffer 908.
  • the RLC buffer 908 may correspond to, for example, the RLC buffer 815 shown and described above in connection with FIG. 8.
  • the LTE RLC sublayer 904 may further initialize an RLC reordering timer 910 with an amount of time sufficient to complete a HARQ process to attempt to recover the undecoded LTE RLC PDU (s) .
  • the RLC reordering timer 910 may correspond to, for example, the RLC reordering timer 816 shown and described above in connection with FIG. 8.
  • the LTE RLC sublayer 904 may terminate the RLC reordering timer 910 and decode and deliver the corresponding LTE PDCP PDUs mapped to the now decoded LTE RLC PDU (s) to the LTE PDCP sublayer 914.
  • the LTE RLC sublayer 904 may generate and transmit an RLC status PDU including, for example, a NACK for the undecoded LTE RLC PDUs to initialize a retransmission (e.g., ARQ) procedure to recover the missing (undecoded) LTE RLC PDUs.
  • a retransmission e.g., ARQ
  • the LTE PDCP sublayer 914 and the NR PDCP sublayer 916 may collectively be configured to detect an out-of-order decoded PDCP PDU (e.g., when one or more of the LTE RLC PDUs remains undecoded) .
  • the NR PDCP sublayer 916 may then be configured to initialize a PDCP reordering timer 918 after the RLC sublayer 902 delivers PDCP PDUs mapped to an out-of-order decoded RLC PDU.
  • the PDCP reordering timer 918 may correspond to, for example, the PDCP reordering timer 818 shown and described above in connection with FIG. 8.
  • the NR PDCP sublayer 916 may terminate the PDCP reordering timer 918. However, upon expiration of the PDCP reordering timer 918, if the missing LTE PDCP PDUs remain missing, the NR PDCP sublayer 916 may instruct the LTE RLC sublayer 904 via the LTE PDCP sublayer 914 to discard any LTE PDCP PDUs remaining in the RLC buffer 908.
  • the LTE RLC sublayer 904 When operating in an unacknowledged mode (UM) , after the LTE RLC sublayer 904 detects an out-of-order decoded LTE RLC PDU, the LTE RLC sublayer 904 may initialize the RLC reordering timer 910 and buffer all of the LTE PDCP PDUs mapped to LTE RLC PDUs received since the last in-order decoded LTE RLC PDU in the RLC buffer 908.
  • UM unacknowledged mode
  • the LTE RLC sublayer may terminate the RLC reordering timer 910 and decode and deliver all of the LTE PDCP PDUs 924 in the RLC buffer 908.
  • the LTE RLC sublayer 902 may decode and deliver any buffered LTE PDCP PDUs mapped to decoded LTE RLC PDUs and discard any buffered LTE PDCP PDUs mapped to the undecoded LTE RLC PDU (s) .
  • the NR PDCP sublayer 916 may also initiate the PDCP reordering timer 918 upon receipt of the first out-of-order NR PDCP PDU 926.
  • FIG. 10 is a flow chart illustrating an exemplary process 1000 for delivering out-of-order PDCP PDUs to the PDCP sublayer in accordance with some aspects of the present disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments.
  • the process 1000 may be carried out by the UE 800 illustrated in FIG. 8. In some examples, the process 1000 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.
  • the UE configured to dual connectivity between LTE and NR RATs may receive a plurality of LTE RLC PDUs and a plurality of LTE PDCP PDUs from an LTE base station in wireless communication with the UE.
  • Each of the LTE RLC PDUs may be mapped to a respective subset of the plurality of LTE PDCP PDUs.
  • each of the LTE RLC PDUs may include a respective sequence number (SN) assigned by the LTE RAT, and each of the LTE PDCP PDUs may include a respective SN assigned independent of the RAT.
  • the RLC processing circuitry 846 and transceiver 810 shown and described above in reference to FIG. 8 may receive the LTE RLC PDUs and LTE PDCP PDUs.
  • the UE may receive a plurality of NR RLC PDUs and a plurality of NR PDCP PDUs from a NR base station in wireless communication with the UE.
  • Each of the NR RLC PDUs may be mapped to a respective subset of the plurality of NR PDCP PDUs.
  • each of the NR RLC PDUs may include a respective sequence number (SN) assigned by the NR RAT, and each of the NR PDCP PDUs may include a respective SN assigned independent of the RAT.
  • the NR PDCP PDUs may include SN’s that immediately follow the SNs of the LTE PDCP PDUs.
  • the RLC processing circuitry 846 and transceiver 810 shown and described above in reference to FIG. 8 may receive the NR RLC PDUs and NR PDCP PDUs.
  • the UE may detect an out-of-order PDCP PDU delivered to the PDCP sublayer from the RLC sublayer. For example, due to high BLER on the LTE downlink, one or more LTE RLC PDUs may fail to be decoded, thus resulting in the UE requesting retransmission via HARQ and ARQ of the undecoded (missing) LTE RLC PDUs when the RLC sublayer is operating in acknowledged mode (AM) .
  • AM acknowledged mode
  • the LTE PDCP PDUs mapped to the missing LTE RLC PDUs may be buffered, resulting in out-of-order LTE PDCP PDUs and/or NR PDCP PDUs being delivered to the PDCP sublayer.
  • the UE may request retransmission via HARQ of the undecoded (missing) LTE RLC PDUs and buffer LTE PDCP PDUs mapped to LTE RLC PDUs received since the last in-order RLC PDU during the pendency of an RLC reordering timer initiated upon detecting an out-of-order decoded RLC PDU.
  • the PDCP sublayer may detect an out-of-order NR PDCP PDU (e.g., due to the buffering of the LTE PDCP PDUs) .
  • the PDCP processing circuitry 848 shown and described above in reference to FIG. 8 may detect an out-of-order PDCP PDU.
  • the UE may initiate a PDCP reordering timer.
  • the PDCP processing circuitry 848 shown and described above in reference to FIG. 8 may initiate the PDCP reordering timer.
  • the UE determines whether the PDCP reordering timer has expired. If the PDCP reordering timer has not expired (N branch of block 1010) , at block 1012, the UE may deliver LTE PDCP PDUs mapped to decoded RLC PDUs from the RLC sublayer to the PDCP sublayer. For example, in acknowledged mode, the UE may deliver LTE PDCP PDUs from the RLC sublayer to the PDCP sublayer as the corresponding LTE RLC PDUs mapped thereto are decoded.
  • the UE may deliver buffered LTE PDCP PDUs mapped to decoded LTE RLC PDUs upon expiration of the RLC reordering timer.
  • the RLC processing circuitry 846 and PDCP processing circuitry 848 shown and described above in connection with FIG. 8 may determine whether the PDCP reordering timer has expired, and if not, deliver LTE PDCP PDUs mapped to decoded LTE RLC PDUs from the RLC sublayer to the PDCP sublayer.
  • the UE may discard buffered LTE PDCP PDUs mapped to missing (undecoded) LTE RLC PDUs.
  • the RLC processing circuitry 846 and PDCP processing circuitry 848 shown and described above in connection with FIG. 8 may discard buffered LTE PDCP PDUs upon expiration of the PDCP reordering timer.
  • various aspects may be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE) , the Evolved Packet System (EPS) , the Universal Mobile Telecommunication System (UMTS) , and/or the Global System for Mobile (GSM) .
  • LTE Long-Term Evolution
  • EPS Evolved Packet System
  • UMTS Universal Mobile Telecommunication System
  • GSM Global System for Mobile
  • Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2) , such as CDMA2000 and/or Evolution-Data Optimized (EV-DO) .
  • 3GPP2 3rd Generation Partnership Project 2
  • EV-DO Evolution-Data Optimized
  • Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Ultra-Wideband (UWB) , Bluetooth, and/or other suitable systems.
  • Wi-Fi IEEE 802.11
  • WiMAX IEEE 8
  • the word “exemplary” is used to mean “serving as an example, instance, or illustration. ” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspects” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.
  • the term “coupled” is used herein to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C may still be considered coupled to one another-even if they do not directly physically touch each other. For instance, a first object may be coupled to a second object even though the first object is never directly physically in contact with the second object.
  • circuit and “circuitry” are used broadly, and intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in the present disclosure, without limitation as to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in the present disclosure.
  • FIGs. 1–10 One or more of the components, steps, features and/or functions illustrated in FIGs. 1–10 may be rearranged and/or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from novel features disclosed herein.
  • the apparatus, devices, and/or components illustrated in FIGs. 1, 2 and 8 may be configured to perform one or more of the methods, features, or steps described herein.
  • the novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware.
  • “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Certains procédés et équipements fournissent des mécanismes de délivrance de PDU non ordonnées de PDCP à la sous-couche de PDCP. Dans un équipement d'utilisateur configuré pour une double connectivité entre LTE et NR, lors de la délivrance d'au moins une PDU non ordonnée de PDCP de la sous-couche de RLC à la sous-couche de PDCP, un temporisateur de réordonnancement de PDCP peut être initialisé. Pour empêcher le rejet des PDU de PDCP à LTE tandis que la sous-couche de RLC met en œuvre une procédure de retransmission, avant l'expiration du temporisateur de réordonnancement de PDCP, les PDU non ordonnées de PDCP à LTE mises en correspondance avec des PDU décodées de RLC à LTE peuvent être délivrées de la sous-couche de RLC à la sous-couche de PDCP sans les réordonnancer. Lorsque le temporisateur de réordonnancement de PDCP expire, toutes les PDU de PDCP à LTE mises en correspondance aves des PDU de RLC à LTE manquantes peuvent être rejetées.
PCT/CN2018/114114 2018-11-06 2018-11-06 Délivrance d'unités de données de protocole (pdu) non ordonnées de protocole de convergence de données par paquets (pdcp) à un pdcp WO2020093230A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2018/114114 WO2020093230A1 (fr) 2018-11-06 2018-11-06 Délivrance d'unités de données de protocole (pdu) non ordonnées de protocole de convergence de données par paquets (pdcp) à un pdcp
PCT/CN2019/114269 WO2020093915A1 (fr) 2018-11-06 2019-10-30 Gestion d'unités de données de protocole de protocole de convergence de données par paquets (pdcp)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/114114 WO2020093230A1 (fr) 2018-11-06 2018-11-06 Délivrance d'unités de données de protocole (pdu) non ordonnées de protocole de convergence de données par paquets (pdcp) à un pdcp

Publications (1)

Publication Number Publication Date
WO2020093230A1 true WO2020093230A1 (fr) 2020-05-14

Family

ID=70611596

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2018/114114 WO2020093230A1 (fr) 2018-11-06 2018-11-06 Délivrance d'unités de données de protocole (pdu) non ordonnées de protocole de convergence de données par paquets (pdcp) à un pdcp
PCT/CN2019/114269 WO2020093915A1 (fr) 2018-11-06 2019-10-30 Gestion d'unités de données de protocole de protocole de convergence de données par paquets (pdcp)

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/114269 WO2020093915A1 (fr) 2018-11-06 2019-10-30 Gestion d'unités de données de protocole de protocole de convergence de données par paquets (pdcp)

Country Status (1)

Country Link
WO (2) WO2020093230A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022007530A1 (fr) * 2020-07-10 2022-01-13 Qualcomm Incorporated Amélioration de la couche croisée avec rétroaction de commande de liaison radio sur couche physique
WO2022012676A1 (fr) * 2020-07-17 2022-01-20 Qualcomm Incorporated Optimisation de calage de données de liaison montante par adressage d'une séquence de paquets en désordre
WO2022094832A1 (fr) 2020-11-05 2022-05-12 Qualcomm Incorporated Techniques de reprise à la suite d'un blocage de données à connectivité double

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117479229A (zh) * 2022-07-22 2024-01-30 中国移动通信有限公司研究院 数据包处理方法、装置、电子设备及可读存储介质
CN117560112A (zh) * 2022-08-01 2024-02-13 大唐移动通信设备有限公司 一种信息传输方法、装置及通信设备
CN118450433B (zh) * 2023-11-15 2024-12-31 荣耀终端有限公司 一种数据处理方法及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160234127A1 (en) * 2015-02-09 2016-08-11 International Business Machines Corporation Handling packet reordering at a network adapter
US20170181185A1 (en) * 2014-03-02 2017-06-22 Lg Electronics Inc. Method for reordering a packet data convergence protocol packet data unit at a user equipment in a dual connectivity systme and device therefor
US20170264562A1 (en) * 2014-05-13 2017-09-14 Lg Electronics Inc. Method for reordering a packet data convergence protocol packet data unit at a user equipment in a dual connectivity system and device therefor
US20180317279A1 (en) * 2014-01-29 2018-11-01 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data using a plurality of carriers in mobile communication system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330492B (zh) * 2007-06-19 2012-08-01 上海贝尔股份有限公司 数据发送方法、数据接收方法和设备
WO2013044982A1 (fr) * 2011-09-30 2013-04-04 Nokia Siemens Networks Oy Interruptions dans des communications sans fil
US9999049B2 (en) * 2015-08-31 2018-06-12 Qualcomm Incorporated Avoiding unnecessary protocol data unit (PDU) transmissions
US10237784B2 (en) * 2017-03-24 2019-03-19 Motorola Mobility Llc Split bearer packet data converge protocol protocol data unit routing
EP3607792B1 (fr) * 2017-04-02 2023-10-04 FG Innovation Company Limited Procédé de transmission de paquets de données de canal logique et équipement utilisateur

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180317279A1 (en) * 2014-01-29 2018-11-01 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data using a plurality of carriers in mobile communication system
US20170181185A1 (en) * 2014-03-02 2017-06-22 Lg Electronics Inc. Method for reordering a packet data convergence protocol packet data unit at a user equipment in a dual connectivity systme and device therefor
US20170264562A1 (en) * 2014-05-13 2017-09-14 Lg Electronics Inc. Method for reordering a packet data convergence protocol packet data unit at a user equipment in a dual connectivity system and device therefor
US20160234127A1 (en) * 2015-02-09 2016-08-11 International Business Machines Corporation Handling packet reordering at a network adapter

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022007530A1 (fr) * 2020-07-10 2022-01-13 Qualcomm Incorporated Amélioration de la couche croisée avec rétroaction de commande de liaison radio sur couche physique
WO2022012676A1 (fr) * 2020-07-17 2022-01-20 Qualcomm Incorporated Optimisation de calage de données de liaison montante par adressage d'une séquence de paquets en désordre
WO2022094832A1 (fr) 2020-11-05 2022-05-12 Qualcomm Incorporated Techniques de reprise à la suite d'un blocage de données à connectivité double
CN116458202A (zh) * 2020-11-05 2023-07-18 高通股份有限公司 用于从双连通性数据停顿中恢复的技术
EP4241405A4 (fr) * 2020-11-05 2024-10-16 Qualcomm Incorporated Techniques de reprise à la suite d'un blocage de données à connectivité double
CN116458202B (zh) * 2020-11-05 2025-02-25 高通股份有限公司 用于从双连通性数据停顿中恢复的技术

Also Published As

Publication number Publication date
WO2020093915A1 (fr) 2020-05-14

Similar Documents

Publication Publication Date Title
US11917472B2 (en) Facilitating quality of service flow remapping utilizing a service data adaptation protocol layer
US11349613B2 (en) Retransmission indication based on an acknowledgement based feedback scheme for wireless communication
EP3738289B1 (fr) Strate d'accès basée sur les services (as) configuration de sécurité
US10972937B2 (en) Group indicator for code block group based retransmission in wireless communication
US10462066B2 (en) Apparatus and method for reordering data radio bearer packets
WO2020093915A1 (fr) Gestion d'unités de données de protocole de protocole de convergence de données par paquets (pdcp)
EP3689020A1 (fr) Formats d'en-tête en communication sans fil
CN110800227A (zh) 用于不可靠的码块群(cbg)级反馈下的下行链路重传的方法和装置
EP4190019B1 (fr) Controle et livraison hors service pdcp controlé par api pour le trafic de liaison descendante
WO2021142764A1 (fr) Évitement d'une suppression erronée de données de liaison descendante dans un mode sans accusé de réception (um)
CN115336318B (zh) 用于无线通信的方法和装置
US20250015934A1 (en) Hyper frame number (hfn) resynchronization of packet data convergence protocol (pdcp) protocol data units
US20230224252A1 (en) Downlink data stall optimization by addressing an out-of-order packet sequence

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18939668

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18939668

Country of ref document: EP

Kind code of ref document: A1