Enhanced PDCCH skipping with dummy grants

Abstract

A method, and related apparatus, for wireless communication in a user equipment (UE) is provided. In the method, the UE receives downlink control information (DCI) indicating that the UE will skip physical downlink control channel (PDCCH) monitoring or extend a connection discontinuous reception (CDRX) active time. The DCI includes one or more of a skip indication, a scheduling for a retransmission of a successfully decoded physical downlink shared channel (PDSCH), a non-zero downlink assignment having a downlink retransmission transport block (TB) size different from an initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from an initial uplink transmission TB size. The UE further skips transmitting hybrid automatic repeat request (HARQ) feedback for the DCI.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS)

[0001] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 383,383, filed November 11, 2022, entitled "ENHANCEMENTS TO PDCCH SKIPPING WITH DUMMY GRANTS," and U.S. Non-Provisional Patent Application No. 18 / 457,776, filed August 29, 2023, entitled "ENHANCEMENTS TO PDCCH SKIPPING WITH DUMMY GRANTS," each of which is expressly incorporated by reference in its entirety into this specification.

[0002] FIELD OF THE DISCLOSURE

[0002] The present disclosure relates generally to communication systems, and more particularly to enhancing PDCCH skipping with dummy grants in wireless communications.

[0003] introduction

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide common protocols that enable different wireless devices to communicate at city, national, regional, or even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology, and these improvements may also be applicable to other multiple access technologies and the telecommunications standards that employ these technologies. Summary of the Invention

[0005]

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. It is not intended to identify key or critical elements of all aspects, nor is it intended to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006]

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication in a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to receive downlink control information (DCI) indicating that the UE is to skip physical downlink control channel (PDCCH) monitoring or extend a connection discontinuous reception (CDRX) active time. The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded physical downlink shared channel (PDSCH), a non-zero downlink assignment having a downlink retransmission transport block (TB) size different from an initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from an initial uplink transmission TB size. The at least one processor may be further configured to skip transmitting hybrid automatic repeat request (HARQ) feedback for the DCI.

[0007]

[0007] In aspects of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication in a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to output a DCI indicating that the UE skips PDCCH monitoring or extends the CDRX active time. The DCI may include one or more of a skip indication, scheduling for retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The at least one processor may be further configured to communicate with the UE based on the DCI.

[0008] To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of the various aspects may be employed. [Brief explanation of the drawings]

[0009] [Figure 1]

[0009] FIG. 1 illustrates an example of a wireless communication system and access network. [Figure 2]

[0010] FIG. 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0011] FIG. 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe, in accordance with various aspects of the present disclosure.

[0012] FIG. 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0013] FIG. 2D is a diagram illustrating an example of an uplink (UL) channel within a subframe, in accordance with various aspects of the present disclosure. [Figure 3]

[0014] FIG. 1 illustrates an example of a base station and user equipment (UE) in an access network. [Figure 4]

[0015] FIG. 4A is a diagram illustrating a discontinuous reception (DRX) cycle in wireless communication.

[0016] FIG. 4B is a diagram illustrating exemplary extended reality (XR) traffic, according to various aspects of the present disclosure. [Figure 5]

[0017] FIG. 10 is a diagram illustrating an example of PDCCH skipping. [Figure 6]

[0018] FIG. 10 is a diagram illustrating an example timing sequence for PDCCH skipping. [Figure 7]

[0019] FIG. 1 is a call flow diagram illustrating a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 8]

[0020] 1 is a first flowchart illustrating a method of wireless communication in a UE, in accordance with various aspects of the present disclosure. [Figure 9]

[0021] 1 is a first flowchart illustrating a method of wireless communication in a UE, in accordance with various aspects of the present disclosure. [Figure 10]

[0022] 1 is a first flowchart illustrating a method of wireless communication in a network entity, in accordance with various aspects of the present disclosure. [Figure 11]

[0023] 1 is a first flowchart illustrating a method of wireless communication in a network entity, in accordance with various aspects of the present disclosure. [Figure 12]

[0024] FIG. 1 illustrates an example of a hardware implementation for an exemplary device and / or network entity. [Figure 13]

[0025] FIG. 2 illustrates an example of a hardware implementation for an exemplary network entity. DETAILED DESCRIPTION OF THE INVENTION

[0010]

[0026] A UE may skip monitoring the PDCCH for power saving purposes. An instruction to skip PDCCH monitoring may be transmitted to the UE via a scheduling DCI. However, because the scheduling DCI is used to simultaneously schedule data, the scheduling DCI may have limited flexibility and transmission resources for instructing skipping of PDCCH monitoring. Aspects presented herein include methods and apparatuses for utilizing a dummy grant as a non-scheduling DCI to extend PDCCH skipping in wireless communications. As presented herein, in one aspect, a UE may receive a DCI indicating that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip instruction, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment with a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment with an uplink retransmission TB size different from the initial uplink transmission TB size. The UE may further skip transmitting HARQ feedback for the DCI.

[0011]

[0027] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: In some examples, by utilizing a dummy grant as a non-scheduling DCI for PDCCH monitoring adaptation, the method allows for more flexible indication with an additional information field for PDCCH monitoring compared to an indication mechanism based on a scheduling DCI, thereby improving the efficiency of wireless communications.

[0012]

[0028] The Detailed Description, set forth below in connection with the accompanying drawings, illustrates various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The Detailed Description includes specific details intended to provide a thorough understanding of the various concepts. However, these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0013]

[0029] Several aspects of telecommunications systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following Detailed Description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0014]

[0030] As an example, an element, or any portion of an element, or any combination of elements, can be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0015]

[0031] Thus, in one or more example aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0016]

[0032] Although aspects, implementations, and / or use cases are described herein by way of example for some embodiments, additional or different aspects, implementations, and / or use cases may occur in many different configurations and scenarios. The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, the aspects, implementations, and / or use cases may occur via integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communications devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some embodiments may or may not be specifically targeted to a use case or application, a wide variety of combined applicability of the described embodiments may arise. Aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and even to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily involves several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, summers / analog summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or non-aggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0017]

[0033] The deployment of a communication system, such as a 5G NR system, can be configured in multiple ways using various components or parts. In a 5G NR system or network, network equipment, such as a network node, network entity, network mobility element, Radio Access Network (RAN) node, core network node, network element, or base station (BS), or one or more units (or one or more components) performing base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmission reception point (TRP), or cell) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a disaggregated base station.

[0018]

[0034] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0019]

[0035] Base station operation or network design may take into account the aggregation characteristics of base station functions. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as the network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units in different physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station, or a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0020]

[0036] FIG. 1 is a diagram 100 illustrating an example of a wireless communication system and access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link or indirectly with the core network 120 through one or more disaggregated base station units (e.g., a near-real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both). The CUs 110 may communicate with one or more DUs 130 via respective midhaul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be served by multiple RUs 140 simultaneously.

[0021]

[0037] Each of the units, i.e., CU 110, DU 130, RU 140, and quasi-RT RIC 125, non-RT RIC 115, and SMO framework 105, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. In addition, a unit may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive and / or transmit signals to one or more of the other units over a wireless transmission medium.

[0022]

[0038] In some aspects, the CU 110 may host one or more upper 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 with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 110 may be implemented to communicate with the DU 130, as needed, for network control and signaling.

[0023]

[0039] The DU 130 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.), at least in part according to a functional division such as that defined by 3GPP. In some aspects, the DU 130 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0024]

[0040] The lower layer functions may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 may correspond to logical nodes hosting RF processing functions, lower PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, the RU(s) 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0025]

[0041] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-cloud) 190) via a cloud computing platform interface (e.g., an O2 interface) to perform network element lifecycle management (e.g., instantiate virtualized network elements). Such virtualized network elements may include, but are not limited to, the CU 110, the DU 130, the RU 140, and the quasi-RT RIC 125. In some implementations, the SMO framework 105 may communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 111, via the O1 interface. Additionally, in some implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0026]

[0042] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 125. The non-RT RIC 115 may be coupled to the quasi-RT RIC 125 or may communicate with the quasi-RT RIC 125 (e.g., via an A1 interface). The quasi-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action via an interface connecting one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the quasi-RT RIC 125 (e.g., via an E2 interface).

[0027]

[0043] In some implementations, the non-RT RIC 115 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 125. Such information may be utilized by the quasi-RT RIC 125 or may be received at the SMO framework 105 or non-RT RIC 115 from non-network data sources or from network functions. In some examples, the non-RT RIC 115 or quasi-RT RIC 125 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 115 may employ AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO framework 105 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0028]

