WO2025231738A1

WO2025231738A1 - Low-power wake-up signal operation in radio resource control connected state

Info

Publication number: WO2025231738A1
Application number: PCT/CN2024/092052
Authority: WO
Inventors: Fangli Xu; Sigen Ye; Ping-Heng Kuo; Haijing Hu; Dan Wu; Jie Cui; Naveen Kumar R PALLE VENKATA
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2024-05-09
Filing date: 2024-05-09
Publication date: 2025-11-13
Anticipated expiration: 2026-11-09

Abstract

The present application relates to devices and components including apparatus, systems, and methods for low-power wake-up signaling configuration and operation in radio resource control connected state in communication networks.

Description

LOW-POWER WAKE-UP SIGNAL OPERATION IN RADIO RESOURCE CONTROL CONNECTED STATE

TECHNICAL FIELD

This application relates generally to wireless networks and, in particular, to technologies for low-power wake-up signal operation in radio resource control connected state.

BACKGROUND

Third Generation Partnership Project (3GPP) Technical Specifications (TSs) define standards for wireless networks. These TSs describe aspects related to signaling traffic through systems that incorporate wireless networks.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network environment in accordance with some embodiments.

FIG. 2 illustrates a timing diagram in accordance with some embodiments.

FIG. 3 illustrates another timing diagram in accordance with some embodiments.

FIG. 4 illustrates another timing diagram in accordance with some embodiments.

FIG. 5 illustrates another timing diagram in accordance with some embodiments.

FIG. 6 illustrates another timing diagram in accordance with some embodiments.

FIG. 7 is an operation flow/algorithmic structure in accordance with some embodiments.

FIG. 8 is another operation flow/algorithmic structure in accordance with some embodiments.

FIG. 9 is another operation flow/algorithmic structure in accordance with some embodiments.

FIG. 10 illustrates a user equipment in accordance with some embodiments.

FIG. 11 illustrates a network device in accordance with some embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, and techniques in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A/B” and “A or B” mean (A) , (B) , or (A and B) ; and the phrase “based on A” means “based at least in part on A, ” for example, it could be “based solely on A” or it could be “based in part on A. ”

The following is a glossary of terms that may be used in this disclosure.

The term “circuitry” as used herein refers to, is part of, or includes hardware components that are configured to provide the described functionality. The hardware components may include an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) , an application specific integrated circuit (ASIC) , a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA) , a programmable logic device (PLD) , a complex PLD (CPLD) , a high-capacity PLD (HCPLD) , a structured ASIC, or a programmable system-on-a-chip (SoC) ) , or a digital signal processor (DSP) . In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data. The term “processor circuitry” may refer an application processor, baseband processor, a central processing unit (CPU) , a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes.

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, and network interface cards.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities that may allow a user to access network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, or workload units. A “hardware resource” may refer to compute, storage, or network resources provided by physical hardware elements. A “virtualized resource” may refer to compute, storage, or network resources provided by virtualization infrastructure to an application, device, or system. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with or equivalent to “communications channel, ” “data communications channel, ” “transmission channel, ” “data transmission channel, ” “access channel, ” “data access channel, ” “link, ” “data link, ” “carrier, ” “radio-frequency carrier, ” or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices for the purpose of transmitting and receiving information.

The terms “instantiate, ” “instantiation, ” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The term “connected” may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.

The term “network element” as used herein refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to or referred to as a networked computer, networking hardware, network equipment, network node, or a virtualized network function.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. An information element may include one or more additional information elements.

FIG. 1 illustrates a network environment 100 in accordance with some embodiments. The network environment 100 may include a user equipment (UE) 104 communicatively coupled with a base station 108 of a radio access network (RAN) 110. The UE 104 and the base station 108 may communicate over air interfaces compatible with 3GPP TSs such as those that define a Fifth Generation (5G) new radio (NR) system or a later system. The base station 108 may provide user plane and control plane protocol terminations toward the UE 104.

The network environment 100 may further include a core network 112. For example, the core network 112 may comprise a 5th Generation Core network (5GC) or later generation core network. The core network 112 may be coupled to the base station 108 via a fiber optic or wireless backhaul. The core network 112 may provide functions for the UE 104 via the base station 108. These functions may include managing subscriber profile information, subscriber location, authentication of services, or switching functions for voice and data sessions.

The UE 104 may include a radio resource control (RRC) state machine that transitions the UE 104 into one of a number of RRC states (or “modes” ) including, for example, a CONNECTED state, an INACTIVE state, and an IDLE state. The UE 104 may start in the IDLE state when it first camps on a cell, which may be after the UE 104 is switched on or after an inter-system cell reselection. To engage in active communications, the RRC state machine may transition the UE 104 from IDLE state to the CONNECTED state by performing an RRC setup procedure to establish a logical connection, for example, an RRC connection, with the base station 108. In the CONNECTED state, the UE 104 may be configured with at least one signaling radio bearer (SRB) for signaling (for example, control messages) with the base station 108; and one or more data radio bearers (DRBs) for data transmission. When the UE 104 is less actively engaged in network communications, the RRC state machine may transition the UE 104 from the CONNECTED state to an INACTIVE state using an RRC release procedure. The INACTIVE state may allow the UE 104 to reduce power consumption as compared to CONNECTED, but will still allow the UE 104 to quickly transition back to CONNECTED state to transfer application data or signaling messages.

The UE 104 may be provided with a discontinuous reception (DRX) configuration that instructs the UE 104 to power down its receiver for periods of time and to wake up its receiver to monitor for a physical downlink control channel (PDCCH) transmission once per DRX cycle. The times in which the receiver wakes up to monitor the PDCCH may be referred to as an on-duration or DRX active time. If the UE 104 detects a PDCCH transmission directed to it during the on-duration, it may fully power on for communication with the base station 108. If the UE 104 does not detect a PDCCH transmission, the UE 104 may again power down its receiver until the next on-duration.

