Discontinuous reception enhancements for reduced physical downlink control channel monitoring and jitter handling

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a dynamic indication of a start offset and length of discontinuous reception (DRX) on duration from a network entity. The UE may monitor a Physical Downlink Control Channel (PDCCH) during the DRX ON duration to obtain a message for an initial transmission in a scheduled transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX ON duration. The UE may stop monitoring of the PDCCH after a final transmission in the transmission burst. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 365,180, filed on May 23, 2022, entitled “DISCONTINUOUS RECEPTION ENHANCEMENTS FOR REDUCED PHYSICAL DOWNLINK CONTROL CHANNEL MONITORING AND JITTER HANDLING,” and U.S. Non-Provisional Patent Application No. 18 / 185,472, filed on March 17, 2023, entitled “DISCONTINUOUS RECEPTION ENHANCEMENTS FOR REDUCED PHYSICAL DOWNLINK CONTROL CHANNEL MONITORING AND JITTER HANDLING,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus associated with discontinuous reception (DRX) enhancements for reduced physical downlink control channel (PDCCH) monitoring and jitter handling. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a dynamic indication of a start offset and length of a discontinuous reception (DRX) on-duration from a network entity. The one or more processors may be configured to monitor a physical downlink control channel (PDCCH) during the DRX on-duration to obtain a message for an initial transmission in a scheduled transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on-duration. The one or more processors may be configured to stop monitoring the PDCCH after the final transmission in the transmission burst.

[0008] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to determine a start offset and a length of a DRX on duration based at least in part on one or more traffic arrival statistics. The one or more processors may be configured to send a dynamic indication of the start offset and the length of the DRX on duration to a UE.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a dynamic indication of a start offset and length of a DRX on duration from a network entity. The method may include monitoring a PDCCH during the DRX on duration to obtain a message scheduling an initial transmission in a transmit burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on duration. The method may include stopping monitoring of the PDCCH after a final transmission in the transmit burst.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include determining a start offset and a length of a DRX on duration based at least in part on one or more traffic arrival statistics. The method may include sending a dynamic indication of the start offset and the length of the DRX on duration to a UE.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a dynamic indication of a start offset and length of a DRX on duration from a network entity. The instruction set, when executed by one or more processors of the UE, may cause the UE to monitor a PDCCH during the DRX on duration to obtain a message for scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on duration. The instruction set, when executed by one or more processors of the UE, may cause the UE to stop monitoring the PDCCH after the final transmission in the transmission burst.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to determine a start offset and a length of a DRX on-duration based at least in part on one or more traffic arrival statistics. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a dynamic indication of the start offset and the length of the DRX on-duration to a UE.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a dynamic indication of a start offset and length of a DRX on duration from a network entity. The apparatus may include means for monitoring a PDCCH during the DRX on duration for a message scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on duration. The apparatus may include means for stopping monitoring of the PDCCH after a final transmission in the transmission burst.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for determining a start offset and a length of a DRX On Duration based at least in part on one or more traffic arrival statistics. The apparatus may include means for sending a dynamic indication of the start offset and the length of the DRX On Duration to a UE.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings and description and as illustrated in the accompanying drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0019] Figure 2is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0021] Figure 4 is a diagram illustrating an example of a discontinuous reception (DRX) configuration according to the present disclosure.

[0022] Figure 5 is a diagram illustrating an example associated with DRX enhancement for reduced physical downlink control channel (PDCCH) monitoring and jitter handling according to the present disclosure.

[0023] Figure 6 to Figure 7 is a diagram illustrating example procedures associated with DRX enhancement for reduced PDCCH monitoring and jitter handling according to the present disclosure.

[0024] Figures 8 to 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0025] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0026] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0027] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0028] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a radio protocol stack that is physically or logically distributed between two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0029] In some examples, the network node 110 is or includes a network entity, such as a RU, that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network entity, such as a DU, that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network entity, such as a CU, that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more DUs, and / or one or more CUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a RU, a DU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other and / or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0030] In some aspects, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station and / or a base station subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro base station. A base station for a pico cell may be referred to as a pico base station. A base station for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, network node 110a may be a macro base station for macro cell 102a, network node 110b may be a pico base station for pico cell 102b, and network node 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0031] In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (eg, a mobile base station).

[0032] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120 or network nodes 110. Figure 1 In the example shown, network node 110d (e.g., a relay base station) can communicate with network node 110a (e.g., a macro base station) and UE 120d to facilitate communication between network node 110a and UE 120d. A network node 110 that relays communications may be referred to as a relay station, relay base station, relay node, relay, etc.

[0033] The wireless network 100 may be a heterogeneous network including different types of network nodes 110, such as macro base stations, pico base stations, femto base stations, relay base stations, TRPs, RUs, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0034] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul link or a wired backhaul link. In some aspects, the network controller 130 may include a CU or a core network device.

[0035] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless medium.

[0036] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0037] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0038] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0039] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0040] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0041] In view of the above examples, unless otherwise specifically stated, it should be understood that where the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that where the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0042] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a dynamic indication of a start offset and length of a discontinuous reception (DRX) on-duration from a network entity (e.g., network node 110); monitor a physical downlink control channel (PDCCH) during the DRX on-duration for a message scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on-duration; and stop monitoring of the PDCCH after a final transmission in a transmission burst. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0043] In some aspects, a network entity (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may determine a start offset and a length of a DRX On Duration based at least in part on one or more traffic arrival statistics; and send a dynamic indication of the start offset and the length of the DRX On Duration to the UE 120. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0044] As indicated above, Figure 1 are provided as examples. Other examples may vary from Figure 1 An example of description.

[0045] Figure 22 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. For example, some network nodes 110 may not include a radio frequency component.

[0046] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0047] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0048] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0049] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2One or more antenna elements of one or more components in.

[0050] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 5 to 9 ) or any aspect of any of the methods described herein.

[0051] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 5 to 9 ) or any aspect of any of the methods described herein.

