Drop timer enhancements for augmented reality communications

Abstract

Aspects of the present disclosure relate to an apparatus for drop timer augmentation for augmented reality communications. The apparatus receives a first signaling as a configuration from a radio access network (RAN). The configuration indicates a plurality of timer configuration sets for a plurality of importance levels. The apparatus applies a first set of timer configurations of the plurality of sets for data of the radio bearer. The apparatus applies a second timer configuration set of the plurality of sets for the data of the radio bearer in response to receiving the message from the RAN.

Description

Cross Reference to Related Applications

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 494,082, filed April 4, 2023, entitled “Discard Timer Enhancements for Extended Reality Communications,” the entirety of which is incorporated by reference herein. TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to extended reality communications. BACKGROUND

[0003] A wireless communication system can include one or more network communication devices (such as base stations), which can be referred to as eNodeBs (eNBs), next generation NodeBs (gNBs), or other suitable terminology. Each network communication device (such as a base station) can support wireless communication for one or more user communication devices, which can also be referred to as user equipment (UE) or other suitable terminology. A wireless communication system can support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system, such as time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). Moreover, a wireless communication system can support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0004] In a wireless communication system, extended reality (XR) use cases are associated with certain network requirements and / or communication traffic. XR is a general term for different types of human-machine interactions generated by computer technology, such as virtual reality (VR), augmented reality (AR), and / or mixed reality (MR). SUMMARY

[0005] The present disclosure relates to methods, apparatuses, and systems that support discard timer enhancements for XR communications. The described techniques enable wireless communication systems to avoid or reduce congestion associated with XR communications over the air interface (e.g., for uplink (UL) transmissions), for example, by configuring multiple packet data convergence protocol (PDCP) discard timer configurations for different importance levels of different protocol data units (PDUs) and / or PDU sets. For example, a quality of service (QoS) flow and / or radio bearer for XR traffic can carry PDU sets with different importance levels (e.g., intra-coded pictures (I-frames) and predicted pictures (P-frames) of a video stream). Accordingly, aspects of the present disclosure relate to differentiated handling of PDU sets based on importance. For example, for data with a higher importance level, a different discard timer configuration can be applied than for data with a lower importance level. As another example, during a congestion period, the system can prioritize high importance data while discarding low importance data.

[0006] By adjusting discard timer configurations based on importance levels and / or network conditions, a communication device can experience improved user experience, low latency, and / or high reliability for wireless communications, particularly with respect to use cases such as XR communications and / or other types of high throughput data communications (e.g., video and / or audio streaming).

[0007] In some implementations of the method and apparatuses described herein, a UE receives, from a radio access network (RAN), first signaling as a configuration indicating a plurality of sets of timer configurations for a plurality of importance levels; applies, for data of a radio bearer, a first set of timer configurations of the plurality of sets of timer configurations; and in response to receiving a message from the RAN, applies, for the data of the radio bearer, a second set of timer configurations of the plurality of sets of timer configurations.

[0008] Some implementations of the methods and apparatuses described in this document can also include that the first set of timer configurations includes a respective timer configuration for each of the plurality of importance levels. Additionally or alternatively, the second set of timer configurations includes a respective timer configuration for each of the plurality of importance levels. Additionally or alternatively, the UE stores data for a radio bearer for transmission. Additionally or alternatively, the data is associated with the plurality of importance levels. Additionally or alternatively, the UE receives the second signaling from the RAN as a message. Additionally or alternatively, the message includes a congestion indication. Additionally or alternatively, the UE starts the timer in response to receiving data for the radio bearer from an upper layer. Additionally or alternatively, the UE sets a timer value for the timer according to the first set of timer configurations based on the data received from the upper layer being associated with a first importance level. Additionally or alternatively, the UE sets the timer value for the timer according to the second set of timer configurations based on the data received from the upper layer being associated with a second importance level. Additionally or alternatively, the UE restarts the timer in response to receiving the message from the RAN.

[0009] In some implementations of the methods and apparatuses described in this document, the base station transmits first signaling to the UE as a configuration indicating a plurality of sets of timer configurations for a plurality of importance levels; and transmits second signaling to the UE as a message including a congestion indication.

[0010] Some implementations of the methods and apparatuses described in this document can also include that the first set of timer configurations includes a respective timer configuration for each of the plurality of importance levels. Additionally or alternatively, the second set of timer configurations includes a respective timer configuration for each of the plurality of importance levels. Additionally or alternatively, the set of timer configurations includes a first timer configuration indicating a first timer value for transmission of data for a radio bearer of the UE according to a first importance level. Additionally or alternatively, the set of timer configurations includes a second timer configuration indicating a second timer value for transmission of data for the radio bearer of the UE according to a second importance level. BRIEF DESCRIPTION OF DRAWINGS

[0011] Figure 1 FIG. 1 illustrates an example of a wireless communications system that supports discard timer enhancements for XR communications in accordance with aspects of the present disclosure.

[0012] Figure 2 FIG. 1 illustrates an example of a wireless communications system that supports discard timer enhancements for XR communications in accordance with aspects of the present disclosure.

[0013] Figure 3FIG. illustrates an example of alternative mapping of lower layer processing for XR communication related to discard timer enhancements for XR communication according to aspects of the present disclosure.

[0014] Figure 4A and Figure 4B are example implementations (e.g., ASN-1 code) according to aspects of the present disclosure that include information about multiple PDCP discard timer configurations for supported PSI levels for a PDCP entity (e.g., DiscardTimerExt3-r18 ) that support discard timer enhancements for XR communication.

[0015] Figure 5 FIG. illustrates an example of processing PDUs to be transmitted in a UE that supports discard timer enhancements for XR communication according to aspects of the present disclosure.

[0016] Figure 6 and Figure 7 FIG. illustrates an example of a block diagram of a device that supports discard timer enhancements for XR communication according to aspects of the present disclosure.

[0017] Figures 8 to 10 FIG. illustrates a flow diagram of a method that supports discard timer enhancements for XR communication according to aspects of the present disclosure. DETAILED DESCRIPTION

[0018] In wireless communication systems, QoS flows and / or radio bearers for XR traffic can carry sets of PDUs with different importance levels (e.g., I-frames and P-frames of a video stream). According to conventional QoS architectures, all data packets of a radio bearer typically receive the same QoS treatment. For example, even though there can be PDUs / sets of PDUs associated with different importance levels, a UE can treat all PDUs of a logical channel (LCH) and / or radio bearer in the same way in terms of QoS. For example, when the UL of the air interface is congested, the UE will attempt to send low importance data even though the application cannot benefit from such low importance data (e.g., the user experience does not benefit from some “stale” low importance data).

[0019] In terms of discard timer enhancements for XR communication, the present disclosure describes details that allow for differentiated treatment (e.g., layer 2 procedures, mechanisms, etc.) of sets of PDUs associated with high importance levels in certain situations (e.g., prioritizing high importance data and discarding low importance data in the case of congestion, etc.). For example, a first set of timer configurations can be applied by a UE (e.g., in normal network conditions). In addition, a second set of discard timer configurations can be applied by the UE, for example, if the UE receives a congestion indication from the RAN, or alternatively, if the UE detects congestion on the air interface (e.g., UL).

[0020] In further aspects of discard timer enhancements for XR communications, the present disclosure provides details for discarding in case of congestion. In an example, the network (NW) configures different PDCP discard timer configurations and / or durations for a radio bearer (e.g., one PDCP discard timer configuration and / or duration per importance level or PSI). In an example, the NW configures multiple PDCP discard timer configurations and / or durations for a radio bearer respectively for each PSI (importance level) supported by the radio bearer (e.g., one PDCP discard timer configuration and / or duration for “normal” mode of operation, one PDCP discard timer configuration and / or duration for “congestion mode”). In an example, the NW signals the mode for PDCP discard to the UE. In an example, the NW indicates congestion and the UE switches PDCP discard timer configuration upon receiving the notification. In an alternative or additional example, the UE considers the PDCP discard timer for low importance data to expire in case congestion is detected or upon receiving a congestion notification from the base station (e.g., gNB).

[0021] In further aspects of discard timer enhancements for XR communications, the present disclosure provides details for importance handling for PDUs not belonging to a PDU set. For example, the UE uses a pre-defined “default” PSI value (e.g., importance level) for PDUs not belonging to a PDU set.

[0022] In further aspects of discard timer enhancements for XR communications, the present disclosure provides details for selective enabling of PDCP duplication based on importance level. In an example, the UE enables PDCP duplication for PDUs of a PDU set based on the associated importance level or PSI of the PDUs of the PDU set. In an example, the gNB configures the UE by indicating the importance levels (or PSI) for which the UE is to enable PDCP duplication.

[0023] In further aspects of discard timer enhancements for XR communications, the present disclosure provides details for delay information reported within a buffer status report (BSR) that takes into account any network sharing delay. In an example, the delay information reported within the BSR takes into account the delay experienced by the PDUs and / or PDU sets on the network sharing link. In an example, a timestamp is included within the data packet or protocol layer header to measure the delay of the network sharing link.

[0024] In further aspects of discard timer enhancements for XR communications, the present disclosure provides details for avoiding or reducing congestion on the air interface (e.g., for UL transmissions) by configuring multiple PDCP discard timer configurations associated with the importance level of PDUs and / or PDU sets.

