IL309189A

IL309189A - Wake-up signal using a low-power wake-up receiver

Info

Publication number: IL309189A
Application number: IL309189A
Authority: IL
Inventors: Hemant Saggar; Igor Gutman; Tao Luo; Sony Akkarakaran
Original assignee: Qualcomm Inc; Hemant Saggar; Igor Gutman; Tao Luo; Sony Akkarakaran
Priority date: 2023-12-07
Filing date: 2023-12-07
Publication date: 2025-07-01
Also published as: WO2025122239A1

Description

WAKE-UP SIGNALING USING A LOW POWER WAKE-UP RECEIVER FIELD OF THE DISCLOSURE [0001] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for wake-up signaling using a low power wake-up receiver. BACKGROUND [0002] Wireless communication systems are widely deployed to provide various services that may include carrying voice, text, messaging, video, data, and/or other traffic. The services may include unicast, multicast, and/or broadcast services, among other examples. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and/or device transmit power, among other examples). Examples of such multiple-access RATs 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. [0003] The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR). NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (IoT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication), massive multiple-input multiple-output (MIMO), disaggregated network architectures and network topology expansions, multiple-subscriber implementations, high-precision positioning, and/or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution. SUMMARY [0004] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include monitoring for an activation signal during an active duration of a connected mode discontinuous reception (CDRX) cycle, where the monitoring is performed using a using a low-power receiver (LR) of the UE. The method may include receiving the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal. The method may include causing a main radio (MR) of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal. [0005] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a signal including an indication of a wake-up level at which an MR of the UE is to operate, where the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and where each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states. The method may include causing the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. [0006] Some aspects described herein relate to a UE for wireless communication. The user equipment may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to monitor for an activation signal during an active duration of a CDRX cycle, where the monitoring is performed using a using an LR of the UE. The one or more processors may be configured to receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal. The one or more processors may be configured to cause an MR of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal. id="p-7" id="p-7" id="p-7" id="p-7" id="p-7"

[0007] Some aspects described herein relate to a UE for wireless communication. The user equipment may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive a signal including an indication of a wake-up level at which an MR of the UE is to operate, where the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and where each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states. The one or more processors may be configured to cause the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. [0008] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to monitor for an activation signal during an active duration of a CDRX cycle, where the monitoring is performed using a using an LR of the UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal. The set of instructions, when executed by one or more processors of the UE, may cause the UE to cause an MR of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal. [0009] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a signal including an indication of a wake-up level at which an MR of the UE is to operate, where the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and where each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states. The set of instructions, when executed by one or more processors of the UE, may cause the UE to cause the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. id="p-10" id="p-10" id="p-10" id="p-10" id="p-10"

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for monitoring for an activation signal during an active duration of a CDRX cycle, where the monitoring is performed using a using an LR of the apparatus. The apparatus may include means for receiving the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal. The apparatus may include means for causing an MR of the apparatus to move from a first sleep state to a second sleep state based at least in part on the activation signal. [0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a signal including an indication of a wake-up level at which an MR of the apparatus is to operate, where the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and where each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states. The apparatus may include means for causing the MR of the apparatus to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. [0012] Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and/or processing system as substantially described with reference to, and as illustrated by, the specification and accompanying drawings. [0013] The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS [0014] The appended drawings illustrate some aspects of the present disclosure, but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements. [0015] Fig. 1 is a diagram illustrating an example of a wireless communication network, in accordance with the present disclosure. [0016] Fig. 2 is a diagram illustrating an example network node in communication with an example user equipment (UE) in a wireless network, in accordance with the present disclosure. [0017] Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure. [0018] Fig. 4 is a diagram illustrating an example of a low power wake-up receiver (LR or LP-WUR) and a low-power wake-up signal (LP-WUS), in accordance with the present disclosure. [0019] Fig. 5 is a diagram illustrating an example of a discontinuous reception (DRX) configuration, in accordance with the present disclosure. [0020] Figs. 6A-6D are diagrams illustrating examples associated with LR-aided connected mode DRX (CDRX) active state operation, in accordance with the present disclosure. [0021] Figs. 7A-7G are diagrams illustrating examples associated with a multi-level wake-up indication using an LR, in accordance with the present disclosure. [0022] Fig. 8 is a diagram illustrating an example process performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. [0023] Fig. 9 is a diagram illustrating an example process performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. [0024] Fig. 10 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure. DETAILED DESCRIPTION [0025] Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and/or functionalities in addition to or other than the structures and/or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim. [0026] Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, apparatuses, and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. [0027] A user equipment (UE) may be configured with a low power wake-up receiver (LR or LP-WUR) and a main radio (MR) (herein referred to as an LR+MR architecture). In general, an LR is a radio that consumes less power than an MR. The LR may be a separate radio from the MR or, in some scenarios, may comprise a subset of components of the MR. One key feature of an LR is that the LR can monitor for a wake-up signal (WUS) with a reduced power consumption (e.g., in a range from 10 times less power to 100 times less power) as compared to the MR through a combination of wake-up signal design and the use of simplified hardware components for the LR. In some systems, a low power wake-up signal (LP-WUS) may be configured to enable the LR to monitor while consuming significantly less energy consumption as compared to having the MR monitor for a physical downlink control channel (PDCCH)-based WUS. [0028] The LR+MR architecture has the potential to provide power savings for a UE during operation of the UE in a radio resource control (RRC) idle mode, an RRC inactive mode, or an RRC connected mode. Further, because power consumption of the UE (e.g., a modem of the UE) is increased during operation in higher frequency bands (e.g., a frequency band in frequency range 2 (FR2)), the LR+MR architecture can potentially provide power savings in higher frequency bands (e.g., frequency bands in FR2). Additionally, the low power monitoring capability of the LR provides an opportunity to improve connected mode DRX (CDRX) operation with respect to, for example, latency and power consumption. [0029] Conventionally, a WUS signal causes the UE to move from a sleep state to a fully active state. Waking to the fully active state causes the UE to consume a highest amount of power, even if a grant or data arrives some amount of time later (e.g., because the UE is in the active state for some amount of time prior to the grant or the data being received). Currently, a network node has few techniques to enable the UE to conserve power. These techniques include cross-slot scheduling and PDCCH skipping. However, these techniques require the network node 110 to have knowledge of data arrival information accurately at the start of a CDRX cycle (e.g., so that the network node can schedule a grant at an arbitrary number of slots away, or configure PDCCH skipping for an arbitrary number of slots). However, the network node does not have such knowledge in some scenarios, meaning that these techniques cannot be implemented. As a result, the network node schedules suboptimal and frequent wake-ups for the UE, thereby increasing power consumption and reducing efficiency. However, using an LR, it may be possible for the network node to trigger the MR to operate in a "partial" sleep state and then wake-up the MR just-in-time for reception of a communication using MR by signaling on the LR. Here, the "partial" sleep state is associated with a guaranteed wake-up time (e.g., a guaranteed amount of time to reach the active state). This way, the UE need not consume the highest amount of power while the network node waits for data intended for the UE to be buffered for transmission to the UE. [0030] Various aspects relate generally to wake-up signaling using an LR. Some aspects more specifically relate to LR-aided CDRX active state operation. In some aspects, a UE may monitor for an activation signal during an active duration of a CDRX cycle, with the monitoring being performed using an LR of the UE. The UE may receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal, and may cause an MR of the UE to move from a first sleep state (e.g., a deep sleep, a light sleep, a micro-sleep, or the like) to a second sleep state (e.g., an active state) based at least in part on the activation signal. [0031] Some aspects more specifically relate to a multi-level wake-up indication using an LR. In some aspects, a UE may receive a signal including an indication of a wake-up level at which an MR of the UE is to operate. Here, the wake-up level is one of a plurality of wake-up levels, with each wake-up level being associated with a different wake-up latency and being associated with a respective sleep state in a plurality of sleep states. The UE may then cause the MR of the UE to move from a first sleep state to a second sleep state based at least in part on the wake-up level. [0032] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the techniques and apparatuses described herein for an LR-aided CDRX active state operation enable an MR of the UE to be in a sleep state during a significant portion of CDRX cycle (e.g., rather than being in a fully active state but waiting to receive a grant during most of the CDRX cycle). As a result, power consumption of the UE is reduced. Further, in some examples, the techniques and apparatuses described herein for multi-level wake-up indication enable the degree to which the MR of the UE is in a sleep state to be controlled so as to enable the UE to conserve power through additional or "deeper" sleep. At the same time, the multi-level wake-up indication enables the network to control the latency to fully wake-up the MR of the UE, when required. Additional details are provided below. [0033] Multiple-access radio access technologies (RATs) have been adopted in various telecommunication standards to provide common protocols that enable wireless communication devices to communicate on a municipal, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). 5G NR supports various technologies and use cases including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV). [0034] As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements may be adopted in or implemented for 5G NR or future RATs, such as 6G, to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, and/or artificial intelligence or machine learning (AI/ML), among other examples. These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and/or aerial platforms, among other examples. The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies and/or support one or more of the foregoing use cases. [0035] Fig. 1 is a diagram illustrating an example of a wireless communication network 100 in accordance with the present disclosure. The wireless communication network 1may be or may include elements of a 5G (or NR) network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110, shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 110d. The network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e. id="p-36" id="p-36" id="p-36" id="p-36" id="p-36"

[0036] The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and/or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular radio access technology (RAT) (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G/NR RAT, and/or a 6G RAT, among other examples. In some examples, when multiple RATs are deployed in a given geographic area, each RAT in the geographic area may operate on different frequencies to avoid interference with one another. [0037] Various operating bands have been defined as frequency range designations FR(410 MHz through 7.125 GHz), FR2 (24.25 GHz through 52.6 GHz), FR3 (7.125 GHz through 24.25 GHz), FR2-2 (52.6 GHz through 71 GHz), FR4 (71 GHz through 114.GHz), and FR5 (114.25 GHz through 300 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a "Sub-6 GHz" band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a "millimeter wave" band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz), which is identified by the International Telecommunications Union (ITU) as a "millimeter wave" band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FRcharacteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, "sub-6 GHz," if used herein, may broadly refer to frequencies that are less than 6 GHz, that are within FR1, and/or that are included in mid-band frequencies. Similarly, the term "millimeter wave," if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR2-2, or FR5, and/or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and/or other RATs beyond 52.6 GHz. For example, each of FR2-2, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS), in which multiple RATs (for example, 4G/LTE and 5G/NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR2-2, and/or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges. [0038] A network node 110 may include one or more devices, components, or systems that enable communication between a UE 120 and one or more devices, components, or systems of the wireless communication network 100. A network node 110 may be, may include, or may also be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, an eNB, a gNB, an access point (AP), a transmission reception point (TRP), a mobility element, a core, a network entity, a network element, a network equipment, and/or another type of device, component, or system included in a radio access network (RAN). [0039] A network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures). For example, a network node 110 may be a device or system that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack), or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node (having an aggregated architecture), meaning that the network node 1may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100. For example, an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100. [0040] Alternatively, and as also shown, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 may implement a radio protocol stack that is physically distributed and/or logically distributed among two or more nodes in the same geographic location or in different geographic locations. For example, a disaggregated network node may have a disaggregated architecture. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance), or in a virtualized radio access network (vRAN), also known as a cloud radio access network (C-RAN), to facilitate scaling by separating base station functionality into multiple units that can be individually deployed. [0041] The network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and/or one or more radio units (RUs). A CU may host one or more higher layer control functions, such as radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, and/or service data adaptation protocol (SDAP) functions, among other examples. A DU may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and/or one or more higher physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host one or more lower PHY layer functions, such as a fast Fourier transform (FFT), an inverse FFT (iFFT), beamforming, physical random access channel (PRACH) extraction and filtering, and/or scheduling of resources for one or more UEs 120, among other examples. An RU may host RF processing functions or lower PHY layer functions, such as an FFT, an iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer functional split. In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120. [0042] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and/or one or more RUs. Additionally or alternatively, a network node 110 may include one or more Near-Real Time (Near-RT) RAN Intelligent Controllers (RICs) and/or one or more Non-Real Time (Non-RT) RICs. In some examples, a CU, a DU, and/or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples. A virtual unit may be implemented as a virtual network function, such as associated with a cloud deployment. [0043] Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term "cell" can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In some examples, a cell may not necessarily be stationary. For example, the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or a non-terrestrial network (NTN) network node). [0044] The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and/or disaggregated network nodes, among other examples. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 130a, the network node 110b may be a pico network node for a pico cell 130b, and the network node 110c may be a femto network node for a femto cell 130c.Various different types of network nodes 110 may generally transmit at different power levels, serve different coverage areas, and/or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts), whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts). [0045] In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. "Downlink" (or "DL") refers to a communication direction from a network node 110 to a UE 120, and "uplink" (or "UL") refers to a communication direction from a UE 120 to a network node 110. Downlink channels may include one or more control channels and one or more data channels. A downlink control channel may be used to transmit downlink control information (DCI) (for example, scheduling information, reference signals, and/or configuration information) from a network node 110 to a UE 120. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCHs), and downlink data channels may include one or more physical downlink shared channels (PDSCHs). Uplink channels may similarly include one or more control channels and one or more data channels. An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and/or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include one or more physical uplink control channels (PUCCHs), and uplink data channels may include one or more physical uplink shared channels (PUSCHs). The downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate. [0046] Downlink and uplink resources may include time domain resources (frames, subframes, slots, and/or symbols), frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and/or resource elements), and/or spatial domain resources (particular transmit directions and/or beam parameters). Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs). A BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs). A BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and/or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and/or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor), leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120. [0047] As described above, in some aspects, the wireless communication network 1may be, may include, or may be included in, an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. An anchor network node 110 may also be referred to as an IAB donor (or "IAB-donor"). The anchor network node 110 may connect to the core network via a wired backhaul link. For example, an Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF). An IAB network also generally includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply as IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 may communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or may communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network node 110 or other non-anchor network node 110 may also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication (such as time resources, frequency resources, and/or spatial resources) may be shared between access links and backhaul links. [0048] In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." In the example shown in Fig. 1, the network node 110d (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. Additionally or alternatively, a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples. [0049] The UEs 120 may be physically dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 1may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and/or smart jewelry, such as a smart ring or a smart bracelet), an entertainment device (for example, a music device, a video device, and/or a satellite radio), an extended reality (XR) device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and/or any other suitable device or function that may communicate via a wireless medium. [0050] A UE 120 and/or a network node 110 may include one or more chips, system-on-chips (SoCs), chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. The processing system includes processor (or "processing") circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs) and/or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASIC), programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as "processors" or collectively as "the processor" or "the processor circuitry"). One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions. [0051] The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as random-access memory (RAM) or read-only memory (ROM), or combinations thereof (all of which may be generally referred to herein individually as "memories" or collectively as "the memory" or "the memory circuitry"). One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively "the radio"), multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers. The UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system. [0052] Some UEs 120 may be considered machine-type communication (MTC) UEs, evolved or enhanced machine-type communication (eMTC), UEs, further enhanced eMTC (feMTC) UEs, or enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be simply referred to as "MTC UEs". An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and/or a location tag. Some UEs 120 may be considered IoT devices and/or may be implemented as NB-IoT (narrowband IoT) devices.

