Dynamic PDCCH skip for augmented reality

Abstract

Methods and apparatus are provided for dynamic PDCCH skipping for XR. The apparatus receives a PDCCH skip configuration. The apparatus receives an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration. The apparatus determines to monitor DCI during the PDCCH skip procedure based on the PDCCH skip configuration. The apparatus may send a UE capability report indicating that the UE supports dynamic behavior of the DCI that monitors the scheduled retransmission during the PDCCH skip period. The apparatus may monitor a PDCCH monitoring adaptation indication based on the non-scheduled DCI. The apparatus may perform a dynamic behavior of monitoring the DCI for scheduling retransmission during a PDCCH skip period.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 370,367, filed on August 3, 2022, entitled “Dynamic PDCCH Skipping for Extended Reality,” and U.S. Non-Provisional Patent Application Serial No. 18 / 363,615, filed on August 1, 2023, entitled “Dynamic PDCCH Skipping for Extended Reality,” the entireties of which are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to configuration for dynamic physical downlink control channel (PDCCH) skipping for extended reality (XR). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of 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.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with 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). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not a comprehensive review of all contemplated aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe 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 a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a UE. The apparatus may be a processor and / or a modem at the UE or the UE itself. The apparatus receives a physical downlink control channel (PDCCH) skip configuration. The apparatus receives an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration. The apparatus determines to monitor downlink control information (DCI) during the PDCCH skip procedure based on the PDCCH skip configuration.

[0008] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus may be a device at a network entity. The apparatus may be a processor and / or a modem at a network entity or the network entity itself. The apparatus outputs a physical downlink control channel (PDCCH) skip configuration. The apparatus outputs an indication of performing a PDCCH skip procedure based on the PDCCH skip configuration. The apparatus determines to output downlink control information (DCI) during the PDCCH skip procedure based on the PDCCH skip configuration.

[0009] To achieve the aforementioned and related purposes, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

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

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

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

[0014] Figure 2Dis a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a diagram illustrating an example of PDCCH skipping.

[0017] Figure 5 It is a call flow diagram of the signaling between the UE and the network entity.

[0018] Figure 6 is a flow chart of a method of wireless communication.

[0019] Figure 7 is a flow chart of a method of wireless communication.

[0020] Figure 8 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0021] Fig. 9 is a flow chart of a method of wireless communication.

[0022] Fig.10 is a flow chart of a method of wireless communication.

[0023] Fig.11 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0024] In wireless communications such as, for example, extended reality (XR), traffic for video data may have stringent latency requirements and large and variable data sizes. Physical downlink control channel (PDCCH) skipping may utilize scheduling downlink control information (DCI) in the PDCCH to inform the UE to skip PDCCH monitoring for a period of time. In PDCCH skipping, the network may provide an indication to the UE to stop or skip monitoring the PDCCH within the configured search space for a skip duration, so that the UE assumes that no data will be sent during the skip duration.

[0025] In an instance where the physical downlink shared channel (PDSCH) associated with the PDCCH is not successfully decoded, the UE sends a negative acknowledgement (NACK) to the network to trigger a retransmission of the PDSCH. However, the PDCCH may instruct the UE to perform a PDCCH skip procedure during the PDCCH skip period. However, the NACK triggers a retransmission of the PDSCH, but the UE may be entering a PDCCH skip period. The retransmission of the PDSCH and the PDCCH skip procedure may be two parallel operations that may conflict with each other.

[0026] Aspects presented herein provide configurations for dynamic PDCCH skipping that allow a UE to monitor a PDCCH during a PDCCH skipping procedure.Aspects presented herein allow a UE to monitor a scheduling DCI for retransmissions of a failed PDSCH during a PDCCH skipping period.

[0027] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the detailed description includes specific details. 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 these concepts.

[0028] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. When multiple processors are implemented, the multiple processors can 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 chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0030] Thus, in one or more example aspects, specific 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 codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media 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 these types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0031] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0032] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0033] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or 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, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

[0035] Figure 11 is a diagram 100 illustrating an example of a wireless communication system and an 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, such as 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 CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0036] Each of the units (i.e., CU 110, DU 130, RU 140, and near-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 send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals from one or more of the other units or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units on a wireless transmission medium.

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

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

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

[0040] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific 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 .

[0041] 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 updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

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

[0043] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each 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 a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0044] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 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 via various wireless D2D communication systems, such as, for example, Bluetooth TM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard TM (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE or NR.

[0045] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0046] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0048] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it 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.

[0049] 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 send 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 send 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 direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

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

[0051] 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. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated 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, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the 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 location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (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), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0052] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 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, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0053] Reference again Figure 1 In certain aspects, the UE 104 may include a skip component 198 configured to: receive a PDCCH skip configuration; receive an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; and determine to monitor DCI during the PDCCH skip procedure based on the PDCCH skip configuration.

[0054] Reference again Figure 1 In certain aspects, the base station 102 may include a configuration component 199 configured to: output a PDCCH skip configuration; output an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; and determine to output a DCI during the PDCCH skip procedure based on the PDCCH skip configuration.

[0055] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0056] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0057] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0058]

[0059] Table 1: Parameter set, SCS and CP

[0060] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a conventional CP is provided, where there are 14 symbols per slot and the parameter set μ=2, where there are 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 frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0061] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0062] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0063] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within 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 radio frame timing. 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) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0064] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0065] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0066] Figure 3 370 is a block diagram of a base station 310 in an access network communicating with a UE 350. 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 functionality. 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 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), 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 functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

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

[0068] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the 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 stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. 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 and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0069] 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 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0070] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the 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 transmission of upper layer PDUs, error correction through 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 between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0071] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select the appropriate coding and modulation schemes 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 corresponding spatial stream for transmission.

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

[0073] 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 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0074] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The skip component 198 performs various aspects.

[0075] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The configuration component 199 performs various aspects.

[0076] In wireless communications such as, for example, XR, the traffic of video data may have strict delay requirements (e.g., 10ms packet delay budget) and large and variable data sizes. PDCCH skipping may utilize scheduling DCI in PDCCH (e.g., format 0_1, 1_1, 0_2, or 1_2) to inform the UE to skip PDCCH monitoring in type 3 common search space (CSS) and UE-specific search space (USS) for a period of time. For the purpose of UE power saving, PDCCH skipping may skip PDCCH monitoring. In PDCCH skipping, the network may provide the UE with an indication to stop or skip monitoring the PDCCH within the configured search space for a skip duration, so that the UE assumes that no data will be sent during the skip duration.

[0077] refer to Figure 4 400, in some instances, a PDSCH 404 associated with a PDCCH 402 may not be successfully decoded by the UE, causing the UE to send a NACK 406 to the base station. The PDCCH 402 may also provide an indication to the UE to perform a PDCCH skip procedure during a PDCCH skip period 408. However, the NACK 406 may trigger a retransmission of the PDSCH 404, but the UE may be entering the PDCCH skip period 408. The retransmission of the PDSCH and the PDCCH skip procedure may be two parallel operations that may conflict with each other. In such instances, the UE will have to wait after the PDCCH skip period 408 to receive the DCI scheduling the retransmission of the PDSCH, but this adds additional delay.