[0025] In further aspects of discard timer enhancements for XR communications, the present disclosure provides details for various procedures (e.g., layer 2 procedures, etc.) that enable differentiation of PDUs and / or PDU sets of radio bearers associated with different importance levels. For example, a base station (e.g., gNB) configures different discard timer configurations for PDU sets having different PSIs. In additional or alternative examples, different discard timer configurations are used when congestion is detected (e.g., compared to a “normal” mode of operation) in order to discard low importance data when congestion occurs over the air interface (e.g., low importance data is discarded in order to free up resources for transmission of high priority data).

[0026] In further aspects of discard timer enhancements for XR communications, the present disclosure provides details for a NW that configures PDCP discard timer configurations per importance level for a radio bearer and / or PDCP entity. In an example, where a radio bearer (e.g., a data radio bearer) carries PDU sets associated with different importance levels, the NW can configure multiple PDCP discard timer configurations for the PDCP entity of the radio bearer (e.g., one PDCP discard timer configuration per importance level).

[0027] In further aspects of discard timer enhancements for XR communications, the present disclosure provides details for a NW that configures multiple PDCP discard timer configurations for a radio bearer separately for each PSI level supported by the radio bearer. In one example, the NW configures two discard timer configurations and / or durations per PSI for one radio bearer. For example, one configuration and / or duration represents a PDCP discard timer duration to be used during “normal” operation (e.g., also referred to as a first mode of operation), and the other configuration and / or duration is to be used by the UE separately in case of UL congestion detected by the UE and in case of NW informing the UE about congestion over the UL air interface (e.g., also referred to as a second mode of operation).

[0028] By adjusting discard timer configurations based on importance levels and / or network conditions, a communication device can experience improved user experience, low latency, and / or high reliability for wireless communications, particularly with respect to use cases such as XR communications and / or other types of high throughput data communications (e.g., video and / or audio streaming).

[0029] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams and flowcharts.

[0030] Figure 1An example of a wireless communications system 100 that supports discard timer enhancements for XR communications in accordance with aspects of the present disclosure is illustrated. The wireless communications system 100 can include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 can support various radio access technologies. In some implementations, the wireless communications system 100 can be a 4G network, such as an LTE network or a LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 can be a 5G network, such as a New Radio (NR) network. In other implementations, the wireless communications system 100 can be a combination of 4G and 5G networks, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 can support radio access technologies other than 5G. Additionally, the wireless communications system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0031] The one or more network entities 102 can be dispersed throughout the geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein can be or include or can be referred to as a network node, base station, network element, RAN, base transceiver station, access point, NodeB, eNodeB (eNB), next generation NodeB (gNB), or other suitable terminology. The network entities 102 and UEs 104 can communicate via communication links 110, which can be wireless or wired connections. For example, the network entities 102 and UEs 104 can perform wireless communications (e.g., receive signaling, transmit signaling) over a Uu interface.

[0032] The network entity 102 can provide a geographic coverage area 112 for which the network entity 102 can support service (e.g., voice, video, packet data, messaging, broadcast, etc.) to one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and UEs 104 can support wireless communication of signals associated with service (e.g., voice, video, packet data, messaging, broadcast, etc.) in accordance with one or more radio access technologies. In some implementations, the network entity 102 can be mobile, such as a satellite (e.g., a non-terrestrial station (NTS)) associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, although different geographic coverage areas 112 can be associated with different network entities 102. Information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0033] The one or more UEs 104 can be dispersed throughout the geographic region of the wireless communication system 100. A UE 104 can include or can be referred to as a mobile device, wireless device, remote device, remote unit, handset, or subscriber device, or some other suitable terminology. In some implementations, a UE 104 can be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, a UE 104 can be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples. In some implementations, a UE 104 can be stationary, or mobile.

[0034] The one or more UEs 104 can be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. Figure 1 As shown in FIG. 1, UEs 104 can include one or more transceivers 104a, one or more processors 104b, one or more memory components 104c, one or more communication components 104d, one or more input / output interfaces 104e, one or more power supply components 104f, or some combination thereof. Figure 1 As shown in FIG. 1, UEs 104 can include one or more transceivers 104a, one or more processors 104b, one or more memory components 104c, one or more communication components 104d, one or more input / output interfaces 104e, one or more power supply components 104f, or some combination thereof.

[0035] The UEs 104 can be configured to connect directly to one another via a device-to-device (D2D) communication link 110. In some implementations, the D2D communication link 110 can be a cellular D2D communication link 110 that utilizes a licensed spectrum (e.g., compared to a wireless local area network (WLAN) communication link that utilizes an unlicensed spectrum). In some implementations, the D2D communication link 110 can be a vehicle-to-everything (V2X) communication link 110. In some implementations, the D2D communication link 110 can be a sidelink communication link 110. In some implementations, the D2D communication link 110 can be a PC5 interface.

[0036] The network entities 102 can support communication with the core network 106, or with another network entity 102, or both. For example, the network entities 102 can interface with the core network 106 through one or more backhaul links 116 (e.g., via an SI, N2, N6, or another network interface). The network entities 102 can communicate with each other over backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 can communicate directly with each other (e.g., between network entities 102). In some other implementations, the network entities 102 can communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more of the network entities 102 can include subcomponents, such as an access network entity, which can be an example of an access node controller (ANC). The ANC can communicate with one or more UEs 104 through one or more other access network transmission entities (which can be referred to as a radio head, a smart radio head, or a transmission reception point (TRP)).

[0037] In some implementations, the network entities 102 can be configured in a disaggregated architecture that can be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entities 102 can include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near-RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0038] A RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmission reception point (TRP). In a disaggregated RAN architecture, one or more components of the network entity 102 can be co-located, or one or more components of the network entity 102 can be located at distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of a disaggregated RAN architecture can be implemented as virtual units (e.g., virtual CUs (VCUs), virtual DUs (VDUs), virtual RUs (VRUs)).

[0039] The functional split between the CU, the DU, and the RU can be flexible and can support different functions depending on the functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) performed at the CU, the DU, or the RU. For example, a functional split of a protocol stack can be employed between the CU and the DU, such that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper layer protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), PDCP). The CU can be connected to one or more DUs or RUs, and the one or more DUs or RUs can host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and each can be controlled at least in part by the CU.

[0040] Additionally or alternatively, a functional split of a protocol stack can be employed between the DU and the RU, such that the DU can support one or more layers of the protocol stack and the RU can support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU can be within a protocol layer (e.g., some functions for a protocol layer can be performed by one of the CU, the DU, or the RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU).

[0041] A CU can be further split in function into a CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU can be connected to one or more DUs via a midhaul communication link (e.g., Fl, Fl-c, Fl-u), and a DU can be connected to one or more RUs via a front-haul communication link (e.g., open front-haul (FH) interface). In some implementations, a midhaul or front-haul communication link can be implemented according to an interface (e.g., channel) between layers of a protocol stack supported by respective network entities 102 communicating via such a communication link.

[0042] The core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 can be an evolved packet core (EPC) or 5G core (5GC), which can include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and a user plane entity that routes packets or interconnects with other networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity can manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearer, signaling bearer, etc.) for one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

[0043] The core network 106 can communicate with the packet data network 108 through one or more backhaul links 116 (e.g., via SI, N2, N6, or another network interface). The packet data network 108 can include an application server 118. In some implementations, the one or more UEs 104 can communicate with the application server 118 through the core network 106 via the network entities 102. A UE 104 can establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via a network entity 102. The core network 106 can route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session). A PDU session can be an example of a logical connection between a UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0044] In the wireless communication system 100, the network entity 102 and the UE 104 can perform various operations (e.g., wireless communications) using resources (such as time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) of the wireless communication system 100. In some implementations, the network entity 102 and the UE 104 can support different resource structures. For example, the network entity 102 and the UE 104 can support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity 102 and the UE 104 can support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 can support various frame structures based on one or more numerologies.