[0044] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is shown with a dotted line to indicate that the component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network including both small cells and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to restricted groups known as closed subscriber groups (CSGs). The communication link between the RU 140 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from the RU 140 to the UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may use spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in a carrier aggregation of up to Yx MHz (x component carriers) in total, used for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (eg, more or fewer carriers may be allocated for DL ​​than for UL).The component carriers may include a primary component carrier, which may be referred to as a primary cell (PCell), and one or more secondary component carriers, which may be referred to as a secondary cell (SCell).

[0029]

[0045] Particular UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed over various wireless D2D communication systems, such as Bluetooth (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0030]

[0046] The wireless communication system may further include a Wi-Fi AP 150 that communicates with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication links 154, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the UEs 104 / APs 150 may perform clear channel assessment (CCA) before communicating to determine whether a channel is available.

[0031]

[0047] The electromagnetic spectrum is often divided into various classes, bands, channels, etc. based on frequency / wavelength. For 5G NR, two initial operating bands have been identified by the frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although portions of FR1 are above 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the “millimeter wave” band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is identified by the International Telecommunications Union (ITU) as the “millimeter wave” band.

[0032]

[0048] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as the frequency range designated FR3 (7.125 GHz to 24.25 GHz). Frequency bands included within FR3 may inherit FR1 and / or FR2 characteristics, thus effectively extending the characteristics of FR1 and / or FR2 to the mid-band frequencies. Higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency ranges designated FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is included within the EHF band.

[0033]

[0049] With the above aspects in mind, unless otherwise specified, as used herein, terms such as "sub-6 GHz" may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless otherwise specified, as used herein, terms such as "millimeter wave" may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0034]

[0050] The base station 102 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 / UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0035]

[0051] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 may be implemented as an aggregated (monolithic) base station having an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A set of base stations, which may include disaggregated base stations and / or aggregated base stations, may be referred to as a next generation (NG) RAN (NG-RAN).

[0036]

[0052] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports authentication and key agreement (AKA) credential generation, user identity handling, access authorization, and subscription management. The one or more location servers 168 are shown as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information.The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the position of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the position of the UE 104. Positioning the UE 104 may include signal measurements, position estimation, and optional velocity calculations based on these measurements. The signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The signals measured may include a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), a global position system (GPS), a non-terrestrial network (NTN), or other satellite position / location system), an LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), or a LTE signal (e.g., a LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS)), sensor-based information (e.g., barometric pressure sensor, motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), or a LTE signal (e.g., a LTE signal ... The signal may be based on one or more of UL Time Domain Observation (TDOA), UL Angle-of-Arrival (UL-AoA) positioning, and / or other systems / signals / sensors.

[0037]

[0053] Examples of UEs 104 include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small cooking appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). The UEs 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation configuration, where one or more of these devices may collectively access the network and / or may individually access the network.

[0038]

[0054] Referring again to FIG. 1 , in certain aspects, the UE 104 may include a DCI receiving component 198. The DCI receiving component 198 may be configured to receive a DCI indicating that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The DCI receiving component 198 may be further configured to skip transmitting HARQ feedback for the DCI. In certain aspects, the base station 102 may include a DCI indication component 199. The DCI indication component 199 may be configured to output a DCI indicating that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip indication, a scheduling for retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The DCI indication component 199 may be further configured to communicate with the UE based on the DCI. While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0039]

[0055] Figure 2A is a diagram 200 illustrating an example of a first subframe in a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of a DL channel in a 5G NR subframe. Figure 2C is a diagram 250 illustrating an example of a second subframe in a 5G NR frame structure. Figure 2D is a diagram 280 illustrating an example of a UL channel in a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) where, for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL, or time division duplexed (TDD) where, for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. In the examples provided by FIGS. 2A and 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 configured (mostly DL) using slot format 28, where D is DL, U is UL, and F is flexible for DL / UL use, and subframe 3 configured using slot format 1 (all UL). While subframes 3 and 4 are shown using slot formats 1 and 28, respectively, any particular subframe may be configured using any of the various available slot formats 0 through 61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2 through 61 contain a mix of DL symbols, UL symbols, and flexible symbols. The UE is configured with the slot format through a received slot format indicator (SFI) (either dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). Please note that the following description also applies to the 5G NR frame structure, which is TDD.

[0040]

[0056] 2A-2D illustrate one frame structure, and embodiments of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the cyclic prefix (CP) is normal or extended. With a normal CP, each slot may include 14 symbols, and with an extended CP, each slot may include 12 symbols. Symbols on the DL may be CP orthogonal frequency division multiplexing (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread OFDM (DFT-s-OFDM) symbols (for power-limited scenarios, when limited to single-stream transmission). The number of slots in a subframe is based on CP and numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0041] [Table 1]

[0042]

[0057] For normal CP (14 symbols / slot), different number logics μ0-μ4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, number logic 2 allows 4 slots per subframe. Therefore, for normal CP and number logic μ, 14 symbols / slot and 2 μThere are slots / subframes. The subcarrier spacing is 2 μ * μ may be equal to 15 kHz, where μ is a numerology from 0 to 4. Therefore, the numerology μ=0 has a subcarrier spacing of 15 kHz, and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2D provide an example of a normal CP with 14 symbols per slot and a numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see Figure 2B), which are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

[0043]

[0058] A resource grid can be used to represent the frame structure. Each time slot contains resource blocks (RBs) (also called physical RBs (PRBs)), which span 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0044]

[0059] As shown in Figure 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RSs may include demodulation RSs (DM-RSs) (shown as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0045]

[0060] Figure 2B shows an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), where each CCE includes 6 RE groups (REGs), and each REG includes 12 consecutive REs within an OFDM symbol of an RB. The PDCCHs within one BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring occasion on the CORESET, a UE is configured to monitor PDCCH candidates within a PDCCH search space (e.g., a common search space, a UE-specific search space), where the PDCCH candidates have different DCI formats and aggregation levels. Additional BWPs may be deployed at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the subframe / symbol timing and the physical layer identity. A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the timing of the radio frame. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS.The physical broadcast channel (PBCH), which carries the master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0046]

[0061] As shown in FIG. 2C , some of the REs carry DM-RS (denoted as R for one particular configuration, although other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and on the specific PUCCH format used. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have comb configurations, and the UE may transmit the SRS in one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0047]

[0062] 2D shows an example of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be arranged as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and, in addition, may be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCIs.

[0048]

[0063] 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes a Radio Resource Control (RRC) layer, and Layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The controller / processor 375 is responsible for RRC layer functions associated with broadcasting system information (e.g., MIBs, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding higher layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and mapping of logical channels to transport channels, multiplexing MAC SDUs onto transport blocks (TBs), and MAC SDUs from TBs. It provides MAC layer functions associated with demultiplexing of SDUs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0049]

[0064] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 processes mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. This OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate a radio frequency (RF) carrier with the respective spatial stream for transmission.

[0050]

[0065] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by a channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel, which are then provided to a controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0051]

[0066] The controller / processor 359 may be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 is responsible for demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0052]

[0067] Similar to the functionality described in connection with DL transmission by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with forwarding upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping of logical channels to transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0053]

[0068] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

[0054]

[0069] UL transmissions are processed at the base station 310 in a manner similar to that described for the receiver functions at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0055]

[0070] The controller / processor 375 may be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 is responsible for demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0056]

[0071] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects associated with the DCI receiving component 198 of FIG.

[0057]

[0072] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects associated with the DCI indication component 199 of FIG.

[0058]

[0073] In the RRC idle and inactive states, radio resource management (RRM) and paging procedures in the UE can consume a significant amount of UE power. In the DRX mode, for power saving purposes, the UE may discontinuously monitor the PDCCH channel using a sleep and wake cycle, e.g., a DRX OFF duration and a DRX ON duration. When the UE is in the RRC connected state, DRX may also be referred to as connected DRX (CDRX). When the UE is in the RRC idle state, DRX may be referred to as IDRX. In the non-DRX mode, the UE monitors the PDCCH in each subframe to check whether there is downlink data available. Continuous monitoring of the PDCCH uses more battery power in the UE, and DRX saves battery power in the UE.

[0059]

[0074] 4A illustrates an example of a DRX cycle 400 that includes periodic ON durations during which the UE monitors the PDCCH and OFF durations during which the UE may not monitor the PDCCH. The OFF durations may be referred to in some aspects as DRX opportunities. During the OFF durations, the UE does not monitor the PDCCH. The UE may enter a sleep mode or low power mode in which the UE minimizes power consumption by shutting down RF functions without detecting communication from a base station.

[0060]

