WO2022187831A1 - Recovery after packet data convergence protocol packet discard - Google Patents
Recovery after packet data convergence protocol packet discard Download PDFInfo
- Publication number
- WO2022187831A1 WO2022187831A1 PCT/US2022/070923 US2022070923W WO2022187831A1 WO 2022187831 A1 WO2022187831 A1 WO 2022187831A1 US 2022070923 W US2022070923 W US 2022070923W WO 2022187831 A1 WO2022187831 A1 WO 2022187831A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- packet
- radio bearer
- timer
- expiry
- transmission
- Prior art date
Links
- 238000011084 recovery Methods 0.000 title description 11
- 230000005540 biological transmission Effects 0.000 claims abstract description 104
- 238000004891 communication Methods 0.000 claims abstract description 84
- 238000000034 method Methods 0.000 claims description 113
- 230000008569 process Effects 0.000 description 46
- 238000010586 diagram Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 15
- 238000001514 detection method Methods 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 230000003321 amplification Effects 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000013507 mapping Methods 0.000 description 4
- 238000003199 nucleic acid amplification method Methods 0.000 description 4
- 238000012937 correction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000001172 regenerating effect Effects 0.000 description 3
- 241000700159 Rattus Species 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000001228 spectrum Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 239000000872 buffer Substances 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000003595 spectral effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
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/04—Error control
Definitions
- aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for recovery after discard of a packet data convergence protocol packet.
- Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
- Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like).
- multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC- FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE).
- LTE/LTE- Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
- UMTS Universal Mobile Telecommunications System
- a wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs.
- a UE may communicate with a base station via downlink communications and uplink communications.
- Downlink (or “DL”) refers to a communication link from the base station to the UE
- uplink (or “UL”) refers to a communication link from the UE to the base station.
- NR New Radio
- 5G is a set of enhancements to the LTE mobile standard promulgated by the 3GPP.
- NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple -input multiple -output (MIMO) antenna technology, and carrier aggregation.
- OFDM orthogonal frequency division multiplexing
- SC-FDM single-carrier frequency division multiplexing
- DFT-s-OFDM discrete Fourier transform spread OFDM
- MIMO multiple -input multiple -output
- the radio bearer may include a memory and one or more processors coupled to the memory.
- the one or more processors may be configured to detect, at a packet data convergence protocol (PDCP) layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer.
- the one or more processors may be further configured to re enqueue, at a modem of the radio bearer or at an application layer of the radio bearer and based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before discarding the packet.
- PDCP packet data convergence protocol
- the radio bearer may include a memory and one or more processors coupled to the memory.
- the one or more processors may be configured to detect, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer.
- the one or more processors may be further configured to retransmit the packet based at least in part on instructions from an application, executed on the one or more processors, that received the packet from the PDCP layer before the packet was discarded.
- Some aspects described herein relate to a method of wireless communication performed by a radio bearer.
- the method may include detecting, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer.
- the method may further include re-enqueuing, based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before discarding the packet.
- Some aspects described herein relate to a method of wireless communication performed by a radio bearer.
- the method may include detecting, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer.
- the method may further include retransmitting the packet based at least in part on instructions from an application, executed on one or more processors of the radio bearer, that received the packet from the PDCP layer before the packet was discarded.
- Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a radio bearer.
- the set of instructions when executed by one or more processors of the radio bearer, may cause the radio bearer to detect, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer.
- the set of instructions when executed by one or more processors of the radio bearer, may further cause the radio bearer to re-enqueue, based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before discarding the packet.
- Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a radio bearer.
- the set of instructions when executed by one or more processors of the radio bearer, may cause the radio bearer to detect, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer.
- the set of instructions when executed by one or more processors of the radio bearer, may further cause the radio bearer to retransmit the packet based at least in part on instructions from an application, executed on the one or more processors, that received the packet from the PDCP layer before the packet was discarded.
- the apparatus may include means for detecting, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the apparatus is configured to discard the packet upon expiry of the timer.
- the apparatus may further include means for re-enqueuing, based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before discarding the packet.
- Some aspects described herein relate to an apparatus for wireless communication.
- the apparatus may include means for detecting, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the apparatus is configured to discard the packet upon expiry of the timer.
- the apparatus may further include means for retransmitting the packet based at least in part on instructions from an application, executed on one or more processors of the apparatus, that received the packet from the PDCP layer before the packet was discarded.
- aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios.
- Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements.
- some aspects may be implemented via integrated chip embodiments or other non-module- component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices).
- Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components.
- Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects.
- transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers).
- RF radio frequency
- aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.
- FIG. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.
- FIG. 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
- UE user equipment
- Fig. 3 is a diagram illustrating an example of a protocol stack for a radio bearer, in accordance with the present disclosure.
- Fig. 4 is a diagram illustrating an example of downlink and uplink between a base station and a UE, in accordance with the present disclosure.
- Fig. 5 is a diagram illustrating an example associated with recovery after discard of a packet data convergence protocol (PDCP) packet, in accordance with the present disclosure.
- Figs. 6 and 7 are diagrams illustrating example processes associated with recovery after discard of a PDCP packet, in accordance with the present disclosure.
- PDCP packet data convergence protocol
- FIGs. 8 and 9 are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.
- Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure.
- the wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples.
- 5G e.g., NR
- 4G e.g., Long Term Evolution (LTE) network
- the wireless network 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110b, a BS 110c, and a BS 1 lOd), a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and/or other network entities.
- a base station 110 is an entity that communicates with UEs 120.
- a base station 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and/or a transmission reception point (TRP).
- Each base station 110 may provide communication coverage for a particular geographic area.
- the term “cell” can refer to a coverage area of a base station 110 and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.
- a network node may be implemented in an aggregated or disaggregated architecture.
- RAN radio access network
- a base station such as a Node B (NB), evolved NB (eNB), NR base station (BS), 5G NB, gNodeB (gNB), access point (AP), transmit receive point (TRP), or cell
- NB Node B
- eNB evolved NB
- BS NR base station
- 5G NB gNodeB
- AP access point
- TRP transmit receive point
- Cell may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.
- Network entity or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).
- An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (for example, within a single device or unit).
- a disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs).
- a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes.
- the DUs may be implemented to communicate with one or more RUs.
- Each of the CU, DU, and RU also may be implemented as virtual units (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).
- VCU virtual central unit
- VDU virtual distributed unit
- VRU virtual radio unit
- Base station-type operation or network design may consider aggregation characteristics of base station functionality.
- disaggregated base stations may be utilized in an integrated access backhaul (LAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of communication systems by separating base station functionality into one or more units that may be individually deployed.
- a disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which may enable flexibility in network design.
- the various units of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
- a base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell.
- a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
- a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription.
- a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)).
- CSG closed subscriber group
- a base station 110 for a macro cell may be referred to as a macro base station.
- a base station 110 for a pico cell may be referred to as a pico base station.
- a base station 110 for a femto cell may be referred to as a femto base station or an in-home base station.
- the BS 110a may be a macro base station for a macro cell 102a
- the BS 110b may be a pico base station for a pico cell 102b
- the BS 110c may be a femto base station for a femto cell 102c.
- a base station may support one or multiple (e.g., three) cells.
- the term “base station” (e.g., the base station 110) or “network node” or “network entity” may refer to an aggregated base station, a disaggregated base station (e.g., described above), an integrated access and backhaul (IAB) node, a relay node, and/or one or more components thereof.
- base station,” “network node,” or “network entity” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof.
- the term “base station,” “network node,” or “network entity” may refer to one device configured to perform one or more functions, such as those described herein in connection with the base station 110.
- the term “base station,” “network node,” or “network entity” may refer to a plurality of devices configured to perform the one or more functions
- each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function
- the term “base station,” “network node,” or “network entity” may refer to any one or more of those different devices.
- base station may refer to one or more virtual base stations and/or one or more virtual base station functions.
- base station may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.
- a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a base station 110 that is mobile (e.g., a mobile base station).
- the base stations 110 may be interconnected to one another and/or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.
- the wireless network 100 may include one or more relay stations.
- a relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110).
- a relay station may be a UE 120 that can relay transmissions for other UEs 120.
- the BS 1 lOd e.g., a relay base station
- the BS 110a e.g., a macro base station
- the UE 120d in order to facilitate communication between the BS 110a and the UE 120d.
- a base station 110 that relays communications may be referred to as a relay station, a relay base station, a relay, or the like.
- the wireless network 100 may be a heterogeneous network that includes base stations 110 of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).
- a network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110.
- the network controller 130 may communicate with the base stations 110 via a backhaul communication link.
- the base stations 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
- the UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile.
- a UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit.
- a UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular component or sensor,
- Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
- An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a base station, another device (e.g., a remote device), or some other entity.
- Some UEs 120 may be considered Intemet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices.
- Some UEs 120 may be considered a Customer Premises Equipment.
- a UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components.
- the processor components and the memory components may be coupled together.
- the processor components e.g., one or more processors
- the memory components e.g., a memory
- the processor components and the memory components may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.
- any number of wireless networks 100 may be deployed in a given geographic area.
- Each wireless network 100 may support a particular RAT and may operate on one or more frequencies.
- a RAT may be referred to as a radio technology, an air interface, or the like.
- a frequency may be referred to as a carrier, a frequency channel, or the like.
- Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
- NR or 5G RAT networks may be deployed.
- two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a base station
- the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to- vehicle (V2V) protocol, a vehicle -to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network.
- V2X vehicle-to-everything
- a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.
- Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands.
- devices of the wireless network 100 may communicate using one or more operating bands.
- two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
- FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
- EHF extremely high frequency
- ITU International Telecommunications Union
- FR3 7.125 GHz - 24.25 GHz
- FR3 7.125 GHz - 24.25 GHz
- Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
- higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
- FR4a or FR4-1 52.6 GHz - 71 GHz
- FR4 52.6 GHz - 114.25 GHz
- FR5 114.25 GHz - 300 GHz
- Each of these higher frequency bands falls within the EHF band.
- sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
- millimeter wave may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
- frequencies included in these operating bands may be modified, and techniques described herein are applicable to those modified frequency ranges.
- example 100 includes a regenerative satellite deployment and a transparent satellite deployment in a non-terrestrial network (NTN).
- NTN non-terrestrial network
- the UE 120a is served by a satellite 140 via a service link 104.
- the satellite 140 may include a BS or a gNB.
- the satellite 140 may be referred to as a non-terrestrial base station, a regenerative repeater, or an on-board processing repeater.
- the satellite 140 may demodulate an uplink radio frequency signal and may modulate a baseband signal derived from the uplink radio signal to produce a downlink radio frequency transmission.
- the satellite 140 may transmit the downlink radio frequency signal on the service link 104.
- the satellite 140 may provide a cell that covers the UE 120a.
- the UE 120e is served by a satellite 150 via the service link 106.
- the satellite 150 may be a transparent satellite.
- the satellite 150 may relay a signal received from a gateway (e.g., the BS 110a in example 100) via a feeder link 108.
- the satellite 150 may receive an uplink radio frequency transmission and may transmit a downlink radio frequency transmission without demodulating the uplink radio frequency transmission.
- the satellite 150 may frequency convert the uplink radio frequency transmission received on the service link 106 to a frequency of the uplink radio frequency transmission on the feeder link 108 and may amplify and/or fdter the uplink radio frequency transmission.
- the UE 120e may be associated with a global navigation satellite system (GNSS) capability and/or a global positioning system (GPS) capability, though not all UEs have such capabilities.
- GNSS global navigation satellite system
- GPS global positioning system
- the satellite 150 may provide a cell that covers the UE 120.
- the service link 106 may include a link between the satellite 150 and the UE 120e, and the service link 106 may include one or more of an uplink or a downlink.
- the feeder link 108 may include a link between the satellite 150 and the BS 110a and may include one or more of an uplink (e.g., from the UE 120e to the BS 110a) or a downlink (e.g., from the BS 110a to the UE 120e).
- the service links 104 and 106 and the feeder link 108 may each experience Doppler effects due to the movement of the satellites 140 and 150, and potentially movement of the UE 120e. These Doppler effects may be significantly larger than in a terrestrial network.
- the Doppler effect on the feeder link 108 may be compensated for to some degree, but the feeder link 108 may still be associated with some amount of uncompensated frequency error.
- the BS 110a may be associated with a residual frequency error, and/or the satellite 140 or the satellite 150 may be associated with an on-board frequency error. These sources of frequency error may cause a received downlink frequency at the UE 120 to drift from a target downlink frequency.
- Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
- Fig. 2 is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure.
- the base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T> 1).
- the UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas ( R > 1).
- a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120).
- the transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120.
- MCSs modulation and coding schemes
- CQIs channel quality indicators
- the base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120.
- the transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols.
- the transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)).
- reference signals e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)
- synchronization signals e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)
- a transmit (TX) multiple -input multiple -output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t.
- each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232.
- Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
- Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal.
- the modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.
- a set of antennas 252 may receive the downlink signals from the base station 110 and/or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r.
- R received signals e.g., R received signals
- each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254.
- DEMOD demodulator component
- Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples.
- Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols.
- a MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
- a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280.
- controller/processor may refer to one or more controllers, one or more processors, or a combination thereof.
- a channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples.
- RSRP reference signal received power
- RSSI received signal strength indicator
- RSSRQ reference signal received quality
- CQI CQI parameter
- the network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292.
- the network controller 130 may include, for example, one or more devices in a core network.
- the network controller 130 may communicate with the base station 110 via the communication unit 294.
- One or more antennas may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples.
- An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig. 2.
- a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280.
- the transmit processor 264 may generate reference symbols for one or more reference signals.
- the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110.
- the modem 254 of the UE 120 may include a modulator and a demodulator.
- the UE 120 includes a transceiver.
- the transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266.
- the transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 5-9).
- the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
- the receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240.
- the base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244.
- the base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications.
- the modem 232 of the base station 110 may include a modulator and a demodulator.
- the base station 110 includes a transceiver.
- the transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230.
- the transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 5-9).
- the controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component(s) of Fig. 2 may perform one or more techniques associated with recovery after discard of a PDCP packet, as described in more detail elsewhere herein.
- the controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component(s) of Fig. 2 may perform or direct operations of, for example, process 600 of Fig. 6, process 700 of Fig. 7, and/or other processes as described herein.
- the memory 242 and the memory 282 may store data and program codes for the base station 110 and the UE 120, respectively.
- the memory 242 and/or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication.
- the one or more instructions when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the base station 110 to perform or direct operations of, for example, process 600 of Fig. 6, process 700 of Fig. 7, and/or other processes as described herein.
- executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.
- a radio bearer described herein is the UE 120, is included in the UE 120, or includes one or more components of the UE 120 shown in Fig. 2.
- a radio bearer described herein is the base station 110, is included in the base station 110, or includes one or more components of the base station 110 shown in Fig.
- a radio bearer (e.g., the UE 120 and/or apparatus 800 of Fig. 8, or network entity 401 and/or the apparatus 900 of Fig. 9) may include means for detecting, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer; and/or means for re- enqueuing, at a modem of the radio bearer or at an application layer of the radio bearer and based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before discarding the packet.
- the means for the radio bearer to perform operations described herein may include, for example, one or more of transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232,
- the means for the radio bearer to perform operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller/processor 280, or memory 282.
- a radio bearer (e.g., the UE 120 and/or apparatus 800 of Fig. 8, or network entity 401 and/or the apparatus 900 of Fig. 9) may include means for detecting, at a PDCP layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer; and/or means for retransmitting the packet based at least in part on instructions from an application, executed on one or more processors of the radio bearer, that received the packet from the PDCP layer before the packet was discarded.
- the means for the radio bearer to perform operations described herein may include, for example, one or more of transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
- the means for the radio bearer to perform operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller/processor 280, or memory 282.
- Fig. 2 While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components.
- the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.
- Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
- Fig. 3 is a diagram illustrating an example 300 of a protocol stack for a radio bearer, in accordance with the present disclosure.
- Example 300 may be implemented in a radio bearer, such as a UE 120, that receives data on a downlink (e.g., from a network entity and/or another UE) and transmits data on an uplink (e.g., from the network entity and/or another UE).
- a radio bearer such as a UE 120
- receives data on a downlink e.g., from a network entity and/or another UE
- an uplink e.g., from the network entity and/or another UE.
- example 300 includes an application and/or an operating system (shown as “App/OS” in Fig. 3) 302 that is executed using at least one processor and at least one memory of the radio bearer.
- the App/OS 302 may request that data (shown as “UL Data” in Fig.
- the data may include one or more packets (e.g., a protocol data unit (PDU) and/or another packet).
- a modem of the radio bearer may process the request from the App/OS 302 and add the packet to the UL queue 304.
- the App/OS 302 may receive data (shown as “DL data” in Fig. 3) from a reordering queue 306.
- the data may include one or more packets (e.g., a PDU and/or another packet).
- the modem of the radio bearer may receive the data from a network stack (e.g., as described below) and add the packet to the reordering queue 306.
- the radio bearer may implement a network stack that includes a PDCP layer 308, a radio link control (RLC) layer 310, and one or more lower layers, such as a medium access control (MAC) layer and a physical layer (shown as “MAC/PHY” in Fig. 3) 312.
- the PDCP layer 308 may add headers to and perform ciphering for outgoing data packets in the UL queue 304.
- the PDCP layer 308 may decode headers and remove ciphering for incoming data packets that are passed to the reordering queue 306.
- a network stack that includes a PDCP layer 308, a radio link control (RLC) layer 310, and one or more lower layers, such as a medium access control (MAC) layer and a physical layer (shown as “MAC/PHY” in Fig. 3) 312.
- the PDCP layer 308 may add headers to and perform ciphering for outgoing data packets in the UL queue 304.
- the RLC layer 310 may include at least one RLC layer 310a for legacy communications (e.g., over an LTE network or another legacy wireless network) and at least one RLC layer 310b for NR communications.
- the RLC layer 310 may implement automatic repeat request (ARQ) sessions, perform error correction when decoding data received by the MAC/PHY layer 312, and/or reorder packets received using the MAC/PHY layer 312 or transmitted using the MAC/PHY layer 312.
- ARQ automatic repeat request
- the MAC/PHY layer 312 may include at least one MAC/PHY layer 312a for legacy communications (e.g., over an LTE network or another legacy wireless network) and at least one MAC/PHY layer 312b for NR communications.
- the MAC/PHY layer 312 may generate frames for transmitting packets from the RLC layer 310 or recognize frames received over-the-air (OTA) and pass those frames as packets to the RLC layer 310. Additionally, in some aspects, the MAC/PHY layer 312 may add destination addresses to frames and transmit those frames OTA or decode destination addresses from received frames and pass frames addressed to the radio bearer as packets to the RLC layer 310.
- OTA over-the-air
- Fig. 3 is provided as an example. Other examples may differ from what is described with respect to Fig. 3.
- Fig. 4 is a diagram illustrating an example 400 of downlink and uplink between a network entity 401 and a UE 120, in accordance with the present disclosure.
- a downlink may begin with server 402 transferring data, that has been requested by or is addressed to an application and/or operating system (shown as “App/OS”) 422 of UE 120, to the network entity 401.
- the data may include one or more packets (e .g . , a PDU and/or another packet).
- the server 402 may transfer the data to the network entity 401 via a proxy (e.g., a gateway and/or another device connected to the network entity 401 through a wired and/or wireless backhaul).
- a proxy e.g., a gateway and/or another device connected to the network entity 401 through a wired and/or wireless backhaul.
- the network entity 401 may process the data at a PDCP layer 406 (which may, for example, be part of a CU of the network entity 401). For example, as described above with respect to Fig. 3, the PDCP layer 406 may add headers to and perform ciphering for the packet(s). Accordingly, the PDCP layer 406 may push the processed data to a data link layer of the network entity 401 (which may, for example, be part of a DU of the network entity 401).
- the PDCP layer 406 may use an FI interface to communicate with the data link layer.
- the data link layer may include an RFC layer 408 and a MAC/PHY layer 410.
- the RFC layer 408 may reorder the packet(s) to be transmitted (e.g., OTA using a Uu interface with the UE 120) using the MAC/PHY layer 410.
- the RFC layer 408 may implement ARQ.
- the RFC layer 408 may transmit acknowledgement signals (ACKs) and negative-acknowledgement signals (NACKs) to the UE 120.
- the MAC/PHY layer 410 may generate one or more frames for transmitting the packet(s) from the RFC layer 408, add destination addresses to the frame(s), and transmit the frame(s) OTA to the UE 120.
- the MAC/PHY layer 412 of the UE 120 may recognize one or more frames received OTA from the network entity 401, decode destination addresses from the received frame(s), and pass the frame(s) as one or more packets to the RFC layer 414. Furthermore, the RFC layer 414 may perform error correction when decoding the packet(s) and, in some cases, reorder the packet(s) received from the MAC/PHY layer 412. The RFC layer 414 may transmit, to the network entity 401, ACKs for decoded packets and NACKs for packets that fail to decode.
- the RFC layer 414 may further pass the packet(s) to a PDCP layer 416.
- the PDCP layer 416 may decode headers and remove ciphering for the packet(s) before passing the packet(s) to the software 418.
- the software 418 may then pass the data from the packet(s) to the App/OS 422 through the modem 420.
- an uplink may begin with App/OS 422 pushing data, that has been requested by or is addressed to server 402, to a modem 420 of the UE 120.
- the data may include one or more packets (e.g., a PDU and/or another packet).
- the App/OS 422 may push the data from a processor and/or a memory of the UE 120 to another part of a chipset of the UE 120 and/or to another chip included in the UE 120, where that chip and/or that portion of the chipset includes the hardware for modem 420.
- Software 418 associated with the modem 420 may pass the packet(s) to an uplink queue associated with a PDCP layer 416.
- the PDCP layer 416 may further process the data before the packet(s) are transmitted OTA (e.g., by the RLC layer 414 and the MAC/PHY layer 412). For example, as described above with respect to Fig. 3, the PDCP layer 416 may add headers to and perform ciphering for the packet(s). Accordingly, the PDCP layer 416 may push the processed data to a data link layer of the UE 120.
- the data link layer may include the RLC layer 414 and the MAC/PHY layer 412.
- the RLC layer 414 may reorder the packet(s) to be transmitted (e.g., OTA using a Uu interface with the network entity 401) using the MAC/PHY layer 412.
- the RLC layer 414 may implement ARQ.
- the RLC layer 414 may transmit ACKs and NACKs to the network entity 401.
- the MAC/PHY layer 412 may generate one or more frames for transmitting the packet(s) from the RLC layer 414, add destination addresses to the frame(s), and transmit the frame(s) OTA to the network entity 401.
- the MAC/PHY layer 410 of the network entity 401 may recognize one or more frames received OTA from the UE 120, decode destination addresses from the received frame(s), and pass the frame(s) as one or more packets to the RLC layer 408. Furthermore, the RLC layer 408 may perform error correction when decoding the packet(s) and, in some cases, reorder the packet(s) received from the MAC/PHY layer 410. The RLC layer 408 may transmit, to the UE 120, ACKs for decoded packets and NACKs for packets that fail to decode.
- the RLC layer 408 may further pass the packet(s) to a PDCP layer 406.
- the PDCP layer 406 may decode headers and remove ciphering for the packet(s) before passing the data from the packet(s) to the server 402.
- the server 402 may receive the data via the proxy 404.
- a PDCP layer of a radio bearer when a PDCP layer of a radio bearer does not receive confirmation that a queued packet (such as a PDU) has been delivered (e.g., by a MAC layer and/or a physical layer) within an amount of time (e.g., after expiry of discardTimer as defined in 3GPP Technical Specification (TS) 38.323 and/or another standard), the PDCP layer discards the queued packet.
- TS 3GPP Technical Specification
- the amount of time may be set to a specialized value or a default value.
- a network entity may configure the amount of time based at least in part on traffic conditions using network slicing or other techniques that request radio bearer setup for particular traffic.
- the network entity may configure a default amount of time when setting up a default radio bearer.
- the latency may be further exacerbated when the default amount of time is too short for traffic on the default radio bearer.
- extended reality (XR) and virtual reality (VR) packets may be particularly affected because XR and VR have very strict packet loss budgets, resulting in significant latency when packets are discarded.
- transmission control protocol (TCP) packets may be affected because TCP packets must eventually be retransmitted unlike real-time transport protocol (RTP) and/or user datagram protocol (UDP) packets.
- a PDCP layer may additionally or alternatively discard Ethernet frames (e.g., encoded according to Institute of Electrical and Electronics Engineers (IEEE) standards family 802) and/or unstructured data.
- IEEE Institute of Electrical and Electronics Engineers
- the radio bearer may reduce latency by preventing packet loss before retransmission of those packets. Additionally, or alternatively, some techniques and apparatuses described herein enable a radio bearer (such as UE 120 or network entity 401) to perform early retransmission of packets before they are discarded by a PDCP layer. As a result, the radio bearer may reduce latency between loss of the packets and retransmission of those packets.
- a radio bearer such as UE 120 or network entity 401
- the radio bearer may reduce latency between loss of the packets and retransmission of those packets.
- Fig. 5 is a diagram illustrating an example 500 associated with recovery after discard of a PDCP packet, in accordance with the present disclosure.
- example 500 includes communication between a network entity 401 and a UE 120.
- the network entity 401 and the UE 120 may be included in a wireless network, such as wireless network 100.
- the network entity 401 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.
- a wireless access link which may include an uplink and a downlink.
- the UE 120 may detect, at PDCP layer 502, expiry of a timer associated with a packet for transmission.
- the packet may be for transmission on the uplink to the network entity 401.
- the PDCP layer 502 may have begun the timer after passing the packet to one or more lower layers of the UE 120 (e.g., an RLC layer and/or a data link layer including at least a MAC layer and a physical layer).
- the timer may expire because the PDCP layer 502 has not received, from the lower layer(s), confirmation that the network entity 401 received and decoded the packet.
- the lower layer(s) may have not yet received an ACK from the network entity 401 and/or may have received at least one NACK from the network entity 401.
- a value of the timer may be associated with a default radio bearer configuration.
- the timer may be associated with a specialized (also referred to as “dedicated”) radio bearer configuration.
- the network entity 401 may have transmitted, and the UE 120 may have received, a radio bearer configuration that indicated a value of the timer.
- the radio bearer configuration may be a PDCP-Config data structure as defined in 3 GPP TS 38.331 and/or another standard and may include a discardTimer variable as defined in 3GPP TS 38.331 and/or another standard that indicates the value of the timer.
- the UE 120 may be configured to discard the packet upon expiry of the timer (e.g., in accordance with 3GPP TS 38.323 and/or another standard). However, in some aspects, the UE 120 may re-enqueue, based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before the PDCP layer 502 discards the packet. For example, as shown in connection with reference number 510a, the PDCP layer 502 may re-enqueue the packet (e.g., by adding the packet to an uplink queue, as described above with respect to Fig. 3, as though it were a new packet). Accordingly, the lower layer(s) of the UE 120 may retransmit the packet sooner than if the PDCP layer 502 had discarded the packet without re-enqueuing.
- the PDCP layer 502 may retransmit the packet sooner than if the PDCP layer 502 had discarded the packet without re-enqueuing.
- the PDCP layer 502 may pass the packet to software associated with a modem 504 before discarding the packet.
- the software may include a driver associated with the modem 504.
- the modem 504 may re-enqueue the packet.
- the modem 504 may re enqueue the packet by adding the packet to an uplink queue, as described above with respect to Fig. 3, as though it were a new packet.
- the PDCP layer 502 may retransmit the packet sooner than if the PDCP layer 502 had discarded the packet without the modem 504 re enqueuing the packet.
- the PDCP layer 502 may pass the packet to an application 506 executed on the UE 120 (e.g., via the modem 504).
- the application 506 may include an operating system or an application executed on top of the operating system.
- the application 506 may re-enqueue the packet.
- the application 506 may provide the packet to the modem 504 as though it were new traffic for transmission to the network entity 401.
- the modem 504 may add the packet to an uplink queue, as described above with respect to Fig. 3, and the PDCP layer 502 may retransmit the packet sooner than if the PDCP layer 502 had discarded the packet without the application 506 re enqueuing that packet.
- the application 506 may request early retransmission of the packet.
- the application 506 may duplicate the packet and send instructions to the PDCP layer 502 (e.g., via the modem 504) to retransmit based at least in part on the duplication.
- the application 506 may provide the duplicated packet to the modem 504 as though it were new traffic for transmission to the network entity 401.
- the modem 504 may schedule retransmission of the duplicated packet with the PDCP layer 502.
- the modem 504 may add the packet to an uplink queue, as described above with respect to Fig. 3, and the network entity 401 may receive the packet sooner than if the PDCP layer 502 had discarded the packet without the application 506 duplicating the packet.
- the PDCP layer 502 may be configured to retransmit after a threshold quantity of NACK signals (e.g., received from the network entity 401). Accordingly, the instructions from the application 506 may cause the PDCP layer 502 to retransmit the packet based at least in part on fewer NACK signals than the threshold quantity. For example, the PDCP layer 502 may be configured to attempt retransmission of the packet only after receiving (e.g., via the lower layer(s)) three NACKs from the network entity 401. Moreover, if the timer has expired before receiving three NACKs, the PDCP layer 502 may have to request the application 506 to provide the packet again since the PDCP layer 502 will have discarded the packet.
- a threshold quantity of NACK signals e.g., received from the network entity 401
- the instructions from the application 506 may cause the PDCP layer 502 to retransmit the packet based at least in part on fewer NACK signals than the threshold quantity.
- the instructions from the application 506 may cause the PDCP layer 502 to attempt retransmission of the packet after only one or two NACKs, such that the network entity 401 may receive the packet sooner than if the PDCP layer 502 had waited until three NACKs to attempt retransmission.
- the description similarly applies to smaller threshold quantities (such as two) and larger threshold quantities (such as four, five, and so on).
- the UE 120 may retransmit, and the network entity 401 may receive, the packet.
- the UE 120 may retransmit the packet based at least in part on re-enqueuing, as described above.
- the UE 120 may retransmit the packet based at least in part on instructions from the application 506.
- the UE 120 may use the lower layer(s), as described above, to retransmit the packet to the network entity 401.
- the UE 120 may re-enqueue and/or request early retransmission (as described above) based at least in part on a tuple associated with the packet, a flow associated with the packet, a packet delay budget associated with the packet, and/or metadata associated with the packet.
- the tuple may indicate a source (e.g., an Internet protocol (IP) address associated with the UE 120 and/or a port associated with the UE 120), a destination (e.g., an IP address associated with a server to which the packet is going and/or a port associated with that server), a protocol (e.g., a TCP, an RTP, a UDP, and/or another protocol), and/or additional information associated with the packet.
- IP Internet protocol
- a protocol e.g., a TCP, an RTP, a UDP, and/or another protocol
- the UE 120 may re-enqueue and/or request early retransmission based at least in part on the destination (e.g., performing re enqueuing and/or early retransmission for traffic addressed to one server but not another), the protocol (e.g., as described below), and/or other information included in the tuple. Additionally, or alternatively, the UE 120 may re-enqueue and/or request early retransmission based at least in part on a flow associated with the packet (e.g., based at least in part on traffic patterns associated with the packet, such as performing re-enqueuing and/or early retransmission for traffic that has been associated with a threshold quantity of timer expiries in an amount of time).
- the destination e.g., performing re enqueuing and/or early retransmission for traffic addressed to one server but not another
- the protocol e.g., as described below
- the UE 120 may re-enqueue and/or request
- the UE 120 may re-enqueue and/or request early retransmission based at least in part on a packet delay budget (PDB) associated with the packet (e.g., performing re-enqueuing and/or early retransmission for traffic that has been associated with a PDB that satisfies a PDB threshold).
- PDB packet delay budget
- the UE 120 may re-enqueue and/or request early retransmission based at least in part on a type of data associated with the packet (e.g., for XR or VR packets), a packet error loss rate associated with the packet (e.g., performing re-enqueuing and/or early retransmission for traffic that has been associated with a packet error loss rate threshold), and/or metadata associated with the packet.
- a type of data associated with the packet e.g., for XR or VR packets
- a packet error loss rate associated with the packet e.g., performing re-enqueuing and/or early retransmission for traffic that has been associated with a packet error loss rate threshold
- metadata associated with the packet.
- the packet may be associated with a TCP, an RTP, a UDP, Ethernet, application-specific protocol data, and/or unstructured data.
- application-specific protocol data may include XR data, VR data, and/or another type of data associated with a protocol specific to one or more applications executed by the radio bearer.
- the UE 120 may re-enqueue and/or request early retransmission (as described above) based at least in part on a protocol associated with the packet (e.g., the packet being associated with the TCP, Ethernet, application-specific protocol data, and/or unstructured data).
- an additional packet may be associated with a TCP, an RTP, a UDP, Ethernet, application-specific protocol data, and/or unstructured data. Accordingly, the UE 120 may discard the additional packet (e.g., at the PDCP layer 502) based at least in part on detecting expiry of an additional timer associated with the additional packet and based at least in part on a protocol associated with the packet (e.g., the packet being associated with the RTP and/or the UDP).
- the UE 120 may reduce latency for traffic where packet loss is not acceptable (e.g., TCP, Ethernet, application- specific protocol data, application-specific protocol data, and/or unstructured data traffic) while keeping network overhead lower for traffic where packet loss is acceptable (e.g., RTP traffic and/or UDP traffic).
- packet loss e.g., TCP, Ethernet, application-specific protocol data, application-specific protocol data, and/or unstructured data traffic
- network overhead lower for traffic where packet loss is acceptable
- the UE 120 may re-enqueue packets for transmission before they are discarded by the PDCP layer 502. As a result, the UE 120 may reduce latency by preventing packet loss before retransmission of those packets. Additionally, or alternatively, the UE 120 (and/or another radio bearer) may perform early retransmission of packets before they are discarded by the PDCP layer 502. As a result, the UE 120 may reduce latency between loss of the packets and retransmission of those packets.
- Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.
- Fig. 6 is a diagram illustrating an example process 600 performed, for example, by a radio bearer, in accordance with the present disclosure.
- Example process 600 is an example where the radio bearer (e.g., UE 120 and/or apparatus 800 of Fig. 8, or network entity 401 and/or apparatus 900 of Fig. 9) performs operations associated with recovery after discarding a PDCP packet.
- the radio bearer e.g., UE 120 and/or apparatus 800 of Fig. 8, or network entity 401 and/or apparatus 900 of Fig. 9
- process 600 may include detecting, at a PDCP layer, expiry of a timer associated with a packet for transmission (block 610).
- the radio bearer e.g., using detection component 808, depicted in Fig. 8 may detect expiry of the timer associated with the packet for transmission, as described above.
- the radio bearer is configured to discard the packet upon expiry of the timer.
- process 600 may include re-enqueuing, based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before discarding the packet (block 620).
- the radio bearer e.g., using queuing component 810, depicted in Fig. 8
- Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
- a value of the timer is associated with a default radio bearer configuration or a dedicated radio bearer configuration.
- the packet is for transmission on an uplink to a network entity.
- process 600 further includes receiving (e.g., using reception component 802, depicted in Fig. 8), from a network entity, a radio bearer configuration that indicates a value of the timer.
- the packet is for transmission on a downlink to a UE.
- the packet is associated with a TCP, an RTP, a UDP, Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- process 600 further includes detecting (e.g., using detection component 808), at the PDCP layer, expiry of an additional timer associated with an additional packet for transmission, and discarding (e.g., using queuing component 810) the additional packet based at least in part on detecting expiry of the additional timer, where the additional packet is associated with a TCP, an RTP, a UDP, Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- the packet is re-enqueued based at least in part on a tuple associated with the packet, a flow associated with the packet, a packet delay budget associated with the packet, or metadata associated with the packet.
- the packet is passed from the PDCP layer to software associated with a modem of the radio bearer, and the packet is re-enqueued by the software associated with the modem.
- the packet is passed from the PDCP layer to an application executed on one or more processors of the radio bearer, and the packet is re-enqueued by the application.
- the packet is re-enqueued by the PDCP layer.
- process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.
- Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a radio bearer, in accordance with the present disclosure.
- Example process 700 is an example where the radio bearer (e.g., UE 120 and/or apparatus 800 of Fig. 8, or network entity 401 and/or apparatus 900 of Fig. 9) performs operations associated with recovery after discarding a PDCP packet.
- process 700 may include detecting, at a PDCP layer, expiry of a timer associated with a packet for transmission (block 710).
- the radio bearer e.g., using detection component 808, depicted in Fig. 8 may detect expiry of the timer associated with the packet for transmission, as described above.
- the radio bearer is configured to discard the packet upon expiry of the timer.
- process 700 may include retransmitting the packet based at least in part on instructions from an application, executed on one or more processors of the radio bearer, that received the packet from the PDCP layer before the packet was discarded (block 720).
- the radio bearer e.g., using transmission component 804, depicted in Fig. 8
- Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
- a value of the timer is associated with a default radio bearer configuration or a dedicated radio bearer configuration.
- the packet is for transmission on an uplink to a network entity.
- process 700 further includes receiving (e.g., using reception component 802, depicted in Fig. 8), from a network entity, a radio bearer configuration that indicates a value of the timer.
- the packet is for transmission on a downlink to a UE.
- the packet is associated with a TCP, an RTP, a UDP, Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- process 700 further includes detecting (e.g., using detection component 808), at the PDCP layer, expiry of an additional timer associated with an additional packet for transmission, and discarding (e.g., using queuing component 810, depicted in Fig. 8) the additional packet based at least in part on detecting expiry of the additional timer, where the additional packet is associated with a TCP, an RTP, a UDP, Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- the packet is retransmitted based at least in part on a tuple associated with the packet, a flow associated with the packet, a packet delay budget associated with the packet, or metadata associated with the packet.
- the packet is duplicated, and the instructions to retransmit are generated based at least in part on the duplication.
- the PDCP layer is configured to retransmit after a threshold quantity of NACK signals, and the packet is retransmitted based at least in part on fewer NACK signals than the threshold quantity.
- process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.
- Fig. 8 is a block diagram of an example apparatus 800 for wireless communication.
- the apparatus 800 may be a radio bearer, such as a UE, or a radio bearer may include the apparatus 800.
- the apparatus 800 includes a reception component 802 and a transmission component 804, which may be in communication with one another (for example, via one or more buses and/or one or more other components).
- the apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using the reception component 802 and the transmission component 804.
- the apparatus 800 may include one or more of a detection component 808 or a queuing component 810, among other examples.
- the apparatus 800 may be configured to perform one or more operations described herein in connection with Fig. 5. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6, process 700 of Fig. 7, or a combination thereof.
- the apparatus 800 and/or one or more components shown in Fig. 8 may include one or more components of the UE described above in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 8 may be implemented within one or more components described above in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
- the reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 806.
- the reception component 802 may provide received communications to one or more other components of the apparatus 800.
- the reception component 802 may perform signal processing on the received communications (such as fdtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 800.
- the reception component 802 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection with Fig. 2.
- the transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 806.
- one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 806.
- the transmission component 804 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 806.
- the transmission component 804 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection with Fig. 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in a transceiver.
- the detection component 808 may detect, at a PDCP layer, expiry of a timer associated with a packet for transmission.
- the detection component 808 may include a MIMO detector, a receive processor, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection with Fig. 2.
- the PDCP layer may be configured to discard the packet upon expiry of the timer.
- the queuing component 810 may re -enqueue, based at least in part on the detection component 808 detecting expiry of the timer, the packet as a new packet for transmission before the PDCP layer discards the packet.
- the queuing component 810 may include a MIMO detector, a receive processor, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection with Fig. 2. Additionally, or alternatively, the transmission component 804 may retransmit the packet (e.g., to the apparatus 806) based at least in part on instructions from an application, executed on the apparatus 800, that received the packet from the PDCP layer before the packet was discarded. [0130] In some aspects, the reception component 802 may receive, from the apparatus 806, a radio bearer configuration that indicates a value of the timer.
- the detection component 808 may detect, at the PDCP layer, expiry of an additional timer associated with an additional packet for transmission. Accordingly, the queuing component 810 may discard the additional packet based at least in part on the detection component 808 detecting expiry of the additional timer, where the additional packet is associated with a TCP, an RTP, a UDP, Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- Fig. 8 The number and arrangement of components shown in Fig. 8 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 8. Furthermore, two or more components shown in Fig. 8 may be implemented within a single component, or a single component shown in Fig. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 8 may perform one or more functions described as being performed by another set of components shown in Fig. 8
- Fig. 9 is a block diagram of an example apparatus 900 for wireless communication.
- the apparatus 900 may be a radio bearer, such as a network entity, or a radio bearer may include the apparatus 900.
- the apparatus 900 includes a reception component 902 and a transmission component 904, which may be in communication with one another (for example, via one or more buses and/or one or more other components).
- the apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using the reception component 902 and the transmission component 904.
- the apparatus 900 may include a downlink management component 908, among other examples.
- the apparatus 900 may be configured to perform one or more operations described herein in connection with Fig. 5. Additionally, or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6, process 700 of Fig. 7, or a combination thereof.
- the apparatus 900 and/or one or more components shown in Fig. 9 may include one or more components of the base station described above in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 9 may be implemented within one or more components described above in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
- the reception component 902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 906.
- the reception component 902 may provide received communications to one or more other components of the apparatus 900.
- the reception component 902 may perform signal processing on the received communications (such as fdtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 900.
- the reception component 902 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with Fig. 2.
- the transmission component 904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 906.
- one or more other components of the apparatus 900 may generate communications and may provide the generated communications to the transmission component 904 for transmission to the apparatus 906.
- the transmission component 904 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 906.
- the transmission component 904 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with Fig. 2. In some aspects, the transmission component 904 may be co-located with the reception component 902 in a transceiver.
- the downlink management component 908 may detect, at a PDCP layer, expiry of a timer associated with a packet for transmission.
- the downlink management component 908 may include a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with Fig. 2.
- the PDCP layer may be configured to discard the packet upon expiry of the timer. Accordingly, the downlink management component 908 may re-enqueue, based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before discarding the packet.
- the transmission component 904 may retransmit the packet (e.g., to the apparatus 906) based at least in part on instructions from a data server, connected to the apparatus 900, that received the packet from the PDCP layer before the packet was discarded.
- the downlink management component 908 may detect, at the PDCP layer, expiry of an additional timer associated with an additional packet for transmission. Accordingly, the downlink management component 908 may discard the additional packet based at least in part on detecting expiry of the additional timer, where the additional packet is associated with a TCP, an RTP, a UDP, Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- Fig. 9 The number and arrangement of components shown in Fig. 9 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 9. Furthermore, two or more components shown in Fig. 9 may be implemented within a single component, or a single component shown in Fig. 9 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 9 may perform one or more functions described as being performed by another set of components shown in Fig. 9.
- a method of wireless communication performed by a radio bearer comprising: detecting, at a packet data convergence protocol (PDCP) layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer; and re-enqueuing, at a modem of the radio bearer or at an application layer of the radio bearer and based at least in part on detecting expiry of the timer, the packet as a new packet for transmission before discarding the packet.
- PDCP packet data convergence protocol
- Aspect 2 The method of Aspect 1, wherein a value of the timer is associated with a default radio bearer configuration or a dedicated radio bearer configuration.
- Aspect 3 The method of any of Aspects 1 through 2, wherein the packet is for transmission on an uplink to a network entity.
- Aspect 4 The method of Aspect 3, further comprising: receiving, from the network entity, a radio bearer configuration that indicates a value of the timer.
- Aspect 5 The method of any of Aspects 1 through 2, wherein the packet is for transmission on a downlink to a user equipment (UE).
- UE user equipment
- Aspect 6 The method of any of Aspects 1 through 5, wherein the packet is associated with a transmission control protocol (TCP), a real-time transport protocol (RTP), a user datagram protocol (UDP), Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- TCP transmission control protocol
- RTP real-time transport protocol
- UDP user datagram protocol
- Ethernet Ethernet
- Aspect 7 The method of any of Aspects 1 through 6, further comprising: detecting, at the PDCP layer, expiry of an additional timer associated with an additional packet for transmission; and discarding the additional packet based at least in part on detecting expiry of the additional timer, wherein the additional packet is associated with a transmission control protocol (TCP), a real-time transport protocol (RTP), a user datagram protocol (UDP), Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- TCP transmission control protocol
- RTP real-time transport protocol
- UDP user datagram protocol
- Ethernet unstructured data
- application-specific protocol data or a combination thereof.
- Aspect 8 The method of Aspect 7, wherein the application-specific protocol data includes extended reality (XR) data, virtual reality (VR) data, or a combination thereof.
- XR extended reality
- VR virtual reality
- Aspect 9 The method of any of Aspects 1 through 8, wherein the packet is re enqueued based at least in part on a tuple associated with the packet, a flow associated with the packet, a packet delay budget associated with the packet, or metadata associated with the packet.
- Aspect 10 The method of any of Aspects 1 through 9, wherein the packet is passed from the PDCP layer to software associated with a modem of the radio bearer, and the packet is re-enqueued by the software associated with the modem.
- Aspect 11 The method of any of Aspects 1 through 9, wherein the packet is passed from the PDCP layer to an application executed on one or more processors of the radio bearer, and the packet is re-enqueued by the application.
- Aspect 12 The method of any of Aspects 1 through 9, wherein the packet is re enqueued by the PDCP layer.
- a method of wireless communication performed by a radio bearer comprising: detecting, at a packet data convergence protocol (PDCP) layer, expiry of a timer associated with a packet for transmission, wherein the radio bearer is configured to discard the packet upon expiry of the timer; and retransmitting the packet based at least in part on instructions from an application, executed on one or more processors of the radio bearer, that received the packet from the PDCP layer before the packet was discarded.
- PDCP packet data convergence protocol
- Aspect 14 The method of Aspect 13, wherein a value of the timer is associated with a default radio bearer configuration or a dedicated radio bearer configuration.
- Aspect 15 The method of any of Aspects 13 through 14, wherein the packet is for transmission on an uplink to a network entity.
- Aspect 16 The method of Aspect 15, further comprising: receiving, from the network entity, a radio bearer configuration that indicates a value of the timer.
- Aspect 17 The method of any of Aspects 13 through 14, wherein the packet is for transmission on a downlink to a user equipment (UE).
- UE user equipment
- Aspect 18 The method of any of Aspects 13 through 17, wherein the packet is associated with a transmission control protocol (TCP), a real-time transport protocol (RTP), a user datagram protocol (UDP), Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- TCP transmission control protocol
- RTP real-time transport protocol
- UDP user datagram protocol
- Ethernet Ethernet
- unstructured data application-specific protocol data
- application-specific protocol data includes extended reality (XR) data, virtual reality (VR) data, or a combination thereof.
- XR extended reality
- VR virtual reality
- Aspect 20 The method of any of Aspects 13 through 19, further comprising: detecting, at the PDCP layer, expiry of an additional timer associated with an additional packet for transmission; and discarding the additional packet based at least in part on detecting expiry of the additional timer, wherein the additional packet is associated with a transmission control protocol (TCP), a real-time transport protocol (RTP), a user datagram protocol (UDP), Ethernet, unstructured data, application-specific protocol data, or a combination thereof.
- TCP transmission control protocol
- RTP real-time transport protocol
- UDP user datagram protocol
- Ethernet unstructured data
- application-specific protocol data or a combination thereof.
- Aspect 21 The method of any of Aspects 13 through 20, wherein the packet is retransmitted based at least in part on a tuple associated with the packet, a flow associated with the packet, a packet delay budget associated with the packet, or metadata associated with the packet.
- Aspect 22 The method of any of Aspects 13 through 21, wherein the packet is duplicated, and the instructions to retransmit are generated based at least in part on the duplication.
- Aspect 23 The method of any of Aspects 13 through 21, wherein the PDCP layer is configured to retransmit after a threshold quantity of negative-acknowledgement (NACK) signals, and the packet is retransmitted based at least in part on fewer NACK signals than the threshold quantity.
- NACK negative-acknowledgement
- Aspect 24 An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-12.
- Aspect 25 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more of Aspects 1-12.
- Aspect 26 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-12.
- Aspect 27 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-12.
- Aspect 28 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-12.
- Aspect 29 An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 13-23.
- Aspect 30 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more of Aspects 13-23.
- Aspect 31 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 13-23.
- Aspect 32 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 13-23.
- Aspect 33 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 13-23.
- the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and 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, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
- a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.
- satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
- “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).
- the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’).
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22716300.3A EP4302517A1 (en) | 2021-03-03 | 2022-03-02 | Recovery after packet data convergence protocol packet discard |
CN202280017573.8A CN116941279A (en) | 2021-03-03 | 2022-03-02 | Recovery after packet data convergence protocol packet discard |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202163156087P | 2021-03-03 | 2021-03-03 | |
US63/156,087 | 2021-03-03 | ||
US17/653,018 | 2022-03-01 | ||
US17/653,018 US20220286907A1 (en) | 2021-03-03 | 2022-03-01 | Recovery after packet data convergence protocol packet discard |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022187831A1 true WO2022187831A1 (en) | 2022-09-09 |
Family
ID=81307370
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2022/070923 WO2022187831A1 (en) | 2021-03-03 | 2022-03-02 | Recovery after packet data convergence protocol packet discard |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2022187831A1 (en) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060031527A1 (en) * | 2001-05-04 | 2006-02-09 | Microsoft Corporation | Expanded transmission control protocol, methods of operation and apparatus |
US20080144633A1 (en) * | 2006-12-18 | 2008-06-19 | Woloszynski Charles H | System for data transfer in a wireless network |
US20140328256A1 (en) * | 2013-05-02 | 2014-11-06 | Futurewei Technologies, Inc. | System and Method for Transmission Source Identification |
-
2022
- 2022-03-02 WO PCT/US2022/070923 patent/WO2022187831A1/en active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060031527A1 (en) * | 2001-05-04 | 2006-02-09 | Microsoft Corporation | Expanded transmission control protocol, methods of operation and apparatus |
US20080144633A1 (en) * | 2006-12-18 | 2008-06-19 | Woloszynski Charles H | System for data transfer in a wireless network |
US20140328256A1 (en) * | 2013-05-02 | 2014-11-06 | Futurewei Technologies, Inc. | System and Method for Transmission Source Identification |
Non-Patent Citations (3)
Title |
---|
3GPP TS 38.323 |
3GPP TS 38.331 |
XIAOFAN LI ET AL: "Throughput Analysis for a Multi-User, Multi-Channel ALOHA Cognitive Radio System", IEEE TRANSACTIONS ON WIRELESS COMMUNICATIONS, IEEE SERVICE CENTER, PISCATAWAY, NJ, US, vol. 11, no. 11, 1 November 2012 (2012-11-01), pages 3900 - 3909, XP011482443, ISSN: 1536-1276, DOI: 10.1109/TWC.2012.092112.111425 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230164085A1 (en) | Modifying modem timers based on jitter timing associated with an application | |
WO2023235130A1 (en) | Duplicating sidelink transmissions for sidelink carrier aggregation | |
US20230319630A1 (en) | Techniques for packet data convergence protocol and radio link control sequence number synchronization | |
US20220286907A1 (en) | Recovery after packet data convergence protocol packet discard | |
WO2022187831A1 (en) | Recovery after packet data convergence protocol packet discard | |
US11818731B2 (en) | Handling of a physical downlink shared channel overlapping with a semi-static symbol | |
US20230254072A1 (en) | Hybrid automatic repeat request acknowledgement codebook retransmission for multiple downlink control information based multiple transmit receive point | |
US20240048297A1 (en) | Hybrid automatic repeat request process space management for multi-cell scheduling | |
US20240163015A1 (en) | Message verification based hybrid automatic repeat request feedback | |
US20230079972A1 (en) | Packet data convergence protocol handling for secondary cell group deactivation | |
US20230141159A1 (en) | User equipment feedback on number of repetitions needed for decoding | |
US20240236983A9 (en) | Uplink transmissions in next available slots | |
US20240137933A1 (en) | Uplink transmissions in next available slots | |
US20240056124A1 (en) | Signaling for multiple transmission reception point activation and deactivation | |
US20230336293A1 (en) | Feedback communications for transport blocks with multiple code block groups | |
US20230308217A1 (en) | Hybrid automatic repeat request codebook transmission | |
WO2023102881A1 (en) | Uplink lossless transmission | |
US20240098733A1 (en) | Efficient scheduling of a two-hop communication link | |
US20240022957A1 (en) | Layer two processing procedures for protocol data unit sets with dependency | |
US20230246823A1 (en) | Lower layer security for groupcast communication | |
US20230318982A1 (en) | Application data unit architecture and signaling | |
US20230217289A1 (en) | Layer 3 measurement associated with dedicated polarization | |
US20230010190A1 (en) | Non-binary beam failure indicators | |
US20240073777A1 (en) | Mobile station relaying verification | |
WO2023097180A1 (en) | Modifying modem timers based on jitter timing associated with an application |
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: 22716300 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280017573.8 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022716300 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022716300 Country of ref document: EP Effective date: 20231004 |