[0045] One or more numerologies can be supported in the wireless communication system 100, and a numerology can include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., a normal cyclic prefix (NCP)) associated with a first subcarrier spacing (e.g., 15 kHz) can be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. A second numerology (e.g., an extended cyclic prefix (ECP)) associated with the first subcarrier spacing (e.g., 15 kHz) can utilize one slot per subframe. A third numerology (e.g., a normal cyclic prefix (NCP)) associated with a second subcarrier spacing (e.g., 30 kHz) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. A fourth numerology (e.g., an extended cyclic prefix (ECP)) associated with the third subcarrier spacing (e.g., 60 kHz) can be associated with a third subcarrier spacing (e.g., 60 kHz) and the normal cyclic prefix or the extended cyclic prefix. A fifth numerology (e.g., a normal cyclic prefix (NCP)) associated with a fourth subcarrier spacing (e.g., 120 kHz) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. A sixth numerology (e.g., an extended cyclic prefix (ECP)) associated with a fifth subcarrier spacing (e.g., 240 kHz) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix. μ μ The first numerology (e.g., a normal cyclic prefix (NCP)) associated with the first subcarrier spacing (e.g., 15 kHz) (e.g., = 0) can utilize one slot per subframe. The second numerology (e.g., an extended cyclic prefix (ECP)) associated with the first subcarrier spacing (e.g., 15 kHz) (e.g., = 1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third numerology (e.g., a normal cyclic prefix (NCP)) associated with the third subcarrier spacing (e.g., 60 kHz) (e.g., = 2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and the normal cyclic prefix or the extended cyclic prefix. The fourth numerology (e.g., a normal cyclic prefix (NCP)) associated with the fourth subcarrier spacing (e.g., 120 kHz) (e.g., = 3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth numerology (e.g., a normal cyclic prefix (NCP)) associated with the fifth subcarrier spacing (e.g., 240 kHz) (e.g., = 4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix. μ μ The first numerology (e.g., a normal cyclic prefix (NCP)) associated with the first subcarrier spacing (e.g., 15 kHz) (e.g., = 0) can utilize one slot per subframe. The second numerology (e.g., an extended cyclic prefix (ECP)) associated with the first subcarrier spacing (e.g., 15 kHz) (e.g., = 1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third numerology (e.g., a normal cyclic prefix (NCP)) associated with the third subcarrier spacing (e.g., 60 kHz) (e.g., = 2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and the normal cyclic prefix or the extended cyclic prefix. The fourth numerology (e.g., a normal cyclic prefix (NCP)) associated with the fourth subcarrier spacing (e.g., 120 kHz) (e.g., = 3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth numerology (e.g., a normal cyclic prefix (NCP)) associated with the fifth subcarrier spacing (e.g., 240 kHz) (e.g., = 4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix. μ μ The first numerology (e.g., a normal cyclic prefix (NCP)) associated with the first subcarrier spacing (e.g., 15 kHz) (e.g., = 0) can utilize one slot per subframe. The second numerology (e.g., an extended cyclic prefix (ECP)) associated with the first subcarrier spacing (e.g., 15 kHz) (e.g., = 1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third numerology (e.g., a normal cyclic prefix (NCP)) associated with the third subcarrier spacing (e.g., 60 kHz) (e.g., = 2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and the normal cyclic prefix or the extended cyclic prefix. The fourth numerology (e.g., a normal cyclic prefix (NCP)) associated with the fourth subcarrier spacing (e.g., 120 kHz) (e.g., = 3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth numerology (e.g., a normal cyclic prefix (NCP)) associated with the fifth subcarrier spacing (e.g., 240 kHz) (e.g., = 4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0046] Time intervals for the resources (e.g., communications resources) can be organized as frames, each frame having a duration of, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration of, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0047] ​​​Additionally or alternatively, a time interval of resources (e.g., communication resources) can be organized according to slots. For example, a subframe can include a number (e.g., quantity) of slots. Each slot can include a number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of slots for a subframe can depend on the numerology. For a normal cyclic prefix, a slot can include 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), a slot can include 12 symbols. For both normal and extended cyclic prefixes, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame can depend on the numerology. It should be understood that references to a first numerology (e.g., associated with a first subcarrier spacing (e.g., 15 kHz), a second numerology (e.g., μ = 0) can be used interchangeably between subframes and slots.

[0048] In the wireless communication system 100, the electromagnetic (EM) spectrum can be split into various categories, bands, frequency channels, and so on based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communication on one or more operating bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104, and other devices or apparatuses, for cellular communications traffic (e.g., control information, data). In some implementations, FR2 can be used by the network entity 102 and the UE 104, and other devices or apparatuses, for short range, high data rate capabilities.

[0049] FR1 can be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 can be associated with: a first numerology (e.g., μ = 0) that includes a subcarrier spacing of 15 kHz; a second numerology (e.g., μ = 1) that includes a subcarrier spacing of 30 kHz; and a third numerology (e.g., μ = 2) that includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 can be associated with: the third numerology (e.g., μ= 2), which includes a subcarrier spacing of 60 kHz; and a fourth numerology (e.g., NR Rel. 17 μ = 3), which includes a subcarrier spacing of 120 kHz.

[0050] According to implementations, one or more of network entity 102 and UE 104 are operable to implement various aspects of discard timer enhancements for XR communications, as described herein. For example, network entity 102 (e.g., a base station) transmits first signaling 120 including various information, such as one or more sets of timer configurations associated with a plurality of importance levels. In at least one implementation, signaling 120 includes a first set of timer configurations and a second set of timer configurations. Each of the first and second sets of timer configurations includes a respective timer configuration for each of a plurality of importance levels. UE 104 receives first signaling 120 and performs process 122 to apply the first set of timer configurations for data transmissions of a radio bearer. Network entity 102 transmits second signaling 124 (e.g., a message) including various information, such as a notification or indication of congestion. UE 104 receives second signaling 124 and performs process 122 to apply the second set of timer configurations (e.g., in place of the first set) for data transmissions of the radio bearer in response to reception of message 124. For example, the second set of discard timer configurations can prioritize high importance level data and discard lower importance data during a period of congestion.

[0051] Referring to XR, XR is a generalization for different types of realities, including VR, AR, MR, and the like. VR is a rendered version of the delivered visual and audio scene. For example, the rendering is designed to mimic the visual and aural stimuli of the real world as naturally as possible to the observers or users as they move within the limits defined by the application. Virtual reality typically (but not necessarily) requires the user to wear a head-mounted display (HMD) to completely replace the user's field of view with a simulated visual component and earphones to provide the user with accompanying audio. In VR, some form of head and motion tracking of the user is also typically required to allow the simulated visual and audio components to be updated, ensuring that, from the user's perspective, the items and sound sources remain consistent with the user's movements. Additional means of interacting with the virtual reality simulation can be provided, but are not strictly necessary. In examples, AR refers to the user being provided with additional information or artificially generated items or content overlaid on their current environment. Such additional information or content is typically visual and / or aural, and their observation of their current environment can be direct, without intermediate sensing, processing, and rendering, or indirect, where their perception of their environment is relayed via sensors and can be augmented or processed. In examples, MR is a high-level form of AR in which some virtual elements are inserted into the physical scene with the goal of providing the illusion that these elements are part of the real scene.

[0052] In implementations, XR refers to various real and virtual combined environments and / or human-machine interactions generated by computer technology and wearable devices. In examples, XR includes representative forms such as AR, MR, and VR, as well as areas inserted between them. In examples, the level of virtuality ranges from partial sensory input to fully immersive VR. In examples, a key aspect of XR is the extension of human experience, particularly the extension of human experience related to presence (represented by VR) and cognitive acquisition (represented by AR).

[0053] In some implementations, XR and configuration grant (CG) use cases are characterized by quasi-periodic traffic (with possible jitter) with high data rates in the downlink (DL) (e.g., video stream) combined with frequent UL (e.g., pose / control updates) and / or UL video stream. In some examples, both the DL traffic and the UL traffic are further characterized by a relatively strict packet delay budget (PDB).

[0054] In some implementations, the set of XR and CG services is expected to have some diversity, and characteristics of the data flow (i.e., video) can change “dynamically” when the service is running over NR. Thus, for example, additional information about the running service from higher layers (e.g., QoS flow association, frame level QoS, ADU based QoS, XR specific QoS, etc.) can be beneficial to facilitate informed selection of radio parameters. In some described implementations, XR application awareness by the UE and / or gNB improves user experience, increases the NR system capacity to support XR services, and / or reduces UE power consumption.

[0055] In some described implementations, an application data unit (ADU) is the smallest unit of data that can be processed independently by an application (such as processing to handle out-of-order traffic data). In examples, a video frame can be an I-frame, a P-frame, or can be composed of I-slices and / or P-slices. In some examples, I-frames and / or I-slices are more important and larger than P-frames and / or P-slices. In examples, an ADU can be one or more I-slices, P-slices, I-frames, P-frames, or combinations thereof.

[0056] In some described implementations, the service-oriented design herein takes into account XR traffic characteristics (e.g., (a) variable packet arrival rate: packets arrive at 30-120 frames / second with some jitter, (b) packet size is variable and large, (c) B / P frames are dependent on I-frames, (d) multiple traffic / data flows exist in the uplink, such as pose and video scene) to enable more efficient XR service delivery (e.g., in terms of meeting XR service requirements for more UEs, or in terms of UE energy saving).

[0057] With reference to packet delay budget, in some implementations, the latency requirement of RAN side (e.g., air interface) XR traffic is modeled as PDB. PDB is a limited time budget for a packet transmitted over the air from a gNB to a UE. In some examples, for a given packet, the delay of the packet incurred in the air interface is measured from the time the packet arrives at the gNB to the time of successful transmission to the UE. For example, if the delay is greater than a given PDB for the packet, the packet violates the PDB, otherwise the packet is successfully delivered. The value of PDB can vary for different applications and traffic types. In one specific example, the value of PDB is 10-20 milliseconds (ms) depending on the application.

[0058] In some implementations, the 5G arrival time of a data burst on the DL can be quasi-periodic (e.g., periodic and with jitter). Some example factors that contribute to the jitter in burst arrival include: different server rendering times, encoder times, real-time transport protocol (RTP) packet times, link between server and 5G gateway, etc. In some implementations, simulation assumptions for evaluating model DL traffic arrival jitter for XR are considered, including using a truncated Gaussian distribution, mean: 0 ms, standard deviation: 2 ms, range: [-4 ms, 4 ms] (baseline), [-5 ms, 5 ms] (optional),

[0059] In some implementations, an application can have certain delay requirements for an ADU that can not be fully translated into packet delay budget requirements. For example, if an ADU delay budget (ADB) is 10 ms, then if all packets of the ADU arrive at the 5G system at the same time, the PDB can be set to 10 ms. For example, if the packets are scattered, then the ADU delay budget is measured from the arrival of the first packet of the ADU or the last packet of the ADU. For example, in either case, a given ADB results in different PDB requirements for different packets of the ADU. In some scenarios, it can be beneficial to specify the ADB to the 5G system.

[0060] With reference to delay-aware communication, in implementations, if the scheduler and / or UE are aware of the delay budget for a packet / ADU, the gNB can take this knowledge into account in scheduling transmissions (e.g., by prioritizing transmissions that are close to their delay budget limit, without scheduling (e.g., UL) transmissions). In examples, the UE can also utilize such knowledge to determine: 1) whether an UL transmission corresponding to a transmission that exceeds its delay budget can be dropped (e.g., in response to a physical downlink shared channel (PDSCH), UL pose, or physical uplink control channel (PUCCH) of a physical uplink shared channel (PUSCH)) (further, for example, the system does not necessarily need to wait for a retransmission of the PDSCH and / or keep the erroneously received PDSCH in the buffer for soft combining with the retransmission that never occurs); or 2) how much of its channel occupancy time can be shared with the gNB in case of unlicensed spectrum usage.

[0061] In some examples, 1) the remaining delay budget for DL transmissions can be indicated to the UE in downlink control information (DCI) (e.g., for packets of a video frame, slice, and / or ADU) or via a MAC control element (MAC-CE) (e.g., for ADUs, video frames, and / or slices); and 2) the remaining delay budget for UL transmissions can be indicated to the gNB via UL transmissions such as uplink control information (UCI), PUSCH transmissions, etc.

[0062] With reference to application awareness at the RAN, PDU Set related QoS aspects of XR can be conveyed to the RAN to optimize the communication, such as PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB), etc. For example, in both UL and DL, XR awareness helps to optimize gNB radio resource scheduling and relies at least on the concepts of PDU Set and Data Burst. In an example, a PDU Set consists of one or more PDUs carrying the payload of one information unit (e.g., frame or video slice) generated at the application level, while a Data Burst is a collection of data PDUs generated and transmitted by the application in a short period of time. In an example, a Data Burst can consist of multiple PDUs belonging to one or more PDU Sets.

[0063] In implementations, the following information can be provided by the CN to the RAN to assist in handling QoS flows and PDUs.

[0064] In implementations, the semi-static information provided for both UL and DL via the control plane (NGAP) includes: periodicity of UL and DL traffic for QoS flows via Time Sensitive Communication Assistance Information (TSCAI) and / or Time Sensitive Communication Assistance Container (TSCAC); traffic jitter information (e.g., jitter range) associated with each periodicity of a QoS flow. In some examples, applicability of the jitter information to UL is considered.

[0065] In implementations, the PDU Set QoS parameters include: PDU Set Error Rate (PSER) which defines an upper limit for the rate of PDU Sets that have been processed by the sender of the link layer protocol but not successfully delivered by the corresponding receiver to the upper layer. In some examples, a PDU Set is considered successfully delivered when all PDUs of the PDU Set are successfully delivered. Additionally or alternatively, the PDU Set QoS parameters also include PDU Set Delay Budget (PSDB), i.e., the time between the reception of the first PDU and the successful delivery of the last arrived PDU of the PDU Set. In an example, PSDB is an optional parameter. Additionally or alternatively, the PDU Set QoS parameters include PDU Set Integration Indication (PSII) (e.g., whether the use of the PDU Set by the application layer requires all PDUs). Additionally or alternatively, the PDU Set QoS parameters also include dynamic information provided by the user plane for DL (GTP-U header) such as: PDU Set Sequence Number; PDU Set Size (bytes); PDU SN within PDU Set; End PDU of PDU Set; PDU Set Importance (e.g., a parameter to identify the importance of a PDU Set within a QoS Flow, which can be used by the RAN for PDU Set level packet discarding in case of congestion; and / or Data Burst End Indication in the header of the last PDU of a Data Burst (e.g., optional).

[0066] Referring to the jitter aspect of XR, in an example, the packet arrival rate is determined by the frame generation rate (e.g., 60 frames per second (fps)). In an example, the average packet arrival periodicity is given by the inverse of the frame rate (e.g., 16.6667 ms = 1 / 60 fps). The periodic arrival without jitter gives the arrival time at the gNB for a packet with index k (= 1, 2, 3,...) as follows: k / F 1000 [ms], where F is the given frame generation rate (per second).

[0067] However, in some examples of real systems, varying frame encoding delays and network transmission times introduce jitter in the packet arrival time at the gNB. In this model, the jitter is modeled as a random variable added on top of the periodic arrival. The jitter follows a truncated Gaussian distribution with the statistical parameters shown in Table 1. Table 1: Statistical parameters for jitter

[0068] Note that in some examples, the given parameter values and the considered frame generation rate (60 or 120 in this model) ensure that the packet arrival is ordered (e.g., the arrival time of the next packet is always greater than the arrival time of the previous packet). For example, the periodic arrival with jitter gives the arrival time at the gNB for a packet with index k (= 1, 2, 3,...) as follows: offset + k / F 1000 + J [ms], where F is the given frame generation rate (per second), and J is a random variable capturing the jitter. Note that the actual traffic arrival timing for the traffic of each UE can be offset by a UE-specific arbitrary offset.

[0069] Referring to dynamic adaptation of discontinuous reception (DRX) parameters and / or configurations, in some examples, a DCI (e.g., within a DRX active time) can indicate an update to one or more of: a C-DRX cycle, an on-duration timer, or an inactivity timer (e.g., for a current or upcoming DRX cycle). For example, DCI signaling within an active time of a DRX cycle can indicate such an update. Aspects of the present disclosure include: details for such DCI signaling, corresponding timelines, UE behavior and / or actions, and / or updates to other DRX configuration parameters and / or timers needed in response to receiving a DCI indicating an update to a DRX parameter and / or timer.

[0070] Referring to multiple simultaneous DRX configurations, the network can enable multiple simultaneous DRX configurations for a UE, where different DRX configurations are aligned almost with the arrival of different traffic flows. In an example, each DRX configuration can be configured with a traffic periodicity, and the DRX cycle start can be aligned with the expected application packet arrival (or start of jitter range) of one particular traffic flow. In an example, regardless of the DRX parameter values selected for each configuration, the multiple-flow DRX solution works as follows: while a drx-onDurationTimer (or drx-inactivityTimer) is running in any DRX configuration, the UE monitors PDCCH (e.g., the total active time is the logical 'or' of the active times given by each DRX configuration); and / or if a PDCCH for a new transmission is received, any drx-inactivityTimer that was running at the time can be restarted.

[0071] In aspects of the disclosure, mapping options for XR communications are considered. One possible mapping option for XR communications includes mapping PDU sets of different importance levels to the same QoS flow and radio bearer. One example of this mapping option is that, for example, I-frames and P-frames of a video stream are carried by the same QoS flow / radio bearer.

[0072] Figure 2 An example 200 of mapping options related to discard timer enhancements for XR communications is illustrated, where I-frames and P-frames of a video stream are carried by the same QoS flow / radio bearer. Referring to Figure 2 A PDU set integration handling indication can indicate whether all PDUs of a PDU set need to be used by the application layer. Additionally or alternatively, a PDU set importance is a parameter to identify the importance of a PDU set within a QoS flow (e.g., the RAN can use this parameter for PDU set level packet discard in case of congestion).

[0073] In some examples, a PDU Set Delay Budget (PDSB) defines an upper limit for the delay that a set of transport PDUs between a UE and an N6 endpoint at the UPF 212 can experience (e.g., the time between the reception of a first PDU and the successful delivery of the last arriving PDU of the set of PDUs). In examples, PDSB applies to a set of DL PDUs received by the UPF 212 over the N6 interface and a set of UL PDUs sent by the UE. In examples, the value of PDSB is the same in UL and DL for a certain 5QI. In examples, to enable support of PDSB, a maximum duration threshold can be assumed for the arrival time interval between a PDU within a per-SLA or preconfigured PDU set and the first arriving PDU. In examples, a case where the maximum duration threshold is not met is considered. In some examples, PDSB is an optional parameter. For example, if the PCF 206 has sufficient information to determine PDSB, PDSB is used to support the configuration of scheduling and link layer functions.

[0074] In some examples, PSER defines an upper limit for the rate of a set of PDUs that have been processed by a sender of a link layer protocol (e.g., RLC in the RAN) but not successfully delivered by the corresponding receiver to an upper layer (e.g., PDCP of the RAN). Thus, in examples, PSER defines an upper limit for the rate of non-congestion related packet loss. In examples, PSER allows for proper link layer protocol configuration (e.g., RLC and HARQ in the RAN). In examples, the value of PSER is the same in UL and DL for each 5QI. In some examples, a set of PDUs is considered erroneous if any PDU within the set of PDUs is not successfully transmitted. In some examples, a set of PDUs is considered successfully delivered when all PDUs of the set of PDUs are successfully delivered.

[0075] In the illustrated example, the XRAF 202 determines PDU set requirements. Example PDU set QoS parameters include: PDSB, PSER, PDU set integration indication (e.g., all PDUs in the PDU set). In an example, the PDU set requirements include burst periodicity (e.g., which can include a frame rate value); and a description of the service protocol (e.g., indicating the RTP and / or Real Time Streaming Protocol (RTSP) header type to be used for PDU set identification at the User Plane Function (UPF) 212). In an example, the description of the service protocol can include a payload type (e.g., the UPF 212 is not necessarily media aware). In some examples, the AF 202 can not necessarily provide jitter information. In an example, a Policy Control Function (PCF) 206 determines QoS rules for the PDU set. In an example, a Session Management Function (SMF) 208 receives the QoS rules. The QoS profile for the QoS flow can include PDSB and PSER information. In an example, the SMF 208 tells the UPF 212 to enable PDU set checking and how to route PDU set packets. In an example, the SMF 208 sends QoS to the RAN via NGAP messages, the QoS including one or more of: periodicity of UL and DL traffic for the QoS flow, which can include frame values (e.g., 15, 20, 30, 45, 60, 72, 90, 120 FPS); a jitter range associated with each periodicity (e.g., the UPF 212 derives jitter per periodicity based on implementation); and / or (optionally) a burst end indication.

[0076] In the illustrated example, the UPF 212 receives XR packets 210a, 210b, 210c (from an XR video application) that include PDU set information corresponding to I-frames, B-frames, P-frames, respectively. For example, the RTP header extension of XR packet 210a includes PDU set information (e.g., importance, size). In an example, the XR packet 210a can also include options for HTTP / Masque and / or GTP-U out. In an example, the UPF 212 determines PDU sets from the XR packets (e.g., different options) and routes the packets to corresponding QoS flows according to N4 rules. In some examples, the UPF 212 also identifies the importance of the PDU set. In some examples, the SMF 208 and / or UPF 212 computes jitter.

[0077] In the illustrated example, the RAN 214 receives the QFI and / or QoS profile of the QoS flow from the SMF 208 (e.g., via the AMF) during PDU session establishment and / or modification (including PDSB and PSER). In examples, the RAN 214 inspects the GTP-U header and ensures that all packets of the same PDU set are processed according to the QoS profile. In some described implementations, the RAN 214 can discard lower importance PDU sets if they cannot be delivered to the UE in time (e.g., different importance levels or flags). In some examples, the RAN 214 marks the start and end PDUs of a PDU set and ensures that the PDU set is delivered to the UE according to the PDSB requirements with consideration of the jitter (e.g., the jitter can be a presumed value based on the SLA agreement). In some examples, when the RAN 214 receives the last PDU of a PDU set, the RAN delivers the PDU set according to the PDSB.

[0078] Figure 3 Figure illustrates an example 300 of alternative mapping options for low layer mapping and / or processing related to discard timer enhancements for XR communications. Referring to Figure 3 , a QoS flow and / or radio bearer for XR traffic can carry PDU sets with different importance levels (e.g., I-frames and P-frames) of a video stream.

[0079] In aspects of discard timer enhancements for XR communications, the NW configures PDCP discard timer configurations per importance level for a radio bearer and / or PDCP entity. For example, for a case where a radio bearer (e.g., a data radio bearer) carries PDU sets associated with different importance levels, the NW can configure the PDCP entity of the radio bearer with multiple PDCP discard timer configurations (e.g., one for each importance level). In some examples, the PDCP discard timer is configured for a data radio bearer (DRB). For example, the duration of the timer is configured by an upper layer (e.g., RRC signaling).

[0080] In implementations, the PSI identifies the relative importance of a set of PDUs compared to other sets of PDUs within a QoS flow and radio bearer. In examples, the UE identifies the set of PDUs and the corresponding PSI of the set of PDUs. In examples, the NW configures a corresponding PDCP discard timer configuration (e.g., PDCP discard timer duration) for each PSI level. In examples, the NW (e.g., gNB) is informed about the different PSI values and / or levels supported for a radio bearer (e.g., the gNB is provided with the different PSI values and / or levels that the set of PDUs of a radio bearer can be associated with). In examples, information about the supported PSI levels and / or values can be provided by the CN to the RAN as part of the semi-static information provided on a per QoS flow level.

[0081] Figure 4A and Figure 4B FIGURE 13 illustrates an example 1300 implementation (e.g., ASN-1 code) including information (e.g., DiscardTimerExt3-r18 ) about multiple PDCP discard timer configurations for supported PSI levels for a PDCP entity, which supports discard timer enhancements for XR communications, in accordance with aspects of the present disclosure. Reference is made to Figures 4A to 4B , an information element (IE) PDCP-Config is used to set configurable PDCP parameters for signaling, multicast and broadcast services (MBS), and data radio bearers. Reference is made to Figures 4A to 4B , certain PDCP-Config field descriptions are provided below.

[0082] cipheringDisabled : If included, ciphering for this DRB is disabled regardless of which ciphering algorithm is configured for the SRB / DRB. In examples, the field can only be included if the UE is connected to 5GC. Otherwise, the field will not be present. In examples, for this field, the network configures the same PDU session ID with the same value for all DRBs. In some examples, the value for this field is configured to remain unchanged after the DRB is established.

[0083] discardTimer : In examples, the value ms10 corresponds to 10 ms, the value ms20 corresponds to 20 ms, and so on. In some examples, the value for this field is configured to remain unchanged in case of reconfiguration with synchronization (e.g., if the bearer is configured as a DAPS bearer).

[0084] discardTimerExt : The discardTimerThe value is in milliseconds (ms). In the example, the value ms0dot5 corresponds to 0.5 ms, the value ms1 corresponds to 1 ms, and so on. If this field exists, it will be used in the implementation. discardTimer Ignored, and used discardTimerExt replace.

[0085] discardTimerExt2 As mentioned above discardTimerExt The value in milliseconds. In the example, the value ms2000 corresponds to 2000 ms. If this field exists, then in the implementation, the field... discardTimer and discardTimerExt Ignored, and used discardTimerExt2 replace.

[0086] discardTimerExt3 As mentioned above discardTimer The value is in milliseconds (ms). In the example, the value ms10 corresponds to 10 ms, the value ms20 corresponds to 20 ms, and so on. If this field exists, it will be used in the implementation. discardTimer , discardTimerExt and discardTimerExt2 Ignored, and used discardTimerExt3 Replacement.

[0087] PSI_level The number of importance levels (PSI) supported for data radio bearers.

[0088] In the implementation, the first entry in the list of PDCP drop timer durations refers to the PDCP drop timer duration used for the lowest importance level (PSI value). In the example, the second entry in the list of PDCP drop timer durations (if there are more than one entry in the list) refers to the PDCP drop timer duration used for the next higher importance level (PSI value), and so on.

[0089] In the implementation, the first entry in the list of PDCP discard timer durations refers to the PDCP discard timer duration corresponding to the highest importance level (PSI value). In the example, the second entry in the list of PDCP discard timer durations (if there is more than one entry in the list) refers to the PDCP discard timer duration corresponding to the second highest importance level (PSI value), and so on.

[0090] In implementations, the UE determines the corresponding PDCP discard timer duration for the PDU / SDU of a PDU set that should be used based on the PSI (e.g., priority level) associated with the PDU set. In examples, the PSI associated with the PDU set is provided by a higher layer to the PDCP entity / layer. In some examples, the UE identifies the PDU set and the corresponding PSI. For example, upon receiving an SDU from the upper layer, the UE starts a new PDCP discard timer with a duration corresponding to the PSI of the PDU set and / or service data unit (SDU). Alternatively, in examples, upon receiving a first SDU of a PDU set from the upper layer (e.g., for the case of maintaining one PDCP discard timer per PDU set), the UE starts a new timer with a corresponding duration (e.g., a duration associated with the priority of the corresponding PDU set (PSI)).

[0091] In implementations, the NW configures multiple PDCP discard timer configurations (e.g., multiple different PDCP discard timer durations) for a radio bearer / PDCP entity per PSI level supported by the radio bearer. In examples, the NW configures 2 discard timer configurations and / or durations per priority level (PSI) for one radio bearer. For example, one configuration and / or duration represents the PDCP discard timer duration to be used during “normal” operation (e.g., also referred to as a first mode of operation), and another configuration and / or duration to be used by the UE upon UL congestion being detected and / or in response to the NW informing the UE about the congestion on the UL air interface (e.g., also referred to as a second mode of operation).

[0092] Figure 5 Fig. illustrates an example 500 of handling PDUs to be transmitted in a UE that supports discard timer enhancements for XR communications, in accordance with aspects of the present disclosure. In aspects of the present disclosure, the priority of a PDU set (PSI) can be used for discard operations during congestion. In some implementations, if the UL air interface is congested and UL transmission resources are not available for every PDU or SDU to be transmitted in the buffer, the UE is configured to prioritize high priority data and discard low priority data and / or PDU sets. For real-time applications like real-time video applications, in some examples, the PDUs to be transmitted in the UE corresponding to old video frames can be irrelevant to the real-time video stream. Moreover, these PDUs and / or SDUs can be discarded as shown, for example, since there can be no reason to send them again, to help alleviate congestion in the network while improving the end user experience of the real-time video stream. Figure 5

[0093] ​In the illustrated example, for the case of new high priority data arriving at the buffer of the UE and having been transmitted in the UL (e.g., I-frames), there can be no reason to transmit additional pending low importance data (e.g., P-frames) that depend on previous I-frames. To reduce the level of congestion on the air interface, an example UE of the present disclosure is configured to discard “stale” low importance data and thereby additionally or alternatively use radio resources for transmission of high importance PDUs / SDUs (P-frames) related to the current I-frames.

[0094] In implementations, the UE (transmitter) restarts any running PDCP discard timer with a duration associated with the corresponding mode (e.g., second operational mode) upon detecting congestion on the air interface or upon receiving a notification from a network entity (e.g., gNB). In examples, when restarting the timer upon a mode change, the UE takes into account the time that has elapsed while the timer was running. For example, when the timer has been running for x ms, the UE restarts the timer (e.g., upon detecting a mode change or upon notification of a mode change) and sets the timer to the duration associated with the updated mode minus x ms.

[0095] In implementations, a message from a network entity (e.g., gNB) to a UE is provided, which is used to control discard timer handling in the UE for uplink. In examples, the message provides information about the level of congestion for the air interface (e.g., Uu interface). In examples, the information informs of congestion occurring on the air interface for uplink. In examples, the message causes the UE to switch between different PDCP discard timer durations and / or configurations. In examples, the message is sent via a MAC control element.

[0096] In implementations, the message includes one or more of: an indication of presence / absence of congestion on the air interface (Uu interface) for UL / DL transmissions; an indication to activate or deactivate “congestion mode” behavior at the UE; an indication to the UE of which PDCP discard timer configuration and / or duration to use for a radio bearer (e.g., for cases where the UE is configured with two or more discard timer configurations and / or durations per radio bearer or per importance level (PSI) supported by a radio bearer); and / or an indication of LCH identifiers (IDs) for which the UE should switch discard timer configurations and / or durations.

[0097] In an example, the message is indicated within a DCI. In an example, a group common DCI can be used for the signaling of the new message (e.g., a group radio network temporary identifier (RNTI) is used to mask the cyclic redundancy check (CRC) of the DCI). In an example, in response to receiving a message from the gNB indicating congestion on the (UL) air interface and / or upon detecting congestion on the air interface, the UE starts a new timer. While this timer is running, the UE operates according to the “congestion mode” behavior (e.g., uses different discard timer durations according to the configuration, or discards PDCP SDUs / PDUs of PDU sets associated with low priority (PSI)). Upon expiry of the new timer, the UE switches back to the “normal mode” behavior (e.g., uses the corresponding discard timer configuration and / or durations).

[0098] In an implementation, upon detecting congestion, the UE considers PDCP discard timers for PDCP SDUs of PDU sets associated with low priority levels to expire. In an example, in response to receiving a notification from the NW indicating “congestion”, the UE considers PDCP discard timers for PDCP SDUs / PDUs of PDU sets associated with low priority to expire. In an example, upon detecting congestion at the UE or upon receiving a notification from the gNB, the priority level(s) for which the UE should consider PDCP discard timers to expire are pre-configured (e.g., RRC signaling) or pre-defined. In an example, upon detecting congestion, the UE considers PDCP discard timers for PDCP SDUs of PDU sets associated with the lowest priority level to expire. In an example, upon detecting congestion and / or upon receiving a notification from the gNB, the UE uses a discard timer duration of 0 ms for PDCP SDUs of PDU sets associated with low priority (PSI) (e.g., the lowest priority level). In an example, the UE considers the air interface (e.g., UL) to be congested when the amount of data for LCHs or radio bearers that can be used for transmission exceeds a pre-defined threshold.

[0099] In an implementation, the UE indicates a cause value when indicating that a CG PUSCH resource is not used (e.g., through signaling of CG-UCI). In an example, the cause value refers to a different set of causes. In an example, the cause value indicates one or more of the following. “Congestion”: it indicates that PDU of a PDU set is discarded and that CG PUSCH transmission is not performed due to congestion. “PDU loss”: it is not meaningful to transmit further remaining PDU(s) in a PDU set due to at least one PDU in the PDU set being determined to be “lost”. “Data availability”: it indicates that there is no further data in the UE buffer that can be used for transmission.

[0100] In implementations, the UE uses a default priority level (PSI) for PDCP SDUs not belonging to a PDU set. In examples, the priority level (PSI) to be used for PDCP SDUs not belonging to a PDU set is pre-configured (e.g., RRC signaling). In examples, the UE uses the highest priority level for PDCP SDUs and / or PDUs not belonging to a PDU set. In examples, the UE uses the lowest priority level (PSI) for PDCP SDUs / PDUs not belonging to a PDU set.

[0101] In implementations, the delay information reported within the buffer status report takes into account the time experienced by the PDU / PDU set for the network sharing link. In examples, the present disclosure supports network sharing use cases for XR (e.g., AR glasses can network share through a non-5G connection (wired, WiFi) or through a 5G connection). In examples, the reported remaining delay budget information includes the time spent by the PDU and / or PDU set on the network sharing link. In examples, an application or some higher layer protocol includes a timestamp for the PDU, PDU set, and / or data packet in order to allow the measurement of the time elapsed in the UE since the generation of the packet, PDU, and / or PDU set. In examples, the timestamp is included in the RTP header. In examples, the UE assumes a given average delay for the network sharing interface when reporting the remaining delay budget within the buffer status report information. In examples, the UE reports the average link delay (average delay of the network sharing link) to the NW (e.g., gNB). In examples, the average link delay is reported within a MAC control element. In examples, the average link delay is reported as part of the UE assistance information.

[0102] In the implementation, the UE enables selective replication (PDCP replication) based on the importance level (PSI) associated with the PDU and / or PDU set. In the example, the UE enables PDCP replication for PDCP SDUs and / or PDUs with a predefined associated importance level (PSI) (e.g., the PDU set to which the SDU / PDU belongs has a predefined associated PSI). After identifying the PSI of the PDCP SDU received from the upper layer, in the example, the UE determines whether the PSI value corresponds to a predefined PSI level within a predefined PSI level set. For example, if the PSI level of the PDU set and / or SDU is equal to a predefined PSI level within a predefined PSI level set, the UE and / or PDCP entity enables PDCP replication for the entire PDU set. In the example, the NW configures whether selective replication based on PSI level is applied. In the example, the network entity (e.g., gNB) configures which PSI levels the PDCP entity and / or UE should enable PDCP replication for (e.g., via RRC signaling). In the example, the new configuration is signaled within the IE PDCP configuration, which is used to set configurable PDCP parameters for signaling, MBS multicast, and / or data radio bearers. In the example, the UE enables NACK-based selective PDCP replication (PDCP replication) based on the importance level (PSI) associated with the PDU and / or PDU set. For a PDU set with a predefined / preconfigured importance level (PSI), the UE enables PDCP replication based on the reception of NACK (e.g., after receiving a scheduled retransmission DCI).

[0103] Figure 6 An example block diagram 600 of a device 602 supporting drop timer enhancements for XR communications according to aspects of this disclosure is illustrated. Device 602 may be an example of a UE 104 as described herein. Device 602 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 602 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 604, memory 606, transceiver 608, and I / O controller 610). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0104] Processor 604, memory 606, transceiver 608, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 604, memory 606, transceiver 608, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0105] In some implementations, the processor 604, the memory 606, the transceiver 608, or various combinations or components thereof, can be implemented in hardware (e.g., in communication management circuitry). The hardware can include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic component, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure. In some implementations, the processor 604 and the memory 606 coupled with the processor 604 can be configured to perform one or more of the functions described herein (e.g., by the processor 604 executing instructions stored in the memory 606).

[0106] For example, the processor 604 can support wireless communication at the device 602 in accordance with examples as disclosed herein. The processor 604 can be configured to or otherwise support means for receiving, from a RAN, first signaling as a configuration indicating a plurality of timer configuration sets for a plurality of importance levels; applying, for data of a radio bearer, a first timer configuration set of the plurality of sets; and applying, for the data of the radio bearer, a second timer configuration set of the plurality of sets in response to receiving a message from the RAN.

[0107] Further, the processor 604 can be configured to or otherwise support any one or combination of means for the first timer configuration set including a respective timer configuration for each importance level of the plurality of importance levels. Additionally or alternatively, the second timer configuration set includes a respective timer configuration for each importance level of the plurality of importance levels. Additionally or alternatively, means for storing data of a radio bearer for transmission, the data being associated with a plurality of importance levels. Additionally or alternatively, means for receiving, from a RAN, second signaling as a message. Additionally or alternatively, the message includes a congestion indication. Additionally or alternatively, means for starting a timer in response to receiving data of a radio bearer from an upper layer. Additionally or alternatively, means for setting a timer value for the timer according to the first timer configuration based on the received data from the upper layer being associated with a first importance level. Additionally or alternatively, means for restarting the timer in response to receiving the message from the RAN.

[0108] Additionally or alternatively, according to examples disclosed herein, the device 602 can include a processor 604; and a memory 606 coupled with the processor 604, the processor 604 configured to cause the device 602 to: receive, from a RAN, first signaling as a configuration, the configuration indicating a plurality of sets of timer configurations for a plurality of importance levels; apply, for data of a radio bearer, a first set of timer configurations of the plurality of sets; and responsive to receiving a message from the RAN, apply, for the data of the radio bearer, a second set of timer configurations of the plurality of sets.

[0109] Additionally, the wireless communication at the device 602 can include any one or combination of the following: the first set of timer configurations includes a respective timer configuration for each importance level of the plurality of importance levels. Additionally or alternatively, the second set of timer configurations includes a respective timer configuration for each importance level of the plurality of importance levels. Additionally or alternatively, the processor 604 is configured to cause the device 602 to store the data of the radio bearer for transmission. Additionally or alternatively, the data is associated with the plurality of importance levels. Additionally or alternatively, the processor 604 is configured to cause the device 602 to receive, from the RAN, second signaling as the message. Additionally or alternatively, the message includes a congestion indication. Additionally or alternatively, the processor 604 is configured to cause the device 602 to start the timer responsive to receiving the data of the radio bearer from an upper layer. Additionally or alternatively, the processor 604 is configured to cause the device 602 to: based on the data received from the upper layer being associated with a first importance level, set a timer value for the timer according to the first timer configuration. Additionally or alternatively, the processor 604 is configured to cause the device 602 to: based on the data received from the upper layer being associated with a second importance level, set a timer value for the timer according to the second timer configuration. Additionally or alternatively, the processor 604 is configured to cause the device 602 to restart the timer responsive to receiving the message from the RAN.

[0110] According to examples disclosed herein, the processor 604 of the device 602 can support wireless communication. The processor 604 includes at least one controller coupled with at least one memory and configured or capable of operating to cause the processor to: receive, from a RAN, first signaling as a configuration, the configuration indicating a plurality of sets of timer configurations for a plurality of importance levels; apply, for data of a radio bearer, a first set of timer configurations of the plurality of sets; and responsive to receiving a message from the RAN, apply, for the data of the radio bearer, a second set of timer configurations of the plurality of sets. The at least one controller coupled with the at least one memory can also be configured to cause the processor 604 to perform various operations described herein, such as operations described with reference to the device 602 and / or the UE 104.

[0111] The processor 604 can include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 604 can be configured to operate a memory array using a memory controller. In some other implementations, a memory controller can be integrated into the processor 604. The processor 604 can be configured to execute computer-readable instructions stored in a memory (e.g., the memory 606) to cause the device 602 to perform various functions in accordance with this disclosure.

[0112] The memory 606 can include random access memory (RAM) and read-only memory (ROM). The memory 606 can store computer-readable computer-executable code including instructions that, when executed by the processor 604, cause the device 602 to perform various functions described herein. The code can be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code can not be directly executable by the processor 604 but can cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 606 can include a basic I / O system (BIOS), among other things, which can control basic hardware or software operation such as the interaction with peripheral components or devices.

[0113] The I / O controller 610 can manage input and output signals for the device 602. The I / O controller 610 can also manage peripherals not integrated into the device 602. In some implementations, the I / O controller 610 can represent a physical connection or port to the external peripherals. In some implementations, the I / O controller 610 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®,

[0114] In some implementations, the device 602 can include a single antenna 612. However, in some other implementations, the device 602 can have more than one antenna 612 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which are capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 608 can communicate bi-directionally, via the one or more antennas 612, wired, or wireless links as described herein. For example, the transceiver 608 can represent a wireless transceiver and can communicate bi-directionally with another wireless transceiver. The transceiver 608 can also include a modem to modulate the packets to provide modulated packets, and to demodulate packets received from the one or more antennas 612.

[0115] Figure 7 FIGURE 8 illustrates an example of a block diagram 800 of a device 802 that supports dropping timer enhancements for XR communications in accordance with aspects of the present disclosure. The device 802 can be an example of one of the network entities 102 as described herein. The device 802 can support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 802 can include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 804, a memory 806, a transceiver 808, and an I / O controller 810. These components can communicate or otherwise be coupled via one or more interfaces (e.g., a bus).

[0116] The processor 804, the memory 806, the transceiver 808, or various combinations thereof or various components thereof can be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 804, the memory 806, the transceiver 808, or various combinations or components thereof can support a method for performing one or more of the operations described herein.

[0117] In some implementations, the processor 804, the memory 806, the transceiver 808, or various combinations or components thereof can be implemented in hardware (e.g., in communication management circuitry). The hardware can include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, a processor 804 and memory 806 coupled with the processor 804 can be configured to perform one or more functions described herein (e.g., by the processor 804 executing instructions stored in memory 806).

[0118] For example, the processor 704 can support wireless communication at the device 702 in accordance with examples as disclosed herein. The processor 704 can be configured as or otherwise support a means for transmitting first signaling to a UE as a configuration, the configuration indicating a plurality of sets of timer configurations for a plurality of importance levels; and a means for transmitting second signaling to the UE as a message, the message including a congestion indication.

[0119] Additionally, the processor 704 can be configured as or otherwise support any one or combination of the following: a first set of timer configurations in the plurality of sets includes a respective timer configuration for each importance level in the plurality of importance levels. Additionally or alternatively, a second set of timer configurations in the plurality of sets includes a respective timer configuration for each importance level in the plurality of importance levels. Additionally or alternatively, the set of timer configurations includes a first timer configuration indicating a first timer value for transmission of data for a radio bearer of the UE according to a first importance level. Additionally or alternatively, the set of timer configurations includes a second timer configuration indicating a second timer value for transmission of data for the radio bearer of the UE according to a second importance level.

[0120] Additionally or alternatively, the device 702 can include the processor 704; and a memory coupled with the processor 704, in accordance with examples as disclosed herein. The processor 704 is configured to cause the device 702 to: transmit first signaling to a UE as a configuration, the configuration indicating a plurality of sets of timer configurations for a plurality of importance levels; and transmit second signaling to the UE as a message, the message including a congestion indication.

[0121] Additionally, wireless communication at the device 702 can include any one or combination of the following: a first set of timer configurations in the plurality of sets includes a respective timer configuration for each importance level in the plurality of importance levels. Additionally or alternatively, a second set of timer configurations in the plurality of sets includes a respective timer configuration for each importance level in the plurality of importance levels. Additionally or alternatively, the set of timer configurations includes a first timer configuration indicating a first timer value for transmission of data for a radio bearer of the UE according to a first importance level. Additionally or alternatively, the set of timer configurations includes a second timer configuration indicating a second timer value for transmission of data for the radio bearer of the UE according to a second importance level.

[0122] The processor 704 can include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 704 can be configured to operate a memory array using a memory controller. In some other implementations, a memory controller can be integrated into the processor 704. The processor 704 can be configured to execute computer-readable instructions stored in a memory (e.g., the memory 706) to cause the device 702 to perform various functions in accordance with this disclosure.

[0123] The memory 706 can include random access memory (RAM) and read-only memory (ROM). The memory 706 can store computer-readable computer-executable code including instructions that, when executed by the processor 704, cause the device 702 to perform various functions described herein. The code can be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code can not be directly executable by the processor 704 but can cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 706 can include a basic I / O system (BIOS), among other things, which can control basic hardware or software operation such as the interaction with peripheral components or devices.

[0124] The I / O controller 710 can manage input and output signals for the device 702. The I / O controller 710 can also manage peripherals not integrated into the device 702. In some implementations, the I / O controller 710 can represent a physical connection or port to the external peripherals. In some implementations, the I / O controller 710 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®,

[0125] In some implementations, the device 702 can include a single antenna 712. However, in some other implementations, the device 702 can have more than one antenna 712 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which can be capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 708 can communicate bi-directionally, via the one or more antennas 712, wired, or wireless links as described herein. For example, the transceiver 708 can represent a wireless transceiver and can communicate bi-directionally with another wireless transceiver. The transceiver 708 can also include a modem to modulate the packets to provide modulated packets, and to demodulate packets received from the one or more antennas 712.

[0126] Figure 8 FIGURE 13 illustrates a flowchart of a method 1300 that supports discard timer enhancements for XR communications in accordance with aspects of the present disclosure. The operations of method 1300 can be implemented by a device or its components as described herein. For example, the operations of method 1300 can be performed by a UE 104 as described with reference to FIGS. 1-6 and 9-12. Figures 1 to 7 In some implementations, a device can perform the operations of the described methods. Additionally or alternatively, the device can perform aspects of the described methods using special-purpose hardware.

[0127] At 802, the method can include receiving, from a RAN, first signaling as a configuration that indicates a plurality of sets of timer configurations for a plurality of importance levels. The operations of 802 can be performed according to the methods described herein. In some implementations, aspects of the operations of 802 can be performed by a device as described with reference to FIGS. 1-6 and 9-12. Figure 1 In some implementations, a device can perform the operations of the described methods. Additionally or alternatively, the device can perform aspects of the described methods using special-purpose hardware.

[0128] At 804, the method can include applying, for data of a radio bearer, a first set of timer configurations of the plurality of sets. The operations of 804 can be performed according to the methods described herein. In some implementations, aspects of the operations of 804 can be performed by a device as described with reference to FIGS. 1-6 and 9-12. Figure 1 In some implementations, a device can perform the operations of the described methods. Additionally or alternatively, the device can perform aspects of the described methods using special-purpose hardware.

[0129] At 806, the method can include applying, for data of a radio bearer, a second set of timer configurations of the plurality of sets in response to receiving a message from a RAN. The operations of 806 can be performed according to the methods described herein. In some implementations, aspects of the operations of 806 can be performed by a device as described with reference to FIGS. 1-6 and 9-12. Figure 1 In some implementations, a device can perform the operations of the described methods. Additionally or alternatively, the device can perform aspects of the described methods using special-purpose hardware.

[0130] Figure 9A flow diagram illustrating a method 900 that supports discard timer enhancements for XR communications in accordance with aspects of the present disclosure is shown. The operations of method 900 can be implemented by a device described herein or its components. For example, the operations of method 900 can be performed by a device as described with reference to FIGS. 1-9. Figures 1 to 7 The described UE 104 performs. In some implementations, the device can execute sets of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device can perform aspects of the described functions using special-purpose hardware.

[0131] At 902, the method can include storing data of a radio bearer for transmission, the data being associated with a plurality of importance levels. The operations of 902 can be performed according to the methods described herein. In some implementations, aspects of the operations of 902 can be performed by a device as described with reference to FIGS. 1-9. Figure 1 The described device performs.

[0132] At 904, the method can include receiving second signaling from the RAN as a message. The operations of 904 can be performed according to the methods described herein. In some implementations, aspects of the operations of 904 can be performed by a device as described with reference to FIGS. 1-9. Figure 1 The described device performs.

[0133] At 906, the method can include starting a timer in response to receiving data of a radio bearer from an upper layer. The operations of 906 can be performed according to the methods described herein. In some implementations, aspects of the operations of 906 can be performed by a device as described with reference to FIGS. 1-9. Figure 1 The described device performs.

[0134] At 908, the method can include setting a timer value for the timer according to a first timer configuration based on the received data from the upper layer being associated with a first importance level. The operations of 908 can be performed according to the methods described herein. In some implementations, aspects of the operations of 908 can be performed by a device as described with reference to FIGS. 1-9. Figure 1 The described device performs.

[0135] At 910, the method can include setting a timer value for the timer according to a second timer configuration based on the received data from the upper layer being associated with a second importance level. The operations of 910 can be performed according to the methods described herein. In some implementations, aspects of the operations of 910 can be performed by a device as described with reference to FIGS. 1-9. Figure 1 The described device performs.

[0136] At 912, the method can include restarting the timer in response to receiving the message from the RAN. The operations of 912 can be performed according to the methods described herein. In some implementations, aspects of the operations of 912 can be performed by a device as described with reference to FIGS. 1-9. Figure 1 The described device performs.

[0137] Figure 10 A flow diagram illustrating a method 1000 that supports discard timer enhancements for XR communications in accordance with aspects of the present disclosure is shown. Operations of the method 1000 can be performed by a device described herein or a component thereof. For example, operations of the method 1000 can be performed by a network entity 102 as described with reference to Figures 1 to 7 In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device can perform aspects of the described functions using special-purpose hardware.

[0138] At 1002, the method can include transmitting, to a UE, first signaling as a configuration that indicates a plurality of sets of timer configurations for a plurality of importance levels. The operations of 1002 can be performed in accordance with the examples described herein. In some implementations, aspects of the operations of 1002 can be performed by a device as described with reference to Figure 1 FIG. 10.

[0139] At 1004, the method can include transmitting, to the UE, second signaling as a message that includes a congestion indication. The operations of 1004 can be performed in accordance with the examples described herein. In some implementations, aspects of the operations of 1004 can be performed by a device as described with reference to Figure 1 FIG. 10.

[0140] implementations, and that the operations and the steps can be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods can be combined.

[0141] The various illustrative blocks and components described in connection with the disclosure herein can be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller or microcontroller. The processor can also be implemented as a combination of a

[0142] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions can also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0143] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0144] Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0145] As used herein, including in the claims, “or” as used in a list of items (for example, the items listed are A, B, or C) means an inclusive list such that, for example, A or B or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, A or B or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” can be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Moreover, as used herein, including in the claims, “set” can include one or more elements.