[0052] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 6 The process of 600 Figure 7 700 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process 700 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0053] In some aspects, the UE 120 includes: means for receiving a dynamic indication of a start offset and length of a DRX on duration from a network entity (e.g., the network node 110); means for monitoring a PDCCH during the DRX on duration for a message scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on duration; and / or means for stopping monitoring of the PDCCH after a final transmission in the transmission burst. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0054] In some aspects, the network entity (e.g., the network node 110) includes: means for determining a start offset and a length of the DRX On Duration based at least in part on one or more traffic arrival statistics; and / or means for sending a dynamic indication of the start offset and the length of the DRX On Duration to the UE 120. In some aspects, the means for the network entity to perform the operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0055] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0056] As mentioned above, Figure 2 are provided as examples. Other examples may vary from Figure 2 An example of description.

[0057] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0058] The deployment of a communication system (such as a 5G NR system) may be arranged with various components or components in a variety of ways. In a 5GNR system or network, a network node may be implemented in an aggregated architecture or a decomposed architecture. For example, a network node or one or more units (or one or more components) that perform network node functionality may be implemented as an aggregated network node (sometimes referred to as an independent base station or a monolithic base station) or a decomposed network node. A "network entity" or "network node" may refer to a decomposed network node, an aggregated network node, or one or more entities of a decomposed network node (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0059] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0060] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN) (such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0061] The decomposed base station 300 architecture may include one or more CUs 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links (such as an F1 interface). The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more radio frequency (RF) access links. In some aspects, a UE 120 may be served by multiple RUs 340 simultaneously. DU 330 and RU 340 may also be referred to as “O-RAN DU (O-DU)” and “O-RAN RU (O-RU)”, respectively. A network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0062] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0063] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0064] The DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of the following depending at least in part on a functional split such as that defined by 3GPP: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, the DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0065] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0066] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0067] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface connecting one or more CUs 310, one or more DUs 330, or both, and an O-eNB to the near-RT RIC 325 (such as via an E2 interface).

[0068] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0069] As mentioned above, Figure 3 are provided as examples. Other examples may vary from Figure 3 An example of description.

[0070] Figure 4 is a diagram illustrating an example 400 of a DRX configuration according to the present disclosure.

[0071] like Figure 4 As shown, the network node 110 may send a DRX configuration to the UE 120 to configure a DRX cycle 405 for the UE 120. The DRX cycle 405 may include a DRX on-duration 410 (e.g., during which the UE 120 is awake or active) and an opportunity to enter a DRX sleep state 415. As used herein, the time during which the UE 120 is configured to be active during the DRX on-duration 410 may be referred to as an active time, and the time during which the UE 120 is configured to be in the DRX sleep state 415 may be referred to as an inactive time. As described below, the UE 120 may monitor the PDCCH during the active time, and the UE 120 may avoid monitoring the PDCCH during the inactive time.

[0072] During the DRX on duration 410 (e.g., active time), the UE 120 may monitor a downlink control channel (e.g., PDCCH), as indicated by reference numeral 420. For example, the UE 120 may monitor the PDCCH for downlink control information (DCI) related to the UE 120. In the event that the UE 120 does not detect and / or successfully decode any PDCCH communication intended for the UE 120 during the DRX on duration 410, the UE 120 may enter a sleep state 415 (e.g., during inactive time) at the end of the DRX on duration 410, as indicated by reference numeral 425. In this way, the UE 120 may conserve battery power and reduce power consumption. As shown, the DRX cycle 405 may be repeated at a configured periodicity according to the DRX configuration.

[0073] In the event that the UE 120 detects and / or successfully decodes a PDCCH communication intended for the UE 120, the UE 120 may remain in an active state (e.g., awake) for the duration of the DRX inactivity timer 430 (e.g., which may extend the active time). The UE 120 may start the DRX inactivity timer 430 at the time the PDCCH communication is received (e.g., in a transmit time interval (TTI), such as a timeslot or subframe, in which the PDCCH communication is received). The UE 120 may remain in the active state until the DRX inactivity timer 430 expires, at which time the UE 120 may enter the sleep state 415 (e.g., within the inactivity time), as indicated by reference numeral 435. During the duration of the DRX inactivity timer 430, the UE 120 may continue to monitor the PDCCH communication, may obtain downlink data communications scheduled by the PDCCH communication (e.g., on a downlink data channel such as a physical downlink shared channel (PDSCH)), and / or may prepare and / or send uplink communications scheduled by the PDCCH communication (e.g., on a physical uplink shared channel (PUSCH)). The UE 120 may restart the DRX inactivity timer 430 each time a PDCCH communication of the UE 120 is detected for an initial transmission (e.g., but not for a retransmission). By operating in this manner, the UE 120 may conserve battery power and reduce power consumption by entering the sleep state 415.

[0074] As mentioned above, Figure 4 are provided as examples. Other examples may vary from Figure 4 An example of description.

[0075] There are existing and ongoing efforts to configure cellular networks to support extended reality (XR) services, which is a general term covering immersive technologies such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and virtual levels inserted between VR, AR, and MR. For example, VR is a rendered version of an audiovisual scene, where the rendering is designed to simulate the visual and auditory stimulation of the real world as naturally as possible when the observer or user moves within the range defined by the VR application. VR typically requires the user to wear a head-mounted display (HMD) to completely replace the field of view with simulated visual components, and use headphones, speakers, and / or another suitable audio device to listen to the accompanying audio. In VR applications, the user's head and motion tracking is also typically required to allow the simulated visual and audio components to be updated to ensure that from the user's perspective, the items and sound sources are consistent with the user's movements. In AR applications, users are typically provided with additional information or artificially generated items or content that is overlaid on the current environment. The additional information or content is typically visual and / or auditory, and the observation of the current environment can be direct (without intermediate sensing, processing, and rendering) or indirect (where the perception of the environment can be relayed via sensors and augmented or processed). MR is an advanced form of AR in which some virtual elements are inserted into the physical scene to provide the illusion that the elements are part of the real scene.

