Timing control in wireless communications

Abstract

Aspects of the present disclosure relate to methods, devices and systems for supporting timing control in wireless communications. For example, for augmented reality (XR) traffic, embodiments provide enhanced scheduling through a network entity to improve radio resource efficiency and capacity. For example, in the case where DRX ActiveTimes of different DRX configurations overlap and in the case where DRX timer values of different DRX configurations are different, embodiments provide a method for notifying a UE of timer configuration information. Further, embodiments are provided for configuring transmission of a scheduling request (SR) by a UE, such as to enable the UE to delay transmission of the SR to avoid an excessive extension of active time. Further, embodiments are provided for configuring dynamic adaptation of a DRX timer, such as for enabling a UE to determine conditions for updating a DRX timer.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Patent Application No. 63 / 359,383, filed on July 8, 2022, entitled “TIMING CONTROL IN WIRELESS COMMUNICATIONS,” the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications and, more particularly, to timing control in wireless communications. Background Art

[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may be further referred to as an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. Each network communication device (e.g., a base station) may support wireless communication of one or more user communication devices, which may be further referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of a wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technologies, fourth generation (4G) radio access technologies, fifth generation (5G) radio access technologies, and other suitable radio access technologies after 5G (e.g., sixth generation (6G)).

[0005] Some wireless communication systems provide methods for configuring different timers related to wireless communication, such as timers related to discontinuous reception (DRX). However, such systems may implement static timer configurations that are not adaptable to different data traffic types. Summary of the invention

[0006] The present disclosure relates to methods, devices and systems for supporting timing control in wireless communications. For example, for extended reality (XR) services, an implementation provides enhanced scheduling through a network entity to improve wireless resource efficiency and capacity. For example, in the case where the DRX ActiveTimes of different DRX configurations overlap and the DRX timer values ​​of different DRX configurations are different, an implementation provides a method for notifying the UE of timer configuration information. In addition, an implementation is provided for configuring the UE to transmit a scheduling request (SR), such as to enable the UE to delay sending the SR to avoid an extension of the active time. Further, an implementation is provided for configuring dynamic adaptation of the DRX timer, such as to enable the UE to determine the conditions for updating the DRX timer.

[0007] By utilizing the described techniques, timer configuration may be controlled and thus power consumption (eg, of a UE) may be reduced and signaling overhead for, eg, UEs and network entities may be reduced.

[0008] Some implementations of the methods and apparatus described herein may further include receiving, at a first time instance, downlink control information (DCI), the downlink control information allocating a resource set for a hybrid automatic repeat request (HARQ) process, wherein the DCI includes a field indicating whether to start a timer; and starting the timer at a second time instance, at least in part based on the field indicating the start of the timer.

[0009] Some implementations of the methods and apparatus described herein may further include: wherein the DCI allocates a downlink resource set for a HARQ process; wherein the second time instance is the first symbol after the end of transmission of HARQ feedback for a downlink transmission allocated by the DCI; wherein the timer is drx-HARQ-RTT-TimerDL (where RTT is round trip time); wherein the timer is drx-HARQ-RTT-TimerUL; wherein the timer is drx-inactivityTimer; wherein the second time instance is the first symbol after the end of reception of the DCI; wherein the DCI further includes an indication of whether to enable or disable HARQ feedback; wherein the DCI further includes an indication of not starting the timer if a packet delay budget (PDB) is below a threshold; wherein the DCI further includes an indication that the device will transition to a sleep mode after a transmission associated with the downlink resources; wherein the DCI further includes an indication of the end of a data burst after which the timer is not started.

[0010] Some implementations of the methods and apparatus described herein may further include receiving a notification identifying a radio resource and a DRX configuration; selecting a DRX timer from a plurality of different DRX timers based on the DRX configuration; and configuring the DRX timer.

[0011] Some implementations of the methods and apparatus described herein may further include: wherein the notification includes a DRX configuration identifier; wherein the notification is received as part of a DCI; wherein, in the case where the notification includes multiple DRX configurations, the method further includes starting two or more of a plurality of DRX timers corresponding to the plurality of DRX configurations; wherein the notification includes multiple DRX configurations and indicates one or more of a search space or a control resource set (CORESET) for each of the DRX configurations; wherein, in the case where the notification includes multiple DRX configurations, the method further includes applying a predefined rule based on the plurality of DRX configurations to determine which of the plurality of DRX timers to start.

[0012] Some implementations of the methods and apparatus described herein may further include receiving a notification identifying a maximum delay time for sending a scheduling request; and transmitting the scheduling request at a time instance determined based at least in part on the maximum delay time.

[0013] Some implementations of the methods and devices described herein may further include applying a maximum delay time to delay a scheduling request until a time instance; wherein the maximum delay time is based at least in part on a remaining PDB; when the device is in an active DRX state, transmitting the scheduling request before an expiration of a scheduling request timer configured at least in part based on the maximum delay time; and when the device is in an inactive DRX state, transmitting the scheduling request after the expiration of the scheduling request timer.

[0014] Some implementations of the methods and apparatus described herein may further include receiving a notification including configuration information indicating whether to start one or more timers in response to a physical uplink shared channel (PUSCH) transmitted on a HARQ process; and operating the one or more timers based on the configuration information in response to the PUSCH transmitted on the HARQ process.

[0015] Some implementations of the methods and apparatus described herein may further include: wherein one or more timers include a drx-HARQ-RTT-TimerUL timer; wherein the configuration information further specifies whether to monitor a physical downlink control channel (PDCCH) for retransmission authorization or to perform one or more of HARQ transmissions on a PUSCH; wherein the configuration information includes: a first HARQ process configuration, for which one or more timers are started in response to a PUSCH transmitted on the HARQ process; and a second HARQ process configuration, for which one or more timers are not started in response to a PUSCH transmitted on the HARQ process; wherein operating one or more timers in response to a PUSCH transmitted on the HARQ process includes: starting one or more timers based on the first HARQ process configuration; or not starting one or more timers based on the second HARQ process configuration.

[0016] Some implementations of the methods and apparatus described herein may further include receiving a notification including configuration information, the configuration information including an uplink configured grant (CG) and an indication of whether to start one or more timers in response to an uplink transmission on the uplink CG; and operating one or more timers based on the configuration information in response to an uplink transmission on the uplink CG.

[0017] Some implementations of the methods and apparatus described herein may further include: wherein one or more timers include one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer; wherein the configuration information includes an indication of not starting one or more timers in response to an uplink transmission of a specific data type on an uplink CG; wherein the configuration information includes one or more timer values ​​applied to the one or more timers in response to an uplink transmission on the uplink CG; wherein operating one or more timers in response to an uplink transmission on the uplink CG includes applying one or timer values ​​to the one or more timers; wherein the configuration information includes an uplink CG configuration for XR data transmission on the uplink CG; applying the uplink CG configuration for XR data transmission to the uplink CG; and transmitting XR data on the uplink CG configured for XR data transmission.

[0018] Some implementations of the methods and apparatus described herein may further include generating a DCI that allocates a set of resources for a HARQ process, wherein the DCI includes a field indicating whether to start a timer; and transmitting the DCI to the UE.

[0019] Some implementations of the methods and apparatus described herein may further include: wherein the timer is a drx-HARQ-RTT-TimerDL; wherein the timer is a drx-inactivityTimer; wherein the DCI further includes an indication of whether HARQ feedback is enabled or disabled; wherein the DCI further includes an indication of not starting the timer if the PDB is below a threshold; wherein the DCI further includes an indication that the device will transition to a sleep mode after a transmission associated with downlink resources; wherein the DCI further includes an indication of the end of a data burst after which the timer is started.

[0020] Some implementations of the methods and apparatus described herein may further include generating a notification identifying the wireless resources and the DRX configuration; and transmitting the notification to the UE.

[0021] Some implementations of the methods and apparatus described herein may further include: wherein the notification includes a DRX configuration identifier; wherein the notification is transmitted as part of a DCI; wherein the notification includes multiple DRX configurations; wherein the notification includes multiple DRX configurations and indicates one or more of a search space or a CORESET for each of the DRX configurations.

[0022] Some implementations of the methods and apparatus described herein may further include generating a notification identifying a maximum delay time for sending a scheduling request; and transmitting the notification to the UE.

[0023] Some implementations of the methods and apparatus described herein may further include: wherein the maximum delay time is based at least in part on the remaining PDB; wherein the notification further includes instructions indicating: when the UE is in an active DRX state, transmitting a scheduling request before expiration of a scheduling request timer configured at least in part based on the maximum delay time; and when the UE is in an inactive DRX state, transmitting a scheduling request after expiration of the scheduling request timer.

[0024] Some implementations of the methods and apparatus described herein may further include generating a notification including configuration information indicating whether to start one or more timers in response to a PUSCH transmitted on a HARQ process; and transmitting the notification to the UE.

[0025] Some implementations of the methods and apparatus described herein may further include: wherein the one or more timers include a drx-HARQ-RTT-TimerUL timer; wherein the configuration information further specifies whether to monitor a retransmission grant of a PDCCH or to perform one or more of a HARQ transmission on a PUSCH; wherein the configuration information includes: a first HARQ process configuration, for which one or more timers are started in response to a PUSCH transmitted on the HARQ process; and a second HARQ process configuration, for which one or more timers are not started in response to a PUSCH transmitted on the HARQ process.

[0026] Some implementations of the methods and apparatus described herein may further include generating a notification including configuration information including an uplink CG and an indication of whether to start one or more timers in response to an uplink transmission on the uplink CG; and transmitting the notification to the UE.

[0027] Some implementations of the methods and apparatus described herein may further include: wherein the one or more timers include one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer; wherein the configuration information includes an indication of not starting one or more timers in response to an uplink transmission of a specific data type on an uplink CG; wherein the configuration information includes one or more timer values ​​applied to the one or more timers in response to an uplink transmission on the uplink CG; wherein the configuration information includes an uplink CG configuration for XR data transmission on the uplink CG.

[0028] Some implementations of the methods and apparatus described herein may further include receiving a notification including configuration information, the configuration information including an uplink configured grant (CG) configuration and an indication of whether to start one or more timers in response to an uplink transmission on a physical uplink shared channel (PUSCH) resource configured by the uplink configured grant; and operating one or more timers based on the configuration information in response to an uplink transmission on a CG PUSCH resource; the one or more timers including one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer; the configuration information including an indication of not starting one or more timers in response to an uplink transmission on a CG PUSCH resource; the configuration information including an indication of not starting one or more timers in a first symbol after an end of a PUSCH transmission.

[0029] Some implementations of the methods and apparatus described herein may further include generating a notification including configuration information, the configuration information including an uplink configured grant (CG) configuration and an indication of whether to start one or more timers in response to an uplink transmission on a physical uplink shared channel (PUSCH) resource configured by the uplink configured grant; and transmitting the notification to a UE; the one or more timers including one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer; and the configuration information including an indication of not starting one or more timers in response to an uplink transmission on a CG PUSCH resource. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 An example of a wireless communication system supporting timing control in wireless communications according to aspects of the present disclosure is described.

[0031] Figure 2 An example of multiple data streams used to carry XR services is described.

[0032] Figure 3 An example of multiple data streams used to carry XR services is described.

[0033] Figure 4 and 5 Different corresponding portions of an information element (IE) supporting timing control in wireless communications according to aspects of the present disclosure are described.

[0034] Figure 6 and 7 An example of a block diagram illustrating an apparatus supporting timing control in wireless communications according to aspects of the present disclosure.

[0035] Figures 8 to 18 A flow chart illustrating a method of supporting timing control in wireless communications according to aspects of the present disclosure. DETAILED DESCRIPTION

[0036] In wireless communication systems, different types of data services may exhibit different characteristics, such as packet size, service periodicity, packet type, etc. For example, XR service characteristics include features such as variable packet arrival rate (e.g., packets arrive at 30 to 120 frames per second with some jitter), packets have variable and large packet sizes, B / P frames are dependent on I frames, there are multiple services / data streams in the uplink (e.g., gesture and video scenes), etc. In addition, the latency parameters of XR services on the radio access network (RAN) side (e.g., air interface) can be modeled as PDB. For example, PDB is the time budget for transmitting a packet from a network entity (e.g., gNB) to a UE over the air. A delay budget can also be defined for an application data unit (ADU).

[0037] When considering end-user XR devices, such devices are typically mobile and of small size, and therefore may have limited battery power resources. The current DRX mechanism is a power saving mechanism that is intended to achieve power saving gains for UEs in the RRC_CONNECTED state. However, some characteristics of XR services are not addressed by the current DRX mechanism and may limit UE power savings. For example, from a power saving perspective, a single DRX configuration may be inefficient because, as discussed above, some service types (e.g., XR services) exhibit different characteristics that cannot be accurately covered by a single DRX configuration. In addition, in some wireless communication implementations for DRX, the UE may extend the ActiveTime in response to the reception of a PDCCH, such as in scenarios where there is no upcoming HARQ retransmission (e.g., due to a PDB) and / or there is no upcoming initial transmission (e.g., for the last packet of a protocol data unit (PDU) set).

[0038] Therefore, the present disclosure provides technology to support timing control in wireless communications. For example, for XR services, the implementation scheme provides enhanced scheduling through network entities to improve wireless resource efficiency and capacity. For example, in the case where the DRX ActiveTimes of different DRX configurations overlap and / or the DRX timer values ​​of different DRX configurations are different, the implementation scheme provides a method for notifying the UE of timer configuration information. In addition, an implementation scheme is provided for configuring the UE to transmit SR, for example, to enable the UE to delay sending the SR to avoid excessive extension of the active time. Furthermore, an implementation scheme is provided for configuring dynamic adaptation of the DRX timer, for example, to enable the UE to determine the conditions for updating the DRX timer.

[0039] Therefore, embodiments provide signaling (e.g., via DCI) to enable a network entity to dynamically control whether a UE is to start a DRX-related timer, e.g., based on whether a subsequent transmission may occur. In addition, an uplink configured CG configuration is provided, which includes an IE indicating whether an uplink (UL) transmission on a CG resource is to trigger the start of different timers. For example, for a CG configuration for XR services with strict latency requirements, the UE is instructed not to monitor the PDCCH for potential retransmission grants, e.g., a DCI with a configured scheduling (CS)-radio network temporary identifier (RNTI).

[0040] Thus, by utilizing the described techniques, UE power consumption and signaling overhead between the UE and network entities may be reduced.

[0041] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure will be further illustrated and described with reference to apparatus diagrams and flow charts.

[0042] Figure 1 An example of a wireless communication system 100 that supports timing control in wireless communication according to aspects of the present disclosure is described. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

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

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

[0045] One or more UEs 104 may be dispersed throughout a geographical area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be fixed in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0046] One or more UEs 104 may be devices of different forms or capabilities. Figure 1Some examples of UE 104 are illustrated in FIG. UE 104 may be able to communicate with various types of devices, such as network entity 102, other UE 104, or network equipment (e.g., core network 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network equipment), such as Figure 1 Additionally or alternatively, UE 104 can support communications with other network entities 102 or UE 104 that can act as relays in wireless communication system 100.

