Low power wake-up signal skipping

Abstract

Methods, systems, and apparatus for conducting wireless communication are described. A user equipment (UE) can receive a signal via its low-power radio component or its main radio component, indicating that the UE will skip monitoring one or more low-power wake-up signals using the low-power radio component. In some examples, the signal may be a low-power wake-up signal indicating a payload. The payload may indicate a skip pattern or a skip duration. In some examples, the signal may be a control signal, such as downlink control information. The UE can skip monitoring one or more low-power wake-up signals based on the signal.

Description

Cross-references

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 403,016, filed January 3, 2024, entitled “LOW POWER WAKEUP SIGNAL SKIPPING”, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0002] The following discussion pertains to wireless communication, including low-power wake-up signal skipping. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses supporting low-power wake-up signal skipping. For example, the described technology allows a user equipment (UE) to skip monitoring low-power wake-up signals using its low-power radio components. A network entity can send a signal instructing the UE to skip monitoring low-power wake-up signals. In some examples, the network entity can send a low-power wake-up signal instructing the UE to skip monitoring it. For example, a sequence carried by the low-power wake-up signal or resources used to send the low-power wake-up signal can instruct the UE to skip monitoring it. In some examples, the network entity can send control signaling for the UE's main radio components instructing the UE to skip the low-power wake-up signal. The network entity can instruct the UE to skip monitoring low-power wake-up signals according to a specific pattern or periodicity. For example, the network entity can instruct the UE to monitor every fourth low-power wake-up signal (e.g., skip monitoring every remaining low-power wake-up signal), or the network entity can instruct the UE to skip an indicated number of DRX cycles for monitoring low-power wake-up signals. In some examples, the UE can send a request to skip monitoring low-power wake-up times based on its battery level or service conditions at the UE. These techniques can reduce power consumption at the UE because it can expend less energy monitoring low-power wake-up signals.

[0005] A method for wireless communication by a UE is described. The method may include: receiving a signal via a low-power radio component of the UE or a main radio component of the UE, the signal indicating that the UE will skip using the low-power radio component to monitor one or more low-power wake-up signals; and skipping the monitoring of the one or more low-power wake-up signals based on the signal.

[0006] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the UE to: receive a signal via a low-power radio component or a main radio component of the UE, the signal indicating that the UE will skip using the low-power radio component to monitor one or more low-power wake-up signals; and skip monitoring of the one or more low-power wake-up signals based on the signal.

[0007] Another UE for wireless communication is described. The UE may include: a component for receiving a signal via a low-power radio component or a main radio component of the UE, the signal indicating that the UE will skip using the low-power radio component to monitor one or more low-power wake-up signals; and a component for skipping the monitoring of the one or more low-power wake-up signals based on the signal.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a signal via a low-power radio component of the UE or the main radio component of the UE, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals; and skip monitoring of the one or more low-power wake-up signals based on the signal.

[0009] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving the signal may include operations, features, components, or instructions for performing the following actions: receiving a low-power wake-up signal via the low-power radio component of the UE, the low-power wake-up signal indicating that the UE may skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the low-power wake-up signal may be received via one or more resources, and one or more indices of the one or more resources indicate skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the one or more resources correspond to time resources, frequency resources, spatial resources, or any combination thereof.

[0012] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: receiving control signaling indicating a set of multiple resources including the one or more resources; and monitoring the low-power wake-up signal via the set of multiple resources based on the control signaling.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the low-power wake-up signal includes one or more modulated bits that indicate that the UE may skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0014] The methods described herein, examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for performing the following actions: using an envelope detector to detect the low-power wake-up signal.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the low-power wake-up signal includes a sequence, and the sequence index of the sequence indicates skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

[0016] The methods described herein, some examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for receiving control signaling that indicates one or more sequence indices including at least the sequence index and one or more corresponding wake-up signal skip parameter sets.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the low-power wake-up signal indicates the identifier of the UE, a group identifier corresponding to a set of multiple UEs, a cell identifier, a tracking area identifier, or any combination thereof.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving the signal may include operations, features, components, or instructions for performing actions such as receiving a control signal via the main radio component of the UE that indicates that the UE may skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0019] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving a low-power wake-up signal during a low-power wake-up signal monitoring period indicated by the control signal, wherein powering down the low-power radio component may be based on receiving the low-power wake-up signal.

[0020] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for powering down the main radio component based on receiving the control signal without receiving a downlink data message associated with the control signal.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, skipping the monitoring may include operations, features, components, or instructions for performing the following actions: skipping the monitoring of one or more low-power wake-up signals based on the absence of a threshold number of consecutive low-power wake-up signals.

[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the signal indicates a pattern for skipping the monitoring of one or more low-power wake-up signals, the duration for skipping the monitoring of one or more low-power wake-up signals, the timing of monitoring one or more low-power wake-up signals, or any combination thereof.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, skipping the monitoring may include operations, features, components, or instructions for performing the following action: skipping a set of multiple low-power wake-up signals, wherein the signal may indicate the number of such sets of multiple low-power wake-up signals.

[0024] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing actions such as receiving an instruction to resume monitoring of a low-power wake-up signal; and monitoring the low-power wake-up signal based on the instruction to resume monitoring.

[0025] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for sending a request for the signal indicating that the UE may skip using the low-power radio component to monitor the one or more low-power wake-up signals, wherein the signal may be received based on the request.

[0026] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the request may be sent based on the UE's battery status, the service status at the UE, or both.

[0027] A method for wireless communication by a network entity is described. The method may include: sending a signal to a UE equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals; and avoiding sending the one or more low-power wake-up signals to the low-power radio component of the UE based on sending the signal.

[0028] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the network entity: sends a signal to a UE equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals; and avoids sending the one or more low-power wake-up signals to the low-power radio component of the UE based on sending the signal.

[0029] Another network entity for wireless communication is described. This network entity may include: components for transmitting a signal to a UE equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals; and components for avoiding transmitting the one or more low-power wake-up signals to the low-power radio component of the UE based on transmitting the signal.

[0030] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: send a signal to a UE equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals; and based on sending the signal, avoid sending the one or more low-power wake-up signals to the low-power radio component of the UE.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the signal may include operations, features, components, or instructions to perform the following actions: sending a low-power wake-up signal to the low-power radio component of the UE, the low-power wake-up signal indicating that the UE may skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the low-power wake-up signal may be transmitted via one or more resources, and one or more indices of the one or more resources indicate skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more resources correspond to time resources, frequency resources, spatial resources, or any combination thereof.

[0034] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending control signaling indicating a set of multiple resources including the one or more resources, wherein the low-power wake-up signal may be sent via the one or more resources based on the control signaling.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the low-power wake-up signal comprises a sequence, and the sequence index of the sequence indicates skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

[0036] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing actions such as sending control signaling that indicates one or more sequence indices including at least the sequence index and one or more corresponding wake-up signal skip parameter sets.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the low-power wake-up signal indicates the UE's identifier, a group identifier corresponding to a set of multiple UEs, a cell identifier, a tracking area identifier, or any combination thereof.

[0038] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the signal may include operations, features, components, or instructions for performing the following actions: sending a control signal to the main radio component of the UE, the control signal indicating that the UE may skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0039] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a low-power wake-up signal during a low-power wake-up signal monitoring period, wherein the control signal indicates the low-power wake-up signal monitoring period.

[0040] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the signal indicates a pattern for skipping the monitoring of one or more low-power wake-up signals, the duration for skipping the monitoring of one or more low-power wake-up signals, the timing of monitoring one or more low-power wake-up signals, or any combination thereof.

[0041] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a request for a signal indicating that the UE may skip using the low-power radio component to monitor the one or more low-power wake-up signals, wherein the signal may be sent based on the request.

[0042] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the request indicates the battery status of the UE, the service status at the UE, or both. Attached Figure Description

[0043] Figure 1 An example of a wireless communication system supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0044] Figure 2 An example of a wireless communication system supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0045] Figure 3 An example of a skip instruction supporting low-power wake-up signal skipping is shown according to one or more aspects of this disclosure.

[0046] Figure 4 An example of a skip configuration supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0047] Figure 5 An example of a skip instruction supporting low-power wake-up signal skipping is shown according to one or more aspects of this disclosure.

[0048] Figure 6 An example of a skip instruction supporting low-power wake-up signal skipping is shown according to one or more aspects of this disclosure.

[0049] Figure 7 An example of a process flow supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0050] Figure 8 and Figure 9 A block diagram of a device supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0051] Figure 10 A block diagram of a communication manager supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0052] Figure 11A diagram of a system including a device that supports low-power wake-up signal skipping, according to one or more aspects of this disclosure, is shown.

[0053] Figure 12 and Figure 13 A block diagram of a device supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0054] Figure 14 A block diagram of a communication manager supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0055] Figure 15 A diagram of a system including a device that supports low-power wake-up signal skipping, according to one or more aspects of this disclosure, is shown.

[0056] Figures 16 to 19 A flowchart illustrating a method for supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. Detailed Implementation

[0057] A user equipment (UE) may be equipped with a low-power radio component and a main radio component. The UE can operate in a low-power state and use the low-power radio component to monitor for low-power wake-up signals. For example, the UE may monitor for low-power wake-up signals during the "on" duration of a discontinuous reception (DRX) cycle. When the UE receives a low-power wake-up signal, it may power the main radio component to use it for transmitting or receiving signaling. In some cases, the UE may operate according to a connection mode DRX cycle with short periods, allowing the UE to frequently wake up the low-power radio component to monitor for low-power wake-up signals. While monitoring with the low-power radio component may use less power than monitoring with the main radio component, frequent use of the low-power radio component to monitor for low-power wake-up signals (even when there is no traffic to the UE) may increase power consumption at the UE.

[0058] Network entities can instruct the UE to skip monitoring for low-power wake-up signals using low-power radio components. In some examples, the network entity can send a low-power wake-up signal that instructs the UE to skip monitoring. For example, a sequence carried by the low-power wake-up signal or resources used to send the signal can instruct the UE to skip monitoring. In some examples, the network entity can send control signaling for the UE's main radio component, which can instruct the UE to skip monitoring. The network entity can instruct the UE to skip monitoring based on a specific pattern or periodicity. For example, the network entity can instruct the UE to monitor every fourth DRX cycle (e.g., skip monitoring DRX cycles one by one), or it can instruct the UE to skip monitoring for the next N DRX cycles. In some examples, the UE can send a request to skip monitoring based on its battery level or service conditions at the UE. These techniques can reduce power consumption at the UE, as the UE consumes energy while monitoring for low-power wake-up signals.