[0076] It is expected that XR will improve productivity and convenience for consumers, enterprises and public institutions in various application areas such as entertainment, training, education, remote support, remote control, communication and / or virtual meetings. XR can be used in many industry fields, including healthcare, real estate, shopping, transportation, manufacturing and / or other industry fields. VR has been used for games at home and in dedicated places, for virtual tours in real estate environments, for education and training purposes, and for remote participation in live events such as concerts and sports. In addition, AR and MR use cases have great potential. For example, while VR applications rely on HMDs that separate users from the physical environment and limit mobility, AR and MR applications allow users to exist in reality and move freely even when using HMDs. Many smartphone users have experienced basic forms of AR through games involving searching for virtual objects in real-world environments and applications that enable shoppers to visualize new furniture at home before making a purchase. In addition, AR technology can be used with HMDs to free the user's hands, thereby improving worker efficiency by providing the ability to overlay information in the real world while both hands are available.

[0077] However, configuring wireless networks to support latency requirements, quality of experience (QoE) requirements, high data rates, and / or other characteristics associated with XR services presents various challenges. For example, at an XR-enabled UE, XR services may include posture data (e.g., related to position and orientation in space), video data, audio data, and / or other data sent by and / or to the XR-enabled UE, may have video frame sizes that vary over time, and / or may have quasi-periodic packet arrival times with application jitter (e.g., variations in delays and / or arrival times of XR services). In addition, due to uncertain application processing times, service arrival times at network nodes (e.g., RAN nodes) are periodic with non-negligible jitter. Video frame sizes are orders of magnitude larger than packets in voice or industrial control communications and are not fixed over time. Instead, segmentation of each frame is expected, which means that packets arrive in bursts and must be processed together to meet strict bounded latency requirements. For example, as described herein, a burst, a traffic burst, a transmission burst, etc. may refer to a continuous sequence of packets having a shorter inter-packet arrival time and / or a higher traffic volume than packets arriving before or after the continuous sequence of packets in the burst. Thus, XR applications typically have a traffic pattern of packet burst arrivals, and XR traffic may have different characteristics than voice or other applications that a DRX configuration is intended to handle. For example, in an existing (e.g., legacy) DRX configuration (e.g., as described above with reference to Figure 4 As described above, the DRX on duration and / or DRX active time can be consistent with a regular traffic pattern, such as one packet every twenty (20) milliseconds for voice traffic. In contrast, XR traffic has a much higher data rate than voice and tends to be highly bursty or cyclical in the sense that many packets arrive very close in time, and then there is an idle period before the next cycle begins and the next traffic burst arrives (e.g., a bursty traffic pattern may include sudden increases and / or decreases in traffic volume and / or inter-packet arrival times). In addition, XR applications are sensitive to jitter because when the UE is streaming video and / or audio data, delay variations from one packet to another can be disruptive and / or reduce QoE.

[0078] Some aspects described herein relate to an enhanced DRX configuration optimized for applications that are sensitive to jitter and / or associated with a bursty traffic pattern, such as an XR application. For example, because the maximum jitter may change over time due to changes in network conditions (e.g., load, interference, and / or other factors), some aspects described herein relate to a dynamic indication of a start offset and length of a DRX on duration associated with a DRX configuration based on an estimate of the maximum jitter. In addition, when the DRX on duration begins, some aspects described herein relate to a reduced monitoring state that the UE can use to monitor the PDCCH at the beginning of the DRX on duration, which can enable the UE to save power while waiting for the first transmission block in the transmission burst, which may not arrive at the UE until later in the DRX on duration (e.g., due to jitter). In addition, in the case where a transmission burst during the DRX active time includes an uplink transmission burst by the UE, some aspects described herein relate to an early termination indication that can be sent by the UE to a network node after the final transmission in the burst to achieve early termination of the DRX active time (e.g., before the DRX inactivity timer expires). In this way, dynamic indication of the start offset and length of the DRX on duration can ensure that jitter does not cause the UE to miss the initial transmission in a transmit burst, and reduced PDCCH monitoring and early termination indications can increase the amount of time the UE spends in a low power state for applications with bursty traffic patterns.

[0079] Figure 5 is a diagram illustrating an example 500 associated with DRX enhancement for reduced PDCCH monitoring and jitter handling according to the present disclosure. Figure 5 As shown, example 500 includes communication between UE 120 and network node 110 (e.g., a base station or a component of a base station, such as a RU, DU, and / or CU). In some aspects, network node 110 and UE 120 may be included in a wireless network, such as wireless network 100. Network node 110 and UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0080] like Figure 5As shown, and by reference numeral 510, the network node 110 may send, and the UE 120 may receive, an enhanced DRX configuration associated with one or more optimizations to improve performance and power savings for applications (e.g., XR applications) that are sensitive to jitter and / or associated with bursty traffic patterns. For example, in some aspects, the enhanced DRX configuration may be used for applications that tend to send and / or receive multiple transport blocks in short time periods (which may be referred to herein as cycles or bursts) and tend to be sensitive to jitter, which may reduce QoE (e.g., cause video and / or audio buffering) and / or cause transmissions to be missed due to inconsistency with a DRX On Duration. For example, as described herein, the enhanced DRX configuration provided by the network node 110 may define a DRX cycle associated with a DRX On Duration, which is a period of time during which the UE 120 is awake or active. During the DRX On Duration, the UE 120 may monitor the PDCCH for messages related to the UE 120 (e.g., DCI scheduling an initial uplink or downlink transmission in a burst of uplink or downlink transmissions), and the UE 120 may remain in an active state for the duration of the DRX Inactivity Timer if the UE 120 detects and / or successfully decodes a PDCCH message intended for the UE 120. Thus, the DRX Active Time may generally include the DRX On Duration and any additional time that the UE 120 remains in an active state while the DRX Inactivity Timer is running (e.g., after detecting and / or successfully decoding a PDCCH message intended for the UE 120).

