Configuration of low power-wake up signal (LP-WUS) in connected-discontinuous reception (c-DRX) off duration

A dual-radio system with LP-WUS monitoring during C-DRX off durations addresses power consumption and latency issues by efficiently triggering PDCCH monitoring windows, enhancing communication efficiency and reducing unnecessary wake-ups.

WO2026101673A1PCT designated stage Publication Date: 2026-05-15QUALCOMM INC
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
QUALCOMM INC
Filing Date
2025-10-14
Publication Date
2026-05-15

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in optimizing power consumption and reducing latency during connected-discontinuous reception (C-DRX) off durations by efficiently monitoring low-power wake-up signals (LP-WUS) to minimize unnecessary main radio wake-ups for physical downlink control channel (PDCCH) transmissions.

Method used

Implementing a dual-radio approach where a low-power wake-up radio monitors LP-WUS during C-DRX off durations, using an additional configuration to trigger PDCCH monitoring windows, allowing efficient monitoring of PDCCH transmissions without waiting for the next DRX on duration.

Benefits of technology

This approach enhances monitoring efficiency, reduces latency, and optimizes power consumption by enabling LP-WUS monitoring occasions during C-DRX off durations, improving overall communication performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2025050902_15052026_PF_FP_ABST
    Figure US2025050902_15052026_PF_FP_ABST
Patent Text Reader

Abstract

A method for wireless communication at a UE comprises receiving a discontinuous reception (DRX) configuration for monitoring physical downlink control channel (PDCCH) transmissions with a first radio, receiving an additional configuration associated with a low power-wake up signal (LP-WUS) and a second radio, and monitoring for the PDCCH transmissions in accordance with the DRX configuration and the additional configuration.
Need to check novelty before this filing date? Find Prior Art

Description

Qualcomm Ref. No. 2500661WO 1CONFIGURATION OF LOW POWER- WAKE UP SIGNAL (LP-WUS) IN CONNECTED-DISCONTINUOUS RECEPTION (C-DRX) OFF DURATIONCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of Israel Patent Application Serial No. 316913 entitled “CONFIGURATION OF LOW POWER-WAKE UP SIGNAL (LP-WUS) IN CONNECTED-DISCONTINUOUS RECEPTION (C-DRX) OFF DURATION” filed on November 10, 2024, which is expressly incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to communication systems, and more particularly, to wireless communication involving low-power wake-up signals (LP- WUSs).INTRODUCTION

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with 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 latency129025- 2534WO01Qualcomm Ref. No. 2500661WO 2 communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.BRIEF SUMMARY

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

[0006] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus comprises memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor is configured to receive a discontinuous reception (DRX) configuration for monitoring physical downlink control channel (PDCCH) transmissions with a first radio and receive an additional configuration associated with a low power-wake up signal (LP-WUS) and a second radio. The additional configuration indicating at least one of a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle, a start of a PDCCH monitoring window associated with the LP- WUS relative to an end of a DRX ON duration, a time difference between the start of a PDCCH monitoring window associated with the LP-WUS and a start time of a LP- WUS monitoring window, or start times of one or more LP-WUS monitoring windows. The at least one processor is further configured to monitor for the PDCCH transmissions in accordance with the DRX configuration and the additional configuration.

[0007] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus comprises memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory,129025- 2534WO01Qualcomm Ref. No. 2500661WO 3 the at least one processor is configured to transmit a discontinuous reception (DRX) configuration for monitoring physical downlink control channel (PDCCH) transmissions with a first radio and transmit an additional configuration associated with a low power- wake up signal (LP-WUS) and a second radio of the UE. The additional configuration indicating at least one of a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle, a start of a PDCCH monitoring window associated with the LP-WUS relative to an end of a DRX ON duration, a time difference between the start of a PDCCH monitoring window associated with the LP-WUS and a start time of a LP-WUS monitoring window, or start times of one or more LP-WUS monitoring windows. The at least one processor is further configured to transmit at least one PDCCH transmission in accordance with the DRX configuration or the additional configuration.

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

[0009] FIG. l is a diagram illustrating an example of a wireless communications system and an access network, in accordance with various aspects of the present disclosure.

[0010] FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

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

[0012] FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

[0013] FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.129025- 2534WO01Qualcomm Ref. No. 2500661WO 4

[0014] FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network, in accordance with various aspects of the present disclosure.

[0001] FIG. 4A is a diagram illustrating an example of a discontinuous reception (DRX) cycle that may be configured by a base station for a UE, in accordance with various aspects of the present disclosure.

[0002] FIG. 4B is a diagram illustrating an example of a UE having a first radio and a low power radio, in accordance with various aspects of the present disclosure.

[0003] FIG. 4C illustrates example aspects of an OOK signal, in accordance with various aspects of the present disclosure.

[0004] FIG. 5 is a diagram illustrating an example of associating DRX cycles with the LP- WUS monitoring, in accordance with various aspects of the present disclosure.

[0005] FIG. 6 is a diagram illustrating another example of associating DRX cycles with the LP-WUS monitoring, in accordance with various aspects of the present disclosure.

[0006] FIG. 7 is a diagram illustrating a further example of associating DRX cycles with the LP-WUS monitoring, in accordance with various aspects of the present disclosure.

[0007] FIG. 8 is a diagram illustrating an example of PDCCH transmission monitoring involving LP-WUS, in accordance with various aspects of the present disclosure.

[0008] FIG. 9 is a flowchart of a method of wireless communication at a UE, in accordance with various aspects of the present disclosure.

[0009] FIG. 10 is a flowchart of a method of wireless communication at a network node, in accordance with various aspects of the present disclosure.

[0015] FIG. 11 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or UE, in accordance with various aspects of the present disclosure.

[0016] FIG. 12 is a diagram illustrating an example of a hardware implementation for an example network entity, in accordance with various aspects of the present disclosure.

[0017] FIG. 13 is a diagram illustrating an example of a hardware implementation for an example network entity, in accordance with various aspects of the present disclosure.DETAILED DESCRIPTION

[0018] Various aspects relate generally to wireless communication systems. Some aspects more specifically relate to monitoring for low-power wake-up signals (LP-WUSs) using a different receiver than used to monitor for physical downlink control channel129025- 2534WO01Qualcomm Ref. No. 2500661WO 5(PDCCH) transmissions. In some aspects, the wireless communication, e.g., including the monitoring, may be performed by a device such as a user equipment (UE). In some aspects, the device may monitor for the LP-WUS during an OFF period of a connected mode-discontinuous reception (C-DRX) (e.g., a DRX OFF duration) to enable reductions in power consumption while also reducing latency for communication. In some examples, a UE may receive a DRX configuration that indicates ON durations for monitoring for PDCCH transmissions and OFF durations during which the UE does not monitor for PDCCH. The PDCCH may be received by the UE with a first radio (e.g., the main radio, also referred to as the first receiver or main receiver). Additionally, the UE may receive an additional configuration for monitoring LP-WUSs (e.g., including an on-off keying (OOK) waveform) with a second radio (e.g., which may be referred to as a low-power wake-up radio / receiver (LP-WUR), or the second receiver). In some aspects, the additional configuration (which may also be referred to as a LP-WUS monitoring configuration or a configuration associated with LP-WUS) may indicate one or more parameters that enable the UE to know when to monitor for the LP-WUS, and / or PDCCH indicated by the LP-WUS, relative to the DRX configuration of the UE. For example, the LP- WUS monitoring configuration may indicate one or more of a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle, a start of a PDCCH monitoring window associated with the LP-WUS relative to an end of a DRX ON duration, a time difference between the start of a PDCCH monitoring window associated with the LP-WUS and a start time of a LP-WUS monitoring window, and / or start times of one or more LP-WUS monitoring windows. The UE may monitor for the LP-WUS using the second, low- power radio based on the additional configuration. The UE may monitor for the PDCCH transmissions in accordance with the DRX configuration, and if the LP-WUS is received, monitor for the PDCCH transmission in accordance with the additional configuration. The UE may use the first radio to monitor for the PDCCH based on the DRX configuration and / or triggered by reception of an LP-WUS.

[0019] Particular aspects of the subject matter described in this disclosure may enable LP- WUS monitoring occasions (also referred to as “LP-WUS monitoring windows”) to129025- 2534WO01Qualcomm Ref. No. 2500661WO 6 be associated with C-DRX for monitoring PDCCH transmissions at a UE. Specifically, according to an LP-WUS monitoring configuration (e.g., in addition to the DRX configuration), one or more LP-WUS monitoring occasions may be configured during DRX OFF durations. When an LP-WUS is detected during the LP- WUS monitoring occasions, one or more PDCCH monitoring windows (also referred as “PDCCH monitoring occasions”) may be triggered. This approach allows the UE to monitor for PDCCH transmissions during the DRX OFF duration, without waiting for the next DRX ON duration. Consequently, the aspects presented herein can improve monitoring efficiency, reduce latency, and optimize power consumption for a UE.