[0078] Retransmission of PDSCH during the PDCCH skip procedure may be allowed by RRC configuration based on UE capabilities. For delay-sensitive XR data, UE behavior may be different. For example, if the retransmission will exceed the delay period, the UE may want to skip monitoring the retransmission scheduling DCI because the data may not be received within the period. In another example, if the retransmission does not exceed the delay period, the UE may want to perform PDCCH monitoring (e.g., 412) for the retransmission scheduling DCI during the PDCCH skip period to meet the delay period for XR video data, which may present a need for dynamic behavior of PDCCH monitoring for retransmissions during the specified PDCCH skip period.

[0079] Aspects presented herein provide configurations for dynamic PDCCH skipping that allow a UE to monitor a PDCCH during a PDCCH skipping procedure.Aspects presented herein allow a UE to monitor a scheduling DCI for retransmissions of a failed PDSCH during a PDCCH skipping period.

[0080] In some instances, the UE may be configured to support dynamic behavior of PDCCH monitoring for DCI scheduled for retransmission during a PDCCH skip period. For example, the UE may report in capability signaling an indication of the characteristics of dynamic behavior of PDCCH monitoring for DCI scheduled for retransmission during a PDCCH skip period.

[0081] In some instances, one or more options may be considered to support dynamic behavior. For example, a PDCCH adaptation indication DCI may be used to explicitly indicate whether DCI for scheduled retransmissions may be monitored during a PDCCH skip period. In some instances, the DCI may include a bit indicating such support, the DCI may swap a bit for the PDCCH adaptation indication field, or a new behavior may be defined for one or more values ​​of the PDCCH adaptation indication field. If the retransmission would exceed the delay period, the network may instruct the UE not to monitor, otherwise the UE monitors the PDCCH for retransmissions during the PDCCH skip period.

[0082] In some instances, support for dynamic behavior may be implicitly based on a delay period. The start of the delay period may be at least one of the following: the start of the DRX on duration, the first scheduled DCI or scheduled data after the DRX on duration, the first scheduled DCI or scheduled data after the last PDCCH skip period, or the first scheduled DCI or scheduled data for a data group associated with the same burst (e.g., an XR video frame in a PDU set). Some association information may be defined to associate the data, such as a PDU set ID in a scheduling DCI, or multiple PDSCHs scheduled by the same scheduling DCI.

[0083] In some examples, support for dynamic behavior may be based on duration. For example, a DCI may indicate two durations. One duration may be skipped for a legacy designed PDCCH, and another duration that may be less than the first duration may be available for the UE to monitor DCI for scheduled retransmissions. Monitoring of DCI for scheduled retransmissions may be subject to a HARQ RTT timer (e.g., 410) and a DRX retransmission timer (e.g., 414). In some examples, the UE may monitor DCI for scheduled retransmissions only after the HARQ RTT timer has expired and before the DRX retransmission timer expires.

[0084] In some instances, PDCCH monitoring adaptation indication signaling based on scheduled DCI may be utilized. In some instances, signaling based on non-scheduled DCI (i.e., DCI that does not schedule data) may be used for more flexible PDCCH monitoring indications. For example, if the UE supports PDCCH monitoring adaptation based on non-scheduled DCI and dynamic behavior of PDCCH monitoring for scheduled retransmissions during the PDCCH skip period, the UE may monitor the retransmission scheduling DCI during the PDCCH skip period, and may be separately configured for PDCCH adaptation indications based on scheduled DCI and non-scheduled DCI. In some instances, the UE separately reports to the base station whether the UE supports dynamic behavior of PDCCH monitoring for scheduled retransmissions during the PDCCH skip period indicated by scheduled DCI and non-scheduled DCI. In some instances, when the non-scheduled DCI provides an indication to perform PDCCH skipping, the UE does not monitor the scheduled DCI for retransmission.

[0085] Figure 5 5 is a call flow diagram 500 of signaling between a UE 502 and a base station 504. The base station 504 may be configured to provide at least one cell. The UE 502 may be configured to communicate with the base station 504. For example, in Figure 1 In the context of , base station 504 may correspond to base station 102 and UE 502 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 504 may correspond to base station 310 and UE 502 may correspond to UE 350.

[0086] At 506, the UE 502 may send a UE capability report. The UE may send a UE capability report indicating that the UE supports dynamic behavior of monitoring DCI scheduled for retransmission during a PDCCH skip period. The UE may send the UE capability report to the base station 504. The base station 504 may receive the UE capability report from the UE 502.

[0087] At 508, the base station 504 may output a PDCCH skip configuration. The base station 504 may output the PDCCH skip configuration to the UE 502. The UE 502 may receive the PDCCH skip configuration from the base station 504. The network entity may output the PDCCH skip configuration to at least one UE. The PDCCH skip configuration may be based on a delay period. In some aspects, the start of the delay period may be based on at least one of: a start of a discontinuous reception (DRX) on duration, a first DCI or scheduled data transmission after the DRX on duration, an end of a previous PDCCH skip period, a first DCI or scheduled data transmission after a previous PDCCH skip period, or a first DCI or scheduled data transmission for a data group associated with the same data burst.

[0088] At 510, the UE may send a NACK indicating unsuccessful data reception. The UE may send the NACK to the base station. The base station may receive the NACK from the UE. The NACK may initiate a retransmission of the unsuccessful data reception. In some aspects, in the event that the UE transmits the NACK, the UE may terminate the PDCCH skip procedure before the PDCCH skip duration or opportunity ends. In some aspects, the data reception may include dynamically scheduled data reception.

[0089] At 512, the base station may output an indication to perform a PDCCH skip procedure. The base station may output an indication to perform a PDCCH skip procedure to the UE. The UE may receive an indication to perform a PDCCH skip procedure from the base station. The network entity may output an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration.

[0090] At 514, UE 502 may determine to monitor DCI during the PDCCH skip procedure. The UE may determine to monitor DCI during the PDCCH skip procedure based on the PDCCH skip configuration. In some aspects, the UE may monitor DCI before the PDCCH skip duration or opportunity ends. In some aspects, in the case where the UE transmits NACK, the UE may terminate the PDCCH skip procedure before the PDCCH skip duration or opportunity ends. At 516, the base station 504 may determine to output DCI during the PDCCH skip procedure. The base station may determine to output DCI during the PDCCH skip procedure based on the PDCCH skip configuration. In some aspects, the DCI schedules retransmission of data during the PDCCH skip procedure. The PDCCH skip configuration may indicate whether to monitor the DCI scheduled for retransmission during the PDCCH skip period of the PDCCH skip procedure. In some aspects, if the retransmission of data exceeds the delay period, the PDCCH skip configuration may indicate that the DCI scheduled for retransmission is not monitored during the PDCCH skip period. The PDCCH skip configuration may be included in the PDCCH adaptation indication. In some aspects, the PDCCH adaptation indication provides instructions for monitoring the DCI for scheduled retransmission during the PDCCH skip period. The instructions for monitoring the DCI for scheduled retransmission during the PDCCH skip period may be within the DCI associated with the PDCCH adaptation indication. In some aspects, the DCI associated with the PDCCH adaptation indication may include at least one bit to indicate instructions for monitoring the DCI for scheduled retransmission during the PDCCH skip period. In some aspects, the DCI associated with the PDCCH adaptation indication may include two or more durations. For example, the first duration may correspond to the PDCCH skip period, and the second duration may correspond to the time period for monitoring the DCI for scheduled retransmission during the PDCCH skip period. In some aspects, the second duration is less than the first duration. In some aspects, the first duration and the second duration may be the same or different.