An IoT UE or NB-IoT device may be, may include, or may be included in or coupled with an industrial machine, an appliance, a refrigerator, a doorbell camera device, a home automation device, and/or a light fixture, among other examples. Some UEs 120 may be considered Customer Premises Equipment, which may include telecommunications devices that are installed at a customer location (such as a home or office) to enable access to a service provider's network (such as included in or in communication with the wireless communication network 100). [0053] Some UEs 120 may be classified according to different categories in association with different complexities and/or different capabilities. UEs 120 in a first category may facilitate massive IoT in the wireless communication network 100, and may offer low complexity and/or cost relative to UEs 120 in a second category. UEs 120 in a second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, full-capability UEs, and/or premium UEs that are capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and/or precise positioning in the wireless communication network 100, among other examples. A third category of UEs 120 may have mid-tier complexity and/or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability). A UE 120 of the third category may be referred to as a reduced capacity UE ("RedCap UE"), a mid-tier UE, an NR-Light UE, and/or an NR-Lite UE, among other examples. RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and/or eMTC UEs, and mission-critical IoT devices and/or premium UEs. RedCap UEs may include, for example, wearable devices, IoT devices, industrial sensors, and/or cameras that are associated with a limited bandwidth, power capacity, and/or transmission range, among other examples. RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and/or smart city deployments, among other examples. [0054] In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary). As an example, the UE 120a may directly transmit data, control information, or other signaling as a sidelink communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the data to the UE 120e in a DL communication. In various examples, the UEs 120 may transmit and receive sidelink communications using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and/or vehicle-to-pedestrian (V2P) protocols), and/or mesh network communication protocols. In some deployments and configurations, a network node 110 may schedule and/or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and/or other operations for sidelink communications. [0055] In various examples, some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full-duplex operation in addition to half-duplex operation. A network node 110 or a UE 120 operating in a half-duplex mode may perform only one of transmission or reception during particular time resources, such as during particular slots, symbols, or other time periods. Half-duplex operation may involve time-division duplexing (TDD), in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time). In contrast, a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources). By operating in a full-duplex mode, network nodes 110 and/or UEs 120 may generally increase the capacity of the network and the radio access link. In some examples, full-duplex operation may involve frequency-division duplexing (FDD), in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for a UE 120 but not for a network node 110. For example, a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for a network node 110 but not for a UE 120. For example, a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both a network node 110 and a UE 120. [0056] In some examples, the UEs 120 and the network nodes 110 may perform MIMO communication. "MIMO" generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time domain or the frequency domain, single-frequency-network (SFN) transmission, or non-coherent joint transmission (NC-JT). [0057] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may monitor for an activation signal during an active duration of a CDRX cycle, wherein the monitoring is performed using a using an LR of the UE 120; receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal; and cause an MR of the UE 120 to move from a first sleep state to a second sleep state based at least in part on the activation signal. Additionally, or alternatively, as described in more detail elsewhere herein, the communication manager 140 may receive a signal including an indication of a wake-up level at which an MR of the UE 120 is to operate, wherein the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and wherein each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states; and cause the MR of the UE 120 to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein. [0058] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1. id="p-59" id="p-59" id="p-59" id="p-59" id="p-59"

[0059] Fig. 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network in accordance with the present disclosure. [0060] As shown in Fig. 2, the network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 2(shown as 232a through 232t, where t ≥ 1), a set of antennas 234 (shown as 234a through 234v, where v ≥ 1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller/processor 240, a memory 242, a communication unit 244, a scheduler 246, and/or a communication manager 150, among other examples. In some configurations, one or a combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and/or the TX MIMO processor 216 may be included in a transceiver of the network node 110. The transceiver may be under control of and used by one or more processors, such as the controller/processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and/or operations described herein. In some aspects, the network node 110 may include one or more interfaces, communication components, and/or other components that facilitate communication with the UE 120 or another network node. [0061] The terms "processor," "controller," or "controller/processor" may refer to one or more controllers and/or one or more processors. For example, reference to "a/the processor," "a/the controller/processor," or the like (in the singular) should be understood to refer to any one or more of the processors described in connection with Fig. 2, such as a single processor or a combination of multiple different processors. Reference to "one or more processors" should be understood to refer to any one or more of the processors described in connection with Fig. 2. For example, one or more processors of the network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and/or controller/processor 240. Similarly, one or more processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and/or controller/processor 280. [0062] In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to "one or more memories" should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig. 2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories. [0063] For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data ("downlink data") intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue). In some examples, the transmit processor 214 may select one or more MCSs for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS(s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI)) and/or control information (for example, CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and/or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS), a demodulation reference signal (DMRS), or a channel state information (CSI) reference signal (CSI-RS)) and/or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS)). [0064] The TX MIMO processor 216 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to the set of modems 232. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 232. Each modem 232 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a time domain downlink signal. The modems 232a through 232t may together transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234. [0065] A downlink signal may include a DCI communication, a MAC control element (MAC-CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication. Downlink signals may be transmitted on a PDCCH, a PDSCH, and/or on another downlink channel. A downlink signal may carry one or more transport blocks (TBs) of data. A TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100. A data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The quantity of TBs used to carry the data associated with a particular data stream may be associated with a TB size common to the multiple TBs. The TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and/or another parameter. In general, the larger the TB size, the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead. However, larger TB sizes may be more prone to transmission and/or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques. [0066] For uplink communication from the UE 120 to the network node 110, uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232), may be detected by the MIMO detector 236 (for example, a receive (Rx) MIMO processor) if applicable, and/or may be further processed by the receive processor 238 to obtain decoded data and/or control information. The receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and/or another type of data sink) and provide the decoded control information to a processor, such as the controller/processor 240. [0067] The network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some aspects, the scheduler 246 may use DCI to dynamically schedule DL transmissions to the UE 120 and/or UL transmissions from the UE 120. In some examples, the scheduler 246 may allocate recurring time domain resources and/or frequency domain resources that the UE 120 may use to transmit and/or receive communications using an RRC configuration (for example, a semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure a configured grant (CG) for the UE 120. [0068] One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and/or the controller/processor 240 may be included in an RF chain of the network node 110. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and/or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or more processors of the network node 110). In some aspects, the RF chain may be or may be included in a transceiver of the network node 110. [0069] In some examples, the network node 110 may use the communication unit 2to communicate with a core network and/or with other network nodes. The communication unit 244 may support wired and/or wireless communication protocols and/or connections, such as Ethernet, optical fiber, common public radio interface (CPRI), and/or a wired or wireless backhaul, among other examples. The network node 110 may use the communication unit 244 to transmit and/or receive data associated with the UE 120 or to perform network control signaling, among other examples. The communication unit 244 may include a transceiver and/or an interface, such as a network interface. [0070] The UE 120 may include a set of antennas 252 (shown as antennas 252a through 252r, where r ≥ 1), a set of modems 254 (shown as modems 254a through 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, a memory 282, and/or a communication manager 140, among other examples. One or more of the components of the UE 120 may be included in a housing 284. In some aspects, one or a combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120. The transceiver may be under control of and used by one or more processors, such as the controller/processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein. In some aspects, the UE 120 may include another interface, another communication component, and/or another component that facilitates communication with the network node 1and/or another UE 120. [0071] For downlink communication from the network node 110 to the UE 120, the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254. For example, each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use the respective demodulator component to condition (for example, filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. The receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and/or an application executed on the UE 120), and may provide decoded control information and system information to the controller/processor 280. [0072] For uplink communication from the UE 120 to the network node 110, the transmit processor 264 may receive and process data ("uplink data") from a data source 262 (such as a data pipeline, a data queue, and/or an application executed on the UE 120) and control information from the controller/processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and/or other types of control information. In some aspects, the receive processor 258 and/or the controller/processor 280 may determine, for a received signal (such as received from the network node 110 or another UE), one or more parameters relating to transmission of the uplink communication. The one or more parameters may include a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, a channel quality indicator (CQI) parameter, or a transmit power control (TPC) parameter, among other examples. The control information may include an indication of the RSRP parameter, the RSSI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and/or another parameter. The control information may facilitate parameter selection and/or scheduling for the UE 120 by the network node 110. [0073] The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink SRS, and/or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 2(for example, for DFT-s-OFDM or CP-OFDM). The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 2may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain an uplink signal. [0074] The modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252. An uplink signal may include a UCI communication, a MAC-CE communication, an RRC communication, or another type of uplink communication. Uplink signals may be transmitted on a PUSCH, a PUCCH, and/or another type of uplink channel. An uplink signal may carry one or more TBs of data. Sidelink data and control transmissions (that is, transmissions directly between two or more UEs 120) may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and/or a physical sidelink feedback channel (PSFCH). [0075] One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Fig. 2. As used herein, "antenna" can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. "Antenna panel" can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas. "Antenna module" may refer to circuitry including one or more antennas, which may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device. [0076] In some examples, each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, and/or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. A spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam). For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, a half wavelength, or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference patterns of signals transmitted by the separate antenna elements within that expected range. [0077] The amplitudes and/or phases of signals transmitted via antenna elements and/or sub-elements may be modulated and shifted relative to each other (such as by manipulating phase shift, phase offset, and/or amplitude) to generate one or more beams, which is referred to as beamforming. The term "beam" may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" may also generally refer to a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and/or a vertical direction), and/or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and/or a set of directional resources associated with the signal. In some implementations, antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and/or phases of the signal(s) to form one or more beams. The shape of a beam (such as the amplitude, width, and/or presence of side lobes) and/or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and/or amplitudes of the multiple signals relative to each other. [0078] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements. As another example, a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements. Generally, a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements. Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmitted using the same time and frequency resources with spatial multiplexing. [0079] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280. [0080] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300 in accordance with the present disclosure. One or more components of the example disaggregated base station architecture 300 may be, may include, or may be included in one or more network nodes (such one or more network nodes 110). The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or that can communicate indirectly with the core network 320 via one or more disaggregated control units, such as a Non-RT RIC 350 associated with a Service Management and Orchestration (SMO) Framework 360 and/or a Near-RT RIC 370 (for example, via an E2 link). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via Finterfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs 340. [0081] Each of the components of the disaggregated base station architecture 300, including the CUs 310, the DUs 330, the RUs 340, the Near-RT RICs 370, the Non-RT RICs 350, and the SMO Framework 360, may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium. [0082] In some aspects, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 may be deployed to communicate with one or more DUs 330, as necessary, for network control and signaling. Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, a DU 330 may host various layers, such as an RLC layer, a MAC layer, or one or more PHY layers, such as one or more high PHY layers or one or more low PHY layers. Each layer (which also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310. Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 may be controlled by the corresponding DU 330. [0083] The SMO Framework 360 may support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an O1 interface. For virtualized network elements, the SMO Framework 360 may interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an O2 interface. A virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and/or a Near-RT RIC 370. In some aspects, the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, a 5G NR RAN, and/or a 6G RAN, such as an open eNB (O-eNB) 380, via an Ointerface. Additionally or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective O1 interface. In some deployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture. [0084] The Non-RT RIC 350 may include or may implement a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence and/or machine learning (AI/ML) workflows including model training and updates, and/or policy-based guidance of applications and/or features in the Near-RT RIC 370. The Non-RT RIC 350 may be coupled to or may communicate with (such as via an A1 interface) the Near-RT RIC 370. The Near-RT RIC 370 may include or may implement a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface (such as via an Einterface) connecting one or more CUs 310, one or more DUs 330, and/or an O-eNB with the Near-RT RIC 370. [0085] In some aspects, to generate AI/ML models to be deployed in the Near-RT RIC 370, the Non-RT RIC 350 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 370 and may be received at the SMO Framework 360 or the Non-RT RIC 350 from non-network data sources or from network functions. In some examples, the Non-RT RIC 350 or the Near-RT RIC 370 may tune RAN behavior or performance. For example, the Non-RT RIC 350 may monitor long-term trends and patterns for performance and may employ AI/ML models to perform corrective actions via the SMO Framework 360 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies). [0086] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3. id="p-87" id="p-87" id="p-87" id="p-87" id="p-87"