[0075] The UE may receive a DRX configuration from the network in RRC signaling from the base station, such as an RRC connection setup request or an RRC connection reconfiguration request. The DRX configuration may include configuration of one or more timers and values. In some examples, the DRX configuration may include, among others, any of an ON duration timer, a DRX inactivity timer, a DRX retransmission timer, a DRX UL retransmission timer, a long DRX cycle, a value of the DRX start offset, a DRX short cycle timer, and / or a short DRX cycle. The ON duration timer may correspond to the number of consecutive PDCCH subframes to be monitored or decoded when the UE wakes up from an OFF duration in a DRX cycle. The DRX retransmission timer may correspond to the number of consecutive PDCCH subframes for the UE to monitor when a retransmission is expected by the UE. The DRX inactivity timer may correspond to the amount of time before the UE can again enter an OFF duration after successfully decoding a PDCCH. The amount of time may be in relation to a transmission time interval (TTI) duration. After the UE successfully receives downlink data, the DRX inactivity timer may start counting the number of subframes. If any uplink or downlink data transmission occurs while the DRX inactivity timer is running, the timer restarts. If the DRX inactivity timer expires without uplink or downlink activity, the UE may enter a DRX cycle to achieve power savings.

[0061]

[0076] Wireless communications may include various types of communications. Among other examples, wireless communications may include XR traffic. FIG. 4B is a diagram 450 illustrating exemplary XR traffic. XR traffic may refer to wireless communications for technologies such as virtual reality (VR), mixed reality (MR), and / or augmented reality (AR). VR may refer to technologies in which a user is immersed in a simulated experience similar to or different from the real world. A user may interact with a VR system through a VR headset or a multi-projection environment that generates realistic images, sounds, and other sensations that simulate the user's physical presence in the virtual environment. MR may refer to technologies in which aspects of virtual and real environments are blended. AR may refer to technologies in which objects present in the real world are augmented through computer-generated perceptual information, sometimes across multiple sensory modalities such as vision, hearing, touch, somatosensation, and / or smell. AR systems may incorporate a combination of real and virtual worlds, real-time interaction, and precise three-dimensional registration of virtual and real objects. In one example, the AR system may overlay sensory information (e.g., images) on a natural environment and / or mask real-world objects from the natural environment. XR traffic may include video data and / or audio data. XR traffic may be transmitted by a base station and received by a UE, or XR traffic may be transmitted by a UE and received by a base station.

[0062]

[0077] XR traffic may arrive in periodic traffic bursts (“XR traffic bursts”). The XR traffic bursts may vary in the number of packets per burst and / or the size of each packet within the burst. Diagram 450 illustrates a first XR flow 402, including a first XR traffic burst 404 and a second XR traffic burst 406. As illustrated in diagram 450, the traffic bursts may include different numbers of packets; for example, the first XR traffic burst 404 is shown with three packets (represented as a rectangle in diagram 450) and the second XR traffic burst 406 is shown with two packets. Furthermore, as illustrated in diagram 450, the three packets in the first XR traffic burst 404 and the two packets in the second XR traffic burst 406 may vary in size. That is, the packets in the first XR traffic burst 404 and the second XR traffic burst 406 may include different amounts of data.

[0063]

[0078] XR traffic bursts may arrive at non-integer periods (i.e., at non-integer cycles). The periods may differ from integers of symbols, slots, etc. In one example, for 60 frames per second (FPS) video data, XR traffic bursts may arrive at 1 / 60=16.67 ms periods. In another example, for 120 FPS video data, XR traffic bursts may arrive at 1 / 120=8.33 ms periods.

[0064]

[0079] Arrival times for XR traffic may vary. For example, an XR traffic burst may arrive and be available for transmission earlier or later than the UE (or base station) expects the XR traffic burst. The variability in packet arrival relative to a period (e.g., a 16.76 ms period, an 8.33 ms period, etc.) may be referred to as "jitter." In one example, the jitter for XR traffic may range from -4 ms (earlier than expected arrival) to +4 ms (later than expected arrival). For example, referring to the first XR flow 402, the UE may expect the first packet of the first XR traffic burst 404 to arrive at time t0, but the first packet of the first XR traffic burst 404 arrives at time t1.

[0065]

[0080] XR traffic may include multiple flows that arrive at the UE (or base station) at the same time (or within a threshold period) of each other. For example, diagram 450 includes a second XR flow 408. The second XR flow 408 may have different characteristics than the first XR flow 402. For example, the second XR flow 408 may have XR traffic bursts with a different number of packets, different size packets, etc. In one example, the first XR flow 402 may include video data, and the second XR flow 408 may include audio data for the video data. In another example, the first XR flow 402 may include intra-coded picture frames (I-frames) that include complete images, and the second XR flow 408 may include predicted picture frames (P-frames) that include changes from the previous image.

[0066]

[0081] XR traffic may have an associated packet delay budget (PDB). If a packet does not arrive within the PDB, the UE (or base station) may discard the packet. In one example, if a packet corresponding to a video frame of a video does not arrive at the UE within the PDB, the UE may discard the packet when the video progresses beyond the frame.

[0067]

[0082] In general, XR traffic may be characterized by relatively high data rates and low latency. Latency in XR traffic may affect user experience. For example, XR traffic may have applications in eMBB and URLLC services.

[0068]

[0083] Some types of wireless communication systems may employ dynamic grants for scheduling purposes to adapt to traffic (e.g., XR traffic). In dynamic grants, a scheduler may use control signaling to allocate resources (e.g., grants of UL or DL ​​resources) for transmission or reception at a UE. Dynamic grants may be flexible and adapt to variations in traffic behavior. A UE may monitor a PDCCH, which includes DCI (e.g., instructions to receive data via a PDSCH) that schedules the UE to transmit or receive communications with a base station. However, monitoring the PDCCH consumes power at the UE and may increase latency in communications between the UE and the base station as the UE waits for resource allocations to transmit or receive communications.

[0069]