[0047] The UE 104 may also be capable of supporting direct wireless communication with other UEs 104 via a communication link 114. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, V2X deployments, or cellular V2X deployments, the communication link 114 may be referred to as a side link. For example, the UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0048] The network entity 102 may support communication with the core network 106 or with another network entity 102 or both. In general, the network entity 102 may interface with the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2 or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn or another network interface). In some embodiments, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other embodiments, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some embodiments, one or more network entities 102 may include subcomponents, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

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

[0050] A RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 102 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0051] The functional division between CU, DU and RU may be flexible, and different functionalities may be supported depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU or RU. For example, functional division of the protocol stack may be adopted between the CU and the DU, so that the CU may support one or more layers of the protocol stack, and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU may be connected to one or more DUs or RUs, and one or more DUs or RUs may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, MAC layer) functionality and signaling, and each may be at least partially controlled by the CU.

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

[0053] The CU may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DU may be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul communication links or fronthaul communication links may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by the respective network entities 102 communicating via such communication links.

[0054] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)) and user plane entities that route packets to or interconnect to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or 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 bearer, signal bearer, etc.) of one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0055] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a PDU session or the like) with the core network 106 via the network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using 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 core network 106 (e.g., one or more network functions of the core network 106).

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

[0057] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. A first parameter set (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third parameter set (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 parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0058] The time intervals of resources (e.g., communication resources) 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 embodiments, each frame may include a plurality of subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0059] In addition or alternatively, the time intervals of resources (e.g., communication resources) may be organized according to time slots. For example, a subframe may include the number of time slots (e.g., quantity). Each time slot may include the number of symbols (e.g., quantity) (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some embodiments, the number of time slots (e.g., quantity) of a subframe may depend on a parameter set. For a conventional cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60kHz subcarrier spacing), a time slot may include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame of a conventional cyclic prefix and an extended cyclic prefix may depend on a parameter set. It should be understood that references to a first parameter set (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15kHz) may be used interchangeably between subframes and time slots.

[0060] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. By way of example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, the network entity 102 and the UE 104 may perform wireless communications over one or more of the operating frequency bands. In some embodiments, FR1 may be used by the network entity 102 and the UE 104 as well as other equipment or devices for cellular communication services (e.g., control information, data). In some implementations, FR2 may be used by the network entity 102 and the UE 104 and other equipment or devices for short-range, high data rate capabilities.

[0061] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with the following parameter sets: a first parameter set (e.g., μ=0) including a 15 kHz subcarrier spacing; a second parameter set (e.g., μ=1) including a 30 kHz subcarrier spacing; and a third parameter set (e.g., μ=2) including a 60 kHz subcarrier spacing. FR2 may be associated with one or more parameter sets (e.g., at least 2 parameter sets). For example, FR2 may be associated with the following parameter sets: a third parameter set (e.g., μ=2) including a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ=3) including a 120 kHz subcarrier spacing.

[0062] According to an implementation scheme for timing control in wireless communication, the network entity 102 may generate a configuration notification 120 and communicate the configuration notification 120 to the UE 104. For example, the configuration notification 120 includes timing related information such as DRX related timers, timing for sending scheduling requests, etc. In at least one implementation, the configuration notification 120 includes CG resources. Based on the configuration information in the configuration notification 120, the UE 104 performs a configuration process 122. For example, as part of the configuration process 122, the UE 104 configures and / or operates different timers, such as DRX related timers, timing related to transmitting SRs, timers related to HARQ processes, etc. In addition, the UE 104 may perform data transmission 124 based at least on one or more timers. For example, the data transmission 124 may include various types of data transmissions, such as PUSCH transmissions, SR transmissions, HARQ related transmissions, etc.

[0063] XR is an umbrella term used to refer to different types of realities, including:

[0064] Virtual reality (VR) is the delivery of a rendered version of a visual and audio scene. The rendering is designed to mimic the visual and auditory stimulation of the real world as naturally as possible to the observer or user as the observer or user moves within the range defined by the application. Virtual reality is usually, but not necessarily, performed while the user is wearing a head-mounted display (HMD).

[0065] It is implemented with the user's field of view replaced with simulated visual components and headphones worn to provide the user with accompanying audio. Some form of user head and motion tracking in VR is typically implemented to allow the simulated visual and audio components to be updated in order to ensure that from the user's perspective, items and sound sources are aligned with the user's movements. Additional means of interacting with the virtual reality simulation may be provided, but are not strictly necessary.

[0066] Augmented Reality (AR) is when a user is provided with additional information or artificially generated objects or content superimposed on their current environment. This additional information or content will typically be visual and / or auditory, and their observation of their current environment may be direct, without intervening sensing, processing and rendering, or indirect, with their perception of their environment being relayed via sensors and may be augmented or processed.

[0067] Mixed reality (MR) is an advanced form of AR in which some virtual elements are inserted into the physical scene.

[0068] The purpose is to provide the illusion that these elements are part of the real scene.

[0069] Therefore, XR can be used to refer to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices. In addition, XR includes representative forms such as AR, MR and VR, as well as areas interpolated therein. The level of virtuality ranges from partial sensory input to fully immersive VR. Example aspects of XR are the extension of human experience, especially human experience related to presence (e.g., as represented by VR) and cognitive acquisition (e.g., as represented by AR).

[0070] Therefore, XR services, such as AR, VR, and cloud gaming services over 5G, are important vertical applications for wireless commercial deployment. Many end-user XR and cloud gaming devices are designed to be mobile and have a small size, and therefore have limited battery power resources. The current DRX mechanism is a power saving mechanism for achieving power saving gains for UEs in the RRC_CONNECTED state. However, some characteristics of XR services are not addressed by the current DRX mechanism and may result in limited UE power savings.

[0071] Implementations with multiple DRX configurations aligned with different XR streams have been proposed. For example, one motivation for doing this is that a single DRX configuration is not efficient from a power saving perspective because the traffic characteristics vary too much and cannot be addressed by a single DRX configuration.