[0020] The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

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

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

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

[0024] While aspects, implementations, and / or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and / or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and / or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-129025- 2534WO01Qualcomm Ref. No. 2500661WO 8 level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders / summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

[0025] Deployment of communication systems, such as 5GNR systems, may be arranged in multiple manners with various components or constituent parts. 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 a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmission reception point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

[0026] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (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 throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).129025- 2534WO01Qualcomm Ref. No. 2500661WO 9

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

[0028] FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can 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). A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an Fl interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.

[0029] Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near- RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver,129025- 2534WO01Qualcomm Ref. No. 2500661WO 10 a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0030] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane 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 implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an El interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.

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

[0032] Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a 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, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 140 can be implemented to handle over the air (OTA)129025- 2534WO01Qualcomm Ref. No. 2500661WO 11 communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0033] The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an 01 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 life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O- eNB) 111, via an 01 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an 01 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.

[0034] The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (Al) / machine learning (ML) (AI / ML) workflows including model training and updates, 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 (such as via an Al interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.

[0035] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment129025- 2534WO01Qualcomm Ref. No. 2500661WO 12 information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. 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 for performance and employ AI / ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0036] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify 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 a UE 104. The base station 102 may include macrocells (high power cellular base station) and / or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be through one or more carriers. The base station 102 / UEs 104 may use spectrum up to F MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Ex MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).129025- 2534WO01Qualcomm Ref. No. 2500661WO 13

[0037] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the 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 through a variety of wireless D2D communications systems, such as for example, Bluetooth™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi™ (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0038] The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0039] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5GNR, 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 referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0040] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into midband frequencies. In addition, higher frequency bands are currently being explored to129025- 2534WO01Qualcomm Ref. No. 2500661WO 14 extend 5GNR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0041] With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

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

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

[0044] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The 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, generally, 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, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and / or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position / location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NRE-CID) methods, NR signals (e.g., multi -round trip time (Multi -RTT), DL angle- of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time129025- 2534WO01Qualcomm Ref. No. 2500661WO 16 difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0045] Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as loT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and / or individually access the network.

[0046] Referring again to FIG. 1, in certain aspects, the UE 104 may have a PDCCH transmission monitoring component 198 that may be configured to perform the PDCCH transmission monitoring involving LP-WUS. In certain aspects, the base station 102 may have a PDCCH transmission component 199 that may be configured to perform the PDCCH transmission monitoring involving LP-WUS. By introducing low power consumption schemes to monitor PDCCH transmissions during DRX OFF durations (e.g., configuring LP-WUS monitoring occasions during DRX OFF durations for avoiding unnecessary main radio wakeup for PDCCH transmission monitoring), the aspects presented herein can enhance monitoring efficiency, reduce latency, and optimize power consumption for a UE when monitoring PDCCH transmissions.

[0047] FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280129025- 2534WO01Qualcomm Ref. No. 2500661WO 17 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi- statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD.

[0048] FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT- s-OFDM) symbols (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration may scale with 1 / SCS.129025- 2534WO01Qualcomm Ref. No. 2500661WO 18Table 1: Numerology, SCS, and CP

[0049] For normal CP (14 symbols / slot), different numerologies p 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology p, there are 14 symbols / slot and 2^ slots / subframe. The subcarrier spacing may be equal to 2 / z* 15 kHz, where . is the numerology 0 to 4. As such, the numerology p=0 has a subcarrier spacing of 15 kHz and the numerology p=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology p=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended).

[0050] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0051] As illustrated in FIG. 2 A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may129025- 2534WO01Qualcomm Ref. No. 2500661WO 19 also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

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

[0053] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the129025- 2534WO01Qualcomm Ref. No. 2500661WO 20 particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequencydependent scheduling on the UL.

[0054] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and / or negative ACK (NACK)). The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0055] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 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, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer 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),129025- 2534WO01Qualcomm Ref. No. 2500661WO 21 demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0056] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may 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 together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted 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 respective spatial stream for transmission.

[0057] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the 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 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a129025- 2534WO01Qualcomm Ref. No. 2500661WO 22 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 most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0058] The controller / processor 359 can 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 and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0059] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC 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 TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0060] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select 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 antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.129025- 2534WO01Qualcomm Ref. No. 2500661WO 23

[0061] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0062] The controller / processor 375 can 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 and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0063] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects in connection with the PDCCH transmission monitoring component 198 of FIG. 1.

[0064] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects in connection with the PDCCH transmission component 199 of FIG. 1.

[0065] DRX provides a power-saving method where a UE skips monitoring for PDCCH during periods of time and periodically wakes up to monitor the PDCCH for control messages. If the UE is in an RRC connected state, the DRX operation may be referred to as C-DRX. During non-active times (e.g., DRX OFF durations), the UE goes into sleep mode. In a non-DRX mode, the UE monitors for PDCCH in each subframe to check whether there is downlink data available. Continuous monitoring of the PDCCH uses more battery power at the UE. The DRX mode, or DRX operation of the UE, enables the UE to save power by skipping PDCCH monitoring during DRX OFF durations. As the C-DRX monitoring periodicity is fixed, the UE wakes up and monitors for PDCCH transmissions during each DRX ON duration, e.g., even if no control message is transmitted by the network. On the other hand, if PDCCH transmissions need to be transmitted during the DRX off durations, the network and the UE wait until the next DRX ON duration to transmit and receive the control message. This reduces potential power savings and impacts latency.129025- 2534WO01Qualcomm Ref. No. 2500661WO 24

[0066] The UE may receive a DRX configuration from the network in RRC signaling from a base station, such as in an RRC Connection Setup request or an RRC connection reconfiguration request. A DRX configuration may include the configuration of one or more timers and values. In some examples, the DRX configuration may include any of an ON duration Timer, a DRX inactivity timer, a DRX retransmission timer, a DRX UL retransmission timer, a long DRX cycle, a value of the DRX start offset, a DRX short cycle timer, and / or a short DRX cycle, among others. A DRX cycle may comprise a periodic repetition of an on duration in which the UE monitors for PDCCH from the base station and an off duration. FIG. 4A illustrates an example of a DRX cycle 400 including periodic ON durations during which the UE monitors for PDCCH and OFF durations during which the UE may not monitor for the PDCCH. The OFF duration may be referred to as a DRX opportunity. During the OFF duration, the UE does not monitor for PDCCH. The UE may enter a sleep mode or a low power mode in which the UE minimizes power consumption by shutting down a radio frequency (RF) function without detecting communication from the base station.

[0067] The ON duration timer may correspond to a number of consecutive PDCCH subframes to be monitored or decoded when the UE wakes up from the OFF duration in the DRX Cycle. The DRX retransmission timer may correspond to a consecutive number of PDCCH subframes for the UE to monitor when a retransmission is expected by the UE. The DRX inactivity timer may correspond to an amount of time before the UE may again enter the OFF duration following successfully decoding PDCCH. The amount of time may be in terms of a transmission time interval (TTI) duration. After a UE successfully receives downlink data, the DRX inactivity timer may start counting a number of subframes. If any uplink or downlink data transmissions occur while the DRX inactivity timer is running, the timer restarts. If the DRX inactivity timer expires without uplink or downlink activity, the UE may enter the DRX cycle to achieve power savings.

[0068] A UE may include an LP-WUR designed to be switched on and off quickly. The LP- WUR may support reception and processing of simple signals (e.g., limited bandwidth and simpler waveforms such as LP-WUS, an on-off keying (OOK) waveform). FIG. 4C illustrates examples aspects of an OOK waveform. For example, OOK may be a modulation scheme of keying a sinusoidal carrier signal on and off with a unipolar binary signal (two level amplitude keying where a first amplitude represents ON and129025- 2534WO01Qualcomm Ref. No. 2500661WO 25 a second amplitude represents OFF). As illustrated in FIG. 4C, a first duration 422 may represent a zero (“0”) bit, a duration 424 may represent a one (“1”) bit, and a third duration 426 may represent a 0 bit. Each of the durations may be a single OFDM symbol, in some examples.

[0069] The LP-WUR operates with significantly lower power than the main radio / receiver. UEs equipped with a LP-WUR in addition to the main radio / receiver may support reception of LP-WUSs using the LP-WUR. FIG. 4B illustrates an example of a UE 416 having a first radio 408 (that may also be referred to as a main radio, a first receiver, a main receiver, a higher power radio, and / or a higher power receiver) and having a second radio 410 that consumes less power than the first radio 408. The second radio 410 may be referred to as an LP-WUR, a second receiver, a low power receiver, and / or a low power radio, among other examples. FIG. 4B illustrates the two radios sharing an antenna 412. However, in some examples, the two radios may use different antennas.