[0059] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to low-power wake-up signal skipping.

[0060] Figure 1 An example of a wireless communication system 100 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0061] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0062] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0063] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0064] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0065] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0066] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0067] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0068] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0069] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0070] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0071] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0072] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support low-power wake-up signal skipping as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0073] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0074] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1As shown.

[0075] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0076] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0077] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0078] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0079] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0080] It can support one or more sets of parameters for a carrier, and the parameter sets may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0081] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0082] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0083] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0084] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0085] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0086] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0087] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0088] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0089] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0090] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0091] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0092] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0093] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0094] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0095] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0096] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

[0097] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0098] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0099] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0100] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0101] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0102] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0103] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback on beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0104] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0105] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0106] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0107] In some wireless communication systems (such as IoT systems), UE 115 can operate in idle mode, where power consumption at UE 115 is primarily spent monitoring paging signaling. Some wireless communication systems support low-power wake-up signals, and UE 115 can be equipped with low-power radio components or low-power receivers. Low-power radio components can use significantly less power than the main radio components. UE 115 can use low-power radio components to monitor low-power wake-up signals instead of downlink control information and continue sleeping or operating in low-power mode until UE 115 receives a low-power wake-up signal. UE 115 can also use low-power radio components to monitor other low-power signaling, such as low-power synchronization signals. In some examples, using low-power radio components to monitor low-power wake-up signals can save power. In some examples, low-power radio components can be used to perform radio resource management (RRM) techniques or signaling.

[0108] When operating in idle or connected mode, UE 115 can use low-power radio components and low-power wake-up signals. In some examples, the connected mode DRX periodicity can be faster than the idle mode DRX periodicity. For example, the connected mode DRX periodicity in frequency range 2 can correspond to milliseconds (e.g., 40 to 80 milliseconds), while the idle mode DRX periodicity can be several seconds long. UE 115 operating according to the connected mode DRX cycle can use low-power radio components to monitor low-power wake-up signals more frequently. However, UE 115 may not have any traffic to transmit or receive. UE 115 can use low-power radio components to monitor low-power wake-up signals frequently, but this may waste power consumption, especially when there is little or no traffic for UE 115.

[0109] In the wireless communication system described herein (such as wireless communication system 100), network entity 105 may instruct UE 115 to skip monitoring of low-power wake-up signals. For example, network entity 105 may instruct UE 115 to skip monitoring of low-power wake-up signals for a specific duration or according to a pattern. Network entity 105 may instruct a one-time skip (e.g., skip monitoring of low-power wake-up signals for the next N DRX cycles) or a pattern-based skip (e.g., monitor low-power wake-up signals every Nth DRX cycle and skip monitoring of other DRX cycles).

[0110] In some examples, network entity 105 may send a low-power wake-up signal that instructs UE 115 to skip monitoring. For example, resources used to send the low-power wake-up signal or the sequence used to send the low-power wake-up signal may indicate to UE 115 information associated with skipping monitoring of the low-power wake-up signal. In some examples, the low-power wake-up signal may carry modulated bits indicating information associated with skipping monitoring. The low-power wake-up signal may indicate a pattern or range for skipping monitoring of subsequent low-power wake-up signals.

[0111] In some examples, network entity 105 may send a control signal to the main radio component of UE 115, indicating information for skipping the monitoring of low-power wake-up signals using low-power radio components. For example, network entity 105 may send downlink control information or a MAC message (e.g., MAC CE) instructing UE 115 to skip monitoring low-power wake-up signals using low-power radio components. The control signal may indicate a pattern for skipping or a range for skipping.

[0112] Figure 2 An example of a wireless communication system 200 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or may be an example of, some aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network entity 105-a and UE 115-a, which may be corresponding examples of network entity 105 and UE 115 described herein.

[0113] UE 115-a may be equipped with a main radio component 205 and a low-power radio component 210. UE 115-a may use the main radio component 205 for higher-layer signaling (e.g., RRC signaling) and lower-layer signaling (e.g., physical layer signaling), such as control and data signaling. UE 115-a may use the low-power radio component 210 to monitor low-power signaling, such as low-power wake-up signals and low-power synchronization signals. In some examples, UE 115-a may use the low-power radio component 210 to conserve power when the main radio component 205 is in sleep mode. In some cases, UE 115-a may use both the low-power radio component 210 and the main radio component 205 simultaneously to improve the processing capabilities of UE 115-a.

[0114] The wireless communication system 200 can support techniques for allowing UE 115-a to skip monitoring low-power wake-up signals. For example, if there is little or no traffic for UE 115-a, network entity 105-a can send a signal 215 instructing UE 115-a to skip using low-power radio component 210 to monitor low-power wake-up signals. During idle or low-traffic periods, network entity 105-a can dynamically instruct UE 115-a not to expect wake-up signals, such as during the next duration T or for the next N DRX cycles, which allows UE 115-a to enter a lower power state or conserve power by not using low-power radio component 210 for monitoring.

[0115] For example, network entity 105-a can send signal 215 to UE 115-a, and signal 215 can instruct UE 115-a to skip monitoring for low-power wake-up signals using low-power radio component 210 for the next three DRX cycles. For example, UE 115-a can skip monitoring for low-power wake-up signals starting from low-power wake-up signal monitoring timing 220-a. After skipping monitoring for three DRX cycles, UE 115-a can resume monitoring for low-power wake-up signals. For example, UE 115-a can monitor for low-power wake-up signals during low-power wake-up signal monitoring timing 220-b.

[0116] In some examples, signal 215 may indicate a pattern or duration for skipping monitoring of the low-power wake-up signal. For example, signal 215 may indicate a pattern or duration for skipping monitoring. In some examples, signal 215 may indicate a one-time skip of monitoring. For example, signal 215 may indicate the duration or number of DRX cycles for which UE 115-a will skip monitoring of the low-power wake-up signal. For example, signal 215 may indicate that UE 115-a skips monitoring of the low-power wake-up signal for the next one, two, four, eight, etc. DRX cycles. Additionally or alternatively, signal 215 may indicate a pattern, and UE 115-a may skip monitoring of the low-power wake-up signal according to that pattern. For example, signal 215 may indicate that UE 115-a skips monitoring of the low-power wake-up signal every other DRX cycle, or the signal may indicate that UE 115-a monitors the low-power wake-up signal every fourth DRX cycle, and UE 115-a may skip monitoring of the low-power wake-up signal for the three DRX cycles in between. Other styles can be configurable, such as monitoring two DRX cycles and then skipping monitoring both DRX cycles, etc.

[0117] In some examples, signal 215 may instruct UE 115-a when to begin skipping monitoring for low-power wake-up signals using low-power radio component 210. For example, signal 215 may instruct UE 115-a to skip monitoring for low-power wake-up signals according to a pattern of monitoring one of four monitoring times, and signal 215 may instruct UE 115-a to begin skipping monitoring after two DRX cycles. For example, if UE 115-a receives signal 215 associated with the first DRX cycle, UE 115-a may monitor for low-power wake-up signals during the second, third, seventh, and eleventh DRX cycles.

[0118] In some examples, signal 215 may be a low-power wake-up signal. For example, network entity 105-a may send a low-power wake-up signal to UE 115-a, and the low-power wake-up signal may instruct UE 115-a to skip using low-power radio component 210 to monitor one or more low-power wake-up signals. Signal 215 may include, indicate, or specify information, which may be referred to as a payload. In some examples, the payload of signal 215 may refer to the actual information bits carried by signal 215. Additionally or alternatively, the payload of signal 215 may refer to information transmitted based on the transmission of signal 215, the characteristics of signal 215, the sequence of signal 215, or the modulation of signal 215, or any combination thereof. For example, a low-power wake-up signal may carry information (e.g., a payload) based on a selected sequence for a low-power wake-up signal or based on resource selection for a low-power wake-up signal.

[0119] In some examples, the payload of signal 215 may include an identifier for UE 115-a. For example, signal 215 may indicate a target-specific identifier for UE 115-a, or signal 215 may indicate a UE group identifier for one or more UEs 115. In some examples, the payload of signal 215 may include a skip indication for skipping low-power wake-up signals. For example, the payload of signal 215 may include skip type, skip duration, skip style, or any combination thereof. In some examples, the payload of signal 215 may include other information, such as (e.g., a cell identifier or tracking area identifier for network entity 105-a).

[0120] In some examples, the payload of the low-power wake-up signal (e.g., signal 215) can be indicated by on / off keying signaling. For example, a single bit of information can be transmitted by using or not using resources. For instance, if eight resource elements exist in the frequency domain for transmitting the low-power wake-up signal, network entity 105-a can transmit the low-power wake-up signal on the zeroth and third resource elements but not on the other resource elements. In this example, the first, second, and fourth through seventh resource elements can be turned off or not used for transmitting the low-power wake-up signal. The payload of the low-power wake-up signal can correspond to the bit sequence "00001001". For example, by turning the eight resources used for transmitting the low-power wake-up signal on or off, eight bits of information can be transmitted, representing up to 256 different configurations of the payload to indicate information such as skip pattern, skip duration, etc. Reference Figure 6 An example of using on / off keying to indicate the payload of signal 215 is described in more detail.