[0081] In some aspects, as shown by reference numeral 520, the network node 110 may send a dynamic indication of a start offset and length of the DRX on duration to the UE 120, wherein the dynamic indication may be included in a physical layer signal (e.g., a wake-up signal) or a MAC control element (MAC-CE) received by the UE 120 before the start of the DRX on duration. In some aspects, the start offset and length of the DRX on duration may be based at least in part on a maximum jitter of a transmit burst. For example, the network node 110 may have the ability to measure or estimate the maximum jitter based on traffic arrival statistics, which may vary over time due to changes in network conditions (e.g., load, interference, activation or deactivation of communication resources, mobility, and / or other factors). Therefore, in some aspects, the network node 110 may configure the dynamic indication of the start offset and length of the DRX on duration based on the maximum jitter of the transmit burst to ensure that the PDCCH message (e.g., DCI) that schedules the initial transmission in the transmit burst will arrive at the UE 120 during the DRX on duration (e.g., while the UE 120 is monitoring the PDCCH). For example, as Figure 5As shown, the length of the DRX on duration may be at least twice the maximum jitter, which may generally refer to the maximum possible or allowed delay difference between two consecutive packets. Specifically, the jitter may be positive (e.g., in the case where the delay of a subsequent packet is greater than the delay of an earlier packet) or negative (e.g., in the case where the delay of a subsequent packet is less than the delay of an earlier packet). Therefore, in the case where the DRX on duration is configured to be shorter than the range of the maximum jitter, the first transmission in a transmission burst may potentially arrive at the UE 120 outside the DRX on duration. In such a scenario, the UE 120 may potentially miss the first transmission in the transmission burst because the UE 120 generally refrains from monitoring the PDCCH outside the DRX on duration.

[0082] Thus, as described herein, a dynamic indication of a DRX On Duration for a bursty traffic pattern or jitter-sensitive application may be configured to be at least twice the duration of the maximum jitter to ensure that the first transmission in a transmit burst arrives during the DRX On Duration (e.g., while the UE 120 is monitoring the PDCCH). Additionally, as described herein, a start offset for the DRX On Duration may be defined based on the maximum jitter of the transmit burst and the expected start time of the transmit burst. For example, the expected start time of the burst may be relatively fixed in time and may be used as a baseline for the DRX On Duration. Thus, as shown, a start offset for the DRX On Duration may be defined as the expected start of the burst plus the maximum jitter to ensure that the DRX On Duration starts no later than the earliest possible arrival time of the first transmission in the burst (e.g., to ensure that the UE 120 is awake and monitoring the PDCCH at the earliest possible arrival time of the first transmission in the burst).

[0083] like Figure 5As further shown, and by reference numeral 530, UE 120 may monitor PDCCH in a reduced monitoring state at the beginning of the DRX On Duration to obtain information about an initial transmission in a scheduled transmit burst (e.g., an initial uplink transmission in an uplink transmit burst and / or an initial downlink transmission in a downlink transmit burst). Specifically, as described herein, UE 120 may monitor PDCCH in a reduced monitoring state (e.g., a PDCCH monitoring state that consumes less power relative to other possible PDCCH monitoring states, a PDCCH monitoring state that monitors PDCCH only on a set of one or more special cells (e.g., a subset of cells of all cells), and / or a PDCCH monitoring state that monitors PDCCH only on one or more carriers in a selected frequency range) before transmitting or receiving the first transmission in a transmit burst. For example, as described above, the start offset and length of the DRX On Duration may be configured (e.g., by dynamic indication) to handle potential jitter, and due to jitter, the first transport block in a transmit burst may not arrive at UE 120 at the beginning of the DRX On Duration. Thus, to save power, the UE 120 may monitor the PDCCH in a reduced monitoring state at the beginning of the DRX on-duration. For example, in some aspects, the network node 110 may configure (e.g., via RRC signaling) one or more search space clusters (SSSGs), which may include an SSSG optimized for power saving, another SSSG optimized for throughput, etc. Thus, in some aspects, the UE 120 may monitor the PDCCH at the beginning of the DRX on-duration using a power-optimized SSSG. Additionally or alternatively, to save power before the first transmission in a burst, the network node 110 may configure the UE 120 to monitor the PDCCH only on a specific special cell (SpCell), such as a primary cell (PCell) or a primary secondary cell (PSCell), or only on a selected set of one or more special cells. Additionally or alternatively, in the case where UE 120 is configured with separate DRX configurations for different frequency ranges (e.g., a first DRX configuration for FR1 and a second DRX configuration for FR2 that generally consumes more power than FR1), network node 110 may configure UE 120 to monitor PDCCH only on a set of one or more carriers (e.g., only FR1 carriers) within the selected frequency range. Additionally or alternatively, in the case where one or more semi-persistent scheduling (SPS) opportunities are configured for UE 120, any SPS opportunities that occur before the arrival of the first transport block in a transmit burst may be skipped or deactivated.

[0084] In some aspects, UE 120 may exit the reduced monitoring state after an event related to a first transmission in a transmit burst. For example, in the case where the transmit burst is a downlink transmit burst, UE 120 may exit the reduced monitoring state when UE 120 receives an initial transmission of a new transport block included in the downlink transmit burst. Alternatively, in the case where the transmit burst is an uplink transmit burst, UE 120 may exit the reduced monitoring state when UE 120 triggers a scheduling request and performs an initial uplink transmission of a new transport block included in the uplink transmit burst. In either case, the reception or transmission of the new transport block may trigger UE 120 to monitor all PDCCH cells configured for UE 120 and / or may trigger UE 120 to switch from a power-optimized SSSG to a high-throughput SSSG or another suitable SSSG. Additionally or alternatively, after exiting the reduced monitoring state, UE 120 may not limit PDCCH monitoring to only SpCells (e.g., PDCCH monitoring may be performed on one or more secondary cells), and / or may perform PDCCH monitoring on carriers in different frequency ranges (e.g., on FR1 and FR2 carriers). Thus, as described herein, UE 120 may take one or more measures to reduce PDCCH monitoring in the reduced monitoring state (e.g., monitoring power-optimized SSSGs, fewer cells, fewer frequency ranges or carriers, etc.), and may stop implementing any one or more (or all) of these measures after exiting the reduced monitoring state.