[0070] Performing LP-WUS triggered PDCCH monitoring in connection with the DRX configuration can help to improve the monitoring efficiency, reduce latency, and reduce power consumption. For example, the UE may turn off its main radio to save power, entering the sleep mode while using the LP-WUR to monitor for LP-WUS. If an LP-WUS is detected / received, the UE may wake up, turn on the main radio (which consumes more power than the LP-WUR), to monitor for and / or receive the control message (e.g., PDCCH transmission) from the network using the main radio. The PDCCH transmission may schedule a data transmission, and the UE may then receive the scheduled data. By using the LP-WUR to monitor for the LP-WUS, the UE saves power in comparison to monitoring for a WUS with the main radio. This enables the UE to monitor for an LP-WUS more frequently while maintaining power savings at the UE.

[0071] The aspects presented herein may enable LP-WUS monitoring windows (also referred to as “LP-WUS monitoring occasions”) to be associated with C-DRX configurations for monitoring for PDCCH transmissions at a UE. Specifically, according to an LP- WUS monitoring configuration (e.g., in addition to the DRX configuration), one or more LP-WUS monitoring windows may be configured during DRX OFF durations. For example, when an LP-WUS is detected during the LP-WUS monitoring occasions / windows, it may trigger one or more PDCCH monitoring windows (also129025- 2534WO01Qualcomm Ref. No. 2500661WO 26 referred to as “PDCCH monitoring occasions”) in which the UE receives PDCCH from the network. Therefore, the UE may monitor PDCCH transmissions during the DRX OFF durations without waiting for the next DRX ON duration. Consequently, the aspects presented herein can improve monitoring efficiency, reduce latency, and optimize power consumption for a UE.

[0072] For example, FIG. 4A is a diagram illustrating an example of a DRX cycle 400 that may be configured by a network node for a UE. As stated above, the UE may reduce power consumption by performing a DRX operation in which the UE monitors for communication or transmits communication during a DRX ON duration and does not monitor for communication or transmit communication during a DRX OFF duration. For example, the UE may monitor for transmission (e.g., from a network node such as a based station) discontinuously using a sleep and wake cycle. The DRX OFF duration may correspond to a time during which the UE operates in a lower power mode, a sleep mode, etc. During the DRX OFF duration, the UE may shut down, turn off, or not use a radio frequency (RF) function. The DRX pattern may include one or more timers or values, such as an DRX ON duration timer or a value that indicates the starting point of the DRX ON duration and / or the DRX OFF duration, etc. The DRX ON duration timer may indicate a period of time, e.g., in consecutive symbols, slots, subframes, or Transmission Time Intervals (TTIs), in which the UE wakes up from the DRX OFF duration and monitors for control signaling. A DRX cycle may include a periodic repetition of the DRX ON duration and the DRX OFF duration. By having periods during which the UE does not monitor for or transmit communication, the UE may save power or extend battery life for the UE. For example, DRX may provide power savings, e.g., at a physical layer or a medium access control (MAC) layer.

[0073] Specifically, a UE may monitor for a PDCCH from a network node during a DRX ON duration (e.g., using a main radio such as 408) to check for an indication of a new transmission (downlink, uplink, or sidelink) on the serving cell within the DRX group. During a DRX OFF duration, the UE may skip monitoring for the PDCCH. If the UE receives a PDCCH 402 during the ON duration, such as illustrated in FIG. 4A, the UE may stay awake for an extended period of time based on an inactivity timer 404 that starts upon reception of the PDCCH 402. If the UE does not receive downlink communication from the network node during the duration of the inactivity timer 404,129025- 2534WO01Qualcomm Ref. No. 2500661WO 27 the UE may stop monitoring, e.g., enter a sleep mode or lower power mode, for communication during the remaining DRX OFF duration.

[0074] According to the DRX configuration, the DRX cycle may start with a starting subframe 406 (e.g., determined based on a configuration parameter such as a drx- LongCycleStartOffset). In some aspects, a DCI with cyclic redundancy check (CRC) scrambled by paging-specific radio network temporary identifier (PS-RNTI) (DCP) may be used by the UE to monitor for a wake-up signal the main radio / receiver. The wake-up signal may be indicated to the UE in DCI that is received by the main radio / receiver. The UE may monitor for the wake-up signal based on a search start time for DCI (e.g., DCI format 2-6) that may be defined relative to the beginning of the DRX ON duration (e.g., defined by parameter drx-onDurationTimer) by an offset parameter (e.g., ps-0ffset-rl6). In some aspects, the offset parameter may be defined in units of 0.125 milliseconds (e.g., a value of 1 corresponds to a 0.125 ms offset, a value of 2 corresponds to a 0.25 ms offset, and a value of 3 corresponds to a 0.375 ms offset). The offset that indicates the beginning of the search time for the DCI helps the UE to know when to begin monitoring for specific control information based on the DRX cycle, aiding in efficient power management and timely reception of paging or signaling messages.

[0075] As described herein, an LP-WUS received with an LP-WUR may be used to trigger PDCCH monitoring in RRC CONNECTED mode in association with a C-DRX configuration. In some aspects, the network node may configure the UE to perform LP-WUS monitoring before the DRX ON duration (e.g., before the DRX ON timer starts), allowing the LP-WUS to trigger the PDCCH monitoring occasions and initiate the PDCCH monitoring during DRX ON duration. In some aspects, the network node may configure the UE for LP-WUS monitoring outside the existing DRX ON durations to trigger PDCCH monitoring during the DRX OFF durations.

[0076] As stated above, a UE capable of performing LP-WUS triggered PDCCH monitoring may include a main radio for monitoring for PDCCH transmissions and a LP-WUR for monitoring for LP-WUSs. FIG. 4B illustrates an example of a UE having the two radios, or two receivers. For example, FIGS. 5-7 illustrate examples of associating DRX cycles with the LP-WUS monitoring for optimizing power consumption, in accordance with various aspects of the present disclosure.129025- 2534WO01Qualcomm Ref. No. 2500661WO 28

[0077] In some aspects, a network node may configure cycles associated with the LP-WUS monitoring occasions for the UE by indicating the duration of the LP-WUS monitoring window, the periodicity of the PDCCH monitoring cycle associated with the LP-WUS, the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.

[0078] As shown in FIG. 5, a PDCCH monitoring timeline 500 may be based on one or more configurations provided to the UE. In some aspects, a DRX configuration may indicate one or more parameters of a DRX cycle 530, e.g., as described in connection with FIG. 4A. During the DRX ON durations of the DRX cycle, the UE may monitor for PDCCH with a main radio. In some aspects, a further configuration associated with a LP-WUS may that indicate one or more of the duration of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 502), the periodicity of the PDCCH monitoring cycle associated with (e.g., triggered by) the LP-WUS (e.g., the PDCCH monitoring occasion cycle 504), the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP-WUS (e.g., the PDCCH monitoring occasion start offset 506), and / or the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 508).

[0079] For example, when the UE receives the configuration(s) in accordance with the example in FIG. 5, the UE may be in an RRC connected mode and may receive a configuration with a new timer for PDCCH monitoring (e.g., the PDCCH monitoring occasion triggered by LP-WUS), as stated above. The size of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 502) may be indicated to the UE by a configuration parameter, which may be referred to as LPWUS-duration. Each PDCCH monitoring window's start time, triggered by receiving a LP-WUS during the LP-WUS monitoring occasion, may be indicated to the UE by the configuration parameter (e.g., which may be referred to as LPWUSCycleStartOffset). For example, a PDCCH monitoring window may begin in the subframe determined by [(SFN x 10) + subframe number within system frame] modulo (LPWUSCycle) = LPWUS StartOffset, where SFN is the system frame number, and LPWUSCycle (e.g.,129025- 2534WO01Qualcomm Ref. No. 2500661WO 29 defining the PDCCH monitoring occasion cycle 504) and LPWUS StartOffset (e.g., defining the PDCCH monitoring occasion start offset 506) are configured for the UE by the LPWUSCycleStartOffset parameter. Additionally, an offset parameter, LPWUS-Offset, defining the start of the LP-WUS monitoring window relative to the beginning of the PDCCH monitoring window for PDCCH triggered by the LP-WUS (e.g., the LP-WUS monitoring occasion start offset 508) may also be configured for the UE, e.g., indicated to the UE by the network node.

[0080] According to the PDCCH monitoring configuration, the UE may determine the start of the PDCCH monitoring occasion / window associated with the LP-WUS 510 based on the periodicity of the PDCCH monitoring cycle associated with the LP-WUS (e.g., the PDCCH monitoring occasion cycle 504) and the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP-WUS (e.g., the PDCCH monitoring occasion start offset 506). The UE may determine the start of the LP-WUS monitoring occasion / window 512 relative to the start of the PDCCH monitoring occasion / window associated with the LP-WUS 510, e.g., based on the start of the PDCCH monitoring occasion / window associated with the LP-WUS 510, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 508).