[0084] For example, various aspects may be employed to provide power savings and / or capacity improvements for wireless communications including XR traffic. In some configurations, the UE may skip PDCCH monitoring for a period of time. Skipping PDCCH monitoring is a feature that helps conserve power in the UE by allowing the UE to skip monitoring the PDCCH during times when the network does not plan to send control signaling to the UE. FIG. 5 is a diagram 500 illustrating an example of PDCCH skipping. As shown in FIG. 5, the UE may operate in a high-throughput state 510 (e.g., search space set group (SSSG) #0) in which the UE may monitor the PDCCH per DRX state (e.g., per CDRX state). When the UE receives a DCI (e.g., a scheduling DCI) indicating to skip PDCCH monitoring, the UE may enter a low-power state 520 (e.g., SSSG #2) in which the UE may skip PDCCH monitoring. The specific DCI may be typically transmitted with the last grant of a data burst and may include a field indicating to the UE that PDCCH monitoring may be skipped for a period of time. The time may be a configured time (which may be referred to as a preconfigured time, for example). PDCCH skipping may allow the UE to go to sleep before the expiration of the CDRX inactivity timer, thereby reducing UE power consumption. The UE may skip PDCCH monitoring until the time period expires or until a condition is met.

[0070]

[0085] 6 is a diagram 600 illustrating an example timing sequence of PDCCH skipping. Referring to FIG. 6, a UE may receive a specific DCI 602 (e.g., a scheduling DCI) that instructs the UE to start skipping PDCCH monitoring. Based on the specific DCI 602, the UE may start skipping PDCCH monitoring (e.g., at t0) before the expiration of a CDRX inactivity timer (e.g., at t1), and PDCCH monitoring may be skipped until a preconfigured timer expires or a condition is met. When the UE is configured for CDRX, the condition may be that the DRX state has left an "active" state or active time.

[0071]

[0086] In a PDCCH skip mechanism based on scheduling DCI, the DL grant used to instruct the UE to skip PDCCH monitoring (i.e., send the UE to a lower power state) is also used to simultaneously schedule data. Therefore, the scheduling DCI has limited flexibility and transmission resources (e.g., information fields within the DCI) to instruct the UE to skip PDCCH monitoring.

[0072]

[0087] The present disclosure provides a method and apparatus for utilizing a dummy grant as a non-scheduling DCI for a PDCCH monitoring adaptation indication. Compared with a PDCCH monitoring adaptation indication based on a scheduling DCI, a non-scheduling DCI can be transmitted more flexibly for a UE to stop further monitoring of the PDCCH whenever necessary. More importantly, a non-scheduling DCI may provide additional field bits originally used for scheduling to indicate a PDCCH skip duration from a larger set of values ​​(e.g., more than three). This may be useful when the CDRX configuration for a UE is not configured for multiple coexisting traffic flows that do not have a common periodicity. Various combinations or uses of fields in a DCI format for scheduling resources may be used to indicate PDCCH skipping to a UE, where the DCI does not actually schedule resources.

[0073]

[0088] By using a dummy grant as a non-scheduling DCI, effects similar to a non-scheduling DCI-based PDCCH skip indication and / or a non-scheduling DCI-based CDRX active time extension may be achieved. For example, referring to FIG. 6, a non-scheduling DCI 612 may be used as an indication for PDCCH skipping. That is, instead of using a scheduling DCI 602 to indicate PDCCH skipping, the non-scheduling DCI 612 may be used to indicate to the UE to skip PDCCH monitoring or extend the CDRX active time (e.g., starting from t0). The non-scheduling DCI 612 may be transmitted to the UE at any time, and the non-scheduling DCI 612 does not schedule data. Upon receiving the non-scheduling DCI 612, the UE may skip transmitting HARQ feedback for the non-scheduling DCI 612. A dummy grant may be used as the non-scheduling DCI 612. The non-scheduling DCI-based mechanism and the dummy grant may be used for XR-specific power savings for more flexible adaptation of the UE CDRX active time to account for random jitter and variable XR video frame sizes.

[0074]

[0089] In some aspects, a non-scheduling DCI may indicate PDCCH skipping or CDRX active time extension, and one or more dummy grants may be used as the non-scheduling DCI. The dummy grant may be used to indicate PDCCH skipping or CDRX active time extension and is not used to schedule any PDSCH. When a dummy grant is used to indicate PDCCH skipping or CDRX active time extension, the UE may not be required to transmit HARQ feedback. The dummy grant may include a new data indicator (NDI) field. In some aspects, the NDI field may not be toggled, the PDCCH monitoring adaptation field of the dummy grant may indicate PDCCH skipping, and the UE may immediately skip PDCCH monitoring. In some other aspects, the NDI field of the dummy grant may be toggled, the PDCCH monitoring adaptation field of the dummy grant may not indicate PDCCH skipping, and the UE may restart the CDRX inactivity timer.

[0075]

[0090] The dummy grant may be implemented in various manners. In some examples, the dummy grant may be a grant with a skip indication. The skip indication may, in some examples, be an invalid RB allocation. That is, the dummy grant may be an indication that will not be interpreted by the UE as a valid RB allocation. For example, the dummy grant may be an all-zeros bitmap for a Type 0 resource allocation or an all-ones bitmap for a Type 1 resource allocation. In this disclosure, a "Type 0" resource allocation may refer to a predefined resource allocation scheme in which an all-zeros bitmap is not a valid RB allocation, and a "Type 1" resource allocation may refer to another predefined resource allocation scheme in which an all-ones bitmap is not a valid RB allocation. In some examples, the skip indication may have a first number of adaptation bits in the DCI that is different from a second number of associated PDCCH skip durations. In some examples, the skip indication may include a single adaptation bit in the DCI for multiple (e.g., two) PDCCH skip durations (which may be defined by the parameter PDCCHSkippingDuration). In some examples, the skip indication may include multiple (eg, two) adaptation bits within the DCI over a single PDCCH skip duration (eg, defined by the parameter PDCCHSkippingDuraiton).

[0076]

[0091] In some examples, the dummy grant may be a retransmission of a successfully decoded PDSCH. When the UE receives such a retransmission, the UE may interpret the retransmission as a dummy grant because the PDSCH has been successfully decoded, and the UE may use the dummy grant for a PDCCH skip indication or a CDRX active time extension. In some examples, the base station may transmit a non-zero DL assignment with a DL retransmission TB size different from the initial DL transmission TB size, and the UE may interpret such a DL assignment as a dummy grant. In some examples, the base station may transmit a non-zero UL assignment with a UL retransmission TB size different from the initial UL transmission TB size, and the UE may interpret such an UL assignment as a dummy grant.

[0077]

[0092] 7 is a call flow diagram 700 illustrating a method of wireless communication in accordance with various aspects of the present disclosure. In some aspects, the wireless communication may include XR traffic, such as described in connection with FIG. 4B. Although aspects are described with respect to a base station 704, aspects may be performed by an aggregating base station and / or by one or more components of the base station 704 (e.g., the CU 110, the DU 130, and / or the RU 140, etc.).

[0078]

[0093] 7, the UE 702 may receive 706 a DCI indicating that the UE 702 will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment with a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment with an uplink retransmission TB size different from the initial uplink transmission TB size. In some examples, the DCI may be a non-scheduling DCI. For example, the DCI may be a non-scheduling DCI 612.

[0079]

[0094] The UE 702 may skip transmitting HARQ feedback for the DCI at 708. For example, referring to FIG. 6, when the UE receives a non-scheduling DCI 612, the UE may skip transmitting HARQ feedback for the non-scheduling DCI 612.

[0080]

[0095] The UE 702 may skip PDCCH monitoring in response to the DCI at 710. For example, with reference to FIG. 6, after the UE receives the non-scheduling DCI 612, the UE may skip PDCCH monitoring in response to the non-scheduling DCI 612 (e.g., at t0).

[0081]

[0096] At 712, the UE 702 may restart a DRX inactivity timer (e.g., a CDRX inactivity timer, etc.) in response to the DCI. For example, with reference to FIG. 6, in some aspects, after the UE receives a non-scheduling DCI 612, the UE may restart a CDRX inactivity timer in response to the non-scheduling DCI 612.

[0082]

[0097] At 714, the base station 704 may skip transmitting a PDCCH to the UE 702 based on the DCI. For example, with reference to FIG. 6, after the base station transmits a non-scheduling DCI 612 to the UE, the base station may skip transmitting a PDCCH to the UE based on the non-scheduling DCI 612.

[0083]

[0098] At 716, the base station 704 may communicate with the UE based on the CDRX inactivity timer restarted for the UE 702 after the DCI. For example, with reference to FIG. 6, after the UE receives the non-scheduling DCI 612, the UE may restart the CDRX inactivity timer in response to the non-scheduling DCI 612, and the base station and UE may communicate based on the restarted CDRX inactivity timer.

[0084]

[0099] The base station 704 may skip receiving HARQ feedback for the DCI at 718. For example, with reference to FIG. 6, after the base station transmits the non-scheduling DCI 612 to the UE, the base station may skip receiving HARQ feedback for the non-scheduling DCI 612.

[0085]

[0100] At 720, the base station 704 may communicate data and / or control with the UE 702 based on the DCI. For example, with reference to FIG. 6, after the base station transmits the non-scheduling DCI 612 to the UE, the base station may communicate with the UE based on the non-scheduling DCI 612.

[0086]

[0101] FIG. 8 is a flowchart 800 illustrating a method of wireless communication in a UE in accordance with various aspects of the present disclosure. In some aspects, the wireless communication may include XR traffic, as described in connection with FIG. 4B . The method may be performed by the UE. The UE may be the UE 104, 350, 702, or the device 1204 in the hardware implementation of FIG. 12. By utilizing a dummy grant as a non-scheduling DCI for PDCCH monitoring adaptation, the method enables a more flexible indication with an additional information field for PDCCH monitoring compared to an indication mechanism based on a scheduling DCI, thereby improving the efficiency of wireless communication.

[0087]

[0102] As shown in FIG. 8, at 802, a UE may receive from a network entity a DCI indicating that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The network entity may be a base station or a component of a base station in the access network of FIG. 1, or a core network component (e.g., base station 102, 310, base station 704, or network entity 1202 in the hardware implementation of FIG. 12). FIGS. 6 and 7 illustrate various aspects of steps associated with flowchart 800. For example, referring to FIGS. 6 and 7, a UE 702 may receive a DCI 612 from a network entity (base station 704) at 706. The DCI 612 may indicate to the UE 702 to skip PDCCH monitoring or extend the CDRX active time. The DCI 612 may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment with a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment with an uplink retransmission TB size different from the initial uplink transmission TB size. In some aspects, 802 may be performed by the DCI receiving component 198.

[0088]

[0103] The UE may skip transmitting HARQ feedback for the DCI at 804. For example, referring to FIG. 7, the UE 702 may skip transmitting HARQ feedback for the DCI at 708. Referring to FIG. 6, after the UE receives the DCI 612, the UE may skip transmitting HARQ feedback (AA) for the DCI 612. In some aspects, 804 may be performed by the DCI receiving component 198.

[0089]

[0104] FIG. 9 is a flowchart 900 illustrating a method of wireless communication in a UE in accordance with various aspects of the present disclosure. In some aspects, the wireless communication may include XR traffic, as described in connection with FIG. 4B . The method may be performed by the UE. The UE may be the UE 104, 350, 702, or the device 1204 in the hardware implementation of FIG. 12. By utilizing a dummy grant as a non-scheduling DCI for PDCCH monitoring adaptation, the method enables a more flexible indication with an additional information field for PDCCH monitoring compared to an indication mechanism based on a scheduling DCI, thereby improving the efficiency of wireless communication.

[0090]

[0105] As shown in FIG. 9, at 902, a UE may receive from a network entity a DCI indicating that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The network entity may be a base station or a component of a base station in the access network of FIG. 1, or a core network component (e.g., base station 102, 310, base station 704, or network entity 1202 in the hardware implementation of FIG. 12). FIGS. 6 and 7 illustrate various aspects of steps associated with flowchart 900. For example, referring to FIGS. 6 and 7, a UE 702 may receive a DCI 612 from a network entity (base station 704) at 706. The DCI 612 may indicate to the UE 702 to skip PDCCH monitoring or extend the CDRX active time. The DCI 612 may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment with a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment with an uplink retransmission TB size different from the initial uplink transmission TB size. In some aspects, 902 may be performed by the DCI receiving component 198.

[0091]

[0106] The UE may skip transmitting HARQ feedback for the DCI at 904. For example, referring to FIG. 7, the UE 702 may skip transmitting HARQ feedback for the DCI at 708. Referring to FIG. 6, after the UE receives the DCI 612, the UE may skip transmitting HARQ feedback (AA) for the DCI 612. In some aspects, 904 may be performed by the DCI receiving component 198.

[0092]

[0107] In some aspects, the DCI may include scheduling for retransmissions of successfully decoded PDSCHs. For example, referring to FIG. 6, DCI 612 may include scheduling for retransmissions of successfully decoded PDSCHs.

[0093]

[0108] In some aspects, at 910, the DCI may include a skip indication. The skip indication may include one or more of a first bitmap of all zeros for a Type 0 resource allocation or a second bitmap of all ones for a Type 1 resource allocation. For example, with reference to FIG. 6, the DCI 612 may include a skip indication. The skip indication may include one or more of a first bitmap of all zeros for a Type 0 resource allocation or a second bitmap of all ones for a Type 1 resource allocation.

[0094]

[0109] In some aspects, at 912, the DCI may include a skip indication. The skip indication may have a first number of adaptation bits within the DCI that is different from a second number of associated PDCCH skip durations. For example, with reference to FIG. 6, the DCI 612 may include a skip indication. The skip indication may have a first number of adaptation bits within the DCI 612 that is different from a second number of associated PDCCH skip durations.

[0095]

[0110] In some aspects, the skip duration may include a single adaptation bit within the DCI across multiple PDCCH skip durations. For example, with reference to FIG. 6, the DCI 612 may include a skip indication. The skip indication may include a single adaptation bit within the DCI 612 across multiple (e.g., two) PDCCH skip durations.

[0096]

[0111] In some aspects, the skip duration may include multiple adaptation bits within the DCI over a single PDCCH skip duration. For example, with reference to FIG. 6, the DCI 612 may include a skip indication. The skip duration may include multiple (e.g., two) adaptation bits within the DCI 612 over a single PDCCH skip duration.

[0097]

[0112] In some aspects, the DCI may include a non-zero downlink assignment having a downlink retransmission TB size that is different from the initial downlink transmission TB size. For example, referring to FIG. 6, the DCI 612 may include a non-zero downlink assignment having a downlink retransmission TB size that is different from the initial downlink transmission TB size.

[0098]

[0113] In some aspects, the DCI may include a non-zero uplink assignment having an uplink retransmission TB size that is different from the initial uplink transmission TB size. For example, referring to FIG. 6, the DCI 612 may include a non-zero uplink assignment having an uplink retransmission TB size that is different from the initial uplink transmission TB size.

[0099]

[0114] In some aspects, an entry in the NDI within the DCI may indicate that a PDCCH monitoring adaptation field of the DCI indicates that the UE is to skip PDCCH monitoring for a period of time, and the UE may be further configured to skip PDCCH monitoring in response to the DCI at 906. For example, with reference to FIG. 6, an entry in the NDI within the DCI 612 may indicate that a PDCCH monitoring adaptation field of the DCI indicates that the UE is to skip PDCCH monitoring for a period of time (e.g., from t0 to t2), and the UE may be further configured to skip PDCCH monitoring in response to the DCI 612. With reference to FIG. 7, after the UE 702 receives the DCI at 706, the UE 702 may skip PDCCH monitoring in response to the DCI at 710. In some aspects, 906 may be performed by the DCI receiving component 198.

[0100]

[0115] In some aspects, an entry in the NDI within the DCI may indicate that a PDCCH monitoring adaptation field of the DCI does not include PDCCH skip information, and the UE may be further configured to restart a CDRX inactivity timer in response to the DCI at 908. For example, with reference to FIG. 6, an entry in the NDI within the DCI 612 may indicate that a PDCCH monitoring adaptation field of the DCI 612 does not include PDCCH skip information, and the UE may be further configured to restart a CDRX inactivity timer in response to the DCI 612. With reference to FIG. 7, after the UE 702 receives a DCI at 706, the UE 702 may restart a CDRX inactivity timer in response to the DCI at 712. In some aspects, 908 may be performed by the DCI receiving component 198.

[0101]

[0116] FIG. 10 is a flowchart 1000 illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure. The method may be performed by the network entity. In some aspects, the wireless communication may include XR traffic, as described in connection with FIG. 4B . The network entity may be a base station or a component of a base station in the access network of FIG. 1 , or a core network component (e.g., base station 102, 310, 704, or network entity 1202 in the hardware implementation of FIG. 12 ). By utilizing a dummy grant as a non-scheduling DCI for PDCCH monitoring adaptation, the method enables a more flexible indication with an additional information field for PDCCH monitoring compared to an indication mechanism based on a scheduling DCI, thereby improving the efficiency of wireless communication.

[0102]

[0117] As shown in FIG. 10 , at 1002, a network entity may output a DCI to a UE indicating that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The UE may be the UE 104, 350, 702, or the device 1204 in the hardware implementation of FIG. 12 . FIGS. 6 and 7 illustrate various aspects of steps associated with flowchart 1000. For example, referring to FIGS. 6 and 7 , a network entity (base station 704) may output a DCI 612 to the UE 702 at 706. The DCI 612 may indicate to the UE that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI 612 may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. In some aspects, 1002 may be performed by the DCI indication component 199.

[0103]

[0118] At 1004, a network entity may communicate with the UE based on the DCI. For example, with reference to Figures 6 and 7, a network entity (base station 704) may communicate with the UE 702 based on the DCI 612 at 720. In some aspects, 1004 may be performed by the DCI indication component 199.

[0104]

[0119] FIG. 11 is a flowchart 1100 illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure. The method may be performed by the network entity. In some aspects, the wireless communication may include XR traffic, as described in connection with FIG. 4B . The network entity may be a base station or a component of a base station in the access network of FIG. 1 , or a core network component (e.g., base station 102, 310, 704, or network entity 1202 in the hardware implementation of FIG. 12 ). By utilizing a dummy grant as a non-scheduling DCI for PDCCH monitoring adaptation, the method enables a more flexible indication with an additional information field for PDCCH monitoring compared to an indication mechanism based on a scheduling DCI, thereby improving the efficiency of wireless communication.

[0105]

[0120] As shown in FIG. 11 , at 1102, a network entity may output a DCI to a UE indicating that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The UE may be the UE 104, 350, 702, or the device 1204 in the hardware implementation of FIG. 12. FIGS. 6 and 7 illustrate various aspects of steps associated with flowchart 1000. For example, referring to FIGS. 6 and 7 , a network entity (base station 704) may output a DCI 612 to the UE 702 at 706. The DCI 612 may indicate to the UE that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI 612 may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. In some aspects, 1102 may be performed by the DCI indication component 199.

[0106]

[0121] At 1104, a network entity may communicate with the UE based on the DCI. For example, with reference to Figures 6 and 7, a network entity (base station 704) may communicate 720 with the UE 702 based on the DCI 612. In some aspects, 1104 may be performed by a DCI indication component 199.

[0107]

[0122] In some aspects, the DCI may include scheduling for retransmissions of successfully decoded PDSCHs. For example, referring to FIG. 6, DCI 612 may include scheduling for retransmissions of successfully decoded PDSCHs.

[0108]

[0123] In some aspects, at 1108, the DCI may include a skip indication, which may include one or more of a first bitmap of all zeros for a Type 0 resource allocation or a second bitmap of all ones for a Type 1 resource allocation. For example, with reference to FIG. 6, the DCI 612 may include a skip indication. The skip indication may include one or more of a first bitmap of all zeros for a Type 0 resource allocation or a second bitmap of all ones for a Type 1 resource allocation.

[0109]

[0124] In some aspects, at 1110, the DCI may include a skip indication, the skip indication may have a first number of adaptation bits, and the first number may be different from a second number of associated PDCCH skip durations.

[0110]

[0125] In some aspects, the skip indication may include a single adaptation bit within the DCI for multiple PDCCH skip durations. For example, with reference to FIG. 6, the DCI 612 may include the skip indication. The skip indication may include a single adaptation bit within the DCI 612 for multiple PDCCH skip durations.

[0111]

[0126] In some aspects, the skip indication may include multiple adaptation bits within the DCI over a single PDCCH skip duration. For example, with reference to FIG. 6, the DCI 612 may include the skip indication. The skip indication may include multiple adaptation bits within the DCI 612 over a single PDCCH skip duration.

[0112]

[0127] In some aspects, the DCI may include a non-zero downlink assignment having a downlink retransmission TB size that is different from the initial downlink transmission TB size. For example, referring to FIG. 6, the DCI 612 may include a non-zero downlink assignment having a downlink retransmission TB size that is different from the initial downlink transmission TB size.

[0113]

[0128] In some aspects, the DCI may include a non-zero uplink assignment having an uplink retransmission TB size that is different from the initial uplink transmission TB size. For example, referring to FIG. 6, the DCI 612 may include a non-zero uplink assignment having an uplink retransmission TB size that is different from the initial uplink transmission TB size.

[0114]

[0129] In some aspects, an entry in the NDI within the DCI may indicate that a PDCCH monitoring adaptation field of the DCI indicates that the UE is to skip PDCCH monitoring for a period of time, and the network entity may be further configured to skip transmitting a PDCCH to the UE based on the DCI, at 1106. For example, with reference to FIG. 6, an entry in the NDI within the DCI 612 may indicate that a PDCCH monitoring adaptation field of the DCI 612 indicates that the UE is to skip PDCCH monitoring for a period of time (e.g., from t0 to t2), and the network entity may be further configured to skip transmitting a PDCCH to the UE based on the DCI 612. With reference to FIG. 7, after the network entity (base station 704) transmits the DCI to the UE 702, at 706, the network entity (base station 704) may skip transmitting a PDCCH to the UE 702 based on the DCI, at 714. In some aspects, 1106 may be performed by the DCI indication component 199.

[0115]

[0130] In some aspects, an entry in the NDI within the DCI may indicate that the PDCCH monitoring adaptation field of the DCI does not include PDCCH skip information, and to communicate with the UE, the network entity may be configured to communicate based on a CDRX inactivity timer that was restarted for the UE after the DCI. For example, with reference to FIG. 6, an entry in the NDI within DCI 612 may indicate that the PDCCH monitoring adaptation field of the DCI does not include PDCCH skip information, and the network entity may be configured to communicate based on a CDRX inactivity timer that was restarted for the UE after the DCI.

[0116]

[0131] In some aspects, to communicate with a UE, a network entity may be configured to skip receiving HARQ feedback for DCI. For example, referring to FIG. 6, to communicate with a UE, a network entity may be configured to skip receiving HARQ feedback (AA) for DCI 612. Referring to FIG. 7, to communicate with a UE 702, a network entity (base station 704) may skip receiving HARQ feedback for DCI at 718.

[0117]

[0132] FIG. 12 is a diagram 1200 illustrating an example of a hardware implementation for an apparatus 1204. The apparatus 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1204 may include at least one cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., cellular RF transceivers). The cellular baseband processor(s) 1224 may include at least one on-chip memory 1224′. In some aspects, the apparatus 1204 may further include one or more subscriber identity module (SIM) cards 1220 and at least one application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor(s) 1206 may include on-chip memory 1206′. In some aspects, the device 1204 may further include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (e.g., a barometric pressure sensor / altimeter, an inertial measurement unit (IMU), a motion sensor such as a gyroscope and / or accelerometer(s), light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies used for positioning), an additional memory module 1226, a power source 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include an on-chip transceiver (TRX) (or in some cases simply a receiver (RX)).The Bluetooth module 1212, WLAN module 1214, and SPS module 1216 may include their own dedicated antennas and / or utilize an antenna 1280 for communications. The cellular baseband processor(s) 1224 communicate with the UE 104 and / or RUs associated with the network entity 1202 through the transceiver(s) 1222 via one or more antennas 1280. The cellular baseband processor(s) 1224 and the application processor(s) 1206 may each include a computer-readable medium / memory 1224′, 1206′, respectively. The additional memory module 1226 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1224′, 1206′, 1226 may be non-transitory. The cellular baseband processor(s) 1224 and the application processor(s) 1206 are each responsible for general processing, including the execution of software stored in a computer-readable medium / memory. The software, when executed by the cellular baseband processor(s) 1224 / application processor(s) 1206, causes the cellular baseband processor(s) 1224 / application processor(s) 1206 to perform the various functions described above. The cellular baseband processor(s) 1224 and the application processor(s) 1206 are configured to perform the various functions described above based at least in part on information stored in memory. That is, the cellular baseband processor(s) 1224 and the application processor(s) 1206 may be configured to perform a first subset of the various functions described above without information stored in memory, and may be configured to perform a second subset of the various functions described above based on information stored in memory.The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor(s) 1224 / application processor(s) 1206 when executing software. The cellular baseband processor(s) 1224 / application processor(s) 1206 may be components of the UE 350 and may include at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1204 may be at least one processor chip (modem and / or application) and may include only the cellular baseband processor(s) 1224 and / or the application processor(s) 1206; in another configuration, the device 1204 may be an entire UE (see, e.g., UE 350 of FIG. 3) and may include additional modules of the device 1204.