[0087] The network node 110, the controller/processor 240 of the network node 110, the UE 120, the controller/processor 280 of the UE 120, the CU 310, the DU 330, the RU 340, or any other component(s) of Figs. 1, 2, or 3 may implement one or more techniques or perform one or more operations associated with wake-up signaling using an LR, as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, any other component(s) of Fig. 2, the CU 310, the DU 330, or the RU 340 may perform or direct operations of, for example, process 800 of Fig. 8, process 900 of Fig. 9, or other processes as described herein (alone or in conjunction with one or more other processors). The memory 242 may store data and program codes for the network node 110, the network node 110, the CU 310, the DU 330, or the RU 340. The memory 282 may store data and program codes for the UE 120. In some examples, the memory 242 or the memory 2may include a non-transitory computer-readable medium storing a set of instructions (for example, code or program code) for wireless communication. The memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). The memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). For example, the set of instructions, when executed (for example, directly, or after compiling, converting, or interpreting) by one or more processors of the network node 110, the UE 120, the CU 310, the DU 330, or the RU 340, may cause the one or more processors to perform process 800 of Fig. 8, process 900 of Fig. 9, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples. [0088] In some aspects, a UE (e.g., a UE 120) includes means for monitoring for an activation signal during an active duration of a CDRX cycle, wherein the monitoring is performed using a using an LR of the UE; means for receiving the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal; and/or means for causing an MR of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal. Additionally, or alternatively, the UE includes means for receiving a signal including an indication of a wake-up level at which an MR of the UE is to operate, wherein the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and wherein each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states; and/or means for causing the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. The means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282. [0089] Fig. 4 is a diagram illustrating an example 400 of an LR and a low-power wake-up signal (LP-WUS), in accordance with the present disclosure. As shown in Fig. 4, a UE (e.g., UE 120) may be equipped with a communication system that includes an MR and an LR to reduce power consumption and enable low latency. For example, power saving and low latency are often conflicting goals because placing one or more components (such as an MR) into a sleep state more often to reduce power consumption also increases latency (e.g., because data cannot be transmitted and/or received while the one or more components are in the sleep state). Furthermore, in cases where the time that one or more components spend in a sleep state is reduced to reduce latency, power consumption may increase. Accordingly, as shown in Fig. 4, the UE may be equipped with the LR, which is a companion receiver that may be used with a MR to reduce power consumption and reduce latency. [0090] For example, in some aspects, the UE may generally use the MR to transmit and/or receive user data, and the MR may be turned off or operated in a sleep state (e.g., a power state associated with one relative power unit, as defined in 3GPP Technical Report (TR) 58.840) unless there is user data to transmit and/or receive. Furthermore, the LR may serve as a simple wake-up receiver for the MR (e.g., the LR may not include a transmitter), and the LR may be active and monitoring for an LP-WUS while the MR is off or in a sleep state. For example, reference number 410-1 depicts a first state associated with the MR and the LR in cases where there is no user data that the MR needs to receive. In such cases, the MR may be off or in the sleep state unless there is user data to transmit, and the LR may actively monitor for an LP-WUS (e.g., continuously or periodically in monitoring occasions that are separated in time). Furthermore, reference number 410-2 depicts a second state associated with the MR and the LR where there is user data that the MR needs to receive. In such cases, the LR may receive an LP-WUS (e.g., from a network node) and the LR or the UE may provide a trigger to wake or otherwise activate the MR based on detecting the LP-WUS. Accordingly, the MR may then transmit and/or receive user data. [0091] In general, the LR may consume very little power (e.g., a target power consumption on the order of tens of milliwatts (mW) in the active state, as compared to hundreds of mW for the MR), which may be achieved using simple modulation schemes (e.g., on-off-keying (OOK)), a narrow bandwidth (e.g., less than 5 MHz), low complexity receiver architectures (e.g., envelope detection), and/or other suitable techniques. In this way, the LR can be used to reduce the time that the MR spends in an on state and/or may avoid unnecessarily waking the MR from the off or sleep state when there is no user data to transmit or receive, which tends to be costly from a power consumption perspective. Frequently waking up the MR wastes significant power because ramping up and ramping down of MR components is an overhead which consumes power and time. Furthermore, because the LR has a very low power consumption, the LR can be used to frequently or continuously perform LP-WUS monitoring, which may improve latency because the MR can be woken up when there is user data that the MR needs to receive (e.g., the LR does not suffer from the latency versus power efficiency tradeoff associated with MR duty cycling schemes, such as DRX). Furthermore, in addition to performing LP-WUS monitoring, which is mainly targeted at paging reception, the LR may monitor a low power reference signal (LP-RS) for time and frequency tracking and radio resource management (RRM) measurement. In this way, by monitoring the LP-RS, serving cell and/or neighbor cell monitoring can be offloaded from the MR to the LR to reduce how often the MR is woken up and thereby reduce power consumption. [0092] In some aspects, as shown by reference number 420, one application for the LR is to monitor the LP-WUS for paging monitoring, which can be used to reduce unnecessary paging reception performed by the MR. For example, as shown in Fig. 4, the LR may be configured to monitor for an LP-WUS (e.g., while the MR is off or in a sleep state) according to a wake-up signal (WUS) monitoring periodicity (e.g., the LR may monitor for the LP-WUS in periodic LP-WUS monitoring occasions that are separated in time by the WUS monitoring periodicity). Alternatively, although not explicitly shown in Fig. 4, the LR may be configured to continuously monitor for the LP-WUS. In general, a network node may transmit an LP-WUS to a UE in cases where there is a paging message that needs to be sent to the UE while the UE is in an idle or inactive state (e.g., a radio resource control (RRC) idle or RRC inactive state). Alternatively, though not shown here, a network node may transmit an LP-WUS to a UE when there is data to be sent to the UE while the UE is in connected state (e.g., an RRC connected state). In such cases, as shown by reference number 422, the LR may receive and detect the LP-WUS, which may trigger the LR to wake up the MR. For example, as shown by reference number 424, the LP-WUS may be a message-based WUS, which may correspond to a packet that includes a preamble, a payload (e.g., a cell identifier or UE addressing for a paging early indication), and a set of cyclic redundancy check (CRC) bits. Alternatively, in some aspects, the LP-WUS may be a sequence-based WUS, which may include a set of sequences that depend on a cell identifier and/or an identifier associated with the UE. In either case, as shown, the MR may wake up after a MR wake-up time, and may then start to monitor one or more synchronization signal block (SSB) transmissions to obtain synchronization with the network node before monitoring and receiving the paging message in a subsequent paging occasion (PO). In some cases, such as when the MR is sufficiently synchronized, the MR may start to monitor for a message such as a control or data message after wake-up and not wait for a SSB reception. Otherwise, in cases where the LR does not detect the LP-WUS, the MR may remain in the sleep state to save power. [0093] In some aspects, the techniques and apparatuses described herein associated with LR-aided CDRX operation and/or multi-level wake-up signaling can utilize an LR or an LP-WUS similar to that described with respect to Fig. 4. [0094] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4. [0095] Fig. 5 is a diagram illustrating an example 500 of a discontinuous reception (DRX) configuration, in accordance with the present disclosure. DRX can be used in RRC idle mode when monitoring for paging messages to avoid a UE 120 having to monitor all PDCCH transmission opportunities and, therefore conserve battery power. DRX can also be used in RRC connected mode to conserve UE battery power. Connected mode DRX (CDRX) takes advantage of periods of inactivity by allowing the UE to enter a "sleep" state during which the UE is not required to monitor the PDCCH. The UE 120 periodically wakes to monitor the PDCCH in case there is a requirement to receive a downlink resource allocation. The UE 120 may in some scenarios be permitted to interrupt the "sleep" state to send a scheduling request (SR) and thus initiate uplink data transfer. id="p-96" id="p-96" id="p-96" id="p-96" id="p-96"