[0072] For a single data stream of a UE, if the DRX periodicity matches the traffic arrival of that data stream, then dynamic grant can be used as the primary means to support XR traffic. However, XR use cases typically do not involve a single data stream: for example, for VR, the video data stream in the downlink (DL) and the gesture / control data stream in the UL have different periodicities. For AR, there may be two data streams in the DL (video, audio / data) and three data streams in the UL (video, gesture / control, audio / data) with different periodicities. Therefore, it is difficult to choose the periodicity and punctuality to handle the possible data streams. Furthermore, supporting non-integer periodicity for DRX may not provide benefits for UE power savings.

[0073] Furthermore, when there are multiple data flows, for example when there is not at least an integer relationship among their periodicities, matching the periodicity of DRX to the periodicity of another data flow may cause the data flow to arrive within the DRX off duration.

[0074] In the context of XR services, the support of video services is particularly important. For example, video services exhibit characteristics such as non-integer periodicity (e.g., 60, 90, and 120 frames / second video services) and time-varying packet sizes, e.g., due to different frame types, such as I-frames, P-frames, B-frames, etc.

[0075] Figure 2 An example of multiple data streams, for example, for carrying XR services, is illustrated at 200. For example, data stream 202 carries video services and exhibits periodic time intervals T 1 , and data stream 204 carries audio traffic and exhibits periodic time intervals T 2 As illustrated, data streams 202, 204 exhibit different periodicities.

[0076] Since video frames can be generated at regular times, DL semi-persistent scheduling (SPS) and UL configured grants can be considered as prime candidates for accommodating XR traffic in general and video traffic in particular. However, the Rel-16 NR design has some limitations. Note that the DL SPS periodicity and UL configured grant periodicity available in Rel-16 (e.g., illustrated at 200) are not relevant to various aspects of video traffic, including:

[0077] Supported periodicity of DL SPS in Rel-16 NR:

[0078] For NR systems with 15 kHz subcarrier spacing, {1,…,640} milliseconds,

[0079] · At 30KHz, it is {1 / 2, 1, 3 / 2, …, 640} milliseconds, etc.

[0080] Supported periodicity of UL configuration grant in Rel-16 NR:

[0081] For 15KHz, multiples of 1 ms, up to 640 ms, 2 symbols (1 / 7 ms), 7 symbols (0.5 ms)

[0082] For 30KHz in multiples of 1 / 2 ms, up to 640 ms, 2 symbols (1 / 14 ms), 7 symbols (0.25 ms)

[0083] Among the many periodicities currently supported in SPS and NR for cloud gaming, proper matching may not be achieved for video frames generated at 30, 60, 90, 120 Hz.

[0084] Figure 3 An example data stream 300 is illustrated, for example, for carrying XR traffic. For example, the data stream 300 includes packet arrival times of packets of a first data stream and packets of a second data stream, and jitter that may occur between arrival times, for example due to different packet periodicities.

[0085] When considering DRX in an XR scenario of some wireless communication systems, the DRX functionality can be configured for the MAC entity through RRC, and the DRX functionality controls the cell access of the UE to the MAC entity. PDCCH monitoring activities for Cell Identifier (CI)-RNTI, CS-RNTI, Interrupt (INT)-RNTI, Slot Format Indication (SFI)-RNTI, Semi-Persistent (SP)-Channel State Information (CSI)-RNTI, Transmit Power Control (TPC)-Physical Uplink Control Channel (PDCCH)-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and Air Interface (AI)-RNTI. When DRX operation is used, the MAC entity may also monitor the PDCCH according to the parameters found in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured for the activated serving cell, 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 Technical Specification (TS) 38.213 [6].

[0086] RRC can control DRX operation by configuring the following parameters:

[0087] -drx-onDurationTimer: Duration when the DRX cycle starts.

[0088] -drx-SlotOffset: Delay before starting drx-onDurationTimer.

[0089] -drx-InactivityTimer: Duration after the PDCCH opportunity when the PDCCH indicates a new UL or DL ​​transmission by the MAC entity.

[0090] -drx-RetransmissionTimerDL (per DL HARQ process except broadcast process): maximum duration before a DL retransmission is received.

[0091] -drx-RetransmissionTimerUL (per UL HARQ process): Maximum duration before receiving a grant for UL retransmission.

[0092] -drx-LongCycleStartOffset: Long DRX cycle and drx-StartOffset, which define the subframes where the long and short DRX cycles start.

[0093] -drx-ShortCycle (optional): short DRX cycle.

[0094] -drx-ShortCycleTimer (optional): Duration of the short DRX cycle that the UE should follow.

[0095] -drx-HARQ-RTT-TimerDL (per DL HARQ process except broadcast process): minimum duration before a DL assignment for which the MAC entity expects a HARQ retransmission.

[0096] -drx-HARQ-RTT-TimerUL (per UL HARQ process): Minimum duration before the MAC entity expects a UL HARQ retransmission grant.

[0097] -ps-Wakeup (optional): Initiates configuration of the associated drx-onDurationTimer if the Data Convergence Protocol (DCP) is monitored but not detected.

[0098] -ps-TransmitOtherPeriodicCSI (optional): Configuration to report periodic CSI other than L1 reference signal received power (RSRP) on PUCCH for the duration indicated by drx-onDurationTimer, if DCP is configured but the associated drx-onDurationTimer is not started.

[0099] -ps-TransmitPeriodicL1-RSRP (optional): If DCP is configured but the associated drx-onDurationTimer is not started, configuration to transmit periodic CSI as L1-RSRP on PUCCH for the duration indicated by drx-onDurationTimer.

[0100] In addition, the serving cells of the MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there may be one DRX group and all serving cells belong to that one DRX group. When two DRX groups are configured, each serving cell can be uniquely assigned to either of the two groups. The DRX parameters configured separately for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters common to the DRX group are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL. When DRX is configured, the active time of the serving cells in the DRX group includes the following times:

[0101] -When the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running;

[0102] or

[0103] - when drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell in the DRX group; or

[0104] - when ra-ContentionResolutionTimer (as described in clause 5.1.5) or msgB-ResponseWindow (as described in clause 5.1.4a) is running; or - when a scheduling request is being sent on PUCCH and is pending; or

[0105] - When a newly transmitted PDCCH indicating a C-RNTI addressed to the MAC entity is not received after successfully receiving a random access response to a random access preamble that was not selected by the MAC entity among contention-based random access preambles.

[0106] According to some scenarios, when DRX is configured, the MAC entity will:

[0107] 1> If a MAC PDU is received in a configured downlink assignment:

[0108] 2> then start drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying DL HARQ feedback;

[0109] 2> Stop drx-RetransmissionTimerDL for the corresponding HARQ process.

[0110] 1> If a MAC PDU is transmitted in a configured uplink grant and no Listen Before Talk (LBT) failure indication is received from lower layers:

[0111] 2> then start drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the first transmission (within the bundle) of the corresponding PUSCH transmission;

[0112] 2> Stop drx-RetransmissionTimerUL for the corresponding HARQ process at the first transmission (within the bundle) of the corresponding PUSCH transmission;

[0113] 1> If drx-HARQ-RTT-TimerDL expires:

[0114] 2> If the data corresponding to the HARQ process is not successfully decoded:

[0115] 3> Then drx-RetransmissionTimerDL is started for the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerDL.

[0116] 1> If drx-HARQ-RTT-TimerUL expires:

[0117] 2> Then drx-RetransmissionTimerUL is started for the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerUL.

[0118] 1> If a DRX command medium access control (MAC) control element (CE) or a long DRX command MAC CE is received:

[0119] 2>Then stop drx-onDurationTimer for each DRX group;

[0120] 2> Stop drx-InactivityTimer for each DRX group.

[0121] 1> If the drx-InactivityTimer for the DRX group expires:

[0122] 2> If short DRX cycle is configured:

[0123] 3> Then start or restart drx-ShortCycleTimer for this DRX group in the first symbol after the expiration of drx-InactivityTimer;

[0124] 3> Use short DRX cycle for this DRX group.

[0125] 2> Or:

[0126] 3> Use long DRX cycle for this DRX group.

[0127] 1> If DRX command MAC CE is received:

[0128] 2> If short DRX cycle is configured:

[0129] 3> Then start or restart drx-ShortCycleTimer for each DRX group in the first symbol after the DRX command MAC CE reception ends;

[0130] 3> Use short DRX cycle for each DRX group.

[0131] 2> Or:

[0132] 3> Use a long DRX cycle for each DRX group.

[0133] 1> If the drx-ShortCycleTimer for the DRX group expires:

[0134] 2> Then a long DRX cycle is used for this DRX group.

[0135] 1> If a long DRX command MAC CE is received:

[0136] 2>Then stop drx-ShortCycleTimer for each DRX group;

[0137] 2> Use a long DRX cycle for each DRX group.

[0138] 1> If the short DRX cycle is used for the DRX group, and [(system frame number (SFN) × 10) + subframe number]

[0139] modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle):

[0140] 2> Then after drx-SlotOffset from the start of the subframe, start drx-onDurationTimer for this DRX group.

[0141] 1> If the long DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo

[0142] (drx-LongCycle)=drx-StartOffset:

[0143] 2> If DCP monitoring is configured for the active DL bandwidth part (BWP) as specified in TS 38.213 [6] clause 10.3:

[0144] 3> if the DCP indication received from lower layers associated with the current DRX cycle indicates the start of the drx-onDurationTimer as specified in TS 38.213 [6]; or

[0145] 3> If it is taken into account that 4 ms before the start of the last DCP opportunity or during the measurement gap, or when the MAC entity monitors PDCCH transmissions on the search space indicated by the recoverySearchSpaceId of the SpCell identified by the C-RNTI while the ra-ResponseWindow is running (as specified in clause 5.1.4), the received grant / assignment / DRX command MAC CE / long DRX command MAC CE and the sent scheduling request are in accordance with the current DRX as specified in TS 38.213 [6]

[0146] All DCP opportunities in the loop-related time domain occur within the active time; or

[0147] 3> If ps-Wakeup is configured with a value of true and a DCP indication associated with the current DRX cycle has not been received from lower layers:

[0148] 4> Then start drx-onDurationTimer after drx-SlotOffset from the start of the subframe.

[0149] 2> Or:

[0150] 3> Start drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

[0151] 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.

[0152] 1> If the DRX group is in active time:

[0153] 2> then monitor PDCCH on the serving cell in this DRX group as specified in TS 38.213[6];

[0154] 2> If PDCCH indicates DL transmission:

[0155] 3> then start drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying DL HARQ feedback;

[0156] NOTE 3: When HARQ feedback is deferred by a physical downlink shared channel (PDSCH)-to-HARQ_feedback timing indicating a non-numeric k1 value, the corresponding transmit opportunity for sending DL HARQ feedback is indicated in a later PDCCH requesting HARQ-ACK feedback as specified in TS 38.213 [6].

