Multiple discontinuous reception (DRX) configurations

Abstract

Various aspects of the present disclosure relate to multiple discontinuous reception (DRX) configurations. An apparatus, such as a user equipment (UE), receives a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters. The UE applies the first set of one or more DRX parameters and applies, in response to downlink signaling, the second set of one or more DRX parameters.

Description

Lenovo Ref. No. SMM920240023-WO-PCT 1 MULTIPLE DISCONTINUOUS RECEPTION (DRX) CONFIGURATIONS RELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 573,133, filed 02 April 2024, entitled “MULTIPLE DISCONTINUOUS RECEPTION (DRX) CONFIGURATIONS,” the disclosure of which is incorporated by reference herein in its entirety. TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to discontinuous reception (DRX) operation in wireless communications systems. BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, which may be otherwise known as network equipment (NE), supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)). SUMMARY

[0004] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 2 “one or more of” or “one or both of”) indicates inclusive list such that, for example, a list of at least one of A, 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” may 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”. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0005] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may be configured to, capable of, or operable to receive a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; apply the first set of one or more DRX parameters; and apply, in response to downlink signaling, the second set of one or more DRX parameters.

[0006] A processor (e.g., a standalone processor chipset, or a component of a UE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to receive a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; apply the first set of one or more DRX parameters; and apply, in response to downlink signaling, the second set of one or more DRX parameters.

[0007] A method performed or performable by a UE for wireless communication is described. The method may include receiving a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; applying the first set of one or more DRX parameters; and applying, in response to downlink signaling, the second set of one or more DRX parameters.

[0008] In some implementations of the UE, the processor, and the method described herein, the first set of one or more DRX parameters includes a first timer configured to a first value and the second set of one or more DRX parameters includes a second timer configured to a second value, Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 3 where the second value is larger than the first In some implementations of the UE, the processor, and the method described herein, the first timer includes a first drx-InactivityTimer and the second timer includes a second drx-InactivityTimer. In some implementations of the UE, the processor, and the method described herein, the downlink signaling includes downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) transmission, and an indication that the PDSCH includes one or more of multimodal data or extended reality data.

[0009] In some implementations of the UE, the processor, and the method described herein, the downlink signaling includes DCI allocating downlink resources for an initial transmission. In some implementations of the UE, the processor, and the method described herein, the DCI includes a field set to a predefined value. In some implementations of the UE, the processor, and the method described herein, the DCI is addressed to a predefined radio network temporary identifier (RNTI). In some implementations of the UE, the processor, and the method described herein, the UE, the processor, and the method may further be configured to, capable of, operable to, performed to, or performable to start a timer in response to applying the second set of one or more DRX parameters. In some implementations of the UE, the processor, and the method described herein, the UE, the processor, and the method may further be configured to, capable of, operable to, performed to, or performable to apply the first set of one or more DRX parameters in response to expiry of the timer.

[0010] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may be configured to, capable of, or operable to receive configuration including a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a semi-persistent scheduling (SPS) configuration, one or more of a medium access control (MAC) protocol data unit (PDU) or a PDSCH; and start the timer in response to receiving one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration.

[0011] A processor (e.g., a standalone processor chipset, or a component of a UE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to receive configuration including a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a SPS configuration, one or more Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 4 of a MAC PDU or a PDSCH; and start the response to receiving one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration.

[0012] A method performed or performable by a UE for wireless communication is described. The method may include receiving configuration including a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and starting the timer in response to receiving one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration. In some implementations of the UE, the processor, and the method described herein, the timer includes a drx-InactivityTimer.

[0013] An NE (e.g., a base station) for wireless communication is described. The NE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the NE may be configured to, capable of, or operable to transmit a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; and transmit downlink signaling indicating to apply the second set of one or more DRX parameters.

[0014] A processor (e.g., a standalone processor chipset, or a component of a NE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to transmit a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; and transmit downlink signaling indicating to apply the second set of one or more DRX parameters.

[0015] A method performed or performable by an NE (e.g., a base station) for wireless communication is described. The method may include transmitting a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; and transmitting downlink signaling indicating to apply the second set of one or more DRX parameters.

[0016] In some implementations of the NE, the processor, and the method described herein, the first set of one or more DRX parameters includes a first timer configured to a first value and the second set of one or more DRX parameters includes a second timer configured to a second value, where the second value is larger than the first value. In some implementations of the NE, the processor, and the method described herein, the first timer includes a first drx-InactivityTimer and Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 5 the second timer includes a second drx- In some implementations of the NE, the processor, and the method described herein, the downlink signaling includes DCI scheduling a PDSCH transmission, and an indication that the PDSCH includes one or more of multimodal data or extended reality data.

[0017] In some implementations of the NE, the processor, and the method described herein, the downlink signaling includes DCI allocating downlink resources for an initial transmission. In some implementations of the NE, the processor, and the method described herein, the DCI includes a field set to a predefined value. In some implementations of the NE, the processor, and the method described herein, the DCI is addressed to a predefined RNTI.

[0018] An NE (e.g., a base station) for wireless communication is described. The NE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the NE may be configured to, capable of, or operable to transmit configuration including a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and transmit one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration.

[0019] A processor (e.g., a standalone processor chipset, or a component of a NE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to transmit configuration including a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and transmit one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration.

[0020] A method performed or performable by an NE (e.g., a base station) for wireless communication is described. The method may include transmitting configuration including a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and transmitting one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration. In some implementations of the NE, the processor, and the method described herein, the timer includes a drx-InactivityTimer. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 6 BRIEF OF THE DRAWINGS

[0021] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0022] Figure 2 illustrates an example system for multimodal traffic.

[0023] Figure 3 illustrates an IE for SPS configuration in accordance with aspects of the present disclosure.

[0024] Figure 4 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0025] Figure 5 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0026] Figure 6 illustrates an example of a NE in accordance with aspects of the present disclosure.

[0027] Figure 7 illustrates a flowchart of a method in accordance with aspects of the present disclosure.

[0028] Figure 8 illustrates a flowchart of a method in accordance with aspects of the present disclosure.

[0029] Figure 9 illustrates a flowchart of a method in accordance with aspects of the present disclosure.

[0030] Figure 10 illustrates a flowchart of a method in accordance with aspects of the present disclosure. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 7

[0031] Wireless communications systems are designed to support a variety of different data traffic types and use cases. For instance, in extended reality (XR) implementations, UE and associated XR devices along with NE can be implemented to accommodate multiple simultaneous traffic flows where the arrival of packets are to be synchronized. XR applications, for example, can involve multimodal data flows such as voice data, video data, audio data, sensor data (e.g., haptic data), etc. Thus incorporating human perception (e.g., human senses) in an XR experience can involve stringent end-to-end latency, jitter, and synchronization parameters on multimodal data. XR-related services may have even more stringent requirements on wireless networks since XR date flows may require tight synchronization of multiple synchronous data flows. Therefore, when designing network system enhancements to support XR applications, it is important to consider multimodal interaction techniques to accommodate multimodal data flows that serve several human senses simultaneously. Multimodal interaction can transform how people communicate remotely, practice for tasks, entertain themselves, process information visualizations, and make decisions based on the provided information. For XR applications involving multimodal data transmitted via a mobile communication system (e.g., NR), the interactions between different input signals can involve inter-dependencies between transmissions of different bearers, Logical Channels (LCHs), data flows (e.g., PDU set level QoS requirements) for XR, and the dependency of different QoS flows are to be considered.

[0032] For XR applications, multimodal data may need to be delivered within a small relative delay. In addition, each of the data streams in multimodal data are to be delivered within a respective latency budget. A delay status report (DSR) can be triggered enabling NE (e.g., gNB) to assign resources to an undelivered traffic flow approaching its latency budget. Thus, it is important that a UE is awake during a time window (e.g., multimodal delay budget) when inter-related and / or dependent multimodal data arrives and is scheduled to the UE, such as for DL cases. In scenarios where a UE has a mixed traffic (e.g., multimodal and non-multimodal data) it can be difficult to tailor a DRX configuration to the traffic characteristics and QoS parameters of such mixed traffic scenarios. Therefore, situations may occur where an existing DRX timer is not running, and a UE is not in active time and ready to receive Physical Downlink Control Channel (PDCCH) and / or Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 8 PDSCH when multimodal data is to be to the UE within a strict multimodal data time window.

[0033] Accordingly, the present disclosure provides solutions to ensure timely delivery of multimodal traffic flows by enhancing DRX operation across a wireless communications system. For instance, implementations provide different DRX timer or different DRX timer values (e.g., DRX inactivity timer lengths) for non-multimodal data and multimodal data. A DRX inactivity timer value for multimodal data, for example, is longer than a DRX inactivity timer value for non- multimodal data, such as to enable a UE to remain in an awake state to receive multimodal data.

[0034] According to implementations, a UE can switch from a non-multimodal DRX configuration to a multimodal-specific DRX configuration in response to various events. For instance, a UE can switch to a multimodal DRX configuration in response to receiving DCI indicating multimodal data, such as based on a specified field and / or codepoint in DCI. As another example a UE can apply a multimodal DRX timer value upon decoding PDSCH and determining that multimodal data flow and / or multimodal LCH is received. In a further example an RNTI (e.g., multimodal RNTI) can indicate that DCI and / or PDSCH pertains to multimodal data, and a UE can switch to a multimodal DRX configuration (e.g., multimodal DRX timer) based on the RNTI.

[0035] Implementations described herein also support UE behaviors for SPS pertaining to configured DL assignment. For instance, upon reception of a MAC PDU and / or PDSCH, a UE can start a DRX inactivity timer. An Information Element (IE), for example, is described for configuring a UE with a DRX inactivity timer based on SPS pertaining to configured DL assignment.