[0096] As shown in Fig. 5, a network node 110 may transmit a DRX configuration to a UE 120 to configure a DRX cycle 505 for the UE 120. A DRX cycle 505 may include a DRX on duration 510 (e.g., during which a UE 120 is in an active state) and an opportunity to enter a DRX sleep state 515. As used herein, the time during which the UE 120 is configured to be in an active state during the DRX on duration 510 may be referred to as an active duration, and the time during which the UE 120 is configured to be in the DRX sleep state 515 may be referred to as an inactive duration. The network may configure the UE 120 to monitor for messages for at least a certain duration after wake-up. The UE 120 may monitor for messages for further duration, based on receiving a message and waiting for the expiration of certain timers (e.g., an inactivity timer). The active duration, as used herein, refers to a duration during the DRX cycle during which the UE 120 generally monitors for messages from the network, using any type of radio (e.g., the LR or the MR). As described below, the UE 120 may monitor a PDCCH during the active duration, and may refrain from monitoring the PDCCH during the inactive duration. [0097] During the DRX on duration 510 (e.g., the active duration), the UE 120 may monitor a downlink control channel (e.g., a PDCCH), as shown by reference 520. For example, the UE 120 may monitor the PDCCH for DCI pertaining to the UE 120. If the UE 120 does not detect and/or successfully decode any PDCCH communications intended for the UE 120 during the DRX on duration 510, then the UE 120 may enter the sleep state 515 (e.g., for the inactive duration) at the end of the DRX on duration 510, as shown by reference number 525. In this way, the UE 120 may conserve battery power and reduce power consumption. As shown, the DRX cycle 505 may repeat with a configured periodicity according to the DRX configuration. [0098] If the UE 120 detects and/or successfully decodes a PDCCH communication intended for the UE 120, then the UE 120 may remain in an active state (e.g., awake) for the duration of an inactivity timer 530 (e.g., which may extend the active duration). The UE 120 may start the inactivity timer 530 at a time at which the PDCCH communication is received (e.g., in a transmission time interval (TTI) in which the PDCCH communication is received, such as a slot or a subframe). The UE 120 may remain in the active state until the inactivity timer 530 expires, at which time the UE 120 may enter the sleep state 515 (e.g., for the inactive duration), as shown by reference number 535. During the duration of the inactivity timer 530, the UE 120 may continue to monitor for PDCCH communications, may obtain a downlink data communication (e.g., on a downlink data channel, such as a physical downlink shared channel (PDSCH)) scheduled by the PDCCH communication, and/or may prepare and/or transmit an uplink communication (e.g., on a physical uplink shared channel (PUSCH)) scheduled by the PDCCH communication. The UE 120 may restart the inactivity timer 530 after each detection of a PDCCH communication for the UE 120 for an initial transmission (e.g., but not for a retransmission). In some scenarios, the UE 120 may be configured with one or more other timers (e.g., a retransmission timer) that may cause the UE 120 to wake-up at particular times, perform an activity (e.g., a retransmission) and return to the sleep state 515. By operating in this manner, the UE 120 may conserve battery power and reduce power consumption by entering the sleep state 515. [0099] In some aspects, the techniques and apparatuses described herein associated with LR-aided CDRX operation and/or multi-level wake-up signaling can be applied to DRX operation as described with respect to Fig. 5. [0100] As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5. [0101] Figs. 6A-6D are diagrams illustrating examples associated with LR-aided CDRX active state operation, in accordance with the present disclosure. As shown in Fig. 6A, an example 600 includes communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink. [0102] As shown in Fig. 6 at reference 602, the UE 120 may monitor for an activation signal during an active duration of a CDRX cycle. As shown, the monitoring for the activation signal may be performed by the LR of the UE 120. In some aspects, an activation signal is a signal that indicates that the UE 120 is to cause an MR of the UE 120 to move from a first sleep state to a second sleep state. [0103] In some aspects, the UE 120 monitors for the activation signal after an LP-WUS is detected using the LR of the UE 120. For example, the UE 120 may be configured such that the LR is to monitor for LP-WUSs (e.g., as described with respect to Fig. 4). Here, upon receiving an LP-WUS, the UE 120 may cause the MR of the UE 120 to wake such that the MR is at an active state at a start of an active duration of a CDRX cycle. The active duration comprises one or more ON durations and one or more inactivity timer periods (e.g., periods of time during which an inactivity timer is running). In some aspects, the UE 120 is configured such that the LR monitors for the activation signal after the LP-WUS is received such that the LR monitors for the activation signal during the active duration. Thus, the UE 120 may in some aspects, begin monitoring for the activation signal during the active duration and after receiving the LP-WUS (e.g., after an initial data or control reception is completed, when an inactivity timer is started, or the like). [0104] In some aspects, the UE 120 may be configured to monitor for the activation signal during one or more periods of time that are indicated in an activation signal configuration. For example, the network node 110 may transmit, and the UE 120 may receive, an activation signal configuration indicating that activation signal monitoring is to be performed during particular time periods, such as an inactivity timer duration or a re-transmission timer duration, while excluding other durations (e.g., the minimum duration for which the UE 120 must monitor after wake-up, referred to as the ON duration). In some aspects, activation signal monitoring may be configured such that activation signal monitoring follows timers that cause monitoring to cease after certain time. For example, activation signal monitoring may be configured such that the LR performs activation signal monitoring during an inactivity timer and such that the UE 1does not monitor for activation signals in a CDRX period after the inactivity timer expires. Such a timer-based configuration may allow the UE 120 to save power by putting both the LR and the MR to sleep after the inactivity timer expires. In some aspects, the timer values may be shared with or may be different from MR-only CDRX timers. [0105] In some aspects, the UE 120 may be configured such that activation signal monitoring comprises continuous monitoring during a period of time associated with monitoring for activation signals (e.g., an example of which is illustrated in the upper diagram of Fig. 6D). Additionally, or alternatively, the UE 120 may be configured such that activation signal monitoring comprises duty-cycle monitoring during the period of time associated with monitoring for the activation signal (e.g., an example of which is illustrated in the lower diagram of Fig. 6D). In some aspects, duty-cycle monitoring may reduce power consumption associated with performing activation signal monitoring. In some aspects, activation signal monitoring can be of different types depending on one or more factors that can be configured, such as continuous monitoring versus duty-cycled monitoring, a bandwidth of the activation signal, a quantity of symbols in the activation signal, one or more sequence(s) to be monitored, an amount of payload on the activation signal, a beam associated with the activation signal, or a TCI state associated with the activation signal, among other examples. In some aspects, a type of activation signal monitoring can be configured per each duration (e.g., e.g., ON duration, inactivity timer, retransmission timer, or the like). In some aspects, the type of monitoring can be changed dynamically by, for example, signaling on the activation signal itself or via DCI (e.g., when the MR is in the active state). In some aspects, to increase coverage of an activation signal, repetition (e.g., in time, frequency, or higher bandwidth) may be utilized. In some aspects, one or more parameters of the activation signal (e.g., a bandwidth, a sequence identifier, or the like) may be signaled to the UE 120 via, for example, RRC signaling or DCI. [0106] In some aspects, the UE 120 may activate or deactivate activation signal monitoring based at least in part on an indication received on the MR. The indication may be received via, for example, RRC signaling, DCI, a medium access control (MAC) control element (CE), or a payload of another activation signal received on the LR. As an example, the network may send the indication on a DCI which already carries a data grant for the UE 120 and is to be decoded by the MR of UE 120. In this way, the network may send the indication with minimal impact on power consumption of the UE 120. In some other aspects, the activation signal monitoring on an LR may be automatically stopped when certain conditions become true for the UE 120. For example, if the MR of the UE 120 is ON and monitoring or if the UE 120 is charging its battery from a power source, then the UE 120 may stop monitoring for the activation signal on the LR and may use the MR to monitor for the activation signal. [0107] In some aspects, the UE 120 may transmit capability information indicating a capability of the UE 120 with respect to monitoring for activation signals. For example, a UE 120 with an LR based on simple envelope detection may support continuous monitoring or duty-cycle monitoring, whereas such monitoring may not be feasible for a UE 120 with an LR based on OFDM. In some aspects, the UE 120 can provide such capability information to the network node 110 dynamically based on a need to save power, a traffic type associated with the UE 120, or the like. In some aspects, the capability information may further include information that identifies latencies associated with moving the MR from one sleep state to another sleep state. id="p-108" id="p-108" id="p-108" id="p-108" id="p-108"

[0108] As shown at reference 604, the UE 120 may receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal. For example, the LR of the UE 120 may receive the activation signal during the active duration based at least in part on monitoring for the activation signal. [0109] In some aspects, a payload capacity of the activation signal may match a payload capacity of the LP-WUS. Additionally, or alternatively, a sequence type of the activation signal may match a sequence type of the LP-WUS. That is, in some aspects, the activation signal may be similar to the LP-WUS – meaning that the activation signal may have the same payload capacity as the LP-WUS or may have the same type of sequence but with a different payload capacity (e.g., an on-off keying (OOK) sequence with payload carried via an index modulation). [0110] In some aspects, the activation signal may comprise a payload carrying information associated with a PDCCH to be received using the MR of the UE 120 while the MR is in an active state. The information associated with the PDCCH may include, for example, information associated with a search space, a DCI format, a PDSCH grant, or another type of information. In some aspects, the use of the activation signal to transmit a payload may reduce power consumption with respect to blind decoding performed by the UE 120. [0111] As shown at reference 606, the UE 120 may cause an MR of the UE 120 to move from a first sleep state to a second sleep state based at least in part on the activation signal. For example, after receiving the activation signal, the LR may send a trigger signal 608 that causes the MR to move from the first sleep state to the second sleep state, as shown in Fig. 6A, and the MR may move from the first sleep state to the second sleep state accordingly. [0112] A sleep state of the MR is a state of operation of the MR. In some aspects, a given sleep state may be defined by a wake-up latency, with the wake-up latency representing an amount of time that is required for the MR transition to a state in which the MR is ready to receive a communication (e.g., a downlink communication) or transmit a communication (e.g., an uplink communication). In some aspects, the MR may be capable of operating in a plurality of sleep states. For example, at a given time, the MR may be capable of operating in any one of a deep sleep that is defined by a first wake-up latency tdeep, a light sleep state that is defined by a second wake-up latency tlight (tlight < tdeep), a micro-sleep state that is defined by a third wake-up latency tmicro (tmicro < tlight), and an active state that defined by a fourth wake-up latency tactive (tactive = milliseconds (ms) < tmicro). As used herein, the term active state may refer to a sleep state in with zero wake-up latency. [0113] In some aspects, the UE 120 may receive a configuration indicating a duration of time that the MR is to remain in the second sleep state after moving to the second sleep state. In some aspects, an indication of the duration of time is received in a CDRX parameter configuration. Additionally, or alternatively, the indication of the duration of time is received in the activation signal itself. In some aspects, the UE 120 causes the MR to remain in the second sleep state for the duration of time based at least in part on the configuration. Thus, the UE 120 may in some aspects wake the MR for at least a minimum time duration after the activation signal is detected (e.g., to prevent frequent on/off power wastage), with the minimum time duration being configured in a CDRX parameter configuration or carried on the activation signal itself. [0114] In some aspects, the UE 120 may receive a configuration indicating an activation latency threshold. Here, the first sleep state may be configured or selected such that an amount of time needed for the MR to move from the first sleep state to the second sleep state satisfies the activation latency threshold. That is, the network node 110 may configure a minimum activation latency Tactivation of the MR after activation signal. In some aspects, the minimum activation latency is configured for different time periods, such as an ON duration, an inactivity timer duration, or the like, to effectively enable different sleep states for MR of the UE 120. As one example, an ON duration activation latency threshold Tactivation,ON that is set to 0 milliseconds (ms) may allow only micro-sleep of the MR during the ON duration, whereas an inactivity timer activation latency threshold Tactivation,inactivity-timer that is set to 3 ms may allow light sleep or micro-sleep of the MR during the inactivity timer. In some aspects, the UE 120 may signal information associated with sleep latency thresholds to the network node 110 to enable the network node 110 to provide sufficiently long activation latency thresholds. In some aspects, activation latencies may be different for different traffic types or CDRX configurations. [0115] In some aspects, the UE 120 may cause the MR to move from the second sleep state (e.g., the active state) to the first sleep state (e.g., the light sleep state) after a period of time during which a communication operation is to occur. That is, after the MR moves from the first sleep state to the second sleep state, the UE 120 may cause the MR to move from the second sleep state back to the first sleep state (or to another sleep state). As one example, the UE 120 may cause the MR to move from the active state to another sleep state (e.g., the light sleep state, the deep sleep state, or the like) after an ON duration of an active duration in which the LR has received the activation signal. [0116] In some aspects, the LR may refrain from monitoring for activation signals for a period of time after causing the MR to move from the first sleep state to the second sleep state. For example, the LR may be configured to refrain from monitoring for activation signals during a period of time within which the MR of the UE 120 is in the active state or is moving to the active state. Activation signal monitoring may not be needed in such a scenario because the MR is (or will soon be able) to receive communications using the MR. [0117] In some aspects, the UE 120 may receive (e.g., using the LR) a deactivation signal. A deactivation signal is an activation signal that indicates that the MR of the UE 120 is to move to a deeper sleep state from a state in which the MR is operating in (e.g., from a light sleep state to a deep sleep state, from a micro-sleep state to a light sleep state, from an active state to a deep sleep state, or the like). In some aspects, the UE 120 may receive the deactivation signal during the active duration of the CDRX cycle and using the LR of the UE, and may cause the MR to transition to move from one sleep state (e.g., the first sleep state) to another sleep state (e.g., a third sleep state) based at least in part on the deactivation signal. As one example, the network node 110 may transmit a deactivation signal that is to cause the LR of the UE 120 is to skip further monitoring for activation signals (e.g., and that the MR is to stop monitoring for DCI and PDSCH). In some aspects, the deactivation signal may be similar to the LR-based activation signal as described herein. Additionally, or alternatively, the deactivation signal may in some aspects be a standalone signal that applies to a legacy active CDRX state where MR is actively monitoring. Here, the LR of the UE 120 may monitor for a deactivation signal. Such a design may allow the network node 110 to transmit a PDCCH-skipping command on the deactivation signal in order to extend PDCCH skipping even while the MR is sleeping. In some aspects, the skipping of activation signal monitoring can be carried out for a configured timer period (e.g., a particular number of slots, a particular duration of time, for a remainder of a CDRX cycle, or the like). [0118] In this way, the UE 120 may monitor for and receive an activation signal during an active duration of a CDRX cycle using an LR, and may cause an MR of the UE 120 to move from a first sleep state (e.g., a deep sleep, a light sleep, a micro-sleep, or the like) to a second sleep state (e.g., an active state) based at least in part on the activation signal. In some aspects, this LR-aided CDRX active state operation enables the MR of the UE 1to be in a sleep state during a significant portion of CDRX cycle (e.g., rather than being in a fully active state during the entire CDRX cycle). As a result, power consumption of the UE 120 is reduced. [0119] Fig. 6B is a diagram illustrating an example of operation of the LR and the MR of the UE 120 according to the process described with respect to Fig. 6A. [0120] As shown, the LR of the UE 120 receives an LP-WUS 610. Notably, the MR of the UE 120 is in a deep sleep state at the time at which the LP-WUS 610 is received by the LR. As shown, the LR provides a wake-up trigger 612 that causes the MR to move from the deep sleep state to an active state (e.g., a state in which the MR can receive data or control information) such that the MR is in the active state at the start of an active duration 614 of a CDRX period 616. As shown at reference 618, the MR of the UE 1remains in the active state for an ON duration 618. [0121] At the end of the ON duration 618, the MR moves from the active state to a light sleep state. Further, the UE 120 starts an inactivity timer 620 and begins performing activation signal monitoring 622. In this example, the LR receives an activation signal 624 based at least in part on the monitoring. Here, the activation signal 624 is received prior to expiration of the inactivity timer 620. As shown, the LR provides a wake-up trigger 626 that causes the MR to move from the light sleep state to the active state such that the MR is in the active state for an ON duration 628. In this way, the UE 1monitors for and receives an activation signal 624 during the active duration 614 of the CDRX period 616 using the LR, and causes the MR to move from a first sleep state (e.g., light sleep) to a second sleep state (e.g., an active state). [0122] At the end of the ON duration 628, the MR moves from the active state to the light sleep state. Further, the UE 120 resets the inactivity timer 620 and begins performing activation signal monitoring 630. In this example, the LR does not receive another activation signal prior to the expiration of the (reset) inactivity timer 620. Therefore, the MR moves from light sleep state to the deep sleep state. In this example, the LP-WUS 634 does not include an indication that the UE 120 is to wake and, therefore, the MR remains in the deep sleep state through the end of the CDRX period 616. [0123] Fig. 6C is a diagram illustrating another example of operation of the LR and the MR of the UE 120 according to the process described with respect to Fig. 6A. id="p-124" id="p-124" id="p-124" id="p-124" id="p-124"