Waking up the receiver of the UE 104 every DRX cycle may waste energy if the UE 104 frequently does not detect PDCCH transmissions directed to it during the on-duration period. To address this issue, low-power (LP) wake-up signal (WUS) operation has been introduced in 3GPP networks. See, for example, 3GPP Technical Specification (TS) 38.869 v18.0.0 (2024-01-18) . LP WUS operation may include a separate, low-power receiver of the UE 104 periodically powering on in advance of an on-duration to monitor for an LP WUS that is sent if the network is intending to provide a PDCCH transmission to the UE 104. If an LP WUS is detected, the main receiver of the UE 104 may power-on in a subsequent on-duration to detect the PDCCH transmission that is expected. If an LP WUS is not detected, the main receiver of the UE 104 may stay powered down during the subsequent on-duration.

Objectives of 3GPP work items with respect to LP WUS operation include specifying an LP-WUS design that is commonly applicable to both IDLE/INACTIVE and CONNECTED states.

For CONNECTED state, it may be desirable to specify procedures to allow PDCCH monitoring triggered by LP WUS. This procedures may include activation and deactivation procedure of LP-WUS monitoring.

There may be three options for PDCCH monitoring triggered by LP WUS with connected mode DRX (C-DRX) .

In a first option, referred to as Option 1, LP WUS may be monitored according to an LP-WUS monitoring configuration before a configured on-duration period to trigger the PDCCH monitoring in the corresponding on-duration. For Option 1 operation, the UE 104 may monitor an LP WUS occasion outside a DRX active time. If the UE 104 detects an LP WUS in the monitored occasion, the UE 104 may perform PDCCH monitoring in the next on-duration period. In Option 1, the LP-WUS cycle is the same as the C-DRX cycle, which ensures an LP WUS occasion occurs in advance of each on-duration period.

Option 1 may be similar to, and replace, downlink control information (DCI) with cyclic redundancy check scrambled by power saving-radio network temporary identity (DCP) functionality.

While option 1 has an advantage of providing an impact on C-DRX mechanism that is similar to the DCP mechanism, it does not allow for achieving both latency reduction and UE power saving purposes. Latency may be reduced by the network using the LP WUS to wake up the UE 104 to monitor for the PDCCH shortly after DL data has arrived. UE power may be saved by not requiring the UE 104 to wake up for PDCCH monitoring if the network does not plan to schedule the UE 104 for data transmission.

With Option 1, the LP-WUS cycle being tied to the C-DRX cycle works against providing for both latency reduction and UE power saving. A long LP-WUS/C-DRX cycle is desired for power saving, while a short LP-WUS/C-DRX is desired for latency reduction purposes. For a short C-DRX cycle configuration, the LP WUS may be used to prevent the UE 104 from monitoring PDCCH during an on duration when the network has no plan to schedule/transmit data to the UE 104. However, it cannot control the UE measurement since the current UE measurement requirement is associated with the C-DRX cycle. Thus, UE power consumption on the measurement part cannot be saved.

In a second option, referred to as Option 2, a new period for PDDCH monitoring is introduced. LP-WUS monitoring may be configured outside the DRX active time, similar to that described above with respect to Option 1. However, with Option 2, LP-WUS triggered PDCCH monitoring may also exist outside a legacy DRX active time that is controlled by DRX configuration. The LP WUS occasions may be configured with a cycle that is less then the DRX cycle. Thus, a plurality of LP WUS occasions may occur between consecutive on-duration periods. An LP WUS in one of the LP WUS occasions that is not associated with a corresponding on-duration period may triggering PDCCH monitoring in a period that is outside the legacy DRX active time. Option 2 may include the following suboptions.

In a first suboption, referred to as Option 2-1, the LP WUS triggered PDDCH monitoring may work together with the legacy C-DRX mechanism. Thus, PDCCH monitoring may be triggered based on a legacy C-DRX cycle (and its associated on-duration periods) or based on a monitored LP WUS occasion.

In a second suboption, referred to as Option 2-2, the legacy PDCCH monitoring controlled by the on-duration timer may be disabled. Thus, PDCCH monitoring may not be triggered by the legacy C-DRX cycle (and its associated on-duration periods) , but may be triggered based on a monitored LP WUS occasion.

Option 2 has an advantage in that the UE 104 can be woken up by the LP WUS when there is downlink data that arrives outside the DRX active time (assuming LP-WUS cycle < C-DRX cycle) . However, the C-DRX operation triggered by the LP WUS (for example, how to manage various C-DRX timers) is unclear.

Embodiments of the present disclosure describe improved support for LP-WUS operation in the CONNECTED state. Embodiments may address various issues associated with the options discussed above. For example, with respect to Option 1, embodiments describe how to both reduce latency and save UE power. And, with respect to Option 2, embodiments describe UE DRX operation when the UE 104 is woke up by an LP WUS outside of the legacy DRX active time.

Some embodiments of the present disclosure decouple the measurement and C-DRX cycle, and provide that the UE 104 is perform measurements per measurement cycle. The LP-WUS cycle and the C-DRX cycle may be configured to reflect desired latency objectives (for example, relatively short values) . The measurement cycle may be configured to achieve desired power saving objectives (for example, a relatively long value) . In some embodiments, the measurement cycle may be greater than or equal to the C-DRX cycle. For example, the measurement cycle may be equal to N *CDRX cycle, where N is an integer of one or greater.

Aspects may describe various network operations. These operations may be performed by the base station 108, a device of the RAN 110, a device of the core network 112, or components therein (e.g., processing circuitry) .

A first aspect of the disclosure, referred to as Aspect 1, may provide improvements with respect to Option 1 operation described above. In Aspect 1, the LP-WUS cycle may be set equal to the C-DRX cycle as discussed above with respect to Option 1.