[0118]

[0133] As described above, component 198 may be configured to receive a DCI indicating that the UE skips PDCCH monitoring or extends the CDRX active time. The DCI may include one or more of a skip instruction, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. Component 198 may be further configured to skip transmitting HARQ feedback for the DCI. Component 198 may be further configured to perform any of the aspects described in connection with flowcharts 800 and 900 in FIGS. 8 and 9 and / or aspects performed by UE 702 in FIG. 7. Component 198 may be internal to cellular baseband processor(s) 1224, application processor(s) 1206, or both cellular baseband processor(s) 1224 and application processor(s) 1206. Component 198 may be one or more hardware components specifically configured to perform the described processes / algorithms, may be implemented by one or more processors configured to perform the described processes / algorithms, may be stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the described processes / algorithms individually or in combination. As shown, apparatus 1204 may include various components configured for various functions. In one configuration, apparatus 1204, in particular cellular baseband processor(s) 1224 and / or application processor(s) 1206, may include means for receiving DCI indicating that the UE is to skip PDCCH monitoring or extend the CDRX active time.The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The apparatus 1204 may further include means for skipping transmission of HARQ feedback for the DCI. The apparatus 1204 may further include means for performing any of the aspects described in connection with flowcharts 800 and 900 in FIG. 8 and FIG. 9 and / or the aspects performed by the UE 702 in FIG. 7. The means may be a component 198 of the apparatus 1204 configured to perform the recited functions by the means. As described above, the apparatus 1204 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the recited functions by that means.