[0121] In some examples, the payload of a low-power wake-up signal (e.g., signal 215) can be indicated by index modulation. For example, information can be embedded in or correspond to the selection of resources used for communication. For example, the selection of frequency resources, time resources, antenna selection, or port selection can indicate the payload of signal 215. For example, network entity 105-a can... Choose one configuration from several options (e.g., frequency resources, time resources, antenna selection, port selection, etc.), and the selected configuration can indicate... Bits. For example, if there are eight possible configurations, the selected configuration can transmit three bits. If there are four bits available for sending a low-power wake-up signal... Frequency resources, and network entity 105-a selects the first frequency resource (e.g., This can indicate a two-bit sequence of "01". In some examples, the frequency resource can be a frequency sub-band. UE 115-a can receive low-power wake-up signals and uses an envelope detector or energy detector to detect the payload of the low-power wake-up signal. In some examples, UE 115-a can use coherent (e.g., channel phase-based) or incoherent (e.g., received energy-based) techniques to detect on / off keying and index modulation. In some examples, coherent techniques can provide an enhanced signal-to-noise ratio, but with higher complexity and power consumption.

[0122] In some examples, the payload of a low-power wake-up signal (e.g., signal 215) can be indicated by a sequence index. For example, an index of a sequence used for a low-power wake-up signal can be used to deliver information or payload. The sequence can be repeated across multiple time, frequency, or antenna port resources, which can provide enhanced coverage. The sequence can be, for example, a Zadoff-Chu sequence, a Golay sequence, an m-sequence, or a binary sequence. In some examples, network entity 105-a can utilize a sequence list to configure UE 115-a, and UE 115-a can monitor sequences in the list. In some examples, UE 115-a can use one or more correlators to detect sequences. For example, UE 115-a can receive signal 215 and can perform front-end processing on signal 215. UE 115-a can compare the received signal with different sequences. For example, UE 115-a can use a first correlator to compare the received signal with a first known sequence, and UE 115-a can use a second correlator to compare the received signal with a second known sequence. UE 115-a can compare the correlation with different known sequences or with a threshold. If the correlation between signal 215 and a known sequence meets the threshold, UE 115-a can demap the bit corresponding to the sequence index. For example, there can be four different sequences (which can indicate four different choices) or two bits. In some examples, sequence indexes, index modulation, on / off keying, or any combination thereof can be used to indicate additional information. For example, the sequence index can correspond to additional configurations used for index modulation.

[0123] In some examples, the payload of the low-power wake-up signal (e.g., signal 215) can be indicated by modulated bits. For example, the low-power wake-up signal can be any modulated bit from a known constellation, such as quadrature amplitude modulation (QAM). Before demodulating the bits of the low-power wake-up signal, a receiver (such as UE 115-a) can be trained on bits or samples to estimate the channel. Training bits or training samples can be included in the low-power wake-up signal or can be transmitted on different sequences or different signals. UE 115-a can receive the low-power wake-up signal, equalize the estimated channel, demodulate the low-power wake-up signal, and decode the bits. In some examples, UE 115-a can use an in-phase / quadrature-based receiver to receive the low-power wake-up signal. For example, network entity 105-a can generate a bit sequence (e.g., The modulated symbols are then mapped to the antenna ports of network entity 105-a. Network entity 105-a can perform a DFT or an inverse fast Fourier transform (IFFT) and send a low-power wake-up signal to UE 115-a. UE 115-a can receive the low-power wake-up signal and perform an inverse DFT (IDFT) or FFT on the received signal, use reference symbols to perform channel estimation and equalization, and demap the bits to obtain the information bits of the low-power wake-up signal.

[0124] In some examples, the low-power wake-up signal for signal 215 may update the skip pattern but not wake up the main radio components of UE 115-a. The payload of the low-power wake-up signal may update the skip pattern, duration, or configuration, but the low-power wake-up signal may not wake up UE 115-a. For example, a first low-power wake-up signal may instruct UE 115-a to wake up within the current DRX cycle and be monitored every other low-power wake-up signal. After several DRX cycles, the data buffer at UE 115-a or network entity 105-a may be exhausted (e.g., there may be no additional traffic for UE 115-a), and network entity 105-a may send a second low-power wake-up signal that does not wake up UE 115-a and configures UE 115-a to be monitored every fourth low-power wake-up signal. In some examples, the low-power wake-up signal that wakes up the main radio component 205 at UE 115-a may have a different sequence than the low-power wake-up signal that does not wake up the main radio component 205 at UE 115-a. Additionally or alternatively, the low-power wake-up signal that wakes up the main radio component 205 at UE 115-a may be modulated differently or transmitted using different resources than the low-power wake-up signal that does not wake up the main radio component 205 at UE 115-a.

[0125] In some examples, there may be a low-power wake-up signal monitoring periodicity for a specific pattern, or a default low-power wake-up signal monitoring periodicity. The periodicity may be a DRX periodicity (e.g., a connected DRX periodicity) or a different periodicity configured by network entity 105-a. For example, network entity 105-a may send an indication of the periodicity for low-power wake-up signal monitoring, such as via control signaling or signal 215. If a low-power wake-up signal indicates that UE 115-a wakes up its primary radio component (e.g., if data for UE 115-a arrives), the periodicity for monitoring the low-power wake-up signal may revert to the default monitoring periodicity. Additionally or alternatively, the low-power wake-up signal waking up the primary radio component at UE 115-a may indicate a different periodicity for monitoring the low-power wake-up signal.

[0126] UE 115-a can be configured with several skip configurations. In some examples, network entity 105-a can send control signaling indicating one or more skip configurations and corresponding payloads. For example, UE 115-a can be configured with a skip configuration corresponding to the first bit sequence. If the payload of the low-power wake-up signal indicates the first bit sequence, UE 115-a can perform low-power wake-up signal monitoring (e.g., or skip monitoring) according to the skip configuration corresponding to the first bit sequence. For example, for the payload of the low-power wake-up signal, there can be eight different bit sequences, and UE 115-a can be configured with eight different skip configurations corresponding to the eight different bit sequences. For example, a first skip configuration can indicate to start monitoring the low-power wake-up sequence in each DRX cycle, but without waking up the main radio component 205; a second skip configuration can indicate not waking up the main radio component and starting to skip every DRX cycle except every fourth DRX cycle (e.g., monitoring the low-power wake-up signal in every fourth DRX cycle); and a third skip configuration can indicate to skip monitoring the low-power wake-up signal for the next four DRX cycles. Other skip configurations or a number of skip configurations are also supported.

[0127] In some examples, UE 115-a can be configured to interpret the payload in a specific way. For example, UE 115-a can be configured to interpret the payload from a low-power wake-up signal. For instance, the payload of the low-power wake-up signal can be delivered via sequence modulation and index modulation, and the choice between sequence modulation and index modulation can correspond to different bits of the payload. UE 115-a can be configured to interpret, for example, the sequence as the most significant bit of the payload and the index modulation as the least significant bit of the payload. In some examples, network entity 105-a can configure UE 115-a to interpret the payload of a low-power wake-up signal.

[0128] In some examples, UE 115-a may be configured with or instructed to have a set of resources, such as when low-power wake-up signals use indexed modulation or on / off keying to deliver payloads. In some examples, UE 115-a may be configured with or instructed to have a set of sequences, such as when low-power wake-up signals use sequence indexing or sequence selection to deliver payloads. In some examples, network entity 105-a may send signaling to UE 115-a to indicate or configure resources or sequences, or both. In some examples, signaling may indicate a sequence or resource, or both, in-place pattern, or skip configuration, or a mapping between both.

[0129] UE 115-a may send a request to skip monitoring of low-power wake-up signals. For example, UE 115-a may send a request to network entity 105-a to skip monitoring of low-power wake-up signals according to a skip pattern or duration. In some examples, the request may indicate or identify a skip pattern or duration. The request may be based on traffic at UE 115-a, the traffic pattern of UE 115-a, the battery status at UE 115-a, or the expected battery status at UE 115-a, or any combination thereof. In some examples, network entity 105-a may send signal 215 in response to the request. The skip configuration or payload of signal 215 may be based on the requested skip pattern or duration.

[0130] In some examples, signal 215 may be transmitted via control signaling (such as downlink control information) or MAC signaling (such as MAC CE). For example, network entity 105-a may send downlink control information to UE 115-a instructing UE 115-a to skip monitoring one or more low-power wake-up signals using low-power radio component 210. Signal 215 may be, for example, downlink grant, dedicated downlink control information, or dedicated MAC CE, indicating information for skipping monitoring of one or more low-power wake-up signals. Signal 215, as downlink control information or MAC CE, may include information similar to the payload of a low-power wake-up signal, such as skip pattern, skip periodicity, duration for skipping monitoring, or any combination thereof. In some examples, network entity 105-a may send signal 215 to the main radio component 205 of UE 115-a when the main radio component 205 is already turned on (e.g., receiving data or available to receive data). UE 115-a can monitor signal 215 and other data during a connection DRX cycle, which includes a default on duration and an inactive timer.

[0131] In some examples, UE 115-a can be configured with a dedicated connection DRX configuration that does not have an inactivity timer or has a short inactivity timer, or has a periodicity for receiving signal 215 that differs from the default DRX periodicity. The main radio unit 205 of UE 115-a can wake up, receive downlink control information or MACCE (e.g., signal 215), and return to sleep without waiting for further downlink signaling reception (e.g., Physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (PDSCH) reception). The dedicated DRX configuration allows UE 115-a to receive signal 215 using minimum power.

[0132] Network entity 105-a can transmit both signals for the main radio component 205 and signals for the low-power radio component 210 to configure UE 115-a to skip monitoring low-power wake-up signals. For example, network entity 105-a can transmit an indication of a portion of the skip configuration or a low-periodic configuration via downlink control information, while the low-power wake-up signal can instruct UE 115-a to begin skipping. For example, network entity 105-a can transmit downlink control information to indicate the skip pattern or duration, and network entity 105-a can transmit a low-power wake-up signal (e.g., with a specific sequence or modulation or via a specific resource) to instruct UE 115-a to begin skipping monitoring low-power wake-up signals.

[0133] Network entity 105-a may send another signal instructing UE 115-a to resume monitoring the low-power wake-up signal or to stop skipping monitoring. For example, network entity 105-a may send a low-power wake-up signal instructing UE 115-a to resume monitoring the low-power wake-up signal. In some examples, UE 115-a may use a detector (e.g., main radio component 205) to detect the low-power wake-up signal without waking up low-power radio component 210, or network entity 105-a may send the low-power wake-up signal during a DRX cycle monitored by UE 115-a. In some examples, network entity 105-a may update the skip periodicity. For example, network entity 105-a may change the periodicity of the DRX cycle in which UE 115-a monitors the low-power wake-up signal, such as monitoring every cycle or monitoring with a periodicity different from the previously configured periodicity.

[0134] If UE 115-a is skipping the monitoring of low-power wake-up signals, network entity 105-a can avoid sending a low-power wake-up signal to UE 115-a. For example, network entity 105-a can configure UE 115-a to skip monitoring of low-power wake-up signals for the next four DRX cycles, and network entity 105-a can choose not to send a low-power wake-up signal for the next four DRX cycles. For example, after the second DRX cycle that UE 115-a is skipping, network entity 105-a may have pending data for UE 115-a. However, because UE 115-a is skipping the monitoring timing, network entity 105-a can wait until after the last skipped DRX cycle before sending a low-power wake-up signal.

[0135] In some examples, UE 115-a can begin skipping low-power wake-up signal monitoring based on the absence of a detected low-power wake-up signal. For example, if UE 115-a does not detect or receive a low-power wake-up signal within a threshold number of timeframes, UE 115-a can begin skipping low-power wake-up signal monitoring, which can further reduce power consumption. For example, if UE 115-a does not detect a low-power wake-up signal within 100 consecutive DRX cycles, UE 115-a can begin skipping low-power wake-up signal monitoring. In some examples, the skipping pattern based on the absence of a detected low-power wake-up signal can be configured by network entity 105-a or pre-configured at UE 115-a. In some examples, if UE 115-a continues to not detect a low-power wake-up signal, the skipping pattern can be modified to skip a larger number of monitoring timeframes. The amount of skipping can gradually increase as more idle time is detected or elapses. For example, UE 115-a can start by skipping every other monitoring opportunity, and if UE 115-a does not detect a low-power wake-up signal within another threshold number of DRX cycles, UE 115-a can start monitoring for a low-power wake-up signal every fourth DRX cycle. In some examples, UE 115-a can adjust its skipping pattern based on other factors, such as time of day. For example, when traffic is likely to be lower, UE 115-a can skip more aggressively at night (e.g., skip monitoring during a larger percentage of DRX cycles).

[0136] Skipping low-power wake-up monitoring can refer to skipping the monitoring of low-power wake-up signals within a DRX loop. A DRX loop can be a connected DRX loop in connected DRX mode or an idle DRX loop in idle mode. In some examples, the timing of skipping low-power wake-up signal monitoring may correspond to skipping the monitoring of low-power wake-up signals within a DRX loop.

[0137] Figure 3An example of a skip instruction 300 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0138] Network entity 105 may send a low-power wake-up signal to UE 115 at timing 315-a (e.g., a low-power wake-up signal timing), which instructs UE 115 to wake up its primary radio component 305. UE 115 may receive the low-power wake-up signal using low-power radio component 310 during timing 315-a. UE 115 may wake up its primary radio component 305 based on receiving the low-power wake-up signal at timing 315-a. For example, the low-power wake-up signal received during timing 315-a may have a payload "00", which may instruct UE 115 to wake up its primary radio component and stop skipping low-power wake-up signals. Network entity 105 may send data 320-a to UE 115, and UE 115 may use its primary radio component 305 to receive data 320-a. After receiving data 320-a using the main radio component 305, the UE 115 can enter a lower power state and shut down the main radio component 305 or reduce the power of the main radio component 305.

[0139] UE 115 can continue to monitor for low-power wake-up signals in subsequent DRX cycles. For example, UE 115 can monitor for low-power wake-up signals during times 315-b and 315-c. However, there may be no service for UE 115, and UE 115 may not receive or detect low-power wake-up signals during these two times 315.

[0140] Network entity 105 may send a signal to UE 115 instructing UE 115 to skip monitoring for low-power wake-up signals using low-power radio component 310. In the example of skip instruction 300, the signal may be a low-power wake-up signal. The low-power wake-up signal may include or indicate information, which may be referred to as a payload. The payload may include a UE identifier, a UE group identifier, information associated with the skip configuration (e.g., skip type, skip duration, or skip style), a cell identifier, a tracking area identifier, or any combination thereof. The payload may be carried or indicated via on / off keying, selection of a sequence of low-power wake-up signals, index modulation, or modulated bits, or any combination thereof. In some other examples, such as references Figure 5 The described skip indication 500 signal can be a downlink control signaling (e.g., downlink control information) or a MAC CE.

[0141] Network entity 105 may send a low-power wake-up signal during timing 315-d, which instructs UE 115 to skip monitoring for one or more low-power wake-up signals using low-power radio component 310. The wake-up signal in timing 315-d may indicate payload "11," which instructs UE 115 not to wake up main radio component 305 and to begin monitoring according to a first skip pattern. For example, a low-power wake-up signal received in timing 315-d may instruct UE 115 to perform monitoring every fourth DRX cycle, thereby skipping monitoring for low-power wake-up signals in the DRX cycles between every fourth DRX cycle. Based on the low-power wake-up signal received in timing 315-d, UE 115 may not monitor for low-power wake-up signals during timings 315-e, 315-f, or 315-g.

[0142] UE 115 can monitor for a low-power wake-up signal in timing 315-h, depending on the skip pattern. Network entity 105 can determine that there is pending data for UE 115, and network entity 105 can send a low-power wake-up signal in timing 315-h, which configures UE 115 to update the skip pattern or periodically. The low-power wake-up signal in timing 315-h may, for example, have a payload "01" indicating that UE 115 does not wake up the main radio component, but instead monitors according to a second skip pattern. For example, the low-power wake-up signal in timing 315-h may instruct UE 115 to resume monitoring for the low-power wake-up signal or to monitor for the low-power wake-up signal in each DRX cycle. UE 115 can monitor for the low-power wake-up signal in timing 315-i of the next DRX cycle. In some examples, network entity 105 may have pending data for UE 115 and may send a wake-up signal to UE 115 in timing 315-i. UE 115 can power the main radio component 305 based on receiving a low-power wake-up signal in timing 315-i, and use the main radio component 305 to receive data 320-b from the network entity.

[0143] Figure 4 Examples of skip patterns 400 and 401 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure are shown.

[0144] UE 115 can be configured to skip monitoring low-power wake-up signals or skip using low-power radio components to monitor low-power wake-up signals. For example, network entity 105 can send signal 415 to UE 115 indicating the monitoring pattern or skipping pattern for low-power wake-up signals.

[0145] In skip pattern 400, network entity 105 may send a signal 415-a to UE 115 indicating a first skip pattern. For example, signal 415-a may instruct UE 115 to monitor a low-power wake-up signal every fourth DRX cycle. In the example of skip pattern 400, every fourth DRX cycle may correspond to a monitored low-power wake-up signal timing 405. The three DRX cycles between monitored low-power wake-up signal timings 405 may correspond to skipped low-power wake-up signal timings 410. Skip pattern 400 may be an example of a pattern-based skipping technique. UE 115 may also be configured with other skip patterns, such as monitoring multiple consecutive DRX cycles and then skipping multiple consecutive DRX cycles.

[0146] In skip pattern 401, network entity 105 may send signal 415-b, which instructs UE 115 to skip monitoring low-power wake-up signals for the next N DRX cycles. For example, this signal may instruct UE 115 to skip monitoring low-power wake-up signals for the next four DRX cycles. The low-power wake-up signal timings in the four DRX cycles following the receipt of signal 415-b may correspond to the skipped low-power wake-up signal timing 410. After the four skipped timings, UE 115 may continue monitoring low-power wake-up signals (e.g., in the monitored low-power wake-up signal timing 405). Skip pattern 401 may be an example of a one-time skip or a single-skip pattern. In some examples, signal 415-b may indicate a duration or the number of DRX cycles.

[0147] In some examples, signal 415 may indicate the start time of skipping, such as by instructing UE 115 when to begin skipping low-power wake-up signals. For example, signal 415 may instruct UE 115 to begin skipping low-power wake-up signal monitoring after two DRX cycles.

[0148] Figure 5 An example of a skip instruction 500 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown.

[0149] Network entity 105 may send a low-power wake-up signal to UE 115 at timing 515-a (e.g., a low-power wake-up signal timing). The low-power wake-up signal may instruct UE 115 to wake up its primary radio component 505. UE 115 may receive the low-power wake-up signal using low-power radio component 510 during timing 515-a. UE 115 may wake up its primary radio component 505 based on receiving the low-power wake-up signal at timing 515-a and monitor control signaling or data signaling, or both, from the network entity.

[0150] For example, a network entity may send control signaling 520 to UE 115. Control signaling 520 may be an example of instructing UE 115 to skip monitoring for low-power wake-up signals using low-power radio components 510. For example, there may be little or no traffic targeting UE 115, and network entity 105 may instruct UE 115 to skip monitoring for low-power wake-up signals, which can reduce energy consumption at UE 115.

[0151] Control signaling 520 may include or indicate information associated with skipping the monitoring of low-power wake-up signals. For example, control signaling 520 may indicate a UE identifier, a UE group identifier, information associated with skip configuration (e.g., skip type, skip duration, or skip style), a cell identifier, a tracking area identifier, or any combination thereof.

[0152] In some examples, control signaling 520 may indicate the start time of the skip. For example, control signaling 520 may instruct UE 115 to begin skipping monitoring of low-power wake-up signals after an indicated time period, DRX cycle, or low-power wake-up signal timing. For example, control signaling 520 may indicate timing 515-d. In some other examples, UE 115 may begin skipping monitoring timing 515 in a DRX cycle after receiving control signaling 520.

[0153] UE 115 may monitor for a low-power wake-up signal during times 515-b and 515-c, but UE 115 may not detect a low-power wake-up signal during time 515. UE 115 may monitor for a low-power wake-up signal during time 515-d. In some examples, UE 115 may not receive a low-power wake-up signal during time 515-d, and UE 115 may begin to skip monitoring for a low-power wake-up signal using the low-power radio component 510. For example, UE 115 may begin to skip monitoring for a low-power wake-up signal based on a skip configuration (e.g., skip pattern or skip duration) indicated by control signaling 520.

[0154] In some examples, UE 115 may begin skipping the monitoring of low-power wake-up signals based on the fact that no low-power wake-up signal has been received before the indicated timing 515. For example, if UE 115 is to receive a low-power wake-up signal in timing 515-b or timing 515-c, UE 115 may not skip monitoring the low-power wake-up signal after timing 515-d.

[0155] In some examples, network entity 105 may transmit a low-power wake-up signal during timing 515-d. The low-power wake-up signal may indicate that the main radio component 505 should not be woken up, and that monitoring of the low-power wake-up signal should be skipped. For example, the sequence or modulation of the low-power wake-up signal transmitted during timing 515-d may indicate that the main radio component 505 should not be activated and that skipping monitoring should begin based on a skip configuration indicated by control signaling 520. In some examples, the low-power wake-up signal transmitted during timing 515-d may indicate information (e.g., payload), such as an updated or modified skip pattern or duration. For example, control signaling 520 may indicate a first portion of the skip configuration, and a wake-up signal received during timing 515-d may indicate a second portion of the skip configuration.

[0156] UE 115 can begin skipping monitoring of the low-power wake-up signal after timing 515-d. In some examples, control signaling 520 can instruct UE 115 to skip monitoring of the low-power wake-up signal for four consecutive DRX cycles. For example, UE 115 may not monitor the low-power wake-up signal in the DRX cycles corresponding to timings 515-e, 515-f, 515-g, or 515-h. After skipping the number of DRX cycles indicated by the monitoring instruction, UE 115 can resume monitoring.

[0157] For example, UE 115 may monitor for a low-power wake-up signal in the DRX cycle corresponding to timing 515-i. In some examples, network entity 105 may have already received pending data or control signaling for UE 115 when UE 115 is not monitoring for a low-power wake-up signal. Network entity 105 may send a low-power wake-up signal in timing 515-i, which may instruct UE 115 to wake up the primary radio component. In some other examples, network entity 105 may send a low-power wake-up signal in timing 515-i, which may instruct UE 115 to continue skipping the monitoring of the low-power wake-up signal.

[0158] In some examples, network entity 105 may not send a low-power wake-up signal in timing 515-i. UE 115 may continue monitoring for the low-power wake-up signal in subsequent timings, such as when control signaling 520 indicates a one-time skip duration of four DRX cycles. In some other examples, UE 115 may continue to skip monitoring for the low-power wake-up signal, such as when control signaling indicates a skip pattern instead of a one-time skip duration. In some other examples, UE 115 may continue to skip monitoring for the low-power wake-up signal based on the fact that no low-power wake-up signal was received in timing 515-i. For example, UE 115 may have detected that it has not received a low-power wake-up signal within a threshold number of timings 515, and UE 115 may continue to skip monitoring timings after timing 515-i.

[0159] Figure 6 Examples of skip configurations 600, 601, and 602 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure are shown.

[0160] UE 115 can be configured to skip monitoring low-power wake-up signals or skip using low-power radio components to monitor low-power wake-up signals. For example, network entity 105 can send a signal to UE 115 instructing the UE to skip using low-power radio components to monitor low-power wake-up signals. In some examples, this signal can be a low-power wake-up signal. The low-power wake-up signal can deliver or carry information or payloads such as skip configuration (e.g., skip pattern or skip duration), UE identifier, UE group identifier, cell identifier, tracking area identifier, or any combination thereof.

[0161] The payload of a low-power wake-up signal can be transmitted or carried through on / off keying, sequence selection, indexed modulation, or modulated bits. For example, skip configurations 600, 601, and 602 can each illustrate examples of using on / off keying to indicate the payload of a low-power wake-up signal. For example, a single bit can be transmitted by using or not using a resource to send the low-power wake-up signal. Using a resource can indicate a "1" bit, while not using a resource can indicate a "0" bit. For example, resource 605 used for sending a low-power wake-up signal can indicate a "1", while unused resource 610 for not sending a low-power wake-up signal can indicate a "0". For example, a "1" can correspond to sending a non-zero sample on a frequency set, while a "0" can correspond to keeping the frequency set off or not transmitting.

[0162] Skip configuration 600 can illustrate an example of on / off keying using frequency division multiplexing resources. The resource 605 used in skip configuration 600 can correspond to the second, fourth, and seventh resources, while the unused resource 610 in skip configuration 600 can correspond to the zeroth, first, third, fifth, and sixth resources. This can correspond to the bit sequence [0,0, 1, 0, 1, 0, 0, 1], which transmits eight bits of information.

[0163] Skip configuration 601 can illustrate an example of on / off keying using time-division multiplexing resources. The resources 605 used in skip configuration 600 can correspond to the first, fourth, and seventh resources, while the unused resources 610 in skip configuration 600 can correspond to the zeroth, second, third, fifth, and sixth resources. This can correspond to the bit sequence [0,1, 0, 0, 1, 0, 0, 1], which transmits eight bits of information.

[0164] Skip configuration 602 can illustrate an example of on / off keying using frequency division multiplexing resources and time division multiplexing resources. The resources 605 used in skip configuration 600 can correspond to the third, fourth, and seventh resources, while the unused resources 610 in skip configuration 600 can correspond to the zeroth, first, second, fifth, and sixth resources. This can correspond to a bit sequence of [0, 0, 0, 1, 1, 0, 0, 1], which transmits eight bits of information.

[0165] In some examples, UE 115 can be configured with multiple bit sequences and various skip configurations. For example, network entity 105 can send control signaling to UE 115 indicating the mapping between the bit sequences of the payload and the skip configurations. For example, the bit sequence indicated by skip configuration 600 may correspond to a first skip configuration. The first skip configuration may, for example, instruct UE 115 to skip using the low-power wake-up radio component to monitor for low-power wake-up signals according to a first skip pattern. In some examples, the skip configuration may include whether UE 115 should activate the primary radio component (e.g., to receive control signaling or data signaling) or not activate the primary radio component.

[0166] Similar techniques can be implemented using antenna elements or antenna ports for on / off keying. For example, One resource can be used for transmission. Bits. The UE 115 can use an energy detector to detect the bit pattern indicated by the on / off key.

[0167] Figure 7An example of a process flow 700 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. Process flow 700 may be implemented by UE 115-b or network entity 105-b, or both. UE 115-b and network entity 105-b may be as described in reference... Figure 1 and Figure 2 The corresponding examples of UE 115 and network entity 105 are described. In some examples, some signaling or procedures of process flow 700 may occur in a different order than presented. In some examples, some signaling or procedures shown may not occur, or some signaling or procedures not shown may occur, or both.

[0168] At point 715, network entity 105-b may send a skip instruction to UE 115-b. The skip instruction may indicate a skip configuration for UE 115-b to skip monitoring for low-power wake-up signals using low-power radio components. For example, UE 115-b may receive a signal via its low-power radio component or its main radio component instructing the UE to skip monitoring for one or more low-power wake-up signals using low-power radio components. This signal may indicate or specify the pattern of skipping monitoring for one or more low-power wake-up signals, the duration of skipping monitoring for one or more low-power wake-up signals, the timing of monitoring for one or more low-power wake-up signals, or any combination thereof.

[0169] In some examples, the signal may be a low-power wake-up signal. For example, UE 115-b may receive a low-power wake-up signal via its low-power radio component, which indicates that the UE will skip using the low-power radio component to monitor for one or more low-power wake-up signals. In some examples, the low-power wake-up signal may specify, indicate, or include a payload, wherein the payload indicates a skip configuration. For example, the payload may indicate a skip pattern or a skip duration. In some examples, the payload may indicate whether UE 115-b wants to wake up its main radio component.

[0170] In some examples, the payload of a low-power wake-up signal can be indicated via indexed modulation or on / off keying. For example, a low-power wake-up signal can be received via one or more resources, and one or more indices of one or more resources can indicate skipping the use of low-power radio components to monitor one or more low-power wake-up signals. In some examples, a single bit can be transmitted by using or not using a resource. In some examples, information can be embedded in the selection of resources used for communication (e.g., selection of time resources, frequency resources, spatial resources, antennas, or antenna ports).

[0171] In some examples, the payload of the low-power wake-up signal can be indicated via modulated bits. For example, the low-power wake-up signal may include one or more modulated bits that indicate that UE 115-b will skip using low-power radio components to monitor one or more low-power wake-up signals. For example, the low-power wake-up signal may be any modulated bits from a known constellation (such as a QAM constellation), rather than a known complex sequence or a known on / off key sequence. In some examples, UE 115-b may receive training bits or samples from network entity 105-b to estimate the channel before demodulating the low-power wake-up signal or bits in the low-power wake-up signal. Training samples may be sent with the low-power wake-up signal or separately.

[0172] In some examples, the payload of a low-power wake-up signal can be indicated via sequence selection. For example, a low-power wake-up signal can include a sequence, and the sequence index of the sequence can indicate skipping the use of low-power radio components to monitor one or more low-power wake-up signals.

[0173] In some examples, at 705, network entity 105-b can send control signaling to UE 115-b. In some examples, the control signaling can instruct one or more skip configurations or bit sequences, or skip the mapping between configurations and bit sequences. In some examples, the control signaling can instruct resources (e.g., for delivering payloads via on / off keying or indexed modulation), one or more sequences or sequence indices (e.g., for delivering payloads via sequence selection), one or more training signals, reference signals, bits or sequences (e.g., for delivering payloads via modulated bits), or any combination thereof.

[0174] For example, UE 115-b can receive control signaling indicating multiple resources. UE 115-b can monitor low-power wake-up signals via multiple resources. UE 115-b can determine the payload of the low-power wake-up signal based on the resources used to transmit the low-power wake-up signal.

[0175] Additionally or alternatively, UE 115-b may receive control signaling indicating one or more sequence indices. The low-power wake-up signal may include a sequence having sequence indices from one or more sequence indices, and UE 115-b may determine the payload of the low-power wake-up signal based on the sequence index corresponding to the sequence of the low-power wake-up signal.

[0176] In some examples, the signal can be control signaling. For example, UE 115-b can receive a control signal via its main radio component instructing UE 115-b to skip monitoring one or more low-power wake-up signals using the low-power radio component. The control signal can indicate a skip configuration, such as a skip pattern or skip duration. In some examples, the control signal can indicate the start time of the skip configuration. For example, the control signal can indicate that UE 115-b will begin skipping a monitored DRX cycle or a low-power wake-up signal monitoring timing. Downlink control information or MAC CE can be examples of control signaling.

[0177] In some examples, at 710, UE 115-b may send a request for a signal instructing the UE to skip using low-power radio components to monitor one or more low-power wake-up signals. For example, UE 115-b may send the request based on UE 115-b's battery state, service conditions at UE 115-b, expected battery state of UE 115-b, or expected service conditions of UE 115-b, or any combination thereof. In some examples, network entity 105-b may send a signal based on the request.

[0178] At 720, UE 115-b can skip monitoring of one or more low-power wake-up signals based on a signal. For example, UE 115-b can skip based on a skip pattern or skip duration indicated by the signal. For example, the signal can indicate skipping monitoring of low-power wake-up signals every other DRX cycle (e.g., a pattern-based skip configuration). UE 115-b can monitor low-power wake-up signals during low-power wake-up signal monitoring opportunities every other DRX cycle (e.g., skipping or not monitoring low-power wake-up signals during wake-up signal monitoring opportunities in other DRX cycles). In some examples, the signal can indicate skipping a certain number of DRX cycles (e.g., a one-time skip configuration). For example, the signal can indicate skipping monitoring for the next four DRX cycles. UE 115-b can skip monitoring low-power wake-up signals during low-power wake-up signal monitoring opportunities in the next four DRX cycles.

[0179] In some examples, UE 115-b can resume monitoring low-power wake-up signals. For instance, after a one-time skip configuration, UE 115-b can resume monitoring low-power wake-up signals at 725.

[0180] In some examples, at 730, network entity 105-b may send a low-power wake-up signal. In some examples, the low-power wake-up signal may update the skip configuration at UE 115-b. For example, the low-power wake-up signal may indicate a different skip pattern or skip duration. In some examples, the low-power wake-up signal may instruct UE 115-b to stop skipping monitoring for low-power wake-up signals. The low-power wake-up signal received at 730 may or may not wake up the main radio component of UE 115-b.

[0181] Figure 8 A block diagram 800 of a device 805 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0182] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with low-power wake-up signal skipping). The information may be delivered to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0183] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with low-power wake-up signal skipping). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0184] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of low-power wake-up signal skipping as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0185] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0186] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0187] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0188] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving signals via a low-power radio component of the UE or the UE's main radio component, the signals indicating that the UE will skip monitoring one or more low-power wake-up signals using the low-power radio component. The communication manager 820 may be capable of, configured to, or operable to support components for skipping monitoring of one or more low-power wake-up signals based on signals.