In Aspect 1, the base station 108 may configure the UE 104 with one or more configurations in a manner to decouple the measurement and C-DRX cycles. For example, the base station 108 may provide the UE 104 with an LP-WUS configuration in CONNECTED state. The LP-WUS configuration may configure the following cycles: C-DRX cycle and measurement cycle.

The C-DRX cycle may also correspond to LP-WUS cycle as discussed above. This may result in a LP-WUS occasion being configured with a time-offset before each on-duration.

The network may configure the measurement cycle in accordance with one or of the following options. In a first option, the network may configure N for the measurement cycle. The value N may be value greater than or equal to one. The measurement cycle may be set equal to N *C-DRX cycle. In some embodiments, N can be predefined in, for example, a 3GPP TS. In a second option, the network may configure a value of measurement cycle directly.

In some embodiments, the network may indicate which cycle out of N C-DRX cycles the UE 104 is to measure. In other embodiments, the UE 104 may select the cycle upon its own initiative according to UE implementation.

Operation of the UE 104 with respect to Aspect 1 may be described as follows.

For measurement, the UE 104 may follow the measurement cycle to perform the measurement. The measurement may be a radio resource management (RRM) measurement, a layer 1 (L1) measurement, or a beam failure detection (BFD) measurement.

Within each measurement cycle, the UE 104 may select one C-DRX cycle for measurement. As indicated above, selection of the one C-DRX cycle may be up to UE implementation or indicated by the network.

In some embodiments, the measurement may be an L1 measurement that is associated with a periodic L1 channel state information (CSI) /beam management (BM) report. Various options may exist for providing the periodic L1 CSI/BM report with respect to Aspect 1. In a first option, the network can explicitly configure whether the L1 CSI/BM report over the on-duration is impacted by a corresponding LP WUS. In a second option, the network can optionally use the LP-WUS to provide an indication to the UE 104 of whether to perform the L1 CSI/BM report or not. In a third option, the UE 104 may provide the L1 CSI/BM report when one or more predetermined conditions are fulfilled. For example, the predetermined conditions may include the UE determining that a best beam changes, a signal quality metric is greater than or less than a predetermined threshold, etc.

For the PDCCH monitoring with respect to Aspect 1, when the UE 104 is outside of the DRX active time, the UE 104 monitors the LP-WUS occasions according to the LP-WUS configuration. When the UE 104 detects an LP WUS in a monitored occasion, the UE 104 wakes up in the next on-duration period for measurement.

FIG. 2 is a timing diagram 200 of a first example of Aspect 1 in accordance with some embodiments.

The network configures the LP WUS together with C-DRX to the UE 104 for CONNECTED state operation. In this example, the network provides the UE 104 with a C-DRX cycle = X milliseconds (ms) and N=3 for the measurement cycle. The network may also configure the measurement and report started from a first on-duration period and once per N C-DRX cycles.

For measurement, the UE 104 may perform the measurement in the 1^st C-DRX cycle and the 4^th C-DRX cycle. For the L1 report, the UE 104 can provide the L1 report during the on-duration period in the 1^st C-DRX cycle and the 4^th C-DRX cycle. If the network configures the L1 report always on, the UE 104 may be required to provide the L1 report on 1^st and 4^th C-DRX cycles regardless of whether receiving the corresponding LP-WUS. For PDCCH monitoring, the UE 104 may monitor for the LP WUS on each LP-WUS occasion. If the UE 104 detects an LP WUS in an LP-WUS occasion, the UE 104 may start PDCCH monitoring in the on-duration period that corresponds to (for example, immediately follows) the LP-WUS occasion.

FIG. 3 is a timing diagram 300 of a second example of Aspect 1 in accordance with some embodiments.

In this example, the network configures the UE 104 with a C-DRX cycle = X milliseconds (ms) and N=2 for the measurement cycle.

The UE 104 may perform PDCCH monitoring in the same manner as discussed above with respect to the first example of Aspect 1.

For measurement, the UE 104 may select one C-DRX cycle per measurement cycle to perform the measurement. Selection may be based on network configuration or UE implementation.

As shown, in measurement cycle #1, the UE 104 may wake up in the 2^nd C-DRX cycle for PDCCH monitoring (based on the corresponding LP-WUS occasion including an LP WUS) . In this case, the UE 104 may also select the 2^nd C-DRX cycle for performing the measurement. In measurement cycle #2, the UE 104 wakes up in the 3^rd C-DRX cycle for PDCCH monitoring (based on the corresponding LP-WUS occasion including an LP WUS) . In this case, the UE 104 may select the 3^rd C-DRX cycle for performing the measurement. In measurement cycle #3, the UE 104 may not receive an LP WUS that causes PDCCH monitoring in either C-DRX cycle. Thus, in this instance, the UE 104 may perform the measurement in the 6^th C-DRX cycle (for example, the last C-DRX cycle of the third measurement cycle) .

A second aspect of the disclosure, referred to as Aspect 2, may provide improvements with respect to Option 2 operation described above. In Aspect 2, the LP-WUS monitoring may occur outside legacy DRX active time, the LP-WUS triggered PDCCH monitoring may be outside of the legacy DRX active time controlled by DRX configuration, and the LP-WUS cycle may be less than a C-DRX cycle as described above with respect to Option 2.

With respect to the Option 2, when the UE 104 receives an LP WUS outside DRX active time (in an LP-WUS occasion that does not have a corresponding on-duration period) , after a time-offset, the UE 104 starts a TIMER to monitor PDCCH. However, it is unclear as to how to maintain the TIMER and UE operation related to the TIMER.