[0119]

[0134] FIG. 13 is a diagram 1300 illustrating an example of a hardware implementation for a network entity 1302. The network entity 1302 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1302 may include at least one of a CU 1310, a DU 1330, or an RU 1340. For example, depending on the layer functions processed by the component 199, the network entity 1302 may include a CU 1310, both the CU 1310 and the DU 1330, each of the CU 1310, the DU 1330, and the RU 1340, both the DU 1330, the DU 1330, and the RU 1340, or an RU 1340. The CU 1310 may include at least one CU processor 1312. The CU processor(s) 1312 may include on-chip memory 1312′. In some aspects, the CU 1310 may further include an additional memory module 1314 and a communication interface 1318. The CU 1310 communicates with the DU 1330 via a midhaul link, such as an F1 interface. The DU 1330 may include at least one DU processor 1332. The DU processor(s) 1332 may include an on-chip memory 1332′. In some aspects, the DU 1330 may further include an additional memory module 1334 and a communication interface 1338. The DU 1330 communicates with the RU 1340 via a fronthaul link. The RU 1340 may include at least one RU processor 1342. The RU processor(s) 1342 may include an on-chip memory 1342′. In some aspects, the RU 1340 may further include an additional memory module 1344, one or more transceivers 1346, an antenna 1380, and a communication interface 1348. The RU 1340 communicates with the UE 104. The on-chip memories 1312', 1332', 1342' and the additional memory modules 1314, 1334, 1344 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1312, 1332, 1342 is responsible for general processing, including executing software stored on the computer-readable medium / memory.The software, when executed by a corresponding processor(s), causes the processor(s) to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the processor(s) when executing the software.

[0120]