[0189] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption, such as by reducing monitoring at device 805.

[0190] Figure 9 A block diagram 900 of a device 905 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0191] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with low-power wake-up signal skipping). The information may be delivered to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0192] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with low-power wake-up signal skipping). In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0193] Device 905 or its various components may be examples of parts used to perform various aspects of low-power wake-up signal skipping as described herein. For example, communication manager 920 may include skip indication component 925, skip component 930, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0194] Communication manager 920 may support wireless communication according to examples disclosed herein. Skip indication component 925 is capable of, configured to, or operable to support components for receiving signals via the UE's low-power radio component or the UE's main radio component, indicating that the UE will skip monitoring one or more low-power wake-up signals using the low-power radio component. Skip component 930 is capable of, configured to, or operable to support components for skipping monitoring of one or more low-power wake-up signals based on signals.

[0195] Figure 10 A block diagram 1000 of a communication manager 1020 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of low-power wake-up signal skipping as described herein. For example, the communication manager 1020 may include a skip indication component 1025, a skip component 1030, a monitoring component 1035, a skip request component 1040, a skip configuration component 1045, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0196] Communication manager 1020 may support wireless communication according to examples disclosed herein. Skip indication component 1025 is capable of, configured to, or operable to support components for receiving signals via the UE's low-power radio component or the UE's main radio component, the signal indicating that the UE will skip monitoring one or more low-power wake-up signals using the low-power radio component. Skip component 1030 is capable of, configured to, or operable to support components for skipping monitoring of one or more low-power wake-up signals based on a signal.