[0091] At 518, the base station 504 may output a configuration message. The base station may output the configuration message to the UE 502. The UE may receive the configuration message from the base station. The configuration message configures whether the non-scheduled DCI-based PDCCH monitoring adaptation indication indicates whether to monitor the scheduled retransmission DCI during the PDCCH skipping period.

[0092] At 520, the base station 504 may output at least one of the following: a PDCCH monitoring adaptation indication based on a non-scheduled DCI during a PDCCH skip period, or a DCI scheduled for retransmission during a PDCCH skip period. The base station may output at least one of the following to the UE 502: a PDCCH monitoring adaptation indication based on a non-scheduled DCI during a PDCCH skip period, or a DCI scheduled for retransmission during a PDCCH skip period. The UE 502 may receive a non-scheduled DCI or a scheduled DCI. In some aspects, the output of the PDCCH monitoring adaptation indication based on the non-scheduled DCI may be based on a UE capability report indicating that the UE supports monitoring of the PDCCH monitoring adaptation indication based on the non-scheduled DCI. In some aspects, if the non-scheduled DCI provides an indication of performing a PDCCH skip procedure, the DCI scheduled for retransmission is not monitored during the PDCCH skip period.

[0093] At 522, UE 502 may monitor a PDCCH monitoring adaptation indication based on a non-scheduled DCI. The UE may monitor a PDCCH monitoring adaptation indication based on a non-scheduled DCI from base station 504. For example, in an instance where the base station outputs a non-scheduled DCI, the UE may monitor the non-scheduled DCI. In some aspects, monitoring of the PDCCH monitoring adaptation indication based on the non-scheduled DCI is based on a UE capability report indicating that the UE supports monitoring of the PDCCH monitoring adaptation indication based on the non-scheduled DCI. In some aspects, if the non-scheduled DCI provides an indication to perform a PDCCH skip procedure, the DCI for scheduled retransmissions is not monitored during the PDCCH skip period.

[0094] At 524, UE 502 may perform a dynamic behavior of monitoring DCI for scheduled retransmissions. The UE may perform a dynamic behavior of monitoring DCI for scheduled retransmissions during a PDCCH skip period. The UE may monitor the scheduled DCI from base station 504. For example, in an instance where the base station outputs the scheduled DCI and the UE receives an indication to monitor the scheduled DCI during the PDCCH skip period, the UE may perform a dynamic behavior of monitoring the DCI for scheduled retransmissions during the PDCCH skip period.

[0095] Figure 6600 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104; device 804). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow a UE to monitor DCI during a PDCCH skip procedure.

[0096] At 602, the UE may receive a PDCCH skip configuration. For example, 602 may be performed by the skip component 198 of the device 804. The UE may receive the PDCCH skip configuration from a network entity. The PDCCH skip configuration may be based on a delay period. In some aspects, the start of the delay period may be based on at least one of: the start of a discontinuous reception (DRX) on duration, the first DCI or scheduled data transmission after the DRX on duration, the end of a previous PDCCH skip period, the first DCI or scheduled data transmission after the previous PDCCH skip period, or the first DCI or scheduled data transmission for a data group associated with the same data burst. The UE may determine the delay period based on a combination of the PDCCH skip configuration and the PDCCH skip configuration. Figure 5 Any of the aspects described above is used to receive a PDCCH skip configuration.

[0097] At 604, the UE may receive an indication to perform a PDCCH skip procedure. For example, 604 may be performed by the skip component 198 of the device 804. The UE may receive an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration. The UE may receive an indication to perform a PDCCH skip procedure from a network entity. The UE may receive an indication to perform a PDCCH skip procedure based on a combination of Figure 5 Any of the aspects described above is used to receive an indication to perform a PDCCH skip procedure.

[0098] At 606, the UE may determine to monitor DCI during the PDCCH skip procedure. For example, 606 may be performed by the skip component 198 of the device 804. The UE may determine to monitor DCI during the PDCCH skip procedure based on the PDCCH skip configuration. In some aspects, the UE may monitor DCI before the PDCCH skip duration or opportunity ends. In some aspects, in the case where the UE transmits NACK, the UE may terminate the PDCCH skip procedure before the PDCCH skip duration or opportunity ends. In some aspects, such as in the case where the UE transmits NACK for a dynamically scheduled PDSCH, after the PDCCH skip procedure has started and before the PDCCH skip duration ends, the UE may monitor the rescheduling DCI from the base station. In some aspects, the DCI schedules the retransmission of data during the PDCCH skip procedure. The PDCCH skip configuration may indicate whether to monitor the DCI scheduled for retransmission during the PDCCH skip period of the PDCCH skip procedure. In some aspects, if the retransmission of the data exceeds the delay period, the PDCCH skip configuration may indicate that the DCI scheduled for retransmission is not monitored during the PDCCH skip period. The PDCCH skip configuration may be included in the PDCCH adaptation indication. In some aspects, the PDCCH adaptation indication provides instructions for monitoring DCI for scheduled retransmissions during the PDCCH skip period. Instructions for monitoring DCI for scheduled retransmissions during the PDCCH skip period may be within the DCI associated with the PDCCH adaptation indication. In some aspects, the DCI associated with the PDCCH adaptation indication may include at least one bit to indicate instructions for monitoring DCI for scheduled retransmissions during the PDCCH skip period. In some aspects, the DCI associated with the PDCCH adaptation indication may include two or more durations. For example, a first duration may correspond to a PDCCH skip period, and a second duration may correspond to a time period for monitoring DCI for scheduled retransmissions during the PDCCH skip period. In some aspects, the second duration is less than the first duration. In some aspects, the first duration and the second duration may be the same or different. The UE may select a DCI for the PDCCH skip configuration based on a combination of the first and second durations. Figure 5 Any of the aspects described is used to monitor DCI during a PDCCH skipping procedure.

[0099] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104; device 804). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow a UE to monitor DCI during a PDCCH skip procedure.

[0100] At 702, the UE may send a UE capability report. For example, 702 may be performed by the skip component 198 of the apparatus 804. The UE may send a UE capability report indicating that the UE supports dynamic behavior of monitoring DCI scheduled for retransmission during a PDCCH skip period. Figure 5 Example aspects of a UE sending a UE capability report are illustrated.

[0101] At 704, the UE may receive a PDCCH skip configuration. For example, 704 may be performed by the skip component 198 of the device 804. The UE may receive the PDCCH skip configuration from a network entity. The PDCCH skip configuration may be based on a delay period. In some aspects, the start of the delay period may be based on at least one of: the start of a discontinuous reception (DRX) on duration, a first DCI or scheduled data transmission after the DRX on duration, an end of a previous PDCCH skip period, a first DCI or scheduled data transmission after a previous PDCCH skip period, or a first DCI or scheduled data transmission for a data group associated with the same data burst. The UE may determine the PDCCH skip configuration based on a combination of the PDCCH skip configuration and the delay period. Figure 5 Any of the aspects described above is used to receive a PDCCH skip configuration.