[0036] According to implementations a timer is described which controls the time period for how long multimodal DRX configurations and / or DRX parameters are to be applied. A UE, for instance, can switch between multimodal DRX configurations and non-multimodal DRX configurations based on DL signaling and a timer event. For example, a DRX timer can be started in response to reception of a switching command, e.g., to switch from non-multimodal configuration to multimodal configuration, and vice-versa. After expiry of the DRX timer the UE can switch back to a previous DRX configuration. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 9

[0037] Implementations also provide a related DRX timer which can be started in response to the reception of multimodal data, such as indicated by DCI and / or RNTI. The multimodal-related DRX timer, for instance, maintains a UE in ActiveTime during a time window within which multimodal data is to be received. In implementations the multimodal-related DRX timer can be started upon reception of specific multimodal data and / or DCI.

[0038] According to implementations a PDCCH skipping command is provided after the end of a multimodal data burst. For instance, a different PDCCH skipping configuration and / or duration is described for during times when a multimodal timer is running, where the duration of PDCCH skipping may be until end of a multimodal time window, e.g., based on multimodal-RNTI with PDCCH skipping.

[0039] Further, implementations consider network energy saving (NES) scenarios. For instance, where a multimodal DRX timer is started and while a NE is in NES discontinuous transmission (DTX) non-ActiveTime, a UE should monitor PDCCH during multimodal data reception. Multimodal data reception, for instance, is prioritized over NES DTX. In implementations, if a multimodal DRX timer is running on a serving cell in a DRX group, the UE is to monitor PDCCH.

[0040] Accordingly, by utilizing the described techniques, power saving techniques such as DRX can be utilized to conserve UE power resources while maintaining quality parameters for different data types, such as multimodal data for XR applications.

[0041] Aspects of the present disclosure are described in the context of a wireless communications system.

[0042] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network equipment (NE) 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 10 suitable radio access technology including of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0043] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next- generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0044] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0045] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of- Everything (IoE) device, or machine-type communication (MTC) device, among other examples. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 11

[0046] A UE 104 may be able to support communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0047] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N6, or other network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other indirectly (e.g., via the CN 106). In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0048] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external 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 may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0049] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S1, N2, N6, or other network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a PDU session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 12 between the UE 104 and the application server the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0050] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0051] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., ^=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., ^=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., ^=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., ^=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., ^=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., ^=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0052] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 13

[0053] Additionally or alternatively, a time of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., ^=0, ^=1, ^=2, ^=3, ^=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may 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 may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., ^=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0054] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency 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 NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0055] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., ^=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., ^=1), which includes 30 kHz Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 14 subcarrier spacing; and a third numerology , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., ^=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., ^=3), which includes 120 kHz subcarrier spacing.

[0056] According to implementations, one or more of the NEs 102 and the UEs 104 are operable to implement various aspects of the techniques described with reference to the present disclosure. For example, an NE 102 transmits, to a UE 104, a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters. The UE 104 applies the first set of one or more DRX parameters. The NE 102 transmits to the UE 104 DL signaling indicating to apply the second set of one or more DRX parameters, and the UE 104 applies, in response to DL signaling, the second set of one or more DRX parameters. The DL signaling, for instance, signals scheduled transmission of multimodal data. Further, the second set of one or more DRX parameters can pertain to multimodal data specific DRX parameters, such as a multimodal specific DRX timer.

[0057] Figure 2 illustrates an example system 200 for multimodal traffic. The system 200 includes XR devices 202 which in this example includes augmented reality (AR) glasses 204 and a haptic glove 206, and the XR devices 202 are connected to a UE 104. Further, the UE 104 is connected to a network system 208 to enable connectivity to an XR application 210. The network system 208 can be implemented in various ways, such as a 3GPP system including 4G, 5G, 6G, and beyond. In the system 200 the XR devices 202 and the UE 104 can exchange multimodal XR traffic 212 with the XR application 210 including, in this example, audio and video data 214 and haptic data 216.

[0058] XR can be used as an umbrella term for different scenarios such as virtual reality (VR), AR, and mixed reality (MR). VR, for instance, represents a rendered version of a delivered visual and audio scene. The rendering can be designed to naturally mimic visual and audio sensory stimuli of the real world to an observer and / or user as they move within the limits defined by an application. VR can involve a user wearing a head mounted display (HMD) to replace the user's field of view with a simulated visual component and headphones to provide the user with accompanying audio. Head and motion tracking of the user in VR can also be utilized to allow the Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 15 simulated visual and audio components to be to enable that, from a user perspective, objects and sound sources remain consistent with the user's movements.

[0059] AR can represent scenarios where a user is provided with additional information, artificially generated items, and / or content overlaid upon their current real world environment. Such additional information and / or content can be visual and / or audible and the user’s observation of their current environment may be direct (e.g., with no intermediate sensing, processing, and / or rendering) or indirect, e.g., where the user’s perception of their environment is relayed via sensors and may be enhanced and / or processed. MR can represent an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that these elements are part of a real scene.

[0060] Accordingly, XR can refer to real-and-virtual combined environments and human- machine interactions generated by computer technology and wearables. XR can include representative forms such as AR, MR and VR and areas interpolated among them. The levels of virtuality can range from partially sensory inputs to fully immersive VR. One aspect of XR is the extension of human experiences especially relating to the senses of existence (e.g., represented by VR) and the acquisition of cognition, e.g., represented by AR.

[0061] XR and cloud gaming use cases can be characterized by quasi-periodic traffic (with possible jitter) with high data rate in DL (e.g., video steam) combined with the frequent Uplink (UL) (e.g., user pose and / or control update) and / or UL video stream. Both DL and UL traffic in such scenarios can be characterized by relatively strict packet delay budget (PDB).

[0062] In such scenarios a set of XR and cloud gaming services has a variety and characteristics of data streams (e.g., video) that may change “on-the-fly”, such as while the services are running over a wireless communications systems, e.g., NR. Therefore, additional information on the running services from higher layers (e.g. the QoS flow association, frame-level QoS, PDU set-based QoS, XR specific QoS, etc.) may be beneficial to facilitate informed choices of radio parameters. XR application awareness by UE and gNB, for instance, may improve the user experience, improve the NR system capacity in supporting XR services, and reduce the UE power consumption.

[0063] An Application Data Unit (ADU) or PDU set may represent a smallest unit of data that can be processed independently by an application, such as processing for handling out-of-order Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 16 traffic data. A video frame can be an intra- frame), predicted frame (P-frame), can be composed of I-slices and / or P-slices, etc. I-frames and / or I-slices can be more important and larger than P-frames and / or P-slices. A PDU set can be one or more I-slices, P-slices, I-frame, P-frame, or a combination thereof.

[0064] A service-oriented design can consider XR traffic characteristics. Examples of XR traffic characteristics include variable packet arrival rate (e.g., packets arriving at 30-120 frames per second (fps) with some jitter), packets having variable and large packet size, bi-directional frames (B-frames) and / or predictive frames (P-frames) being dependent on I-frames, presence of multiple traffic and / data flows such as pose and video scene in uplink, etc. Such service-oriented designs can enable more efficient XR service delivery, such as for satisfying XR service parameters for a greater number of UEs and / or for UE power saving.

[0065] With reference to delay status reporting such as for multimodal data and / or XR data traffic, a NE can take information regarding PDU set delay into account in scheduling transmissions. The NE, for instance, can give priority to transmissions close to their delay budget limit, and not schedule transmissions (e.g., UL) exceeding a PDU set delay budget. The UE can utilize such information to save UE power by determining if an UL transmission (e.g., UL user pose data and / or Physical Uplink Shared Channel (PUSCH)) corresponding to a transmission that exceeds its delay budget can be dropped. Additionally, UE does not need to wait for re-transmission of a PDSCH that will not occur, e.g., DRX retransmission timers can be stopped. For DL transmissions it can be assumed that NE is aware of the remaining delay budget of the data pending for transmission (e.g., based on information provided by the Session Management Function (SMF)) and can use such information for scheduling decisions.

[0066] For UL resource allocation, a UE can provide assistance information regarding the remaining delay budget of the data pending in its buffer to the NE. Thus, it has been considered that a UE is to provide information on the remaining delay budget of the data for which UL resources are requested. Such assistance information can be referred to as DSR reporting. The PDU set delay budget (PSDB) information provided to the RAN, for instance, may not be sufficient. Since a network may not be aware of the exact arrival time of UL data in the buffer and thus the network may be unaware of the remaining valid time of data pending in the buffer for transmission, a UE can provide this information (e.g., remaining delay information) within the DSR reporting. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 17

[0067] Latency parameters for XR traffic the RAN side (e.g., air interface) can be modelled as PDB. The PDB is a limited time budget for a packet to be transmitted over the air from a NE to a UE. For a given packet, the delay of the packet incurred in air interface is measured from the time that the packet arrives at the NE to the time that it is successfully transferred to the UE. If the delay is larger than a given PDB for the packet, then the packet can be considered to violate PDB, otherwise the packet can be considered to be successfully delivered. The value of PDB may vary for different applications and traffic types, which can be 10-20 ms depending on the application.

[0068] In scenarios, arrival time of data bursts on the DL can be quasi periodic, e.g., periodic with jitter. Some of the factors leading to jitter in burst arrival include varying server render time, encoder time, Real-time Transport Protocol (RTP) packetization time, link between server and 5G gateway, etc. 3GPP agreed simulation assumptions for XR evaluation model DL traffic arrival jitter using truncated Gaussian distribution with mean include: 0ms, std. dev: 2ms, range: [-4ms, 4ms] (baseline), [-5ms, 5ms] (optional).

[0069] Applications can have a delay parameter on a PDU set that may not be adequately translated into packet delay budget requirements. For example, if the PSDB is 10ms, then PDB can be set to 10ms if packets of the PDU set arrive at the wireless communications system at the same time. If the packets are spread out, then the PDU set delay budget can be measured either in terms of the arrival of the first packet of the PDU set or the last packet of the PDU set. In either case, a given PSDB can result in different PDB requirements on different packets of the PDU set. It is observed that specifying the PSDB to the wireless network system can be beneficial.