[0124] As shown, the LR of the UE 120 receives an LP-WUS 640. Notably, the MR of the UE 120 is in a deep sleep state at the time at which the LP-WUS 640 is received by the LR. As shown, the LR provides a wake-up trigger 642 that causes the MR to move from the deep sleep state to an active state (e.g., a state in which the MR can receive data or control information) such that the MR is in the active state at the start of an active duration 644 of a CDRX period 646. As shown, the MR of the UE 120 remains in the active state for an ON duration 648. [0125] At the end of the ON duration 648, the MR moves from the active state to a light sleep state. Further, the UE 120 starts an inactivity timer 650 and begins performing activation signal monitoring 652. In this example, the LR receives an activation signal 654 based at least in part on the monitoring. Here, the activation signal 654 is received prior to expiration of the inactivity timer 650. As shown, the LR provides a wake-up trigger 656 that causes the MR to move from the light sleep state to the active state such that the MR is in the active state for an ON duration 658. In this way, the UE 1monitors for and receives an activation signal 654 during the active duration 644 of the CDRX period 646 using the LR, and causes the MR to move from a first sleep state (e.g., light sleep) to a second sleep state (e.g., an active state). [0126] At the end of the ON duration 658, the MR moves from the active state to the light sleep state. Further, the UE 120 resets the inactivity timer 650 and begins performing activation signal monitoring 660. In this example, the LR receives another activation signal 662 prior to the expiration of the (reset) inactivity timer 650. Here, the activation signal 662 indicates that the MR is to move to the deep sleep state (i.e., the activation signal may in some cases be a deactivation signal). In this way, the UE 1monitors for and receives an activation signal 662 during the active duration 644 of the CDRX period 646 using the LR, and causes the MR to move from the first sleep state (e.g., light sleep) to a third sleep state (e.g., deep sleep). As shown, the LR provides a sleep trigger 664 that causes the MR to move from the light sleep state to the deep state. In this example, the LP-WUS 666 does not include an indication that the UE 120 is to wake and, therefore, the MR remains in the deep sleep state through the end of the CDRX period 646. [0127] As indicated above, Figs. 6A-6D are provided as examples. Other examples may differ from what is described with respect to Figs. 6A-6D. id="p-128" id="p-128" id="p-128" id="p-128" id="p-128"

[0128] Figs. 7A-7G are diagrams illustrating examples associated with a multi-level wake-up indication using an LR, in accordance with the present disclosure. As shown in Fig. 7A, an example 700 includes communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100. The network node 110 and the UE 1may communicate via a wireless access link, which may include an uplink and a downlink. [0129] As shown at reference 702, the UE 120 may receive a signal including an indication of a wake-up level at which an MR of the UE 120 is to operate. In some aspects, the wake-up level is one of a plurality of wake-up levels, with each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency. As described above, a wake-up latency represents an amount of time that is required for the MR transition to a state in which the MR is ready to receive a communication (e.g., a downlink communication) or transmit a communication (e.g., an uplink communication). Further, each wake-up level in the plurality of wake-up levels may be associated with a respective sleep state in a plurality of sleep states. The plurality of sleep states may include, for example, a deep sleep state, a light sleep state, a micro-sleep state, or an active state, as described above with respect to Figs. 6A-6D. [0130] In some aspects, the signal including the indication of the wake-up level is an LP-WUS. That is, in some aspects, the indication of the wake-up level can be communicated along with a WUS, such as an LP-WUS (e.g., an initial WUS at the beginning of a CDRX cycle). In some aspects, the indication of the wake-up level can be communicated in an LP-WUS that is transmitted within a CDRX cycle (e.g., an example of which is illustrated in Fig. 7C). Additionally, or alternatively, the signal including the indication of the wake-up level may be a PDCCH-based WUS. [0131] In some aspects, the signal including the indication of the wake-up level is received using the LR of the UE 120. Additionally, or alternatively, the signal including the indication of the wake-up level may be received using the MR of the UE 120. [0132] In some aspects, the indication of the wake-up level may be communicated via modulation of a sequence (e.g., a sequence used to transmit an LP-WUS carrying the wake-up level indication). Additionally, or alternatively, the indication of the wake-up level may be communicated via bits on a channel. For example, an indication of the wake-up level may be transmitted for reception by the LR of the UE 120 via a modulation of a sequence, while an indication of a wake-up level may be transmitted for reception by the MR of the UE 120 via one or more bits on a PDCCH, index modulation, or a sequence index, among other examples. [0133] In some aspects, the UE 120 may receive a configuration that permits the UE 120 to map each wake-up level in the plurality of wake-up levels to a respective sleep state in the plurality of sleep states. In some aspects, the configuration may be received via, for example, RRC signaling or DCI. In some aspects, the configuration indicates a permitted wake-up latency associated with a change from a given wake-up level of the plurality of wake-up levels to one or more other wake-up levels of the plurality of wake-up levels. In some aspects, the UE 120 may determine or otherwise decide a wake-up-level-to-sleep-state mapping based at least in part on the configuration provided by the network node 110. Additionally, or alternatively, the network node 110 may signal the mapping of wake-up levels to sleep states to the UE 120 (e.g., when the network node 110 has knowledge of wake-up latencies associated with the MR of the UE 120). Thus, in some aspects, the UE 120 may transmit information that indicates approximate wake-up latencies, where each approximate wake-up latency is associated with a respective sleep state. In some such aspects, the network node 110 can determine and configure a permitted wake-up latency for each wake-up level. [0134] Fig. 7B illustrates examples associated with mapping wake-up levels to sleep states as described herein. The upper table in Fig. 7B is an example of wake-up level and full wake-up latency mapping (e.g., as determined by the UE 120 or as signaled by the network node 110). As shown in the upper table Fig. 7B, wake-up level 0 is mapped to a deep sleep state, and a permissible latency associated with wake-up level 0 is 10 ms. As further shown, wake-up level 1 is mapped to a light sleep state, and a latency associated with wake-up level 1 is 3 ms. As further shown, wake-up level 2 is mapped to a micro-sleep state, and a latency associated with wake-up level 2 is 1 slot. As further shown, wake-up level 3 is mapped to the active (i.e., fully awake) state, and there is no associated latency to wake-up. [0135] The lower table in Fig. 7B is an example of permitted inter-wake-up level switching latencies. In some aspects, such a table can be signaled to the UE 120 in order to enable the UE 120 to map wake-up levels to achievable sleep states of the UE 120. Further, such a table implicitly signals a time after which the network node 110 can assume that a switch in wake-up level from a given wake-up level to another wake-up level has been completed. In this example, as shown in the row corresponding to wake-up level 0, a permitted latency between wake-up level 0 and wake-up level 1 is 5 ms, a permitted latency between wake-up level 0 and wake-up level 2 is 10 ms, and a permitted latency between wake-up level 0 and wake-up level 3 is 10 ms. As shown in the row corresponding to wake-up level 1, a permitted latency between wake-up level 1 and wake-up level 0 is 5 ms, a permitted latency between wake-up level 1 and wake-up level is 3 ms, and a permitted latency between wake-up level 1 and wake-up level 3 is 1 slot. As shown in the row corresponding to wake-up level 2, a permitted latency between wake-up level 2 and wake-up level 0 is 10 ms, a permitted latency between wake-up level and wake-up level 1 is 3 ms, and a permitted latency between wake-up level 2 and wake-up level 3 is 1 slot. As shown in the row corresponding to wake-up level 3, a permitted latency between wake-up level 3 and wake-up level 0 is 10 ms, a permitted latency between wake-up level 3 and wake-up level 1 is 3 ms, and a permitted latency between wake-up level 3 and wake-up level 2 is 1 slot. [0136] In some aspects, the UE 120 may receive the indication of the wake-up level in a CDRX configuration. That is, the wake-up level indication can be provided in a CDRX configuration so that the UE 120 (automatically) move the MR to the desired wake-up level at a particular point in time (e.g., after receiving an LP-WUS) when configured for a particular CDRX configuration (among multiple CDRX configurations). In some aspects, such a technique reduces signaling from the network node 110 each time the MR of the UE 120 is to wake. In some aspects, such CDRX configurations can be received via, for example, RRC signaling or DCI. In some aspects, different default wake-up levels can be configured for different phases of CDRX (e.g., ON duration, inactivity timer duration, re-transmission timer expiration, or the like). [0137] In some aspects, the UE 120 performs continuous monitoring for signals including wake-up level indications during a period of time. Additionally, or alternatively, the UE 120 may perform duty-cycle monitoring for signals including wake-up level indications during the period of time. In some aspects, a CDRX configuration can specify the manner in which the UE 120 monitors for wake-up level indications while MR is not in the active state (e.g., continuously, in duty-cycle mode at specific locations, or the like). [0138] Returning to Fig. 7A, as shown at reference 704, the UE 120 may cause the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. For example, after receiving the signal indicating the wake-up level, the LR may identify the sleep state associated with the wake-up level (e.g., based at least in part on the mapping described above), and may send a trigger signal 706 that causes the MR to move from the first sleep state to the second sleep state. As shown in Fig. 7A, and the MR may then move from the first sleep state to the second sleep state accordingly. [0139] In some aspects, after receiving the wake-up level indication, the MR of the UE 120 is caused to move from the first sleep state to the second sleep state after a period of time corresponding to a relaxed wake-up latency value. For example, upon receiving the signal indicating the wake-up level, the UE 120 may cause the MR to move from the first sleep state to the second sleep state with a relaxed latency of, for example, a milliseconds (e.g., a period of time during which no grant will arrive at the UE 120). In some aspects, if the wake-up level indication is carried on a LP-WUS, the relaxed wake-up latency enables the MR to sleep for a longer amount of time before wake-up is needed, thereby conserving power. In some aspects, the UE 120 may receive a configuration indicating the relaxed wake-up latency value via, for example, RRC signaling, DCI, or the signal including the indication of the wake-up level itself. For example, in some aspects, multiple relaxed wake-up latency values can be configured via RRC or DCI, and one of the multiple relaxed wake-up latency values can be indicated in the signal that carries the indication of the wake-up level. [0140] In some aspects, the second sleep state corresponds to the wake-up level or to another wake-up level associated with a wake-up latency that is shorter than a wake-up latency associated with the wake-up level. That is, the indication of the wake-up level does not preclude the UE 120 from waking the MR to a wake-up level that is higher than the requested wake-up level. For example, the indicated wake-up level may be a wake-up level with a 3 ms wake-up latency. Here, the UE 120 may be permitted to move the MR to any sleep state that has a wake-up latency that is less than or equal to 3 ms. [0141] In some aspects, the UE 120 may receive a second signal including an indication of a second wake-up level, based at least in part on which the MR of the UE 120 is to operate, and may cause the MR to move from the second sleep state to a third sleep state based at least in part on the second wake-up level. That is, the UE 120 may receive multiple (time-spaced) wake-up level indications (e.g., at time t0 → wake-up level 1, then at time t1 > t0 → wake-up level 2, then at time t2 > t1 → wake-up level 3). id="p-142" id="p-142" id="p-142" id="p-142" id="p-142"

