Robust header compression with out of order delivery for multiple data packets

Abstract

Systems and techniques are provided for wireless communications. For example, a computing device can obtain configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven; receive a plurality of data packets associated with a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality of data packets are received out-of-order from the sequence; and perform out-of-order delivery (OOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.

Description

PATENTQualcomm Docket No 2502422WO1ROBUST HEADER COMPRESSION WITH OUT OF ORDER DELIVERY FOR MULTIPLE DATA PACKETSINTRODUCTION

[0001] Aspects of the present disclosure generally relate to wireless communication. In some implementations, examples are described for robust header compression (ROHC) with out of order delivery and / or multiple flows.

[0002] Wireless communications systems are deployed to provide various telecommunication services, including telephony, video, data, messaging, broadcasts, among others. Wireless communications systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G networks), a third-generation (3G) high speed data, Internet-capable wireless service, a fourth-generation (4G) service (e.g., Long-Term Evolution (LTE), WiMax), and a fifth-generation (5G) sendee (e.g., New Radio (NR)). There are presently many different types of wireless communications systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communication (GSM), etc.SUMMARY

[0003] The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

[0004] Disclosed are systems, methods, apparatuses, and computer-readable media for performing wireless communication. In some aspects, an apparatus for wirelessPATENTQualcomm Docket No 2502422WO2communication is provided. The apparatus includes: a processing system configured to: obtain configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven; receive a plurality of data packets associated with a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality of data packets are received out-of-order from the sequence; and perform out-of-order delivery (GOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.

[0005] In some aspects, a method of wireless communication is provided. The method includes: obtaining configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven; receiving a plurality of data packets associated with a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality of data packets are received out-of-order from the sequence; and performing out-of-order delivery (OOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.

[0006] In some aspects, a non-transitory computer-readable storage medium is provided including instructions stored thereon which, when executed by at least one processor, causes the at least one processor to: obtain configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven; receive a plurality of data packets associated withPATENTQualcomm Docket No 2502422WO3a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality of data packets are received out-of-order from the sequence; and perform out-of-order delivery (GOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.

[0007] In some aspects, an apparatus for wireless communication is provided. The apparatus includes: means for obtaining configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven; means for receiving a plurality of data packets associated with a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality of data packets are received out-of-order from the sequence; and means for performing out-of-order delivery (OOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.

[0008] In some aspects, an apparatus for wireless communication is provided. The apparatus includes: a processing system configured to: configure a plurality of contexts for a robust header compression (ROHC) bearer, wherein each context of the plurality of contexts is configured for a respective flow of a plurality of flows associated with realtime data packet traffic, and wherein a number of the plurality of contexts is less than or equal to a configured maximum number of contexts; determine an elapsed time from a last use of a respective context of the plurality of contexts exceeds a configured threshold amount of time; and evict the respective context from the ROHC bearer based on the elapsed time exceeding the configured threshold amount of time.

[0009] In some aspects, a method of wireless communication is provided. The method includes: configuring a plurality of contexts for a robust header compression (ROHC) bearer, wherein each context of the plurality of contexts is configured for a respective flow of a plurality of flows associated with real-time data packet traffic, and wherein a number of the plurality of contexts is less than or equal to a configured maximum number of contexts; determining an elapsed time from a last use of a respective context of thePATENTQualcomm Docket No 2502422WO4plurality of contexts exceeds a configured threshold amount of time; and evicting the respective context from the ROHC bearer based on the elapsed time exceeding the configured threshold amount of time.

[0010] In some aspects, a non-transitory computer-readable storage medium is provided including instructions stored thereon which, when executed by at least one processor, causes the at least one processor to: configure a plurality of contexts for a robust header compression (ROHC) bearer, wherein each context of the plurality of contexts is configured for a respective flow of a plurality of flows associated with realtime data packet traffic, and wherein a number of the plurality of contexts is less than or equal to a configured maximum number of contexts; determine an elapsed time from a last use of a respective context of the plurality of contexts exceeds a configured threshold amount of time; and evict the respective context from the ROHC bearer based on the elapsed time exceeding the configured threshold amount of time.

[0011] In some aspects, an apparatus for wireless communication is provided. The apparatus includes: means for configuring a plurality of contexts for a robust header compression (ROHC) bearer, wherein each context of the plurality of contexts is configured for a respective flow of a plurality of flows associated with real-time data packet traffic, and wherein a number of the plurality of contexts is less than or equal to a configured maximum number of contexts; means for determining an elapsed time from a last use of a respective context of the plurality of contexts exceeds a configured threshold amount of time; and means for evicting the respective context from the ROHC bearer based on the elapsed time exceeding the configured threshold amount of time.

[0012] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the drawings and specification. The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appendedPATENTQualcomm Docket No 2502422WO3claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

[0013] While 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. For example, some aspects may be implemented via integrated chip implementations 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. For example, 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). It is intended that 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.

[0014] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. This summary’ is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire specification of this patent, any or all drawings, and each claim. The foregoing, together with other features and aspects, will become more apparent upon referring to the following specification, claims, and accompanying drawings.PATENTQualcomm Docket No 2502422WO6BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof. So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

[0016] FIG. 1 is a block diagram illustrating an example of a wireless communication network, in accordance with some examples;

[0017] FIG. 2 is a diagram illustrating a design of a base station and a User Equipment (UE) device that enable transmission and processing of signals exchanged between the UE and the base station, in accordance with some examples;

[0018] FIG. 3 is a diagram illustrating an example of a disaggregated base station, in accordance with some examples;

[0019] FIG. 4 is a block diagram illustrating components of a user equipment (UE), in accordance with some examples;

[0020] FIG. 5 is a diagram illustrating an example of physical channels and reference signals in a wireless network, in accordance with some examples;

[0021] FIG. 6 is a diagram illustrating an example of a 5G NR protocol stack, in accordance with some examples;

[0022] FIG. 7 illustrates an example of a data packet including one or more headers and a payload transmitted within a wireless network, in accordance with some examples;

[0023] FIG. 8 is an example of a Packet Data Convergence Protocol (PDCP) control Protocol Data Unit (PDU) including a flow control (FC) indication indicative of a request to stop Robust Header Compression (ROHC) decompression, in accordance with some examples;PATENTQualcomm Docket No 2502422WO7

[0024] FIG. 9 is a flow diagram illustrating an example of a process for wireless communication, in accordance with some examples; and

[0025] FIG. 10 is a block diagram illustrating an example of a computing system, in accordance with some examples.DETAILED DESCRIPTION

[0026] Certain aspects of this disclosure are provided below for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure. Some of the aspects described herein may be applied independently and some of them may be applied in combination as would be apparent to those of skill in the art. In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of aspects of the application. However, it will be apparent that various aspects may be practiced without these specific details. The figures and description are not intended to be restrictive.

[0027] The ensuing description provides example aspects only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the example aspects will provide those skilled in the art with an enabling description for implementing an example aspect. It should be understood that various changes may be made in the function and arrangement of elements without departing from the scope of the application as set forth in the appended claims.

[0028] Wireless communication networks can be deployed to provide various communication services, such as voice, video, packet data, messaging, broadcast, any combination thereof, or other communication services. A wireless communication network may support both access links and sidelinks for communication between wireless devices. An access link may refer to any communication link between a client device (e.g., a user equipment (UE), a station (STA), or other client device) and a base station (e.g.. a 3GPP gNB for 5G / NR, a 3GPP eNB for 4G / LTE. a Wi-Fi access point (AP), or other base station). For example, an access link may support uplink signaling, downlink signaling, connection procedures, etc. An example of an access link is a Uu link or interface (also referred to as an NR-Uu) between a 3 GPP gNB and a UE.PATENTQualcomm Docket No 2502422WO8

[0029] In various wireless communication networks (e.g., 4G / LTE, 5G / NR, 6G, and beyond), header compression can be performed for data packets prior to transmission to a destination unit. For example, prior to transmission from a source unit to a destination unit, the header information stored within data packets may be compressed, at the source unit, using various compression and encoding mechanisms. At the destination, the header information is decompressed and is attached to its corresponding payload to re-form the original data packet. In some cases, Robust Header Compression (ROHC) can be used to compress the respective headers of different protocol stack packet transmissions, with the ROHC-based header compression performed according to one of a configured plurality of compression profiles selected based on the protocol stack and / or header ty pe being compressed.

[0030] For example, ROHC includes different respective profiles (e.g., also referred to as ROHC profiles, compression profiles, and / or ROHC compression profiles, etc.) to indicate how the header compression is to be performed for respective protocol stacks such as Real-Time Transfer Protocol (RTP), which is a protocol that supports real time transmission of voice and video packets, on top of a User Datagram Protocol (UDP) / Intemet Protocol (IP). In some examples. ROHC may be used to increase efficiency and / or to reduce packet transmission overhead over constrained links by compressing repetitive and predictable IP / UDP / RTP / etc. headers into minimal-size encodings. For example, the ROHC standard codified as RFC 3095 by the Internet Engineering Task Force (IETF) defines different profiles for header compression. Each ROHC compression profile can be used for a corresponding network protocol stack, can be associated with a unique 16-bit profile identifier, and can be indicative of a definition for the compression of headers of a particular protocol combination.

[0031] For example, ROHC compression profile 0x0001 can be used for compression of headers for RTP / UDP / IP. The ROHC compression profile 0x0002 can be used for header compression associated with UDP / IP. The ROHC compression profile 0x0003 can be used for header compression associated with Encapsulating Security Payload (ESP) / IP. The ROHC compression profile 0x0004 can be used for compression of IP-only headers (e.g., no upper layer). In some examples, profile 0x0000 is an uncompressed profile where ROHC and / or header compression are not implemented and packets are transmitted without performing header compression. Various other ROHC compression profiles andPATENTQualcomm Docket No 2502422WO9profile IDs (e.g., 0x0007, 0x0008, etc.) can be reserved or unassigned, and may be used for header compression outside of or in addition to that codified by the ROHC standards. In some cases, the ROHC profiles 0x0007 and 0x0008 can be used for compression of UDP-Lite headers.

[0032] Transmission of data packets can experience packet loss and / or reordering for at least a portion of the total number of data packets that are transmitted from a source unit. Reordering can refer to a type of transmission taking place between compressor and decompressor where in-order delivery of header-compressed packets is not guaranteed. For example, during transmission and / or reception within the wireless communication system, and prior to arrival at the source unit, certain data packets may be lost and / or misplaced within the network Misplaced data packets may eventually reenter the data stream at a later time, but the header field information of the re-entering data packets is inconsistent with the rest of the data packets in the stream at the later time.

[0033] Out of order (OOO) delivery (GOOD) can refer to packet transmissions betw een a source and destination with one or more packets experience reordering. For example, OOOD can occur for one or more packets transmitted over a reordering channel, which refers to a connection over which reordering may occur. In some cases, OOOD can correspond to one or more sequentially early packets, which are packets that reach the decompressor (e.g., destination unit) before one or several packets of the same context identifier (CID) that were delayed on the link. At the time of the arrival of a sequentially early packet, the packet(s) delayed on the link cannot be differentiated from lost packet(s) and decompression failure can occur due to the reordering. In some examples. OOOD can correspond to one or more sequentially late packets, which are packets that are late within their corresponding sequence based on reaching the decompressor (e.g., destination unit) after one or several other packets belonging to the same CID have been received, although the sequentially late packet was sent from the compressor before the other packet(s).

[0034] ROHC was designed with an assumption that data packets will be delivered in order from compressor (e.g., source unit) to decompressor (e g., destination unit), for example with no reordering of data packets and / or with minimal reordering of the data packets. For example, ROHC as codified in RFC 3095 assumes in-order delivery is guaranteed for packets transmitted from compressor to decompressor, and OOOD is not permitted if ROHC is configured for data packet transmission. Many real-world networksPATENTQualcomm Docket No 2502422WO10do reorder packets, including IP core networks with equal cost multipath (ECMP) routing and / or load balancing configured, tunneling and / or virtual private network (VPN) networks, mesh networks, wireless networks where physical (PHY) layer block error rate (BLER) causes retransmission(s) of one or more packets that results in late arrival(s), etc. When reordering occurs for a sequence of transmitted data packets with ROHC header compression applied to the packet headers, ROHC decompression may fail at the destination unit. For example, ROHC decompression may use window-least significant bits (W-LSB) encoding, which uses a monotonically increasing reference value (e.g., an RTP sequence number (SN)) for decoding compressed header fields. GOOD of ROHC compressed data packets can cause decompression to fail, based on the out-of-order packets deviating from the expected monotonic increase in the SN reference value used at the decompressor.

[0035] Systems and techniques that can be used to implement GOOD for data packets transmitted using ROHC header compression may be beneficial. For example, real-time traffic such as voice data packets and / or extended reality (XR) data packets may benefit from Packet Data Convergence Protocol (PDCP) OOOD to achieve reduced latency and / or reduced underflow based on performing reordering of out-of-order ROHC compressed packets that are received within a reordering timer interval and before a play out time of the OOOD ROHC compressed packet. Systems and techniques that can be used to implement ROHC for header compression of data packets included in multiple flow traffic and / or transmitted on multiple ROHC bearers may also be beneficial. For example, XR and other types of data traffic may be associated with multiple flows between a source and destination, and ROHC may be limited by a maximum threshold number of contexts per ROHC bearer that is indicated by the PDCP specification. It may be desirable for systems and techniques that can be used to implement ROHC for a data packet flow having a number of contexts that is greater than the threshold number of contexts corresponding to PDCP.

[0036] Systems, apparatuses, processes (also referred to as methods), and computer-readable media (collectively referred to as “systems and techniques”) are described herein that can be used to provide OOOD and / or packet reordering for real-time data traffic of a plurality of data packets transmitted using ROHC header compression. For example, the systems and techniques can be used to increase a maximum packet reordering interval forPATENTQualcomm Docket No 2502422WO11performing reordering of late-arriving and / or other OOOD packets received by an ROHC decompressor. In some examples, the packets may be voice data packets included in realtime voice traffic which may comprise one or multiple respective flows on an ROHC bearer. In some cases, the packets may be XR data packets included in real-time XR traffic which may comprise one or multiple respective flows on an ROHC bearer. In some cases, the systems and techniques can be used for increasing the maximum OOOD reordering threshold for ROHC OOOD delivery of voice and / or XR and / or various other real-time data packets, based on using compression profiles configured with increased values of an interpretation window offset used for least significant bit (LSB) encoding performed by an ROHC decompressor. The increased value(s) of the offset parameter can be configured using one or more ROHC compression profiles, and / or can be signaled to the ROHC decompressor by a network entity (e.g., base station, gNB, etc.

[0037] In some cases, the systems and techniques can be used for ROHC packet header compression for voice and / or XR and / or real-time data traffic comprising multiple flows. For example, the multiple flows may be multiple uplink flows from a UE to a network entity (e.g.. base station, gNB, etc.). In some examples, the systems and techniques can provide multiple flow implementations for ROHC based on context eviction for bearers with a number of contexts greater than or equal to a configured maximum number of contexts per bearer. The context eviction can be performed based on an elapsed time since each respective active context on an ROHC bearer was last used, with an active context evicted from the bearer in response to the elapsed time from last use exceeding the configured threshold time for eviction. In some cases, the systems and techniques can provide per-flow configuration for ROHC, based on UE capability information signaled from a UE to a network entity' to indicate a selection of one or more flows (e.g., of a plurality of flows associated with the UE and / or a particular bearer) to be used for ROHC compression. In some examples, the systems and techniques can implement flow control for real-time data traffic comprising multiple flows (e.g., real-time voice and / or XR data traffic, etc.), where the flow control is based on signaling from the UE to the network to indicate a request by the UE to stop compression.

[0038] Further aspects of the systems and techniques will be described with respect to the figures.

[0039] As used herein, the phrase “based on” shall not be construed as a reference to aPATENTQualcomm Docket No 2502422WO12closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase "based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

[0040] As used herein, the terms “user equipment” (UE) and “network entity” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, and / or tracking device, etc.), wearable (e.g., smartwatch, smart-glasses, wearable ring, and / or an extended reality (XR) device such as a virtual reality (VR) headset, an augmented reality (AR) headset or glasses, or a mixed reality (MR) headset), vehicle (e.g., automobile, motorcycle, bicycle, etc.), aircraft (e.g., an airplane, jet, unmanned aerial vehicle (UAV) or drone, helicopter, airship, glider, etc ), and / or Internet of Things (loT) device, etc., used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core netw ork via a RAN, and through the core netw ork the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standards, etc.), and so on.

[0041] A network entity can be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or aNon-Real Time (Non-RT) RIC. Abase station (e.g., with an aggregated / monolithic base station architecture or disaggregated base station architecture) may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB (NB), anPATENTQualcomm Docket No 2502422WO13evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for the supported UEs. In some systems, a base station may provide edge node signaling functions while in other systems it may provide additional control and / or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, or a forw ard traffic channel, etc.). The term traffic channel (TCH), as used herein, can refer to either an uplink, reverse or downlink, and / or a forward traffic channel.

[0042] The term ‘'network entity’’ or '‘base station” (e.g., with an aggregated / monolithic base station architecture or disaggregated base station architecture) may refer to a single physical transmit receive point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term “network entity” or “base station” refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term “network entity” or “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (e.g., a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (e.g.. a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals (e.g., or simply “reference signals”) the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station.PATENTQualcomm Docket No 2502422WO14

[0043] In some implementations that support positioning of UEs, a network entity7or base station may not support wireless access by UEs (e.g., may not support data, voice, and / or signaling connections for UEs). but may instead transmit reference signals to UEs to be measured by the UEs, and / or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and / or as a location measurement unit (e.g., when receiving and measuring signals from UEs).

[0044] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, a processing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote unit (RU), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity7. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, processing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, processing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receivePATENTQualcomm Docket No 2502422WO15information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first processing system, a first one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second processing system, a second one or more components, a second processing entity, or the like.

[0045] As described herein, a network entity (which may alternatively be referred to as an entity, a node, a network node, or a wireless entity) may be, be similar to, include, or be included in (e.g., be a component of) a base station (e.g., any base station described herein, including a disaggregated base station), a UE (e.g., any UE described herein), a reduced capability (RedCap) device, an enhanced reduced capability (eRedCap) device, an ambient intemet-of-things (loT) device, an energy harvesting (EH)-capable device, a network controller, an apparatus, a device, a computing system, a processing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU). a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network entity may be a UE. As another example, a network entity may be a base station. As used herein, “network entity” may refer to an entity that is configured to operate in a network, such as the wireless communications system 100 of FIG. 1. For example, a “network entity” is not limited to an entity’ that is currently located in and / or currently operating in the network. Rather, a network entity may be any entity that is capable of communicating and / or operating in the network.

[0046] The adjectives “first,” “second,” “third,” and so on are used for contextual distinction between two or more of the modified noun in connection with a discussion and are not meant to be absolute modifiers that apply only to a certain respective entity throughout the entire document. For example, a network entity' may be referred to as a “first network entity” in connection with one discussion and may be referred to as a “second network entity” in connection with another discussion, or vice versa. As an example, a first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entityPATENTQualcomm Docket No 2502422WO16may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different relative to these examples.

[0047] Similarly, reference to a UE, base station, network node, apparatus, device, computing system, processing system or the like may include disclosure of the UE, base station, network node, apparatus, device, computing system, processing system or the like being a network entity. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE. a first base station, a first apparatus, a first device, a first computing system, a first processing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network entity may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second processing system, a second set of one or more components, a second processing entity7, or the like.

[0048] As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network entity may be described as being configured to transmit information to a second network entity'. In this example and consistent with this disclosure, disclosure that the first network entity is configured to transmit information to the second network entity includes disclosure that the first network entity is configured to provide, send, output, communicate, or transmit information to the second network entity’. Similarly, in this example and consistent with this disclosure, disclosure that thePATENTQualcomm Docket No 2502422WO17first network entity is configured to transmit information to the second network entity7includes disclosure that the second network entity is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network entity.

[0049] In some examples, the base station 102 may include a processing system (e.g., such as the processing system 470 of FIG. 4 and / or the processing system 1002 of FIG.10, etc.). Similarly, the base station 180 (e.g., a millimeter wave (mmW) base station, network entity, etc.) may include a respective processing system (e.g.. such as the processing system 470 of FIG. 4 and / or the processing system 1002 of FIG. 10, etc.). A processing system may include one or more components (or subcomponents), such as one or more components described herein. For example, a respective component of the one or more components may be. be similar to, include, or be included in at least one memory, at least one communication interface, or at least one processor. For example, a processing system may include one or more components. In such an example, the one or more components may include a first component, a second component, and a third component. In this example, the first component may be coupled to a second component and a third component. In this example, the first component may be at least one processor, the second component may be a communication interface, and the third component may be at least one memory. A processing system may generally be a system including one or more components that may perform one or more functions, such as any function or combination of functions described herein. For example, one or more components may receive input information (e.g., any information that is an input, such as a signal, any digital information, or any other information), one or more components may process the input information to generate output information (e.g., any information that is an output, such as a signal or any other information), one or more components may perform any function as described herein, or any combination thereof. As described herein, an ‘'input7’ and “input information” may be used interchangeably. Similarly, as described herein, an “output” and “output information” may be used interchangeably. Any information generated by any component may be provided to one or more other systems or components of, for example, a network entity described herein). For example, a processing system may include a first component configured to receive or obtain information, a second component configured to process the information to generate output information, and / or a third component configured to provide the outputPATENTQualcomm Docket No 2502422WO18information to other systems or components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., that is coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e g., the first communication interface or a second communication interface). For example, a processing system may include at least one memory, at least one communication interface, and / or at least one processor, where the at least one processor may, for example, be coupled to the at least one memory and the at least one communication interface.

[0050] A processing system of a network entity described herein may interface with one or more other components of the network entity7, may process information received from one or more other components (such as input information), or may output information to one or more other components. For example, a processing system may include a first component configured to interface with one or more other components of the network entity to receive or obtain information, a second component configured to process the information to generate one or more outputs, and / or a third component configured to output the one or more outputs to one or more other components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., that is coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., the first communication interface or a second communication interface). For example, a chip or modem of the network entity may include a processing system. The processing system may include a first communication interface to receive or obtain information, and a second communication interface to output, transmit, or provide information. In some examples, the first communication interface may be an interface configured to receive input information, and the information may be provided to the processing system. In some examples, the second system interface may be configured to transmit information output from the chip or modem. The second communication interface may also obtain or receive input information, and the first communication interface may also output, transmit, or provide information.

[0051] An RF signal comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As usedPATENTQualcomm Docket No 2502422WO19herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.

[0052] Various aspects of the systems and techniques described herein will be discussed below with respect to the figures. According to various aspects, FIG. 1 illustrates an example of a wireless communications system 100. The wireless communications system 100 (e.g., which may also be referred to as a wireless wide area network (WWAN)) can include various base stations 102 and various UEs 104. In some aspects, the base stations 102 may also be referred to as “network entities” or “network nodes.” One or more of the base stations 102 can be implemented in an aggregated or monolithic base station architecture. Additionally, or alternatively, one or more of the base stations 102 can be implemented in a disaggregated base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU). a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC. The base stations 102 can include macro cell base stations (e.g., high power cellular base stations) and / or small cell base stations (e.g., low power cellular base stations). In an aspect, the macro cell base station may include eNBs and / or ng-eNBs where the wireless communications system 100 corresponds to a long-term evolution (LTE) network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0053] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., which may be part of core network 170 or may be external to core network 170). In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dualPATENTQualcomm Docket No 2502422WO20connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS). subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC or 5GC) over backhaul links 134, which may be wired and / or wireless.