[0070] Regarding delay-aware communication, if a scheduler and / or the UE is aware of delay budgets for a packet / ADU, the NE can utilize this information for scheduling transmissions. The NE, for instance, can give priority to transmissions close to their delay budget limit and / or not schedule transmissions, e.g., UL. The UE can also utilize such information such as to determine if an UL transmission (e.g., Physical Uplink Control Channel (PUCCH) in response to PDSCH, UL user pose information, or PUSCH) corresponding to a transmission that exceeds its delay budget can be dropped (additionally, no requirement to wait for re-transmission of a PDSCH and no requirement to keep the erroneously received PDSCH in buffer for soft combining with a re- transmission that never occurs) and / or how much of the UE channel occupancy time in cases of unlicensed spectrum usage can be shared with the NE. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 18

[0071] Remaining delay budget for a DL can be indicated to the UE in a DCI (e.g., for a packet of a video frame, slice, and / or ADU) or via a MAC-CE (e.g., for an ADU, video frame, and / or video slice) and for an UL transmission can be indicated to the NE via an UL transmission such as Uplink Control Information (UCI), PUSCH transmission, etc.

[0072] XR application awareness can be based on QoS flows, PDU Sets, data bursts, and traffic assistance information. To enable PDU Sets based QoS handling, PDU Set QoS parameters may be provided by the SMF to the NE as part of the QoS profile of the QoS flow. Examples of PDU Set QoS parameters include PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), and PDU Set Integrated Handling Information (PSIHI). PSDB (such as defined in 3GPP Technical Specification (TS) 23.501) can represent an upper bound for the duration between the reception time of the first PDU (e.g., at the UPF for DL, at the UE for UL) and the time when PDUs of a PDU Set have been successfully received, e.g., at the UE in DL, at the UPF in UL. A QoS Flow may be associated with only one PSDB, and when available, it applies to both DL and UL and supersedes the PDB of the QoS flow. The Access Network (AN) PSDB can be derived by subtracting the CN PDB from the PSDB.

[0073] PSER (such as defined in TS 23.501) can represent an upper bound for a rate of non- congestion related PDU Set losses between RAN and the UE. A QoS Flow may be associated with only one PSER, and when available, can apply to both DL and UL and supersedes the Packet Error Rate (PER) of the QoS flow. A PDU set, for instance, is considered as successfully delivered when PDUs of a PDU Set are delivered successfully. PSIHI can indicate whether PDUs of the PDU Set are needed for the usage of PDU Set by application layer, as defined in TS 23.501. The PDU Set QoS parameters can be common for PDU Sets within a QoS flow.

[0074] Further, the UPF can identify PDUs that belong to PDU Sets, and may determine the following PDU Set Information which it sends to the gNB in the General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) header: PDU Set Sequence Number; Indication of End PDU of the PDU Set; PDU Sequence Number within a PDU Set; PDU Set Size in bytes; and PDU Set Importance (PSI), which identifies the relative importance of a PDU Set compared to other PDU Sets within the same QoS Flow. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 19

[0075] Traffic assistance information may be provided by a core network to the NE, such as: Via Time Sensitive Communication Assistance Information (TSCAI) (for both Guaranteed Bit Rate (GBR) and non-GBR QoS flows) (e.g., UL and / or DL Periodicity; N6 Jitter Information (i.e. between UPF and Data Network) associated with the DL Periodicity); and Indication of End of Data Burst in the GTP-U header of the last PDU in DL. In the UL, the UE may identify PDU Sets and Data Bursts dynamically, including PSI.

[0076] Regarding jitter aspects associated with XR, packet arrival rate can be determined by the frame generation rate, e.g., 60 fps. Accordingly, the average packet arrival periodicity can be given by the inverse of the frame rate, e.g., 16.6667ms = 1 / 60fps. The periodic arrival without jitter gives the arrival time at NE for packet with index k (=1,2,3….) as k / F*1000 [ms], where F is the given frame generation rates per second. The periodic packet arrival can implicitly assume fixed delay contributed from network side including fixed video encoding time, fixed network transfer delay, etc. However, in a real system, the varying frame encoding delay and network transfer time can introduce jitter in packet arrival time at gNB. In this model, the jitter can be modeled as a random variable added on top of periodic arrivals. The jitter can follow truncated Gaussian distribution with example statistical parameters illustrated in Table 1 below. Table 1: Statistical parameters for jitter Parameter unit Baseline value for Optional value for evaluation evaluation Mean ms 0 Standard ms 2 Truncation range ms [-4, 4] [-5, 5]

[0077] Note that the given parameter values and considered frame generation rates (e.g., 60 or 120) can ensure that packet arrivals are in order, e.g., arrival time of a next packet can be larger than that of the previous packet. Thus, the periodic arrival with jitter gives the arrival time for packet with index k (=1,2,3….) as: offset + k / F*1000 + J [ms], where F is the given frame generation rates (per second) and J is a random variable capturing jitter. Note that actual traffic arrival timing of traffic for each UE can be shifted by the UE specific arbitrary offset. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 20

[0078] A current specified (Rel-18) DRX in TS 38.321 (e.g. corresponding UE behavior) is presented below for reference. Implementations presented in the present disclosure, however, provide enhancements to the current specified DRX procedure described in the following:

[0079] For DRX: The MAC entity may be configured by Radio Resource Control (RRC) with a DRX functionality that controls the UE's PDCCH monitoring activity for the MAC entity's cell (C)-RNTI, CI-RNTI, Common Search (CS)-RNTI, Interruption (INT)-RNTI, SFI-RNTI, SP- CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, Air Interface (AI)-RNTI, SL-RNTI, SL-CS-RNTI and Sidelink (SL) Semi-Persistent Scheduling V-RNTI. When using DRX operation, the MAC entity shall also monitor PDCCH according to requirements found in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured, for the activated Serving Cells, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this clause; otherwise the MAC entity shall monitor the PDCCH as specified in 3GPP TS 38.213.

[0080] RRC controls DRX operation by configuring the following parameters: - drx-onDurationTimer: the duration at the beginning of a DRX cycle; - drx-SlotOffset: the delay before starting the drx-onDurationTimer; - drx-InactivityTimer: the duration after the PDCCH occasion in which a PDCCH indicates a new UL, DL or SL transmission for the MAC entity; - drx-RetransmissionTimerDL (per DL Hybrid Automatic Repeat Request (HARQ) process except for the broadcast process): the maximum duration until a DL retransmission is received; - drx-RetransmissionTimerUL (per UL HARQ process): the maximum duration until a grant for UL retransmission is received; - drx-LongCycleStartOffset: the Long DRX cycle and drx-StartOffset which defines the subframe where the Long and Short DRX cycle starts; Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 21 - drx-NonIntegerLongCycleStartOffset : the Long DRX cycle and drx-StartOffset which defines the subframe where the Long and Short DRX cycle start, when the length of the Long DRX cycle and / or the short DRX cycle is not an integer; - drx-ShortCycle (optional): the Short DRX cycle; - drx-NonIntegerShortCycle (optional): the Short DRX cycle whose length is not an integer; - drx-ShortCycleTimer (optional): the duration the UE shall follow the Short DRX cycle; - drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process): the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity; - drx-HARQ-RTT-TimerUL (per UL HARQ process): the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity; - drx-RetransmissionTimerSL (per sidelink process): the maximum duration until a grant for SL retransmission is received; - drx-HARQ-RTT-TimerSL (per sidelink process): the minimum duration before an SL retransmission grant is expected by the MAC entity; - drx-LastTransmissionUL (optional): the configuration to start drx-HARQ-RTT-TimerUL after the last transmission within a bundle; - ps-Wakeup (optional): the configuration to start associated drx-onDurationTimer in case of DCI of Power Saving (DCP) is monitored but not detected; - ps-TransmitOtherPeriodicCSI (optional): the configuration to report periodic Channel State Information (CSI) that is not L1- Reference Signal Received Power (RSRP) on PUCCH during the time duration indicated by drx-onDurationTimer in case DCP is configured but associated drx-onDurationTimer is not started; Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 22 - ps-TransmitPeriodicL1-RSRP configuration to transmit periodic CSI that is L1-RSRP on PUCCH during the time duration indicated by drx-onDurationTimer in case DCP is configured but associated drx-onDurationTimer is not started; - DLHARQ-FeedbackDisabled (optional): the configuration to disable HARQ feedback per DL HARQ process; - uplinkHARQ-Mode (optional): the configuration to set HARQmodeA or HARQmodeB per UL HARQ process; - disableCG-RetransmissionMonitoring (optional): the configuration to disable starting drx- HARQ-RTT-TimerUL for UL transmission over a configured uplink grant; - drx-TimeReferenceSFN (optional): the reference System Frame Number (SFN) used in determining the start time of DRX on durations when short and / or long DRX cycle is not an integer.

[0081] The following UE variable is used for the DRX operation if drx- NonIntegerLongCycleStartOffset is configured: - DRX_SFN_COUNTER: the counter that increments when SFN changes to 0. This counter can be implemented with a maximum value of 65535.

[0082] Serving Cells of a MAC entity may be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and Serving Cells belong to that one DRX group. When two DRX groups are configured, each Serving Cell is assigned to either of the two groups. The DRX parameters that are separately configured for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters that are common to the DRX groups are: drx-SlotOffset, drx- RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx- NonIntegerLongCycleStartOffset, drx-ShortCycle (optional), drx-NonIntegerShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT- TimerUL.