[0081] In some aspects, DRX cycles associated with the LP-WUS monitoring occasions may be configured for the UE by the network node indicating, to the UE, the duration of the LP-WUS monitoring window, the start of the PDCCH monitoring window associated with the LP-WUS relative to the end (or expiration) of DRX ON duration timer, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window, in addition to the DRX configuration.

[0082] As shown in FIG. 6, a PDCCH monitoring timeline 600 may be based on one or more configurations provided to the UE. The UE may receive a DRX configuration that indicates one or more parameters of the DRX cycle 630, e.g., as described in connection with FIG. 4A. During the DRX ON durations of the DRX cycle, the UE may monitor for PDCCH with a main radio. In some aspects, the UE may receive a further configuration that indicates the duration of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 602), the start of the PDCCH129025- 2534WO01Qualcomm Ref. No. 2500661WO 30 monitoring window associated with (e.g., triggered by) the LP-WUS relative to the end of DRX ON duration timer (e.g., the PDCCH monitoring occasion start offset 604), and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 606), in addition to the DRX configuration. According to the example in FIG. 6, the duration of the PDCCH monitoring occasion cycle 608 may equal to the duration of the PDCCH monitoring occasion start offset 604.

[0083] For example, when the UE receives a configuration in accordance with the example in FIG. 6, the UE may be in RRC connected mode and may receive a configuration with a new timer for PDCCH monitoring (e.g., the PDCCH monitoring occasion triggered by LP-WUS), as stated above. The size of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 602) may be indicated to the UE by a parameter LPWUS -duration. The example in FIG. 6 is different from the example in FIG. 5, because the duration of the PDCCH monitoring occasion cycle 608 equals to the duration of the PDCCH monitoring occasion start offset 604, each PDCCH monitoring window, triggered by receiving a LP-WUS, may begin at an integer multiple of the LPWUS-pdcch-offset (e.g., defining the PDCCH monitoring occasion start offset 604) from the end of the DRX ON duration, which is the point when the DRX ON duration timer (e.g., drx-OnDurationTimer) expires. Furthermore, a parameter LPWUS-Offset may be used to indicate the start of the LP-WUS monitoring window relative to the beginning of the PDCCH monitoring window (e.g., the LP-WUS monitoring occasion start offset 606).

[0084] According to the example in FIG. 6, the start of the PDCCH monitoring occasion / window associated with the LP-WUS 610 may be indicated to the UE relative to an end of the DRX ON duration, e.g., based on the periodicity of the PDCCH monitoring cycle associated with the LP-WUS (e.g., the duration of the PDCCH monitoring occasion cycle 608 and / or the duration of the PDCCH monitoring occasion start offset 604). The start of the LP-WUS monitoring occasion / window 612 may be indicated to the UE relative to the start of the PDCCH monitoring occasion / window associated with the LP-WUS 610, e.g., based on the start of the PDCCH monitoring occasion / window associated with the LP-WUS 610, and the time difference between the start of the PDCCH monitoring window associated with the129025- 2534WO01Qualcomm Ref. No. 2500661WO 31LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 606).

[0085] In some aspects, DRX cycles associated with the LP-WUS monitoring occasions (e.g., within the DRX OFF duration of the DRX cycle 530 or 630) may be configured by indicating to the UE the start time of the LP-WUS monitoring occasion / window independent from the start of the PDCCH monitoring window associated with the LP- WUS.

[0086] For example, when the UE receives a configuration in accordance with PDCCH configuration timeline 700, the UE may be in RRC connected mode and may receive a configuration with a new timer for PDCCH monitoring (e.g., the PDCCH monitoring occasion triggered by LP-WUS), as stated above. For example, the configuration may provide one or more parameters for the UE to monitor, within a DRX OFF duration of the DRX cycle 730, for the LP-WUS and / or PDCCH monitoring triggered by LP-WUS. The periodicity and the start offset of the LP-WUS monitoring occasion / window may be indicated to the UE by a parameter LPWUSMOCycle StartOffset, independent from the start of the PDCCH monitoring window associated with (e.g., triggered by) the LP-WUS. For example, the LP-WUS monitoring occasion begin in the subframe determined as [(SFN x 10) + subframe number within system frame] modulo (LPWUSMOCycle) = LPWUSMO StartOffset, where SFN is the system frame number, and LPWUSMOCycle (e.g., defining the periodicity of the LP-WUS monitoring occasion) and LPWUSMO StartOffset (e.g., defining the start offset of the LP-WUS monitoring occasion) are configured by parameter LPWUSMOCycleStartOffset. The start of the PDCCH monitoring occasion may be indicated to the UE similarly to PDCCH monitoring configuration described in connection with FIG. 5 and / or FIG. 6, as discussed above.

[0087] Although the LP-WUS monitoring occasion and the PDCCH monitoring occasion are indicated to the UE independently, a minimum offset, LPWUSOffsetZ (e.g., specifying an LP-WUS offset of 704), may be configured. This offset represents the minimum time between the LP-WUS and the start of the current PDCCH monitoring occasion, allowing an LP-WUS 706 to trigger the initiation of the PDCCH monitoring occasion (e.g., PDCCH monitoring occasion A).

[0088] For example, if the UE receives an LP-WUS 705 within the minimum offset (e.g., within the LP-WUS offset of 704), the reception of the LP-WUS may not trigger the129025- 2534WO01Qualcomm Ref. No. 2500661WO 32 start of the current PDCCH monitoring occasion (e.g., PDCCH monitoring occasion A). Instead, the LP-WUS 705 may trigger the UE to monitor for a PDCCH transmission in a subsequence PDCCH monitoring occasion, such as the next available PDCCH monitoring occasion (e.g., PDCCH monitoring occasion B) that meets the minimum offset. In some configurations, the minimum offset may be determined by the capabilities of the UE, such as how quickly the main radio can be activated for PDCCH monitoring in response to receiving the LP-WUS.

[0089] FIG. 8 is a diagram illustrating an example communication flow 800 that includes PDCCH transmission monitoring involving LP-WUS, in accordance with various aspects of the present disclosure. The PDCCH transmission monitoring in the example communication flow 800 may be performed between a UE 802 and a network node 804. In some aspects, the UE 802 may correspond to the UE 104 in FIG. 1, the UE 350 in FIG. 3, or the apparatus 1104 in the hardware implementation of FIG. 11. The network node 804 may correspond to the base station 102 in aggregation and / or by one or more components (e.g., such as a CU 110, a DU 130, and / or an RU 140) in FIG. 1, the base station 310 in aggregation and / or by one or more components in FIG. 3, or the network entity 1202 in the hardware implementation of FIG. 12. In some aspects, the network node 804 may also correspond to a network entity in the core network 120 in FIG. 1 or the apparatus (e.g., 1360) in the hardware implementation of FIG. 13.

[0090] As shown at 806, the network node 804 may transmit to the UE 802 a DRX configuration. For example, the base station may configure DRX parameters for the UE that indicate the DRX cycle, the DRX ON duration and the DRX OFF duration, etc., as discussed with respect to FIG. 4 A. The DRX configuration may correspond to the DRX cycle 530, 630, and / or 730 in any of FIG. 5, FIG. 6, and / or FIG. 7, in some examples. In some aspects, the UE 802 may receive the DRX configuration using the main radio / receiver. Additionally, or alternatively, the network node 804 may schedule communications for the UE based on the UE’s DRX configuration as the network node 804 is aware of the DRX configuration provided to the UE.

[0091] At arrow 808, the network node 804 may transmit an additional configuration (e.g., a LP-WUS monitoring configuration, in addition to the DRX configuration) to the UE 802. In some aspects, the additional configuration may be transmitted based on or comprised in a RRC transmission. In some aspects, the UE 802 may receive the129025- 2534WO01Qualcomm Ref. No. 2500661WO 33 additional configuration may be associated with the LP-WUR of the UE (e.g., 410 in FIG. 4B).

[0092] As stated above, the additional configuration may configure LP-WUS monitoring occasions and PDCCH monitoring occasions triggered by reception of an LP-WUS during the DRX OFF durations of a DRX cycle indicated in the DRX configuration. In some aspects, the LP-WUS monitoring configuration may indicate at least one of a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle, a start of a PDCCH monitoring window associated with the LP-WUS relative to an end of a DRX ON duration, a time difference between the start of a PDCCH monitoring window associated with the LP-WUS and a start time of a LP-WUS monitoring window, or start times of one or more LP-WUS monitoring windows.

[0093] In some aspects, the LP-WUS monitoring configuration may indicate the duration of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 502), the periodicity of the PDCCH monitoring cycle associated with (e.g., triggered by) the LP-WUS (e.g., the PDCCH monitoring occasion cycle 504), the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP-WUS (e.g., the PDCCH monitoring occasion start offset 506), and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 508), as discussed with respect to FIG. 5.