Embodiments of the present disclosure describe that, for an LP-WUS occasion that does not have a corresponding on-duration period, the UE 104 starts the TIMER after the time-offset from receiving LP-WUS outside DRX active time. This TIMER may be referred to as a wake up (WU) TIMER. When the WU TIMER is running, the UE 104 is considered to be in a DRX active time (even if such a DRX active time was not one previously provided by the DRX configuration) . The UE 104 may then perform the DRX operation in DRX active time as legacy) . For example, the UE 104 may start an inactivity timer based on DCI scheduling, and start hybrid automatic repeat request (HARQ) round-trip time (RTT) timer/retransmission timer based on associated transmissions. This may be referred to as operating in a DRX active time mode. Thus, with Aspect 1, DRX active time may be entered based on DRX configuration that defines periodic on-durations/DRX active times; or DRX active time may be entered based on receipt of the LP WUS.

In some embodiments, whether to support short DRX cycle can be based on a configuration or be predefined in a 3GPP TS.

When the WU-TIMER expires, the UE 104 may consider the DRX active time according to other legacy DRX timers.

If the UE 104 does not receive any UE-specific PDCCH during the WU-TIMER running, the UE 104 may perform one or more of the following options. In a first option, the UE 104 may fall back to a legacy C-DRX mechanism and not monitor LP-WUS occasions after WU-TIMER expiry (e.g., when out of DRX active time) . In a second option, the UE 104 may provide a notification to the network that no PDCCH transmission was received after receipt of the LP WUS. This notification may be provided at a point in which the UE 104 can transmit data to the network.

In some embodiments, the UE 104 may not monitor LP-WUS occasions during the DRX active time controlled by the WU TIMER.

In some embodiments, the WU TIMER can be a new DRX timer configured by the network. For example, the base station 108 may provide a timer value that the UE 104 is to use when starting the WU timer.

FIG. 4 is a timing diagram 400 of a first example of Aspect 2 in accordance with some embodiments.

In this example, the network configures the UE 104 with LP WUS, a time offset, and a WU-TIMER value. Then, outside of DRX active time, the UE 104 monitors for an LP WUS in WUS occasions. When the UE’s LP WUS is detected, as shown in the first LP WUS occasion of the timing diagram 400, the UE 104 may start a WU TIMER, with the WU-TIMER value, after the time offset. When the WU TIMER is running, the UE 104 enters DRX active time. During the DRX active time, the UE 104 receives a PDCCH transmission with a new DCI for DL scheduling, and the UE 104 starts a DRX inactivity timer. The UE 104 may also start HARQ RTT Timer and retransmission timer according to a particular transmission situation. When the WU TIMER expires, the UE 104 is still in DRX active time according to another DRX timer (e.g. the DRX inactivity timer) , UE keeps the legacy CDRX operation in DRX active time. When the DRX inactivity timer expires (and assuming no other DRX timer is running that would keep the UE 104 in the DRX active time) , the UE 104 may leave the DRX active time. The UE 104 may continue to monitor for LP WUSs if the LP-WUS function is still enabled/activated.

FIG. 5 is a timing diagram 500 of a second example of Aspect 2 in accordance with some embodiments.

In this example, the network configures the UE 104 with LP WUS, a time offset, and a WU-TIMER value in a manner similar to that discussed above with respect to timing diagram 400. When the UE’s LP WUS is detected, as shown in the first LP WUS occasion of the timing diagram 500, the UE 104 may start a WU TIMER, with the WU-TIMER value, after the time offset. When the WU TIMER is running, the UE 104 enters DRX active time. However, unlike timing diagram 400, in this instance, the UE 104 does not receive any UE-dedicated scheduling in the DRX active time, and the UE 104 has no UL data for transmission in the DRX active time. Thus, in this embodiment, upon expiration of the WU TIMER the UE 104 may disable LP-WUS monitoring outside DRX active time. The UE 104 may then follow the legacy C-DRX mechanism to monitor PDCCH in the on-duration periods.

FIG. 6 is a timing diagram 600 of a third example of Aspect 2 in accordance with some embodiments.

In this example, the network configures the UE 104 with LP WUS, a time offset, and a WU-TIMER value in a manner similar to that discussed above with respect to timing diagrams 400 and 500. When the UE’s LP WUS is detected, as shown in the first LP WUS occasion of the timing diagram 600, the UE 104 may start a WU TIMER, with the WU-TIMER value, after the time offset. When the WU TIMER is running, the UE 104 enters DRX active time. Similar to timing diagram 500, in this instance, the UE 104 does not receive any UE-dedicated scheduling in the DRX active time, and the UE 104 has no UL data for transmission in the DRX active time. However, unlike timing diagram 500, in this case, after expiration of the WU timer, the UE 104 will trigger a scheduling request (SR) and transmit a UE report to the network. The UE report may include information to notify the network that no UE-specific PDCCH was scheduled/detected during the DRX active time (based on the WU-TIMER running, which was triggered by detection of the LP WUS) . The network may respond with network signaling. The network signaling may be explicit signaling for the UE 104 to perform (or not perform) LP-WUS operation going forward. For example, the network signaling may deactivate or deconfigure the LP-WUS signaling, in which case, the UE 104 will disable LP-WUS operation accordingly.

FIG. 7 is an operation flow/algorithmic structure 700 in accordance with some embodiments. The operation flow/algorithmic structure 700 may be implemented or performed by a base station such as, for example, base station 108, network device 1100, or components therein, e.g., processing circuitry of processors 1104.

The operation flow/algorithmic structure 700 may include, at 704, generating one or more configurations to configure an LP WUS cycle and a measurement cycle. In some embodiments, the one or more configurations may also configure a C-DRX cycle. The LP-WUS cycle and C-DRX cycles may be less than or equal to the measurement cycle. In some embodiments, the measurement cycle may be N times the LP WUS cycle or the C-DRX cycle, where N is a value greater than one. The value N may be predefined or provided by a parameter of the one or more configurations.