[0146] When referring to a network entity, the terms “transmit,” “receive,” or “communicate” can refer to any portion of the network entity of the RAN (e.g., base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0147] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that can be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “superior” to other examples. The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0148] The description herein is presented to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a network entity, first signaling as a configuration, the configuration indicating a first discard timer configuration and at least one additional discard timer configuration for a packet data convergence protocol (PDCP) entity of a radio bearer; apply, at the PDCP entity, a first discard mode by applying the first discard timer configuration for data of the radio bearer, the data of the radio bearer being associated with a plurality of importance levels; and in response to receiving second signaling from the network entity, apply, at the PDCP entity, a second discard mode by applying the first discard timer configuration and the at least one additional discard timer configuration based on the plurality of importance levels of the data of the radio bearer.

2. The UE of claim 1, wherein to apply the second discard mode, the at least one processor is configured to cause the UE to: apply the first discard timer configuration for the data of the radio bearer associated with a first set of importance levels of the plurality of importance levels; and apply the at least one additional discard timer configuration for the data of the radio bearer associated with a second set of importance levels of the plurality of importance levels.

3. The UE of claim 2, wherein the at least one additional discard timer configuration is applied to the data of the radio bearer associated with low importance.

4. The UE of claim 1, wherein the at least one processor is configured to cause the UE to store the data of the radio bearer for transmission.