[0083] When DRX is configured, the Active Time for Serving Cells in a DRX group includes the time while: Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 23 - drx-onDurationTimer or drx- configured for the DRX group is running; or - drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL is running on any Serving Cell in the DRX group; or - ra-ContentionResolutionTimer (as described in clause 5.1.5) or msgB-ResponseWindow (as described in clause 5.1.4a) is running; or - a Scheduling Request is sent on PUCCH and is pending (as described in clause 5.4.4 or 5.22.1.5). If this Serving Cell is part of a non-terrestrial network, the Active Time is started after the Scheduling Request transmission that is performed when the SR_COUNTER is 0 for the Scheduling Request (SR) configurations with pending SR(s) plus the UE-gNB Round Trip Time (RTT); or - a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble (as described in clauses 5.1.4 and 5.1.4a); or - there is an ongoing Random Access Channel (RACH)-less Lower-layer Triggered Mobility (LTM) cell switch; or - there is an ongoing RACH-less handover in a terrestrial network.

[0084] The following MAC timers are used for DRX operation in a non-terrestrial network: - HARQ-RTT-TimerDL-NTN (per DL HARQ process configured with HARQ feedback enabled): the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity; - HARQ-RTT-TimerUL-NTN (per UL HARQ process configured with HARQModeA): the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity.

[0085] When DRX is not configured and multicast DRX is configured for a G-RNTI or G- CS-RNTI, the MAC entity shall: 1> monitor the PDCCH as specified in TS 38.213; Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 24 1> if a MAC PDU is received in a DL assignment for unicast; or 1> if the PDCCH indicates a DL unicast transmission: 2> stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process.

[0086] When DRX is configured, the MAC entity shall: 1> if a MAC PDU is received in a configured DL assignment for unicast: 2> if this Serving Cell is configured with DLHARQ-FeedbackDisabled: 3> if the corresponding HARQ process is configured with HARQ feedback enabled: 4> set HARQ-RTT-TimerDL-NTN for the corresponding HARQ process equal to drx- HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value; 4> start the HARQ-RTT-TimerDL-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. 2> else: 3> start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. NOTE 1a: Void. NOTE 1b: Void. 2> stop the drx-RetransmissionTimerDL for the corresponding HARQ process; 2> stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process. 1> if a MAC PDU is transmitted in a configured uplink grant and Listen Before Talk (LBT) failure indication is not received from lower layers: 2> if this Serving Cell is configured with uplinkHARQ-Mode: Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 25 3> if the corresponding HARQ is configured as HARQModeA: 4> set HARQ-RTT-TimerUL-NTN for the corresponding HARQ process equal to drx- HARQ-RTT-TimerUL plus the latest available UE-gNB RTT value; 4> if drx-LastTransmissionUL is configured: 5> start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission. 4> else: 5> start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission. 2> else: 3> if disableCG-RetransmissionMonitoring is not configured for the configured uplink grant: 4> if drx-LastTransmissionUL is configured: 5> start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission. 4> else: 5> start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission. 2> stop the drx-RetransmissionTimerUL for the corresponding HARQ process at the first transmission (within a bundle) of the corresponding PUSCH transmission. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 26 1> if a MAC PDU is transmitted in a sidelink grant: 2> if the PUCCH resource is configured: 3> start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH transmission carrying the SL HARQ feedback; or 3> start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH resource for the SL HARQ feedback when the PUCCH is not transmitted; 3> stop the drx-RetransmissionTimerSL for the corresponding HARQ process. 2> else: 3> start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after the end of the corresponding Physical Sidelink Shared Channel (PSSCH) transmission; 3> stop the drx-RetransmissionTimerSL for the corresponding HARQ process. 1> if a drx-HARQ-RTT-TimerDL expires: 2> if the data of the corresponding HARQ process was not successfully decoded: 3> start the drx-RetransmissionTimerDL for the corresponding HARQ process in the first symbol after the expiry of drx-HARQ-RTT-TimerDL. 1> if a HARQ-RTT-TimerDL-NTN expires: 2> if the data of the corresponding HARQ process was not successfully decoded: 3> start the drx-RetransmissionTimerDL for the corresponding HARQ process in the first symbol after the expiry of HARQ-RTT-TimerDL-NTN. 1> if a drx-HARQ-RTT-TimerUL expires: Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 27 2> start the drx- the corresponding HARQ process in the first symbol after the expiry of drx-HARQ-RTT-TimerUL. 1> if a HARQ-RTT-TimerUL-NTN expires: 2> start the drx-RetransmissionTimerUL for the corresponding HARQ process in the first symbol after the expiry of HARQ-RTT-TimerUL-NTN. 1> if a drx-HARQ-RTT-TimerSL expires: 2> if a HARQ Negative Acknowledgement (NACK) feedback for the corresponding HARQ process is transmitted on PUCCH; or 2> if a HARQ NACK feedback for the corresponding HARQ process is generated but not transmitted on PUCCH; or 2> if the PUCCH resource is not configured for the SL grant: 3> start the drx-RetransmissionTimerSL for the corresponding HARQ process in the first symbol after the expiry of drx-HARQ-RTT-TimerSL. NOTE : The UE handles the drx-RetransmissionTimerSL operation when sl-PUCCH-Config is configured by RRC but PUCCH resource is not scheduled same as when sl- PUCCH-Config is not configured. 1> if a DRX Command MAC CE indicated by PDCCH addressed to C-RNTI or CS-RNTI, or by a configured DL assignment for unicast transmission or a Long DRX Command MAC CE is received: 2> stop drx-onDurationTimer for each DRX group; 2> stop drx-InactivityTimer for each DRX group. 1> if drx-InactivityTimer for a DRX group expires: 2> if the Short DRX cycle is configured: Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 28 3> start or restart drx- this DRX group in the first symbol after the expiry of drx-InactivityTimer; 3> use the Short DRX cycle for this DRX group. 2> else: 3> use the Long DRX cycle for this DRX group. 1> if a DRX Command MAC CE indicated by PDCCH addressed to C-RNTI or CS-RNTI, or by a configured DL assignment for unicast transmission is received: 2> if the Short DRX cycle is configured: 3> start or restart drx-ShortCycleTimer for each DRX group in the first symbol after the end of DRX Command MAC CE reception; 3> use the Short DRX cycle for each DRX group. 2> else: 3> use the Long DRX cycle for each DRX group. 1> if drx-ShortCycleTimer for a DRX group expires: 2> use the Long DRX cycle for this DRX group. 1> if a Long DRX Command MAC CE is received: 2> stop drx-ShortCycleTimer for each DRX group; 2> use the Long DRX cycle for each DRX group. 1> if the drx-NonIntegerLongCycleStartOffset is configured: 2> increment DRX_SFN_COUNTER by 1 in the first symbol of a slot in which SFN changes to 0; 2> if DRX is (re-)configured by RRC: Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 29 3> set DRX_SFN_COUNTER to 0 in first symbol of the slot immediately after the successful completion of the RRC (re-)configuration; 1> if the Short DRX cycle is used for a DRX group and the drx-NonIntegerShortCycle is not configured, and [(SFN × 10) + subframe number] modulo (drx-ShortCycle) = (drx- StartOffset) modulo (drx-ShortCycle); or 1> if the Short DRX cycle is used for a DRX group and the drx-NonIntegerShortCycle is configured, and floor([(DRX_SFN_COUNTER × 10240) + (SFN × 10) + subframe number] modulo (drx-NonIntegerShortCycle)) = floor([(drx-TimeReferenceSFN × 10) + drx- StartOffset] modulo (drx-NonIntegerShortCycle)): 2> start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe. 1> if the Long DRX cycle is used for a DRX group and the drx- NonIntegerLongCycleStartOffset is not configured, and [(SFN × 10) + subframe number] modulo (drx-LongCycle) = drx-StartOffset; or 1> if the Long DRX cycle is used for a DRX group and the drx- NonIntegerLongCycleStartOffset is configured, and floor([(DRX_SFN_COUNTER × 10240) + (SFN × 10) + subframe number] modulo (drx-NonIntegerLongCycle)) = floor([(drx-TimeReferenceSFN × 10) + drx-StartOffset] modulo (drx- NonIntegerLongCycle)): 2> if DCP monitoring is configured for the active DL Bandwidth Part (BWP) as specified in TS 38.213 [6], clause 10.3: 3> if DCP indication associated with the current DRX cycle received from lower layer indicated to start drx-onDurationTimer, as specified in TS 38.213; or 3> if all DCP occasion(s) in time domain, as specified in TS 38.213, associated with the current DRX cycle occurred in Active Time considering grants / assignments / DRX Command MAC CE / Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to start of the last DCP occasion, or during a Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 30 measurement gap, or when the entity monitors for a PDCCH transmission on the search space indicated by recoverySearchSpaceId of the SpCell identified by the C-RNTI while the ra-ResponseWindow is running (as specified in clause 5.1.4); or 3> if ps-Wakeup is configured with value true and DCP indication associated with the current DRX cycle has not been received from lower layers: 4> start drx-onDurationTimer after drx-SlotOffset from the beginning of the subframe. 2> else: 3> start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe. NOTE 2: In case of unaligned SFN across carriers in a cell group, the SFN of the SpCell is used to calculate the DRX duration. 1> if a DRX group is in Active Time: 2> monitor the PDCCH on the Serving Cells in this DRX group as specified in TS 38.213 [6]; 2> if the PDCCH indicates a DL transmission; or 2> if the PDCCH indicates a one-shot HARQ feedback as specified in clause 9.1.4 of TS 38.213; or 2> if the PDCCH indicates a retransmission of HARQ feedback as specified in clause 9.1.5 of TS 38.213: 3> if this Serving Cell is configured with DLHARQ-FeedbackDisabled: 4> if the corresponding HARQ process is configured with HARQ feedback enabled: 5> set HARQ-RTT-TimerDL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value; Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 31 5> start the HARQ-RTT- NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. 3> else: 4> start or restart the drx-HARQ-RTT-TimerDL for the corresponding HARQ process(es) whose HARQ feedback is reported in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. NOTE 3: When HARQ feedback is postponed by PDSCH-to-HARQ_feedback timing indicating an inapplicable k1 value, as specified in TS 38.213, the corresponding transmission opportunity to send the DL HARQ feedback is indicated in a later PDCCH requesting the HARQ-Acknowledgement (ACK) feedback. 3> stop the drx-RetransmissionTimerDL for the corresponding HARQ process(es) whose HARQ feedback is reported; 3> stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process; 3> if the PDSCH-to-HARQ_feedback timing indicate an inapplicable k1 value as specified in TS 38.213: 4> start the drx-RetransmissionTimerDL in the first symbol after the (end of the last) PDSCH transmission (within a bundle) for the corresponding HARQ process. 2> if the PDCCH indicates a UL transmission: 3> if this Serving Cell is configured with uplinkHARQ-Mode: 4> if the corresponding HARQ process is configured as HARQModeA: 5> set HARQ-RTT-TimerUL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerUL plus the latest available UE-gNB RTT value; 5> if drx-LastTransmissionUL is configured: Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 32 6> start the HARQ-RTT- NTN for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission. 5> else: 6> start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission. 3> else: 4> if drx-LastTransmissionUL is configured: 5> start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission. 4> else: 5> start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission. 3> stop the drx-RetransmissionTimerUL for the corresponding HARQ process. 2> if the PDCCH indicates an SL transmission: 3> if the PUCCH resource is configured: 4> start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH transmission carrying the SL HARQ feedback; or 4> start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH resource for the SL HARQ feedback when the PUCCH is not transmitted; Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 33 4> stop the drx- for the corresponding HARQ process. 3> else: 4> start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after end of PDCCH occasion; 4> stop the drx-RetransmissionTimerSL for the corresponding HARQ process. 2> if the PDCCH indicates a new transmission (DL, UL or SL) on a Serving Cell in this DRX group: 3> start or restart drx-InactivityTimer for this DRX group in the first symbol after the end of the PDCCH reception. NOTE 3a: A PDCCH indicating activation of SPS, configured grant type 2, or configured sidelink grant of configured grant Type 2 is considered to indicate a new transmission. NOTE 3b: If the PDCCH reception includes two PDCCH candidates from corresponding search spaces, as described in clause 10.1 in TS 38.213, start or restart drx- InactivityTimer for this DRX group in the first symbol after the end of the PDCCH candidate that ends later in time. 2> if a HARQ process receives DL feedback information and acknowledgement is indicated: 3> stop the drx-RetransmissionTimerUL for the corresponding HARQ process. 1> if DCP monitoring is configured for the active DL BWP as specified in TS 38.213, clause 10.3; and 1> if the current symbol n occurs within drx-onDurationTimer duration; and 1> if drx-onDurationTimer associated with the current DRX cycle is not started as specified in this clause: Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 34 2> if the MAC entity would not be in Time considering grants / assignments / DRX Command MAC CE / Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and 2> if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any of the active BWP(s) of the Serving Cell(s), or if all multicast DRXes would not be in Active Time considering multicast assignments / DRX Command MAC CE for Multicast Broadcast Service (MBS) multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions are configured with multicast DRX: 3> not transmit periodic Sounding Reference Signal (SRS) and semi-persistent SRS defined in TS 38.214; 3> not report semi-persistent CSI configured on PUSCH; 3> not report semi-persistent CSI on PUCCH; 3> if ps-TransmitPeriodicL1-RSRP is not configured with value true: 4> not report periodic CSI that is L1-RSRP on PUCCH. 3> if ps-TransmitOtherPeriodicCSI is not configured with value true: 4> not report periodic CSI that is not L1-RSRP on PUCCH. 1> else: 2> in current symbol n, if a DRX group would not be in Active Time considering grants / assignments scheduled on Serving Cell(s) in this DRX group and DRX Command MAC CE / Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and 2> if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any of the active BWP(s) of the Serving Cell(s), or, in current symbol Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 35 n, if all multicast DRXes to the DRX group would not be in Active Time considering multicast assignments / DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions corresponding to the DRX group are configured with multicast DRX: 3> not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 in this DRX group; 3> not report CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group. 2> if CSI masking (csi-Mask) is setup by upper layers: 3> in current symbol n, if drx-onDurationTimer of a DRX group would not be running considering grants / assignments scheduled on Serving Cell(s) in this DRX group and DRX Command MAC CE / Long DRX Command MAC CE received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and 3> if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any of the active BWP(s) of the Serving Cell(s), or, in current symbol n, if drx-onDurationTimerPTM(s) of all multicast DRXes corresponding to the DRX group would not be running considering DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions corresponding to the DRX group are configured with multicast DRX: 4> not report CSI on PUCCH in this DRX group. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 36 NOTE 4: If a UE multiplexes a CSI on PUCCH with other overlapping UCI(s) according to the procedure specified in TS 38.213 clause 9.2.5 and this CSI multiplexed with other UCI(s) would be reported on a PUCCH resource either outside DRX Active Time of the DRX group in which this PUCCH is configured or outside the on-duration period of the DRX group in which this PUCCH is configured if CSI masking is setup by upper layers, it is up to UE implementation whether to report this CSI multiplexed with other UCI(s).