In some embodiments, the one or more configurations may include a C-DRX configuration and further include a time offset the defines the LP-WUS occasions before respective on-durations of the C-DRX cycle.

In some embodiments, the one or more configurations are to configure measurements, based on the measurement cycle, once every N on-durations of the C-DRX cycle. The value N may be a value greater than or equal to one.

The operation flow/algorithmic structure 700 may further include, at 708, generating one or more signals to convey the one or more configurations to a UE. The signals may include one or more configuration messages such as, but not limited to, RRC messages.

FIG. 8 is an operation flow/algorithmic structure 800 in accordance with some embodiments. The operation flow/algorithmic structure 800 may be implemented or performed by a UE such as, for example, UE 104, UE 1000, or components therein, e.g., processing circuitry of processors 1004.

The operation flow/algorithmic structure 800 may include, at 804, processing one or more configurations that configure an LP-WUS cycle and a measurement cycle. The one or more configurations may be similar to that described with respect to FIG. 8 or elsewhere herein.

The operation flow/algorithmic structure 800 may further include, at 808, monitoring an LP-WUS occasion based on the LP-WUS cycle.

The operation flow/algorithmic structure 800 may further include, at 812, performing a measurement based on the measurement cycle.

In some embodiments, performing the measurement may include selecting an on duration of a C-DRX configuration within the measurement cycle. The measurement may be performed within the on duration. The measurement may be an RRM measurement, an L1 measurement, a BFD measurement, or a BM measurement.

In some embodiments, the UE may determine a selection configuration and select the on duration within the measurement cycle based on the selection configuration. The selection configuration may be received from a network or may be predefined by, for example, a 3GPP TS.

In some embodiments, on-duration may be selected by determining whether an LP WUS is received in an LP WUS occasion that corresponds to any of the plurality of on-durations. If an LP WUS is received in one or more LP WUS occasions, the on-duration that corresponds to a first LP WUS occasion of the one or more LP WUS occasions occurring in a time domain may be selected. If an LP WUS is not received in an LP WUS occasion that corresponds to any of the plurality of on-durations, a last LP WUS occasion of the one or more LP WUS occasions occurring in the time domain may be selected.

FIG. 9 is an operation flow/algorithmic structure 900 in accordance with some embodiments. The operation flow/algorithmic structure 900 may be implemented or performed by a UE such as, for example, UE 104, UE 1000, or components therein, e.g., processing circuitry of processors 1004.

The operation flow/algorithmic structure 900 may include, at 904, determining a time offset and a WU timer value. These parameters may be determined from one or configurations received from a base station. In some embodiments, one or more of these parameters may be preconfigured or predefined in, for example, a 3GPP TS.

The operation flow/algorithmic structure 900 may further include, at 908, detecting an LP WUS in an LP WUS occasion. The LP WUS occasion may be defined based on an LP WUS configuration. In some embodiments, the LP WUS configuration may be the same configuration as the configuration that provides the time offset and WU timer value. In other embodiments, these configurations may be different.

The operation flow/algorithmic structure 900 may further include, at 912, starting a WU timer.

The operation flow/algorithmic structure 900 may further include, at 916, operating in DRX active time mode while the WU timer is running.

If a PDCCH transmission is received while operating in DRX active time mode, a DRX timer may be started. The DRX timer may be any of a number of different timers relevant to operating during a DRX active time. If the WU timer expires and the DRX timer is still running, the device may stay in the DRX active time mode until the DRX timer also expires.

If the WU timer expires without receiving a PDCCH transmission, the operation flow/algorithmic structure may include either ceasing LP WUS operation altogether or generating an indication that no PDCCH transmission was detected and sending that indication to a network. Responsive network signaling may indicate whether to continue LP WUS operation or cease LP WUS operation.

FIG. 10 illustrates a UE 1000 in accordance with some embodiments. The UE 1000 may be similar to and substantially interchangeable with UE 104.

The UE 1000 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, electric voltage/current meters, or actuators) , video surveillance/monitoring devices (for example, cameras or video cameras) , wearable devices (for example, a smart watch) , or Internet-of-things devices.

The UE 1000 may include processors 1004, RF interface circuitry 1008, memory/storage 1012, user interface 1016, sensors 1020, driver circuitry 1022, power management integrated circuit (PMIC) 1024, antenna 1026, and battery 1028. The components of the UE 1000 may be implemented as integrated circuits (ICs) , portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 10 is intended to show a high-level view of some of the components of the UE 1000. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

The components of the UE 1000 may be coupled with various other components over one or more interconnects 1032, which may represent any type of interface, input/output, bus (local, system, or expansion) , transmission line, trace, or optical connection that allows various circuit components (on common or different chips or chipsets) to interact with one another.

The processors 1004 may include processing circuitry such as, for example, baseband processor circuitry (BB) 1004A, central processor unit circuitry (CPU) 1004B, and graphics processor unit circuitry (GPU) 1004C. The processors 1004 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory/storage 1012 to cause the UE 1000 to perform LP WUS operations as described herein. The processors 1004 may also include interface circuitry 1004D to communicatively couple the processor circuitry with one or more other components of the UE 1000.

In some embodiments, the baseband processor circuitry 1004A may access a communication protocol stack 1036 in the memory/storage 1012 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 1004A may access the communication protocol stack 1036 to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a NAS layer. In some embodiments, the PHY layer operations may additionally/alternatively be performed by the components of the RF interface circuitry 1008.

The baseband processor circuitry 1004A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks. In some embodiments, the waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

The memory/storage 1012 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 1036) that may be executed by one or more of the processors 1004 to cause the UE 1000 to perform various delay-adaptive operations described herein.