[0094] In some aspects, the LP-WUS monitoring configuration may also indicate the duration of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 602), the start of the PDCCH monitoring window associated with (e.g., triggered by) the LP-WUS relative to the end of DRX ON duration timer (e.g., the PDCCH monitoring occasion start offset 604), and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 606), in addition to the DRX configuration, as discussed with respect to FIG. 6. According to the PDCCH configuration, the duration of the PDCCH monitoring129025- 2534WO01Qualcomm Ref. No. 2500661WO 34 occasion cycle 608 may equal to the duration of the PDCCH monitoring occasion start offset 604.

[0095] In some aspects, the LP-WUS monitoring configuration may further indicate the LP- WUS monitoring occasion / window (e.g., the start time and / or the cycle / periodicity of the LP-WUS monitoring occasion / window) independent from the start of the PDCCH monitoring window associated with the LP-WUS, as discussed with respect to FIG. 7. In some aspects, a minimum offset, LPWUSOffsetZ (e.g., an LP-WUS offset of 704), may be indicated in the additional configuration to specify the minimum time between the LP-WUS and the start of the current PDCCH monitoring occasion, allowing an LP-WUS to trigger the initiation of that PDCCH monitoring occasion (e.g., PDCCH monitoring occasion A in FIG. 7).

[0096] At block 810, the UE 802 may monitor for the PDCCH transmissions from the network node 804 in accordance with the DRX configuration and the additional configuration. The network node 804 may transmit at least one PDCCH transmission in accordance with the DRX configuration or the additional configuration. For example, the UE may monitor for PDCCH transmissions using the first radio during the DRX ON durations (e.g., 532, 632, 732) of the DRX configuration (e.g., 530, 630, 730). In some aspects, the UE 802 may monitor for the LP-WUS with the second radio (e.g., LP-WUR) based on the additional configuration. The UE 802 may monitor for the LP-WUS using the second radio (e.g., LP-WUR) during the DRX OFF duration of the DRX cycle configured by the DRX configuration (e.g., 530, 630, 730). If the UE 802 receives the LP-WUS using the second radio, the UE 802 may monitor for the PDCCH transmissions with the first radio (e.g., the main radio / receiver) in response to reception of the LP-WUS and based on the additional configuration and the DRX configuration.

[0097] FIG. 9 is a flowchart of a method 900 of wireless communication at a UE, in accordance with various aspects of the present disclosure. The UE may correspond to the UE 104 in FIG. 1, the UE 350 in FIG. 3, the UE 802 in FIG. 8, or the apparatus 1104 in the hardware implementation of FIG. 11.

[0098] At 902, the UE may receive a DRX configuration for monitoring PDCCH transmissions with a first radio (e.g., using the main radio / receiver). In some aspects, the DRX configuration may be configured as discussed with respect to FIG. 4A. In129025- 2534WO01Qualcomm Ref. No. 2500661WO 35 some aspects, 902 may be performed by the PDCCH transmission monitoring component 198.

[0099] At 904, the UE may receive an additional configuration associated with a LP-WUS and a second radio (e.g., using the LP-WUR). In some aspects, the additional configuration indicating at least one of a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle, a start of a PDCCH monitoring window associated with the LP- WUS relative to an end of a DRX ON duration, a time difference between the start of a PDCCH monitoring window associated with the LP-WUS and a start time of a LP- WUS monitoring window, or start times of one or more LP-WUS monitoring windows.

[0100] As discussed above, in some aspects, the LP-WUS monitoring configuration may indicate the duration of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 502), the periodicity of the PDCCH monitoring cycle associated with (e.g., triggered by) the LP-WUS (e.g., the PDCCH monitoring occasion cycle 504), the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP-WUS (e.g., the PDCCH monitoring occasion start offset 506), and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 508), as discussed with respect to FIG. 5.

[0101] In some aspects, the LP-WUS monitoring configuration may also indicate the duration of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 602), the start of the PDCCH monitoring window associated with (e.g., triggered by) the LP-WUS relative to the end of DRX ON duration timer (e.g., the PDCCH monitoring occasion start offset 604), and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 606), in addition to the DRX configuration, as discussed with respect to FIG. 6. According to the PDCCH configuration, the duration of the PDCCH monitoring129025- 2534WO01Qualcomm Ref. No. 2500661WO 36 occasion cycle 608 may equal to the duration of the PDCCH monitoring occasion start offset 604.

[0102] In some aspects, the LP-WUS monitoring configuration may further indicate the LP- WUS monitoring occasion / window (e.g., the start time and / or the cycle / periodicity of the LP-WUS monitoring occasion / window) independent from the start of the PDCCH monitoring window associated with the LP-WUS, as discussed with respect to FIG. 7. In some aspects, a minimum offset, LPWUSOffsetZ (e.g., an LP-WUS offset of 704), may be indicated in the additional configuration to specify the minimum time between the LP-WUS and the start of the current PDCCH monitoring occasion, allowing an LP-WUS to trigger the initiation of that PDCCH monitoring occasion (e.g., PDCCH monitoring occasion A in FIG. 7).

[0103] In some aspects, the additional configuration may be transmitted based on a RRC transmission. In some aspects, 904 may be performed by the PDCCH transmission monitoring component 198.

[0104] At 906, the UE may monitor for the PDCCH transmissions in accordance with the DRX configuration and the additional configuration. In some aspects, the UE 802 may monitor for the LP-WUS with the second radio based on the additional configuration, and may monitor for the PDCCH transmissions with the first radio in response to reception of the LP-WUS and based on the additional configuration and the DRX configuration. In some aspects, 906 may be performed by the PDCCH transmission monitoring component 198.

[0105] FIG. 10 is a flowchart of a method 1000 of wireless communication at a network node, in accordance with various aspects of the present disclosure. The network node may correspond to the base station 102 in aggregation and / or by one or more components (e.g., such as a CU 110, a DU 130, and / or an RU 140) in FIG. 1, the base station 310 in aggregation and / or by one or more components in FIG. 3, the network node 804 in FIG. 8, or the network entity 1202 in the hardware implementation of FIG. 12. In some aspects, the network node may also correspond to a network entity in the core network 120 in FIG. 1, or the apparatus (e.g., 1360) in the hardware implementation of FIG. 13.

[0106] At 1002, the network node may transmit a DRX for a UE to monitoring PDCCH transmissions with a first radio (e.g., the main radio / receiver). In some aspects, the129025- 2534WO01Qualcomm Ref. No. 2500661WO 37DRX configuration may be configured as discussed with respect to FIG. 4A. In some aspects, 1002 may be performed by the PDCCH transmission component 199.

[0107] At 1004, the network node may transmit an additional configuration associated with a LP-WUS and a second radio (e.g., the LP-WUR) of the UE. In some aspects, the additional configuration indicating at least one of 1. a duration of an LP-WUS monitoring window for the LP-WUS, 2. a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, 3. a time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle, 4. a start of a PDCCH monitoring window associated with the LP-WUS relative to an end of a DRX ON duration, 5. a time difference between the start of a PDCCH monitoring window associated with the LP- WUS and a start time of a LP-WUS monitoring window, or 6. start times of one or more LP-WUS monitoring windows.

[0108] As discussed above, in some aspects, the LP-WUS monitoring configuration may indicate the duration of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 502), the periodicity of the PDCCH monitoring cycle associated with (e.g., triggered by) the LP-WUS (e.g., the PDCCH monitoring occasion cycle 504), the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP-WUS (e.g., the PDCCH monitoring occasion start offset 506), and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 508), as discussed with respect to FIG. 5.

[0109] In some aspects, the LP-WUS monitoring configuration may also indicate the duration of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion duration 602), the start of the PDCCH monitoring window associated with (e.g., triggered by) the LP-WUS relative to the end of DRX ON duration timer (e.g., the PDCCH monitoring occasion start offset 604), and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window (e.g., the LP-WUS monitoring occasion start offset 606), in addition to the DRX configuration, as discussed with respect to FIG. 6. According to the PDCCH configuration, the duration of the PDCCH monitoring129025- 2534WO01Qualcomm Ref. No. 2500661WO 38 occasion cycle 608 may equal to the duration of the PDCCH monitoring occasion start offset 604.

[0110] In some aspects, the LP-WUS monitoring configuration may further indicate the LP- WUS monitoring occasion / window (e.g., the start time and / or the cycle / periodicity of the LP-WUS monitoring occasion / window) independent from the start of the PDCCH monitoring window associated with the LP-WUS, as discussed with respect to FIG. 7. In some aspects, a minimum offset, LPWUSOffsetZ (e.g., an LP-WUS offset of 704), may be indicated in the additional configuration to specify the minimum time required before the start of the current PDCCH monitoring occasion (e.g., between the LP-WUS and the PDCCH monitoring occasion), to allow the LP-WUS to trigger the initiation of that PDCCH monitoring occasion (e.g., PDCCH monitoring occasion A in FIG. 7).[OHl] In some aspects, the additional configuration may be transmitted based on a RRC transmission. In some aspects, 1004 may be performed by the PDCCH transmission component 199.