[0197] In some examples, in order to support the reception of signals, the skip indication component 1025 is capable of, configured to, or able to operate to support the components for receiving low-power wake-up signals via the low-power radio components of the UE, which indicate that the UE will skip using the low-power radio components to monitor one or more low-power wake-up signals.

[0198] In some examples, low-power wake-up signals are received via one or more resources. In some examples, one or more indices of one or more resources indicate that low-power radio components are skipped when monitoring one or more low-power wake-up signals.

[0199] In some examples, one or more resources correspond to time resources, frequency resources, space resources, or any combination thereof.

[0200] In some examples, the skip configuration component 1045 is capable of, configured to, or operable to support components for receiving control signaling indicating a set of multiple resources including one or more resources. In some examples, the skip configuration component 1045 is capable of, configured to, or operable to support components for monitoring low-power wake-up signals based on control signaling via a set of multiple resources.

[0201] In some examples, the low-power wake-up signal includes one or more modulated bits that indicate that the UE will skip using low-power radio components to monitor one or more low-power wake-up signals.

[0202] In some examples, the skip indicator component 1025 is capable of, configured to, or able to operate to support components for using an envelope detector to detect low-power wake-up signals.

[0203] In some examples, the low-power wake-up signal includes a sequence. In some examples, the sequence index of the sequence indicates skipping the use of low-power radio components to monitor one or more low-power wake-up signals.