The memory/storage 1012 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1000. In some embodiments, some of the memory/storage 1012 may be located on the processors 1004 themselves (for example, memory/storage 1012 may be part of a chipset that corresponds to the baseband processor circuitry 1004A) , while other memory/storage 1012 is external to the processors 1004 but accessible thereto via a memory interface. The memory/storage 1012 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM) , static random access memory (SRAM) , erasable programmable read only memory (EPROM) , electrically erasable programmable read only memory (EEPROM) , Flash memory, solid-state memory, or any other type of memory device technology.

The RF interface circuitry 1008 may include transceiver circuitry and a radio frequency front module (RFEM) that allows the UE 1000 to communicate with other devices over a radio access network. The RF interface circuitry 1008 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

In the receive path, the RFEM may receive a radiated signal from an air interface via antenna 1026 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 1004.

In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna 1026.

In various embodiments, the RF interface circuitry 1008 may be configured to transmit/receive signals in a manner compatible with NR access technologies.

The antenna 1026 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna 1026 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna 1026 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna 1026 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.

The user interface 1016 includes various input/output (I/O) devices designed to enable user interaction with the UE 1000. The user interface 1016 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button) , a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position (s) , or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs) , LED displays, quantum dot displays, and projectors) , with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 1000.

The sensors 1020 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and send the information (sensor data) about the detected events to some other device, module, or subsystem. Examples of such sensors include inertia measurement units comprising accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors) ; pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (for example, cameras or lensless apertures) ; light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like) ; depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other like audio capture devices.

The driver circuitry 1022 may include software and hardware elements that operate to control particular devices that are embedded in the UE 1000, attached to the UE 1000, or otherwise communicatively coupled with the UE 1000. The driver circuitry 1022 may include individual drivers allowing other components to interact with or control various input/output (I/O) devices that may be present within, or connected to, the UE 1000. For example, driver circuitry 1022 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensors 1020 and control and allow access to sensors 1020, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The PMIC 1024 may manage power provided to various components of the UE 1000. In particular, with respect to the processors 1004, the PMIC 1024 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

A battery 1028 may power the UE 1000, although in some examples the UE 1000 may be mounted deployed in a fixed location and may have a power supply coupled to an electrical grid. The battery 1028 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 1028 may be a typical lead-acid automotive battery.

FIG. 11 illustrates a network device 1100 in accordance with some embodiments. The network device 1100 may be similar to and substantially interchangeable with base station 118 or a device of the core network 112 or external data network 120.

The network device 1100 may include processors 1104, RF interface circuitry 1108 (if implemented as a base station) , core network (CN) interface circuitry 1114, memory/storage circuitry 1112, and antenna structure 1126.

The components of the network device 1100 may be coupled with various other components over one or more interconnects 1128.

The processors 1104, RF interface circuitry 1108, memory/storage circuitry 1112 (including communication protocol stack 1110) , antenna structure 1126, and interconnects 1128 may be similar to like-named elements shown and described with respect to FIG. 10.

The processors 1104 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1104A, central processor unit circuitry (CPU) 1104B, and graphics processor unit circuitry (GPU) 1104C. The processors 1104 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory/storage circuitry 1112 to cause the network device 1100 to perform LP WUS operations described herein. The processors 1104 may also include interface circuitry 1104D to communicatively couple the processor circuitry with one or more other components of the network device 1100.

The CN interface circuitry 1114 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to/from the network device 1100 via a fiber optic or wireless backhaul. The CN interface circuitry 1114 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1114 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

Any of the above-described examples may be combined with any other example (or combination of examples) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

Examples

In the following sections, further exemplary embodiments are provided.

Example 1 includes a method comprising: generating one or more configurations to configure a low-power (LP) wake-up signal (WUS) cycle and a measurement cycle to be used in a radio resource control (RRC) connected state, wherein the LP WUS cycle is less than the measurement cycle; and generating one or more signals to convey the one or more configurations to a UE.

Example 2 includes method of example 1 or some other example herein, wherein the one or more configurations are to further configure a connected mode discontinuous reception (C-DRX) cycle that is less than or equal to the measurement cycle.

Example 3 includes method of example 2 or some other example herein, wherein the measurement is cycle is N times the LP WUS cycle or the C-DRX cycle, where N is a value greater than one that is predefined or is provided by a parameter of the one or more configurations.

Example 4 includes a method of example 1 or some other example herein, wherein the one or more configurations include a first configuration to configure the LP WUS cycle and a second configuration to configure the measurement cycle.

Example 5 includes a method of example 1 or some other example herein, wherein the one or more configurations include a connected-mode discontinuous reception (C-DRX) configuration that configures on-durations with a C-DRX cycle, and the one or more configurations further include a time offset that define LP-WUS occasions before respective on-durations of the C-DRX cycle.

Example 6 includes a method of example 5 or some other example herein, wherein the one or more configurations are to configure measurements, based on the measurement cycle, once every N on-durations of the C-DRX cycle, wherein N is a value greater than or equal to one.

Example 7 includes a method comprising: receiving one or more configurations to configure a low-power (LP) wake-up signal (WUS) cycle and a measurement cycle to be used in a radio resource control (RRC) connected state, wherein the LP-WUS cycle is less than the measurement cycle; monitoring an LP WUS occasion based on the LP-WUS cycle; and performing a measurement based on the measurement cycle.

Example 8 includes the method of example 7 or some other example herein, wherein the one or more configurations are to further configure a connected mode discontinuous reception (C-DRX) cycle that is less than or equal to the measurement cycle.

Example 9 includes the method of example 8 or some other example herein, wherein the measurement is cycle is N times the LP WUS cycle or the C-DRX cycle, where N is a value greater than one that is predefined or is provided by a parameter of the one or more configurations.

Example 10 includes the method of example 7 or some other example herein, wherein the one or more configurations include a first configuration to configure the LP WUS cycle and a second configuration to configure the measurement cycle.