[0142] In some aspects, a wake-up latency associated with the second sleep state is longer than a wake-up latency associated with the first sleep state. That is, in some aspects, the wake-up level indication cause the MR to move from a higher wake-up level to a lower wake-up level. [0143] In some aspects, the UE 120 may cause the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on no additional wake-up level indication being received within a particular period of time. That is, the wake-up indication can cause the UE 120 to move the MR to a particular wake-up level (e.g., wake-up level i) and then, if no further wake-up indication is received during a particular period of time Tswitch, the MR may automatically move the MR to another wake-up level (e.g., wake-up level j). Here, wake-up level i may be higher or lower than wake-up level j (i.e., the UE 120 can be scheduled to go from a higher sleep state to a lower sleep state or vice-a-versa after the period of time Tswitch of inactivity). In some aspects, the value of Tswitch can be configured via, for example, RRC signaling or DCI, or may be indicated in the signal along with the indication of the wake-up level. Similarly, the value of the sleep state j can be configured (e.g., j = 0 (deep sleep) or j = (active state)) via, for example, RRC signaling or DCI, or may be indicated in the signal including the indication of the wake-up level. [0144] In some aspects, the UE 120 may cause the MR of the UE 120 to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on expiration of a timer. For example, the UE 120 can be configured with one or more rules to allow automatic wake-up level switching (e.g., from a higher wake-up level to a lower wake-up level) upon expiration of a particular CDRX timer (e.g., an inactivity timer). In some aspects, such a technique enables the UE 120 to maintain a legacy behavior –not monitoring for DCI outside an inactivity timer duration (e.g., automatically switching to wake-up level 0 (deep sleep) upon expiration of the inactivity timer). [0145] In this way, the UE 120 may receive a signal including an indication of a wake-up level at which an MR of the UE 120 is to operate, and may cause the MR of the UE 120 to move from a first sleep state to a second sleep state based at least in part on the wake-up level. In some aspects, this multi-level wake-up indication enables the degree to which the MR of the UE 120 is in a sleep state to be controlled so as to enable the UE 1to conserve power through additional or "deeper" sleep, thereby conserving battery power of the UE 120. id="p-146" id="p-146" id="p-146" id="p-146" id="p-146"

[0146] Fig. 7C is a diagram illustrating an example of operation of the LR and the MR of the UE 120 according to the process described with respect to Fig. 7A. [0147] As shown, the LR of the UE 120 receives a signal 708 (e.g., a first LP-WUS) including an indication that the MR of the UE 120 is to move to wake-up level 1. Notably, the MR of the UE 120 is operating at wake-up level 0 (corresponding to a deep sleep state) at the time at which the signal 708 is received by the LR. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the deep sleep state to a light sleep state (which corresponds to wake-up level 1) such that the MR is in the light sleep state after a time period twu (e.g., which may correspond to a relaxed wake-up latency value configured for the UE 120). [0148] As further shown, in this example, the LR of the UE 120 receives a signal 7(e.g., a second LP-WUS) including an indication that the MR of the UE 120 is to move to wake-up level 3. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the light sleep state to the active state (which corresponds to wake-up level 3) at a particular point in time during an ON duration TON of a CDRX period. [0149] As further shown, the MR of the UE 120 receives a signal 712 (e.g., a PDCCH-based indication) including an indication that the MR of the UE 120 is to move to wake-up level 2. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the active state to a micro-sleep state (which corresponds to wake-up level 2) at the end of the ON duration TON. As further shown, the UE 120 may start an inactivity timer (e.g., a time period with a duration of tinactivity). [0150] As further shown, in this example, the LR of the UE 120 receives a signal 7(e.g., a third LP-WUS) including an indication that the MR of the UE 120 is to move to wake-up level 1. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the micro-sleep state to the light state (which corresponds to wake-up level 1) at a particular point in time during the inactivity period. As further shown, the UE 120 may receive no further wake-up level indications during the inactivity period, and may cause the MR to move from the light sleep state to the deep sleep state upon expiration of the inactivity timer. [0151] Fig. 7D is a diagram illustrating an example of operation of the LR and the MR of the UE 120 in a scenario in which additional data is to be transmitted to the UE 1within a CDRX cycle after a first data transmission during the CDRX cycle. id="p-152" id="p-152" id="p-152" id="p-152" id="p-152"

[0152] As shown, the LR of the UE 120 receives a signal 716 (e.g., a first LP-WUS) including an indication that the MR of the UE 120 is to move to wake-up level 3. Notably, the MR of the UE 120 is operating at wake-up level 0 (corresponding to a deep sleep state) at the time at which the signal 716 is received by the LR. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the deep sleep state (corresponding to wake-up level 0) to an active state (corresponding to wake-up level 3). [0153] As further shown, the MR of the UE 120 receives a signal 718 (e.g., a first PDCCH-based indication) including an indication that the MR of the UE 120 is to move to wake-up level 1. Based at least in part on the wake-up level indication, the UE 1may cause the MR to move from the active state to the light sleep state (corresponding to wake-up level 1) (e.g., at the end of a CDRX ON duration). [0154] In this example, the network node 110 needs to transmit additional data to the UE 120 and, therefore, as shown, the LR of the UE 120 receives a signal 720 (e.g., a second LP-WUS) including an indication that the MR of the UE 120 is to move to wake-up level 3. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the light sleep state back to the active state. [0155] As further shown, the MR of the UE 120 then receives a signal 722 (e.g., a second PDCCH-based indication) including an indication that the MR of the UE 120 is to move to wake-up level 0. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the active state to the deep sleep state (corresponding to wake-up level 0) for a remainder of the CDRX cycle. By using the above described signaling, the network may allow the UE 120 to save power by going to light sleep between the two data reception locations. [0156] Fig. 7E is a diagram illustrating an example of operation of the LR and the MR of the UE 120 in a scenario in which no additional data is to be transmitted to the UE 1within a CDRX cycle after a first data transmission during the CDRX cycle. [0157] As shown, the LR of the UE 120 receives a signal 724 (e.g., a first LP-WUS) including an indication that the MR of the UE 120 is to move to wake-up level 3. Notably, the MR of the UE 120 is operating at wake-up level 0 (corresponding to a deep sleep state) at the time at which the signal 724 is received by the LR. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the deep sleep state (corresponding to wake-up level 0) to an active state (corresponding to wake-up level 3). [0158] As further shown, the MR of the UE 120 receives a signal 726 (e.g., a PDCCH-based indication) including an indication that the MR of the UE 120 is to move to wake-up level 1. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the active state to the light sleep state (corresponding to wake-up level 1) (e.g., at the end of a CDRX ON duration). As an example scenario, the network may signal the UE 120 to move to light sleep state as a compromise between saving power at the UE 120 and achieving reduced wake-up latency in case further data for the UE 120 arrives. [0159] In this example, the network node 110 does not need to transmit additional data to the UE 120 and, therefore, as shown, the LR of the UE 120 receives a signal 728 (e.g., a second LP-WUS), at a later time than the signal 726, including an indication that the MR of the UE 120 is to move to wake-up level 0. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the light sleep state to the deep sleep state (corresponding to wake-up level 0) for a remainder of the CDRX cycle. [0160] Figs. 7F and 7G are diagrams illustrating examples of operation of the LR and the MR of the UE 120 in scenarios in which rule-based (automatic) sleep state switching of the MR is configured. The example shown in Fig. 7F is an example associated with a high-to-low sleep state rule-based switch, while the example shown in Fig. 7G is an example associated with a low-to-high sleep state rule-based switch. [0161] As shown in the left diagram of Fig. 7F, the LR of the UE 120 receives a signal 730 (e.g., a first LP-WUS) including an indication that the MR of the UE 120 is to move to wake-up level 3. Further, the signal 730 indicates that the MR is to move to a particular wake-up level j after a period of time Tswitch. In this example, Tswitch is configured as 5 ms and wake-up level j is configured as wake-up level 0. Notably, the MR of the UE 120 is operating at wake-up level 0 (corresponding to a deep sleep state) at the time at which the signal 730 is received by the LR. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the deep sleep state (corresponding to wake-up level 0) to an active state (corresponding to wake-up level 3). [0162] In the scenario illustrated in the upper right diagram of Fig. 7F, the LR does not receive another indication within the time period Tswitch. Therefore, at the end of the time period Tswitch, the UE 120 causes the MR to move from the active state to the deep sleep state (which corresponds to wake-up level 0). [0163] Conversely, in the scenario illustrated in the lower right diagram of Fig. 7F, the LR receives a signal 732 (e.g., a second LP-WUS), within Tswitch time period of the signal 730, including an indication that the MR of the UE 120 is to move to wake-up level 3. The signal 732 also indicates that the MR is to move to a particular wake-up level j after a period of time Tswitch, with Tswitch being configured as 5 ms and the wake-up level j is configured as wake-up level 0. Here, the automatic high-to-low sleep state switch configured by the signal 730 is overridden, and the MR remains in the active state for an additional 5 ms based at least in part on the signal 732. The LR does not receive another indication within the second occurrence of the time period Tswitch and, therefore, causes the MR to move from the active state to the deep sleep state (which corresponds to wake-up level 0) at the end of the second occurrence of the time period Tswitch. [0164] As shown in the left diagram of Fig. 7G, the LR of the UE 120 receives a signal 734 (e.g., a first LP-WUS) including an indication that the MR of the UE 120 is to move to wake-up level 1. Further, the signal 734 indicates that the MR is to move to a particular wake-up level j after a period of time Tswitch. In this example, Tswitch is configured as 5 ms and wake-up level j is configured as wake-up level 3. Notably, the MR of the UE 120 is operating at wake-up level 0 (corresponding to a deep sleep state) at the time at which the signal 734 is received by the LR. Based at least in part on the wake-up level indication, the UE 120 may cause the MR to move from the deep sleep state (corresponding to wake-up level 0) to a light sleep state (corresponding to wake-up level 1). [0165] In the scenario illustrated in the upper right diagram of Fig. 7G, the LR does not receive another indication within the time period Tswitch. Therefore, at the end of the time period Tswitch, the UE 120 causes the MR to move from the light sleep state to the active state (which corresponds to wake-up level 3). [0166] Conversely, in the scenario illustrated in the lower right diagram of Fig. 7G, the LR receives a signal 736 (e.g., a second LP-WUS), within the time period Tswitch of the signal 734, including an indication that the MR of the UE 120 is to move to wake-up level 1. The signal 736 also indicates that the MR is to move to a particular wake-up level j after a period of time Tswitch, with Tswitch being configured as 5 ms and the wake-up level j is configured as wake-up level 3. Here, the automatic low-to-high sleep state switch configured by the signal 734 is overridden, and the MR remains in the light sleep state for an additional 5 ms based at least in part on the signal 736. The LR does not receive another indication within the second occurrence of the time period Tswitch and, therefore, causes the MR to move from the light sleep state to the active state (which corresponds to wake-up level 3) at the end of the second occurrence of the time period Tswitch. [0167] As indicated above, Figs. 7A-7G are provided as examples. Other examples may differ from what is described with respect to Figs. 7A-7G. [0168] Fig. 8 is a diagram illustrating an example process 800 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 800 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with wake-up signaling using an LR. [0169] As shown in Fig. 8, in some aspects, process 800 may include monitoring for an activation signal during an active duration of a CDRX cycle, wherein the monitoring is performed using a using an LR of the UE (block 810). For example, the UE (e.g., using communication manager 1006, depicted in Fig. 10) may monitor for an activation signal during an active duration of a CDRX cycle, wherein the monitoring is performed using a using an LR of the UE, as described above. In some aspects, the monitoring is performed using a using a low-power receiver (LR) of the UE. [0170] As further shown in Fig. 8, in some aspects, process 800 may include receiving the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal (block 820). For example, the UE (e.g., using reception component 1002 and/or communication manager 1006, depicted in Fig. 10) may receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal, as described above. [0171] As further shown in Fig. 8, in some aspects, process 800 may include causing an MR of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal (block 830). For example, the UE (e.g., using communication manager 1006, depicted in Fig. 10) may cause an MR of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal, as described above. [0172] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein. id="p-173" id="p-173" id="p-173" id="p-173" id="p-173"