[0112] At 1006, the network node may transmit at least one PDCCH transmission in accordance with the DRX configuration or the additional configuration. In some aspects, according to the configurations, the UE 802 may monitor for the LP-WUS with the second radio based on the additional configuration, and may monitor for the PDCCH transmissions with the first radio in response to reception of the LP-WUS and based on the additional configuration and the DRX configuration. In some aspects, 1006 may be performed by the PDCCH transmission component 199.

[0113] FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for an apparatus 1104. The apparatus 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatusl 104 may include at least one cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., cellular RF transceiver). The cellular baseband processor(s) 1124 may include at least one on-chip memory 1124'. In some aspects, the apparatus 1104 may further include one or more subscriber identity modules (SIM) cards 1120 and at least one application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor(s) 1106 may include on-chip memory 1106'. In some aspects, the apparatus 1104 may further include a Bluetooth module 1112, a WLAN module 1114, an SPS module 1116 (e.g.,129025- 2534WO01Qualcomm Ref. No. 2500661WO 39GNSS module), one or more sensor modules 1118 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial measurement unit (IMU), gyroscope, and / or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and / or other technologies used for positioning), additional memory modules 1126, a power supply 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include their own dedicated antennas and / or utilize the antennas 1180 for communication. The cellular baseband processor(s) 1124 communicates through the transceiver(s) 1122 via one or more antennas 1180 with the UE 104 and / or with an RU associated with a network entity 1102. The cellular baseband processor(s) 1124 and the application processor(s) 1106 may each include a computer-readable medium / memory 1124', 1106', respectively. The additional memory modules 1126 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1124', 1106', 1126 may be non -transitory. The cellular baseband processor(s) 1124 and the application processor(s) 1106 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor(s) 1124 / application processor(s) 1106, causes the cellular baseband processor(s) 1124 / application processor(s) 1106 to perform the various functions described supra. The cellular baseband processor(s) 1124 and the application processor(s) 1106 are configured to perform the various functions described supra based at least in part of the information stored in the memory. That is, the cellular baseband processor(s) 1124 and the application processor(s) 1106 may be configured to perform a first subset of the various functions described supra without information stored in the memory and may be configured to perform a second subset of the various functions described supra based on the information stored in the memory. The computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor(s) 1124 / application processor(s) 1106 when executing software. The cellular baseband processor(s) 1124 / application processor(s) 1106 may be a component of the UE 350 and may include the at least one memory 360 and / or at least one of the TX processor129025- 2534WO01Qualcomm Ref. No. 2500661WO 40368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1104 may be at least one processor chip (modem and / or application) and include just the cellular baseband processor(s) 1124 and / or the application processor(s) 1106, and in another configuration, the apparatus 1104 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 1104.

[0114] As discussed supra, the PDCCH transmission monitoring component 198 may be configured to receive a DRX configuration for monitoring PDCCH transmissions with a first radio (e.g., using the main radio / receiver), receive an additional configuration associated with a LP-WUS and a second radio (e.g., using the LP- WUR), and monitor for the PDCCH transmissions in accordance with the DRX configuration and the additional configuration. The PDCCH transmission monitoring component 198, and / or the apparatus may be further configured to perform any of the aspects described in connection with the flowchart in FIG. 9 and / or performed by the UE in the communication flow in FIG. 8. The PDCCH transmission monitoring component 198 may be within the cellular baseband processor(s) 1124, the application processor(s) 1106, or both the cellular baseband processor(s) 1124 and the application processor(s) 1106. The component 198 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within 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 stated processes / algorithm individually or in combination. As shown, the apparatus 1104 may include a variety of components configured for various functions. In one configuration, the apparatus 1104, and in particular the cellular baseband processor(s) 1124 and / or the application processor(s) 1106, may include means for receiving a DRX configuration for monitoring PDCCH transmissions with a first radio (e.g., using the main radio / receiver), receiving an additional configuration associated with a LP-WUS and a second radio (e.g., using the LP-WUR), and monitoring for the PDCCH transmissions in accordance with the DRX configuration and the additional configuration. The apparatus may further include means for performing any of the aspects described in connection with the flowchart in FIG. 9 and / or performed by the129025- 2534WO01Qualcomm Ref. No. 2500661WO 41UE in the communication flow in FIG. 8. The means may be the component 198 of the apparatus 1104 configured to perform the functions recited by the means. As described supra, the apparatus 1104 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0115] FIG. 12 is a diagram 1200 illustrating an example of a hardware implementation for a network entity 1202. The network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1202 may include at least one of a CU 1210, a DU 1230, or an RU 1240. For example, depending on the layer functionality handled by the component 199, the network entity 1202 may include the CU 1210; both the CU 1210 and the DU 1230; each of the CU 1210, the DU 1230, and the RU 1240; the DU 1230; both the DU 1230 and the RU 1240; or the RU 1240. The CU 1210 may include at least one CU processor 1212. The CU processor(s) 1212 may include on-chip memory 1212'. In some aspects, the CU 1210 may further include additional memory modules 1214 and a communications interface 1218. The CU 1210 communicates with the DU 1230 through a midhaul link, such as an Fl interface. The DU 1230 may include at least one DU processor 1232. The DU processor(s) 1232 may include on-chip memory 1232'. In some aspects, the DU 1230 may further include additional memory modules 1234 and a communications interface 1238. The DU 1230 communicates with the RU 1240 through a fronthaul link. The RU 1240 may include at least one RU processor 1242. The RU processor(s) 1242 may include on-chip memory 1242'. In some aspects, the RU 1240 may further include additional memory modules 1244, one or more transceivers 1246, antennas 1280, and a communications interface 1248. The RU 1240 communicates with the UE 104. The on-chip memory 1212', 1232', 1242' and the additional memory modules 1214, 1234, 1244 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1212, 1232, 1242 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(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium / 129025- 2534WO01Qualcomm Ref. No. 2500661WO 42 memory may also be used for storing data that is manipulated by the processor(s) when executing software.

[0116] As discussed supra, the PDCCH transmission component 199 may be configured to transmit a DRX configuration for a UE to monitoring PDCCH transmissions with a first radio (e.g., using the main radio / receiver), transmit an additional configuration associated with a LP-WUS and a second radio (e.g., the LP-WUR) of the UE, and may transmit at least one PDCCH transmission in accordance with the DRX configuration or the additional configuration. The PDCCH transmission component 199 may be further configured to perform any of the aspects described in connection with the flowchart in FIG. 10 and / or performed by the network node in the communication flow in FIG. 8. The PDCCH transmission component 199 may be within one or more processors of one or more of the CU 1210, DU 1230, and the RU 1240. The PDCCH transmission component 199 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within 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 stated processes / algorithm individually or in combination. The network entity 1202 may include a variety of components configured for various functions. In one configuration, the network entity 1202 may include means for transmitting a DRX for a UE to monitoring PDCCH transmissions with a first radio (e.g., using the main radio / receiver), transmitting an additional configuration associated with a LP-WUS and a second radio (e.g., the LP- WUR) of the UE, and transmitting at least one PDCCH transmission in accordance with the DRX configuration or the additional configuration. The network entity may further include means for performing any of the aspects described in connection with FIG. 10 and / or performed by the network node in FIG. 8. The means may be the PDCCH transmission component 199 of the network entity 1202 configured to perform the functions recited by the means. As described supra, the network entity 1202 may include the TX processor 316, the RX processor 370, and the controller / processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.129025- 2534WO01Qualcomm Ref. No. 2500661WO 43

[0117] FIG. 13 is a diagram 1300 illustrating an example of a hardware implementation for a network entity 1360. In one example, the network entity 1360 may be within the core network 120. The network entity 1360 may include at least one network processor 1312. The network processor(s) 1312 may include on-chip memory 1312'. In some aspects, the network entity 1360 may further include additional memory modules 1314. The network entity 1360 communicates via the network interface 1380 directly (e.g., backhaul link) or indirectly (e.g., through a RIC) with the CU 1302. The on-chip memory 1312' and the additional memory modules 1314 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The network processor(s) 1312 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(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) when executing software.

[0118] As discussed supra, the PDCCH transmission component 199 may be configured to transmit a DRX for a UE to monitoring PDCCH transmissions with a first radio (e.g., using the main radio / receiver), transmit an additional configuration associated with a LP-WUS and a second radio (e.g., the LP-WUR) of the UE, and may transmit at least one PDCCH transmission in accordance with the DRX configuration or the additional configuration. The PDCCH transmission component 199 may be within the network processor(s) 1312. The PDCCH transmission component 199 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within 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 stated processes / algorithm individually or in combination. The network entity 1360 may include a variety of components configured for various functions. In one configuration, the network entity 1360 may include means for transmitting a DRX for a UE to monitoring PDCCH transmissions with a first radio (e.g., using the main radio / receiver), transmitting an additional configuration associated with a LP-WUS and a second radio (e.g., the LP-WUR) of the UE, and transmitting at least one129025- 2534WO01Qualcomm Ref. No. 2500661WO 44PDCCH transmission in accordance with the DRX configuration or the additional configuration. The means may be the PDCCH transmission component 199 of the network entity 1360 configured to perform the functions recited by the means.

[0119] Allowing the UE to monitor for PDCCH transmissions during the DRX OFF duration using less power consuming monitoring schemes (e.g., configuring LP-WUS triggered PDCCH monitoring), without waiting for the next DRX ON duration, the aspects presented herein can improve monitoring efficiency, reduce latency, and optimize power consumption for a UE.

[0120] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

[0121] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of129025- 2534WO01Qualcomm Ref. No. 2500661WO 45A, 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 A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. A processor may be referred to as processor circuitry. A memory / memory module may be referred to as memory circuitry. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received / transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data or “provide” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and / or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

[0122] As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor,129025- 2534WO01Qualcomm Ref. No. 2500661WO 46 or the like) shall be construed as “based at least on A” unless specifically recited differently.

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