Example 11 includes the method of example 7 or at some other example herein, wherein the one or more configurations include a connected-mode discontinuous reception (C-DRX) configuration that configures on-durations with a C-DRX cycle, and the one or more configurations further include a time offset that define LP-WUS occasions before respective on-durations of the C-DRX cycle.

Example 12 includes the method of example 7 or some other example herein, further comprising: selecting an on-duration of a connected-mode discontinuous reception (C-DRX) configuration within the measurement cycle; and performing the measurement within the on-duration, wherein the measurement is a radio resource management (RRM) measurement, a layer 1 measurement, a beam failure detection measurement, or a beam management measurement.

Example 13 includes the method of example 12 or some other example herein, further comprising: determining a selection configuration, wherein the selection configuration is received from a network or is predefined; and selecting the on-duration within the measurement cycle based on the selection configuration.

Example 14 includes the method of example 12 or some other example herein, wherein a plurality of on-durations are within the measurement cycle and selecting the on-duration further comprises: determining whether an LP WUS is received in an LP WUS occasion that corresponds to any of the plurality of on-durations; if an LP WUS is received in one or more LP WUS occasions, selecting the on-duration that corresponds to a first LP WUS occasion of the one or more LP WUS occasions occurring in a time domain; and if an LP WUS is not received in an LP WUS occasion that corresponds to any of the plurality of on-durations, selecting a last LP WUS occasion of the one or more LP WUS occasions occurring in the time domain.

Example 15 includes the method of example 7 or some other example herein, further comprising: receiving a configuration for a periodic layer 1 (L1) report, wherein the configuration is to indicate whether a measurement for the L1 report is to be based on the LP WUS cycle, a connected mode discontinuous reception (C-DRX) cycle, or the measurement cycle.

Example 16 includes the method of example 7 or some other example herein, further comprising: detecting an LP WUS in an occasion defined by the LP WUS cycle, wherein the LP WUS is to indicate whether to perform a measurement for a periodic layer 1 (L1) report within an on-duration that follows the occasion.

Example 17 includes the method of example 7 or some other example herein, further comprising: receiving a configuration for a periodic layer 1 (L1) report, wherein the configuration includes an indication of one or more conditions to be fulfilled to trigger the L1 report.

Example 18 includes the method of example 7 or some other example herein, further comprising: detecting an LP WUS based on said monitoring the LP WUS occasion; and waking up for physical downlink control channel (PDCCH) monitoring in an on-duration that follows the LP WUS occasion based on detecting the LP WUS.

Example 19 includes a method comprising: determining, based on one or more configurations received from a network, a time offset and a wake-up (WU) timer value; detecting a low-power wake-up signal (LP WUS) within an LP WUS occasion defined by the one or more configurations; starting a WU timer with the WU timer value after the time offset from the LP WUS occasion; and operating in a discontinuous reception (DRX) active time mode while the WU timer is running.

Example 20 includes the method of example 19 or some other example herein, further comprising: receiving a physical downlink control channel (PDCCH) transmission while operating in the DRX active time mode; and starting a DRX timer based on receiving the PDCCH transmission.

Example 21 includes the method of example 20 or some other example herein, further comprising: operating in the DRX active time after expiration of the WU timer while the DRX timer is running.

Example 22 includes the method of example 19 or some other example herein, further comprising: detecting an expiration of the WU timer; and determining that no physical downlink control channel (PDCCH) transmission was detected while operating in the DRX active time mode.

Example 23 includes the method of example 22 or some other example herein, further comprising: exiting the DRX active time mode after expiration of the WU timer; and ceasing LP WUS operation based on said determining that no PDCCH transmission was detected while operating in the DRX active time mode.

Example 24 includes the method of example 22 or some other example herein, further comprising: exiting the DRX active time mode after expiration of the WU timer; and generating, for transmission to a base station, an indication that no PDCCH transmission was detected while operating in the DRX active time mode.

Example 25 includes the method of example 24 some other example herein, further comprising: processing network signaling to determine whether to continue LP WUS operation or cease LP WUS operation after exiting the DRX active time mode.

Another example may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1–25, or any other method or process described herein.

Another example may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1–25, or any other method or process described herein.

Another example may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1–25, or any other method or process described herein.

Another example may include a method, technique, or process as described in or related to any of examples 1–25, or portions or parts thereof.

Another example may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1–25, or portions thereof.

Another example may include a signal as described in or related to any of examples 1–25, or portions or parts thereof.

Another example may include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1–25, or portions or parts thereof, or otherwise described in the present disclosure.

Another example may include a signal encoded with data as described in or related to any of examples 1–25, or portions or parts thereof, or otherwise described in the present disclosure.

Another example may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1–25, or portions or parts thereof, or otherwise described in the present disclosure.

Another example may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1–25, or portions thereof.

Another example may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1–25, or portions thereof.

Another example may include a signal in a wireless network as shown and described herein.

Another example may include a method of communicating in a wireless network as shown and described herein.

Another example may include a system for providing wireless communication as shown and described herein.

Another example may include a device for providing wireless communication as shown and described herein.

Claims

A method comprising:

generating one or more configurations to configure a low-power (LP) wake-up signal (WUS) cycle and a measurement cycle to be used in a radio resource control (RRC) connected state, wherein the LP WUS cycle is less than the measurement cycle; and