[0087] The MAC entity shall ensure no rounding error is generated when performing the modulus operation with drx-NonIntegerShortCycle or drx-NonIntegerLongCycle as the divisor.

[0088] Regardless of whether the MAC entity is monitoring PDCCH or not on the Serving Cells in a DRX group, the MAC entity transmits HARQ feedback, aperiodic CSI on PUSCH, and aperiodic SRS defined in TS 38.214 on the Serving Cells in the DRX group when such is expected. The MAC entity needs not to monitor the PDCCH if it is not a complete PDCCH occasion, e.g., the Active Time starts or ends in the middle of a PDCCH occasion.

[0089] Implementations disclosed herein provide for improved and enhanced DRX operation for multimodal data traffic, such as XR-related data traffic. As discussed herein, multimodal data can include data pertaining to multimodal data flows such as voice data, video data, audio data, sensor (e.g., haptic data), and combinations thereof.

[0090] According to implementations, a UE is configured with a first DRX configuration (e.g., a first set of DRX parameters) and a second DRX configuration (e.g., a second set of DRX parameters) for a DRX group and / or a MAC entity, and can switch between the DRX configurations and / or parameters to be applied for a DRX group and / or MAC entity in response to the reception of DL control signaling. In an example, a UE uses as default the first DRX configuration. For instance, based on configuration of the DRX configurations, the UE applies the first DRX configuration. In response to the reception of a predefined DL control signaling the UE applies the second DRX configuration. In at least one example the second DRX configuration includes a drx-InactivityTimer set to a longer value than a drx-InactivityTimer specified by the first DRX configuration. While implementations are discussed herein with reference to a drx- Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 37 InactivityTimer, the disclosed and claimed can pertain to any timer related to DRX, such as for energy savings at a UE and / or NE.

[0091] In implementations, a UE uses a longer drx-InactivityTimer value in response to the reception of a predefined DL control signaling. In at least one example the predefined DL control signaling is a DCI scheduling a PDSCH transmission and indicating that the PDSCH includes multimodal data. In response to the reception of such DCI, a UE starts a drx-InactivityTimer with a second, longer, drx-InactivityTimer value than the previously used drx-InactivityTimer value which was configured within the first DRX configuration. Setting the drx-inactivitiyTimer to a longer value can enable the UE to be awake for a time duration where inter-related multimodal data is expected to be received, e.g., relative (multimodal) delay budget. In at least one example the predefined DL control signaling schedules an uplink transmission.

[0092] According to implementations, a field and / or indicator within a DCI indicates that the UE is to apply a different DRX timer configuration. In at least one example, a new field is introduced in a DCI (e.g., a new DCI format) which indicates to the UE to use a different DRX parameter and / or timer configuration in response to the reception of the DCI. In at least one example the UE starts a different drx-InactivityTimer (e.g., referred to as drx- InactivityTimerMultiModal) rather than a legacy drx-InactivityTimer in response to the reception of the DCI including the field and / or indicator. In at least one example a field of a DCI (e.g., an existing DCI) set to a specific value and / or codepoint or a combination of fields set to specific values and / or codepoints indicates to the UE to use a different drx-InactivityTimer, e.g. drx- InactivityTimerMultiModal. The DCI indicating to start a different drx-InactivityTimer, for instance, schedules a new initial transmission.

[0093] In at least one example a field and / or indicator within a DCI indicates to the UE which of a plurality of configured DRX parameters to apply. For instance, the UE may be configured with more than two drx-InactivityTimer, e.g., for the cases where multiple different relative delay parameters are to be satisfied. In such scenarios the field and / or indicator can indicate which drx- InactivityTimer to apply and / or start.

[0094] In implementations, a DCI addressed to an RNTI (e.g., referred to as (MultiModal) MM- RNTI) can indicate to the UE to use a specific DRX configuration and / or parameter. In at least one Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 38 example, the UE starts, in response to the of a PDCCH addressed to the RNTI, a drx- InactivityTimer from the second set DRX configuration, e.g., referred to as drx- InactivityTimerMultiModal. In at least one example the DCI addressed to the RNTI schedules an initial DL and / or UL transmission. As discussed above the multimodal-specific drx-InactivityTimer can be set to a different (e.g., longer) value as compared to an existing drx-InactivityTimer (e.g., a drx-InactivityTimer configured in the first DRX configuration) to accommodate the relative delay parameters of multimodal traffic. For instance, using the multimodal-specific drx-InactivityTimer can enable the UE to be in ActiveTime during a time period (e.g., relative delay budget) where multimodal traffic is expected.