[0102] At 706, the UE may send a NACK indicating unsuccessful data reception. For example, 706 may be performed by the skip component 198 of the device 804. The UE may send the NACK to the network entity. The NACK may initiate a retransmission of the unsuccessful data reception. In some aspects, in the event that the UE transmits the NACK, the UE may terminate the PDCCH skip procedure before the PDCCH skip duration or opportunity ends. In some aspects, the data reception may include dynamically scheduled data reception. Figure 5 The UE is illustrated based on the combination Figure 5 An example aspect of sending a NACK according to any of the aspects described.

[0103] At 708, the UE may receive an indication to perform a PDCCH skip procedure. For example, 708 may be performed by the skip component 198 of the device 804. The UE may receive an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration. The UE may receive an indication to perform a PDCCH skip procedure from a network entity. The UE may receive an indication to perform a PDCCH skip procedure based on a combination of Figure 5 Any of the aspects described above is used to receive an indication to perform PDCCH skip configuration.

[0104] At 710, the UE may determine to monitor DCI during the PDCCH skip procedure. For example, 710 may be performed by the skip component 198 of the device 804. The UE may determine to monitor DCI during the PDCCH skip procedure based on the PDCCH skip configuration. In some aspects, the UE may monitor DCI before the PDCCH skip duration or opportunity ends. In some aspects, in the case where the UE transmits a NACK, the UE may terminate the PDCCH skip procedure before the PDCCH skip duration or opportunity ends. In some aspects, the DCI schedules the retransmission of data during the PDCCH skip procedure. The PDCCH skip configuration may indicate whether to monitor the DCI scheduled for retransmission during the PDCCH skip period of the PDCCH skip procedure. In some aspects, if the retransmission of the data exceeds the delay period, the PDCCH skip configuration may indicate that the DCI scheduled for retransmission is not monitored during the PDCCH skip period. The PDCCH skip configuration may be included in the PDCCH adaptation indication. In some aspects, the PDCCH adaptation indication provides instructions for monitoring the DCI scheduled for retransmission during the PDCCH skip period. Instructions for monitoring DCI for scheduled retransmissions during a PDCCH skip period may be within a DCI associated with a PDCCH adaptation indication. In some aspects, the DCI associated with the PDCCH adaptation indication may include at least one bit to indicate instructions for monitoring DCI for scheduled retransmissions during a PDCCH skip period. In some aspects, the DCI associated with the PDCCH adaptation indication may include two or more durations. For example, a first duration may correspond to a PDCCH skip period, and a second duration may correspond to a time period for monitoring DCI for scheduled retransmissions during a PDCCH skip period. In some aspects, the second duration is less than the first duration. In some aspects, the first duration and the second duration may be the same or different. The UE may select a time duration based on a combination of the first and second durations. Figure 5 Any of the aspects described is used to monitor DCI during a PDCCH skipping procedure.

[0105] At 712, the UE may receive a configuration message. For example, 712 may be performed by the skip component 198 of the device 804. The configuration message configures whether the PDCCH monitoring adaptation indication based on non-scheduled DCI indicates whether to monitor the DCI scheduled for retransmission during the PDCCH skip period. The UE may receive a configuration message from a network entity. Figure 5 Example aspects of a UE receiving a configuration message are illustrated.

[0106] At 714, the UE may monitor for a PDCCH monitoring adaptation indication based on a non-scheduled DCI. For example, 714 may be performed by the skip component 198 of the apparatus 804. The UE may monitor for a PDCCH monitoring adaptation indication based on a non-scheduled DCI from a network entity. In some aspects, the monitoring for the PDCCH monitoring adaptation indication based on the non-scheduled DCI is based on a UE capability report indicating that the UE supports monitoring for the PDCCH monitoring adaptation indication based on the non-scheduled DCI. In some aspects, if the non-scheduled DCI provides an indication to perform a PDCCH skip procedure, then the DCI for scheduled retransmissions is not monitored during the PDCCH skip period. The UE may monitor for a PDCCH monitoring adaptation indication based on a non-scheduled DCI ... Figure 5 Any of the aspects described is used to monitor the PDCCH monitoring adaptation indication based on non-scheduled DCI.

[0107] At 716, the UE may perform a dynamic behavior of monitoring the DCI for scheduled retransmissions. For example, 716 may be performed by the skip component 198 of the apparatus 804. The UE may perform a dynamic behavior of monitoring the DCI for scheduled retransmissions during the PDCCH skip period. The UE may perform a dynamic behavior of monitoring the DCI for scheduled retransmissions based on the combination of Figure 5 Any of the aspects described is used to perform dynamic behavior of monitoring DCI scheduled for retransmission.

[0108] Figure 8800 is a diagram illustrating an example of a hardware implementation for an apparatus 804. The apparatus 804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 804 may include at least one cellular baseband processor 824 (also referred to as a modem) coupled to one or more transceivers 822 (e.g., a cellular RF transceiver). The cellular baseband processor 824 may include at least one on-chip memory 824'. In some aspects, the apparatus 804 may also include one or more subscriber identity module (SIM) cards 820 and at least one application processor 806 coupled to a secure digital (SD) card 808 and a screen 810. The application processor 806 may include an on-chip memory 806'. In some aspects, the device 804 may also include a Bluetooth module 812, a WLAN module 814, an SPS module 816 (e.g., a GNSS module), one or more sensor modules 818 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 826, a power source 830, and / or a camera 832. The Bluetooth module 812, the WLAN module 814, and the SPS module 816 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 812, the WLAN module 814, and the SPS module 816 may include their own dedicated antennas and / or communicate using an antenna 880. The cellular baseband processor 824 communicates with the UE 104 and / or with the RU associated with the network entity 802 through the transceiver 822 via one or more antennas 880. The cellular baseband processor 824 and the application processor 806 may each include a computer-readable medium / memory 824', 806', respectively. The additional memory module 826 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 824', 806', 826 may be non-transitory. The cellular baseband processor 824 and the application processor 806 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software enables the cellular baseband processor 824 / application processor 806 to perform the various functions described above when executed by the cellular baseband processor 824 / application processor 806. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 824 / application processor 806 when executing the software. The cellular baseband processor 824 / application processor 806 may be a component 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 804 may be at least one processor chip (modem and / or applications) and include only the cellular baseband processor 824 and / or the application processor 806, while in another configuration, the device 804 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 804.

[0109] As discussed above, component 198 may be configured to receive a PDCCH skip configuration; receive an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; and determine to monitor DCI during the PDCCH skip procedure based on the PDCCH skip configuration. Component 198 may be within the cellular baseband processor 824, the application processor 806, or within both the cellular baseband processor 824 and the application processor 806. Component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the process / algorithm individually or in combination. As shown, device 804 may include multiple components configured for various functions. In one configuration, device 804 (and in particular cellular baseband processor 824 and / or application processor 806) may include a component for receiving a PDCCH skip configuration. The device includes a component for receiving an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration. The device includes a component for determining to monitor DCI during the PDCCH skip procedure based on the PDCCH skip configuration. The device also includes a component for sending a UE capability report indicating that the UE supports the dynamic behavior of monitoring the DCI of scheduled retransmission during the PDCCH skip period. The device also includes a component for monitoring the PDCCH monitoring adaptation indication based on non-scheduled DCI. The device also includes a component for performing the dynamic behavior of monitoring the DCI of scheduled retransmission during the PDCCH skip period. The device also includes a component for receiving a configuration message, wherein the configuration message configuration based on the PDCCH monitoring adaptation indication of non-scheduled DCI indicates whether to monitor the DCI of scheduled retransmission during the PDCCH skip period. The device also includes a component for sending a NACK indicating unsuccessful data reception. NACK initiates the retransmission of unsuccessful data reception. The component can be a component 198 of the device 804 configured to perform the function recorded by the component. As described above, the device 804 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, a component may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the component.