[0124] Aspect 1 is a method of wireless communication at a UE, comprising receiving a discontinuous reception (DRX) configuration for monitoring physical downlink control channel (PDCCH) transmissions with a first radio; receiving an additional configuration associated with a low power-wake up signal (LP-WUS) and a second radio, wherein the additional configuration indicating at least one of a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle, a start of a PDCCH monitoring window associated with the LP-WUS relative to an end of a DRX ON duration, a time difference between the start of a PDCCH monitoring window associated with the LP- WUS and a start time of a LP-WUS monitoring window , or start times of one or more LP-WUS monitoring windows; and monitoring for the PDCCH transmissions in accordance with the DRX configuration and the additional configuration.

[0125] Aspect 2 is the method of aspect 1, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the periodicity of the PDCCH monitoring cycle associated with the LP-WUS, the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window, wherein the start of the PDCCH monitoring window associated with the LP- WUS is determined based on the periodicity of the PDCCH monitoring cycle associated with the LP-WUS and the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP- WUS.

[0126] Aspect 3 is the method of aspect 1, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the start of the PDCCH monitoring window associated with the LP-WUS relative to the end of DRX ON duration timer,129025- 2534WO01Qualcomm Ref. No. 2500661WO 47 and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.

[0127] Aspect 4 is the method of any of aspects 1 to 3, wherein the start time of the LP-WUS monitoring window is determined based on: the start of the PDCCH monitoring window associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.

[0128] Aspect 5 is the method of aspect 1, wherein the additional configuration indicates the start time of the LP-WUS monitoring window independent from the start of the PDCCH monitoring window associated with the LP-WUS.

[0129] Aspect 6 is the method of any of aspects 1 or 5, wherein monitoring for the PDCCH transmissions in accordance with the additional configuration comprises: initiating the PDCCH monitoring window in response to receiving a LP-WUS at least a predetermined time before the start of the PDCCH monitoring window.

[0130] Aspect 7 is the method of any of aspects 1 to 6, wherein monitoring for the PDCCH transmissions in accordance with the additional configuration comprises: initiating the PDCCH monitoring window associated with the LP-WUS in response to receiving the LP-WUS.

[0131] Aspect 8 is the method of any of aspects 1 to 7, wherein monitoring for the PDCCH transmissions in accordance with the additional configuration comprises: monitoring for the LP-WUS with the second radio based on the additional configuration; and monitoring for the PDCCH transmissions with the first radio in response to reception of the LP-WUS and based on the additional configuration and the DRX configuration.

[0132] Aspect 9 is the method of any of aspects 1 to 8, wherein the DRX configuration indicates DRX ON durations and DRX OFF durations, and wherein the additional configuration corresponds to the DRX OFF durations.

[0133] Aspect 10 is the method of any of aspects 1 to 9, wherein the additional configuration is indicated in a radio resource control (RRC) transmission.

[0134] Aspect 11 is the method of any of aspects 1 to 10, wherein the LP-WUS comprises an on-off keying (OOK) waveform.

[0135] Aspect 12 is the method of any of aspects 1 to 11, wherein the additional configuration indicates the duration of the LP-WUS monitoring window for the LP-WUS.129025- 2534WO01Qualcomm Ref. No. 2500661WO 48

[0136] Aspect 12 is the method of any of aspects 1 to 11, wherein the additional configuration indicates the periodicity of the PDCCH monitoring cycle.

[0137] Aspect 13 is the method of any of aspects 1 to 12, wherein the additional configuration indicates the PDCCH monitoring cycle including the PDCCH monitoring window associated with the LP-WUS.

[0138] Aspect 14 is the method of any of aspects 1 to 13, wherein the additional configuration indicates the time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle.

[0139] Aspect 15 is the method of any of aspects 1 to 14, wherein the additional configuration indicates the start of the PDCCH monitoring window associated with the LP-WUS relative to the end of the DRX ON duration.

[0140] Aspect 16 is the method of any of aspects 1 to 15, wherein the additional configuration indicates the time difference between the start of the PDCCH monitoring window associated with the LP-WUS.

[0141] Aspect 17 is the method of any of aspects 1 to 16, wherein the additional configuration indicates the start time of LP-WUS monitoring window.

[0142] Aspect 18 is the method of any of aspects 1 to 17, wherein the additional configuration indicates the start times of one or more LP-WUS monitoring windows.

[0143] Aspect 19 is an apparatus for wireless communication at UE, comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 1 to 18.

[0144] Aspect 20 is an apparatus for wireless communication at a UE, comprising means for performing each step in the method of any of aspects 1 to 18.

[0145] Aspect 21 is the apparatus of any of aspects 19 or 20, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 1 to 18.

[0146] Aspect 22 is a computer-readable medium (e.g., non-transitory) storing computer executable code at a UE, the code when executed by at least one processor causes the at least one processor to perform the method of any of aspects 1 to 18.

[0147] Aspect 23 is a method of wireless communication at a network node, comprising transmitting a discontinuous reception (DRX) configuration for a user equipment (UE) to monitoring physical downlink control channel (PDCCH) transmissions with129025- 2534WO01Qualcomm Ref. No. 2500661WO 49 a first radio; and transmitting an additional configuration associated with a low powerwake up signal (LP-WUS) and a second radio of the UE, wherein the additional configuration indicating at least one of a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle, a start of a PDCCH monitoring window associated with the LP- WUS relative to an end of a DRX ON duration, a time difference between the start of a PDCCH monitoring window associated with the LP-WUS and a start time of a LP- WUS monitoring window, or start times of one or more LP-WUS monitoring windows; and transmitting at least one PDCCH transmission in accordance with the DRX configuration or the additional configuration.

[0148] Aspect 24 is the method of aspect 23, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the periodicity of the PDCCH monitoring cycle associated with the LP-WUS, the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window, wherein the start of the PDCCH monitoring window associated with the LP- WUS is determined based on the periodicity of the PDCCH monitoring cycle associated with the LP-WUS and the time offset defining the PDCCH monitoring window relative to the start of PDCCH monitoring cycle associated with the LP- WUS.

[0149] Aspect 25 is the method of aspect 23, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the start of the PDCCH monitoring window associated with the LP-WUS relative to the end of DRX ON duration timer, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.

[0150] Aspect 26 is the method of any of aspects 23 to 25, wherein the start time of the LP- WUS monitoring window is determined based on: the start of the PDCCH monitoring window associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.129025- 2534WO01Qualcomm Ref. No. 2500661WO 50

[0151] Aspect 27 is the method of aspect 23, wherein the additional configuration indicates the start time of the LP-WUS monitoring window independent from the start of the PDCCH monitoring window associated with the LP-WUS.

[0152] Aspect 28 is the method of any of aspects 23 to 27, wherein the DRX configuration indicates DRX ON durations and DRX OFF durations, and wherein the additional configuration corresponds to the DRX OFF durations.

[0153] Aspect 29 is the method of any of aspects 23 to 28, wherein the additional configuration indicates the duration of the LP-WUS monitoring window for the LP- WUS.

[0154] Aspect 30 is the method of any of aspects 23 to 29, wherein the additional configuration indicates the periodicity of the PDCCH monitoring cycle.

[0155] Aspect 31 is the method of any of aspects 23 to 30, wherein the additional configuration indicates the PDCCH monitoring cycle including the PDCCH monitoring window associated with the LP-WUS.