[0204] In some examples, the skip configuration component 1045 is capable of being configured or operated to support components for receiving control signaling that indicates at least one or more sequence indices of the sequence index and one or more corresponding wake-up signal skip parameter sets.

[0205] In some examples, the low-power wake-up signal indicates the UE's identifier, a group identifier corresponding to a set of multiple UEs, a cell identifier, a tracking area identifier, or any combination thereof.

[0206] In some examples, in order to support the reception of signals, the skip indication component 1025 is able to be configured or operated to support the component for receiving control signals via the UE’s main radio component, which instructs the UE to skip using low-power radio components to monitor one or more low-power wake-up signals.

[0207] In some examples, the skip indicator component 1025 is capable of, configured to, or able to operate to support components for receiving a low-power wake-up signal during a low-power wake-up signal monitoring period indicated by a control signal, wherein powering down the low-power radio component is based on receiving the low-power wake-up signal.

[0208] In some examples, the skip component 1030 is capable of, configured to, or able to operate to support a component for powering down the main radio component based on the receipt of a control signal without the receipt of a downlink data message associated with the control signal.

[0209] In some examples, to support skip monitoring, the skip component 1030 is capable of being configured or operated to support components for skipping the monitoring of one or more low-power wake-up signals based on a consecutive number of low-power wake-up signals that have not been received based on a threshold number.

[0210] In some examples, the signal indicates the pattern for skipping the monitoring of one or more low-power wake-up signals, the duration for skipping the monitoring of one or more low-power wake-up signals, the timing of monitoring one or more low-power wake-up signals, or any combination thereof.

[0211] In some examples, to support skip monitoring, the skip component 1030 is capable of being configured or operable to support components for skipping sets of multiple low-power wake-up signals, wherein the signal indicates the number of sets of multiple low-power wake-up signals.

[0212] In some examples, the monitoring component 1035 is capable of, configured to, or operable to support components for receiving indications of monitoring for recovery of low-power wake-up signals. In some examples, the monitoring component 1035 is capable of, configured to, or operable to support components for monitoring low-power wake-up signals based on indications of recovery monitoring.

[0213] In some examples, the skip request component 1040 is capable of, configured to, or able to operate to support a component for sending a request for a signal that instructs the UE to skip using low-power radio components to monitor one or more low-power wake-up signals, where the signal is received based on the request.

[0214] In some examples, the request is sent based on the UE's battery status, the service status at the UE, or both.

[0215] Figure 11 A diagram of a system 1100 including a device 1105 supporting low-power wake-up signal skipping, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may communicate electronically via one or more buses (e.g., bus 1145) or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0216] I / O controller 1110 manages the input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of one or more processors, such as at least one processor 1140. In some cases, a user may interact with the device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0217] In some cases, device 1105 may include a single antenna 1125. However, in other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125 as described herein, a wired link, or a wireless link. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be an example of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof as described herein.

[0218] At least one memory 1130 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1130 may store computer-readable, computer-executable code 1135, including instructions that, when executed by at least one processor 1140, cause device 1105 to perform the various functions described herein. Code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1135 may not be directly executable by at least one processor 1140, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1130 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0219] At least one processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1140. At least one processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1130) to cause device 1105 to perform various functions (e.g., various functions or tasks supporting low-power wake-up signal skipping). For example, device 1105 or components of device 1105 may include at least one processor 1140 and at least one memory 1130 coupled to or coupled to at least one processor 1140, at least one processor 1140 and at least one memory 1130 configured to perform various functions described herein. In some examples, at least one processor 1140 may include multiple processors, and at least one memory 1130 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1140 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1140) and memory circuitry (which may include at least one memory 1130)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1140 or a processing system including at least one processor 1140 may be configured, capable of being configured, or operable to cause device 1105 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” may be used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1130 or otherwise.

[0220] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving signals via a low-power radio component of the UE or the UE's main radio component, the signals indicating that the UE will skip monitoring one or more low-power wake-up signals using the low-power radio component. The communication manager 1120 may be capable of, configured to, or operable to support components for skipping monitoring of one or more low-power wake-up signals based on signals.

[0221] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support technologies for reducing power consumption and extending battery life.

[0222] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the transceiver 1115, one or more antennas 1125, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by at least one processor 1140, at least one memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions that can be executed by at least one processor 1140 to cause the device 1105 to perform various aspects of low-power wake-up signal skipping as described herein, or at least one processor 1140 and at least one memory 1130 may be otherwise configured to perform or support such operations individually or jointly.

[0223] Figure 12 A block diagram 1200 of a device 1205 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of network entity 105 as described herein. Device 1205 may include receiver 1210, transmitter 1215, and communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, and communication manager 1220) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0224] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0225] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0226] The communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of low-power wake-up signal skipping as described herein. For example, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0227] In some examples, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0228] Additionally or alternatively, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0229] In some examples, the communication manager 1220 may be configured to use the receiver 1210, the transmitter 1215, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated with the receiver 1210, the transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0230] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for transmitting a signal to a UE equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals. The communication manager 1220 may be capable of, configured to, or operable to support components for avoiding transmitting one or more low-power wake-up signals to the UE's low-power radio component based on the transmitted signal.

[0231] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 (e.g., controlling receiver 1210, transmitter 1215, communication manager 1220, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for reducing power consumption.

[0232] Figure 13 A block diagram 1300 of a device 1305 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. Device 1305 may be an example of aspects of device 1205 or network entity 105 as described herein. Device 1305 may include receiver 1310, transmitter 1315, and communication manager 1320. Device 1305 or one or more components of device 1305 (e.g., receiver 1310, transmitter 1315, and communication manager 1320) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0233] Receiver 1310 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1305. In some examples, receiver 1310 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0234] Transmitter 1315 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0235] Device 1305 or its various components may be examples of parts for performing various aspects of low-power wake-up signal skipping as described herein. For example, communication manager 1320 may include skip indication component 1325, transmission avoidance component 1330, or any combination thereof. Communication manager 1320 may be examples of aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to use receiver 1310, transmitter 1315, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in combination with receiver 1310, transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0236] Communication manager 1320 may support wireless communication according to examples disclosed herein. Skip indication component 1325 is capable of, configured to, or operable to support components for transmitting a signal to a UE equipped with low-power radio components and a main radio component, indicating that the UE will skip using the low-power radio components to monitor one or more low-power wake-up signals. Transmission avoidance component 1330 is capable of, configured to, or operable to support components for avoiding transmitting one or more low-power wake-up signals to the UE's low-power radio components based on transmission signals.

[0237] Figure 14 A block diagram 1400 of a communication manager 1420 supporting low-power wake-up signal skipping according to one or more aspects of this disclosure is shown. The communication manager 1420 may be an example of aspects of the communication manager 1220, communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of parts for performing various aspects of low-power wake-up signal skipping as described herein. For example, the communication manager 1420 may include a skip indication component 1425, a transmission avoidance component 1430, a skip request component 1435, a skip configuration component 1440, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0238] Communication manager 1420 may support wireless communication according to examples disclosed herein. Skip indication component 1425 is capable of, configured to, or operable to support components for transmitting a signal to a UE equipped with low-power radio components and a main radio component, indicating that the UE will skip using the low-power radio components to monitor one or more low-power wake-up signals. Transmission avoidance component 1430 is capable of, configured to, or operable to support components for avoiding transmitting one or more low-power wake-up signals to the UE's low-power radio components based on transmission signals.