[0110] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102; network entity 1102). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow a base station to configure a UE to monitor DCI during a PDCCH skip procedure.

[0111] At 902, the network entity may output a PDCCH skip configuration. For example, 902 may be performed by a configuration component 199 of the network entity 1102. The network entity may output the PDCCH skip configuration to at least one UE. The PDCCH skip configuration may be based on a delay period. In some aspects, the start of the delay period may be based on at least one of: a start of a discontinuous reception (DRX) on duration, a first DCI or scheduled data transmission after the DRX on duration, an end of a previous PDCCH skip period, a first DCI or scheduled data transmission after a previous PDCCH skip period, or a first DCI or scheduled data transmission for a data group associated with the same data burst ... Figure 5 Any of the aspects described above is used to output the PDCCH skip configuration.

[0112] At 904, the network entity may output an indication to perform a PDCCH skip procedure. For example, 904 may be performed by configuration component 199 of network entity 1102. The network entity may output an indication to perform a PDCCH skip procedure to at least one UE. The network entity may output an indication to perform a PDCCH skip procedure based on a PDCCH skip configuration. The network entity may output an indication to perform a PDCCH skip procedure based on a combination of Figure 5 Any of the aspects described above is used to output an indication of performing a PDCCH skipping procedure.

[0113] At 906, the network entity may determine to output DCI during the PDCCH skip procedure. For example, 906 may be performed by the configuration component 199 of the network entity 1102. The network entity may determine to output DCI during the PDCCH skip procedure based on the PDCCH skip configuration. In some aspects, the DCI schedules the retransmission of data during the PDCCH skip procedure. The PDCCH skip configuration may indicate whether to monitor the DCI scheduled for retransmission during the PDCCH skip period of the PDCCH skip procedure. In some aspects, if the retransmission of the data exceeds the delay period, the PDCCH skip configuration may indicate that the DCI scheduled for retransmission is not monitored during the PDCCH skip period. The PDCCH skip configuration may be included in the PDCCH adaptation indication. In some aspects, the PDCCH adaptation indication provides instructions for monitoring the DCI scheduled for retransmission during the PDCCH skip period. The instructions for monitoring the DCI scheduled for retransmission during the PDCCH skip period may be within the DCI associated with the PDCCH adaptation indication. In some aspects, the DCI associated with the PDCCH adaptation indication may include at least one bit to indicate an instruction for monitoring the DCI for scheduled retransmissions during the PDCCH skip period. In some aspects, the DCI associated with the PDCCH adaptation indication may include two or more durations. For example, the first duration may correspond to the PDCCH skip period, and the second duration may correspond to a time period for monitoring the DCI for scheduled retransmissions during the PDCCH skip period. In some aspects, the second duration is less than the first duration. In some aspects, the first duration and the second duration may be the same or different. The network entity may determine the DCI for the PDCCH adaptation indication based on the combination of the first and second durations. Figure 5 Any of the aspects described herein determines to output DCI during a PDCCH skip procedure.

[0114] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102; network entity 1102). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow a base station to configure a UE to monitor DCI during a PDCCH skip procedure.

[0115] At 1002, the network entity may obtain a UE capability report. For example, 1002 may be performed by configuration component 199 of network entity 1102. The network entity may obtain a UE capability report from at least one UE. The UE capability report indicates that the UE supports dynamic behavior of monitoring DCI scheduled for retransmission during a PDCCH skip period. Figure 5 Example aspects of a network entity obtaining a UE capability report are illustrated.

[0116] At 1004, the network entity may output a PDCCH skip configuration. For example, 1004 may be performed by a configuration component 199 of the network entity 1102. The network entity may output the PDCCH skip configuration to at least one UE. The PDCCH skip configuration may be based on a delay period. In some aspects, the start of the delay period may be based on at least one of: a start of a DRX on duration, a first DCI or scheduled data transmission after the DRX on duration, an end of a previous PDCCH skip period, a first DCI or scheduled data transmission after a previous PDCCH skip period, or a first DCI or scheduled data transmission for a data group associated with the same data burst ... Figure 5 Any of the aspects described above is used to output the PDCCH skip configuration.

[0117] At 1006, the network entity may obtain a NACK indicating unsuccessful data reception. For example, 1006 may be performed by configuration component 199 of network entity 1102. The network entity may obtain a NACK from at least one UE. The NACK may initiate a retransmission of unsuccessful data reception. Figure 5 Example aspects of a network entity obtaining a NACK are illustrated.

[0118] At 1008, the network entity may output an indication to perform a PDCCH skip procedure. For example, 1008 may be performed by configuration component 199 of network entity 1102. The network entity may output an indication to perform a PDCCH skip procedure to at least one UE. The network entity may output an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration. The network entity may output an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration. Figure 5 Any of the aspects described above is used to output an indication of performing a PDCCH skipping procedure.

[0119] At 1010, the network entity may determine to output DCI during the PDCCH skip procedure. For example, 1010 may be performed by the configuration component 199 of the network entity 1102. The network entity may determine to output DCI during the PDCCH skip procedure based on the PDCCH skip configuration. In some aspects, the DCI schedules the retransmission of data during the PDCCH skip procedure. The PDCCH skip configuration may indicate whether to monitor the DCI scheduled for retransmission during the PDCCH skip period of the PDCCH skip procedure. In some aspects, if the retransmission of the data exceeds the delay period, the PDCCH skip configuration may indicate that the DCI scheduled for retransmission is not monitored during the PDCCH skip period. The PDCCH skip configuration may be included in the PDCCH adaptation indication. In some aspects, the PDCCH adaptation indication provides instructions for monitoring the DCI scheduled for retransmission during the PDCCH skip period. The instructions for monitoring the DCI scheduled for retransmission during the PDCCH skip period may be within the DCI associated with the PDCCH adaptation indication. In some aspects, the DCI associated with the PDCCH adaptation indication may include at least one bit to indicate an instruction for monitoring the DCI for scheduled retransmissions during the PDCCH skip period. In some aspects, the DCI associated with the PDCCH adaptation indication may include two or more durations. For example, the first duration may correspond to the PDCCH skip period, and the second duration may correspond to a time period for monitoring the DCI for scheduled retransmissions during the PDCCH skip period. In some aspects, the second duration is less than the first duration. In some aspects, the first duration and the second duration may be the same or different. The network entity may determine the DCI for the PDCCH adaptation indication based on the combination of the first and second durations. Figure 5 Any of the aspects described herein determines to output DCI during a PDCCH skip procedure.

[0120] At 1012, the network entity may output a configuration message. For example, 1012 may be performed by the configuration component 199 of the network entity 1102. The network entity may output a configuration message to at least one UE. The configuration message configures whether the PDCCH monitoring adaptation indication based on non-scheduled DCI indicates whether to monitor the DCI scheduled for retransmission during the PDCCH skip period. Figure 5 Example aspects of a network entity outputting configuration messages are illustrated.