5. The UE of claim 1, wherein the second signaling from the network entity is configured to activate or deactivate the second discard mode at the PDCP entity of the UE.

6. The UE of claim 1, wherein the second signaling includes an indication of the radio bearer for which the second discard mode is to be activated or deactivated.

7. The UE of claim 1, wherein the at least one processor is configured to cause the UE to apply the first discard mode at the PDCP entity in response to the second signaling including an indication to deactivate the second discard mode at the PDCP entity.

8. The UE of claim 1, wherein the at least one processor is configured to cause the UE to at least one of: start a PDCP discard timer in response to receiving the data of the radio bearer from an upper layer; or set a timer value for the PDCP discard timer according to a first timer configuration based on the data received from the upper layer being associated with a first importance level and the second signaling indicating activation of the second discard mode based on a second importance level.

9. The UE of claim 8, wherein the at least one processor is configured to cause the UE to set a timer value for the PDCP discard timer according to a second timer configuration based on the data received from the upper layers being associated with a third importance level.

10. The UE of claim 8, wherein the at least one processor is configured to cause the UE to restart the PDCP timer in response to receiving the second signaling from the network entity.

11. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive first signaling from a network entity as a configuration, the configuration indicating a first discard timer configuration and at least one additional discard timer configuration for a packet data convergence protocol (PDCP) entity of a radio bearer; apply a first discard mode at the PDCP entity by applying the first discard timer configuration for data of the radio bearer, the data of the radio bearer being associated with a plurality of importance levels; and in response to receiving second signaling from the network entity, apply a second discard mode at the PDCP entity by applying the first discard timer configuration and the at least one additional discard timer configuration based on the plurality of importance levels of the data of the radio bearer.