[0156] Aspect 32 is the method of any of aspects 23 to 31, wherein the additional configuration indicates the time offset defining a PDCCH monitoring window relative to the start of PDCCH monitoring cycle.

[0157] Aspect 33 is the method of any of aspects 23 to 32, wherein the additional configuration indicates the start of the PDCCH monitoring window associated with the LP-WUS relative to the end of the DRX ON duration.

[0158] Aspect 34 is the method of any of aspects 23 to 33, wherein the additional configuration indicates the time difference between the start of the PDCCH monitoring window associated with the LP-WUS.

[0159] Aspect 35 is the method of any of aspects 23 to 34, wherein the additional configuration indicates the start time of LP-WUS monitoring window.

[0160] Aspect 36 is the method of any of aspects 23 to 35, wherein the additional configuration indicates the start times of one or more LP-WUS monitoring windows.

[0161] Aspect 37 is an apparatus for wireless communication at a network node, comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 23 to 36.

[0162] Aspect 38 is an apparatus for wireless communication at a network node, comprising means for performing each step in the method of any of aspects 23 to 36.129025- 2534WO01Qualcomm Ref. No. 2500661WO 51

[0163] Aspect 39 is the apparatus of any of aspects 37 or 38, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 23 to 36.

[0164] Aspect 40 is a computer-readable medium (e.g., non-transitory) storing computer executable code at a network node, the code when executed by at least one processor causes the at least one processor to perform the method of any of aspects 23 to 36.129025- 2534WO01

Claims

Qualcomm Ref. No. 2500661WO 52WHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a user equipment (UE), comprising: memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to: receive a discontinuous reception (DRX) configuration to monitor for physical downlink control channel (PDCCH) transmissions with a first radio; receive an additional configuration associated with a low power-wake up signal (LP-WUS) and a second radio, wherein the additional configuration indicating at least one of: a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining the PDCCH monitoring window relative to a start of the PDCCH monitoring cycle, a start of the PDCCH monitoring window associated with the LP-WUS relative to an end of a DRX ON duration, a time difference between the start of the PDCCH monitoring window associated with the LP-WUS and a start time of the LP-WUS monitoring window, or start times of one or more LP-WUS monitoring windows; and monitor for the PDCCH transmissions in accordance with the DRX configuration and the additional configuration.

2. The apparatus of claim 1, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the periodicity of the PDCCH monitoring cycle associated with the LP-WUS, the time offset defining the PDCCH monitoring window relative to the start of the PDCCH monitoring cycle associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window,129025- 2534WO01Qualcomm Ref. No. 2500661WO 53 wherein the start of the PDCCH monitoring window associated with the LP-WUS is determined based on the periodicity of the PDCCH monitoring cycle associated with the LP-WUS and the time offset defining the PDCCH monitoring window relative to the start of the PDCCH monitoring cycle associated with the LP-WUS.

3. The apparatus of claim 1, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the start of the PDCCH monitoring window associated with the LP-WUS relative to the end of DRX ON duration timer, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.

4. The apparatus of claim 1, wherein the start time of the LP-WUS monitoring window is determined based on: the start of the PDCCH monitoring window associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.

5. The apparatus of claim 1, wherein the additional configuration indicates the start time of the LP-WUS monitoring window independent from the start of the PDCCH monitoring window associated with the LP-WUS.

6. The apparatus of claim 5, wherein to monitor for the PDCCH transmissions in accordance with the additional configuration, the at least one processor is configured to: initiate the PDCCH monitoring window in response to receiving the LP-WUS at least a predetermined time before the start of the PDCCH monitoring window.

7. The apparatus of claim 1, wherein to monitor for the PDCCH transmissions in accordance with the additional configuration, the at least one processor is configured to: initiate the PDCCH monitoring window associated with the LP-WUS in response to receiving the LP-WUS.129025- 2534WO01Qualcomm Ref. No. 2500661WO 548. The apparatus of claim 1, wherein to monitor for the PDCCH transmissions in accordance with the additional configuration, the at least one processor is configured to: monitor for the LP-WUS with the second radio based on the additional configuration; and monitor for the PDCCH transmissions with the first radio in response to reception of the LP-WUS and based on the additional configuration and the DRX configuration.

9. The apparatus of claim 1, wherein the DRX configuration indicates DRX ON durations and DRX OFF durations, wherein the additional configuration corresponds to the DRX OFF durations and is indicated in a radio resource control (RRC) transmission, and wherein the LP-WUS comprises an on-off keying (OOK) waveform.

10. The apparatus of claim 1, wherein the additional configuration indicates the duration of the LP-WUS monitoring window for the LP-WUS.

11. The apparatus of claim 1, wherein the additional configuration indicates the time difference between the start of the PDCCH monitoring window associated with the LP- WUS and the start time of the LP-WUS monitoring window.

12. The apparatus of claim 1, wherein the additional configuration indicates the start times of the one or more LP-WUS monitoring windows.

13. An apparatus for wireless communication at a network node, comprising: memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to: transmit a discontinuous reception (DRX) configuration for a user equipment (UE) to monitor for physical downlink control channel (PDCCH) transmissions with a first radio of the UE; and transmit an additional configuration associated with a low power-wake up signal (LP-WUS) and a second radio of the UE, wherein the additional configuration indicating at least one of: a duration of an LP-WUS monitoring window for the LP-WUS,129025- 2534WO01Qualcomm Ref. No. 2500661WO 55 a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining the PDCCH monitoring window relative to a start of the PDCCH monitoring cycle, a start of the PDCCH monitoring window associated with the LP- WUS relative to an end of a DRX ON duration, a time difference between the start of the PDCCH monitoring window associated with the LP-WUS and a start time of the LP-WUS monitoring window, or start times of one or more LP-WUS monitoring windows; and transmit at least one PDCCH transmission in accordance with the DRX configuration or the additional configuration.

14. The apparatus of claim 13, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the periodicity of the PDCCH monitoring cycle associated with the LP-WUS, the time offset defining the PDCCH monitoring window relative to the start of the PDCCH monitoring cycle associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window, wherein the start of the PDCCH monitoring window associated with the LP-WUS is determined based on the periodicity of the PDCCH monitoring cycle associated with the LP-WUS and the time offset defining the PDCCH monitoring window relative to the start of the PDCCH monitoring cycle associated with the LP-WUS.

15. The apparatus of claim 13, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the start of the PDCCH monitoring window associated with the LP-WUS relative to the end of DRX ON duration timer, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.129025- 2534WO01Qualcomm Ref. No. 2500661WO 5616. The apparatus of claim 13, wherein the start time of the LP-WUS monitoring window is determined based on: the start of the PDCCH monitoring window associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window.

17. The apparatus of claim 13, wherein the additional configuration indicates the start time of the LP-WUS monitoring window independent from the start of the PDCCH monitoring window associated with the LP-WUS.

18. The apparatus of claim 13, wherein the DRX configuration indicates DRX ON durations and DRX OFF durations, and wherein the additional configuration corresponds to the DRX OFF durations.

19. A method of wireless communication of a user equipment (UE), comprising: receiving a discontinuous reception (DRX) configuration for monitoring physical downlink control channel (PDCCH) transmissions with a first radio; receiving an additional configuration associated with a low power-wake up signal (LP-WUS) and a second radio, wherein the additional configuration indicating at least one of: a duration of an LP-WUS monitoring window for the LP-WUS, a periodicity of a PDCCH monitoring cycle, the PDCCH monitoring cycle including a PDCCH monitoring window associated with the LP-WUS, a time offset defining the PDCCH monitoring window relative to a start of the PDCCH monitoring cycle, a start of the PDCCH monitoring window associated with the LP-WUS relative to an end of a DRX ON duration, a time difference between the start of the PDCCH monitoring window associated with the LP-WUS and a start time of the LP-WUS monitoring window, or start times of one or more LP-WUS monitoring windows; and monitoring for the PDCCH transmissions in accordance with the DRX configuration and the additional configuration.129025- 2534WO01Qualcomm Ref. No. 2500661WO 5720. The method of claim 19, wherein the additional configuration indicates: the duration of the LP-WUS monitoring window, the periodicity of the PDCCH monitoring cycle associated with the LP-WUS, the time offset defining the PDCCH monitoring window relative to the start of the PDCCH monitoring cycle associated with the LP-WUS, and the time difference between the start of the PDCCH monitoring window associated with the LP-WUS and the start time of the LP-WUS monitoring window, wherein the start of the PDCCH monitoring window associated with the LP-WUS is determined based on the periodicity of the PDCCH monitoring cycle associated with the LP-WUS and the time offset defining the PDCCH monitoring window relative to the start of the PDCCH monitoring cycle associated with the LP-WUS.129025- 2534WO01