[0121] At 1014, the network entity may output at least one of: a PDCCH monitoring adaptation indication based on a non-scheduled DCI during a PDCCH skip period, or a DCI scheduled for retransmission during a PDCCH skip period. For example, 1014 may be performed by a configuration component 199 of the network entity 1102. The network entity may output at least one of the following to at least one UE: a PDCCH monitoring adaptation indication based on a non-scheduled DCI during a PDCCH skip period, or a DCI scheduled for retransmission during a PDCCH skip period. In some aspects, the output of the PDCCH monitoring adaptation indication based on the non-scheduled DCI may be based on a UE capability report indicating that the UE supports monitoring of the PDCCH monitoring adaptation indication based on the non-scheduled DCI. In some aspects, if the non-scheduled DCI provides an indication to perform a PDCCH skip procedure, the DCI scheduled for retransmission is not monitored during the PDCCH skip period. The network entity may output at least one of the following to at least one UE: a PDCCH monitoring adaptation indication based on a non-scheduled DCI during a PDCCH skip period, or a DCI scheduled for retransmission during a PDCCH skip period ... the output of the PDCCH monitoring adaptation indication based on the non-scheduled DCI may be based on a UE capability report indicating that the UE supports monitoring of the PDCCH monitoring adaptation indication based on the non-scheduled DCI. In some aspects, if the non-scheduled DCI provides an indication to perform a PDCCH skip procedure, the Figure 5 Any of the aspects described above is used to output at least one non-scheduled DCI or a scheduled retransmission DCI.

[0122] Fig.111100 is a diagram illustrating an example of a hardware implementation for a network entity 1102. The network entity 1102 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1102 may include at least one of a CU 1110, a DU 1130, or a RU 1140. For example, depending on the layer functionality handled by the component 199, the network entity 1102 may include a CU 1110; both a CU 1110 and a DU 1130; each of the CU 1110, the DU 1130, and the RU 1140; the DU 1130; both a DU 1130 and a RU 1140; or a RU 1140. The CU 1110 may include at least one CU processor 1112. The CU processor 1112 may include an on-chip memory 1112'. In some aspects, the CU 1110 may also include an additional memory module 1114 and a communication interface 1118. CU1110 communicates with DU 1130 via a midhaul link, such as an F1 interface. DU 1130 may include at least one DU processor 1132. DU processor 1132 may include on-chip memory 1132'. In some aspects, DU 1130 may also include additional memory modules 1134 and communication interfaces 1138. DU 1130 communicates with RU 1140 via a fronthaul link. RU 1140 may include at least one RU processor 1142. RU processor 1142 may include on-chip memory 1142'. In some aspects, RU 1140 may also include additional memory modules 1144, one or more transceivers 1146, antennas 1180, and communication interfaces 1148. RU 1140 communicates with UE 104. On-chip memories 1112', 1132', 1142' and additional memory modules 1114, 1134, 1144 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 1112, 1132, 1142 is responsible for general processing, including the execution of software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0123] As discussed above, component 199 may be configured to output a physical downlink control channel (PDCCH) skip configuration; output an indication of performing a PDCCH skip procedure based on the PDCCH skip configuration; and determine to output DCI during the PDCCH skip procedure based on the PDCCH skip configuration. Component 199 may be within one or more processors of one or more of CU 1110, DU 1130, and RU 1140. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, 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 process / algorithm individually or in combination. Network entity 1102 may include multiple components configured for various functions. In one configuration, network entity 1102 may include a component for outputting a PDCCH skip configuration. The network entity includes a component for outputting an indication of performing a PDCCH skip procedure based on the PDCCH skip configuration. The network entity includes a component for determining to output DCI during the PDCCH skipping procedure based on the PDCCH skipping configuration. The network entity also includes a component for obtaining a UE capability report indicating the dynamic behavior of the UE supporting monitoring of the DCI scheduled for retransmission during the PDCCH skipping period. The network entity also includes a component for outputting at least one of the following: a PDCCH monitoring adaptation indication based on non-scheduled DCI during the PDCCH skipping period, or a DCI scheduled for retransmission during the PDCCH skipping period. The network entity also includes a component for outputting a configuration message. The configuration message configures whether the PDCCH monitoring adaptation indication based on non-scheduled DCI indicates whether to monitor the DCI scheduled for retransmission during the PDCCH skipping period. The network entity also includes a component for obtaining a NACK indicating unsuccessful data reception, wherein the NACK initiates retransmission of unsuccessful data reception. The component may be a component 199 of the network entity 1102 configured to perform the functions recorded by the component. As described above, the network entity 1102 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, a component may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the component.

[0124] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0125] 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 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 various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, 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" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. 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" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, wherein the number of elements is one or more. Thus, for a set of 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, either individually or in any combination. Thus, each of the at least one processor may be configured to perform a specific subset of a set of functions, where the subset is a complete set, a proper subset of a set, or an empty subset of a set. If a first device receives data from a second device or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a set of devices. A device configured to "output" data (such as, transmit, signal, or message) may, for example, send the data with a transceiver, or may transmit the data to a device that sends the data. A device configured to "obtain" data (such as, transmit, signal, or message) may, for example, receive data with a transceiver, or may obtain the data from a device that receives the data.The information stored in the memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will later be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0126] As used herein, the phrase "based on" should not be interpreted as referring 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.) should be interpreted as "based at least on A" unless specifically stated differently.

[0127] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limiting.

[0128] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving a PDCCH skip configuration; receiving an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; and determining to monitor DCI during the PDCCH skip procedure based on the PDCCH skip configuration.

[0129] Aspect 2 is a method according to aspect 1, the method further comprising: the DCI scheduling retransmission of data during the PDCCH skip procedure.

[0130] Aspect 3 is a method according to any one of aspects 1 and 2, the method further comprising: sending a UE capability report indicating that the UE supports dynamic behavior of monitoring the DCI scheduled for retransmission during a PDCCH skip period.

[0131] Aspect 4 is a method according to any one of aspects 1 to 3, the method further comprising: the PDCCH skip configuration indicates whether to monitor DCI scheduled for retransmission during a PDCCH skip period of the PDCCH skip procedure.

[0132] Aspect 5 is a method according to any one of aspects 1 to 4, the method further comprising: in a case where retransmission of data exceeds a delay period, the PDCCH skip configuration indicates that the DCI scheduled for retransmission is not monitored during the PDCCH skip period.

[0133] Aspect 6 is a method according to any one of Aspects 1 to 5, the method further comprising: the PDCCH skip configuration is included in a PDCCH adaptation indication, wherein the PDCCH adaptation indication provides instructions for monitoring the DCI scheduled for retransmission during the PDCCH skip period.

[0134] Aspect 7 is a method according to any one of aspects 1 to 6, the method further comprising: the instruction for monitoring the DCI for scheduling retransmission during the PDCCH skipping period is within the DCI associated with the PDCCH adaptation indication.

[0135] Aspect 8 is a method according to any one of Aspects 1 to 7, the method further comprising: the DCI associated with the PDCCH adaptation indication includes at least one bit to indicate the instruction for monitoring the DCI for scheduled retransmission during the PDCCH skip period.

[0136] Aspect 9 is a method according to any one of aspects 1 to 8, the method further comprising: the DCI associated with the PDCCH adaptation indication includes two or more durations.