12. A network entity (NE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the NE to: send first signaling to a user equipment (UE) as a configuration, the configuration indicating a first discard timer configuration and at least one additional discard timer configuration for a packet data convergence protocol (PDCP) entity of a radio bearer; and send second signaling to the UE, the second signaling including an indication to activate or deactivate a discard mode at the PDCP entity of the radio bearer based on an importance level of data of the radio bearer.

13. The NE of claim 12, wherein the second signaling comprises: a congestion indication.

14. The NE of claim 12, wherein the discard mode based on the importance level of the data of the radio bearer is a first mode of discarding the data of the radio bearer, and wherein a second discard mode indicates the PDCP entity to apply the first discard timer configuration for the data associated with the importance level.

15. The NE of claim 12, wherein the activation of the discard mode based on the importance level of the data indicates the PDCP entity to: apply the first discard timer configuration for a service data unit (SDU) of the data of the radio bearer if the SDU has a first importance level; and apply the at least one additional discard timer configuration for the SDU if the SDU has a second importance level lower than the first importance level.

16. The NE of claim 12, wherein the at least one additional discard timer configuration is configured for service data units (SDUs) or protocol data units (PDUs) associated with low importance in the data of the radio bearer.

17. A method performed by a user equipment (UE), the method comprising: receiving, from a network entity, first signaling as a configuration, the configuration indicating a first discard timer configuration and at least one additional discard timer configuration for a packet data convergence protocol (PDCP) entity of a radio bearer; applying, at the PDCP entity, a first discard mode by applying the first discard timer configuration for data of the radio bearer, the data of the radio bearer being associated with a plurality of importance levels; and in response to receiving, from the network entity, second signaling, applying, at the PDCP entity, a second discard mode by applying the first discard timer configuration and the at least one additional discard timer configuration based on the plurality of importance levels of the data of the radio bearer.

18. The method of claim 17, wherein to apply the second discard mode, the method further comprises: applying the first discard timer configuration for the data of the radio bearer associated with a first set of importance levels of the plurality of importance levels; and applying the at least one additional discard timer configuration for the data of the radio bearer associated with a second set of importance levels of the plurality of importance levels. a respective timer configuration for each importance level of the plurality of importance levels.

19. The method of claim 17, wherein the second set of timer configuration comprises:

20. The method of claim 17, further comprising at least one of: storing the data of the radio bearer for transmission; receiving, from the network entity, the second signaling, wherein the second signaling activates or deactivates the second discard mode at the PDCP entity of the UE based on the importance levels; starting a PDCP discard timer in response to receiving the data of the radio bearer from an upper layer; setting a timer value for the PDCP discard timer according to a first timer configuration based on the data received from the upper layer being associated with a first importance level and the second discard mode based on importance levels being activated; setting a timer value for the PDCP discard timer according to a second timer configuration based on the data received from the upper layer being associated with a second importance level and the second discard mode based on importance levels being activated; or restarting the PDCP discard timer in response to receiving the second signaling from the network entity. ​

Images