[0157] 3> Stop drx-RetransmissionTimerDL for the corresponding HARQ process.

[0158] 3> If the PDSCH-to-HARQ_feedback timing indicates a non-numeric k1 value as specified in TS 38.213 [6]:

[0159] 4> Then start drx-RetransmissionTimerDL in the first symbol after the (last) PDSCH transmission (within the bundle) of the corresponding HARQ process (end).

[0160] 2> If PDCCH indicates UL transmission:

[0161] 3> then start drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the first transmission (in the bundle) of the corresponding PUSCH transmission;

[0162] 3> Stop drx-RetransmissionTimerUL for the corresponding HARQ process.

[0163] 2> If PDCCH indicates a new transmission (DL or UL) on a serving cell in this DRX group:

[0164] 3> Then start or restart the drx-InactivityTimer for this DRX group in the first symbol after the end of PDCCH reception.

[0165] Note 3a: A PDCCH indicating activation of SPS or configured grant type 2 is considered to indicate a new transmission.

[0166] 2> If the HARQ process receives downlink feedback information and confirmation is indicated:

[0167] 3> Then stop drx-RetransmissionTimerUL for the corresponding HARQ process.

[0168] 1> if DCP monitoring is configured for the active DL BWP as specified in clause 10.3 of TS 38.213 [6]; and 1> if the current symbol n occurs within the drx-onDurationTimer duration; and 1> if the drx-onDurationTimer associated with the current DRX cycle is not started as specified in this clause:

[0169] 2> If taken into account when evaluating all DRX active time conditions specified in this clause 4 before symbol n

[0170] The MAC entity will not be in the active time when the ms receives the authorization / assignment / DRX command MAC CE / long DRX command MAC CE and sends the scheduling request:

[0171] 3> Then the periodic sounding reference signal (SRS) and semi-persistent SRS defined in TS 38.214 [7] are not transmitted;

[0172] 3> Do not report semi-persistent CSI configured on PUSCH;

[0173] 3> If ps-TransmitPeriodicL1-RSRP is not configured and has a value of true:

[0174] 4> Then periodic CSI as L1-RSRP on PUCCH is not reported.

[0175] 3> If ps-TransmitOtherPeriodicCSI is not configured and has a value of true:

[0176] 4> Then do not report periodic CSI that is not L1-RSRP on PUCCH.

[0177] 1> Or:

[0178] 2> In the current symbol n, the DRX group shall not be in active time if, taking into account the grant / assignment scheduled on the serving cell in this DRX group 4 ms before symbol n and the received DRX Command MAC CE / Long DRX Command MAC CE and the sent Scheduling Request, when evaluating all DRX Active Time conditions specified in this clause:

[0179] 3> Then the periodic SRS and semi-persistent SRS defined in TS 38.214 [7] are not transmitted in this DRX group;

[0180] 3> CSI on PUCCH and semi-persistent CSI configured on PUSCH are not reported in this DRX group.

[0181] 2> If CSI masking (csi-mask) is set by the upper layer:

[0182] 3> then in the current symbol n, if the grant / assignment scheduled on the serving cell in this DRX group 4 ms before symbol n and the received DRX Command MAC CE / Long DRX Command MAC CE are taken into account when evaluating all DRX Active Time conditions specified in this clause,

[0183] The drx-onDurationTimer of the DRX group will not be running; and

[0184] 4> CSI on PUCCH is not reported in this DRX group.

[0185] NOTE 4: If the UE multiplexes CSI configured on PUCCH with other overlapping uplink control information (UCI) according to the procedure specified in clause 9.2.5 of TS 38.213 [6], and this CSI multiplexed with other UCI is to be reported on PUCCH resources outside the DRX Active Time of the DRX group configured with this PUCCH, or outside the OnDuration period of the DRX group configured with this PUCCH if CSI masking is set by upper layers, it is up to the UE implementation to decide whether to report this CSI multiplexed with other UCI.

[0186] In some current scenarios, regardless of whether the MAC entity is monitoring PDCCH on a serving cell in a DRX group, the MAC entity transmits HARQ feedback, aperiodic CSI on PUSCH, and aperiodic SRS as defined in TS 38.214 [7] on a serving cell in a DRX group when expected. In addition, if the PDCCH is not a full PDCCH opportunity, such as when the active time starts or ends in the middle of a PDCCH opportunity, then the MAC entity may not need to monitor the PDCCH.

[0187] Many XR and cloud gaming use cases are characterized by quasi-periodic traffic (possibly with jitter) with high data rates in the DL (e.g., video streaming) combined with frequent UL (e.g., gesture / control updates) and / or UL video streaming. Both DL and UL traffic are also characterized by relatively tight PDBs.

[0188] For example, the expected set of XR and cloud gaming services may have data streams (e.g., video) of specific kinds and characteristics that may change "in real time" when the services run wireless connectivity. Therefore, additional information from higher layers about the running services, such as QoS flow association, frame-level QoS, ADU-based QoS, XR-specific QoS, etc., may be helpful in facilitating the intelligent selection of radio parameters. In addition, XR application awareness of UE and network entities can improve the user experience, increase the wireless system capacity to support XR services, and reduce UE power consumption. As discussed in this article, ADU may refer to the smallest data unit that an application can process independently, such as processing for handling out-of-order business data.

[0189] The latency requirement of XR services on the RAN side (e.g., air interface) can be modeled as a PDB. The PDB is a limited time budget for transmitting packets from a network entity to a UE via over-the-air download. For a given packet, the packet delay induced in the air interface can be measured from the time the packet arrives at the network entity to the time the packet is successfully delivered to the UE. If the delay is greater than a given PDB for the packet, the packet is considered to violate the PDB, otherwise the packet is considered to be successfully delivered.

[0190] The value of PDB may vary for different applications and traffic types, and may be 10 to 20 ms depending on the application (see Technical Report (TR) 26.926).

[0191] According to R1-2112245: The 5G arrival time of data bursts on the downlink can be quasi-periodic, for example with jittery periodicity. Some factors that cause jitter in burst arrival include different server rendering times, encoder times, real-time transport protocol (RTP) packet times, links between servers and 5G gateways, etc. 3GPP agrees to use a truncated Gaussian distribution with mean: 0ms, standard deviation: 2ms, range: [-4ms, 4ms] (baseline), [-5ms, 5ms] (optional) to simulate the XR evaluation model DL service arrival jitter.

[0192] In addition, applications may have specific latency requirements for the ADU that may not translate adequately into packet delay budget requirements. For example, if the ADU delay budget (ADB) is 10ms, then the PDB can be set to 10ms only if all packets of the ADU arrive at the 5G system at the same time. If the packets are spread out, then the ADU delay budget is measured based on the arrival of the first packet of the ADU or the last packet of the ADU. In either case, a given ADB will result in different PDB requirements for different packets of the ADU.

[0193] Therefore, a solution is provided in the present disclosure that allows enhanced scheduling in network entities, for example for XR traffic, in order to improve resource efficiency and capacity. Furthermore, enhancements to UL transmission of XR traffic in UE are provided.

[0194] In some scenarios, the DRX ActiveTimes of different DRX configurations may overlap and the DRX timer values ​​of different DRX configurations may be different. Therefore, when a PDCCH is received within a certain "overlapping" ActiveTime, it will be helpful for the UE to know which DRX timer to update in response to the reception of the timer.

[0195] Therefore, in an implementation scheme, the DCI that allocates downlink and / or uplink resources includes a field that identifies the DRX configuration. For scenarios where the UE is configured with multiple DRX configurations and more than one DRX configuration is active (e.g., currently applied by the UE and the MAC entity in the UE, respectively), the DCI can be identified by an indication of which DRX configuration the resource allocation applies to. This may be important for situations where the ActiveTimes of different DRX configurations overlap in time. For example, when the UE starts a DRX-related timer in response to receiving a PDCCH and / or PDSCH / PUSCH, it will be helpful for the UE to know which of the multiple DRX configurations to (re)start, stop, or update the corresponding timer.

[0196] In some scenarios, the timer value may be different for different DRX configurations. Therefore, in at least one embodiment, the DCI includes a field that conveys an identifier that identifies the DRX configuration associated with the PDCCH and / or PDSCH / PUSCH transmission. For example, this signaling ensures that the UE and network entities are synchronized and aligned in terms of DRX behavior and / or DRXstate.

[0197] According to at least one embodiment, a different radio network temporary identifier (RNTI) is configured and / or assigned to a UE for each of a plurality of DRX configurations. For example, when scheduling DL / UL resources, a network entity uses the corresponding RNTI of a PDCCH in order to indicate to the UE the DRX configuration associated with this resource allocation. Based on the received RNTI, the UE and / or MAC knows for which of the plurality of DRX configurations it will (re)start and / or stop the corresponding DRX-related timer.

[0198] In at least some embodiments, the UE starts / updates a corresponding DRX-related timer for each of the DRX configurations in which the ActiveTime overlaps in response to receiving a resource allocation (e.g., PDCCH). For example, the UE may start DRX timers for multiple DRX configurations, which may cause the ActiveTime to be extended according to the timer with the largest value. A benefit of this embodiment may be that no additional signaling is required to identify the DRX configuration.

[0199] In at least some embodiments, the network entity configures a separate search space and / or CORESET for each of the multiple DRX configurations. For example, based on the search space and / or CORESET on which the PDCCH is received, the UE can identify and determine for which of the multiple DRX configurations to perform a corresponding DRX-related timer update.

[0200] In at least some embodiments, the UE determines for which of the multiple DRX configurations to update the corresponding DRX-related timer based on a predefined rule. For example, the rule specifies that the UE updates the DRX-related timer of the DRX configuration with a minimum timer value or a maximum timer value. For example, after receiving a PDCCH that allocates DL / UL resources for an initial transmission, the UE starts a drx-inactivitytimer with a minimum timer value or a maximum timer value among the multiple overlapping DRX configurations, depending on the implementation of the rule.

[0201] Thus, the implementation discussed above includes aspects related to scenarios where the DRX ActiveTimes of different DRX configurations may overlap and where the DRX timer values ​​of the different DRX configurations are different. For example, when a PDCCH is received within overlapping ActiveTimes, the UE needs to know which DRX timer to start in response to the reception of the timer. Aspects of the implementation discussed include:

[0202] • The PDCCH indicates the DRX configuration identifier (ID).

[0203] Different PDCCH search spaces for different DRX configurations.

[0204] Different RNTIs.

[0205] For scenarios where DRX configurations overlap, s rules are provided which specify which DRX timer to use,

[0206] For example a timer with a minimum length or a maximum length.