[0173] In a first aspect, the monitoring is performed after an LP-WUS is detected using the LR of the UE. [0174] In a second aspect, alone or in combination with the first aspect, process 8includes causing the MR to move from the second sleep state to the first sleep state after a period of time during which a communication operation is to occur . [0175] In a third aspect, alone or in combination with one or more of the first and second aspects, process 800 includes receiving a deactivation signal during the active duration of the CDRX cycle and using the LR of the UE, and causing the MR to move from the first sleep state to a third sleep state based at least in part on the deactivation signal. [0176] In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 800 includes refraining from monitoring for activation signals for a period of time after causing the MR to move from the first sleep state to the second sleep state. [0177] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, at least one of a payload capacity of the activation signal matches a payload capacity of the LP-WUS or a sequence type of the activation signal matches a sequence type of the LP-WUS. [0178] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 800 includes receiving a configuration indicating a duration of time that the MR is to remain in the second sleep state after moving to the second sleep state, wherein the indication of the duration of time is received in at least one of a CDRX parameter configuration or the activation signal, and causing the MR to remain in the second sleep state for the duration of time based at least in part on the configuration. [0179] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process 800 includes receiving a configuration indicating an activation latency threshold, wherein the first sleep state is configured such that an amount of time associated with causing the MR to move from the first sleep state to the second sleep state satisfies the activation latency threshold. [0180] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, monitoring for the activation signal comprises monitoring for the activation signal during one or more periods of time that are indicated in an activation signal configuration. id="p-181" id="p-181" id="p-181" id="p-181" id="p-181"

[0181] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, monitoring for the activation signal comprises performing continuous monitoring during a period of time associated with monitoring for the activation signal or performing duty-cycle monitoring during the period of time associated with monitoring for the activation signal. [0182] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 800 includes activating or deactivating activation signal monitoring based at least in part on an indication received on the MR via at least one of RRC signaling, DCI, a MAC CE, or a payload of another activation signal received on the LR. [0183] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 800 includes transmitting capability information indicating a capability of the UE with respect to monitoring for activation signals. [0184] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the activation signal comprises a payload carrying information associated with a PDCCH to be received using the MR of the UE while the MR is in an active state. In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the first sleep state is defined by a first wake-up latency that represents a first amount of time required for the MR transition to a state in which the MR is ready to communicate and the second sleep state is defined by a second wake-up latency represents a second amount of time required for the MR transition to a state in which the MR is ready to communicate. [0185] Although Fig. 8 shows example blocks of process 800, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel. [0186] Fig. 9 is a diagram illustrating an example process 900 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 900 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with wake-up signaling using an LR. [0187] As shown in Fig. 9, in some aspects, process 900 may include receiving a signal including an indication of a wake-up level at which an MR of the UE is to operate, wherein the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and wherein each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states (block 910). For example, the UE (e.g., using reception component 1002 and/or communication manager 1006, depicted in Fig. 10) may receive a signal including an indication of a wake-up level at which an MR of the UE is to operate, wherein the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and wherein each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states, as described above. [0188] As further shown in Fig. 9, in some aspects, process 900 may include causing the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level (block 920). For example, the UE (e.g., using communication manager 1006, depicted in Fig. 10) may cause the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level, as described above. [0189] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein. [0190] In a first aspect, the MR of the UE is caused to move from the first sleep state to the second sleep state after a period of time corresponding to a relaxed wake-up latency value. [0191] In a second aspect, alone or in combination with the first aspect, process 9includes receiving a configuration indicating the relaxed wake-up latency value via at least one of RRC signaling, DCI, or the signal including the indication of the wake-up level. [0192] In a third aspect, alone or in combination with one or more of the first and second aspects, process 900 includes receiving a configuration that permits the UE to map each wake-up level in the plurality of wake-up levels to a respective sleep state in the plurality of sleep states, wherein the configuration is received via at least one of RRC signaling or DCI. [0193] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the configuration indicates an allowable wake-up latency associated with a change from a given wake-up level of the plurality of wake-up levels to one or more other wake-up levels of the plurality of wake-up levels. [0194] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 900 includes transmitting information that indicates a plurality of approximate wake-up latencies, each approximate wake-up latency in the plurality of approximate wake-up latencies being associated with a respective sleep state in the plurality of sleep states. [0195] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the signal including the indication of the wake-up level is an LP-WUS and is received using an LR of the UE. [0196] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the signal including the indication of the wake-up level is a PDCCH-based WUS and is received using the MR of the UE. [0197] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the second sleep state corresponds to the wake-up level or to another wake-up level associated with a wake-up latency that is shorter than a wake-up latency associated with the wake-up level. [0198] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process 900 includes receiving a second signal including an indication of a second wake-up level of the plurality of wake-up levels based at least in part on which the MR of the UE is to operate, and causing the MR of the UE to move from the second sleep state to a third sleep state of the plurality of sleep states based at least in part on the second wake-up level. [0199] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a wake-up latency associated with the second sleep state is longer than a wake-up latency associated with the first sleep state. [0200] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 900 includes causing the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on no additional wake-up level indication being received within a particular period of time. id="p-201" id="p-201" id="p-201" id="p-201" id="p-201"

[0201] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the indication of the wake-up level is received in a CDRX configuration. [0202] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process 900 includes causing the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on expiration of a timer. [0203] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process 900 includes performing continuous monitoring for signals including wake-up level indications during a period of time or performing duty-cycle monitoring for signals including wake-up level indications during the period of time. [0204] Although Fig. 9 shows example blocks of process 900, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel. [0205] Fig. 10 is a diagram of an example apparatus 1000 for wireless communication, in accordance with the present disclosure. The apparatus 1000 may be a UE, or a UE may include the apparatus 1000. In some aspects, the apparatus 1000 includes a reception component 1002, a transmission component 1004, and/or a communication manager 1006, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager 1006 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 1000 may communicate with another apparatus 1008, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1002 and the transmission component 1004. [0206] In some aspects, the apparatus 1000 may be configured to perform one or more operations described herein in connection with Figs. 6A-6D or 7A-7G. Additionally, or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as process 800 of Fig. 8, process 900 of Fig. 9, or a combination thereof. In some aspects, the apparatus 1000 and/or one or more components shown in Fig. 10 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 10 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component. [0207] The reception component 1002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1008. The reception component 1002 may provide received communications to one or more other components of the apparatus 1000. In some aspects, the reception component 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1000. In some aspects, the reception component 1002 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection with Fig. 2. [0208] The transmission component 1004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1008. In some aspects, one or more other components of the apparatus 1000 may generate communications and may provide the generated communications to the transmission component 1004 for transmission to the apparatus 1008. In some aspects, the transmission component 1004 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1008. In some aspects, the transmission component 1004 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 1004 may be co-located with the reception component 1002 in one or more transceivers. [0209] The communication manager 1006 may support operations of the reception component 1002 and/or the transmission component 1004. For example, the communication manager 1006 may receive information associated with configuring reception of communications by the reception component 1002 and/or transmission of communications by the transmission component 1004. Additionally, or alternatively, the communication manager 1006 may generate and/or provide control information to the reception component 1002 and/or the transmission component 1004 to control reception and/or transmission of communications. [0210] The communication manager 1006 may monitor for an activation signal during an active duration of a CDRX cycle wherein the monitoring is performed using a using an LR of the UE. The reception component 1002 may receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal. The communication manager 1006 may cause an MR of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal. [0211] The communication manager 1006 may cause the MR to move from the second sleep state to the first sleep state after a period of time during which a communication operation is to occur. [0212] The reception component 1002 may receive a deactivation signal during the active duration of the CDRX cycle and using the LR of the UE. [0213] The communication manager 1006 may cause the MR to move from the first sleep state to a third sleep state based at least in part on the deactivation signal. [0214] The communication manager 1006 may refrain from monitoring for activation signals for a period of time after causing the MR to move from the first sleep state to the second sleep state. [0215] The reception component 1002 may receive a configuration indicating a duration of time that the MR is to remain in the second sleep state after moving to the second sleep state wherein the indication of the duration of time is received in at least one of a CDRX parameter configuration or the activation signal. [0216] The communication manager 1006 may cause the MR to remain in the second sleep state for the duration of time based at least in part on the configuration. id="p-217" id="p-217" id="p-217" id="p-217" id="p-217"

[0217] The reception component 1002 may receive a configuration indicating an activation latency threshold, wherein the first sleep state is configured such that an amount of time associated with causing the MR to move from the first sleep state to the second sleep state satisfies the activation latency threshold. [0218] The communication manager 1006 may activate or deactivating activation signal monitoring based at least in part on an indication received on the MR via at least one of RRC signaling, DCI, a MAC CE, or a payload of another activation signal received on the LR. [0219] The transmission component 1004 may transmit capability information indicating a capability of the UE with respect to monitoring for activation signals. [0220] In some aspects, the reception component 1002 may receive a signal including an indication of a wake-up level at which an MR of the UE is to operate wherein the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and wherein each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states. The communication manager 1006 may cause the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. [0221] The reception component 1002 may receive a configuration indicating the relaxed wake-up latency value via at least one of RRC signaling, DCI, or the signal including the indication of the wake-up level. [0222] The reception component 1002 may receive a configuration that permits the UE to map each wake-up level in the plurality of wake-up levels to a respective sleep state in the plurality of sleep states, wherein the configuration is received via at least one of RRC signaling or DCI. [0223] The transmission component 1004 may transmit information that indicates a plurality of approximate wake-up latencies, each approximate wake-up latency in the plurality of approximate wake-up latencies being associated with a respective sleep state in the plurality of sleep states. [0224] The reception component 1002 may receive a second signal including an indication of a second wake-up level of the plurality of wake-up levels based at least in part on which the MR of the UE is to operate. id="p-225" id="p-225" id="p-225" id="p-225" id="p-225"

[0225] The communication manager 1006 may cause the MR of the UE to move from the second sleep state to a third sleep state of the plurality of sleep states based at least in part on the second wake-up level. [0226] The communication manager 1006 may cause the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on no additional wake-up level indication being received within a particular period of time. [0227] The communication manager 1006 may cause the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on expiration of a timer. [0228] The communication manager 1006 may perform continuous monitoring for signals including wake-up level indications during a period of time or performing duty-cycle monitoring for signals including wake-up level indications during the period of time. [0229] The number and arrangement of components shown in Fig. 10 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 10. Furthermore, two or more components shown in Fig. 10 may be implemented within a single component, or a single component shown in Fig. 10 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 10 may perform one or more functions described as being performed by another set of components shown in Fig. 10. [0230] The following provides an overview of some Aspects of the present disclosure: [0231] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: monitoring for an activation signal during an active duration of a connected mode discontinuous reception (CDRX) cycle, wherein the monitoring is performed using a using a low-power receiver (LR) of the UE; receiving the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal; and causing a main radio (MR) of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal. [0232] Aspect 2: The method of Aspect 1, wherein the monitoring is performed after a low-power wake-up signal (LP-WUS) is detected using the LR of the UE. id="p-233" id="p-233" id="p-233" id="p-233" id="p-233"