generating one or more signals to convey the one or more configurations to a user equipment (UE) .
The method of claim 1, wherein the one or more configurations are to further configure a connected mode discontinuous reception (C-DRX) cycle that is less than or equal to the measurement cycle.
The method of claim 2, wherein the measurement is cycle is N times the LP WUS cycle or the C-DRX cycle, where N is a value greater than one that is predefined or is provided by a parameter of the one or more configurations.
The method of claim 1, wherein the one or more configurations include a first configuration to configure the LP WUS cycle and a second configuration to configure the measurement cycle.
The method of claim 1, wherein the one or more configurations include a connected-mode discontinuous reception (C-DRX) configuration that configures on-durations with a C-DRX cycle, and the one or more configurations further include a time offset that define LP-WUS occasions before respective on-durations of the C-DRX cycle.
The method of claim 5, wherein the one or more configurations are to configure measurements, based on the measurement cycle, once every N on-durations of the C-DRX cycle, wherein N is a value greater than or equal to one.
One or more computer-readable media having instructions that, when executed, cause processing circuitry to:

receive one or more configurations to configure a low-power (LP) wake-up signal (WUS) cycle and a measurement cycle to be used in a radio resource control (RRC) connected state, wherein the LP WUS cycle is less than the measurement cycle;

monitor an LP WUS occasion based on the LP WUS cycle; and

perform a measurement based on the measurement cycle.
The one or more computer-readable media of claim 7, wherein the one or more configurations are to further configure a connected mode discontinuous reception (C-DRX) cycle that is less than or equal to the measurement cycle.
The one or more computer-readable media of claim 8, wherein the measurement is cycle is N times the LP WUS cycle or the C-DRX cycle, where N is a value greater than one that is predefined or is provided by a parameter of the one or more configurations.
The one or more computer-readable media of claim 7, wherein the one or more configurations include a first configuration to configure the LP WUS cycle and a second configuration to configure the measurement cycle.
The one or more computer-readable media of claim 7, wherein the one or more configurations include a connected-mode discontinuous reception (C-DRX) configuration that configures on-durations with a C-DRX cycle, and the one or more configurations further include a time offset that define LP-WUS occasions before respective on-durations of the C-DRX cycle.
The one or more computer-readable media of claim 7, wherein the instructions, when executed, further cause the processing circuitry to:

select an on-duration of a connected-mode discontinuous reception (C-DRX) configuration within the measurement cycle; and

perform the measurement within the on-duration, wherein the measurement is a radio resource management (RRM) measurement, a layer 1 measurement, a beam failure detection measurement, or a beam management measurement.
The one or more computer-readable media of claim 12, wherein the instructions, when executed, further cause the processing circuitry to:

determine a selection configuration, wherein the selection configuration is received from a network or is predefined; and

select the on-duration within the measurement cycle based on the selection configuration.
The one or more computer-readable media of claim 12, wherein a plurality of on-durations are within the measurement cycle and to select the on-duration further comprises:

determine whether an LP WUS is received in an LP WUS occasion that corresponds to any of the plurality of on-durations;

if an LP WUS is received in one or more LP WUS occasions, select the on-duration that corresponds to a first LP WUS occasion of the one or more LP WUS occasions occurring in a time domain; and

if an LP WUS is not received in an LP WUS occasion that corresponds to any of the plurality of on-durations, select a last LP WUS occasion of the one or more LP WUS occasions occurring in the time domain.
The one or more computer-readable media of claim 7, wherein the instructions, when executed, further cause the processing circuitry to:

receive a configuration for a periodic layer 1 (L1) report, wherein the configuration is to indicate whether a measurement for the L1 report is to be based on the LP WUS cycle, a connected mode discontinuous reception (C-DRX) cycle, or the measurement cycle.
The one or more computer-readable media of claim 7, wherein the instructions, when executed, further cause the processing circuitry to:

detect an LP WUS in an occasion defined by the LP WUS cycle, wherein the LP WUS is to indicate whether to perform a measurement for a periodic layer 1 (L1) report within an on-duration that follows the occasion.
The one or more computer-readable media of claim 7, wherein the instructions, when executed, further cause the processing circuitry to:

receive a configuration for a periodic layer 1 (L1) report, wherein the configuration includes an indication of one or more conditions to be fulfilled to trigger the L1 report.
The one or more computer-readable media of claim 7, wherein the instructions, when executed, further cause the processing circuitry to:

detect an LP WUS based on said monitoring the LP WUS occasion; and

wake up for physical downlink control channel (PDCCH) monitoring in an on-duration that follows the LP WUS occasion based on detecting the LP WUS.
An apparatus comprising:

processing circuitry to:

determine, based on one or more configurations received from a network, a time offset and a wake-up (WU) timer value;

detect a low-power wake-up signal (LP WUS) within an LP WUS occasion defined by the one or more configurations;

start a WU timer with the WU timer value after the time offset from the LP WUS occasion; and

operate in a discontinuous reception (DRX) active time mode while the WU timer is running; and

interface circuitry coupled with the processing circuitry, the interface circuitry to communicatively couple the processing circuitry to a component of the device.
The apparatus of claim 19, wherein the processing circuitry is further to:

receiving a physical downlink control channel (PDCCH) transmission while operating in the DRX active time mode; and

starting a DRX timer based on receiving the PDCCH transmission.
The apparatus of claim 20, wherein the processing circuitry is further to:

operate in the DRX active time after expiration of the WU timer while the DRX timer is running.
The method of claim 19, wherein the processing circuitry is further to:

detect an expiration of the WU timer; and

determine that no physical downlink control channel (PDCCH) transmission was detected while operating in the DRX active time mode.
The method of claim 22, wherein the processing circuitry is further to:

exit the DRX active time mode after expiration of the WU timer; and

cease LP WUS operation based on said determining that no PDCCH transmission was detected while operating in the DRX active time mode.
The method of claim 22, wherein the processing circuitry is further to:

exit the DRX active time mode after expiration of the WU timer; and

generate, for transmission to a base station, an indication that no PDCCH transmission was detected while operating in the DRX active time mode.
The method of claim 24, wherein the processing circuitry is further to:

process network signaling to determine whether to continue LP WUS operation or cease LP WUS operation after exiting the DRX active time mode.