[0207] • In the scenario where LCH is mapped to a DRX configuration: the UE may (eg, in post-processing) start a corresponding timer after decoding the packet.

[0208] • Starting and / or restarting a timer, for example starting a corresponding timer for each DRX configuration.

[0209] According to a further embodiment, UE power consumption can be optimized by controlling the transmission of SR, for example, for DL / UL alignment. For example, a configuration is provided to enable the UE to delay the transmission of SR in order to avoid extending the ActiveTime. For example, the network entity configures the maximum time to wait until the SR is sent (e.g., network response time) for the logical channel (LCH), and the UE can optimize the transmission of SR based on this information, for example, to delay the SR transmission.

[0210] In one or more implementations, the LCH is configured with a parameter indicating whether the UE and / or MAC is to delay the transmission of the SR. For example, a parameter is defined as a Boolean value indicating whether the UE is to additionally delay the transmission of the SR (e.g., on the PUCCH) when triggered, or whether the UE is to perform the SR procedure specified in the current specification, such as the legacy behavior.

[0211] In addition to one or more implementations, the UE and / or MAC is also configured with a time value used in the MAC to determine when to send a delayed SR transmission. For example, the configured time value indicates a network response time, such as the time from sending and / or receiving the SR to the transmission of the corresponding UL transmission.

[0212] According to one or more implementations, after the SR has been triggered in the UE and / or the MAC, the UE starts a timer in at least one instance for a scenario when the UE is configured to delay SR transmission. For example, the UE is to send the SR as long as the timer is running, such as before the timer expires. For example, the timer represents a time window for the UE to send the SR. The time window (e.g., timer value) is determined based on a packet delay budget for a transport block (TB) and a configured time value (e.g., network response).

[0213] In at least one instance, the timer value is set to "PDB of TB - configured network response time". To optimize UE power consumption, the UE may be instructed to send an SR when the timer is running and the UE is in DRX ActiveTime. In addition, to minimize UE power consumption, the UE may send an SR when it is in DRX ActiveTime and monitoring PDCCH.

[0214] In some systems, for example for UL grants, after the UE sends an SR on the PUCCH, it goes to the ActiveTime and monitors the PDCCH. Therefore, when the SR transmission falls within the ActiveTime of the UE, no additional power consumption caused by PDCCH monitoring may be introduced. In addition, the timer started when the SR is triggered ensures that the UE does not send the SR too late to transmit a TB within the configured PDB. In addition, when the UE determines when to send the SR, the UE may take into account the SR configuration, such as the PUCCH resources allocated for the transmission of the SR.

[0215] According to an alternative or additional implementation, the LCH is configured with a time value used in the MAC in order to determine when to send a delayed SR transmission, such as a time value indicative of a network response time.

[0216] Thus, the implementation discussed above includes aspects related to whether the UE waits before sending an SR, e.g., to avoid further extending the ActiveTime. For example, the network entity configures a maximum time (e.g., network response time) for waiting until sending an SR for an LCH, and the UE may optimize sending an SR based thereon, e.g., delaying SR transmission. Aspects of the implementation discussed include:

[0217] • The network entity configures the network response time to the SR, and the UE sends the SR before the RDB within the signaled network reaction time, e.g. different from the SRdelayTimer.

[0218] UE behavior: When the UE is in ActiveTime and the timer is still running, a triggered SR is sent; when the timer expires, the UE will send a SR regardless of the DRX state.

[0219] • The UE shall take the SR resources (eg, timing) into account when calculating the latest time the UE shall send a SR.

[0220] According to further embodiments, an adaptive configuration for the DRX timer is provided, such as dynamically controlling whether to update the DRX timer. For example, in at least some embodiments, the DCI indicates whether the UE is to start the drx-InactivityTimer in response to the reception of the PDCCH carrying the DCI. For example, the DCI allocates DL or UL resources for the initial transmission. In at least one instance, information about whether to start the drx-InactivityTimer is signaled in a 1-bit field in the DCI. For example, in the case of transmitting the last DL packet of a PDU set, for a scenario where the network entity does not have more DL data to transmit, starting the drx-InactivityTimer and extending the ActiveTime may not be beneficial. Therefore, allowing the network entity to dynamically control whether to start the drx-InactivityTimer in the UE in response to the reception of the DCI through the DCI can improve (e.g., reduce) the power consumption of the UE.

[0221] In at least some embodiments, the DCI indicates whether the UE triggers (re)starting DRX-related timers in response to the reception of the PDCCH and the corresponding reception and / or transmission of the PDSCH and / or PUSCH. For example, the DCI allocates DL and / or UL resources for the transmission. In at least one instance, the DRX-related timers include drx-InactivityTimer, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, drx-HARQ-RTT-TimerDL and / or drx-RetransmissionTimerUL. According to at least one embodiment, information about whether to start DRX-related timers in response to the reception of the DCI and / or the corresponding PDSCH or PUSCH is signaled in a 1-bit field in the DCI. For example, the UE does not start the drx-InactivityTimer in response to the reception of the DCI indicating that no DRX-related timer is started. In addition, the UE does not start the drx-HARQ-RTT-TimerDL and drx-RetransmissionTimerDL in response to the reception of the corresponding PDSCH. In the scenario where the UE does not correctly decode the PDSCH, according to one or more implementations, the UE does not start drx-RetransmissionTimerDL and monitors the retransmission of the PDCCH. In addition, after transmitting the PUSCH scheduled by the DCI, the UE does not start drx-HARQ-RTT-TimerUL and subsequently does not start drx-RetransmissionTimerUL.

[0222] According to one or more implementations, the DCI that schedules the initial transmission indicates whether the UE is to start drx-HARQ-RTT-TimerDL in response to the reception of PDCCH and / or PDSCH. In at least one instance, the DCI further indicates whether the UE is to transmit HARQ feedback (e.g., acknowledgement (ACK) or negative ACK (NACK)) in response to the reception of PDSCH, and to start drx-RetransmissionTimerDL in response to the transmission of NACK. For scenarios where the DL transmission has a tight latency budget that does not allow HARQ retransmissions, the UE does not need to monitor the potential retransmissions of the PDCCH, such as starting the drx-RetransmissionTimerDL timer and skipping the transmission of ACK / NACK. In at least one instance, information indicating that the UE does not start drx-HARQ-RTT-TimerDL and / or does not transmit HARQ feedback (e.g., ACK and / or NACK) in response to the reception of PDSCH and does not start drx-RetransmissionTimerDL is signaled in a field in the DCI. In an alternative or additional implementation, this information is signaled by reusing an existing field in the DCI. In at least one example, a specific K1 value "PDSCH-to-HARQ-timing-indicator" indicating the transmission timing of the HARQ feedback indicates that the UE does not start the HARQ-RTT-TimerDL, drx-RetransmissionTimerDL timers and / or the UE does not transmit a HARQ ACK / NACK.

[0223] According to one or more embodiments, the DCI indicates to the UE that the drx-HARQ-RTT-TimerDL timer is not started in response to the reception of the PDCCH and / or PDSCH. In at least one instance, the indication is signaled by a "PDSCH-to-HARQ-timing-indicator" field (e.g., a K1 value). In at least one instance, for a scenario in which the signaled K1 value is greater than a predefined threshold and / or if the signaled K1 value is greater than the remaining delay budget for the data (e.g., as indicated in the DCI), the UE does not start the drx-HARQ-RTT-TimerDL timer and does not start the drx-RetransmissionTimerDL timer. For example, the UE does not extend the ActiveTime and monitor the retransmission of the PDCCH.

[0224] According to one or more embodiments, a downlink HARQ process is configured with a configuration indicating whether the UE starts a drx-HARQ-RTT-TimerDL timer in response to a PDCCH and / or PDSCH received on the HARQ process. In at least one instance, the configuration defines whether the UE is to send HARQ feedback for a corresponding PDSCH transmission. For example, two different configurations of a DL HARQ process are defined. In addition, a HARQ process according to a first configuration may behave as in a previous embodiment with respect to DRX timer handling and / or HARQ feedback transmission. A DL HARQ process configured according to a second configuration may provide different DRX timer handling for DL ​​transmissions occurring on the HARQ process compared to previous embodiments of DRX behavior.

[0225] In at least one instance, the DL HARQ process configured according to the second configuration is used for low-latency transmissions that may not tolerate HARQ retransmissions. For example, PDCCH and / or PDSCH transmissions occurring on the HARQ process configured according to the second configuration may not trigger the start of the drx-HARQ-RTT-TimerDL timer and the drx-RetransmissionTimerDL timer. In at least one instance, the UE may also not send HARQ feedback in response to reception of a PDSCH transmission on the HARQ process configured according to the second configuration.

[0226] In one or more implementations, the UE ignores the "PDSCH-to-HARQ-timing-indicator" field (e.g., K1 timing) in the DCI for the HARQ process indicated by the HARQ process ID field that does not support HARQ retransmission and HARQ feedback signaling (e.g., the HARQ process configured according to the second configuration). For example, the "PDSCH-to-HARQ-timing-indicator" field for the K1 value may be reused for scenarios in which the HARQ process ID indicates a HARQ process that does not support HARQ retransmission and / or HARQ feedback transmission.

[0227] In one or more implementations, the UL HARQ process is configured with a configuration that indicates whether the UE is to start a drx-HARQ-RTT-TimerUL timer in response to a PUSCH transmitted on the HARQ process.

[0228] In at least one instance, the HARQ process configuration defines whether the UE monitors the PDCCH for retransmission grants and / or whether the UE is to perform HARQ retransmissions on the PUSCH. In at least one instance, two different configurations of the UL HARQ process are specified. For example, the HARQ process according to the first configuration behaves as in the previous implementation with respect to DRX timer handling and / or HARQ retransmissions. The UL HARQ process configured according to the second configuration provides different DRX behavior for UL transmissions occurring on the HARQ process compared to the previous implementation of DRX behavior.

[0229] In at least one instance, the UL HARQ process configured according to the second configuration is used for low-latency transmissions that may not tolerate HARQ retransmissions. For example, a PUSCH transmission occurring on the HARQ process configured according to the second configuration may not trigger the start of the drx-HARQ-RTT-TimerUL timer and the drx-RetransmissionTimerUL timer. In at least one instance, the UE does not perform HARQ retransmissions on the PUSCH in response to receiving a PDCCH scheduling HARQ retransmissions on the HARQ process configured according to the second configuration, for example, the UE ignores the DCI scheduling the retransmissions.