[0095] In at least one example, a UE starts a predefined DRX timer in response to the reception of a PDSCH including data of a set of LCHs. For instance, the UE starts a predefined drx- InactivityTimer in response to having successfully decoded a PDSCH carrying multimodal data, e.g., data of a LCH which is configured for a multimodal service. In at least one example the UE starts a drx-InactivityTimer configured in the second DRX configuration. The second DRX configuration, for instance, includes a set of multimodal specific DRX parameters such as including a timer referred to as drx-InactivityTimerMultiModal. The UE can apply the second DRX configuration in response to successfully decoding a PDSCH and determining that the transport block (TB) includes data of a set of predefined LCHs, e.g., LCHs configured for multimodal service. In at least one example, a timeline parameter is defined for switching a subset of set of DRX configuration parameters, such as via a DCI. For instance, consider (a) drx-InactivityTimer value (referred to as ‘T1’) of the DRX configuration (e.g., the first DRX configuration) which was applicable to the UE prior to the reception of the DCI switching the subset of set of DRX configuration parameters, and (b) drx-InactivityTimer value (referred to as ‘T2’) of the DRX configuration (e.g., the second DRX configuration) which is applicable to the UE after the reception of the DCI switching the subset of set of DRX configuration parameters. The minimum of T1 and T2, for example, is to be larger than a threshold duration, e.g., which can be defined per Sub-Carrier Spacing (SCS). In an example, ‘min (T1, T2) = 4 slots’ for SCS=30 KHz. Such implementations can provide a UE with sufficient time to switch DRX configuration parameters.

[0096] Implementations also support UE behavior for configured DL assignment of SPS configuration. For instance, a UE starts a drx-InactivityTimer in response to MAC PDU and / or Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 39 PDSCH reception in a configured DL of a SPS configuration. In at least one example, a UE starts an existing configured drx-InactivityTimer when receiving DL data on a SPS resource (e.g. PDSCH, not PDCCH) to maintain the UE in an awake state for further subsequent transmissions and / or receptions. In at least one example, when a UE performs a PUSCH transmission on Configured Grant (CG) PUSCH resources of a CG configuration, the UE starts the drx-InactivityTimer.

[0097] In implementations, a DL SPS configuration includes an IE configuring a drx- InactivityTimer value to be applied by the UE in response to a MAC PDU and / or PDSCH reception in a configured DL assignment of SPS configuration. For instance, the UE starts the configured drx- InactivityTimer in response to having received a MAC PDU on a PDSCH in a configured DL assignment.

[0098] In implementations according to the current specifications, a UE does not start a drx- InactivityTimer in response to a PDSCH reception on a SPS resource (e.g., configured DL assignment) but instead starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in a first symbol after an end of the corresponding transmission carrying the DL HARQ feedback. Based at least on starting a drx-InactivityTimer being configured in an IE in the SPS-Config IE and in response to receipt of a PDSCH / MAC PDU on a configured SPS resource, a UE can be subsequently in DRX ActiveTime while the drx-InactivityTimer is running. This can enable the UE to monitor PDCCH for the subsequent inter-related multimodal data.

[0099] In implementations a NE can configure a specific SPS configuration for multimodal traffic and / or service. In at least one example the IE within the SPS-Config is an optional IE. In case the IE (e.g. drx-InactivityTimer) is not present, a UE may not start the drx-InactivityTimer in response to a reception of a MAC PDU on a configured DL assignment of this SPS configuration. For instance, when a drx-inacitiyTimer is configured for a SPS configuration, the UE starts the drx- InactivityTimer when receiving a PDSCH and / or MAC PDU such as described herein.

[0100] Figure 3 illustrates an IE 300 for SPS configuration in accordance with aspects of the present disclosure. The IE 300, for instance, represents an SPS-Config-XR IE that can be used to configure DL semi-persistent transmission for multimodal traffic. The IE 300 includes a field 302 that signals that the IE 300 signals XR specific information for SPS and a field 304 that configures a Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 40 drx-InactivityTimer for XR traffic. In at least example multiple Downlink SPS configurations may be configured in one BWP of a serving cell. In implementations, SPS configurations for DL transmissions can be configured specifically for multimodal data. A new IE (e.g., the IE 300) can be used which configures semi-persistent DL resources (e.g., configured DL PDSCH resources) for multimodal data. At least some parameters of this SPS configuration can be similar to the legacy SPS configurations with additional parameters according to the disclosed implementations. In at least one example new parameters and / or IE are included in the XR-specific SPS configuration which are multimodal data specific such as described above, e.g., drx-InactivityTimer.

[0101] In implementations, an UL CG configuration includes IE(s) configuring a drx- InactivityTimer to be applied for uplink transmissions performed on the configured uplink grant resources. When a UE performs a PUSCH transmission on a CG PUSCH resources of the CG configuration, the UE can start the drx-InactivityTimer set to the value configured in the CG configuration IE.

[0102] In implementations, configured grant configurations for UL transmissions can be configured specifically for multimodal data. A new IE (e.g., ConfiguredGrantConfig-XR IE) is introduced which configures semi-persistent UL resources (e.g., CG-PUSCH resources) for multimodal data. At least some of the parameters of this new CG configuration can be similar to existing configured grant configurations and include additional parameters according to implementations described herein. In at least one example parameters and / or IE are included in the multimodal-specific CG configuration which are multimodal data specific, such as discussed above, e.g. drx-InactivityTimer.

[0103] In implementations, a UE is configured with a timer which controls the time period during which the UE applies a DRX configuration. In at least one example, the UE starts the timer in response to a switch to a different DRX configuration and maintains the DRX configuration while the timer is running. At the expiry of the timer, the UE can switch (e.g., autonomously) back to a previous DRX configuration. In at least one example, the UE can start the timer upon switching to a different multimodal-specific drx-InactivityTimer, e.g., in response to the reception of a predefined DL signaling such as discussed above. While the timer is running the UE can apply a drx-InactivityTimer configuration (e.g., the second DRX configuration discussed above) which is configured for delay parameters of multimodal data. Upon expiry of the timer the UE can apply the Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 41 previous drx-InactivityTimer configuration, first DRX configuration described above. In at least one example the timer is configured by the network, e.g., via RRC signaling.

[0104] In implementations, the UE indicates in a CG-UCI a set of DRX configuration parameters which can be applicable from a time after the transmission of the CG-UCI. For instance, in case of multimodal transmission of multiple streams and / or in case of a single stream approaching its delay budget, the UE indicates to the NE that the UE will be awake in ActiveTime for an additional time period and is available to monitor PDCCH candidates. In at least one example the length of the extended ActiveTime can be indicated within the CG-UCI. In an alternative or additional example the length of the (additional) ActiveTime can be predefined and / or preconfigured.

[0105] In implementations, a UE is configured with a drx-related timer which controls the DRX ActiveTime of the UE. In at least one example, the UE is in DRX ActiveTime while the drx-related timer is running. According to at least one example the drx-related timer (e.g., also referred as drx- MMTimer) is started in response to the reception of a predefined DL signaling. In at least one example the DL signaling includes a DCI including a field and / or indicator indicating that the accompanying PDSCH carries multimodal data such as described above. In another example the DL signaling includes a DCI addressed to a predefined RNTI, e.g. MM-RNTI. The drx-related timer can allow NE to control the UE’s ActiveTime more efficiently to enable the UE to be in ActiveTime during a time period during which the reception of multimodal data is expected. In at least one example the drx-related timer can be set to the relative delay parameter and / or delay budget of multimodal data and / or multimodal service.

[0106] The following provides details for example implementations of the drx-related timer (e.g. drx-MMTimer) in the DRX procedure as shown: When DRX is configured, the Active Time for Serving Cells in a DRX group includes the time while: - drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or - drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL is running on any Serving Cell in the DRX group; or Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 42 - ra-ContentionResolutionTimer or is running; or - drx-MultiModalTimer is running; or - a Scheduling Request is sent on PUCCH and is pending. If this Serving Cell is part of a non-terrestrial network, the Active Time is started after the Scheduling Request transmission that is performed when the SR_COUNTER is 0 for the SR configurations with pending SR(s) plus the UE-gNB RTT; or - a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble; or - there is an ongoing RACH-less LTM cell switch; or - there is an ongoing RACH-less handover in a terrestrial network.

[0107] In at least one example, a UE stops the drx-related timer (e.g., drx-MultiModalTimer) in response to the reception of a DRX Command MAC CE.

[0108] In implementations, a UE stops monitoring until the expiry of the drx-related timer (e.g., drx-MultiModalTimer as introduced above) for cases that a PDCCH skipping command (e.g., DCI) is received while the timer is running. In at least one example a UE behavior in response to the reception of a PDCCH skipping command is defined to optimize the UE power consumption. In examples such as described above, a UE is in DRX ActiveTime while the drx-related timer (e.g., drx-MultiModalTimer) is running to enable the UE to be ready to receive the multimodal data within a relative delay budget. At the end of a multimodal data burst, an NE may transmit a DCI indicating that the UE is to skip PDCCH monitoring. In at least one example, the UE is to skip PDCCH until the end of the time period while the drx-related timer is running. In at least one example the DCI indicating the PDCCH skipping command is addressed to a specified RNTI, e.g. MM-RNTI. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 43

[0109] In implementations a UE monitors while the UE is expecting to receive multimodal data even though an associated cell is in DTX non-ActiveTime, e.g., a time period where the cell is not expected to transmit DL channels. In at least one example, the UE monitors PDCCH on serving cells in a DRX group while the drx-MultiModalTimer is running (e.g., a drx- related timer as discussed above) such as for cases where a serving cell is not in the cell DTX active period. In at least one example, the reception of multimodal data can be prioritized over procedures for cell (e.g., NE) energy saving. If, for example, the transmission of multimodal has started at the end of the cell DTX Active period, the transmission of the multimodal data may still be completed even though some of the transmission and / or reception time may fall within the cell DTX non- ActiveTime.