[0239] In some examples, to support the transmission of signals, the skip indication component 1425 is capable of, configured to, or able to operate to support components for transmitting low-power wake-up signals to the low-power radio components of the UE, which indicate that the UE will skip using the low-power radio components to monitor one or more low-power wake-up signals.

[0240] In some examples, the low-power wake-up signal is transmitted via one or more resources. In some examples, one or more indices of one or more resources indicate skipping the use of low-power radio components to monitor one or more low-power wake-up signals.

[0241] In some examples, one or more resources correspond to time resources, frequency resources, space resources, or any combination thereof.

[0242] In some examples, the skip configuration component 1440 is capable of, configured to, or able to operate to support components for sending control signaling indicating a set of multiple resources including one or more resources, wherein the low-power wake-up signal is sent based on the control signaling via one or more resources.

[0243] In some examples, the low-power wake-up signal includes a sequence. In some examples, the sequence index of the sequence indicates skipping the use of low-power radio components to monitor one or more low-power wake-up signals.

[0244] In some examples, the skip configuration component 1440 is capable of, configured to, or able to operate to support components for sending control signaling that indicates at least one or more sequence indices of the sequence index and one or more corresponding wake-up signal skip parameter sets.

[0245] In some examples, the low-power wake-up signal indicates the UE's identifier, a group identifier corresponding to a set of multiple UEs, a cell identifier, a tracking area identifier, or any combination thereof.

[0246] In some examples, to support the transmission of signals, the skip indication component 1425 is capable of, configured to, or able to operate to support components for transmitting control signals to the UE's main radio component, which instruct the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals.

[0247] In some examples, the skip indicator component 1425 is capable of, configured to, or able to operate to support components for sending a low-power wake-up signal during a low-power wake-up signal monitoring period, wherein a control signal indicates the low-power wake-up signal monitoring period.

[0248] In some examples, the signal indicates the pattern for skipping the monitoring of one or more low-power wake-up signals, the duration for skipping the monitoring of one or more low-power wake-up signals, the timing of monitoring one or more low-power wake-up signals, or any combination thereof.

[0249] In some examples, the skip request component 1435 is capable of, configured to, or able to operate to support a component for receiving a request for a signal that instructs the UE to skip using low-power radio components to monitor one or more low-power wake-up signals, wherein the signal is sent based on the request.

[0250] In some examples, the request indicates the UE's battery status, the service status at the UE, or both.

[0251] Figure 15 A diagram of a system 1500 including a device 1505 supporting low-power wake-up signal skipping, according to one or more aspects of this disclosure, is shown. Device 1505 may be an example of device 1205, device 1305, or network entity 105 as described herein, or may include components thereof. Device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1505 may include components supporting output and acquisition of communication, such as a communication manager 1520, a transceiver 1510, an antenna 1515, at least one memory 1525, code 1530, and at least one processor 1535. These components may communicate electronically or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1540).

[0252] Transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1510 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1510 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1505 may include one or more antennas 1515 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1510 may also include a modem for modulating signals to provide modulated signals for transmission (e.g., via one or more antennas 1515, via a wired transmitter), for receiving modulated signals (e.g., from one or more antennas 1515, from a wired receiver), and for demodulating signals. In some embodiments, transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1510 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1510, or transceiver 1510 and one or more antennas 1515, or transceiver 1510 and one or more antennas 1515 and one or more processors or one or more memory components (e.g., at least one processor 1535, at least one memory 1525, or both) may be included in a chip or chip assembly mounted in device 1505. In some examples, transceiver 1510 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0253] At least one memory 1525 may include RAM, ROM, or any combination thereof. At least one memory 1525 may store computer-readable, computer-executable code 1530 including instructions that, when executed by one or more of at least one processor 1535, cause device 1505 to perform the various functions described herein. Code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1530 may not be directly executable by one of the at least one processor 1535, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1525 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0254] At least one processor 1535 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1535. At least one processor 1535 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1525) to cause device 1505 to perform various functions (e.g., various functions or tasks that support low-power wake-up signal skipping). For example, device 1505 or components of device 1505 may include at least one processor 1535 and at least one memory 1525 coupled to one or more processors in at least one processor 1535, wherein at least one processor 1535 and at least one memory 1525 are configured to perform the various functions described herein. At least one processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1530) host functions for performing the functions of device 1505. At least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as within one or more memories in at least one memory 1525). In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1535 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1535) and memory circuitry (which may include at least one memory 1525)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1535 or a processing system including at least one processor 1535 may be configured, configured to, or operable to cause the device 1505 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1525 or otherwise.

[0255] In some examples, bus 1540 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1540 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1505, or communication performed between different components of device 1505 that are co-addressable or may be located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, at least one memory 1525, code 1530 and at least one processor 1535 may be located in one component of different components or partitioned between different components).

[0256] In some examples, the communication manager 1520 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1520 can manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1520 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 1520 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0257] The communication manager 1520 may support wireless communication according to examples disclosed herein. For example, the communication manager 1520 may be capable of, configured to, or operable to support components for transmitting a signal to a UE equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals. The communication manager 1520 may be capable of, configured to, or operable to support components for avoiding transmitting one or more low-power wake-up signals to the UE's low-power radio component based on the transmitted signal.

[0258] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 can support techniques for reducing power consumption.

[0259] In some examples, the communication manager 1520 may be configured to use or otherwise coordinate with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by the transceiver 1510, one or more processors in at least one processor 1535, one or more memories in at least one memory 1525, code 1530, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1535, at least one memory 1525, code 1530, or any combination thereof). For example, code 1530 may include instructions that can be executed by one or more processors in at least one processor 1535 to cause the device 1505 to perform various aspects of low-power wake-up signal skipping as described herein, or at least one processor 1535 and at least one memory 1525 may be otherwise configured to perform or support such operations individually or jointly.

[0260] Figure 16 A flowchart illustrating a method 1600 for supporting low-power wake-up signal skipping according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be implemented by, as referenced... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0261] At 1605, the method may include: receiving a signal via a low-power radio component of the UE or a main radio component of the UE, the signal indicating that the UE will skip using the low-power radio component to monitor one or more low-power wake-up signals. Operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be derived from references... Figure 10 The described skip instruction component 1025 is executed.

[0262] At 1610, the method may include: skipping the monitoring of one or more low-power wake-up signals based on a signal. The operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be derived from references... Figure 10 The described skip component 1030 is executed.

[0263] Figure 17A flowchart illustrating a method 1700 supporting low-power wake-up signal skipping according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be implemented by, as referenced... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0264] At 1705, the method may include: receiving a low-power wake-up signal via a low-power radio component of the UE, the low-power wake-up signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be derived from references... Figure 10 The described skip instruction component 1025 is executed.

[0265] At 1710, the method may include: skipping the monitoring of one or more low-power wake-up signals based on low-power wake-up signals. The operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 10 The described skip component 1030 is executed.

[0266] Figure 18 A flowchart illustrating a method 1800 supporting low-power wake-up signal skipping according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by a UE or its components as described herein. For example, operation of method 1800 can be implemented by, as referenced... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0267] At 1805, the method may include: receiving a control signal via the UE's main radio component, the control signal instructing the UE to skip using a low-power radio component to monitor one or more low-power wake-up signals. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be derived from references... Figure 10 The described skip instruction component 1025 is executed.

[0268] At 1810, the method may include: skipping the monitoring of one or more low-power wake-up signals based on a control signal. The operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be determined by reference to [reference needed]. Figure 10 The described skip component 1030 is executed.

[0269] Figure 19 A flowchart illustrating a method 1900 supporting low-power wake-up signal skipping according to various aspects of this disclosure is shown. Operation of method 1900 may be implemented by a network entity or its components as described herein. For example, operation of method 1900 may be implemented by, as referenced... Figures 1 to 7 as well as Figures 12 to 15 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0270] At 1905, the method may include: sending a signal to a UE equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals. The operation of block 1905 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1905 may be derived from references... Figure 14 The described skip instruction component 1425 is executed.

[0271] At 1910, the method may include: avoiding the transmission of one or more low-power wake-up signals to the low-power radio components of the UE based on the transmitted signal. The operation of block 1910 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1910 may be derived from references... Figure 14 The described sending avoidance component 1430 is used to perform this.

[0272] The following provides an overview of the various aspects of this disclosure:

[0273] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a signal via a low-power radio component of the UE or a main radio component of the UE, the signal indicating that the UE will skip using the low-power radio component to monitor one or more low-power wake-up signals; and skipping the monitoring of the one or more low-power wake-up signals at least in part based on the signal.

[0274] Aspect 2: According to the method of aspect 1, receiving the signal includes: receiving a low-power wake-up signal via the low-power radio component of the UE, the low-power wake-up signal indicating that the UE will skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0275] Aspect 3: According to the method of aspect 2, wherein the low-power wake-up signal is received via one or more resources, and one or more indices of the one or more resources indicate skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

[0276] Aspect 4: According to the method of aspect 3, the one or more resources correspond to time resources, frequency resources, spatial resources, or any combination thereof.

[0277] Aspect 5: The method according to any one of Aspects 3 to 4, the method further comprising: receiving control signaling indicating a plurality of resources including the one or more resources; and monitoring the low-power wake-up signal via the plurality of resources at least in part based on the control signaling.

[0278] Aspect 6: The method according to any one of Aspects 2 to 5, wherein the low-power wake-up signal includes one or more modulated bits that indicate that the UE will skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0279] Aspect 7: The method according to any one of Aspects 2 to 6, the method further comprising: using an envelope detector to detect the low-power wake-up signal.

[0280] Aspect 8: The method according to any one of Aspects 2 to 7, wherein the low-power wake-up signal comprises a sequence, the sequence index of which indicates skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

[0281] Aspect 9: According to the method of aspect 8, the method further includes: receiving control signaling, the control signaling indicating at least one or more sequence indices including the sequence index and one or more corresponding wake-up signal skip parameter sets.

[0282] Aspect 10: The method according to any one of Aspects 2 to 9, wherein the low-power wake-up signal indicates the identifier of the UE, a group identifier corresponding to a plurality of UEs, a cell identifier, a tracking area identifier, or any combination thereof.