[0233] Aspect 3: The method of any of Aspects 1-2, further comprising causing the MR to move from the second sleep state to the first sleep state after a period of time during which a communication operation is to occur . [0234] Aspect 4: The method of Aspect 3, further comprising: receiving a deactivation signal during the active duration of the CDRX cycle and using the LR of the UE, and causing the MR to move from the first sleep state to a third sleep state based at least in part on the deactivation signal. [0235] Aspect 5: The method of any of Aspects 1-4, further comprising refraining from monitoring for activation signals for a period of time after causing the MR to move from the first sleep state to the second sleep state. [0236] Aspect 6: The method of any of Aspects 1-5, wherein at least one of a payload capacity of the activation signal matches a payload capacity of the LP-WUS or a sequence type of the activation signal matches a sequence type of the LP-WUS. [0237] Aspect 7: The method of any of Aspects 1-6, further comprising: receiving a configuration indicating a duration of time that the MR is to remain in the second sleep state after moving to the second sleep state, wherein the indication of the duration of time is received in at least one of a CDRX parameter configuration or the activation signal, and causing the MR to remain in the second sleep state for the duration of time based at least in part on the configuration. [0238] Aspect 8: The method of any of Aspects 1-7, further comprising receiving a configuration indicating an activation latency threshold, wherein the first sleep state is configured such that an amount of time associated with causing the MR to move from the first sleep state to the second sleep state satisfies the activation latency threshold. [0239] Aspect 9: The method of any of Aspects 1-8, wherein monitoring for the activation signal comprises monitoring for the activation signal during one or more periods of time that are indicated in an activation signal configuration. [0240] Aspect 10: The method of any of Aspects 1-9, wherein monitoring for the activation signal comprises performing continuous monitoring during a period of time associated with monitoring for the activation signal or performing duty-cycle monitoring during the period of time associated with monitoring for the activation signal. [0241] Aspect 11: The method of any of Aspects 1-10, further comprising activating or deactivating activation signal monitoring based at least in part on an indication received on the MR via at least one of radio resource control (RRC) signaling, downlink control information (DCI), a medium access control (MAC) control element (CE), or a payload of another activation signal received on the LR. [0242] Aspect 12: The method of any of Aspects 1-11, further comprising transmitting capability information indicating a capability of the UE with respect to monitoring for activation signals. [0243] Aspect 13: The method of any of Aspects 1-12, wherein the activation signal comprises a payload carrying information associated with a physical downlink control channel (PDCCH) to be received using the MR of the UE while the MR is in an active state. [0244] Aspect 14: The method of any of Aspects 1-13, wherein the first sleep state is defined by a first wake-up latency that represents a first amount of time required for the MR transition to a state in which the MR is ready to communicate and the second sleep state is defined by a second wake-up latency represents a second amount of time required for the MR transition to a state in which the MR is ready to communicate. [0245] Aspect 15: A method of wireless communication performed by a user equipment (UE), comprising: receiving a signal including an indication of a wake-up level at which a main radio (MR) of the UE is to operate, wherein the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and wherein each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states; and causing the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level. [0246] Aspect 16: The method of Aspect 15, wherein the MR of the UE is caused to move from the first sleep state to the second sleep state after a period of time corresponding to a relaxed wake-up latency value. [0247] Aspect 17: The method of Aspect 16, further comprising receiving a configuration indicating the relaxed wake-up latency value via at least one of radio resource control (RRC) signaling, downlink control information (DCI), or the signal including the indication of the wake-up level. [0248] Aspect 18: The method of any of Aspects 15-17, further comprising receiving a configuration that permits the UE to map each wake-up level in the plurality of wake-up levels to a respective sleep state in the plurality of sleep states, wherein the configuration is received via at least one of radio resource control (RRC) signaling or downlink control information (DCI). [0249] Aspect 19: The method of Aspect 18, wherein the configuration indicates an allowable wake-up latency associated with a change from a given wake-up level of the plurality of wake-up levels to one or more other wake-up levels of the plurality of wake-up levels. [0250] Aspect 20: The method of any of Aspects 15-19, further comprising transmitting information that indicates a plurality of approximate wake-up latencies, each approximate wake-up latency in the plurality of approximate wake-up latencies being associated with a respective sleep state in the plurality of sleep states. [0251] Aspect 21: The method of any of Aspects 15-20, wherein the signal including the indication of the wake-up level is a low-power wake-up signal (LP-WUS) and is received using a low-power receiver (LR) of the UE. [0252] Aspect 22: The method of any of Aspects 15-21, wherein the signal including the indication of the wake-up level is a physical downlink control channel (PDCCH)-based wake-up signal (WUS) and is received using the MR of the UE. [0253] Aspect 23: The method of any of Aspects 15-22, wherein the second sleep state corresponds to the wake-up level or to another wake-up level associated with a wake-up latency that is shorter than a wake-up latency associated with the wake-up level. [0254] Aspect 24: The method of any of Aspects 15-23, further comprising: receiving a second signal including an indication of a second wake-up level of the plurality of wake-up levels based at least in part on which the MR of the UE is to operate; and causing the MR of the UE to move from the second sleep state to a third sleep state of the plurality of sleep states based at least in part on the second wake-up level. [0255] Aspect 25: The method of any of Aspects 15-24, wherein a wake-up latency associated with the second sleep state is longer than a wake-up latency associated with the first sleep state. [0256] Aspect 26: The method of any of Aspects 15-25, further comprising causing the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on no additional wake-up level indication being received within a particular period of time. id="p-257" id="p-257" id="p-257" id="p-257" id="p-257"

[0257] Aspect 27: The method of any of Aspects 15-26, wherein the indication of the wake-up level is received in a connected mode discontinuous reception (CDRX) configuration. [0258] Aspect 28: The method of any of Aspects 15-27, further comprising causing the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on expiration of a timer. [0259] Aspect 29: The method of any of Aspects 15-28, further comprising performing continuous monitoring for signals including wake-up level indications during a period of time or performing duty-cycle monitoring for signals including wake-up level indications during the period of time. [0260] Aspect 30: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-29. [0261] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-29. [0262] Aspect 32: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-28. [0263] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-29. [0264] Aspect 34: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-29. [0265] Aspect 35: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-29. id="p-266" id="p-266" id="p-266" id="p-266" id="p-266"

[0266] Aspect 36: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-29. [0267] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. [0268] As used herein, the term "component" is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. "Software" shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise. [0269] As used herein, "satisfying a threshold" may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples. [0270] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of: a, b, or c" is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c). [0271] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Further, as used herein, the article "the" is intended to include one or more items referenced in connection with the article "the" and may be used interchangeably with "the one or more." Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more." Where only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, the terms "has," "have," "having," and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element "having" A may also have B). Further, the phrase "based on" is intended to mean "based on or otherwise in association with" unless explicitly stated otherwise. Also, as used herein, the term "or" is intended to be inclusive when used in a series and may be used interchangeably with "and/or," unless explicitly stated otherwise (for example, if used in combination with "either" or "only one of"). It should be understood that "one or more" is equivalent to "at least one." [0272] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.

ABSTRACT Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may monitor for an activation signal during an active duration of a connected mode discontinuous reception (CDRX) cycle, wherein the monitoring is performed using a using a low-power receiver (LR) of the UE. The UE may receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal. The UE may cause a main radio (MR) of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal. Numerous other aspects are described.

Claims

1. WHAT IS CLAIMED IS: 1. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the UE to: monitor for an activation signal during an active duration of a connected mode discontinuous reception (CDRX) cycle, wherein the monitoring is performed using a using a low-power receiver (LR) of the UE; receive the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal; and cause a main radio (MR) of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal.

2. The UE of claim 1, wherein the monitoring is performed after a low-power wake-up signal (LP-WUS) is detected using the LR of the UE.

3. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to cause the MR to move from the second sleep state to the first sleep state after a period of time during which a communication operation is to occur .

4. The UE of claim 3, wherein the one or more processors are further configured to cause the UE to: receive a deactivation signal during the active duration of the CDRX cycle and using the LR of the UE, and cause the MR to move from the first sleep state to a third sleep state based at least in part on the deactivation signal.

5. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to refrain from monitoring for activation signals for a period of time after causing the MR to move from the first sleep state to the second sleep state.

6. The UE of claim 1, wherein at least one of a payload capacity of the activation signal matches a payload capacity of a low power wake-up signal (LP-WUS) or a sequence type of the activation signal matches a sequence type of the LP-WUS.

7. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: receive a configuration indicating a duration of time that the MR is to remain in the second sleep state after moving to the second sleep state, wherein the indication of the duration of time is received in at least one of a CDRX parameter configuration or the activation signal, and cause the MR to remain in the second sleep state for the duration of time based at least in part on the configuration.

8. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to receive a configuration indicating an activation latency threshold, wherein the first sleep state is configured such that an amount of time associated with causing the MR to move from the first sleep state to the second sleep state satisfies the activation latency threshold.

9. The UE of claim 1, wherein the one or more processors, to cause the UE to monitor for the activation signal, are configured to cause the UE to monitor for the activation signal during one or more periods of time that are indicated in an activation signal configuration.

10. The UE of claim 1, wherein the one or more processors, to cause the UE to monitor for the activation signal, are configured to cause the UE to perform continuous monitoring during a period of time associated with monitoring for the activation signal or performing duty-cycle monitoring during the period of time associated with monitoring for the activation signal.

11. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to activate or deactivating activation signal monitoring based at least in part on an indication received on the MR via at least one of radio resource control (RRC) signaling, downlink control information (DCI), a medium access control (MAC) control element (CE), or a payload of another activation signal received on the LR.

12. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to transmit capability information indicating a capability of the UE with respect to monitoring for activation signals.

13. The UE of claim 1, wherein the activation signal comprises a payload carrying information associated with a physical downlink control channel (PDCCH) to be received using the MR of the UE while the MR is in an active state.

14. The UE of claim 1, wherein the first sleep state is defined by a first wake-up latency that represents a first amount of time required for the MR transition to a state in which the MR is ready to communicate and the second sleep state is defined by a second wake-up latency represents a second amount of time required for the MR transition to a state in which the MR is ready to communicate.

15. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the UE to: receive a signal including an indication of a wake-up level at which a main radio (MR) of the UE is to operate, wherein the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and wherein each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states; and cause the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level.

16. The UE of claim 15, wherein the MR of the UE is caused to move from the first sleep state to the second sleep state after a period of time corresponding to a relaxed wake-up latency value.

17. The UE of claim 16, wherein the one or more processors are further configured to cause the UE to receive a configuration indicating the relaxed wake-up latency value via at least one of radio resource control (RRC) signaling, downlink control information (DCI), or the signal including the indication of the wake-up level.

18. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to receive a configuration that permits the UE to map each wake-up level in the plurality of wake-up levels to a respective sleep state in the plurality of sleep states, wherein the configuration is received via at least one of radio resource control (RRC) signaling or downlink control information (DCI).

19. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to transmit information that indicates a plurality of approximate wake-up latencies, each approximate wake-up latency in the plurality of approximate wake-up latencies being associated with a respective sleep state in the plurality of sleep states.

20. The UE of claim 15, wherein the signal including the indication of the wake-up level is a low-power wake-up signal (LP-WUS) and is received using a low-power receiver (LR) of the UE.

21. The UE of claim 15, wherein the signal including the indication of the wake-up level is a physical downlink control channel (PDCCH)-based wake-up signal (WUS) and is received using the MR of the UE.

22. The UE of claim 15, wherein the second sleep state corresponds to the wake-up level or to another wake-up level associated with a wake-up latency that is shorter than a wake-up latency associated with the wake-up level.

23. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to: receive a second signal including an indication of a second wake-up level of the plurality of wake-up levels based at least in part on which the MR of the UE is to operate; and cause the MR of the UE to move from the second sleep state to a third sleep state of the plurality of sleep states based at least in part on the second wake-up level.

24. The UE of claim 15, wherein a wake-up latency associated with the second sleep state is longer than a wake-up latency associated with the first sleep state.

25. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to cause the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on no additional wake-up level indication being received within a particular period of time.

26. The UE of claim 15, wherein the indication of the wake-up level is received in a connected mode discontinuous reception (CDRX) configuration.

27. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to cause the MR of the UE to move from the second sleep state to another sleep state of the plurality of sleep states based at least in part on expiration of a timer.

28. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to perform continuous monitoring for signals including wake-up level indications during a period of time or performing duty-cycle monitoring for signals including wake-up level indications during the period of time.

29. A method of wireless communication performed by a user equipment (UE), comprising: monitoring for an activation signal during an active duration of a connected mode discontinuous reception (CDRX) cycle, wherein the monitoring is performed using a using a low-power receiver (LR) of the UE; receiving the activation signal during the active duration of the CDRX cycle based at least in part on monitoring for the activation signal; and causing a main radio (MR) of the UE to move from a first sleep state to a second sleep state based at least in part on the activation signal.

30. A method of wireless communication performed by a user equipment (UE), comprising: receiving a signal including an indication of a wake-up level at which a main radio (MR) of the UE is to operate, wherein the wake-up level is one of a plurality of wake-up levels, each wake-up level in the plurality of wake-up levels being associated with a different wake-up latency, and wherein each wake-up level in the plurality of wake-up levels is associated with a respective sleep state in a plurality of sleep states; and causing the MR of the UE to move from a first sleep state of the plurality of sleep states to a second sleep state of the plurality of sleep states based at least in part on the wake-up level.