[0085] like Figure 5 As further shown, and by reference numeral 540, the UE 120 may send an early termination indication (or burst end indication) to the network node 110 after the final uplink transmission in the uplink transmission burst, so as to terminate the DRX active time before the DRX inactivity timer expires. For example, as described herein, the UE 120 may generally start or restart the DRX inactivity timer each time a transport block is transmitted or received, which may extend the DRX active time. Thus, after the final transmission in the transmission burst, the DRX active time may be terminated by the network node 110 or the UE 120 to save power at the UE 120. For example, in the case of a downlink transmission burst, the network node 110 may know which transport block is the final transmission in the downlink transmission burst, and may send an indication to the UE 120 to terminate the DRX active time after the final transmission in the downlink transmission burst. In some aspects, the UE 120 may then reduce or terminate monitoring of the PDCCH after the final transmission in the downlink transmission burst. However, in case of uplink transmission bursts, the network node 110 may not know which transport block is the last transmission in the uplink transmission burst.

[0086] Thus, in some aspects, a UE-initiated early termination indication may be used to support termination of the DRX active time prior to expiration of the DRX inactivity timer. For example, the UE 120 may receive an indication from an application (e.g., an XR application) that a protocol data unit (PDU) to be transmitted is the last transmission in an uplink transmission burst, and the UE 120 may then transmit an early termination indication or a burst end indication with the last PDU (e.g., in a MAC-CE, uplink control information (UCI), and / or a buffer status report (BSR)). In some aspects, the network node 110 may then determine how and / or when to terminate the DRX active time. For example, the network node 110 may configure the UE 120 to skip one or more PDCCH opportunities until the DRX inactivity timer expires, may terminate the DRX active time using a DRX MAC-CE, and / or may configure the UE 120 to switch to a low power SSSG. Additionally or alternatively, the UE 120 may start a timer based at least in part on the sending of an early termination indication, and may determine whether and / or when to terminate the DRX active time based on what occurs after the early termination indication is sent. For example, in some aspects, the UE 120 may start a timer at the same time as or shortly after sending the early termination indication, and may autonomously terminate the DRX active time if the UE 120 does not receive any downlink assignment for new data before the timer expires. Alternatively, if a downlink assignment for new data is received before the timer expires, the UE 120 may restart the DRX inactivity timer.

[0087] As mentioned above, Figure 5 are provided as examples. Other examples may vary from Figure 5 An example of description.

[0088] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a UE in accordance with the present disclosure. Example process 600 is an example of operations in which a UE (eg, UE 120) performs DRX enhancement for reduced PDCCH monitoring and jitter handling.

[0089] like Figure 6 As shown, in some aspects, process 600 may include receiving a dynamic indication of a start offset and length of a DRX on-duration from a network entity (block 610). Figure 8 The communication manager 140 and / or receiving component 802 depicted in FIG. 8 may receive a dynamic indication of a start offset and length of a DRX on-duration from a network entity, as described above.

[0090] like Figure 6As further shown, in some aspects, process 600 may include: during the DRX on duration, monitoring a PDCCH for a message scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on duration (block 620). Figure 8 The communication manager 140 and / or PDCCH monitoring component 808 depicted in FIG. 1 may monitor the PDCCH during a DRX on duration to obtain a message for an initial transmission in a scheduled transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on duration, as described above.

[0091] like Figure 6 As further shown, in some aspects, process 600 may include reducing monitoring of the PDCCH after a final transmission in a transmission burst (block 630). Figure 8 The communications manager 140 and / or PDCCH monitoring component 808 depicted in FIG. 8 may cease monitoring the PDCCH after a final transmission in a transmission burst, as described above.

[0092] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0093] In a first aspect, the start offset of the DRX OnDuration is based at least in part on an expected start time of the transmit burst and a maximum jitter.

[0094] In a second aspect, alone or in combination with the first aspect, the length of the DRX OnDuration is based at least in part on a maximum jitter of the transmit burst.

[0095] In a third aspect, either alone or in combination with one or more of the first and second aspects, the dynamic indication of the start offset and the length of the DRX on duration is included in a physical layer signal or MAC-CE received before the start of the DRX on duration.

[0096] In a fourth aspect, alone or in combination with one or more of the first to third aspects, monitoring the PDCCH includes monitoring a power-optimized SSSG in the reduced monitoring state.

[0097] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, monitoring the PDCCH includes monitoring the PDCCH only on a selected set of one or more special cells in the reduced monitoring state.

[0098] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, monitoring the PDCCH comprises monitoring the PDCCH only on one or more carriers within a selected frequency range in the reduced monitoring state.

[0099] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, one or more SPS opportunities before the arrival of an initial transport block in the transmit burst are disabled or not monitored.

[0100] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, monitoring the PDCCH comprises detecting an event triggering an exit from the reduced monitoring state while monitoring the PDCCH in the reduced monitoring state, and monitoring each cell on which the PDCCH is configured and switching to a high-throughput SSSG based at least in part on the event.

[0101] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the event comprises receiving an initial transmission of a new transport block comprised in the transmission burst.

[0102] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the event comprises triggering a scheduling request to perform an initial uplink transmission of a new transport block included in the transmission burst.

[0103] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 600 includes: receiving an indication from an application during the DRX active time that the PDU to be sent is the final transmission in the transmit burst, and sending an early termination indication to the network entity to terminate the DRX active time before the DRX inactivity timer expires, at least in part based on the indication.

[0104] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the early termination indication is included in a MAC-CE, a UCI or a BSR.

[0105] In the thirteenth aspect, alone or in combination with one or more aspects of the first to twelfth aspects, process 600 includes: receiving information from the network entity to terminate the DRX active time before the expiration of the DRX inactivity timer based at least in part on the early termination indication, and terminating the DRX active time based at least in part on the information received from the network entity.

[0106] In a fourteenth aspect, either alone or in combination with one or more of aspects one to thirteen, process 600 comprises starting a timer based at least in part on sending the early termination indication, and terminating the DRX active time based at least in part on expiration of the timer without receiving a downlink assignment for new data.