[0110] The following describes a procedure for specifying scenarios where a UE is to be ready monitor for DL transmission (e.g., PDCCH), including where a drx-related timer (e.g., drx- MultiModalTimer) is running: 1> if any drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx- RetransmissionTimerSL or drx-MultiModalTimer is running on any Serving Cell in the DRX group of this Serving Cell; or 1> if ra-ContentionResolutionTimer or msgB-ResponseWindow is running; or 1> if a Scheduling Request is sent on PUCCH and is pending; or 1> if a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble: 2> monitor PDCCH on the Serving Cells in the DRX group of this Serving Cell, as specified in 3GPP TS 38.213 and other clauses of this specification.

[0111] In at least one implementation, a UE can apply a second configured drx-InactivityTimer and / or a new multimodal-specific drx timer (e.g. drx-MultiModalTimer) as described above in response to the transmission of a DSR and / or an MultiModal (MM)-DSR, and / or upon reception of an acknowledgement in response to a DSR and / or MM-DSR.

[0112] Figure 4 illustrates an example of a UE 400 in accordance with aspects of the present disclosure. The UE 400 may include a processor 402, a memory 404, a controller 406, and a Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 44 transceiver 408. The processor 402, the the controller 406, or the transceiver 408, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0113] The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0114] The processor 402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 402 may be configured to operate the memory 404. In some other implementations, the memory 404 may be integrated into the processor 402. The processor 402 may be configured to execute computer-readable instructions stored in the memory 404 to cause the UE 400 to perform various functions of the present disclosure.

[0115] The memory 404 may include volatile or non-volatile memory. The memory 404 may store computer-readable, computer-executable code including instructions when executed by the processor 402 cause the UE 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 404 or another type of memory. 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 may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0116] In some implementations, the processor 402 and the memory 404 coupled with the processor 402 may be configured to cause the UE 400 to perform one or more of the functions described herein (e.g., executing, by the processor 402, instructions stored in the memory 404). For example, the processor 402 may support wireless communication at the UE 400 in accordance with Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 45 examples as disclosed herein. The UE 400 configured to or operable to support a means for receiving a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; applying the first set of one or more DRX parameters; and applying, in response to DL signaling, the second set of one or more DRX parameters.

[0117] Additionally, the UE 400 may be configured to support any one or combination of where the first set of one or more DRX parameters includes a first timer configured to a first value and the second set of one or more DRX parameters includes a second timer configured to a second value, where the second value is larger than the first value; the first timer includes a first drx- InactivityTimer and the second timer includes a second drx-InactivityTimer; the DL signaling includes DCI scheduling a PDSCH transmission, and an indication that the PDSCH includes one or more of multimodal data or extended reality data; the DL signaling includes DCI allocating DL resources for an initial transmission; the DCI includes a field set to a predefined value; the DCI is addressed to a predefined RNTI; further including starting a timer in response to applying the second set of one or more DRX parameters; further including applying the first set of one or more DRX parameters in response to expiry of the timer.

[0118] The UE 400 may further be configured to or operable to support a means for receiving configuration including a timer value for a timer to be applied in response to receiving, in a configured DL assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and starting the timer in response to receiving one or more of the MAC PDU or the PDSCH in the configured DL assignment of the SPS configuration.

[0119] Additionally, the UE 400 may be configured to support any one or combination of where the timer includes a drx-InactivityTimer.

[0120] Additionally, or alternatively, the UE 400 may support at least one memory (e.g., the memory 404) and at least one processor (e.g., the processor 402) coupled with the at least one memory and configured to cause the UE to receive a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; apply the first set of one or more DRX parameters; and apply, in response to DL signaling, the second set of one or more DRX parameters. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 46

[0121] Additionally, the UE 400 may be to support any one or combination of where the first set of one or more DRX parameters includes a first timer configured to a first value and the second set of one or more DRX parameters includes a second timer configured to a second value, where the second value is larger than the first value; the first timer includes a first drx- InactivityTimer and the second timer includes a second drx-InactivityTimer; the DL signaling includes DCI scheduling a PDSCH transmission, and an indication that the PDSCH includes one or more of multimodal data or extended reality data; the DL signaling includes DCI allocating DL resources for an initial transmission; the DCI includes a field set to a predefined value; the DCI is addressed to a predefined RNTI; the at least one processor is configured to cause the UE to start a timer in response to applying the second set of one or more DRX parameters; the at least one processor is configured to cause the UE to apply the first set of one or more DRX parameters in response to expiry of the timer.

[0122] Additionally, or alternatively, the UE 400 may support at least one memory (e.g., the memory 404) and at least one processor (e.g., the processor 402) coupled with the at least one memory and configured to cause the UE to receive configuration including a timer value for a timer to be applied in response to receiving, in a configured DL assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and start the timer in response to receiving one or more of the MAC PDU or the PDSCH in the configured DL assignment of the SPS configuration.

[0123] Additionally, the UE 400 may be configured to support any one or combination of where the timer includes a drx-InactivityTimer.

[0124] The controller 406 may manage input and output signals for the UE 400. The controller 406 may also manage peripherals not integrated into the UE 400. In some implementations, the controller 406 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 406 may be implemented as part of the processor 402.

[0125] In some implementations, the UE 400 may include at least one transceiver 408. In some other implementations, the UE 400 may have more than one transceiver 408. The transceiver 408 may represent a wireless transceiver. The transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 47

[0126] A receiver chain 410 may be to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 410 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 410 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 410 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 410 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0127] A transmitter chain 412 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 412 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 412 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0128] Figure 5 illustrates an example of a processor 500 in accordance with aspects of the present disclosure. The processor 500 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 500 may include a controller 502 configured to perform various operations in accordance with examples as described herein. The processor 500 may optionally include at least one memory 504, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 500 may optionally include one or more arithmetic-logic units (ALUs) 506. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0129] The processor 500 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 48 may include one or more cores, one or more (e.g., memory local to or included in the processor chipset (e.g., the processor 500) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0130] The controller 502 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein. For example, the controller 502 may operate as a control unit of the processor 500, generating control signals that manage the operation of various components of the processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0131] The controller 502 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 504 and determine subsequent instruction(s) to be executed to cause the processor 500 to support various operations in accordance with examples as described herein. The controller 502 may be configured to track memory addresses of instructions associated with the memory 504. The controller 502 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 502 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 502 may be configured to manage flow of data within the processor 500. The controller 502 may be configured to control transfer of data between registers, ALUs 506, and other functional units of the processor 500.

[0132] The memory 504 may include one or more caches (e.g., memory local to or included in the processor 500 or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 504 may reside within or on a processor chipset (e.g., local to the processor 500). In some other implementations, the memory 504 may reside external to the processor chipset (e.g., remote to the processor 500). Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 49

[0133] The memory 504 may store readable, computer-executable code including instructions that, when executed by the processor 500, cause the processor 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 502 and / or the processor 500 may be configured to execute computer-readable instructions stored in the memory 504 to cause the processor 500 to perform various functions. For example, the processor 500 and / or the controller 502 may be coupled with or to the memory 504, the processor 500, and the controller 502, and may be configured to perform various functions described herein. In some examples, the processor 500 may include multiple processors and the memory 504 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0134] The one or more ALUs 506 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 506 may reside within or on a processor chipset (e.g., the processor 500). In some other implementations, the one or more ALUs 506 may reside external to the processor chipset (e.g., the processor 500). One or more ALUs 506 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 506 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 506 may be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 506 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 506 to handle conditional operations, comparisons, and bitwise operations.

[0135] The processor 500 may support wireless communication in accordance with examples as disclosed herein. The processor 500 may be configured to or operable to support at least one controller (e.g., the controller 502) coupled with at least one memory (e.g., the memory 504) and configured to cause the processor to receive a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; apply the first set of one or more DRX parameters; and apply, in response to DL signaling, the second set of one or more DRX parameters. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 50

[0136] Additionally, the processor 500 configured to or operable to support any one or combination of where the first set of one or more DRX parameters includes a first timer configured to a first value and the second set of one or more DRX parameters includes a second timer configured to a second value, where the second value is larger than the first value; the first timer includes a first drx-InactivityTimer and the second timer includes a second drx-InactivityTimer; the DL signaling includes DCI scheduling a PDSCH transmission, and an indication that the PDSCH includes one or more of multimodal data or extended reality data; the DL signaling includes DCI allocating DL resources for an initial transmission; the DCI includes a field set to a predefined value; the DCI is addressed to a predefined RNTI; the at least one controller is configured to cause the processor to start a timer in response to applying the second set of one or more DRX parameters; the at least one controller is configured to cause the processor to apply the first set of one or more DRX parameters in response to expiry of the timer.

[0137] The processor 500 may be configured to or operable to support at least one controller (e.g., the controller 502) coupled with at least one memory (e.g., the memory 504) and configured to cause the processor to receive configuration including a timer value for a timer to be applied in response to receiving, in a configured DL assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and start the timer in response to receiving one or more of the MAC PDU or the PDSCH in the configured DL assignment of the SPS configuration.

[0138] Additionally, the processor 500 may be configured to or operable to support any one or combination of where the timer includes a drx-InactivityTimer.

[0139] The processor 500 may support wireless communication in accordance with examples as disclosed herein. The processor 500 may be configured to or operable to support at least one controller (e.g., the controller 502) coupled with at least one memory (e.g., the memory 504) and configured to cause the processor to transmit a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; and transmit downlink signaling indicating to apply the second set of one or more DRX parameters.

[0140] Additionally, the processor 500 may be configured to or operable to support any one or combination of where the first set of one or more DRX parameters includes a first timer configured to a first value and the second set of one or more DRX parameters includes a second timer Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 51 configured to a second value, where the second is larger than the first value; the first timer includes a first drx-InactivityTimer and the second timer includes a second drx-InactivityTimer; the downlink signaling includes DCI scheduling a PDSCH transmission, and an indication that the PDSCH includes one or more of multimodal data or extended reality data; the downlink signaling includes DCI allocating downlink resources for an initial transmission; the DCI includes a field set to a predefined value; the DCI is addressed to a predefined RNTI.