[0137] Aspect 10 is a method according to any one of Aspects 1 to 9, the method further comprising: a first duration corresponds to the PDCCH skip period, and a second duration corresponds to a time period for monitoring the DCI scheduled for retransmission during the PDCCH skip period, wherein the second duration is less than the first duration.

[0138] Aspect 11 is a method according to any one of Aspects 1 to 10, and the method also includes: the PDCCH skip configuration is based on a delay period, wherein the start of the delay period is based on at least one of the following: the start of the DRX on duration, the first DCI or scheduled data transmission after the DRX on duration, the end of the previous PDCCH skip period, the first DCI or scheduled data transmission after the previous PDCCH skip period, or the first DCI or scheduled data transmission for a data group associated with the same data burst.

[0139] Aspect 12 is a method according to any one of aspects 1 to 11, the method further comprising: monitoring a PDCCH monitoring adaptation indication based on a non-scheduled DCI; and performing a dynamic behavior of monitoring the DCI scheduled for retransmission during a PDCCH skip period.

[0140] Aspect 13 is a method according to any one of Aspects 1 to 12, and the method also includes: the monitoring of the PDCCH monitoring adaptation indication based on the non-scheduled DCI is based on a UE capability report indicating that the UE supports the monitoring of the PDCCH monitoring adaptation indication based on the non-scheduled DCI.

[0141] Aspect 14 is a method according to any one of Aspects 1 to 13, the method further comprising: receiving a configuration message, wherein the configuration message configures the non-scheduled DCI-based PDCCH monitoring adaptation indication to indicate whether to monitor the DCI scheduled for retransmission during the PDCCH skip period.

[0142] Aspect 15 is a method according to any one of Aspects 1 to 14, the method further comprising: when the non-scheduled DCI provides an indication to perform the PDCCH skipping procedure, not monitoring the DCI for scheduled retransmission during the PDCCH skipping period.

[0143] Aspect 16 is a method according to any one of aspects 1 to 15, the method further comprising: sending a NACK indicating unsuccessful data reception, wherein the NACK initiates a retransmission of the unsuccessful data reception.

[0144] Aspect 17 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one processor, the at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement any one of aspects 1 to 16.

[0145] Aspect 18 is an apparatus for wireless communication at a UE, the apparatus comprising: a means for implementing any one of aspects 1 to 16.

[0146] Aspect 19 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 16.

[0147] Aspect 20 is a method for wireless communication at a network entity, the method comprising: outputting a PDCCH skip configuration; outputting an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; and determining to output DCI during the PDCCH skip procedure based on the PDCCH skip configuration.

[0148] Aspect 21 is a method according to aspect 20, the method further comprising: the DCI scheduling retransmission of data during the PDCCH skip procedure.

[0149] Aspect 22 is a method according to any one of aspects 20 and 21, the method further comprising: obtaining a UE capability report indicating that the UE supports dynamic behavior of monitoring the DCI scheduled for retransmission during a PDCCH skipping period.

[0150] Aspect 23 is a method according to any one of aspects 20 to 22, the method further comprising: the PDCCH skip configuration indicating whether to monitor DCI scheduled for retransmission during a PDCCH skip period of the PDCCH skip procedure.

[0151] Aspect 24 is a method according to any one of aspects 20 to 23, the method further comprising: in a case where retransmission of data exceeds a delay period, the PDCCH skip configuration indicates that the DCI scheduling retransmission is not monitored during the PDCCH skip period.

[0152] Aspect 25 is a method according to any one of Aspects 20 to 24, the method further comprising: the PDCCH skipping configuration is included in a PDCCH adaptation indication, wherein the PDCCH adaptation indication provides instructions for monitoring the DCI scheduled for retransmission during the PDCCH skipping period.

[0153] Aspect 26 is a method according to any one of aspects 20 to 25, the method further comprising: the instruction for monitoring the DCI scheduling retransmission during the PDCCH skipping period is within a DCI associated with the PDCCH adaptation indication.

[0154] Aspect 27 is a method according to any one of Aspects 20 to 26, the method further comprising: the DCI associated with the PDCCH adaptation indication includes at least one bit to indicate the instruction for monitoring the DCI for scheduled retransmission during the PDCCH skipping period.

[0155] Aspect 28 is a method according to any one of aspects 20 to 27, the method further comprising: the DCI associated with the PDCCH adaptation indication includes two or more durations.

[0156] Aspect 29 is a method according to any one of Aspects 20 to 28, the method further comprising: a first duration corresponds to the PDCCH skip period, and a second duration corresponds to a time period for monitoring the DCI scheduled for retransmission during the PDCCH skip period, wherein the second duration is less than the first duration.

[0157] Aspect 30 is a method according to any one of Aspects 20 to 29, the method further comprising: the PDCCH skip configuration is based on a delay period, wherein the start of the delay period is based on at least one of: the start of the DRX on duration, the first DCI or scheduled data transmission after the DRX on duration, the end of the previous PDCCH skip period, the first DCI or scheduled data transmission after the previous PDCCH skip period, or the first DCI or scheduled data transmission for a data group associated with the same data burst.

[0158] Aspect 31 is a method according to any one of Aspects 20 to 30, the method also including outputting at least one of the following: a PDCCH monitoring adaptation indication based on a non-scheduled DCI during a PDCCH skipping period, or the DCI scheduled for retransmission during the PDCCH skipping period.

[0159] Aspect 32 is a method according to any one of Aspects 20 to 31, and the method also includes: the output of the non-scheduled DCI based PDCCH monitoring adaptation indication is based on a UE capability report indicating that the UE supports the monitoring of the non-scheduled DCI based PDCCH monitoring adaptation indication.

[0160] Aspect 33 is a method according to any one of Aspects 20 to 32, the method further comprising: outputting a configuration message, wherein the configuration message configures the non-scheduled DCI-based PDCCH monitoring adaptation indication to indicate whether to monitor the DCI scheduled for retransmission during the PDCCH skip period.

[0161] Aspect 34 is a method according to any one of aspects 20 to 33, the method further comprising: when the non-scheduled DCI provides an indication to perform the PDCCH skipping procedure, not monitoring the DCI for scheduled retransmission during the PDCCH skipping period.

[0162] Aspect 35 is a method according to any one of aspects 20 to 34, the method further comprising: obtaining a NACK indicating unsuccessful data reception, wherein the NACK initiates a retransmission of the unsuccessful data reception.

[0163] Aspect 36 is an apparatus for wireless communication at a network node, the apparatus comprising: at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement any one of aspects 20 to 35.

[0164] Aspect 37 is an apparatus for wireless communication at a network node, the apparatus comprising: means for implementing any one of aspects 20 to 35.

[0165] Aspect 38 is a computer readable medium storing computer executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 20 to 35.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, alone or in any combination, configured to cause the apparatus to: receiving a physical downlink control channel (PDCCH) skip configuration; receiving an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; and Downlink control information (DCI) is monitored during the PDCCH skip procedure based on the PDCCH skip configuration.

2. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, the transceiver being configured to: Receiving the PDCCH skip configuration; receiving the indication to perform the PDCCH skip procedure based on the PDCCH skip configuration; and The DCI is monitored during the PDCCH skip procedure based on the PDCCH skip configuration. 3 . The apparatus of claim 1 , wherein the DCI schedules retransmission of data during the PDCCH skip procedure.