[0107] In a fifteenth aspect, either alone or in combination with one or more of aspects one to fourteen, process 600 comprises starting a timer based at least in part on sending the early termination indication, and restarting the DRX inactivity timer based at least in part on receiving a downlink assignment for new data before expiration of the timer.

[0108] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 In some embodiments, the process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more blocks of the blocks of process 600 may be performed in parallel.

[0109] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a network entity in accordance with the present disclosure. The example process 700 is an example of operations in which a network entity (eg, the network node 110) performs DRX enhancement for reduced PDCCH monitoring and jitter handling.

[0110] like Figure 7 As shown, in some aspects, process 700 may include determining a start offset and length of a DRX on-duration based at least in part on one or more traffic arrival statistics (block 710). Fig. 9 The communication manager 150 and / or the DRX configuration component 908 depicted in FIG. 1 may determine a start offset and length of the DRX On-Duration based at least in part on one or more traffic arrival statistics, as described above.

[0111] like Figure 7 As further shown, in some aspects, process 700 may include sending a dynamic indication of a start offset and length of a DRX on-duration to the UE (block 720). Fig. 9 The communication manager 150 and / or the sending component 904 depicted in FIG. 1 may send a dynamic indication of the start offset and length of the DRX on-duration to the UE, as described above.

[0112] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0113] In a first aspect, the start offset of the DRX OnDuration is based at least in part on an expected start time of a transmit burst and a maximum jitter.

[0114] In a second aspect, alone or in combination with the first aspect, the length of the DRX OnDuration is based at least in part on a maximum jitter of a transmit burst.

[0115] In a third aspect, either alone or in combination with one or more of the first and second aspects, the dynamic indication of the start offset and the length of the DRX on duration is included in a physical layer signal or MAC-CE sent before the start of the DRX on duration.

[0116] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 700 includes: sending information to the UE to configure the UE to monitor the PDCCH only on a selected group of one or more special cells at the beginning of the DRX on-duration to obtain a message for an initial transmission in a scheduled transmission burst.

[0117] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 700 includes sending information to the UE to configure the UE to monitor the PDCCH only on one or more carriers within a selected frequency range at the beginning of the DRX on-duration period to obtain a message for an initial transmission in a scheduled transmission burst.

[0118] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 700 comprises: sending a transmit burst to the UE during a DRX active time, and receiving an early termination indication from the UE to terminate the DRX active time before expiration of a DRX inactivity timer.

[0119] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the early termination indication is included in a MAC-CE, a UCI or a BSR.

[0120] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 700 includes sending information to the UE to terminate the DRX active time before the DRX inactivity timer expires, at least in part based on the early termination indication.

[0121] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7The blocks depicted in the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks of the blocks in the process 700 may be performed in parallel.

[0122] Figure 8 800 is a diagram of an example apparatus 800 for wireless communication. Apparatus 800 may be a UE, or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using receiving component 802 and transmitting component 804. As further shown, apparatus 800 may include a communication manager 140. Communication manager 140 may include one or more of a PDCCH monitoring component 808 or a DRX activity time termination component 810, etc.

[0123] In some aspects, the apparatus 800 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 The process 600. In some aspects, Figure 8 The device 800 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Figure 8 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0124] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 800. In some aspects, the receiving component 802 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0125] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 806. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0126] The receiving component 802 can receive a dynamic indication of a start offset and length of a DRX on duration from a network entity. The PDCCH monitoring component 808 can monitor the PDCCH during the DRX on duration for information scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on duration. The PDCCH monitoring component 808 can stop monitoring the PDCCH after a final transmission in a transmission burst.

[0127] The DRX active time terminating component 810 may receive an indication from an application during the DRX active time that the PDU to be transmitted is the final transmission in the transmission burst. The transmitting component 804 may transmit an early termination indication to the network entity to terminate the DRX active time before the DRX inactivity timer expires based at least in part on the indication.

[0128] Receiving component 802 can receive information from a network entity to terminate the DRX active time prior to expiration of the DRX inactivity timer based at least in part on the early termination indication.DRX active time terminating component 810 can terminate the DRX active time based at least in part on the information received from the network entity.

[0129] DRX active time terminating component 810 can start a timer based at least in part on sending an early termination indication.DRX active time terminating component 810 can terminate the DRX active time based at least in part on expiration of the timer without receiving a downlink assignment for new data.

[0130] DRX activity time terminating component 810 can start a timer based at least in part on sending an early termination indication.DRX activity time terminating component 810 can restart the DRX inactivity timer based at least in part on receiving a downlink assignment for new data prior to expiration of the timer.

[0131] Figure 8 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 8 Additional components, fewer components, different components, or components arranged differently than those shown. Figure 8 Two or more components shown may be implemented in a single component, or Figure 8 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The illustrated set (one or more) of components may be described as being executable by Figure 8 Another group of components shown performs one or more functions.

[0132] Fig. 9 900 is a diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a network entity, or a network entity may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include a DRX configuration component 908, etc.

[0133] In some aspects, the apparatus 900 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0134] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0135] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0136] DRX configuring component 908 can determine a start offset and a length of the DRX On Duration based at least in part on one or more traffic arrival statistics.Transmitting component 904 can transmit a dynamic indication of a start offset and a length of the DRX On Duration to the UE.

[0137] Transmitting component 904 can transmit information to the UE configuring the UE to monitor the PDCCH only on a selected set of one or more special cells for an initial transmission in a scheduled transmission burst at the beginning of the DRX On Duration.

[0138] Transmitting component 904 can transmit information to the UE configuring the UE to monitor the PDCCH only on one or more carriers within the selected frequency range for an initial transmission in a scheduled transmission burst at the beginning of the DRX On Duration.

[0139] Transmitting component 904 can transmit a transmit burst to the UE during the DRX active time.Receiving component 902 can receive an early termination indication from the UE to terminate the DRX active time prior to expiration of the DRX inactivity timer.

[0140] The transmitting component 904 can transmit information to the UE to terminate the DRX active time before the expiration of the DRX inactivity timer based at least in part on the early termination indication.