[0141] The processor 500 may support wireless communication in accordance with examples as disclosed herein. The processor 500 may be configured to or operable to support at least one controller (e.g., the controller 502) coupled with at least one memory (e.g., the memory 504) and configured to cause the processor to transmit configuration including a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a SPS configuration, one or more of MAC PDU or a PDSCH; and transmit one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration.

[0142] Additionally, the processor 500 may be configured to or operable to support any one or combination of where the timer includes a drx-InactivityTimer.

[0143] Figure 6 illustrates an example of a NE 600 in accordance with aspects of the present disclosure. The NE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0144] The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 52

[0145] The processor 602 may include an hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604 to cause the NE 600 to perform various functions of the present disclosure.

[0146] The memory 604 may include volatile or non-volatile memory. The memory 604 may store computer-readable, computer-executable code including instructions when executed by the processor 602 cause the NE 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 604 or another type of memory. 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 may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0147] In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to cause the NE 600 to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604). For example, the processor 602 may support wireless communication at the NE 600 in accordance with examples as disclosed herein. The NE 600 may be configured to or operable to support a means for transmitting a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; and transmitting DL signaling indicating to apply the second set of one or more DRX parameters.

[0148] Additionally, the NE 600 may be configured to or operable to support any one or combination of where the first set of one or more DRX parameters includes a first timer configured to a first value and the second set of one or more DRX parameters includes a second timer configured to a second value, where the second value is larger than the first value; the first timer includes a first drx-InactivityTimer and the second timer includes a second drx-InactivityTimer; the DL signaling includes DCI scheduling a PDSCH transmission, and an indication that the PDSCH includes one or more of multimodal data or extended reality data; the DL signaling includes DCI Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 53 allocating DL resources for an initial the DCI includes a field set to a predefined value; the DCI is addressed to a predefined RNTI.

[0149] The NE 600 may be configured to or operable to support a means for transmitting configuration including a timer value for a timer to be applied in response to receiving, in a configured DL assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and transmitting one or more of the MAC PDU or the PDSCH in the configured DL assignment of the SPS configuration.

[0150] Additionally, the NE 600 may be configured to or operable to support any one or combination of where the timer includes a drx-InactivityTimer.

[0151] Additionally, or alternatively, the NE 600 may support at least one memory (e.g., the memory 604) and at least one processor (e.g., the processor 602) coupled with the at least one memory and configured to cause the NE to transmit a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters; and transmit DL signaling indicating to apply the second set of one or more DRX parameters.

[0152] Additionally, the NE 600 may be configured to support any one or combination of where the first set of one or more DRX parameters includes a first timer configured to a first value and the second set of one or more DRX parameters includes a second timer configured to a second value, where the second value is larger than the first value; the first timer includes a first drx- InactivityTimer and the second timer includes a second drx-InactivityTimer; the DL signaling includes DCI scheduling a PDSCH transmission, and an indication that the PDSCH includes one or more of multimodal data or extended reality data; the DL signaling includes DCI allocating DL resources for an initial transmission; the DCI includes a field set to a predefined value; the DCI is addressed to a predefined RNTI.

[0153] Additionally, or alternatively, the NE 600 may support at least one memory (e.g., the memory 604) and at least one processor (e.g., the processor 602) coupled with the at least one memory and configured to cause the NE to transmit configuration including a timer value for a timer to be applied in response to receiving, in a configured DL assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH; and transmit one or more of the MAC PDU or the PDSCH in the configured DL assignment of the SPS configuration. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 54

[0154] Additionally, the NE 600 may be to support any one or combination of where the timer includes a drx-InactivityTimer.

[0155] The controller 606 may manage input and output signals for the NE 600. The controller 606 may also manage peripherals not integrated into the NE 600. In some implementations, the controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 606 may be implemented as part of the processor 602.

[0156] In some implementations, the NE 600 may include at least one transceiver 608. In some other implementations, the NE 600 may have more than one transceiver 608. The transceiver 608 may represent a wireless transceiver. The transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0157] A receiver chain 610 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 610 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 610 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 610 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0158] A transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 55

[0159] Figure 7 illustrates a flowchart of 700 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0160] At 702, the method may include receiving a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters. The operations of 702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 702 may be performed by a UE as described with reference to Figure 4.

[0161] At 704, the method may include applying the first set of one or more DRX parameters. The operations of 704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 704 may be performed by a UE as described with reference to Figure 4.

[0162] At 706, the method may include applying, in response to DL signaling, the second set of one or more DRX parameters. The operations of 706 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 706 may be performed a UE as described with reference to Figure 4.

[0163] Figure 8 illustrates a flowchart of a method 800 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0164] At 802, the method may include receiving configuration including a timer value for a timer to be applied in response to receiving, in a configured DL assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH. The operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a UE as described with reference to Figure 4. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 56

[0165] At 804, the method may include the timer in response to receiving one or more of the MAC PDU or the PDSCH in the configured DL assignment of the SPS configuration. The operations of 804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 804 may be performed by a UE as described with reference to Figure 4.

[0166] Figure 9 illustrates a flowchart of a method 900 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0167] At 902, the method may include transmitting a configuration including a first set of one or more DRX parameters and a second set of one or more DRX parameters. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a NE as described with reference to Figure 6.

[0168] At 904, the method may include transmitting DL signaling indicating to apply the second set of one or more DRX parameters. The operations of 904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 904 may be performed by a NE as described with reference to Figure 6.

[0169] Figure 10 illustrates a flowchart of a method 1000 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0170] At 1002, the method may include transmitting configuration including a timer value for a timer to be applied in response to receiving, in a configured DL assignment of a SPS configuration, one or more of a MAC PDU or a PDSCH. The operations of 1002 may be performed Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 57 in accordance with examples as described In some implementations, aspects of the operations of 1002 may be performed by a NE as described with reference to Figure 6.

[0171] At 1004, the method may include transmitting one or more of the MAC PDU or the PDSCH in the configured DL assignment of the SPS configuration. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a NE as described with reference to Figure 6.

[0172] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not 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. Attorney Ref. No. SMM920240023-WO-PCT

Claims

Lenovo Ref. No. SMM920240023-WO-PCT 58 What is claimed is:

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 operable to cause the UE to: receive a configuration comprising a first set of one or more discontinuous reception (DRX) parameters and a second set of one or more DRX parameters; apply the first set of one or more DRX parameters; and apply, in response to downlink signaling, the second set of one or more DRX parameters.

2. The UE of claim 1, wherein the first set of one or more DRX parameters comprises a first timer configured to a first value and the second set of one or more DRX parameters comprises a second timer configured to a second value, wherein the second value is larger than the first value.

3. The UE of claim 2, wherein the first timer comprises a first drx-InactivityTimer and the second timer comprises a second drx-InactivityTimer.

4. The UE of claim 1, wherein the downlink signaling comprises downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) transmission, and an indication that the PDSCH comprises one or more of multimodal data or extended reality data.

5. The UE of claim 1, wherein the downlink signaling comprises downlink control information (DCI) allocating downlink resources for an initial transmission.

6. The UE of claim 5, wherein the DCI comprises a field set to a predefined value.

7. The UE of claim 5, wherein the DCI is addressed to a predefined radio network temporary identifier (RNTI). Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 59 8. The UE of claim 1, wherein the at least one processor is operable to cause the UE to start a timer in response to applying the second set of one or more DRX parameters.

9. The UE of claim 8, wherein the at least one processor is operable to cause the UE to apply the first set of one or more DRX parameters in response to expiry of the timer.

10. 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 operable to cause the UE to: receive configuration comprising a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a semi-persistent scheduling (SPS) configuration, one or more of a medium access control (MAC) protocol data unit (PDU) or a physical downlink shared channel (PDSCH); and start the timer in response to receiving one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration.

11. The UE of claim 10, wherein the timer comprises a drx-InactivityTimer.

12. A network equipment for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the network equipment to: transmit a configuration comprising a first set of one or more discontinuous reception (DRX) parameters and a second set of one or more DRX parameters; and transmit downlink signaling indicating to apply the second set of one or more DRX parameters.

13. The network equipment of claim 12, wherein the first set of one or more DRX parameters comprises a first timer configured to a first value and the second set of one or more DRX Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 60 parameters comprises a second timer a second value, wherein the second value is larger than the first value.

14. The network equipment of claim 13, wherein the first timer comprises a first drx- InactivityTimer and the second timer comprises a second drx-InactivityTimer.

15. The network equipment of claim 12, wherein the downlink signaling comprises downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) transmission, and an indication that the PDSCH comprises one or more of multimodal data or extended reality data.

16. The network equipment of claim 12, wherein the downlink signaling comprises downlink control information (DCI) allocating downlink resources for an initial transmission.

17. The network equipment of claim 16, wherein the DCI comprises a field set to a predefined value.

18. The network equipment of claim 16, wherein the DCI is addressed to a predefined radio network temporary identifier (RNTI).

19. A network equipment for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the network equipment to: transmit configuration comprising a timer value for a timer to be applied in response to receiving, in a configured downlink assignment of a semi-persistent scheduling (SPS) configuration, one or more of a medium access control (MAC) protocol data unit (PDU) or a physical downlink shared channel (PDSCH); and transmit one or more of the MAC PDU or the PDSCH in the configured downlink assignment of the SPS configuration. Attorney Ref. No. SMM920240023-WO-PCTLenovo Ref. No. SMM920240023-WO-PCT 61 20. The network equipment of 19, wherein the timer comprises a drx- InactivityTimer. Attorney Ref. No. SMM920240023-WO-PCT

Images