[0230] According to one or more embodiments, the uplink CG configuration includes an IE indicating whether a UL transmission on the CG resource triggers the start of the drx-HARQ-RTT-TimerUL timer and the drx-RetransmissionTimerUL timer. For example, for a CG configuration for XR services with strict latency requirements (e.g., for a CG configuration that may not tolerate HARQ retransmissions), the UE will not monitor the PDCCH for retransmission authorizations, such as DCI with CS-RNTI. Therefore, the UE according to this embodiment does not extend the ActiveTime by starting the drx-HARQ-RTT-TimerUL timer and therefore the drx-RetransmissionTimerUL timer. In at least one instance, the UE ignores the PDCCH scheduling HARQ retransmissions of a previous PUSCH transmission performed on a CG PUSCH resource configured with an IE, for example, where the IE indicates that retransmissions are not supported.

[0231] According to one or more embodiments, the UL CG configuration includes an IE that configures a drx-HARQ-RTT-TimerUL timer value and / or a drx-RetransmissionTimerUL timer value to be applied to UL transmissions performed on corresponding uplink CG resources. For example, when the UE performs a PUSCH transmission on a CG PUSCH resource configured with a CG, the UE starts a drx-HARQ-RTT-TimerUL timer set to the value configured in the UL CG configuration IE. In addition, the UE starts a drx-RetransmissionTimerUL timer set to the configured value. In at least one instance, a drx-HARQ-RTT-TimerUL timer value configured as zero indicates that the UE does not start a drx-HARQ-RTT-TimerUL timer and a drx-RetransmissionTimerUL timer in response to performing a UL transmission on a CG PUSCH resource configured with a UL CG.

[0232] According to one or more embodiments, the CG configuration for UL transmission is specifically configured for XR data / service. For example, an IE (e.g., ConfiguredGrantConfig-XR as described below) is provided, which configures semi-persistent UL resources (e.g., CG-PUSCH resources) for XR services. In at least some embodiments, some IE parameters of this CG configuration are similar to the previous CG configuration. In at least one instance, new parameters and / or IEs are included in the XR-specific CG configuration, and these new parameters and / or IEs are XR-specific, such as discussed above, such as drx-HARQ-RTT-TimerUL timer value, drx-RetransmissionTimerUL timer value, indication of whether HARQ retransmission is supported, etc.

[0233] Figure 4 and 5 Different corresponding portions of an IE 400 supporting timing control in wireless communications according to aspects of the present disclosure are illustrated. For example, the IE 400 (e.g., "ConfiguredGrantConfig-XR") supports CG configuration of XR. The IE 400 includes parameters 402 and 404 that specify configurations (e.g., values) of different timers. For example, the parameter 402 specifies the configuration (e.g., value) of a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerUL), and the parameter 404 specifies the configuration (e.g., value) of a UL retransmission timer (e.g., drx-RetransmissionTimerUL). Figure 5 Describe other features and parameters of IE 400. In at least some embodiments, Figure 4 and 5 The portions of IE 400 in the IE400 may be combined into a single IE. Alternatively or additionally, the portions of IE 400 may be communicated via different IEs and / or notifications.

[0234] According to one or more embodiments, for a scenario in which the configured delay bound (e.g., delay budget) of a TB is less than a configured threshold, the UE does not start the drx-HARQ-RTT-TimerUL timer and the drx-RetransmissionTimerUL timer. In at least one instance, the UE determines the delay budget and / or packet delay budget of the TB as the minimum or maximum delay budget associated with the LCH among the LCHs multiplexed in the TB. For example, the network entity configures a threshold value that is used to determine whether the UE extends the ActiveTime by starting the drx-HARQ-RTT-TimerUL timer and / or the drx-RetransmissionTimerUL timer. In at least some embodiments, for data with strict delay requirements (e.g., HARQ retransmissions are not allowed), the UE does not extend the ActiveTime and monitors the PDCCH for, for example, potential retransmission grants. For example, the network entity knows the delay budget of the PUSCH transmission and / or the TB. This behavior can be ensured by controlling which LCHs are allowed to be mapped to the scheduled UL resources, for example, by LCH restrictions. For example, for a CG, the network entity may control which LCHs are allowed to be mapped to CG resources and therefore the network entity is aware of the PDB.

[0235] According to one or more embodiments, the LCH is configured with an LCH parameter (e.g., an LCH field), the LCH parameter indicating whether a PUSCH transmission including data of the LCH supports HARQ retransmission. In at least one instance, the LCH parameter is signaled within the logicalchannelconfig IE. For example, for a scenario in which a TB includes data of an LCH configured to not support HARQ retransmission, the UE does not start a drx-HARQ-RTT-TimerUL timer and / or a drx-RetransmissionTimerUL timer in response to having performed a PUSCH transmission. For example, the UE does not extend the ActiveTime and monitor the retransmission grant of the PDCCH. In a scenario in which the logicalchannelconfig IE does not contain the LCH parameter (e.g., the LCH parameter is not present in the logicalchannelconfig IE) and / or the LCH parameter indicates that the data transmission of the LCH supports HARQ retransmission (e.g., the LCH parameter is a Boolean value), the UE may apply a previous DRX behavior to the PUSCH transmission.

[0236] According to one or more embodiments, a HARQ process is configured with a configuration indicating that the UE does not start the drx-HARQ-RTT-TimerUL timer in response to a PUSCH transmitted on the HARQ process. In such embodiments, for the case where a PUSCH transmission (initial transmission) is scheduled on such a HARQ process, the UE may consider only LCHs that do not support HARQ retransmission during a logical channel prioritization (LCP) process. In at least one instance, the LCH is configured with a HARQ retransmission mode configuration through a field in the logicalchannelconfig IE as discussed above. According to at least one embodiment, the UE multiplexes data of only LCHs in a TB that are configured with the same HARQ retransmission mode, such as a mode that supports HARQ retransmission or a mode that does not support HARQ retransmission. According to one or more embodiments, LCH mapping criteria (e.g., LCH to HARQ process mapping configuration) are provided. In at least one example, the LCH mapping criteria specifies that, for a scenario in which a PUSCH transmission is scheduled on a HARQ process configured with a DRX / HARQ mode that supports retransmission, the UE considers only logical channels configured to support HARQ retransmission during the LCP process. For example, the UE starts a drx-HARQ-RTT-TimerUL timer in response to a PUSCH transmitted on such a HARQ process.

[0237] Therefore, the implementation discussed above includes aspects related to PDCCH retransmission timing. Aspects of the implementation discussed include:

[0238] • Indicate in the initially transmitted PDCCH whether a NACK is to trigger a PDCCH retransmission timer, and / or whether a NACK is to be transmitted and / or an ACK is also transmitted. For example, an implementation indicates in the DCI whether HARQ feedback is enabled or disabled.

[0239] o The last packet or delay bound does not allow HARQ retransmission.

[0240] • For UL, CG configuration may be configured for HARQ disable / enable operation.

[0241] o The UE does not need to monitor retransmissions (e.g., CS-RNTI).

[0242] • LCH configuration (eg, HARQ deactivation).

[0243] · LCP rules for multiplexing HARQ disabled and HARQ enabled LCHs.

[0244] The HARQ process is configured regardless of whether drxretransmissionTimer is used, and the CG is mapped to a specific HARQ process.

[0245] • The LCH is configured to the HARQ process to which it can be mapped.

[0246] ·HARQ RTT timer per process (e.g., different values): HARQ_RTT timer value or DRX retransmission timer configured per CG, e.g., setting it to zero means no retransmission timer.

[0247] Example rule: If the PDB is below the threshold, the UE does not start the HARQ RTT timer and the Drx-Retx timer.

[0248] • PUCCH format (eg, ACK / NACK bundling).

[0249] In addition, the implementations discussed above include aspects related to whether to start a DRX inactivity timer and / or a timer value (e.g., a list of configured values) for the last packet of a packet set (e.g., a packet burst), such as when there is no time to start a DRX retransmission timer or a DRX inactivity timer. Aspects of the implementations discussed include:

[0250] PDCCH indicates "no DRX timer start" (e.g., neither drx-inactivity nor drx-Restart)

[0251] PDCCH indicates the end of a data burst

[0252] • The PDCCH indicates that after the scheduled transmission, the UE will transition to sleep mode, without starting timers etc.

[0253] Figure 6 An example of a block diagram 600 illustrating an apparatus 602 (e.g., device) that supports timing control in wireless communications according to aspects of the present disclosure. The apparatus 602 may be an example of a UE 104 as described herein. The apparatus 602 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The apparatus 602 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 604, a memory 606, a transceiver 608, and an I / O controller 610. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0254] The processor 604, 606, 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. For example, the processor 604, 606, transceiver 608, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0255] In some implementations, the processor 604, 606, transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some implementations, the processor 604 and 606 coupled to the processor 604 may be configured to perform one or more of the functions described herein (e.g., the processor 604 executes instructions stored in 606). For example, in the context of the UE 104, the transceiver 608 and the processor 604 coupled to the transceiver 608 are configured to cause the UE 104 to perform various described operations and / or combinations thereof.

[0256] For example, the processor 604 and / or the transceiver 608 may support wireless communication at the device 602 according to examples as disclosed herein. For example, the processor 604 and / or the transceiver 608 may be configured to or otherwise support means for: receiving a DCI that allocates a resource set for a HARQ process at a first time instance, wherein the DCI includes a field indicating whether to start a timer; and starting the timer at a second time instance, at least in part based on the field indicating to start the timer.

[0257] In addition, in some embodiments, the DCI allocates a downlink resource set for the HARQ process; the second time instance is the first symbol after the end of the transmission of the HARQ feedback carrying the downlink transmission allocated by the DCI; the timer is drx-HARQ-RTT-TimerDL; the timer is drx-HARQ-RTT-TimerUL; the timer is drx-inactivityTimer; the second time instance is the first symbol after the end of the reception of the DCI; the DCI further includes an indication whether to enable or disable the HARQ feedback; the DCI further includes an indication not to start the timer if the PDB is below a threshold; the DCI further includes an indication that the device will transition to a sleep mode after the transmission associated with the downlink resources; the DCI further includes an indication of the end of a data burst after which the timer is not started.

[0258] In another example, the processor 604 and / or the transceiver 608 can support wireless communication at the device 602 according to examples as disclosed herein. For example, the processor 604 and / or the transceiver 608 can be configured to or otherwise support means for: receiving a notification identifying a wireless resource and a DRX configuration; selecting a DRX timer from a plurality of different DRX timers based on the DRX configuration; and configuring the DRX timer.

[0259] In addition, in some embodiments, the notification includes a DRX configuration identifier; the notification is received as part of the DCI; the notification includes multiple DRX configurations, and the processor and transceiver are configured to cause the device to initiate two or more of multiple DRX timers corresponding to the multiple DRX configurations; the notification includes multiple DRX configurations and indicates one or more of the search spaces or CORESETs for each of the DRX configurations; the notification includes multiple DRX configurations, and the processor and transceiver are configured to cause the device to apply predefined rules based on the multiple DRX configurations to determine which of the multiple DRX timers to start.