4. The apparatus of claim 1 , wherein the at least one processor is configured to cause the apparatus to: A UE capability report is sent indicating that the UE supports dynamic behavior of monitoring the DCI scheduled for retransmission during a PDCCH skip period. 5 . The apparatus of claim 1 , wherein the PDCCH skip configuration indicates whether to monitor DCI scheduled for retransmission during a PDCCH skip period of the PDCCH skip procedure. 6 . The apparatus according to claim 5 , wherein in a case where retransmission of data exceeds a delay period, the PDCCH skip configuration indicates not to monitor the DCI scheduling retransmission during the PDCCH skip period.

7. The apparatus of claim 5, wherein the PDCCH skip configuration is included within a PDCCH adaptation indication, wherein the PDCCH adaptation indication provides instructions for monitoring the DCI scheduled for retransmission during the PDCCH skip period.

8. The apparatus of claim 7, wherein the instructions for monitoring the DCI scheduling retransmissions during the PDCCH skipping period are within a DCI associated with the PDCCH adaptation indication.

9. An apparatus according to claim 8, wherein the DCI associated with the PDCCH adaptation indication includes at least one bit to indicate the instruction for monitoring the DCI for scheduling retransmission during the PDCCH skip period, wherein the DCI associated with the PDCCH adaptation indication includes two or more durations, wherein a first duration corresponds to the PDCCH skip period, and a second duration corresponds to a time period for monitoring the DCI for scheduling retransmission during the PDCCH skip period, wherein the second duration is less than the first duration.

10. An apparatus according to claim 1, wherein the PDCCH skip configuration is based on a delay period, wherein the start of the delay period is based on at least one of the following: the start of a discontinuous reception (DRX) on-duration, the first DCI or scheduled data transmission after the DRX on-duration, the end of a previous PDCCH skip period, the first DCI or scheduled data transmission after the previous PDCCH skip period, or the first DCI or scheduled data transmission for a data group associated with the same data burst.

11. The apparatus of claim 1 , wherein the at least one processor is configured to cause the apparatus to: Monitoring the PDCCH monitoring adaptation indication based on the non-scheduled DCI; and A dynamic behavior of monitoring the DCI scheduled for retransmission during a PDCCH skip period is performed.

12. An apparatus according to claim 11, wherein monitoring the PDCCH monitoring adaptation indication based on the non-scheduled DCI is based on a UE capability report indicating that the UE supports the monitoring of the PDCCH monitoring adaptation indication based on the non-scheduled DCI, and wherein in the case where the non-scheduled DCI provides an indication to perform the PDCCH skipping procedure, the DCI scheduled for retransmission is not monitored during the PDCCH skipping period.

13. The apparatus of claim 11, wherein the at least one processor is configured to: A configuration message is received, wherein the configuration message configures whether the non-scheduled DCI-based PDCCH monitoring adaptation indication indicates whether to monitor the DCI scheduling the retransmission during the PDCCH skipping period.

14. The apparatus of claim 1, wherein the at least one processor is configured to: A negative acknowledgement (NACK) is sent indicating an unsuccessful data reception, wherein the NACK initiates a retransmission of the unsuccessful data reception.

15. A method of wireless communication at a user equipment (UE), the method comprising: receiving a physical downlink control channel (PDCCH) skip configuration; receiving an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; as well as Determining to monitor downlink control information (DCI) during the PDCCH skip procedure is based on the PDCCH skip configuration.

16. An apparatus for wireless communication at a network entity, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, alone or in any combination, configured to cause the apparatus to: Output physical downlink control channel (PDCCH) skip configuration; outputting an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; and Downlink control information (DCI) is output during the PDCCH skip procedure based on the PDCCH skip configuration.

17. The apparatus of claim 16, further comprising a transceiver coupled to the at least one processor, the transceiver being configured to: Outputting the PDCCH skip configuration; outputting the indication to perform the PDCCH skip procedure based on the PDCCH skip configuration; and The DCI is output during the PDCCH skip procedure based on the PDCCH skip configuration.

18. The apparatus of claim 16, wherein the DCI schedules retransmission of data during the PDCCH skip procedure.

19. The apparatus of claim 16, wherein the at least one processor is configured to: A UE capability report is obtained indicating that a user equipment (UE) supports dynamic behavior of monitoring the DCI scheduled for retransmission during a PDCCH skip period.

20. The apparatus of claim 16, wherein the PDCCH skip configuration indicates whether to monitor DCI scheduled for retransmission during a PDCCH skip period of the PDCCH skip procedure. 21 . The apparatus of claim 20 , wherein in a case where retransmission of data exceeds a delay period, the PDCCH skip configuration indicates not to monitor the DCI scheduling retransmission during the PDCCH skip period.

22. The apparatus of claim 20, wherein the PDCCH skip configuration is included within a PDCCH adaptation indication, wherein the PDCCH adaptation indication provides instructions for monitoring the DCI scheduled for retransmission during the PDCCH skip period.

23. The apparatus of claim 22, wherein the instructions for monitoring the DCI scheduling retransmissions during the PDCCH skipping period are within a DCI associated with the PDCCH adaptation indication.

24. An apparatus according to claim 23, wherein the DCI associated with the PDCCH adaptation indication includes at least one bit to indicate the instruction for monitoring the DCI for scheduling retransmission during the PDCCH skip period, wherein the DCI associated with the PDCCH adaptation indication includes two or more durations, wherein a first duration corresponds to the PDCCH skip period, and a second duration corresponds to a time period for monitoring the DCI for scheduling retransmission during the PDCCH skip period, wherein the second duration is less than the first duration.

25. An apparatus according to claim 16, wherein the PDCCH skip configuration is based on a delay period, wherein the start of the delay period is based on at least one of: the start of a discontinuous reception (DRX) on-duration, the first DCI or scheduled data transmission after the DRX on-duration, the end of a previous PDCCH skip period, the first DCI or scheduled data transmission after the previous PDCCH skip period, or the first DCI or scheduled data transmission for a data group associated with the same data burst.

26. The apparatus of claim 16, wherein the at least one processor is configured to: At least one of the following is output: a PDCCH monitoring adaptation indication based on a non-scheduled DCI during a PDCCH skipping period, or the DCI scheduled for retransmission during the PDCCH skipping period.

27. The apparatus of claim 26, wherein outputting the non-scheduled DCI based PDCCH monitoring adaptation indication is based on a UE capability report indicating that the UE supports monitoring of the non-scheduled DCI based PDCCH monitoring adaptation indication.

28. The apparatus of claim 26, wherein the at least one processor is configured to: A configuration message is output, wherein the configuration message configures whether the non-scheduled DCI-based PDCCH monitoring adaptation indication indicates whether to monitor the DCI scheduling the retransmission during the PDCCH skipping period.

29. The apparatus of claim 16, wherein the at least one processor is configured to: A negative acknowledgement (NACK) is obtained indicating an unsuccessful data reception, wherein the NACK initiates a retransmission of the unsuccessful data reception.

30. A method for wireless communication at a network entity, the method comprising: Output physical downlink control channel (PDCCH) skip configuration; outputting an indication to perform a PDCCH skip procedure based on the PDCCH skip configuration; as well as Downlink control information (DCI) is output during the PDCCH skip procedure based on the PDCCH skip configuration.

Images