[0135] As described above, component 199 may be configured to output a DCI indicating that the UE skips PDCCH monitoring or extends the CDRX active time. The DCI may include one or more of a skip indication, scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment with a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment with an uplink retransmission TB size different from the initial uplink transmission TB size. Component 199 may be further configured to communicate with the UE based on the DCI. Component 199 may be further configured to perform any of the aspects described in connection with flowcharts 1000 and 1100 in FIG. 10 and FIG. 11 and / or aspects performed by base station 704 in FIG. 7. Component 199 may reside within one or more processors of one or more of CU 1310, DU 1330, and RU 1340. The component 199 may be one or more hardware components specifically configured to perform the described processes / algorithms, may be implemented by one or more processors configured to perform the described processes / algorithms, may be stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the described processes / algorithms individually or in combination. The network entity 1302 may include various components configured for various functions. In one configuration, the network entity 1302 may include means for outputting a DCI indicating that the UE will skip PDCCH monitoring or extend the CDRX active time. The DCI may include one or more of a skip indication, scheduling for retransmission of a successfully decoded PDSCH, a non-zero downlink assignment with a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment with an uplink retransmission TB size different from the initial uplink transmission TB size.The network entity 1302 may further include means for communicating with the UE based on the DCI. The network entity 1302 may further include means for performing any of the aspects described in connection with flowcharts 1000 and 1100 in Figures 10 and 11 and / or the aspects performed by the base station 704 in Figure 7. The means may be components 199 of the network entity 1302 configured to perform the recited functions. As described above, the network entity 1302 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the recited functions.

[0121]

[0136] The present disclosure provides a method for wireless communication in a UE. The method may include receiving DCI indicating that the UE is to skip PDCCH monitoring or extend a CDRX active time, the DCI including one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from an initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from an initial uplink transmission TB size, and skipping transmission of HARQ feedback for the DCI. By utilizing a dummy grant as a non-scheduling DCI for PDCCH monitoring adaptation, the method enables a more flexible indication with an additional information field for PDCCH monitoring compared to an indication mechanism based on a scheduling DCI, thereby improving efficiency of wireless communication.

[0122]

[0137] It should be understood that the specific order or hierarchy of the blocks in the disclosed processes / flowcharts is an example of an example approach. Based on design preferences, it should be understood that the specific order or hierarchy of the blocks in those processes / flowcharts can be rearranged. Furthermore, some blocks can be combined or omitted. The accompanying method claims present elements of the various blocks in an example order and are not limited to the specific order or hierarchy presented.

[0123]

[0138] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but are to be accorded the full scope consistent with the language of the claims. Reference to an element in the singular does not mean "one and only one," unless so expressly stated, but rather "one or more." Terms such as "if," "when," and "while" do not imply an immediate temporal relationship or reaction. That is, these phrases, such as "when," do not imply immediate action in response to or during the occurrence of an action; they simply mean that if a condition is met, an action will occur, but that the action does not require any specific or immediate time constraints for its occurrence. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. Unless expressly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" are inclusive of any combination of A, B, and / or C, and may include multiple As, multiple Bs, or multiple Cs.Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” can refer to A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination may include one or more elements of A, B, or C. A set should be interpreted as a set of elements, the number of elements being one or more. Thus, for a set X, X will include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor is configured to perform the set of functions individually or in any combination. Thus, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, the subset being the full set, a proper subset of the set, or an empty subset of the set. When a first device receives data from or transmits data to a second device, the data can be received / transmitted directly between the first and second devices or indirectly between the first and second devices via a set of devices. A device configured to "output" data, such as a transmission, signal, or message, may transmit the data or send the data to a device that transmits the data, for example, using a transceiver. A device configured to "receive" data, such as a transmission, signal, or message, may receive the data or obtain the data from a device that receives the data, for example, using a transceiver. Information stored in a memory includes instructions and / or data. All structural and functional equivalents to elements of various aspects described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims.Words such as "module," "mechanism," "element," and "device" may not be substitutes for the word "means." Thus, no element of a claim should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

[0124]

[0139] As used herein, the phrase "based on" should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) shall be construed as "based on at least A," unless expressly stated otherwise.

[0125]

[0140] The following aspects are exemplary only and may be combined with other aspects or teachings described herein without limitation.

[0126]

[0141] Aspect 1 is a method of wireless communication in a UE. The method may include receiving a DCI indicating that the UE will skip PDCCH monitoring or extend a CDRX active time. The DCI may include one or more of a skip indication, a scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from an initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from an initial uplink transmission TB size. The method may further include skipping transmission of hybrid automatic repeat request (HARQ) feedback for the DCI.

[0127]

[0142] Example 2 is the method of example 1, wherein the DCI may include scheduling for retransmission of successfully decoded PDSCHs.

[0128]

[0143] Aspect 3 is the method of aspect 1, wherein the DCI may include a skip indication, and the skip indication may include one or more of a first bitmap of all 0s for a Type 0 resource allocation or a second bitmap of all 1s for a Type 1 resource allocation.

[0129]

[0144] Example 4 is the method of example 1, wherein the DCI may include a skip indication, and the skip indication may have a first number of adaptation bits within the DCI that is different from a second number of associated PDCCH skip durations.

[0130]

[0145] Example 5 is the method of example 4, wherein the skip indication may include a single adaptation bit in the DCI for multiple PDCCH skip durations.

[0131]

[0146] Example 6 is the method of example 4, wherein the skip indication may include multiple adaptation bits in the DCI for a single PDCCH skip duration.

[0132]

[0147] Example 7 is the method of example 1, wherein the DCI may include a non-zero downlink allocation having a downlink retransmission TB size different from the initial downlink transmission TB size.

[0133]

[0148] Example 8 is the method of example 1, wherein the DCI may include a non-zero uplink allocation having an uplink retransmission TB size different from the initial uplink transmission TB size.

[0134]

[0149] Example 9 is the method of any of Examples 1 to 8, wherein the entry in the NDI within the DCI may indicate that a PDCCH monitoring adaptation field of the DCI indicates that the UE skips PDCCH monitoring for a period of time, and the method further includes skipping PDCCH monitoring in response to the DCI.

[0135]

[0150] Example 10 is the method of any of Examples 1 to 8, wherein the entry in the NDI in the DCI may indicate that a PDCCH monitoring adaptation field of the DCI does not include PDCCH skip information, and the method further includes restarting a CDRX inactivity timer in response to the DCI.

[0136]

[0151] Aspect 11 is an apparatus for wireless communication in a UE, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to perform, individually or in any combination, the methods of any of aspects 1 to 10 based at least in part on information stored in the at least one memory.

[0137]

[0152] A twelfth aspect is an apparatus for wireless communication in a UE, comprising means for performing each step of the method of any one of the first to tenth aspects.

[0138]

[0153] A thirteenth aspect of the present invention is the device of the eleventh or twelfth aspect, further comprising a transceiver configured to receive or transmit in connection with the method of any one of the first to tenth aspects.

[0139]

[0154] Aspect 14 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code in a UE, which, when executed by at least one processor, causes the at least one processor to perform any of the methods of aspects 1 to 10, individually or in any combination.

[0140]

[0155] Aspect 15 is a method of wireless communication in a network entity. The method may include outputting a DCI indicating that a UE skips PDCCH monitoring or extends a CDRX active time. The DCI may include one or more of a skip indication, scheduling for a retransmission of a successfully decoded PDSCH, a non-zero downlink assignment having a downlink retransmission TB size different from the initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size. The method may further include communicating with the UE based on the DCI.

[0141]

[0156] Example 16 is the method of example 15, wherein the DCI may include scheduling for retransmission of successfully decoded PDSCHs.

[0142]

[0157] Example 17 is the method of example 15, wherein the DCI may include a skip indication, and the skip indication may include one or more of a first bitmap of all zeros for a type 0 resource allocation or a second bitmap of all ones for a type 1 resource allocation.

[0143]

[0158] Example 18 is the method of example 15, wherein the DCI may include a skip indication, and the skip indication may have a first number of adaptation bits within the DCI that is different from a second number of associated PDCCH skip durations.

[0144]

[0159] Example 19 is the method of example 18, wherein the skip indication may include a single adaptation bit in the DCI for multiple PDCCH skip durations.

[0145]

[0160] Example 20 is the method of example 18, wherein the skip indication may include multiple adaptation bits in the DCI over a single PDCCH skip duration.

[0146]

[0161] Example 21 is the method of example 15, wherein the DCI may include a non-zero downlink allocation having a downlink retransmission TB size different from the initial downlink transmission TB size.

[0147]

[0162] Example 22 is the method of example 15, wherein the DCI may include a non-zero uplink allocation having an uplink retransmission TB size different from the initial uplink transmission TB size.

[0148]

[0163] Example 23 is the method of any of Examples 15 to 22, wherein the entry in the NDI in the DCI may indicate that a PDCCH monitoring adaptation field of the DCI indicates that the UE skips PDCCH monitoring for a period of time, and the method further includes skipping transmission of a PDCCH to the UE based on the DCI.

[0149]