[0260] In another example, the processor 604 and / or the transceiver 608 can support wireless communication at the device 602 according to examples as disclosed herein. For example, the processor 604 and / or the transceiver 608 can be configured to or otherwise support means for: receiving a notification identifying a maximum delay time for sending a scheduling request; and transmitting a scheduling request at a time instance determined at least in part based on the maximum delay time.

[0261] In addition, in some embodiments, the processor and transceiver are configured to cause the device to apply a maximum delay time to delay a scheduling request until a time instance; the maximum delay time is based at least in part on a remaining PDB; the processor and transceiver are configured to: when the device is in an active DRX state, transmit a scheduling request before a scheduling request timer configured at least in part based on the maximum delay time expires; and when the device is in an inactive DRX state, transmit a scheduling request after the scheduling request timer expires.

[0262] In another example, the processor 604 and / or the transceiver 608 can support wireless communication at the device 602 according to examples as disclosed herein. For example, the processor 604 and / or the transceiver 608 can be configured to or otherwise support means for: receiving a notification including configuration information indicating whether to start one or more timers in response to a PUSCH transmitted on a HARQ process; and operating the one or more timers based on the configuration information in response to the PUSCH transmitted on the HARQ process.

[0263] In addition, in some embodiments, one or more timers include a drx-HARQ-RTT-TimerUL timer; the configuration information further specifies whether to monitor the retransmission authorization of the PDCCH or to perform one or more of HARQ transmissions on the PUSCH; the configuration information includes: a first HARQ process configuration, for which one or more timers are started in response to a PUSCH transmitted on the HARQ process; and a second HARQ process configuration, for which one or more timers are not started in response to a PUSCH transmitted on the HARQ process; in order to operate one or more timers in response to a PUSCH transmitted on the HARQ process, the processor and the transceiver are configured to cause the device to: start one or more timers based on the first HARQ process configuration; or not start one or more timers based on the second HARQ process configuration.

[0264] In another example, the processor 604 and / or the transceiver 608 can support wireless communication at the device 602 according to examples as disclosed herein. For example, the processor 604 and / or the transceiver 608 can be configured to or otherwise support means for: receiving a notification including configuration information including an uplink CG and an indication of whether to start one or more timers in response to an uplink transmission on the uplink CG; and operating one or more timers based on the configuration information in response to an uplink transmission on the uplink CG.

[0265] In addition, in some embodiments, one or more timers include one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer; the configuration information includes an indication of not starting one or more timers in response to an uplink transmission of a specific data type on an uplink CG; the configuration information includes one or more timer values ​​applied to the one or more timers in response to an uplink transmission on the uplink CG; in order to operate one or more timers in response to an uplink transmission on the uplink CG, the processor and transceiver are configured to cause the device to apply one or timer values ​​to the one or more timers; the configuration information includes an uplink CG configuration for XR data transmission on the uplink CG; the processor and transceiver are configured to cause the device to: apply the uplink CG configuration for XR data transmission to the uplink CG; and transmit XR data on the uplink CG configured for XR data transmission.

[0266] In another example, the processor 604 and / or the transceiver 608 can support wireless communication at the device 602 according to examples as disclosed herein. For example, the processor 604 and / or the transceiver 608 can be configured to or otherwise support means for: receiving a notification including configuration information including an uplink configured grant (CG) configuration and an indication of whether to start one or more timers in response to an uplink transmission on a physical uplink shared channel (PUSCH) resource configured by the uplink configured grant; and operating one or more timers based on the configuration information in response to an uplink transmission on the CG PUSCH resource.

[0267] In addition, in some embodiments, one or more timers include one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer; the configuration information includes an indication not to start one or more timers in response to an uplink transmission on a CG PUSCH resource; the configuration information includes an indication not to start one or more timers in the first symbol after the end of the PUSCH transmission; the configuration information includes one or more timer values ​​applied to the one or more timers in response to an uplink transmission on a CG PUSCH resource; in order to operate one or more timers in response to an uplink transmission on an uplink CG, the processor is configured to cause the UE to apply one or timer values ​​to the one or more timers; the configuration information includes an uplink CG configuration for extended reality (XR) data transmission; the processor is configured to cause the UE to: apply the uplink CG configuration to extended reality (XR) data transmission; and transmit XR data on the CG PUSCH resources of the uplink CG configuration configured for XR data transmission.

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

[0269] 606 may include random access memory (RAM) and read-only memory (ROM). 606 may store computer-readable, computer-executable code, which includes instructions that, when executed by processor 604, cause device 602 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. In some embodiments, the code may not be directly executable by processor 604, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some embodiments, 606 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0270] I / O controller 610 can manage input and output signals of device 602. I / O controller 610 can also manage peripheral devices that are not integrated into device 2402. In some embodiments, I / O controller 610 can represent a physical connection or port to an external peripheral device. In some embodiments, I / O controller 610 can utilize an operating system, such as or another known operating system. In some embodiments, I / O controller 610 may be implemented as part of a processor (e.g., processor M08). In some embodiments, a user may interact with device 602 via I / O controller 610 or via hardware components controlled by I / O controller 610.

[0271] In some embodiments, the device 602 may include a single antenna 612. However, in some other embodiments, the device 602 may have more than one antenna 612 (i.e., multiple antennas) including multiple antenna panels or antenna arrays, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously. The transceiver 608 may communicate bidirectionally via one or more antennas 612, wired or wireless links as described herein. For example, the transceiver 608 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 608 may also include a modem to modulate packets, provide the modulated packets to one or more antennas 612 for transmission, and demodulate packets received from the one or more antennas 612.

[0272] Figure 7An example of a block diagram 700 illustrating an apparatus 702 (e.g., a device) that supports timing control in wireless communications according to aspects of the present disclosure. The apparatus 702 may be an example of a network entity 102 (e.g., a base station) as described herein. The apparatus 702 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The apparatus 702 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 704, a memory 706, a transceiver 708, and an I / O controller 710. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0273] The processor 704, the memory 706, the transceiver 708, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 704, the memory 706, the transceiver 708, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0274] In some implementations, the processor 704, memory 706, transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some implementations, the processor 704 and the memory 706 coupled to the processor 704 may be configured to perform one or more of the functions described herein (e.g., the processor 704 executes instructions stored in the memory 706). For example, in the context of the network entity 102, the transceiver 708 and the processor 704 coupled to the transceiver 708 are configured to cause the network entity 102 to perform various described operations and / or combinations thereof.

[0275] For example, the processor 704 and / or the transceiver 708 can support wireless communication at the device 702 according to examples as disclosed herein. For example, the processor 704 and / or the transceiver 708 can be configured to or otherwise support means for: generating a DCI that allocates a resource set for a HARQ process, wherein the DCI includes a field indicating whether to start a timer; and transmitting the DCI to a UE.

[0276] In addition, in some embodiments, the timer is drx-HARQ-RTT-TimerDL; the timer is drx-inactivityTimer; the DCI further includes an indication of whether HARQ feedback is enabled or disabled; the DCI further includes an indication that the timer is not started if the PDB is below a threshold; the DCI further includes an indication that the device will transition to sleep mode after a transmission associated with the downlink resources; the DCI further includes an indication of the end of the data burst after which the timer is started.

[0277] In another example, the processor 704 and / or the transceiver 708 can support wireless communication at the device 702 according to examples as disclosed herein. For example, the processor 704 and / or the transceiver 708 can be configured to or otherwise support means for: generating a notification identifying wireless resources and a DRX configuration; and transmitting the notification to the UE.

[0278] Furthermore, in some implementations, the notification includes a DRX configuration identifier; the notification is transmitted as part of the DCI; the notification includes multiple DRX configurations; the notification includes multiple DRX configurations and indicates one or more of a search space or a CORESET for each of the DRX configurations.

[0279] In another example, the processor 704 and / or the transceiver 708 can support wireless communication at the device 702 according to examples as disclosed herein. For example, the processor 704 and / or the transceiver 708 can be configured to or otherwise support means for: generating a notification identifying a maximum delay time for sending a scheduling request; and transmitting the notification to a UE.

[0280] In addition, in some embodiments, the maximum delay time is based at least in part on the remaining PDB; the notification further includes instructions indicating the following: when the UE is in an active DRX state, transmit a scheduling request before the expiration of a scheduling request timer configured at least in part based on the maximum delay time; and when the UE is in an inactive DRX state, transmit a scheduling request after the expiration of the scheduling request timer.

[0281] In another example, the processor 704 and / or the transceiver 708 can support wireless communication at the device 702 according to examples as disclosed herein. For example, the processor 704 and / or the transceiver 708 can be configured to or otherwise support means for: generating a notification including configuration information indicating whether to start one or more timers in response to a PUSCH transmitted on a HARQ process; and transmitting the notification to a UE.

[0282] In addition, in some embodiments, one or more timers include a drx-HARQ-RTT-TimerUL timer; the configuration information further specifies whether to monitor retransmission authorization of the PDCCH or to perform one or more of HARQ transmissions on the PUSCH; the configuration information includes: a first HARQ process configuration, for which one or more timers are started in response to a PUSCH transmitted on the HARQ process; and a second HARQ process configuration, for which one or more timers are not started in response to a PUSCH transmitted on the HARQ process.

[0283] In another example, the processor 704 and / or the transceiver 708 can support wireless communication at the device 702 according to examples as disclosed herein. For example, the processor 704 and / or the transceiver 708 can be configured to or otherwise support means for: generating a notification including configuration information including an uplink CG and an indication of whether to start one or more timers in response to an uplink transmission on the uplink CG; and transmitting the notification to the UE.

[0284] In addition, in some embodiments, one or more timers include one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer; the configuration information includes an indication of not starting one or more timers in response to an uplink transmission of a specific data type on the uplink CG; the configuration information includes one or more timer values ​​applied to the one or more timers in response to an uplink transmission on the uplink CG; the configuration information includes an uplink CG configuration for XR data transmission on the uplink CG.

[0285] In another example, the processor 704 and / or the transceiver 708 can support wireless communication at the device 702 according to examples as disclosed herein. For example, the processor 704 and / or the transceiver 708 can be configured to or otherwise support means for: generating a notification including configuration information including an uplink configured grant (CG) configuration and an indication of whether to start one or more timers in response to an uplink transmission on a physical uplink shared channel (PUSCH) resource configured by the uplink configured grant; and transmitting the notification to a UE; the one or more timers including one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer; the configuration information including an indication not to start one or more timers in response to an uplink transmission on a CG PUSCH resource; the configuration information including an indication not to start one or more timers in a first symbol after an end of a PUSCH transmission; the configuration information including an uplink CG configuration for an extended reality (XR) data transmission.

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

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