[0283] Aspect 11: The method according to any one of Aspects 1 to 10, wherein receiving the signal comprises: receiving a control signal via the main radio component of the UE, the control signal instructing the UE to skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0284] Aspect 12: The method according to aspect 11, the method further comprising: receiving a low-power wake-up signal during a low-power wake-up signal monitoring timing indicated by the control signal, wherein powering off the low-power radio component is based at least in part on receiving the low-power wake-up signal.

[0285] Aspect 13: The method according to any one of Aspects 11 to 12, the method further comprising: powering off the main radio component at least in part based on receiving the control signal without receiving a downlink data message associated with the control signal.

[0286] Aspect 14: The method according to any one of Aspects 1 to 13, wherein skipping the monitoring comprises: skipping the monitoring of the one or more low-power wake-up signals based at least in part on the absence of a threshold number of consecutive low-power wake-up signals.

[0287] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the signal indicates a pattern for skipping the monitoring of the one or more low-power wake-up signals, a duration for skipping the monitoring of the one or more low-power wake-up signals, or a timing of monitoring the one or more low-power wake-up signals, or any combination thereof.

[0288] Aspect 16: The method according to any one of Aspects 1 to 15, wherein skipping the monitoring comprises: skipping a plurality of low-power wake-up signals, wherein the signals indicate the number of the plurality of low-power wake-up signals.

[0289] Aspect 17: The method according to any one of Aspects 1 to 16, the method further comprising: receiving an instruction to resume monitoring of a low-power wake-up signal; and monitoring the low-power wake-up signal at least in part based on the instruction to resume monitoring.

[0290] Aspect 18: The method according to any one of Aspects 1 to 17, the method further comprising: sending a request for the signal, the signal instructing the UE to skip using the low-power radio component to monitor the one or more low-power wake-up signals, wherein the signal is received at least in part based on the request.

[0291] Aspect 19: The method according to aspect 18, wherein the request is sent at least in part based on the battery state of the UE, the service status at the UE, or both.

[0292] Aspect 20: A method for wireless communication at a network entity, the method comprising: transmitting a signal to a UE equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals; and avoiding transmitting the one or more low-power wake-up signals to the low-power radio component of the UE at least in part based on transmitting the signal.

[0293] Aspect 21: According to the method of aspect 20, sending the signal includes: sending a low-power wake-up signal to the low-power radio component of the UE, the low-power wake-up signal instructing the UE to skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0294] Aspect 22: According to the method of aspect 21, wherein the low-power wake-up signal is transmitted via one or more resources, and one or more indices of the one or more resources indicate skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

[0295] Aspect 23: According to the method of aspect 22, the one or more resources correspond to time resources, frequency resources, spatial resources, or any combination thereof.

[0296] Aspect 24: The method according to any one of Aspects 22 to 23, the method further comprising: transmitting control signaling indicating a plurality of resources including the one or more resources, wherein the low-power wake-up signal is transmitted via the one or more resources at least in part based on the control signaling.

[0297] Aspect 25: The method according to any one of Aspects 21 to 24, wherein the low-power wake-up signal comprises a sequence, the sequence index of which indicates skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

[0298] Aspect 26: According to the method of aspect 25, the method further includes: sending control signaling, the control signaling indicating at least one or more sequence indices including the sequence index and one or more corresponding wake-up signal skip parameter sets.

[0299] Aspect 27: The method according to any one of Aspects 21 to 26, wherein the low-power wake-up signal indicates the identifier of the UE, a group identifier corresponding to a plurality of UEs, a cell identifier, a tracking area identifier, or any combination thereof.

[0300] Aspect 28: The method according to any one of Aspects 20 to 27, wherein sending the signal comprises: sending a control signal to the main radio component of the UE, the control signal instructing the UE to skip using the low-power radio component to monitor the one or more low-power wake-up signals.

[0301] Aspect 29: The method according to aspect 28, the method further comprising: sending a low-power wake-up signal during a low-power wake-up signal monitoring period, wherein the control signal indicates the low-power wake-up signal monitoring period.

[0302] Aspect 30: The method according to any one of Aspects 20 to 29, wherein the signal indicates a pattern for skipping the monitoring of the one or more low-power wake-up signals, a duration for skipping the monitoring of the one or more low-power wake-up signals, or a timing of monitoring the one or more low-power wake-up signals, or any combination thereof.

[0303] Aspect 31: The method according to any one of Aspects 20 to 30, the method further comprising: receiving a request for the signal indicating that the UE will skip using the low-power radio component to monitor the one or more low-power wake-up signals, wherein the request is sent at least in part based on the request.

[0304] Aspect 32: The method according to aspect 31, wherein the request indicates the battery status of the UE, the service status at the UE, or both.

[0305] Aspect 33: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 19.

[0306] Aspect 34: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 19.

[0307] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 19.

[0308] Aspect 36: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 20 to 32.

[0309] Aspect 37: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 20 to 32.

[0310] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform a method according to any one of aspects 20 to 32.

[0311] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0312] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0313] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0314] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0315] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0316] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0317] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0318] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0319] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0320] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0321] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0322] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: The UE receives a signal via its low-power radio component or its main radio component, the signal indicating that the UE will skip using the low-power radio component to monitor one or more low-power wake-up signals; and The monitoring of the one or more low-power wake-up signals is skipped, at least in part, based on the signal.

2. The UE of claim 1, wherein, in order to receive the signal, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The UE receives a low-power wake-up signal via its low-power radio component, the low-power wake-up signal indicating that the UE will skip using the low-power radio component to monitor the one or more low-power wake-up signals.

3. The UE of claim 2, wherein the low-power wake-up signal is received via one or more resources, and one or more indices of the one or more resources indicate skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

4. The UE of claim 3, wherein the one or more resources correspond to time resources, frequency resources, spatial resources, or any combination thereof.

5. The UE of claim 3, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The received instruction includes control signaling for multiple resources, including one or more of the resources mentioned above; and The low-power wake-up signal is monitored, at least in part, through the plurality of resources, based on the control signaling.

6. The UE of claim 2, wherein the low-power wake-up signal includes one or more modulated bits that indicate that the UE will skip using the low-power radio component to monitor the one or more low-power wake-up signals.

7. The UE of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: An envelope detector is used to detect the low-power wake-up signal.

8. The UE of claim 2, wherein the low-power wake-up signal comprises a sequence, and the sequence index of the sequence indicates skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

9. The UE of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive control signaling, the control signaling indicating at least one or more sequence indices of the sequence index and one or more corresponding wake-up signal skip parameter sets.

10. The UE of claim 2, wherein the low-power wake-up signal indicates the identifier of the UE, a group identifier corresponding to a plurality of UEs, a cell identifier, a tracking area identifier, or any combination thereof.

11. The UE of claim 1, wherein, in order to receive the signal, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The UE receives a control signal via its main radio component, the control signal instructing the UE to skip using the low-power radio component to monitor the one or more low-power wake-up signals.

12. The UE of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: A low-power wake-up signal is received during a low-power wake-up signal monitoring period indicated by the control signal, wherein powering down the low-power radio component is based at least in part on receiving the low-power wake-up signal.

13. The UE of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The main radio component is powered off, at least in part, based on the receipt of the control signal without the receipt of a downlink data message associated with the control signal.

14. The UE of claim 1, wherein, in order to bypass the monitoring, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The monitoring of the one or more low-power wake-up signals is skipped at least in part based on the absence of a threshold number of consecutive low-power wake-up signals.

15. The UE of claim 1, wherein the signal indicates a pattern for skipping the monitoring of the one or more low-power wake-up signals, a duration for skipping the monitoring of the one or more low-power wake-up signals, or a timing of monitoring the one or more low-power wake-up signals, or any combination thereof.

16. The UE of claim 1, wherein, in order to bypass the monitoring, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Skip multiple low-power wake-up signals, wherein the signal indicates the number of the multiple low-power wake-up signals.

17. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive instructions on resuming monitoring of low-power wake-up signals; and The low-power wake-up signal is monitored at least in part based on the indications for recovery monitoring.

18. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: A request is sent for the signal, which instructs the UE to skip using the low-power radio component to monitor the one or more low-power wake-up signals, wherein the signal is received at least in part based on the request.

19. The UE of claim 18, wherein the request is sent at least in part based on the battery state of the UE, the service status at the UE, or both.

20. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: A signal is sent to user equipment (UE) equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals; and At least in part, this is based on sending the signal to avoid sending the one or more low-power wake-up signals to the low-power radio components of the UE.

21. The network entity of claim 20, wherein, in order to send the signal, the one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: A low-power wake-up signal is sent to the low-power radio component of the UE, the low-power wake-up signal instructing the UE to skip using the low-power radio component to monitor the one or more low-power wake-up signals.

22. The network entity of claim 21, wherein the low-power wake-up signal is transmitted via one or more resources, and one or more indices of the one or more resources indicate skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

23. The network entity of claim 22, wherein the one or more resources correspond to time resources, frequency resources, spatial resources, or any combination thereof.

24. The network entity of claim 22, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The transmission instruction includes control signaling for multiple resources of the one or more resources, wherein the low-power wake-up signal is transmitted via the one or more resources based at least in part on the control signaling.

25. The network entity of claim 21, wherein the low-power wake-up signal comprises a sequence, and a sequence index of the sequence indicates skipping the use of the low-power radio component to monitor the one or more low-power wake-up signals.

26. The network entity of claim 25, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: Send control signaling, the control signaling indicating at least one or more sequence indices of the sequence index and one or more corresponding wake-up signal skip parameter sets.

27. The network entity of claim 21, wherein the low-power wake-up signal indicates an identifier of the UE, a group identifier corresponding to a plurality of UEs, a cell identifier, a tracking area identifier, or any combination thereof.

28. The network entity of claim 20, wherein, in order to send the signal, the one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: A control signal is sent to the main radio component of the UE, the control signal instructing the UE to skip using the low-power radio component to monitor the one or more low-power wake-up signals.

29. A method for conducting wireless communication at a user equipment (UE), the method comprising: The UE receives a signal via its low-power radio component or its main radio component, the signal indicating that the UE will skip using the low-power radio component to monitor one or more low-power wake-up signals; and The monitoring of the one or more low-power wake-up signals is skipped, at least in part, based on the signal.

30. A method for conducting wireless communication at a network entity, the method comprising: A signal is sent to user equipment (UE) equipped with a low-power radio component and a main radio component, the signal instructing the UE to skip using the low-power radio component to monitor one or more low-power wake-up signals; and At least in part, this is based on sending the signal to avoid sending the one or more low-power wake-up signals to the low-power radio components of the UE.

Images