[0141] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged differently than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The illustrated set (one or more) of components may be described as being executable by Fig. 9 Another group of components shown performs one or more functions.

[0142] The following provides an overview of some aspects of the disclosure:

[0143] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving a dynamic indication of a start offset and length of a DRX on duration from a network entity; monitoring a PDCCH during the DRX on duration to obtain a message scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX on duration; and stopping monitoring of the PDCCH after a final transmission in the transmission burst.

[0144] Aspect 2: The method according to aspect 1, wherein the start offset of the DRX on-duration is based at least in part on an expected start time and a maximum jitter of the transmission burst.

[0145] Aspect 3: The method according to any one of aspects 1 to 2, wherein the length of the DRX on-duration is based at least in part on a maximum jitter of the transmit burst.

[0146] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the dynamic indication of the start offset and the length of the DRX on duration is included in a physical layer signal or MAC-CE received before the start of the DRX on duration.

[0147] Aspect 5: The method according to any one of aspects 1 to 4, wherein monitoring the PDCCH comprises: in the reduced monitoring state, monitoring a power-optimized SSSG.

[0148] Aspect 6: The method according to any one of aspects 1 to 5, wherein monitoring the PDCCH comprises monitoring the PDCCH only on a selected set of one or more special cells in the reduced monitoring state.

[0149] Aspect 7: The method according to any one of aspects 1 to 6, wherein monitoring the PDCCH comprises monitoring the PDCCH only on one or more carriers within a selected frequency range in the reduced monitoring state.

[0150] Aspect 8: The method according to any one of aspects 1 to 7, wherein one or more SPS opportunities before the arrival of an initial transport block in the transmit burst are deactivated or not monitored.

[0151] Aspect 9: A method according to any one of Aspects 1 to 8, wherein monitoring the PDCCH comprises: while monitoring the PDCCH in the reduced monitoring state, detecting an event that triggers an exit from the reduced monitoring state; and monitoring each cell on which the PDCCH is configured and switching to a high-throughput SSSG based at least in part on the event.

[0152] Aspect 10: The method according to aspect 9, wherein the event comprises receiving an initial transmission included in the transmission burst of a new transport block.

[0153] Aspect 11: The method according to aspect 9, wherein the event comprises a scheduling request triggering the execution of an initial uplink transmission included in the transmission burst of a new transport block.

[0154] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: receiving an indication from an application during the DRX active time that the PDU to be sent is the final transmission in the transmission burst; and sending an early termination indication to the network entity to terminate the DRX active time before the expiration of the DRX inactivity timer based at least in part on the indication.

[0155] Aspect 13: The method according to aspect 12, wherein the early termination indication is included in a MAC-CE, a UCI or a BSR.

[0156] Aspect 14: According to the method described in any one of Aspects 12 to 13, the method further includes: receiving information from the network entity to terminate the DRX active time before the expiration of the DRX inactivity timer based at least in part on the early termination indication; and terminating the DRX active time based at least in part on the information received from the network entity.

[0157] Aspect 15: According to the method described in any one of Aspects 12 to 13, the method also includes: starting a timer based at least in part on sending the early termination indication; and terminating the DRX active time based at least in part on the expiration of the timer without receiving a downlink assignment for new data.

[0158] Aspect 16: According to the method described in any one of Aspects 12 to 13, the method also includes: starting a timer based at least in part on sending the early termination indication; and restarting the DRX inactivity timer based at least in part on receiving a downlink assignment for new data before the timer expires.

[0159] Aspect 17: A method of wireless communication performed by a network entity, the method comprising: determining a start offset and a length of a DRX on duration based at least in part on one or more service arrival statistics; and sending a dynamic indication of the start offset and the length of the DRX on duration to a UE.

[0160] Aspect 18: The method according to aspect 17, wherein the start offset of the DRX On-Duration is based at least in part on an expected start time of a transmit burst and a maximum jitter.

[0161] Aspect 19: The method according to any one of aspects 17 to 18, wherein the length of the DRX On Duration is based at least in part on a maximum jitter of a transmit burst.

[0162] Aspect 20: A method according to any one of Aspects 17 to 19, wherein the dynamic indication of the start offset and the length of the DRX on duration is included in a physical layer signal or MAC-CE sent before the start of the DRX on duration.

[0163] Aspect 21: According to the method described in any one of Aspects 17 to 20, the method further includes: sending information to the UE to configure the UE to monitor the PDCCH only on a selected group of one or more special cells at the beginning of the DRX on-duration to obtain a message for the initial transmission in the scheduled transmission burst.

[0164] Aspect 22: According to the method described in any one of Aspects 17 to 21, the method further includes: sending information to the UE to configure the UE to monitor the PDCCH only on one or more carriers within the selected frequency range at the beginning of the DRX on-duration to obtain a message for the initial transmission in the scheduled transmission burst.

[0165] Aspect 23: According to the method described in any one of Aspects 17 to 22, the method further includes: sending a transmit burst to the UE during the DRX active time; and receiving an early termination indication from the UE to terminate the DRX active time before the DRX inactivity timer expires.

[0166] Aspect 24: The method according to aspect 23, wherein the early termination indication is included in a MAC-CE, a UCI or a BSR.

[0167] Aspect 25: According to any one of aspects 23 to 24, the method further includes: sending information to the UE to terminate the DRX active time before the DRX inactivity timer expires, at least in part based on the early termination indication.

[0168] Aspect 26: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 16.

[0169] Aspect 27: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 16.

[0170] Aspect 28: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 16.

[0171] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 16.

[0172] Aspect 30: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 16.

[0173] Aspect 31: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 17 to 25.

[0174] Aspect 32: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 17 to 25.

[0175] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 17 to 25.

[0176] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 17 to 25.

[0177] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 17 to 25.

[0178] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0179] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0180] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0181] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0182] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "having" an element of A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., when used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving a dynamic indication of a start offset and length of a discontinuous reception (DRX) on-duration from a network entity; monitoring a physical downlink control channel (PDCCH) during the DRX On Duration for a message scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX On Duration; and Monitoring of the PDCCH is stopped after a final transmission in the transmission burst.