[0288] I / O controller 710 can manage input and output signals of device 702. I / O controller 710 can also manage peripheral devices that are not integrated into device 2402. In some embodiments, I / O controller 710 can represent a physical connection or port to an external peripheral device. In some embodiments, I / O controller 710 can utilize an operating system, such as or another known operating system. In some embodiments, I / O controller 710 may be implemented as part of a processor (e.g., processor M06). In some embodiments, a user may interact with device 702 via I / O controller 710 or via hardware components controlled by I / O controller 710.

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

[0290] Figure 8 Flowchart illustrating a method 800 of supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 800 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 800 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0291] At 802, the method may include receiving a DCI at a first time instance that allocates a resource set for a HARQ process, wherein the DCI includes a field indicating whether to start a timer. The operations of 802 may be performed according to examples as described herein. In some embodiments, aspects of the operations of 802 may be performed as described in reference to Figure 1 The described device performs.

[0292] At 804, the method may include starting a timer at a second time instance based at least in part on the field indicating a start timer. The operations of 804 may be performed according to examples as described herein. In some embodiments, aspects of the operations of 804 may be described as described in reference to Figure 1The described device performs.

[0293] Fig. 9 Flowchart illustrating a method 900 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 900 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 900 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0294] At 902, the method may include receiving a notification identifying a wireless resource and a DRX configuration. The operations of 902 may be performed according to examples as described herein. In some implementations, aspects of the operations of 902 may be performed as described in reference to Figure 1 The described device performs.

[0295] At 904, the method may include selecting a DRX timer from a plurality of different DRX timers based on the DRX configuration. The operations of 904 may be performed according to examples as described herein. In some embodiments, aspects of the operations of 904 may be as described in reference Figure 1 The described device performs.

[0296] At 906, the method may include configuring a DRX timer. The operations of 906 may be performed according to examples as described herein. In some embodiments, aspects of the operations of 906 may be performed as described in reference Figure 1 The described device performs.

[0297] Fig.10 Flowchart illustrating a method 1000 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 1000 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1000 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0298] At 1002, the method may include receiving a notification identifying a maximum delay time for sending a scheduling request. The operations of 1002 may be performed according to examples as described herein. In some embodiments, aspects of the operations of 1002 may be performed as described in reference to Figure 1 The described device performs.

[0299] At 1004, the method may include transmitting a scheduling request at a time instance determined at least in part based on the maximum delay time. The operations of 1004 may be performed according to examples as described herein. In some embodiments, aspects of the operations of 1004 may be performed as described in reference to Figure 1 The described device performs.

[0300] Fig.11 1. Flowchart illustrating a method 1100 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 1100 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1100 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0301] At 1102, the method may include receiving a notification including configuration information indicating whether to start one or more timers in response to a PUSCH transmitted on a HARQ process. The operations of 1102 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1102 may be as described in reference to Figure 1 The described device performs.

[0302] At 1104, the method may include operating one or more timers based on the configuration information in response to a PUSCH transmitted on the HARQ process. The operations of 1104 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1104 may be as described in reference to Figure 1 The described device performs.

[0303] Fig.12 1. Flowchart illustrating a method 1200 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 1200 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1200 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0304] At 1202, the method may include receiving a notification including configuration information, the configuration information including an uplink CG and an indication of whether to start one or more timers in response to an uplink transmission on the uplink CG. The operations of 1202 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1202 may be as described in reference to Figure 1The described device performs.

[0305] At 1204, the method may include operating one or more timers based on the configuration information in response to an uplink transmission on the uplink CG. The operations of 1204 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1204 may be described as described in reference to Figure 1 The described device performs.

[0306] Fig.13 1300 is a flowchart illustrating a method 1300 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 1300 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1300 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0307] At 1302, the method may include applying an uplink CG configuration for XR data transmission to the uplink CG. The operations of 1302 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1302 may be described as described in reference to Figure 1 The described device performs.

[0308] At 1304, the method may include transmitting XR data on an uplink CG configured for XR data transmission. The operations of 1304 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1304 may be described as described in reference to Figure 1 The described device performs.

[0309] Fig.14 1400. The operations of the method 1400 may be performed by an apparatus or component thereof as described herein. For example, the operations of the method 1400 may be performed by an apparatus or component thereof as described herein. Figures 1 to 7 The described network entity 102 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0310] At 1402, the method may include generating a DCI that allocates a resource set for a HARQ process, wherein the DCI includes a field indicating whether to start a timer. The operations of 1402 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1402 may be as described in reference to Figure 1 The described device performs.

[0311] At 1404, the method may include transmitting the DCI to the UE. The operations of 1404 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1404 may be performed as described in reference to Figure 1 The described device performs.

[0312] Fig.15 1500 is a flowchart illustrating a method 1500 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 1500 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1500 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described network entity 102 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0313] At 1502, the method may include generating a notification identifying a wireless resource and a DRX configuration. The operations of 1502 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1502 may be performed as described in reference to Figure 1 The described device performs.

[0314] At 1504, the method may include transmitting a notification to the UE. The operations of 1504 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1504 may be performed as described in reference to Figure 1 The described device performs.

[0315] Fig.16 1600 is a flowchart illustrating a method 1600 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 1600 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1600 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described network entity 102 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0316] At 1602, the method may include generating a notification identifying a maximum delay time for sending a scheduling request. The operations of 1602 may be performed according to examples as described herein. In some embodiments, aspects of the operations of 1602 may be performed as described in reference to Figure 1 The described device performs.

[0317] At 1604, the method may include transmitting a notification to the UE. The operations of 1604 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1604 may be performed as described in reference to Figure 1 The described device performs.

[0318] Fig.17 1700 is a flowchart illustrating a method 1700 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 1700 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1700 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described network entity 102 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0319] At 1702, the method may include generating a notification including configuration information indicating whether to start one or more timers in response to a PUSCH transmitted on a HARQ process. The operations of 1702 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1702 may be as described in reference to Figure 1 The described device performs.

[0320] At 1704, the method may include transmitting a notification to the UE. The operations of 1704 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1704 may be performed as described in reference to Figure 1 The described device performs.

[0321] Fig.18 1800 is a flowchart illustrating a method 1800 for supporting timing control in wireless communications according to aspects of the present disclosure. The operations of the method 1800 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1800 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 7 The described network entity 102 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0322] At 1802, the method may include generating a notification including configuration information, the configuration information including an uplink CG and an indication of whether to start one or more timers in response to an uplink transmission on the uplink CG. The operations of 1802 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1802 may be as described in reference to Figure 1 The described device performs.

[0323] At 1804, the method may include transmitting a notification to the UE. The operations of 1804 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1804 may be performed as described in reference to Figure 1 The described device performs.

[0324] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0325] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0326] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features that implement the functions may also be physically located at various locations, including being distributed so that portions of the functions are implemented at different physical locations.

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

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

[0329] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of..." or "one or more of..." or "one or both of...") indicates an inclusive list, so 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 (e.g., A and B and C). In addition, as used herein, including in the claims, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on." In addition, as used herein, including in the claims, a "set" may include one or more elements.

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

[0331] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some examples, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0332] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment UE for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the UE to: receiving a notification comprising configuration information including an uplink configured grant CG configuration and an indication of whether to start one or more timers in response to an uplink transmission on a physical uplink shared channel (PUSCH) resource configured by the uplink configured grant; and In response to an uplink transmission on the CG PUSCH resources, the one or more timers are operated based on the configuration information.

2. The UE of claim 1, wherein the one or more timers comprise one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer.

3. The UE of claim 1, wherein the configuration information comprises an indication not to start the one or more timers in response to the uplink transmission on the CG PUSCH resources. 4 . The UE of claim 3 , wherein the configuration information comprises an indication not to start one or more timers in a first symbol after the PUSCH transmission ends.

5. The UE of claim 1, wherein the configuration information comprises one or more timer values ​​applied to the one or more timers in response to the uplink transmission on the CG PUSCH resources.

6. A UE according to claim 5, wherein in order to operate the one or more timers in response to the uplink transmission on the uplink CG, the processor is configured to cause the UE to apply the one or timer values ​​to the one or more timers.

7. The UE according to claim 1, wherein the configuration information includes an uplink CG configuration for extended reality (XR) data transmission.

8. The UE of claim 1, wherein the processor is configured to cause the UE to: Applying the uplink CG configuration to extended reality XR data transmission; and XR data is transmitted on the CG PUSCH resources of the uplink CG configuration configured for XR data transmission.

9. A base station for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the base station to: generating a notification including configuration information, the configuration information including an uplink configured grant CG configuration and an indication of whether to start one or more timers in response to an uplink transmission on a physical uplink shared channel (PUSCH) resource configured by the uplink configured grant; and The notification is transmitted to the UE.

10. The base station of claim 9, wherein the one or more timers include one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer.

11. The base station of claim 9, wherein the configuration information comprises an indication not to start the one or more timers in response to the uplink transmission on the CG PUSCH resources. 12 . The base station according to claim 11 , wherein the configuration information includes an indication not to start one or more timers in a first symbol after the end of the PUSCH transmission.

13. The base station according to claim 9, wherein the configuration information includes an uplink CG configuration for extended reality (XR) data transmission.

14. A method performed by a user equipment UE, the method comprising: receiving a notification comprising configuration information including an uplink configured grant CG configuration and an indication of whether to start one or more timers in response to an uplink transmission on a physical uplink shared channel (PUSCH) resource configured by the uplink configured grant; and In response to an uplink transmission on the CG PUSCH resources, the one or more timers are operated based on the configuration information.

15. The method of claim 14, wherein the one or more timers include one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer.

16. The method of claim 14, wherein the configuration information comprises an indication not to start the one or more timers in response to the uplink transmission on the CG PUSCH resources.

17. The method of claim 16, wherein the configuration information includes an indication not to start one or more timers in a first symbol after the end of the PUSCH transmission.

18. A method performed by a base station, the method comprising: generating a notification including configuration information, the configuration information including an uplink configured grant CG configuration and an indication of whether to start one or more timers in response to an uplink transmission on a physical uplink shared channel (PUSCH) resource configured by the uplink configured grant; and The notification is transmitted to the UE.

19. The method of claim 18, wherein the one or more timers include one or more of a drx-HARQ-RTT-TimerUL timer or a drx-RetransmissionTimerUL timer.

20. The method of claim 18, wherein the configuration information comprises an indication not to initiate the one or more timers in response to the uplink transmission on the CG PUSCH resources.

Images