[0054] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by abase station 102 in each geographic coverage area 110. A “cell’' is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI), a cell global identifier (CGI)) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband loT (NB-IoT). enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” may be used interchangeably. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.

[0055] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell base station 102' may have a geographic coverage area 110' that substantially overlaps with the geographic coverage area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also includePATENTQualcomm Docket No 2502422WO21home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

[0056] The communication links 120 between the base stations 102 and the UEs 104 may include uplink (e.g., also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (e.g., also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 may be provided using one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., a greater or lesser quantity of carriers may be allocated for downlink than for uplink).

[0057] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., one or more of the base stations 102, UEs 104, etc.) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be implemented based on combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by abeamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0058] A transmitting device and / or a receiving device (e.g., such as one or more of base stations 102 and / or UEs 104) may use beam sweeping techniques as part of beam forming operations. For example, a base station 102 (e.g., or other transmitting device) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 104 (e.g., or other receiving device). Some signals (e.g., synchronization signals, reference signals, beamPATENTQualcomm Docket No 2502422WO22selection signals, or other control signals) may be transmitted by base station 102 (or other transmitting device) multiple times in different directions. For example, the base station 102 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by a transmitting device, such as a base station 102, or by a receiving device, such as a UE 104) a beam direction for later transmission or reception by the base station 102.

[0059] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a base station 102 in a single beam direction (e.g., a direction associated with the receiving device, such as a UE 104). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted in one or more beam directions. For example, a UE 104 may receive one or more of the signals transmitted by the base station 102 in different directions and may report to the base station 102 an indication of the signal that the UE 104 received with a highest signal quality or an otherwise acceptable signal quality.

[0060] In some examples, transmissions by a device (e.g., by a base station 102 or a UE 104) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from a base station 102 to a UE 104, from a transmitting device to a receiving device, etc.). The UE 104 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across a system bandwidth or one or more sub-bands. The base station 102 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), etc.), which may be precoded or unprecoded. The UE 104 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multipanel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted in one or more directions by a base station 102, a UE 104 may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 104) or for transmitting a signal in a single direction (e.g., for transmitting data to a receiving device).PATENTQualcomm Docket No 2502422WO23

[0061] A receiving device (e.g., a UE 104) may try' multiple receive configurations (e.g., directional listening) when receiving various signals from the base station 102, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as ‘listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0062] The wireless communications system 100 may further include a WLAN AP 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 Gigahertz (GHz)). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available. In some examples, the wireless communications system 100 can include devices (e.g., UEs, etc.) that communicate with one or more UEs 104, base stations 102, APs 150, etc., utilizing the ultra-wideband (UWB) spectrum. The UWB spectrum can range from 3.1 to 10.5 GHz.

[0063] The small cell base station 102' may operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE and / or 5G in an unlicensed frequency spectrum, may boost coverage to and / or increase capacity of the access network. NR in unlicensed spectrum may bePATENTQualcomm Docket No 2502422WO24referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0064] The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and / or near mmW frequencies in communication with a UE 182. The mmW base station 180 may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture (e.g., including one or more of a CU, a DU, a RU, a Near-RT RIC, or a Non-RT RIC). Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW and / or near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (e.g., transmit and / or receive) over an mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[0065] In some aspects relating to 5G, the frequency spectrum in which wireless network nodes or entities (e g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges, FR1 (e.g., from 450 to 6,000 Megahertz (MHz)), FR2 (e.g., from 24,250 to 52,600 MHz), FR3 (e.g., above 52,600 MHz), and FR4 (e.g., between FR1 and FR2). In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier" or “anchor carrier’’ or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as "secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE 104 / 182 and the cell in which the UE 104 / 182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-PATENTQualcomm Docket No 2502422WO25establishment procedure. The primary carrier carries all common and UE-specific control channels and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary' carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary’ signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell may have different downlink primary' carriers. The same is true for the uplink primary' carriers. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a "serving cell” (e.g., whether a PCell or an SCell) corresponds to a carrier frequency and / or component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably.

[0066] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and / or the mmW base station 180 may be secondary' carriers (“SCells”). In carrier aggregation, the base stations 102 and / or the UEs 104 may use spectrum up to Y MHz (e.g., 5. 10. 15, 20, 100 MHz) bandwidth per carrier up to a total of Yx MHz (e.g., x component carriers) for transmission in each direction. The component carriers may or may' not be adjacent to each other on the frequency' spectrum. Allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., a greater or lesser quantity of carriers may be allocated for downlink than for uplink). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically' lead to a two-fold increase in data rate (e.g., 40 MHz), compared to that attained by a single 20 MHz carrier.

[0067] In order to operate on multiple carrier frequencies, a base station 102 and / or a UE 104 can be equipped with multiple receivers and / or transmitters. For example, a UEPATENTQualcomm Docket No 2502422WO26104 may have two receivers, ‘‘Receiver 1” and “Receiver 2,” where “Receiver 1” is a multi-band receiver that can be tuned to band (e.g., carrier frequency) ‘X’ or band ‘Y and “Receiver 2” is a one-band receiver tunable to band ‘Z’ only. In this example, if the UE 104 is being served in band ‘X,’ band ‘X’ would be referred to as the PCell or the active carrier frequency, and “Receiver 1” would need to tune from band ‘X’ to band ‘Y’ (e.g., an SCell) in order to measure band ‘Y’ (and vice versa). In contrast, whether the UE 104 is being served in band ‘X’ or band Y,' because of the separate “Receiver 2,” the UE 104 can measure band Z’ without interrupting the service on band ‘X’ or band ‘Y’

[0068] The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and / or the mmW base station 180 over an mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164.

[0069] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (e.g., referred to as “sidelinks”). In the example of FIG. 1. UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (e.g., through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D). Wi-Fi Direct (Wi-Fi-D). Bluetooth®, and so on.

[0070] FIG. 2 illustrates a block diagram of an example architecture 200 of a base station 102 and a UE 104 that enables transmission and processing of signals exchanged between the UE and the base station, in accordance with some aspects of the present disclosure. Example architecture 200 includes components of a base station 102 and a UE 104, which may be one of the base stations 102 and one of the UEs 104 illustrated in FIG. 1. Base station 102 may be equipped with T antennas 234a through 234t, and UE 104 may be equipped with R antennas 252a through 252r, where in general T>1 and R>1.PATENTQualcomm Docket No 2502422WO27

[0071] At base station 102, a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based on channel quality indicators (CQIs) received from the UE. process (e g., encode and modulate) the data for each UE based on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi -static resource partitioning information (SRPI) and / or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and / or the like) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS)) and synchronization signals (e.g., the primary synchronization signal (PSS) and 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 T output symbol streams to T modulators (MODs) 232a through 232t. The modulators 232a through 232t are shown as a combined modulator-demodulator (MOD-DEMOD). In some cases, the modulators and demodulators can be separate components. Each modulator of the modulators 232a to 232t may process a respective output symbol stream (e.g., for an orthogonal frequency-division multiplexing (OFDM) scheme and / or the like) to obtain an output sample stream. Each modulator of the modulators 232a to 232t may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals may be transmitted from modulators 232a to 232t via T antennas 234a through 234t, respectively. According to certain aspects described in more detail below, the synchronization signals can be generated with location encoding to convey additional information.

[0072] At UE 104, antennas 252a through 252r may receive the downlink signals from base station 102 and / or other base stations and may provide received signals to one or more demodulators (DEMODs) 254a through 254r, respectively. The demodulators 254a through 254r are shown as a combined modulator-demodulator (MOD-DEMOD). In some cases, the modulators and demodulators can be separate components. Each demodulator of the demodulators 254a through 254r may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator of the demodulators 254a through 254r may further process the input samples (e.g., forPATENTQualcomm Docket No 2502422WO28OFDM and / or the like) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 104 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. A channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), and / or the like.

[0073] On the uplink, at UE 104, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RS SI, RSRQ, CQI, and / or the like) from controller / processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals (e g., based on a beta value or a set of beta values associated with the one or more reference signals). The symbols from transmit processor 264 may be precoded by a TX-MIMO processor 266, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, and / or the like), and transmitted to base station 102. At base station 102, the uplink signals from UE 104 and other UEs may be received by antennas 234a through 234t, processed by demodulators 232a through 232t, detected by a MIMO detector 236 (e.g., if applicable), and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 104. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller (e.g., processor) 240. Base station 102 may include communication unit 244 and communicate to a network controller 231 via communication unit 244. Network controller 231 may include communication unit 294, controller / processor 290, and memory 292.

[0074] In some aspects, one or more components of UE 104 may be included in a housing. Controller 240 of base station 102. controller / processor 280 of UE 104, and / or any other component(s) of FIG. 2 may perform one or more techniques associated with implicit Uplink Control Information (UCI) beta value determination for NR.

[0075] Memories 242 and 282 may store data and program codes for the base station 102 and the UE 104, respectively. A scheduler 246 may schedule UEs for data transmission on the downlink, uplink, and / or sidelink.PATENTQualcomm Docket No 2502422WO29