2. The UE of claim 1, wherein the start offset of the DRX on-duration is based at least in part on an expected start time of the transmit burst and a maximum jitter. 3 . The UE of claim 1 , wherein the length of the DRX On-Duration is based at least in part on a maximum jitter of the transmit burst.

4. The UE of claim 1, wherein the dynamic indication of the start offset and the length of the DRX on-duration is included in a physical layer signal or a medium access control (MAC) control element (MAC-CE) received before the start of the DRX on-duration. 5 . The UE of claim 1 , wherein to monitor the PDCCH, the one or more processors are configured to monitor a power optimized search space cluster in the reduced monitoring state.

6. The UE of claim 1, wherein to monitor the PDCCH, the one or more processors are configured to monitor the PDCCH only on a selected set of one or more special cells in the reduced monitoring state.

7. The UE of claim 1, wherein to monitor the PDCCH, the one or more processors are configured to monitor the PDCCH only on one or more carriers within a selected frequency range in the reduced monitoring state.

8. The UE of claim 1, wherein one or more semi-persistent scheduling opportunities before an initial transport block in the transmit burst arrives are deactivated or not monitored.

9. The UE of claim 1 , wherein to monitor the PDCCH, the one or more processors are configured to: while monitoring the PDCCH in the reduced monitoring state, detecting an event that triggers an exit from the reduced monitoring state; and Each cell on which the PDCCH is configured is monitored and switched to a high throughput search space cluster based at least in part on the event.

10. The UE of claim 9, wherein the event comprises receiving an initial transmission comprised in the transmit burst of a new transport block.

11. The UE of claim 9, wherein the event comprises a scheduling request triggering execution of an initial uplink transmission included in the transmission burst of a new transport block.

12. The UE of claim 1, wherein the one or more processors are further configured to: receiving from an application during a DRX active time a protocol data unit (PDU) to be transmitted is an indication of said final transmission in said transmit burst; and An early termination indication is sent to the network entity to terminate the DRX active time prior to expiration of a DRX inactivity timer based at least in part on the indication.

13. The UE of claim 12, wherein the early termination indication is included in a medium access control (MAC) control element (MAC-CE), uplink control information, or a buffer status report.

14. The UE of claim 12, wherein the one or more processors are further configured to: receiving, from the network entity, information to terminate the DRX active time prior to expiration of the DRX inactivity timer based at least in part on the early termination indication; and The DRX active time is terminated based at least in part on the information received from the network entity.

15. The UE of claim 12, wherein the one or more processors are further configured to: starting a timer based at least in part on sending the early termination indication; and The DRX active time is terminated based at least in part on expiration of the timer without receiving a downlink assignment for new data.

16. The UE of claim 12, wherein the one or more processors are further configured to: starting a timer based at least in part on sending the early termination indication; and The DRX inactivity timer is restarted based at least in part on receiving a downlink assignment for new data prior to expiration of the timer.

17. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: determining a start offset and a length of a discontinuous reception (DRX) on-duration based at least in part on one or more traffic arrival statistics; as well as A dynamic indication of the start offset and the length of the DRX On-Duration is sent to a user equipment (UE).

18. The network entity of claim 17, wherein the start offset of the DRX On-Duration is based at least in part on an expected start time of a transmit burst and a maximum jitter.

19. The network entity of claim 17, wherein the length of the DRX On-Duration is based at least in part on a maximum jitter of a transmit burst.

20. The network entity of claim 17, wherein the dynamic indication of the start offset and the length of the DRX On Duration is included in a physical layer signal or a Medium Access Control (MAC) Control Element (MAC-CE) sent prior to the start of the DRX On Duration.

21. The network entity of claim 17, wherein the one or more processors are further configured to: Information is sent to the UE to configure the UE to monitor a physical downlink control channel (PDCCH) only on a selected set of one or more special cells at the beginning of the DRX on-duration for an initial transmission in a scheduled transmission burst.

22. The network entity of claim 17, wherein the one or more processors are further configured to: Information is sent to the UE to configure the UE to monitor a physical downlink control channel (PDCCH) only on one or more carriers within a selected frequency range at the beginning of the DRX on-duration for an initial transmission in a scheduled transmission burst.

23. The network entity of claim 17, wherein the one or more processors are further configured to: sending a transmit burst to the UE during the DRX active time; and An early termination indication is received from the UE to terminate the DRX active time before expiration of a DRX inactivity timer.

24. The network entity of claim 23, wherein the early termination indication is included in a medium access control (MAC) control element (MAC-CE), uplink control information, or a buffer status report.

25. The network entity of claim 23, wherein the one or more processors are further configured to: Information is sent to the UE to terminate the DRX active time before the DRX inactivity timer expires based at least in part on the early termination indication.

26. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a dynamic indication of a start offset and length of a discontinuous reception (DRX) on-duration from a network entity; monitoring a physical downlink control channel (PDCCH) during the DRX On Duration for a message scheduling an initial transmission in a transmission burst, wherein the PDCCH is monitored in a reduced monitoring state at the beginning of the DRX On Duration; and Monitoring of the PDCCH is stopped after a final transmission in the transmission burst.

27. The method of claim 26, wherein the start offset of the DRX On-Duration is based at least in part on an expected start time of the transmit burst and a maximum jitter.

28. The method of claim 26, wherein the length of the DRX On-Duration is based at least in part on a maximum jitter of the transmit burst.

29. A method of wireless communication performed by a network entity, the method comprising: determining a start offset and a length of a discontinuous reception (DRX) on-duration based at least in part on one or more traffic arrival statistics; as well as A dynamic indication of the start offset and the length of the DRX On-Duration is sent to a user equipment (UE).

30. The method of claim 29, wherein the start offset of the DRX On Duration is based at least in part on an expected start time and a maximum jitter of a transmit burst, and wherein the length of the DRX On Duration is based at least in part on the maximum jitter of the transmit burst.

Images