[0164] Example 24 is the method of any of Examples 15 to 22, wherein the entry in the NDI within the DCI may indicate that a PDCCH monitoring adaptation field of the DCI does not include PDCCH skip information, and communicating with the UE may include communicating based on a CDRX inactivity timer that is restarted for the UE after the DCI.

[0150]

[0165] Example 25 is the method of any one of Examples 15 to 24, wherein communicating with the UE may include skipping receiving HARQ feedback for the DCI.

[0151]

[0166] Aspect 26 is an apparatus for wireless communication in a network entity, including at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to perform, at least in part, the methods of aspects 15 to 25, individually or in any combination, based on information stored in the at least one memory.

[0152]

[0167] Aspect 27 is an apparatus for wireless communication in a network entity, comprising means for performing each step of the method of any one of aspects 15 to 25.

[0153]

[0168] Aspect 28 is the device of aspect 26 or 27, further comprising a transceiver configured to receive or transmit in connection with the method of any of aspects 15 to 25.

[0154]

[0169] Aspect 29 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code in a network entity, which, when executed by at least one processor, causes the at least one processor to perform any of the methods of aspects 15 to 25, individually or in any combination.

Claims

1. 1. An apparatus for wireless communication in a user equipment (UE), comprising: at least one memory; at least one processor coupled to the at least one memory; Equipped with Based at least in part on the information stored in the at least one memory, the at least one processor, individually or in any combination, may cause the UE to: receiving downlink control information (DCI) indicating that the UE will skip physical downlink control channel (PDCCH) monitoring or extend a connection discontinuous reception (CDRX) active time, the DCI including one or more of a skip indication, a scheduling for a retransmission of a successfully decoded physical downlink shared channel (PDSCH), a non-zero downlink assignment having a downlink retransmission transport block (TB) size that is different from an initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size that is different from an initial uplink transmission TB size; skipping transmission of hybrid automatic repeat request (HARQ) feedback for the DCI; The apparatus is configured to:

2. 2. The apparatus of claim 1, further comprising: a transceiver coupled to the at least one processor, wherein the at least one processor is configured to, individually or in any combination, cause the UE to receive the DCI via the transceiver to receive the DCI.

3. 2. The apparatus of claim 1, wherein the DCI includes the scheduling for the retransmission of the successfully decoded PDSCH.

4. The DCI includes the skip indication, and the skip indication comprises: A first bitmap of all zeros for Type 0 resource allocation, or A second bitmap of all ones for Type 1 resource allocation The apparatus of claim 1 , comprising one or more of:

5. 2. The apparatus of claim 1, wherein the DCI includes the skip indication, the skip indication having a first number of adaptation bits within the DCI that is different from a second number of associated PDCCH skip durations.

6. The apparatus of claim 5 , wherein the skip indication comprises a single adaptation bit within the DCI for multiple PDCCH skip durations.

7. The apparatus of claim 5 , wherein the skip indication comprises multiple adaptation bits within the DCI for a single PDCCH skip duration.

8. The apparatus of claim 1 , wherein the DCI includes the non-zero downlink allocation having the downlink retransmission TB size different from the initial downlink transmission TB size.

9. The apparatus of claim 1 , wherein the DCI includes the non-zero uplink allocation having the uplink retransmission TB size different from the initial uplink transmission TB size.

10. an entry in a new data indicator (NDI) in the DCI indicates that a PDCCH monitoring adaptation field of the DCI indicates that the UE skips the PDCCH monitoring for a period of time, and the at least one processor, individually or in any combination, sends to the UE: skipping the PDCCH monitoring in response to the DCI; The apparatus of claim 1 , further configured to:

11. an entry in a new data indicator (NDI) in the DCI indicates that a PDCCH monitoring adaptation field of the DCI does not include PDCCH skip information, and the at least one processor, individually or in any combination, sends to the UE: restarting a CDRX inactivity timer in response to the DCI; The apparatus of claim 1 , further configured to:

12. 1. An apparatus for wireless communication in a network entity, comprising: at least one memory; at least one processor coupled to the at least one memory; Equipped with Based at least in part on the information stored in the at least one memory, the at least one processor, individually or in any combination, may cause the network entity to: outputting downlink control information (DCI) indicating that a user equipment (UE) will skip physical downlink control channel (PDCCH) monitoring or extend a connection discontinuous reception (CDRX) active time, the DCI including one or more of a skip indication, scheduling for retransmission of a successfully decoded physical downlink shared channel (PDSCH), a non-zero downlink assignment having a downlink retransmission transport block (TB) size different from an initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size; communicating with the UE based on the DCI; The apparatus is configured to:

13. 13. The apparatus of claim 12, further comprising: a transceiver coupled to the at least one processor, wherein the at least one processor is configured to, individually or in any combination, cause the network entity to output the DCI via the transceiver to output the DCI.

14. 13. The apparatus of claim 12, wherein the DCI includes the scheduling for the retransmission of the successfully decoded PDSCH.

15. The DCI includes the skip indication, and the skip indication comprises: A first bitmap of all zeros for Type 0 resource allocation, or A second bitmap of all ones for Type 1 resource allocation 13. The apparatus of claim 12, comprising one or more of:

16. 13. The apparatus of claim 12, wherein the DCI includes the skip indication, the skip indication having a first number of adaptation bits within the DCI that is different from a second number of associated PDCCH skip durations.

17. 17. The apparatus of claim 16, wherein the skip indication comprises a single adaptation bit within the DCI for multiple PDCCH skip durations.

18. 17. The apparatus of claim 16, wherein the skip indication comprises multiple adaptation bits within the DCI for a single PDCCH skip duration.

19. The apparatus of claim 12 , wherein the DCI includes the non-zero downlink allocation with the downlink retransmission TB size different from the initial downlink transmission TB size.

20. The apparatus of claim 12 , wherein the DCI includes the non-zero uplink allocation with the uplink retransmission TB size different from the initial uplink transmission TB size.

21. an entry in a new data indicator (NDI) in the DCI indicates that a PDCCH monitoring adaptation field of the DCI indicates that the UE skips the PDCCH monitoring for a period of time, and the at least one processor, individually or in any combination, sends to the network entity: skipping transmission of a PDCCH to the UE based on the DCI; The apparatus of claim 12 further configured to:

22. an entry in a new data indicator (NDI) in the DCI indicates that a PDCCH monitoring adaptation field of the DCI does not include PDCCH skip information, and to communicate with the UE, the at least one processor, individually or in any combination, communicating based on a CDRX inactivity timer restarted for the UE after the DCI; 13. The apparatus of claim 12, configured to:

23. To communicate with the UE, the at least one processor may, individually or in any combination, send to the network entity: skipping reception of Hybrid Automatic Repeat Request (HARQ) feedback for the DCI; 13. The apparatus of claim 12, configured to:

24. 1. A method of wireless communication in a user equipment (UE), comprising: receiving downlink control information (DCI) indicating that the UE will skip physical downlink control channel (PDCCH) monitoring or extend a connection discontinuous reception (CDRX) active time, the DCI including one or more of a skip indication, a scheduling for a retransmission of a successfully decoded physical downlink shared channel (PDSCH), a non-zero downlink assignment having a downlink retransmission transport block (TB) size different from an initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from an initial uplink transmission TB size; skipping transmission of Hybrid Automatic Repeat Request (HARQ) feedback for the DCI; and A method comprising:

25. 25. The method of claim 24, wherein the DCI includes the scheduling for the retransmission of the successfully decoded PDSCH.

26. The DCI includes the skip indication, and the skip indication comprises: A first bitmap of all zeros for Type 0 resource allocation, or A second bitmap of all ones for Type 1 resource allocation 25. The method of claim 24, comprising one or more of:

27. 25. The method of claim 24, wherein the DCI includes the skip indication, the skip indication having a first number of adaptation bits within the DCI that is different from a second number of associated PDCCH skip durations.

28. 28. The method of claim 27, wherein the skip indication comprises a single adaptation bit within the DCI for multiple PDCCH skip durations.

29. 28. The method of claim 27, wherein the skip indication comprises multiple adaptation bits within the DCI for a single PDCCH skip duration.

30. 1. A method of wireless communication in a network entity, comprising: outputting downlink control information (DCI) indicating that a user equipment (UE) will skip physical downlink control channel (PDCCH) monitoring or extend a connection discontinuous reception (CDRX) active time, the DCI including one or more of a skip indication, scheduling for retransmission of a successfully decoded physical downlink shared channel (PDSCH), a non-zero downlink assignment having a downlink retransmission transport block (TB) size different from an initial downlink transmission TB size, or a non-zero uplink assignment having an uplink retransmission TB size different from the initial uplink transmission TB size; communicating with the UE based on the DCI; A method comprising:

Images