[0076] In some aspects, deployment of communication systems, such as 5G new radio (NR) systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (e.g., such as a Node B (NB), evolved NB (eNB), NRBS, 5GNB, access point (AP), a transmit receive point (TRP), or a cell, etc.) may be implemented as an aggregated base station (e.g., also known as a standalone BS or a monolithic BS) or a disaggregated base station.

[0077] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be colocated 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 can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU). or a virtual radio unit (VRU).

[0078] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (e.g., such as the netw ork configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (e.g., vRAN. also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, w hich can enable flexibility7in netw ork design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.PATENTQualcomm Docket No 2502422WO30

[0079] FIG. 3 is a diagram illustrating an example disaggregated base station 300 architecture. The disaggregated base station 300 architecture may include one or more central units (CUs) 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units (e.g., such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 325 via an E2 link, or a Non-Real Time (Non-RT) RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an Fl interface. The DUs 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RUs 340 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 340.

[0080] Each of the units (e.g., the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305) illustrated in FIG. 3 and / or described herein may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (e.g., collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (e.g., such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0081] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU-UP)), control plane functionality (e.g., Central Unit - Control Plane (CU-CP)), or a combination thereof. InPATENTQualcomm Docket No 2502422WO31some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with the DU 330, as necessary, for network control and signaling.

[0082] The DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending on a functional split, such as those defined by the 3rd Generation Partnership Proj ect (3GPP). In some aspects, the DU 330 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

[0083] Lower-layer functionality can be implemented by one or more RUs 340. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions, or low- PHY layer functions (e.g., such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical randomaccess channel (PRACH) extraction and filtering, or the like), or both, based on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 340 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable the DU(s) 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0084] The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (e.g., such as an 01 interface). For virtualized network elements, the SMO Framework 305 may be configured to interactPATENTQualcomm Docket No 2502422WO32with a cloud computing platform (e.g., such as an open cloud (O-Cloud) 390) to perform network element life cycle management (e.g.. such as to instantiate virtualized network elements) via a cloud computing platform interface (e.g., such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with one or more RUs 340 via an 01 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

[0085] The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (e.g., such as via an Al interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (e g., such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

[0086] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from nonnetwork data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 305 (e.g., such as reconfiguration via 01) or via creation of RAN management policies (e.g., such as Al policies).

[0087] FIG. 4 illustrates an example of a processing system 470 of a wireless device 407. In some examples, the processing system 470 may also be referred to as a computingPATENTQualcomm Docket No 2502422WO33system. The processing system 470 may include and / or implement one or more components that are the same as or similar to respective components included in and / or implemented by the processing system 1002 of FIG. 10 (e.g.. and the processing system 1002 of FIG. 10 may include and / or implement one or more components that are the same as or similar to respective components included in and / or implemented by the processing system 470 of FIG. 4). In some cases, the wireless device 407 may also be referred to as a user computing device. The wireless device 407 may include a client device such as a UE (e.g., UE 104, UE 152, UE 190) or other type of device (e.g., a station (STA) configured to communication using a Wi-Fi interface) that may be used by an end-user. In some cases, the processing system 470 of the wireless device 407 can be implemented by one or more of the UEs 104 of FIG. 1. For example, the wireless device 407 may include a mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., a smart watch, glasses, an extended reality (XR) device such as a virtual reality (VR), augmented reality (AR), or mixed reality (MR) device, etc.), Internet of Things (loT) device, a vehicle, an aircraft, and / or another device that is configured to communicate over a wireless communications network.

[0088] The processing system 470 includes software and hardware components that may be electrically or communicatively coupled via a bus 489 (e g., or may otherwise be in communication, as appropriate). The processing system 470 may generally be a system including one or more components that may perform one or more functions, such as any function or combination of functions described herein. For example, one or more components may receive input information (e.g., any information that is an input, such as a signal, any digital information, or any other information), one or more components may process the input information to generate output information (e.g., any information that is an output, such as a signal or any other information), one or more components may perform any function as described herein, or any combination thereof. For example, the processing system 470 includes one or more processors 484. The one or more processors 484 may include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, dedicated hardware, any combination thereof, and / or other processing device or system. The bus 489 may be used by the one or more processors 484 to communicate between cores and / or with the one or more memory devices 486.PATENTQualcomm Docket No 2502422WO34

[0089] The processing system 470 may also include one or more memory devices 486, one or more digital signal processors (DSPs) 482, one or more SIMs 474, one or more modems 476, one or more wireless transceivers 478, an antenna 487, one or more input devices 472 (e.g., a camera, a mouse, a keyboard, a touch sensitive screen, a touch pad, a keypad, a microphone, and / or the like), and one or more output devices 480 (e.g., a display, a speaker, a printer, and / or the like).

[0090] In some aspects, processing system 470 may include one or more radio frequency (RF) interfaces configured to transmit and / or receive RF signals. In some examples, an RF interface may include components such as modem(s) 476, wireless transceiver(s) 478, and / or antennas 487. The one or more wireless transceivers 478 may transmit and receive wireless signals (e.g., signal 488) via antenna 487 from one or more other devices, such as other wireless devices, network devices (e.g.. base stations such as eNBs and / or gNBs, Wi-Fi access points (APs) such as routers, range extenders or the like, etc.), cloud networks, and / or the like. In some examples, the processing system 470 may' include multiple antennas or an antenna array that may facilitate simultaneous transmit and receive functionality. Antenna 487 may be an omnidirectional antenna such that radio frequency (RF) signals may’ be received from and transmitted in all directions. The wireless signal 488 may be transmitted via a wireless network. The wireless network may be any wireless network, such as a cellular or telecommunications network (e.g., 3G, 4G, 5G, etc.), wireless local area network (e.g., a Wi-Fi network), a Bluetooth™ network, and / or other network.

[0091] In some examples, the wireless signal 488 may be transmitted directly to other wireless devices using sidelink communications (e.g., using a PC5 interface, using a DSRC interface, etc.). Wireless transceivers 478 may be configured to transmit RF signals for performing sidelink communications via antenna 487 in accordance with one or more transmit power parameters that may be associated with one or more regulation modes. Wireless transceivers 478 may also be configured to receive sidelink communication signals having different signal parameters from other wireless devices.

[0092] In some examples, the one or more w ireless transceivers 478 may include an RF front end including one or more components, such as an amplifier, a mixer (e.g., also referred to as a signal multiplier) for signal down conversion, a frequency synthesizer (e.g., also referred to as an oscillator) that provides signals to the mixer, a baseband filter.PATENTQualcomm Docket No 2502422WO35an analog-to-digital converter (ADC), one or more power amplifiers, among other components. The RF front-end may generally handle selection and conversion of the wireless signals 488 into a baseband or intermediate frequency and may convert the RF signals to the digital domain.

[0093] In some cases, the processing system 470 may include a coding-decoding device (or CODEC) configured to encode and / or decode data transmitted and / or received using the one or more wireless transceivers 478. In some cases, the processing system 470 may include an encryption-decryption device or component configured to encrypt and / or decrypt data (e.g., according to the Advanced Encryption Standard (AES) and / or Data Encryption Standard (DES) standard) transmitted and / or received by the one or more wireless transceivers 478.

[0094] The one or more SIMs 474 may each securely store an international mobile subscriber identity (IMSI) number and related key assigned to the user of the wireless device 407. The IMSI and key may be used to identify and authenticate the subscriber when accessing a network provided by a network sen-ice provider or operator associated with the one or more SIMs 474. The one or more modems 476 may modulate one or more signals to encode information for transmission using the one or more wireless transceivers 478. The one or more modems 476 may also demodulate signals received by the one or more wireless transceivers 478 in order to decode the transmitted information. In some examples, the one or more modems 476 may include a Wi-Fi modem, a 4G (or LTE) modem, a 5G (or NR) modem, and / or other types of modems. The one or more modems 476 and the one or more wireless transceivers 478 may be used for communicating data for the one or more SIMs 474.

[0095] The processing system 470 may also include (and / or be in communication with) one or more non- transitory- machine-readable storage media or storage devices (e.g., one or more memory- devices 486). which may include, without limitation, local and / or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device such as a RAM and / or a ROM, which may be programmable, flash-updateable, and / or the like. Such storage devices may be configured to implement any appropriate data storage, including without limitation, various file systems, database structures, and / or the like.PATENTQualcomm Docket No 2502422WO36

[0096] In various aspects, functions may be stored as one or more computer-program products (e.g., instructions or code) in memory device(s) 486 and executed by the one or more processor(s) 484 and / or the one or more DSPs 482. The processing system 470 may also include software elements (e.g., located within the one or more memory devices 486), including, for example, an operating system, device drivers, executable libraries, and / or other code, such as one or more application programs, which may comprise computer programs implementing the functions provided by various aspects, and / or may be designed to implement methods and / or configure systems, as described herein.

[0097] FIG. 5 is a diagram illustrating an example 500 of physical channels and reference signals in a wireless network. In some examples, one or more downlink channels and one or more downlink reference signals may carry information from a base station 102 to a UE 104. One or more uplink channels and one or more uplink reference signals may cany' information from UE 104 to base station 102.

[0098] In some aspects, a downlink channel may include one or more of a physical downlink control channel (PDCCH) that carries downlink control information (DCI), a physical downlink shared channel (PDSCH) that carries downlink data, and / or a physical broadcast channel (PBCH) that carries system information, among other examples. In some aspects, PDSCH communications may be scheduled by PDCCH communications.

[0099] In some examples, an uplink channel may include one or more of a physical uplink control channel (PUCCH) that carries uplink control information (UCI), a physical uplink shared channel (PUS CH) that carries uplink data, and / or a physical random access channel (PRACH) used for initial network access, among other examples. In some aspects, UE 104 may transmit acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in UCI on the PUCCH and / or the PUSCH.

[0100] In some cases, a downlink reference signal may include one or more of a synchronization signal block (SSB). a channel state information (CSI) reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), and / or a phase tracking reference signal (PTRS), among other examples. In some examples, an uplink reference signal may include one or more of a sounding reference signal (SRS), a DMRS, and / or a PTRS, among other examples.PATENTQualcomm Docket No 2502422WO37

[0101] An SSB may carry' or include information used for initial network acquisition and synchronization. For example, an SSB can carry or include one or more of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and / or a PBCH DMRS. An SSB may also be referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, base station 102 may transmit multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0102] A CSI-RS may carry information used for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, among other examples. For example, base station 102 can configure a set of CSI-RSs for UE 104, and UE 104 can measure the configured set of CSI-RSs. Based on the CSI-RS measurements, UE 104 can perform channel estimation and report channel estimation parameters to base station 102 (e.g., in a CSI report). For example, the channel estimation parameters can include one or more of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), and / or a reference signal received power (RSRP), among other examples.

[0103] In some examples, base station 102 can use the CSI report to select transmission parameters for downlink communications to UE 104. For example, base station 102 can use the CSI report to select transmission parameters that include one or more of a quantity of transmission layers (e.g., a rank), a precoding matrix (e.g., a precoder), a modulation and coding scheme (MCS), and / or a refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), among other examples.

[0104] A DMRS may carry information used to estimate a radio channel for demodulation of an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of a DMRS may be specific to a physical channel for which the DMRS is used for estimation. DMRSs are UE-specific, can be beamformed, can be confined in a scheduled resource (e.g., rather than transmitted on a wideband), and can be transmitted only when necessary. As shown, DMRSs are used for both downlink communications and uplink communications.

[0105] A PTRS can carry' information used to compensate for oscillator phase noise. In some cases, oscillator phase noise may increase as an oscillator carrier frequencyPATENTQualcomm Docket No 2502422WO38increases. In some examples, a PTRS can be utilized at high carrier frequencies (e.g., such as millimeter wave frequencies) to mitigate oscillator phase noise. The PTRS may be used to track the phase of the local oscillator and to enable suppression of phase noise and common phase error (CPE). As illustrated in FIG. 5, in some examples one or more PTRSs can be used for both downlink communications (e.g., on the PDSCH) and uplink communications (e.g., on the PUSCH).

[0106] A PRS may carry information associated with timing or ranging measurements of UE 104. For example, UE 104 may utilize one or more signals (e.g., PRSs) transmitted by base station 102 to improve an observed time difference of arrival (OTDOA) positioning performance. In some examples, a PRS may be a pseudo-random Quadrature Phase Shift Keying (QPSK) sequence mapped in diagonal patterns with shifts in frequency and time to avoid collision with cell-specific reference signals and control channels (e.g., a PDCCH). A PRS can be designed to improve detectability by UE 104, which may need to detect downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Accordingly, UE 104 may receive a PRS from multiple cells (e.g., a reference cell and one or more neighbor cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRSs received from the multiple cells. In some aspects, base station 102 can calculate a position of UE 104 based on the RSTD measurements reported by UE 104.

[0107] In some examples, an SRS can carry information used for uplink channel estimation, which may be used for scheduling, link adaptation, precoder selection, and / or beam management, among other examples. Base station 102 can configure one or more SRS resource sets for UE 104, and UE 104 can transmit SRSs on the configured SRS resource sets. An SRS resource set may have a configured usage, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity -based operations, uplink beam management, among other examples. Base station 102 may measure the SRSs. may perform channel estimation based on the measurements, and / or may use the SRS measurements to configure communications with UE 104.

[0108] In some cases, a UE may receive a reference signal (e.g., a CSI-RS, an SSB, a DMRS, etc.) from a network entity (or another UE) and can report channel state feedback (CSF) to the network entity (or the other UE), where the CSF is determined based on measurements of the reference signal received at the UE. In some cases, a UE may alsoPATENTQualcomm Docket No 2502422WO39transmit a reference signal (e.g., CSI-RS, DMRS, PT-RS, SRS, etc.), and a network entity (or another UE) may determine characteristics associated with the channel based on measurements of the received reference signal.

[0109] As noted above, systems and techniques are provided herein that can be used to provide enhanced Robust Header Compression (ROHC) for transmitting data packets with ROHC compressed headers and support for out-of-order delivery (GOOD) of one or more packets. In some aspects, the systems and techniques can be used to provide ROHC enhancements for real-time data traffic with latency requirements, including real-time and / or latency-sensitive data traffic such as voice data packet streams and / or XR data packet streams, among various others. For example, the systems and techniques can be used to provide GOOD enhancements for downlink (DL) communications of real-time and / or latency-sensitive ROHC compressed data packets. In some aspects, the systems and techniques can be used to implement ROHC header compression for data packets associated with or utilizing multiple flows in the uplink (UL). In some aspects, the systems and techniques can provide improved flow control for ROHC compressed data packets.

[0110] FIG. 6 is a diagram illustrating an example of a protocol stack, which may be a 5G NR control plane stack and user plane stack corresponding to a UE 600, a base station 602 (e.g., gNB, network entity, etc.), and a core network node 604. In some examples, where the control plane stack is the 5G NR control plane stack, the core network node 604 may be a 5G core netw ork (5GC) node, such as an application management function (AMF), etc. The UE 600 may be any UE described herein, such as UE 104, etc. In some aspects, the base station 602 may be a 5G base station (gNB) or any other base station described herein, such as base station 102, etc. The core network node 604 may be any core network node described herein, e.g., a core access and mobility management function (AMF) in some aspects. Layers common to both the UE 600 and the BS 602 include the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the medium access control (MAC) layer. Downlink traffic is from the BS 602 to the UE 600, and uplink traffic is from the UE 600 to the BS 602.

[0111] The RRC layer can be configured for establishment, maintenance, and release of an RRC connection between the UE 104 and next generation (NG) radio accessPATENTQualcomm Docket No 2502422WO40network (RAN). For example, the RRC layer can be used for the establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs). The RRC layer can be used for mobility functions including handover and context transfer. The RRC layer can be used for UE cell selection and reselection, among various other functions.

[0112] The PDCP layer can be used for the sequence numbering of packets, reordering and duplicate detection of packets, ciphering and deciphering, retransmitting or discarding service data units (SDUs), duplicating protocol data units (PDUs). among various other functions. The PDCP layer may operate with the RLC layer configured for operation in an Acknowledged Mode (AM), or an Unacknowledged Mode (UM). In some examples, the AM operation mode of the RLC layer may be used for DRBs in the user plane with acknowledgements used to support and provide retransmissions when needed. In some examples, the UM operation mode of the RLC layer may be used for DRBs in the user plane, and does not use acknowledgements and does not support RLC -layer retransmission. PDCP Sequence Numbers (SNs) can be used for delivery ordering and to support packet reordering, and may be associated with SRBs for control plane signaling such as RRC. NAS, etc. (e.g., SRBL SRB2, etc.). In some examples, PDCP SNs can also be used for packet reordering and loss detection over bearers for user plane traffic (e.g., VoIP, HTTP, etc.), such as DRBs. Each bearer represents a virtual logical path established between a UE and the core network of the wireless communications network for carrying data packets. Each bearer can be configured with corresponding quality -of-service (QoS) parameters, encryption, routing rules, etc., and can be used for particular t pes of traffic on different bearers.

[0113] The RLC layer can be used for sequence numbering of packets independent of the PDCP sequence numbering, segmentation and reassembly of SDUs. The MAC layer can be used for mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels, among various other functions. The functions of the non-access stratum (NAS) layer and the physical (PHY) layer can be according to the wireless network standard or protocol, such as according to the 5GNR, 6G, and beyond standards, etc.PATENTQualcomm Docket No 2502422WO41

[0114] In some cases, atransmitting communications device (e.g., such as UE 600) may send multiple DRB packets to a receiving communications device, and the packets may be received out of order. The PDCP layer on a receiving communications device (e.g.. the UE 600 for downlink traffic and the BS 602 for uplink traffic) includes a reorder buffer 606 for reordering incoming packets, including DRB packets, that are received from a transmitting communications device (e.g., the BS 602 for downlink traffic and the UE 600 for uplink traffic). The PDCP layer receives these incoming packets from the RLC layer, stores them in the reorder buffer 606 as needed, and may send data from the reordered DRBs to the application layer for processing, etc. For example, if the PDCP layer detects that an out-of-order (OOO) packet was received, the PDCP layer stores the 000 packet and waits for the missing packet(s) to arrive, at which time the PDCP layer reorders the packets into the correct order before releasing the packets to the application layer. In some aspects, receiving out-of-order packets can also be referred to herein as out-of-order deliver (GOOD) and / or out-of-order packet delivery, etc.

[0115] In some examples, the storage space in the reorder buffer 606 is limited, and a reordering timer (e.g., “Treordering’") can be used to clear out old packets, for example according to a packet eviction scheme implemented by or for the reorder buffer 606. In some cases, clearing old packets and / or implementing a packet eviction scheme can correspond to releasing stored packets (e.g., data from DRBs) to the application layer. The reordering timer value, Treordering, can be configured by the network and in at least some cases may be set to a short value. Relatively short values of the reordering timer Treordering may, in at least some cases, provide improved performance for certain Data Radio Bearers (DRBs), which may benefit from or may require relatively lower latency. In other examples, other applications may utilize TCP and may not benefit from or see improved performance with OOO packets.

[0116] In some examples, a transmitting device (e.g., a UE or network entity, etc.) can apply compression to one or more portions of data packets that are to be transmitted to a destination or receiving device (e.g., a network entity or UE, etc.). The destination or receiving device can include a decompression module to receive compressed data packets from the source and apply decompression to recover the communication, uncompressed information from the transmitting device. FIG. 7 illustrates an example of a data packet 700 including one or more headers and a payload transmitted within a wireless network,PATENTQualcomm Docket No 2502422WO42in accordance with some examples. A data packet 700 in a wireless communication network can include a data payload 740, including data to be transmitted within the wireless communication network. The data packet 700 can further include a header 705 attached to the payload 740, where the header 705 of the data packet 700 includes multiple fields of header data used in administration of data packets within the network. For example, the data packet 700 can be transmitted within the network using a Real-Time Transfer Protocol (RTP), which is a protocol that supports real time transmission of voice and video packets, on top of a User Datagram Protocol (UDP)ZIntemet Protocol (IP).

[0117] In examples where the data packet 700 is transmitted in an RTP / UDP / IP environment, the header 705 can include a first header portion (e.g., first header field) comprising an RTP header 730. a second header portion (e.g., second header field) comprising a UDP header 720, and a third header portion (e.g., third header field) comprising an IP header 710. In some cases, the first header field for the RTP header 730 may include at least 12 bytes, the second header field for the UDP header 720 may include at least 8 bytes, and the third header field for the IP header 710 may include at least 20 bytes. In this example, the header 705 of the data packet 700 can include 40 or more bytes, which can be larger than the number of data bytes within the payload 740. The relatively large size of the header 705 relative to the data payload 740 can correspond to high overhead associated with the transmission of the packet 700, where the overhead corresponds to the ratio between non-payload bytes (e.g., header 705 bytes) to payload bytes (e.g., data payload 740 bytes), the ratio of non-payload bytes (e.g., header 705 bytes) to the total bytes in the packet 700, and / or the ratio of pay load bytes (e.g., data payload 740 bytes) to the total bytes in the packet 700.

[0118] Header compression can be performed to reduce the overhead associated with transmitting the packet 700. based on the header compression reducing the number of bytes used to represent the information of the at least 40 uncompressed bytes of data across the three header fields 710, 720, and 730. For example, a relatively large portion of the header data within the header 705 may be static information. In some examples, header compression may be applied to compress the header 705 in a compression module of a source unit, transmitting device, etc. associated with the data packet 700. In some examples of header compression for data packets, static header fields may be transmittedPATENTQualcomm Docket No 2502422WO43at the beginning of a session corresponding to the communication of a plurality of data packets 700. The non-static information and / or header fields within the header 705 can be referred to as dynamic header fields, and can include, for example, an RTP timestamp (TS) field, an RTP sequence number (SN) field, and an IP identification (IP-ID) field, among various others. The dynamic header field information within the packet header 705 can be compressed before transmission of each data packet 700. In some cases, dynamic header fields may be inferred from the value of the RTP SN field, and header compression for the header 705 of the data packet 700 can be performed based on the RTP SN being the only field that is compressed and transmitted with each data packet 700.

[0119] In some cases, header compression can be performed using Robust Header Compression (ROHC), where the data packet headers are compressed according to a compression profile mapped to the particular protocol stack used for the bearers and / or transmission of the data packets. For example, as noted above, ROHC includes different compression profiles that are indicative of header compression techniques and / or parameters that may be used to compress the data packet headers associated with protocols such as Real-Time Transfer Protocol (RTP), which is a protocol that supports real time transmission of voice and video packets, on top of a User Datagram Protocol (TJDP) / Internet Protocol (IP). In some examples, ROHC may be used to increase efficiency and / or to reduce packet transmission overhead over constrained links by compressing repetitive and predictable IP / UDP / RTP / etc. headers into minimal-size encodings. For example, the ROHC standard codified as RFC 3095 by the Internet Engineering Task Force (IETF) defines different profiles for header compression. Each ROHC compression profile can be used for a corresponding network protocol stack, can be associated with a unique 16-bit profile identifier, and can be indicative of a definition for the compression of headers of a particular protocol combination. In some examples, ROHC compression profile 0x0001 can be used for compression of headers for RTP / UDP / IP. The ROHC compression profile 0x0002 can be used for header compression associated with UDP / IP. The ROHC compression profile 0x0003 can be used for header compression associated with Encapsulating Security Payload (ESP) / IP. The ROHC compression profile 0x0004 can be used for compression of IP-only headers (e.g., no upper layer). In some examples, profile 0x0000 is an uncompressed profile where ROHC and / or header compression are not implemented and packets are transmittedPATENTQualcomm Docket No 2502422WO44without performing header compression. Various other ROHC compression profiles and profile IDs (e.g., 0x0007, 0x0008, etc.) can be reserved or unassigned, and may be used for header compression outside of or in addition to that codified by the ROHC standards. In some cases, the ROHC profiles 0x0007 and 0x0008 can be used for compression of UDP-Lite headers.

[0120] In some examples, ROHC header compression can use Least Significant Bits (LSB) encoding for the header fields being compressed. For example, LSB encoding may be used for header fields whose values are subject to relatively small changes. With LSB encoding, a quantity k least significant bits (LSBs) of the header field value are transmitted instead of the original field value (where k is a positive integer comprising a number of bits that is less than or equal to the number of bits in the original field value). After receiving the k LSBs of the header field value, the decompressor may derive the original header field value using a previously received header field value as reference. The previously received header field value used as reference by the decompressor can be represented as the reference vref.

[0121] In one illustrative example, ROHC compressors and decompressors may implement LSB encoding for header compression based on an SN field value “v” that is to be encoded and compressed. The ROHC compressor can use the LSB encoding to facilitate transmission of the “k” least significant bits of the “v” value, if a previously transmitted reference value “vref” is present at both the ROHC compressor and the ROHC decompressor. The LSB encoding technique can be applied when the compressor and decompressor each use an interpretation interval or shifting interval in which “v” resides, and in which "‘v” is the only value that has the exact same “k” as those transmitted.

[0122] For example, the LSB encoding of header fields for ROHC compression may be guaranteed to be correct if the compressor and decompressor implementing ROHC are each configured to use interpretation intervals in which the original header field value resides, and in which the original header field value is the only value that has the exact same k LSBs as those that were transmitted as the compressed representation of the currently received header field value. In some examples, the interpretation interval used for an ROHC compressor and ROHC decompressor using LSB encoding of header fields can be represented as a function of the previously received header field reference v,c / and the uantity k of LSBs.PATENTQualcomm Docket No 2502422WO45

[0123] For example, the interpretation interval within which the header field value v is expected to vary can be described as the function f(vref, kj = [vref— p, vre+ 2k— 1 — p], where p is an integer used to represent a shifting parameter selected for the SN header field. In one illustrative example, the interpretation interval function f(vref, k) has the property that for any value k, the k least significant bits (LSBs) will uniquely identify a value in f(vref,. As noted above, the parameter p can be introduced to configure different integer shifts of the interpretation interval with respect to the vref reference value.

[0124] In some aspects, the interpretation interval described by the function— 1 — p] may have a size equal to 2k, spanning between the first interpretation interval endpoint (vre^ — p) to the second interpretation interval endpoint2k— 1 — p). The value k of LSBs can correspond to the number of bits that are used to compress an input sequence number (SN) for a data packet header field, in some aspects.

[0125] In one illustrative example, based on the 2kwindow size of the interpretation interval (re, k~. the value of the integer p can be equal to the number of GOOD packet deliveries that can be tolerated before the ROHC decompressor is unable to use the LSB encoding scheme to decompress a received k LSBs representing a compressed header field value. The 2kwindow size of the interpretation interval (v,.ek) may be a constant or static window size for ROHC.

[0126] The different ROHC compression profiles corresponding to the different packet protocols can be associated with corresponding table values or table entries that are indicative of parameters describing the interpretation interval f(vref> ) used by the ROHC compressor and decompressor to perform the LSB encoding of data packet header fields. For example, compression profile 0x0001 (e.g., RTP / UDP / IP, which may be the ROHC compression profile used for voice data traffic or voice data streams (e.g., including VoIP, VoLTE, etc.)), compression profile 0x0003, and compression profile 0x0007 can be configured to perform LSB encoding using a value of the interpretation interval offset, p, determined according to:For profiles 0x0001. 0x0003. and 0x0007:p = 1, when bits(SN) < 4;PATENTQualcomm Docket No 2502422WO46p=2bits(SNt-5 J, otherwise (c.g., if bits(SN) > 4).

[0127] Table 1, below, illustrates an example LSB encoding configuration table for the interpretation interval used for LSB encoding by an ROHC compressor or decompressor with ROHC compression profiles 0x0001, 0x0003, and / or 0x0007.Table 1. Example interpretation interval parameters for LSB encoding implemented by ROHC compressors or decompressors using one of the compression profiles 0x0001, 0x0003. or 0x0007.

[0128] In the interpretation interval parameters indicated in the example of Table 1, the first column represents the number of LSB bits, k, used to compress a data packet header field value between the ROHC compressor and the ROHC decompressor. The second column represents the maximum amount of reordering (e.g., the maximum reordering depth within the sequence of packets) that can be tolerated before the ROHC decompressor is no longer able to perform decompression to recover the original data packet header field value. For example, the maximum amount of reordering, given a value of k, is equal to the value of the offset p applied to the interpretation interval. For example, the offset p may indicate the maximum reordering depth for an out-of-order packet, where the reordering depth is the difference between the SN of the out-of-order packet and the expected packet SN in the sequence (e.g., the number of SN slots that an out-of-order packet arrives early or late relative to the expected SN and sequence slot or position for the out-of-order packet if arriving on-time). The third column represents the maximum amount of packet losses that can be tolerated by the ROHC decompressor, given the values of k and p.

[0129] For example, the interpretation interval offset parameter p is greater than or equal to two when the number of compressed bits (e.g., k) for the compressed SN packet header field is less than seven. The interpretation interval offset parameter p is greaterPATENTQualcomm Docket No 2502422WO47than or equal to four w hen the number of compressed bits (e.g., k) for the compressed SN packet header field is equal to seven.

[0130] In some aspects, the reference point vref is located within the interpretation interval, away from either endpoint. The portion of the interpretation interval to the left of the reference vref is [vre— p, vrey], and may be the portion of the interpretation interval representing the amount of packet reordering (e.g., number of OOOD packet deliveries) that can be tolerated by the ROHC decompressor. The maximum delta betweenvref ~ P and vref is p. and the maximum OOOD packets and / or packet reordering for a compressed header field is equal to p.

[0131] The portion of the interpretation interval to the right of the reference v’re / is [vref, vref + 2k— 1 — p], which can be the portion of the interpretation interval representing the amount of packet loss(es) that can be tolerated by the ROHC decompressor. The maximum delta between vref and vref + 2k— 1 — p is equal to 2k— 1 — p, and the maximum packet loss(es) for a compressed header field is equal to 2k— 1 — p.

[0132] Based on the interpretation interval offset p being equal to the number of OOOD packet deliveries that can be tolerated by the ROHC decompressor implementing LSB encoding, a k = 4 LSB compressed header field can be decompressed with up to p = 1 OOOD packets that are reordered by the decompressor, with maximum packet losses of 14. AC = 5 LSB compressed header field cannot be decompressed if any OOOD packets are present or experience reordering, based on the entry7in Table 1 for k =5 being mapped to a corresponding offset supported OOOD reordering ofp = 0. and with maximum packet losses of 31..

[0133] In another example, a k = 6 LSB compressed header field can be decompressed with up to p = 1 OOOD packets that are reordered by the decompressor, with maximum packet losses of 62. A k = 7 LSB compressed header field can be decompressed with up to p = 3 OOOD packets that are reordered by the decompressor, with maximum packet losses of 124. AC = 8 LSB compressed header field can be decompressed with up top = 7 OOOD packets that are reordered by the decompressor, with maximum packet losses of 248. A C = 9 LSB compressed header field can be decompressed with up to p = 15 OOOD packets that are reordered by the decompressor, with maximum packet losses of 496.PATENTQualcomm Docket No 2502422WO48

[0134] Accordingly, as represented in Table 1, the ability for ROHC compression and / or decompression to be performed while handling sequentially late packets (e.g., OOOD packets) can be based on the number of bits that are sent in each packet (e.g.. the k LSBs, etc.). For example, a sequentially late packet of type 0 has either 4-bits or 6-bits of SN, which sets the limit to only one single packet out of sequence for successful ROHC decompression to be possible (e.g., based on k =4 and k = 6 both corresponding to = 1, as indicated by Table 1).

[0135] For ROHC compression profiles 0x0002 (UDP / IP), 0x0004. and 0x0008. the tolerated amount of OOOD packets and packet reordering at the decompressor can be equal to zero (e.g., no OOOD packets or packet reordering may be performed in some examples where ROHC compression profiles 0x0002, 0x0004, or 0x0008 are used). In these examples, the interpretation interval offset value p = -1. independent of the particular SN for a header field value. The interpretation interval offset value of p = -1 indicates that the interpretation interval offset p may only take positive values, and that no sequentially late packet (e.g., OOOD packet) can be decompressed if reordering occurs over the link between ROHC compressor and ROHC decompressor.

[0136] In some examples, the ability of ROHC to be performed when sequentially late packets are present between the compressor and decompressor (e.g., transmitter and receiver) can be limited by the interpretation interval offset p of the sliding window' used for the LSB encoding. The offset p may have a small value for packets with a small number of sequence number (SN) bits. The value of the offset p can grow with the number of SN bits that are transmitted. In some cases, for channels where both packet losses and packet reordering may occur, modifications to the interpretation interval are implemented as a trade-off between the amount of reordering and the number of consecutive packet losses that can be handled by the decompressor. For example, for channels where both packet losses and packet reordering may occur, an increase in the interpretation interval offset p (e.g., amount of packet reordering and OOOD packets) is compensated by a decrease in the number of consecutive packet losses tolerated. A decrease in the interpretation interval offset p (e.g., amount of packet reordering and OOOD packets) is compensated by an increase in the number of consecutive packet losses tolerated, etc.

[0137] In cases where the negative offset (e.g., p) is increased to support or handle a larger amount of packet reordering (e.g., more OOOD packets) by the ROHCPATENTQualcomm Docket No 2502422WO49decompressor, the value of the positive offset of the interpretation interval must be decreased, which can impact the compression efficiency over the channel in examples where the channel has a high loss rate.

[0138] As noted above, real-time traffic and / or streams, such as voice and / or XR, may benefit from the use of PDCP OOOD and packet reordering. For example, in real-time voice traffic scenarios, an Audio Dejitter buffer is implemented in association with processing the real-time voice traffic. The Audio Dejitter buffer associated with the realtime voice traffic has a corresponding waiting time for buffering, and in one illustrative example, the waiting time of the Audio Dejitter buffer used for real-time voice traffic can be used as the reordering timer Treordermg to implement ROHC header compression. In some cases, if a missing real-time voice data packet arrives at a receiver (e.g., decompressor) prior to the playout time of the packet, the use of OOOD and packet reordering with the Audio Dejitter buffer as the reordering timer Treordering can allow the receiver to still play out the late-arriving and previously missing voice data packet after performing reordering and decompression according to the LSB encoding for the ROHC implementation. In some aspects, the determination that a missing packet arrives before playout time may be according to the Audio Dejitter buffer target delay.

[0139] In some cases, the use of PDCP OOOD for real-time traffic such as voice and / or XR may be used to reduce latency associated with the real-time traffic. For example, the target delay for the Audio Dejitter buffer may be greater than 40 milliseconds (ms) if the channel has been previously measured or determined to have jitter. Using PDCP OOOD can reduce the latency associated with the real-time traffic on the channel with previously measured jitter, based on PDCP OOOD and packet reordering reducing the waiting time of subsequently arriving packets after a missing packet in the expected sequence (e.g., expected sequence according to the monotonically increasing SN, etc.), which is delivered after expiry of the timer Treordering in PDCP. In some aspects, the use of PDCP OOOD and packet reordering for real-time traffic (e.g., such as real-time voice traffic and / or real-time XR traffic, etc.) can reduce the underflow in cases where the target delay was insufficient to handle delays due to Treordering implementations.

[0140] The systems and techniques described herein can be used to provide enhanced OOOD and / or packet reordering implementations for real-time data traffic including a plurality of packets with ROHC header compression. For example, the systems andPATENTQualcomm Docket No 2502422WO50techniques can be used for enhanced GOOD and / or packet reordering for real-time voice traffic comprising a plurality of voice data packets with at least a portion of the packets using ROHC header compression. As noted above, in some ROHC techniques, GOOD is not permitted and / or minimal GOOD is supported. For example, ROHC as codified in RFC 3095 assumes in-order delivery7is guaranteed for packets transmitted from compressor to decompressor, while RFC 4224 considers ROHC over reordering channels with minimal or relatively small amounts of reordering and / or GOOD. In one illustrative example, the systems and techniques can be used to enable GOOD and / or packet reordering for real-time traffic including one or more of voice data packets and / or XR data packets, based at least in part on using a corresponding compression profile with modified values for the interpretation interval offset p of the sliding window used for the LSB encoding by the ROHC compressor and decompressor.

[0141] In some examples, the systems and techniques can be used for GOOD of realtime traffic (e.g., voice data packets and / or XR data packets, etc.), where the systems and techniques can provide an increased number of GOOD packet deliveries than other ROHC techniques. For example, in some cases the network can configure an OOODthreshoid parameter, where the ROHC compressor and decompressor (e.g.. included in a transmitter and receiver, respectively) are configured to use the same OOODthreshoid value. An OOO packet can be delivered if the difference between the current or next SN expected in the sequential order of packet SNs, and the SN of the 000 packet is less than the OOODthreshoid value, for example based on ASJV< OOODthreshoid. The value of the parameter OOODthreshoid may be determined and configured by the network, based on OOODthreshoid = offset p reordering (k) corresponding to the ROHC compression profile used and k = number of bits for RTP SN. In some examples, k = 4 (e.g., from field logs for profile 0x0001 RTP / UDP / IP) and the OOODthreshoid = 1, indicating a maximum of one packet may be delivered out-of-order when used for real-time data traffic (e.g., voice packets and / or XR packets, etc.) with ROHC header compression. In the example of the OOODthreshoid being used for GOOD delivery7, packets may be delivered out-of-order when the configured compression profile is the 0x0001 profile. When the configured compression profile is 0x0002 (UDP / IP), as may be used for real-time XR traffic and / or data packets, the interpretation interval offset p has a value of -1, and no reordering is allowed or performed by the ROHC decompressor.PATENTQualcomm Docket No 2502422WO51

[0142] In another illustrative example, the systems and techniques can support increased numbers of OOOD packet deliveries for voice and / or XR traffic based on selecting a higher k value from the respective entries within the corresponding table of interpretation interval parameters for LSB encoding used by the different ROHC compression profiles (e.g., the corresponding table, such as the Table 1 interpretation interval parameters noted above, corresponding to ROHC compression profiles 0x0001, 0x0003, 0x0007).

[0143] For example, when the compression profile is configured as profile 0x0001 (RTP / UDP / IP), as may be used for real-time voice traffic and latency-sensitive data packets, and / or if the compression profile is configured as profile 0x0003 or 0x0007, the Table 1 interpretation interval parameters can be used to select interpretation interval parameters for higher values of k, where k is the number of LSB bits used for compressing header field value (e.g., SN, etc.).

[0144] In some aspects, higher values of k can be used for the real-time voice traffic stream(s), such as the row of Table 1 corresponding to k = 8, or k = 9, etc. Selecting a higher value of k from the interpretation interval parameters table for the configured compression profile corresponds to the ROHC compressor and decompressor supporting an increased number of OOOD deliveries, without changes to the compression profile. For example, using k = 8, real-time voice packets transmitted with ROHC compression using profile 0x0001 can be received by the decompressor with up to p = 7 OOOD deliveries. The offset of p = 7 corresponds to a late-arriving packet that is 7 SNs out of order (e.g., late) in the sequence of SNs. For example, using k = 8 for compression profile 0x0001, a real-time voice packet can arrive up to 7 SNs late and still be decompressed by the decompressor applying LSB encoding within the interpretation interval configured using k= 8 and p = 7 (e.g., an OOOD late-arrive packet with SN = 93 can be decompressed when SN = 100 was the last decoded packet).

[0145] In some examples, higher values of k selected from the configured set of interpretation interval parameters provided for each ROHC compression profile may be used in combination with the OOODthresholdnoted above. Using higher values of k from the compression profile table of interpretation interval parameters corresponds to using more compressed bits to represent a header field value, based on k indicating the number of LSBs used as the compressed representation of each header field value. Increasing thePATENTQualcomm Docket No 2502422WO52value of k reduces compression gain of the ROHC scheme implemented by the compressor and decompressor, based on the trade-off noted above where increasing the maximum supported reordering causes a decrease in the packet loss tolerance of the decompressor. For example, higher k, and therefore higher p, values correspond to increased reordering tolerance by the decompressor. The increased reordering tolerance is based on the higher p value shifting the interpretation window further backward, which increases the probability of the interpretation window overlapping with older SN values for late-arriving OOO packets. Shifting the interpretation window further backward by increasing p causes a corresponding reduction in the forward reach of the interpretation window to include future SNs in the sequence (e.g., reduction in how far ahead in sequence a compressed SN can be successfully interpreted), meaning that fewer losses can be tolerated by the decompressor. In some aspects, increasing the number of bits used for each compressed SN for the real-time voice data packets (e.g., increasing k) may reduce the compression gain of the ROHC scheme implemented between the compressor and decompressor.

[0146] In one illustrative example, the systems and techniques can be used to implement new and / or modified ROHC compression profiles having higher p offset values for the interpretation interval window. As noted above, higher p offset values correspond to increasing the maximum supported GOOD delivery that is supported by the decompressor before decoding fails for a late-arriving or 000 packet delivery. In some aspects, real-time traffic such as voice and / or XR packets, can be configured to use ROHC header compression and OOOD at the compressor and decompressor. In some cases, the increased (e.g., higher) value of the offset p for the interpretation interval window may be implemented by modifying the ROHC compression profile tables used by the compressor and decompressor. For example, the increased values of the p offset can be stored in the compression profile tables (e.g., such as Table 1, etc.) mapped to the existing k values for the number of bits used for each compressed SN. For example, the existing Table 1 entry for the k = 6, p = 1 row may be modified to use a higher offset value such as p = 3, etc., where the updated Table 1 entry indicates the mapping between k = 6 and p = 3 for profiles 0x0001, 0x0003, 0x0007. Updated (e.g., increased) values of the p offsets for the interpretation interval window can be implemented for the respective compression profile tables used for other ROHC compression profiles including 0x0002, 0x0004, 0x0005, 0x0008, etc.PATENTQualcomm Docket No 2502422WO53

[0147] In some aspects, the systems and techniques can provide ROHC header compression and GOOD for real-time voice and / or XR data packet traffic flows based on signaling indicative of the k and p values configured for use in the ROHC compression scheme by the compressor and decompressor. For example, a network entity (e.g., base station, gNB, etc.) can transmit signaling indicative of a configured k value and the corresponding configured p offset value. The compressor and decompressor can receive the signaling, and implement ROHC compression and decompression, respectively, using the configured k and p values, which may be the same as or which may be different from the respective k and p values that may otherwise be indicated according to the compression profile table of interpretation interval parameters. In some cases, the network entity that transmits the signaling indicative of the configured k and p values may be different from the transmitter unit including the ROHC compressor and the receiver unit including the ROHC decompressor. In some examples, the network entity that transmits the signaling indicative of the configured k and p values may be the same as the transmitter unit with the ROHC compressor, or may be the same as the receiver unit with the ROHC decompressor.

[0148] Examples where configured k and p values are implemented can increase the maximum supported reordering and GOOD deliveries at the decompressor, with a corresponding reduction in the loss tolerance of the decompressor. Increasing the maximum reordering by increasing the p offset value can, in some cases, cause the ROHC scheme and / or compressor and decompressor to use a lower (e.g., reduced) modulation coding scheme (MCS), and / or more HARQ feedback, among various other techniques to reduce loss and / or compensate for the reduced loss tolerance from the increased p and maximum supported reordering for OOOD deliveries.

[0149] In one illustrative example, new values for k and p may be configured for data packets associated with any compression profile, including the compression profiles 0x0002, 0x0004, and 0x0008 that use p = -1 and do not support any reordering under the ROHC standards. For example, compression profile interpretation interval tables for one or more of the 0x0002, 0x0004, and / or 0x0008 profiles can be modified or updated to include positive values of p mapped to the different numbers of SN compressed bits, k and / or positive values of p (and a corresponding value of k) may be signaled by a networkPATENTQualcomm Docket No 2502422WO54entity to the compressor and decompressor configured with compression profile 0x0002, 0x0004, or 0x0008, etc.

[0150] In some cases, XR and / or XR-based data traffic and packets can be associated with multiple flows. For example, XR data traffic can include multiple independent data streams or flows of real-time and latency -sensitive data packets. Multiple Hows or streams for XR data traffic may correspond, in some examples, to multiple RTP sessions (e.g., a respective RTP session and XR data traffic flow for each audio and / or video track), separate UDP streams for control information and data information, and / or multiple UDP streams or combinations of various UDP flows, etc. Each flow of the multiple XR traffic How s may be implemented using its own SNs and packet header fields, which may evolve and / or be generated independently from the SNs and packet header fields within other ones of the multiple XR traffic flows. In ROHC, each flow is compressed separately, based on the independent evolution of the header fields such as the SN, IP ID, and / or TS, etc., which corresponds to a need for individual tracking for ROHC applied to each stream to achieve correct decompression of the ROHC compressed packets.

[0151] The PDCP specification implements a maximum number of contexts per ROHC bearer, represented as MAX CID for each respective ROHC bearer. In ROHC. each active flow being compressed is assigned a corresponding Context ID (CID) that is used to track the state of the static and dynamic fields of or within the active flow being compressed. The respective CID for each flow' being compressed is used by the decompressor to differentiate between multiple compressed flows over the same ROHC channel. In some aspects, the parameter MAX_CID is configured to be indicative of the maximum number of contexts (e.g., flows) that are concurrently supported over a single ROHC bearer, and may be determined and / or indicated during ROHC negotiation (e.g., signaled over RRC, etc.). The decompressor can be configured to perform simultaneous tracking of a number of flows equal to (or less than) MAX CID for a single ROHC bearer. An ROHC bearer is a logical channel over which ROHC-compressed packets can be transmitted betw een the compressor and decompressor, for example corresponding to a user-plane Data Radio Bearer (DRB) (and / or control plane Signaling Radio Bearer (SRB), as noted above). The compressed flows within the same ROHC bearer use the same ROHC profile negotiation and same compression profile, and also use the same decompression entity' (e.g., ROHC decompressor).PATENTQualcomm Docket No 2502422WO55

[0152] In some examples, the systems and techniques can be used to provide ROHC for XR traffic flows and / or other real-time and / or latency-sensitive data traffic comprising multiple flows, including when the number of flows in the multiple flows exceeds the configured MAX CID per ROHC bearer. For example, the systems and techniques can be used to implement an eviction scheme that is performed in response to a new7flow7that exceeds the MAX_CID number of contexts (e.g., that exceeds the maximum number of flows supported on the current ROHC bearer). For example, the new flow can be implemented based on selecting one or more existing flows to evict from the set of contexts on the bearer, w ith the new flow replacing the evicted flow to remain within the MAX CID number of contexts on the bearer.

[0153] In a Least Recently Used (LRU) scheme of eviction, processing overhead and complexity may be introduced based on repeated attempts or cycles where an existing flow is evicted to support a new flow, and later the evicted flow is added back to the contexts on the bearer (e.g., after termination of the new7flow7, etc.). In one illustrative example, the systems and techniques can analyze one or more parameters or characteristics of the set of flows on an ROHC bearer to determine which flows benefit from ROHC compression. For example, not all flow s of a bearer need to be compressed, or would benefit from performing ROHC compression for the data packets of the flow. Some ROHC configuration techniques may support only a per-bearer configuration, where ROHC is enabled (e.g., and therefore performed) for the data packets of each individual flow of the multiple flows on an ROHC bearer, or where ROHC is disabled (e.g., and therefore not performed) for any of the data packets on any of the flow's of the multiple flows on the ROHC bearer. In some cases, ROHC configuration on higher throughput bearers may lead to CPU issues resulting in data stall.

[0154] The systems and techniques can be used to provide ROHC configurations to enable or disable ROHC on a per-flow basis, where the configuration information causes a compressor and decompressor implementing the ROHC scheme to determine individually whether ROHC compression is performed (e.g., enabled) or not performed (e.g., disabled) for each respective flow of a plurality of flows associated with a single ROHC bearer. For example, flows with smaller PDU sizes and / or lower latency requirements may benefit relatively more, or the most, from using ROHC to perform header compression, while flows with larger PDU sizes and / or higher latencyPATENTQualcomm Docket No 2502422WO56requirements (or no latency requirements), may benefit relatively less from using ROHC to perform header compression. The system and techniques can provide ROHC configuration information indicative of ROHC enablement to cause the compressor to perform header compression using ROHC for a first subset of flows included in the plurality7of flows, and to not perform header compression and to not use ROHC for a second or remaining subset of flows included in the plurality of flows. The first subset of floyvs for which ROHC is enabled can include the flows with smaller PDU sizes and / or lower latency requirements. The second subset of flows for which ROHC is disabled (e.g., not enabled) can include the flows with larger PDU sizes, larger latency requirement, and / or no latency requirements, etc.

[0155] In one illustrative example, the systems and techniques can be used to perform eviction of existing contexts of an ROHC bearer based on usage information determined for the ROHC bearer and / or for respective flows on the ROHC bearer within a configured interval prior to the current time. For example, eviction of contexts can be performed based on usage information measured or determined for the last X seconds, where X is the configured time interval measurement period for the contexts eviction scheme. In some examples, the time interval measurement period can be used for contexts eviction instead of the LRU-based eviction yvhere the least recently used context(s) are selected for eviction. The usage information-based eviction scheme can reduce the chum of contexts on the bearer, as the LRU-based eviction scheme may often be associated with a constant chum in the contexts on the bearer, as the least recently used context changes frequently or rapidly over time. In one illustrative example, the systems and techniques can monitor the elapsed time since a context of an ROHC bearer was last used, and can evict the context in response to the elapsed time from the last use exceeding the configured threshold time X for eviction. In some aspects, if a neyv context is added to the bearer that would cause the bearer to exceed the MAX CID maximum number of contexts per bearer, and if none of the active (e.g., existing) contexts on the bearer have an elapsed time from last use that exceeds the eviction time threshold X, the systems and techniques can be configured to use uncompressed context for the new context and any further new contexts that may be added to the bearer, until an active context is identified as reaching an elapsed time from last use that exceeds the eviction threshold time X.PATENTQualcomm Docket No 2502422WO57

[0156] In one illustrative example, the systems and techniques can be used to provide per-flow ROHC configuration(s) and / or configuration information, for a plurality of flows of an ROHC bearer. In some cases, ROHC is configured per flow in NAS. The network may configure only the flows that can benefit from using ROHC, while the remaining portion of the flows on the bearer will be uncompressed and do not use ROHC or header compression.

[0157] In some aspects, per-flow ROHC configuration can be performed based on capability information corresponding to the compressor and / or the decompressor. For example, a UE may indicate corresponding capability information indicative of one or more QoS Class Identifiers (QCIs) and / or flows of a bearer associated with the UE that can benefit from using ROHC. In some cases, the UE may indicate UE Application Information (UAI) indicative of the one or more QCIs and / or flows of a bearer associated with the UE that may benefit from using ROHC. In some aspects, the indicated QCIs and / or flows may be a set of flows for which the UE requests that ROHC and header compression be used. In some aspects, the UE can determine and / or verify, prior to transmitting the capability information, UAI, or request, that the indicated QCIs and / or flows for ROHC would remain within the UE throughput limitations of UE processing if ROHC is enabled for each requested QCI and / or flow. For example, the capability information or request from the UE can indicate a set of QCIs or flows that would be within the UE throughput processing capabilities if ROHC is used for each requested QCI or flow of the indicated set. In some cases, transmitting the UE capability information and / or UE request for ROHC for one or more QCIs and / or flows can reduce the occurrence of context exceeding the MAX_CID for a bearer, and / or may be used to reduce the occurrence of high throughput UE processing limitations during the multiple flows being communicated over the bearer. In some aspects, the configuration of per-flow ROHC can also be used for different compression schemes and techniques, including Uplink Data Compression (UDC), etc., among various others.

[0158] In another illustrative example, the systems and techniques can be used to provide flow control for multiple flows on a bearer (e.g., ROHC bearer, etc.). For example, ROHC configuration on higher throughput bearers may cause CPU and / or processing issues at a UE that can cause data stall over the bearer or channel. In uplink (UL) scenarios, the UE may be configured with a choice of selectively sending one orPATENTQualcomm Docket No 2502422WO58more uncompressed packets, which can mitigate the possibility of ROHC configuration on higher throughput bearers causing CPU and / or processing issues, or data stall. In downlink (DL) scenarios, it may be beneficial for systems and techniques to be provided for a mechanism for the UE to request or cause packet decompression to be stopped, for example a temporary' stop or pause to prevent data stall, etc. In the UL scenarios, the UE can be configured as the ROHC compressor, and in the DL scenarios, the UE may be configured as the ROHC decompressor. In DL scenarios, the UE receives ROHC compressed packets from the compressor, which may be implemented by a network entity (e.g., base station, gNB, etc.). Existing ROHC techniques do not support stopping decompression at the UE or decompressor, based on stopping the decompression corresponding to packet loss due to the dependency on previous decompressed packets in the sequence of SNs as input(s) to the decompression of packets for the currently decoded SN in the sequence.

[0159] FIG. 8 is an example of a Packet Data Convergence Protocol (PDCP) control Protocol Data Unit (PDU) 800 including a flow control (FC) indication indicative of a request to stop Robust Header Compression (ROHC) decompression, in accordance with some examples. In one illustrative example, the PDCP control PDU 800 can be transmitted by a UE and / or by an ROHC decompressor to indicative a request to stop or pause compression being performed at the corresponding ROHC compression that transmits compressed packets to the UE for decompression (e.g., a network entity, base station, gNB. etc., including the corresponding ROHC compressor, etc.). In some cases, the PDCP control PDU 800 is indicative of a request for the network to stop compression of packets sent to the UE. For example, the request to stop compression can be used to implement flow control, where stopping compression allows the UE to avoid data stall and / or provides the UE with time to process a backlog or queue of packets awaiting decompression. In some cases, the UE can send the PDCP control PDU 800 indicative of the request to stop compression, based on the UE determining that the number of received compressed packets awaiting decompression (e.g., queued for decompression) is approaching a data stall limit, where the currently decoded compressed packet SNcurrently decodedis earlier than the currently received compressed packet SNcurrently receivedby a delta that exceeds a configured threshold for triggering the transmission of the PDCP control PDU 800 or other request from the UE to stop compression. For example, the UE may determine a risk of data stall in response to SNcurrentiy decoded « SNcurrentiy received, and / or mayPATENTQualcomm Docket No 2502422WO59determine a risk of data stall in response to SNcurrentiy received - SNcurrentiy decoded > threshold value.

[0160] In some cases, the PDCP control PDU 800 can include a Data / Control (DC) field 810, which can be provided on the most significant bit (MSB) of the first byte of the PDCP control PDU 800. The D / C field 810 can have a length of 1 -bit, and may indicate whether the PDCP 800 is a Data PDU or a Control PDU. Based on the PDCP control PDU 800 being a control PDU, the D / C field 810 can be set to a value of 0, indicative of the Control PDU flag.

[0161] The PDCP control PDU 800 can include a PDU type field 820, which may comprise the next 3 bits (e.g., after the D / C field 810 on the first bit) of the first byte in the PDU 800. The 3-bit PDU type field 820 may indicate the ty pe of control message carried by the PDCP control PDU 800. In one illustrative example, the systems and techniques can use a new PDU type as the indication within the 3-bit PDU type field 820. For example, the new PDU type indication in the 3-bit PDU type field 820 can be indicative of an ‘ROHC flow control’ PDU type, which can be configured as a PDU control message that may be carried to indicate a value of a Flow Control (FC) indication field 830 within the PDU 800. The PDCP control PDU 800 can include one or more reserved bits and / or fields. For example, the PDCP control PDU 800 may include a first reserved bit and / or field 840-1, a second reserved bit and / or field 840-2, a third reserved bit and / or field 840-3, etc.

[0162] In some aspects, the ‘ROHC flow control’ PDU type indicated as the 3-bit PDU type field 820 can comprise ‘100’ or other 3-bit values not assigned to existing PDU types. The presence of the 3-bit PDU type field 820 with value '100’ can indicate that the PDCP control PDU 800 includes the FC indication field 830 to indicate a first value (e.g., '1’) indicative of a flow control indication or request from the UE for the network to stop compression, or a second value (e.g., ‘0‘) indicative of a negative flow control indication or request from the UE (e.g., no request to stop compression, or an indication for the network to continue with compression).

[0163] The UE can trigger the transmission of the PDCP control PDU 800 with the PDU type field 820 set to ‘100’ and including the FC indication field 830 = 1 based on the UE determining, detecting, and / or identifying decompression issues at the UE that arePATENTQualcomm Docket No 2502422WO60causing or may cause data stall, etc. For example, the UE can trigger the transmission of the PDCP control PDU 800 with the PDU type field 820 set to ‘100’ and including the FC indication field 830 = 1 based on the UE determining a possible data stall, as noted above. For example, the UE may determine a risk of data stall in response to SNcurrentiy decoded « SNcurrently received, and / or may determine a risk of data stall in response to SNcunentiy received—SNcurrentiy decoded > threshold value. Based on receiving the PDCP control PDU 800 with the flow control indication from the UE with FC indication field 830 = 1, the network can stop compression for subsequently transmitted packets to the UE after the FC indication field 830 is received. In some cases, receiving the PDCP control PDU 800 with the FC indication field 830 = 1 from the UE can cause the network to stop compression at the ROHC compressor for a configured amount of time, with compression resuming after the pause interval (e.g., the configured amount of time) has elapsed. In another illustrative example, receiving the FC indication field 830 from the UE can cause the network to stop compression until, or unless, receiving a subsequent message from the UE indicative of a request to resume compression. For example, receiving the PDCP control PDU 800 with PDU type field 820 = ‘100’ and FC indication field 830 = ‘1’ can cause the network to stop compression at the ROHC compressor. The UE can transmit a request at a later time to resume compression based on the UE transmitting to the network another PDCP control PDU 800 with PDU type field 820 = ‘100’ and FC indication field 830 = ‘O’. Based on receiving the PDCP control PDU 800 with FC indication field 830 'O’, the network can cause the ROHC compressor to resume compression for packets transmitted to the UE.

[0164] FIG. 9 is a flowchart diagram illustrating an example of a process 900 for wireless communications. In some aspects, the process 900 can be a process for wireless communications by a network entity (e.g.. aUE, etc.). For example, the process 900 can be a process for wireless communications by a UE. In some examples, the process 900 can be performed by a network entity or network device (or apparatus) or a component (e.g., a chipset, codec, etc.) of the network entity7or device. The process 900 can be performed by one or more processors such as one or more CPUs, DSPs, NPUs, NSPs, microcontrollers. ASICs. FPGAs, programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc., any combination thereof, and / or other component or system) of the network entity or device or apparatus. The operations of the process 900 may be implemented as software components that are executed andPATENTQualcomm Docket No 2502422WO61run on one or more processors (e.g., processor 1010 and / or processing system 1002 of FIG. 10, or other processor(s)).

[0165] In some examples, the process 900 can be performed by a UE, including any of the various UEs described herein. In some aspects, the process 900 can be performed by a UE, smartphone, mobile computing device, user computer device, etc. The process 900 can be performed by a component or system (e.g., a chipset) of a network device (e.g., one or more of UEs 104. 152, 164, 182, 190 of FIG. 1; UE 104 of FIG. 2; UE(s) 104 of FIG. 3; wireless device 407 of FIG. 4; computing system 1000 and / or processing system 1002 of FIG. 10; etc ). The network device may be a mobile device (e g., a mobile phone), a network-connected wearable such as a watch, an extended reality (XR) device such as a virtual reality (VR) device or augmented reality (AR) device, a vehicle or component or system of a vehicle, or other type of computing device. The operations of the process 900 may be implemented as software components that are executed and run on one or more processors (e.g., the transmit processor 264, the receive processor 258, the TX MIMO processor 266, the MIMO detector 256 of FIG. 2, the processing system 470 of FIG. 4, the processor(s) 484 of FIG. 4, the processing system 1002 of FIG. 10, and / or the processor 1010 of FIG. 10, or other processor(s) (e.g., such as one or more other processors included within and / or associated with the processing system 470 of FIG. 4, the processing system 1002 of FIG. 10, etc.). Further, the transmission and reception of signals by the network entity in the process 900 may be enabled, for example, by one or more antennas, one or more transceivers (e.g., wireless transceiver(s)), and / or other communication components (e.g., the transmit processor 264, the receive processor 258, the TX MIMO processor 266, the MIMO detector 256, the modulator(s) / demodulator(s) 254a through 254t, and / or the antenna(es) 252a through 252t of FIG. 2, the antenna(es) 487 of FIG. 4, the wireless transceiver(s) 478 of FIG. 4, the communication interface 1040 of FIG. 10, or other antennae(s), transceiver(s), and / or components )).

[0166] At block 902, the apparatus (or component thereof) can obtain configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset. The interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven.PATENTQualcomm Docket No 2502422WO62

[0167] In some cases, the apparatus can be a UE. In some cases, the apparatus can be a network entity (e.g., base station, gNB, etc.). In some examples, the apparatus includes a processing system. To obtain the configuration information, the processing system may be configured to receive, from a network entity, signaling indicative of the configuration information. The signaling indicative of the configuration information can include at least a configured value for the offset parameter indicative of the interpretation interval offset. In some cases, the offset parameter indicative of the interpretation interval offset can correspond to the offset p, for example the offset p in the example of Table 1, etc. In some cases, the processing system can be configured to replace a value of the offset parameter in the ROHC compression profile with the configured value indicated by the signaling.

[0168] In some examples, the size parameter can be indicative of the number of compressed bits of packet header sequence number (SN) information included in a received data packet of a plurality of data packets. In some cases, to obtain the configuration information, the processing system can be configured to obtain a value of the offset parameter as a corresponding interpretation interval offset value mapped to the value of the size parameter. For example, the size parameter can correspond to the parameter k, for example the parameter k in the example of Table 1. etc. The value of the offset parameter can be obtained as the value of p mapped to a value of k based on the signaling.

[0169] In some examples, the value of the offset parameter can be mapped to the value of the size parameter based on information included in the ROHC compression profile. In some cases, the ROHC compression profile includes the configuration information. In some cases, each data packet of the plurality of data packets includes the number of compressed bits in the packet header field based on compression of each data packet according to the ROHC compression profile. In some examples, the interpretation interval offset included in the configuration information can be greater than or equal to four when the number of compressed bits is equal to seven. For example, the interpretation interval offset p can be greater than or equal to four (e.g., p ≥ 4) for values of the number of compressed bits k equal to seven f(e.g., p ≥ 4, for k = 7).

[0170] At block 904, the apparatus (or component thereof) can receive a plurality of data packets associated with a sequence. Each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or morePATENTQualcomm Docket No 2502422WO63out-of-order (000) data packets of the plurality of data packets are received out-of-order from the sequence.

[0171] In some examples, the plurality of data packets comprises a plurality of extended reality (XR) data packets associated with real-time XR traffic. In some cases, the plurality of data packets comprises a plurality of XR data packets associated with real-time XR traffic, where the real-time XR traffic includes one or more data packets corresponding to a User Datagram Protocol (UDP). In some cases, the apparatus (or component thereof) can be configured to obtain the configuration information including a positive integer value for the interpretation interval offset. For example, the configuration information can include the interpretation interval offset p, with a value of p ≥ 0. The apparatus (or component thereof) can be configured to use the positive integer value to replace a value of the offset parameter included in a configured ROHC compression profile associated with XR traffic, where the value of the offset parameter included in the configured ROHC compression profile associated with XR traffic is less than zero.

[0172] At block 906, the apparatus (or component thereof) can perform out-of-order delivery (GOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset. In some cases, to perform OOOD for the plurality of data packets, the apparatus (or component thereof) can be configured to use a packet data convergence protocol (PDCP) layer to perform PDCP OOOD for the plurality of data packets. In some examples, the plurality of data packets comprises a plurality of voice data packets associated with real-time voice traffic. In some cases, the plurality of data packets comprises at least one of: a plurality of voice data packets associated with real-time voice traffic or a plurality of video data packets associated with real-time video traffic. In some examples, the ROHC compression profile corresponds to Real-Time Transfer Protocol (RTP) for at least the real-time voice traffic.

[0173] In some aspects, the techniques described herein relate to an apparatus for wireless communication, including a processing system configured to: configure a plurality of contexts for a robust header compression (ROHC) bearer, where each context of the plurality of contexts is configured for a respective flow of a plurality of flows associated with data packet traffic. In some examples, a number of the plurality of contexts exceeds a configured maximum number of contexts.PATENTQualcomm Docket No 2502422WO64

[0174] In some cases, the processing system can determine an elapsed time from a last use of a respective context of the plurality of contexts exceeds a configured threshold amount of time. In some examples, the processing system can evict the respective context from the plurality of contexts for the ROHC bearer based on the elapsed time exceeding the configured threshold amount of time.

[0175] In some examples, the techniques described herein relate to an apparatus, wherein the processing system is configured to receive ROHC configuration information indicative of a per-flow configuration for the plurality of flows, the per-flow configuration corresponding to enabling or not enabling ROHC for the respective context configured for each flow of the plurality of flows. In some cases, the techniques described herein relate to an apparatus, wherein the processing system is configured to transmit signaling indicative of a first subset of flows of the plurality of flows. The signaling can include a request to use ROHC for the first subset of flows. The processing system can receive a respective plurality of data packets with compressed headers using ROHC for each flow of the first subset of flows.

[0176] In some examples, the techniques described herein relate to an apparatus, where the processing system is configured to receive a respective plurality of uncompressed data packets without using ROHC for each flow of a second subset of flows, where the plurality of flows includes the first subset and the second subset. In some cases, the techniques described herein relate to an apparatus, where the signaling is indicative of the first subset of flows based on the signaling including a quality of service (QoS) class identifier (QCI) associated with each flow of the first subset of flows.

[0177] In some examples, the techniques described herein relate to an apparatus, where the processing system is configured to transmit information indicative of a request for a network entity to stop compression associated with one or more flows of the plurality of flows associated with the real-time data packet traffic. Based on the request, the processing system can receive uncompressed data packets for each flow of the one or more flows corresponding to the request to stop compression.

[0178] In some cases, the techniques described herein relate to an apparatus, where, to transmit information indicative of the request to stop compression, the processing system is configured to transmit a packet data convergence protocol (PDCP) protocol data unitPATENTQualcomm Docket No 2502422WO65(PDU) indicative of the request for the network entity to stop compression. In some aspects, the PDCP PDU is a PDCP control PDU, and where the PDCP PDU includes a flow control indication field indicative of the request. In some cases, a first value of the flow control indication field indicates the request for the network entity to stop compression, and a second value of the flow control indication field indicates a request for the network entity to resume compression

[0179] In some examples, the processes described herein (e.g.. process 900 and / or other process described herein) may be performed by a computing device or apparatus (e.g.. a network node such as a UE, base station, a portion of a base station, etc.). For example, as noted above, the process 900 may be performed by a UE and / or network entity (e.g., base station, gNB, etc.). In some examples, the process 900 may be performed by a computing device with the computing system 1000 shown in FIG. 10. For example, a wireless communication device with the computing architecture shown in FIG. 10 may include the components of the UE and / or the network entity (e.g., base station, gNB, etc.) and may implement the operations of FIG. 9 and / or process 900, etc.

[0180] In some cases, the computing device or apparatus may include various components, such as one or more input devices, one or more output devices, one or more processors, one or more microprocessors, one or more microcomputers, one or more cameras, one or more sensors, and / or other component(s) that are configured to carry out the steps of processes described herein. In some examples, the computing device may include a display, one or more network interfaces configured to communicate and / or receive the data, any combination thereof, and / or other component(s). The one or more network interfaces may be configured to communicate and / or receive wired and / or wireless data, including data according to the 3G, 4G, 5G, and / or other cellular standard, data according to the WiFi (802.1 lx) standards, data according to the Bluetooth™ standard, data according to the Internet Protocol (IP) standard, and / or other types of data.

[0181] The components of the computing device may be implemented in circuitry. For example, the components may include and / or may be implemented using electronic circuits or other electronic hardware, which may include one or more programmable electronic circuits (e.g., microprocessors, graphics processing units (GPUs), digital signal processors (DSPs), central processing units (CPUs), and / or other suitable electronicPATENTQualcomm Docket No 2502422WO66circuits), and / or may include and / or be implemented using computer software, firmware, or any combination thereof, to perform the various operations described herein.

[0182] The process 900 is illustrated as a logical flow diagram, the operation of which represents a sequence of operations that may be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations may be combined in any order and / or in parallel to implement the processes.

[0183] Additionally, the process 900 and / or other process described herein may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware, or combinations thereof. As noted above, the code may be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non-transitory.

[0184] FIG. 10 is a diagram illustrating an example of a system for implementing certain aspects of the present technology. In particular, FIG. 10 illustrates an example of computing system 1000 including a processing system 1002, which may be for example any computing device making up internal computing system, a remote computing system, a camera, or any component thereof in which the components of the system are in communication with each other using connection 1005. Connection 1005 may be a physical connection using a bus, or a direct connection into processor 1010 (and / or one or more other processors included within and / or associated with the processing system 1002), such as in a chipset architecture. Connection 1005 may also be a virtual connection, networked connection, or logical connection.PATENTQualcomm Docket No 2502422WO67

[0185] In some aspects, computing system 1000 and / or the processing system 1002 can be provided as a distributed system in which the functions described in this disclosure may be distributed within a datacenter, multiple data centers, a peer network, etc. In some aspects, one or more of the described system components represents many such components each performing some or all of the function for which the component is described. In some aspects, the components may be physical or virtual devices.

[0186] The example processing system 1002 includes at least one processing unit (CPU or processor) 1010 and connection 1005 that communicatively couples various system components including system memory 1015, such as read-only memory (ROM) 1020 and random access memory’ (RAM) 1025 to processor 1010. The processing system 1002 may include a cache 1012 of high-speed memory connected directly with, in close proximity to, or integrated as part of processor 1010 and / or one or more other processors included within and / or associated with the processing system 1002.

[0187] Processor 1010 may include any general-purpose processor and a hardware service or software service, such as services 1032, 1034, and 1036 stored in storage device 1030, configured to control processor 1010 and / or one or more other processors included within and / or associated with the processing system 1002, as well as a special -purpose processor where software instructions are incorporated into the actual processor design. Processor 1010 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multicore processor may be symmetric or asymmetric.

[0188] To enable user interaction, processing system 1002 includes an input device 1045, which may represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc. Processing system 1002 may also include output device 1035, which may be one or more of a number of output mechanisms. In some examples, multimodal systems may enable a user to provide multiple types of input / output to communicate with processing system 1002.

[0189] Processing system 1002 may include communications interface 1040, which may generally govern and manage the user input and system output. The communication interface may perform or facilitate receipt and / or transmission wired or wirelessPATENTQualcomm Docket No 2502422WO68communications using wired and / or wireless transceivers, including those making use of an audio jack / plug, a microphone jack / plug, a universal serial bus (USB) port / plug, an Apple™ Lightning™ port / plug, an Ethernet port / plug, a fiber optic port / plug, a proprietary wired port / plug, 3G, 4G, 5G and / or other cellular data network wireless signal transfer, a Bluetooth™ wireless signal transfer, a Bluetooth™ low energy (BLE) wireless signal transfer, an IBEACON™ wireless signal transfer, a radio-frequency identification (RFID) wireless signal transfer, near-field communications (NFC) wireless signal transfer, dedicated short range communication (DSRC) wireless signal transfer, 802.11 Wi-Fi wireless signal transfer, wireless local area network (WLAN) signal transfer, Visible Light Communication (VLC), Worldwide Interoperability' for Microwave Access (WiMAX), Infrared (IR) communication wireless signal transfer, Public Switched Telephone Network (PSTN) signal transfer, Integrated Services Digital Network (ISDN) signal transfer, ad-hoc network signal transfer, radio wave signal transfer, microwave signal transfer, infrared signal transfer, visible light signal transfer, ultraviolet light signal transfer, wireless signal transfer along the electromagnetic spectrum, or some combination thereof. The communications interface 1040 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers that are used to determine a location of the computing system 1000 based on receipt of one or more signals from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the US-based Global Positioning System (GPS), the Russia-based Global Navigation Satellite System (GLONASS), the China-based BeiDou Navigation Satellite System (BDS), and the Europe-based Galileo GNSS. There is no restriction on operating on any particular hardware arrangement, and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

[0190] Storage device 1030 may be a non-volatile and / or non-transitory and / or computer-readable memory device and may be a hard disk or other types of computer readable media which may store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, a floppy disk, a flexible disk, a hard disk, magnetic tape, a magnetic strip / stripe, any other magnetic storage medium, flash memory, memristor memory, any other solid-state memory', a compact disc read only memory (CD-ROM) optical disc, a rewritable compact disc (CD) optical disc, digital video disk (DVD) optical disc, a blu-PATENTQualcomm Docket No 2502422WO69ray disc (BDD) optical disc, a holographic optical disk, another optical medium, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Stick® card, a smartcard chip, a Europay, Mastercard, and Visa (EMV) chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, another integrated circuit (IC) chip / card, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash EPROM (FLASHEPROM), cache memory (e.g., Level 1 (LI) cache, Level 2 (L2) cache, Level 3 (L3) cache, Level 4 (L4) cache, Level 5 (L5) cache, or other (L#) cache), resistive random-access memory (RRAM / ReRAM), phase change memory (PCM), spin transfer torque RAM (STT-RAM), another memory chip or cartridge, and / or a combination thereof.

[0191] The storage device 1030 may include software services, servers, services, etc., that when the code that defines such software is executed by the processor 1010 and / or one or more other processors included within and / or associated with the processing system 1002. it causes the system to perform a function. In some aspects, a hardware service that performs a particular function may include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 1010 (e.g., and / or one or more other processors included within and / or associated with the processing system 1002), connection 1005, output device 1035, etc., to carry’ out the function. The term ‘“computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other mediums capable of storing, containing, or carry ing instruct! on(s) and / or data. A computer-readable medium may include a non-transitory medium in which data may be stored and that does not include carrier waves and / or transitory electronic signals propagating wirelessly or over wired connections. Examples of a non-transitory medium may include, but are not limited to, a magnetic disk or tape, optical storage media such as compact disk (CD) or digital versatile disk (DVD), flash memory, memory’ or memory' devices. A computer-readable medium may have stored thereon code and / or machineexecutable instructions that may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receivingPATENTQualcomm Docket No 2502422WO70information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc., may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, or the like.

[0192] Specific details are provided in the description above to provide a thorough understanding of the aspects and examples provided herein, but those skilled in the art will recognize that the application is not limited thereto. Thus, while illustrative aspects of the application have been described in detail herein, it is to be understood that the inventive concepts may be otherwise variously embodied and employed, and that the appended claims are intended to be construed to include such variations, except as limited by the prior art. Various features and aspects of the above-described application may be used individually or jointly. Further, aspects may be utilized in any number of environments and applications beyond those described herein without departing from the broader scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive. For the purposes of illustration, methods were described in a particular order. It should be appreciated that in alternate aspects, the methods may be performed in a different order than that described.

[0193] For clarity of explanation, in some examples the present technology may be presented as including individual functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software. Additional components may be used other than those shown in the figures and / or described herein. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the aspects in unnecessary detail. In other examples, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the aspects.

[0194] Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality isPATENTQualcomm Docket No 2502422WO71implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0195] Individual aspects may be described above as a process or method which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

[0196] Processes and methods according to the above-described examples may be implemented using computer-executable instructions that are stored or otherwise available from computer-readable media. Such instructions may include, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or a processing device to perform a certain function or group of functions. Portions of computer resources used may be accessible over a netw ork. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, source code. Examples of computer-readable media that may be used to store instructions, information used, and / or information created during methods according to described examples include magnetic or optical disks, flash memory. USB devices provided with non-volatile memory, networked storage devices, and so on.

[0197] In some aspects the computer-readable storage devices, mediums, and memories may include a cable or wireless signal containing a bitstream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

[0198] Those of skill in the art will appreciate that information and signals may bePATENTQualcomm Docket No 2502422WO72represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, in some cases depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

[0199] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and may take any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-program product) may be stored in a computer-readable or machine-readable medium. Aprocessor(s) may perform the necessary tasks. Examples of form factors include laptops, smart phones, mobile phones, tablet devices or other small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also may be embodied in peripherals or add-in cards. Such functionality may also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

[0200] The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are example means for providing the functions described in the disclosure.

[0201] The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of a variety of devices such as general purposes computers, wireless communication device handsets, or integrated circuit devices having multiple uses including application in wireless communication device handsets and other devices. Any features described as modules or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques may be realized at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, performs one or more of the methods, algorithms, and / or operations describedPATENTQualcomm Docket No 2502422WO73above. The computer-readable data storage medium may form part of a computer program product, which may include packaging materials. The computer-readable medium may comprise memory or data storage media, such as random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, and the like. The techniques additionally, or alternatively, may be realized at least in part by a computer-readable communication medium that carries or communicates program code in the form of instructions or data structures and that may be accessed, read, and / or executed by a computer, such as propagated signals or waves.

[0202] The program code may be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, an application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Such a processor may be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor; but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality7of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Accordingly, the term 'processor." as used herein may refer to any of the foregoing structure, any combination of the foregoing structure, or any other structure or apparatus suitable for implementation of the techniques described herein.

[0203] One of ordinary skill will appreciate that the less than (“<”) and greater than (“>”) symbols or terminology used herein may be replaced with less than or equal to (“<”) and greater than or equal to (“>”) symbols, respectively, without departing from the scope of this description.

[0204] Where components are described as being ‘'configured to” perform certain operations, such configuration may be accomplished, for example, by designing electronic circuits or other hardware to perform the operation, by programming programmable electronic circuits (e.g.. microprocessors, or other suitable electronic circuits) to perform the operation, or any combination thereof.PATENTQualcomm Docket No 2502422WO74

[0205] The phrase “coupled to” or “communicatively coupled to” refers to any component that is physically connected to another component either directly or indirectly, and / or any component that is in communication with another component (e.g., connected to the other component over a wired or wireless connection, and / or other suitable communication interface) either directly or indirectly.

[0206] Claim language or other language reciting “at least one of’ a set and / or “one or more” of a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, claim language reciting “at least one of A and B” or “at least one of A or B” means A, B, or A and B. In another example, claim language reciting “at least one of A, B, and C” or “at least one of A, B, or C” means A, B, C, or A and B, or A and C, or B and C, A and B and C, or any duplicate information or data (e.g., A and A. B and B. C and C. A and A and B, and so on), or any other ordering, duplication, or combination of A, B, and C. The language “at least one of’ a set and / or “one or more” of a set does not limit the set to the items listed in the set. For example, claim language reciting “at least one of A and B” or “at least one of A or B” may mean A, B, or A and B, and may additionally include items not listed in the set of A and B.

[0207] Claim language or other language reciting “at least one processor configured to,” “at least one processor being configured to,” or the like indicates that one processor or multiple processors (in any combination) can perform the associated operation(s). For example, claim language reciting “at least one processor configured to: X, Y, and Z” means a single processor can be used to perform operations X, Y, and Z; or that multiple processors are each tasked with a certain subset of operations X, Y and Z such that together the multiple processors perform X, Y, and Z; or that a group of multiple processors work together to perform operations X, Y, and Z. In another example, claim language reciting “at least one processor configured to: X, Y, and Z” can mean that any single processor may only perform at least a subset of operations X, Y, and Z.

[0208] Where reference is made to one or more elements performing functions (e.g.. steps of a method), one element may perform all functions, or more than one element may collectively perform the functions. When more than one element collectively performs the functions, each function need not be performed by each of those elements (e.g., different functions may be performed by different elements) and / or each function need not be performed in whole by only one element (e.g., different elements may performPATENTQualcomm Docket No 2502422WO75different sub-functions of a function). Similarly, where reference is made to one or more elements configured to cause another element (e.g.. an apparatus) to perform functions, one element may be configured to cause the other element to perform all functions, or more than one element may collectively be configured to cause the other element to perform the functions.

[0209] Where reference is made to an entity (e.g., any entity or device described herein) performing functions or being configured to perform functions (e.g., steps of a method), the entity may be configured to cause one or more elements (individually or collectively) to perform the functions. The one or more components of the entity’ may include at least one memory, at least one processor, at least one communication interface, another component configured to perform one or more (or all) of the functions, and / or any combination thereof. Where reference to the entity performing functions, the entity may be configured to cause one component to perform all functions, or to cause more than one component to collectively perform the functions. When the entity’ is configured to cause more than one component to collectively perform the functions, each function need not be performed by each of those components (e.g., different functions may be performed by different components) and / or each function need not be performed in whole by only one component (e.g., different components may perform different sub-functions of a function).

[0210] Illustrative aspects of the disclosure include:

[0211] Aspect 1. An apparatus for wireless communication, comprising: a processing system configured to: obtain configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven; receive a plurality of data packets associated with a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality of data packets are received out-of-order from the sequence; and perform out-of-order delivery (OOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.PATENTQualcomm Docket No 2502422WO76

[0212] Aspect 2. The apparatus of Aspect 1, wherein, to obtain the configuration information, the processing system is configured to: receive, from a network entity, signaling indicative of the configuration information and including at least a configured value for the offset parameter, wherein the processing system is configured to replace a value of the offset parameter in the ROHC compression profile with the configured value indicated by the signaling.

[0213] Aspect 3. The apparatus of any of Aspects 1 to 2, wherein: the size parameter is indicative of the number of compressed bits of packet header sequence number (SN) information included in a received data packet of the plurality of data packets; and to obtain the configuration information, the processing system is configured to determine a value of obtain a value of the offset parameter as a corresponding interpretation interval offset value mapped to the value of the size parameter.

[0214] Aspect 4. The apparatus of Aspect 3, wherein the value of the offset parameter is mapped to the value of the size parameter based on information included in the ROHC compression profile.

[0215] Aspect 5. The apparatus of Aspect 4, wherein the ROHC compression profile includes the configuration information, and wherein each data packet of the plurality of data packets includes the number of compressed bits in the packet header field based on compression of each data packet according to the ROHC compression profile.

[0216] Aspect 6. The apparatus of any of Aspects 1 to 5, wherein the interpretation interval offset included in the configuration information is greater than or equal to four when the number of compressed bits is equal to seven.

[0217] Aspect 7. The apparatus of any of Aspects 1 to 6, wherein, to perform OOOD for the plurality of data packets, the processing system is configured to use a packet data convergence protocol (PDCP) layer to perform PDCP OOOD for the plurality of data packets.

[0218] Aspect 8. The apparatus of any of Aspects 1 to 7, wherein the plurality of data packets comprises at least one of: a plurality of voice data packets associated with realtime voice traffic or a plurality of video data packets associated with real-time video traffic, and wherein the ROHC compression profile corresponds to Real-Time Transfer Protocol (RTP) for at least the real-time voice traffic.PATENTQualcomm Docket No 2502422WO77

[0219] Aspect 9. The apparatus of any of Aspects 1 to 8, wherein the plurality of data packets comprises a plurality of extended reality (XR) data packets associated with realtime XR traffic, the real-time XR traffic including one or more data packets corresponding to a User Datagram Protocol (UDP), and wherein the processing system is configured to: obtain the configuration information including a positive integer value for the interpretation interval offset; and use the positive integer value to replace a value of the offset parameter included in a configured ROHC compression profile associated with XR traffic, wherein the value of the offset parameter included in the configured ROHC compression profile associated with XR traffic is less than zero.

[0220] Aspect 10. An apparatus for wireless communication, comprising: a processing system configured to: configure a plurality of contexts for a robust header compression (ROHC) bearer, wherein each context of the plurality of contexts is configured for a respective flow of a plurality of flows associated with data packet traffic, and wherein a number of the plurality7of contexts exceeds a configured maximum number of contexts; determine an elapsed time from a last use of a respective context of the plurality of contexts exceeds a configured threshold amount of time; and evict the respective context from the plurality of contexts for the ROHC bearer based on the elapsed time exceeding the configured threshold amount of time.

[0221] Aspect 11. The apparatus of Aspect 10, wherein the processing system is configured to: receive ROHC configuration information indicative of a per-flow configuration for the plurality of flows, the per-flow configuration corresponding to enabling or not enabling ROHC for the respective context configured for each flow of the plurality of flows.

[0222] Aspect 12. The apparatus of Aspect 11, wherein the processing system is configured to: transmit signaling indicative of a first subset of flows of the plurality of flows, wherein the signaling comprises a request to use ROHC for the first subset of flows; and receive a respective plurality of data packets with compressed headers using ROHC for each flow of the first subset of flows.

[0223] Aspect 13. The apparatus of Aspect 12, wherein the processing system is configured to receive a respective plurality of uncompressed data packets without usingPATENTQualcomm Docket No 2502422WO78ROHC for each flow of a second subset of flows, wherein the plurality of flows comprises the first subset and the second subset.

[0224] Aspect 14. The apparatus of any of Aspects 12 to 13, wherein the signaling is indicative of the first subset of flows based on the signaling including a quality of service (QoS) class identifier (QCI) associated with each flow of the first subset of flows.

[0225] Aspect 15. The apparatus of any of Aspects 10 to 14, wherein the processing system is configured to: transmit information indicative of a request for a network entity to stop compression associated with one or more flows of the plurality of flows associated with the real-time data packet traffic; and receive uncompressed data packets for each flow of the one or more flows corresponding to the request to stop compression.

[0226] Aspect 16. The apparatus of Aspect 15, wherein, to transmit information indicative of the request to stop compression, the processing system is configured to: transmit a packet data convergence protocol (PDCP) protocol data unit (PDU) indicative of the request for the network entity to stop compression.

[0227] Aspect 17. The apparatus of Aspect 16, wherein the PDCP PDU is a PDCP control PDU, and wherein the PDCP PDU includes a How control indication field indicative of the request.

[0228] Aspect 18. The apparatus of Aspect 17, w herein a first value of the flow control indication field indicates the request for the network entity to stop compression, and wherein a second value of the flow control indication field indicates a request for the network entity to resume compression.

[0229] Aspect 19. A method of wireless communication, comprising: obtaining configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven; receiving a plurality of data packets associated with a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality7of data packets are received out-of-order from the sequence; and performing out-of-order delivery (GOOD) for thePATENTQualcomm Docket No 2502422WO79plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.

[0230] Aspect 20. The method of Aspect 19, wherein obtaining the configuration information comprises: receiving, from a network entity, signaling indicative of the configuration information and including at least a configured value for the offset parameter, wherein a value of the offset parameter in the ROHC compression profile is replaced with the configured value indicated by the signaling.

[0231] Aspect 21. The method of any of Aspects 19 to 20, wherein: the size parameter is indicative of the number of compressed bits of packet header sequence number (SN) information included in a received data packet of the plurality of data packets; and obtaining the configuration information includes obtaining a value of the offset parameter as a corresponding interpretation interval offset value mapped to the value of the size parameter.

[0232] Aspect 22. The method of Aspect 21, wherein the value of the offset parameter is mapped to the value of the size parameter based on information included in the ROHC compression profile.

[0233] Aspect 23. The method of Aspect 22, wherein the ROHC compression profile includes the configuration information, and wherein each data packet of the plurality of data packets includes the number of compressed bits in the packet header field based on compression of each data packet according to the ROHC compression profile..

[0234] Aspect 24. The method of any of Aspects 19 to 23, wherein the interpretation interval offset included in the configuration information is greater than or equal to four when the number of compressed bits is equal to seven.

[0235] Aspect 25. The method of any of Aspects 19 to 24, wherein performing OOOD for the plurality of data packets is based on using a packet data convergence protocol (PDCP) layer to perform PDCP OOOD for the plurality of data packets.

[0236] Aspect 26. The method of any of Aspects 19 to 25, wherein the plurality of data packets comprises at least one of: a plurality of voice data packets associated with realtime voice traffic or a plurality of video data packets associated with real-time videoPATENTQualcomm Docket No 2502422WO80traffic, and wherein the ROHC compression profile corresponds to Real-Time Transfer Protocol (RTP) for at least the real-time voice traffic.

[0237] Aspect 27. The method of any of Aspects 19 to 26. wherein the plurality of data packets comprises a plurality of extended reality (XR) data packets associated with realtime XR traffic, the real-time XR traffic including one or more data packets corresponding to a User Datagram Protocol (UDP), and wherein the processing system is configured to: obtain the configuration information including a positive integer value for the interpretation interval offset; and use the positive integer value to replace a value of the offset parameter included in a configured ROHC compression profile associated with XR traffic, wherein the value of the offset parameter included in the configured ROHC compression profile associated with XR traffic is less than zero.

[0238] Aspect 28. A method for wireless communication, comprising: configuring a plurality of contexts for a robust header compression (ROHC) bearer, wherein each context of the plurality of contexts is configured for a respective flow of a plurality of flows associated with data packet traffic, and wherein a number of the plurality of contexts is less than or equal to a configured maximum number of contexts; determining an elapsed time from a last use of a respective context of the plurality of contexts exceeds a configured threshold amount of time; and evicting the respective context from the plurality of contexts for the ROHC bearer based on the elapsed time exceeding the configured threshold amount of time.

[0239] Aspect 29. The method of Aspect 28, further comprising: receiving ROHC configuration information indicative of a per-flow configuration for the plurality of flows, the per-flow configuration corresponding to enabling or not enabling ROHC for the respective context configured for each flow of the plurality of flows.

[0240] Aspect 30. The method of Aspect 29, further comprising: transmitting signaling indicative of a first subset of flows of the plurality of flows, wherein the signaling comprises a request to use ROHC for the first subset of flows; and receiving a respective plurality of data packets with compressed headers using ROHC for each flow of the first subset of flows.

[0241] Aspect 31. The method of Aspect 30, further comprising receiving a respective plurality7of uncompressed data packets without using ROHC for each flow of a secondPATENTQualcomm Docket No 2502422WO81subset of flows, wherein the plurality of flows comprises the first subset and the second subset.

[0242] Aspect 32. The method of any of Aspects 30 to 31, wherein the signaling is indicative of the first subset of flows based on the signaling including a quality of service (QoS) class identifier (QCI) associated with each flow of the first subset of flows.

[0243] Aspect 33. The method of any of Aspects 28 to 32, further comprising: transmitting information indicative of a request for a network entity to stop compression associated with one or more flows of the plurality of flows associated with the real-time data packet traffic; and receiving uncompressed data packets for each flow of the one or more flows corresponding to the request to stop compression.

[0244] Aspect 34. The method of Aspect 33, wherein transmitting information indicative of the request to stop compression comprises: transmitting a packet data convergence protocol (PDCP) protocol data unit (PDU) indicative of the request for the network entity to stop compression.

[0245] Aspect 35. The method of Aspect 34, wherein the PDCP PDU is a PDCP control PDU, and wherein the PDCP PDU includes a flow control indication field indicative of the request.

[0246] Aspect 36. The method of Aspect 35, wherein a first value of the flow control indication field indicates the request for the network entity to stop compression, and wherein a second value of the flow control indication field indicates a request for the network entity to resume compression.

[0247] Aspect 37. A non-transitory computer-readable storage medium comprising instructions stored thereon which, when executed by at least one processor, causes the at least one processor to perform operations according to any of Aspects 1 to 9.

[0248] Aspect 38. An apparatus for wireless communication comprising one or more means for performing operations according to any of Aspects 1 to 9.

[0249] Aspect 39. A non-transitory computer-readable storage medium comprising instructions stored thereon which, when executed by at least one processor, causes the at least one processor to perform operations according to any of Aspects 10 to 18.PATENTQualcomm Docket No 2502422WO82

[0250] Aspect 40. An apparatus for wireless communication comprising one or more means for performing operations according to any of Aspects 10 to 18.

Claims

PATENTQualcomm Docket No 2502422WO83CLAIMSWhat is claimed is:

1. An apparatus for wireless communication, comprising:a processing system configured to:obtain configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven;receive a plurality of data packets associated with a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in a packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality of data packets are received out-of-order from the sequence; andperform out-of-order delivery (GOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.

2. The apparatus of claim 1, wherein, to obtain the configuration information, the processing system is configured to:receive, from a network entity, signaling indicative of the configuration information and including at least a configured value for the offset parameter, wherein the processing system is configured to replace a value of the offset parameter in the ROHC compression profile with the configured value indicated by the signaling.

3. The apparatus of claim 1, wherein:the size parameter is indicative of the number of compressed bits of packet header sequence number (SN) information included in a received data packet of the plurality of data packets; andto obtain the configuration information, the processing system is configured to obtain a value of the offset parameter as a corresponding interpretation interval offset value mapped to the value of the size parameter.PATENTQualcomm Docket No 2502422WO844. The apparatus of claim 3, wherein the value of the offset parameter is mapped to the value of the size parameter based on information included in the ROHC compression profile.

5. The apparatus of claim 4, wherein the ROHC compression profile includes the configuration information, and wherein each data packet of the plurality of data packets includes the number of compressed bits in the packet header field based on compression of each data packet according to the ROHC compression profile.

6. The apparatus of claim 1, wherein the interpretation interval offset included in the configuration information is greater than or equal to four when the number of compressed bits is equal to seven.

7. The apparatus of claim 1, wherein, to perform OOOD for the plurality of data packets, the processing system is configured to use a packet data convergence protocol (PDCP) layer to perform PDCP OOOD for the plurality of data packets.

8. The apparatus of claim 1, wherein the plurality of data packets comprises at least one of: a plurality of voice data packets associated with real-time voice traffic or a plurality of video data packets associated with real-time video traffic, and wherein the ROHC compression profile corresponds to Real-Time Transfer Protocol (RTP) for at least the real-time voice traffic.

9. The apparatus of claim 1, wherein the plurality of data packets comprises a plurality of extended reality (XR) data packets associated with real-time XR traffic, the real-time XR traffic including one or more data packets corresponding to a User Datagram Protocol (UDP), and wherein the processing system is configured to:obtain the configuration information including a positive integer value for the interpretation interval offset; anduse the positive integer value to replace a value of the offset parameter included in a configured ROHC compression profile associated with XR traffic, wherein the value of the offset parameter included in the configured ROHC compression profile associated with XR traffic is less than zero.PATENTQualcomm Docket No 2502422WO8510. An apparatus for wireless communication, comprising:a processing system configured to:configure a plurality of contexts for a robust header compression (ROHC) bearer, wherein each context of the plurality of contexts is configured for a respective flow of a plurality of flows associated with data packet traffic, and wherein a number of the plurality of contexts exceeds a configured maximum number of contexts;determine an elapsed time from a last use of a respective context of the plurality of contexts exceeds a configured threshold amount of time; and evict the respective context from the plurality of contexts for the ROHC bearer based on the elapsed time exceeding the configured threshold amount of time.

11. The apparatus of claim 10, wherein the processing system is configured to: receive ROHC configuration information indicative of a per-flow configuration for the plurality of flows, the per-flow configuration corresponding to enabling or not enabling ROHC for the respective context configured for each flow of the plurality of flows.

12. The apparatus of claim 11, wherein the processing system is configured to: transmit signaling indicative of a first subset of flows of the plurality of flows, wherein the signaling comprises a request to use ROHC for the first subset of flows; and receive a respective plurality of data packets with compressed headers using ROHC for each flow of the first subset of flows.

13. The apparatus of claim 12, wherein the processing system is configured to receive a respective plurality of uncompressed data packets without using ROHC for each flow of a second subset of flows, wherein the plurality of flows comprises the first subset and the second subset.PATENTQualcomm Docket No 2502422WO8614. The apparatus of claim 12, wherein the signaling is indicative of the first subset of flows based on the signaling including a quality of service (QoS) class identifier (QCI) associated with each flow of the first subset of flows.

15. The apparatus of claim 10, wherein the processing system is configured to: transmit information indicative of a request for a network entity to stop compression associated with one or more flows of the plurality of flows associated with the data packet traffic; andreceive uncompressed data packets for each flow of the one or more flows corresponding to the request to stop compression.

16. The apparatus of claim 15. wherein, to transmit information indicative of the request to stop compression, the processing system is configured to:transmit a packet data convergence protocol (PDCP) protocol data unit (PDU) indicative of the request for the network entity to stop compression.

17. The apparatus of claim 16, wherein the PDCP PDU is a PDCP control PDU, and wherein the PDCP PDU includes a flow control indication field indicative of the request.

18. The apparatus of claim 17, wherein a first value of the flow control indication field indicates the request for the network entity to stop compression, and wherein a second value of the flow control indication field indicates a request for the network entity to resume compression.

19. A method of wireless communication, comprising:obtaining configuration information corresponding to a robust header compression (ROHC) compression profile, the configuration information including a size parameter indicative of a number of compressed bits and an offset parameter indicative of an interpretation interval offset, wherein the interpretation interval offset is greater than or equal to two when the number of compressed bits is less than seven; receiving a plurality of data packets associated with a sequence, wherein each data packet of the plurality of data packets includes the number of compressed bits in aPATENTQualcomm Docket No 2502422WO87packet header field, and wherein one or more out-of-order (OOO) data packets of the plurality of data packets are received out-of-order from the sequence; and performing out-of-order delivery (OOOD) for the plurality of data packets based on a maximum packet reordering depth equal to the interpretation interval offset.

20. The method of claim 19, wherein obtaining the configuration information comprises:receiving, from a network entity, signaling indicative of the configuration information and including at least a configured value for the offset parameter, wherein a value of the offset parameter in the ROHC compression profile is replaced with the configured value indicated by the signaling.

Images