WO2025241594A1

WO2025241594A1 - Handling of low-power wake-up signal

Info

Publication number: WO2025241594A1
Application number: PCT/CN2025/074933
Authority: WO
Inventors: Luning Liu; Jie Hu; Haiming Wang; Jing HAN; Zhi YAN
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2025-01-24
Filing date: 2025-01-24
Publication date: 2025-11-27
Anticipated expiration: 2027-07-24

Abstract

Various aspects of the present disclosure relate to handling of LP-WUS. In an aspect, a UE performs physical downlink control channel (PDCCH) monitoring in a first active time. The UE determines a monitoring occasion (MO) for low-power wakeup signal (LP-WUS). The UE determines whether to trigger a second active time for PDCCH monitoring based on at least one of the following: a time location of the first active time, a time location of the MO for LP-WUS, a time location of a monitoring window including the MO for LP-WUS, or an indication related to LP-WUS monitoring received from a network entity.

Description

HANDLING OF LOW-POWER WAKE-UP SIGNAL

TECHNICAL FIELD

The present disclosure relates to a user equipment (UE) , a base station, processors for wireless communication, methods, and non-transitory computer readable media for handling of low-power wake-up signal (LP-WUS) .

BACKGROUND

A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)) .

Techniques related to low-power wake-up signal and receiver (LP-WUS/WUR) for NR are now under study. The intention of the LP-WUS/WUR is to wake up the UE only when triggered by LP-WUS, e.g., in the case of paging in RRC_IDLE/INACTIVE mode, or in the case of data transmission in RRC_CONNECTED mode. In this way, the power consumption could be dramatically reduced. Further study on the LP-WUS/WUR are still needed.

SUMMARY

The present disclosure relates to methods, apparatuses, and systems that support handling of LP-WUS. By determining whether to trigger a second active time for PDCCH monitoring associated with a determined LP-WUS MO or a monitoring window comprising the LP-WUS MO in the case that the LP-WUS MO is after a first active time for PDCCH monitoring, operations of the gNB and the UE may be aligned considering the case that the UE might miss the LP-WUS MO. The communication performance may thus be improved.

In a first aspect of the solution, a UE performs physical downlink control channel (PDCCH) monitoring in a first active time. The UE determines a monitoring occasion (MO) for low-power wakeup signal (LP-WUS) . The UE determines whether to trigger a second active time for PDCCH monitoring based on at least one of the following: a time location of the first active time, a time location of the MO for LP-WUS, a time location of a monitoring window including the MO for LP-WUS, or an indication related to LP-WUS monitoring received from a network entity.

In some implementations of the method and apparatuses described herein, a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is shorter than a duration threshold.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH monitoring associated with the MO is triggered. Some implementations of the method and apparatuses described herein may further include: starting a timer associated with the MO; performing PDCCH monitoring in the second active time for PDCCH monitoring; and ending the second active time for PDCCH monitoring at an expiry of the timer or based on an indication of stopping the PDCCH monitoring received from a network entity.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH monitoring associated with the MO is not triggered.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH monitoring associated with the MO is triggered. Some implementations of the method and apparatuses described herein may further include: performing PDCCH monitoring in the second active time for PDCCH monitoring; receiving, from a network entity, an indication of stopping the PDCCH monitoring; and ending the second active time for PDCCH monitoring.

Some implementations of the method and apparatuses described herein may further include: skipping the MO, wherein the MO is an invalid MO, wherein the second active time for PDCCH monitoring associated with the invalid MO is not triggered.

In some implementations of the method and apparatuses described herein, a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is no shorter than a duration threshold. Some implementations of the method and apparatuses described herein may further include: performing LP-WUS monitoring in the MO; and determining, based on the LP-WUS monitoring, whether to trigger the second active time for PDCCH monitoring associated with the MO.

Some implementations of the method and apparatuses described herein may further include: turning on the low-power receiver before a duration threshold prior to the MO; and skipping the MO, wherein the MO is at least partially overlapped with the first active time for PDCCH monitoring.

Some implementations of the method and apparatuses described herein may further include: turning on the low-power receiver before a duration threshold prior to the MO; performing LP-WUS monitoring in the MO, wherein the MO is outside the first active time for PDCCH monitoring; and determining, based on the LP-WUS monitoring, whether to trigger the second active time for PDCCH monitoring associated with the MO.

In some implementations of the method and apparatuses described herein, the MO is a first MO in the monitoring window, the monitoring window further includes at least one MO after the first MO. A start of the first MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the first MO is shorter than a duration threshold.

In some implementations of the method and apparatuses described herein, the MO is a first MO in the monitoring window, the monitoring window further includes at least one MO after the first MO. A start of the monitoring window is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the monitoring window is shorter than a duration threshold.

Some implementations of the method and apparatuses described herein may further include: performing LP-WUS monitoring in the at least one MO; and triggering the second active time for PDCCH monitoring associated with the monitoring window, wherein a LP-WUS indicating wake-up is received in the at least one MO.

Some implementations of the method and apparatuses described herein may further include: performing LP-WUS monitoring in the at least one MO, wherein no LP-WUS indicating wake-up is received in the at least one MO.

Some implementations of the method and apparatuses described herein may further include: skipping the at least one MO.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH monitoring associated with the monitoring window is triggered. Some implementations of the method and apparatuses described herein may further include: starting a timer associated with the monitoring window; performing PDCCH monitoring in the second active time for PDCCH monitoring associated with the monitoring window; and ending the second active time for PDCCH monitoring at an expiry of the timer or based on an indication of stopping the PDCCH monitoring received from a network entity.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH monitoring associated with the monitoring window is not triggered.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH monitoring associated with the monitoring window is triggered. Some implementations of the method and apparatuses described herein may further include: performing PDCCH monitoring in the second active time for PDCCH monitoring associated with the monitoring window; receiving, from a network entity, an indication of stopping the PDCCH monitoring; and ending the second active time for PDCCH monitoring.

Some implementations of the method and apparatuses described herein may further include: turning on the low-power receiver before a duration threshold prior to the monitoring window including the MO. The second active time for PDCCH monitoring associated with the monitoring window is not triggered. A start of the monitoring window is within the first active time for PDCCH monitoring.

Some implementations of the method and apparatuses described herein may further include: turning on the low-power receiver before a duration threshold prior to the monitoring window including the MO. The second active time for PDCCH monitoring associated with the monitoring window is not triggered. The MO is a first MO in the monitoring window, a start of the first MO is within the first active time for PDCCH monitoring.

Some implementations of the method and apparatuses described herein may further include: turning on the low-power receiver before a duration threshold prior to the monitoring window including the MO; performing LP-WUS monitoring in at least one MO in the monitoring window; and determining, based on the LP-WUS monitoring, whether to trigger the second active time for PDCCH monitoring associated with the monitoring window. A start of the monitoring window is outside the first active time for PDCCH monitoring.

Some implementations of the method and apparatuses described herein may further include: turning on the low-power receiver before a duration threshold prior to the monitoring window including the MO; performing LP-WUS monitoring in at least one MO in the monitoring window; and determining, based on the LP-WUS monitoring, whether to trigger the second active time for PDCCH monitoring associated with the monitoring window. The MO is a first MO in the monitoring window, a start of the first MO is outside the first active time for PDCCH monitoring.

In some implementations of the method and apparatuses described herein, simultaneous operations of the transceiver and the low-power receiver are supported.

In some implementations of the method and apparatuses described herein, the duration threshold is predefined.

Some implementations of the method and apparatuses described herein may further include: receiving, from a network entity, a configuration associated with LP-WUS monitoring, wherein the configuration includes an indication of the duration threshold.

Some implementations of the method and apparatuses described herein may further include: determining the duration threshold based on capability information of the UE; and transmitting, to a network entity, an indication of the duration threshold.

Some implementations of the method and apparatuses described herein may further include: receiving, from a network entity, the indication related to LP-WUS monitoring, wherein the indication related to LP-WUS monitoring is indicative of changing the MO for LP-WUS monitoring; determining a changed MO; skipping the MO; and performing LP-WUS monitoring in the changed MO.

In some implementations of the method and apparatuses described herein, the indication related to LP-WUS monitoring includes at least one of the following: a time domain location of the MO; a time domain location of the changed MO; an indication of the MO; or a time offset between the MO and the changed MO.

In some implementations of the method and apparatuses described herein, a time offset between the MO and the changed MO is predefined or preconfigured.

Some implementations of the method and apparatuses described herein may further include: transmitting, to a network entity, capability information of the UE.

In some implementations of the method and apparatuses described herein, the capability information includes at least one of the following: an indication of whether simultaneous operations of the transceiver and the low-power receiver are supported; or a time requirement for the low-power receiver to enter an active time for LP-WUS monitoring.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH monitoring associated with the monitoring window starts after an end of the monitoring window or after an end of a last MO in the monitoring window.

Some implementations of the method and apparatuses described herein may further include: receiving, from a network entity, an indication of starting PDCCH monitoring after an end of the monitoring window or an indication of starting PDCCH monitoring after an end of the last MO in the monitoring window.

In a second aspect of the solution, a network entity transmits, to a user equipment (UE) , a configuration associated with low-power wakeup signal (LP-WUS) monitoring by a low-power receiver of the UE. The network entity determines a monitoring occasion (MO) for LP-WUS. The MO is after a first active time for physical downlink control channel (PDCCH) transmission. The network entity determines whether a second active time for PDCCH transmission is available based on the configuration associated with LP-WUS monitoring. The second active time for PDCCH transmission is associated with the MO or a monitoring window including the MO.

In some implementations of the method and apparatuses described herein, a start of the MO is after an end of the first active time for PDCCH transmission, and a time gap between the end of the first active time for PDCCH transmission and the start of the MO is shorter than a duration threshold.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission is available. Some implementations of the method and apparatuses described herein may further include: starting a timer associated with the MO; and ending the second active time for PDCCH transmission at an expiry of the timer or based on an indication of stopping PDCCH monitoring transmitted to the UE.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission is unavailable.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission is available. Some implementations of the method and apparatuses described herein may further include: transmitting, to the UE, an indication of stopping PDCCH monitoring; and ending the second active time for PDCCH transmission.

Some implementations of the method and apparatuses described herein may further include: skipping the MO, wherein the MO is an invalid MO; and wherein the second active time for PDCCH transmission is unavailable.

In some implementations of the method and apparatuses described herein, a start of the MO is after an end of the first active time for PDCCH transmission, and a time gap between the end of the first active time for PDCCH transmission and the start of the MO is no shorter than a duration threshold. Some implementations of the method and apparatuses described herein may further include: performing LP-WUS transmission in the MO; and determining, based on the LP-WUS transmission, whether the second active time for PDCCH transmission is available.

In some implementations of the method and apparatuses described herein, the MO is outside the first active time for PDCCH transmission. Some implementations of the method and apparatuses described herein may further include: determining, based on LP-WUS transmission in the MO, whether the second active time for PDCCH transmission is available.

In some implementations of the method and apparatuses described herein, the MO is a first MO in the monitoring window, the monitoring window further includes at least one MO after the first MO. A start of the first MO is after an end of the first active time for PDCCH transmission, and a time gap between the end of the first active time for PDCCH transmission and the start of the first MO is shorter than a duration threshold.

In some implementations of the method and apparatuses described herein, the MO is a first MO in the monitoring window, the monitoring window further includes at least one MO after the first MO. A start of the monitoring window is after an end of the first active time for PDCCH transmission, and a time gap between the end of the first active time for PDCCH transmission and the start of the monitoring window is shorter than a duration threshold.

Some implementations of the method and apparatuses described herein may further include: transmitting, to the UE, a LP-WUS transmission in the at least one MO, wherein a LP-WUS indicating wake-up is transmitted in the at least one MO, and wherein the second active time for PDCCH transmission associated with the monitoring window is available.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission associated with the monitoring window is available. Some implementations of the method and apparatuses described herein may further include: starting a timer associated with the monitoring window; and ending the second active time for PDCCH transmission at an expiry of the timer or based on an indication of stopping PDCCH monitoring transmitted to the UE.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission associated with the monitoring window is unavailable.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission associated with the monitoring window is available. Some implementations of the method and apparatuses described herein may further include: transmitting, to the UE, an indication of stopping PDCCH monitoring; and ending the second active time for PDCCH transmission.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission associated with the monitoring window is unavailable. A start of the monitoring window is within the first active time for PDCCH transmission.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission associated with the monitoring window is unavailable. The MO is a first MO in the monitoring window, a start of the first MO is within the first active time for PDCCH transmission.

In some implementations of the method and apparatuses described herein, the monitoring window includes at least one MO. Some implementations of the method and apparatuses described herein may further include: performing LP-WUS transmission in the at least one MO; and determining, based on the LP-WUS transmission, whether the second active time for PDCCH transmission associated with the monitoring window is available. A start of the monitoring window is outside the first active time for PDCCH transmission.

In some implementations of the method and apparatuses described herein, the monitoring window includes at least one MO. Some implementations of the method and apparatuses described herein may further include: performing LP-WUS transmission in the at least one MO; and determining, based on the LP-WUS transmission, whether the second active time for PDCCH transmission associated with the monitoring window is available. The MO is a first MO in the monitoring window, a start of the first MO is outside the first active time for PDCCH transmission.

In some implementations of the method and apparatuses described herein, the configuration associated with LP-WUS monitoring includes an indication of a duration threshold for a time gap between the end of the first active time for PDCCH transmission and the start of the monitoring window.

Some implementations of the method and apparatuses described herein may further include: receiving, from the UE, capability information of the UE; and determining the duration threshold based on the capability information of the UE.

Some implementations of the method and apparatuses described herein may further include: receiving, from the UE, an indication of the duration threshold.

Some implementations of the method and apparatuses described herein may further include: transmitting, to the UE, an indication related to LP-WUS monitoring, wherein the indication related to LP-WUS monitoring is indicative of changing the MO for LP-WUS transmission; determining a changed MO; skipping the MO; and performing LP-WUS transmission in the changed MO.

Some implementations of the method and apparatuses described herein may further include: receiving, from the UE, capability information of the UE; and transmitting, to the UE, the indication related to LP-WUS monitoring based on the capability information of the UE.

In some implementations of the method and apparatuses described herein, the capability information includes at least one of the following: an indication of whether the UE supports simultaneous operations of a transceiver and the low-power receiver included in the UE; or a time requirement for the low-power receiver of the UE to enter an active time for LP-WUS monitoring.

In some implementations of the method and apparatuses described herein, the second active time for PDCCH transmission associated with the monitoring window starts after an end of the monitoring window or after an end of a last MO in the monitoring window.

Some implementations of the method and apparatuses described herein may further include: transmitting, to the UE, an indication of starting PDCCH monitoring after an end of the monitoring window or an indication of starting PDCCH monitoring after an end of the last MO in the monitoring window.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example of a wireless communications system that supports handling of LP-WUS in accordance with aspects of the present disclosure.

FIGS. 1B through 1D illustrate examples of missing a LP-WUS monitoring occasion (MO) .

FIG. 1E illustrates an example of a LP-WUS monitoring window.

FIG. 2 illustrates an example signaling chart of a communication process that supports handling of LP-WUS in accordance with some example embodiments of the present disclosure.

FIGS. 3 through 5 illustrate examples of operations in case of missing a LP-WUS MO in accordance with some example embodiments of the present disclosure.

FIGS. 6A through 6B illustrate examples of operations based on validity of a LP-WUS MO in accordance with some example embodiments of the present disclosure.

FIG. 7 illustrates an example of operations of a LP-WUR in accordance with some example embodiments of the present disclosure.

FIG. 8 illustrates an example of location changing of a LP-WUS MO in accordance with some example embodiments of the present disclosure.

FIG. 9 illustrates an example of missing a first LP-WUS MO in a monitoring window in accordance with some example embodiments of the present disclosure.

FIG. 10 illustrates an example of a device that supports handling of LP-WUS in accordance with aspects of the present disclosure.

FIG. 11 illustrates an examples of a processor that supports handling of LP-WUS in accordance with aspects of the present disclosure.

FIGS. 12 and 13 illustrate flowcharts of methods that support handling of LP-WUS in accordance with aspects of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar elements.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof. For example, the term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ” The term “based on” is to be read as “based at least in part on. ” The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ” The term “another embodiment” is to be read as “at least one other embodiment. ” The use of an expression such as “Aand/or B” can mean either “only A” or “only B” or “both A and B. ” Other definitions, explicit and implicit, may be included below.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as, 5G NR, long term evolution (LTE) , LTE-advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , narrow band internet of things (NB-IoT) , and so on. Further, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will also be future type communication technologies and systems in which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned systems.

As used herein, the term “network device” generally refers to a node in a communication network via which a terminal device can access the communication network and receive services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a remote radio unit (RRU) , a radio header (RH) , an infrastructure device for a V2X (vehicle-to-everything) communication, a transmission and reception point (TRP) , a reception point (RP) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto BS, a pico BS, and so forth, depending on the applied terminology and technology.

As used herein, the term “terminal device” generally refers to any end device that may be capable of wireless communications. By way of example rather than a limitation, a terminal device may also be referred to as a communication device, a user equipment (UE) , an end user device, a subscriber station (SS) , an unmanned aerial vehicle (UAV) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) . The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable terminal device, a personal digital assistant (PDA) , a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , a USB dongle, a smart device, wireless customer-premises equipment (CPE) , an internet of things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device (for example, a remote surgery device) , an industrial device (for example, a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms: “terminal device, ” “communication device, ” “terminal, ” “user equipment” and “UE” may be used interchangeably.

Aspects of the present disclosure are described in the context of a wireless communications system. FIG. 1A illustrates an example of a wireless communications system 100 that supports handling of LP-WUS in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1A. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1A. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, 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, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.

An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU)) .

Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.

Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .

A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .

In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

As mentioned above, the power consumption may be dramatically reduced by waking up the UE only when triggered by LP-WUS. This can be achieved by using a WUS to trigger the main radio (MR) and a separate receiver, e.g., a low-power receiver (LR) , which has the ability to monitor LP-WUS with ultra-low power consumption. Specifically, MR is the Tx/Rx module operating for NR signals/channels apart from signals/channel related to low-power wake-up, and LR is the Rx module operating for receiving/processing signals/channel related to low-power wake-up. With the assistance of LR, MR can have more opportunity to enter sleep state, thus saving UE’s power consumption. As used herein, the terms “LR” and “LP-WUR” may be used interchangeably.

For RRC CONNECTED mode, PDCCH monitoring is triggered by LP-WUS with C-DRX configuration. In a first option, LP-WUS is monitored according to the LP-WUS monitoring configuration before drx-onDurationTimer to trigger the starting of the drx-onDurationTimer. LR is turned on to monitor LP-WUS before the drx-onDurationTimer configured according to the LP-WUS monitoring configuration; if LP-WUS is detected, the drx-onDurationTimer is started to monitor PDCCH with MR; if LP-WUS is not detected, the start of the drx-onDurationTimer is skipped and PDCCH would not be monitored using MR. If the UE receives a DRX command MAC CE or a long DRX command MAC CE, the UE stops the drx-onDurationTimer.

In a second option, LP-WUS is monitored outside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring. LP-WUS MOs are configured according to the LP-WUS monitoring configuration to monitor LP-WUS; in response to detecting a LP-WUS at a MO, the MR wakes up, a timer is started , and the PDCCH is monitored with the MR. If the UE receives a DRX command MAC CE or a long DRX command MAC CE, the UE stops the timer triggered by LP-WUS.

When the UE is in C-DRX active time, UE PDCCH monitoring behaviors related to other legacy DRX timers (except for drx-onDurationTimer) are not affected. For RRC CONNECTED mode, the maximum number of LP-WUS information bits is up to X bits, where X is no more than 8 or 16. LP-WUS MOs may be configured by RRC, at which the UE can monitor for LP-WUS transmission in RRC CONNECTED mode.

For LP-WUS MOs in connected mode for the first option of LP-WUS CONNECTED mode operation, it is proposed that LP-WUS MOs, including periodicity and offset, are configured independently from the C-DRX periodicity/offset by RRC parameter (s) . The UE selectively monitors LP-WUS in the LP-WUS MOs identified by other parameters such as time offset prior to the start of drx-onDurationTimer. In another approach, it is proposed that LP-WUS MOs, including periodicity and offset, are identified based on the slot that drx-onDurationTimer would start and a RRC parameter indicating the time offset until the slot that drx-onDurationTimer would start. Consecutive LP-WUS MOs in time identified by a RRC parameter may be associated with a same C-DRX cycle. UE does not expect to detect more than one LP-WUSs with different indications for the UE in the LP-WUS MOs associated with the same C-DRX cycle.

For LP-WUS MOs in connected mode for the second option of LP-WUS CONNECTED mode operation, it is proposed that LP-WUS MOs, including periodicity and offset, are configured independently from the C-DRX periodicity/offset by RRC parameter (s) . UE monitors LP-WUS in the LP-WUS MOs and starts a timer for PDCCH monitoring triggered by LP-WUS, after a time offset. In another approach, it is proposed that periodicity/offset of the slot that the timer for PDCCH monitoring may be potentially triggered by LP-WUS are configured by RRC parameters. LP-WUS MOs, including periodicity and offset, are identified based on the slot that timer would start and a RRC parameter indicating the time offset until the slot that timer would start. Consecutive LP-WUS MOs in time identified by a RRC parameter may be associated with the same slot that the timer would start. UE does not expect to detect more than one LP-WUSs with different indications for the UE in the LP-WUS MOs associated with the same slot that the timer would start.

For RRC_CONNECTED mode, regarding how LR monitors MO, two cases are proposed, namely, Case 1 in which LR monitors LP-WUS at every configured MO; and Case 2 in which LR doesn’ t monitor LP-WUS during an active time for PDCCH monitoring. The advantage of Case 1 is that LR will not miss any MO. However, Case 1 may bring the issue that LR monitors LP-WUS during an active time for PDCCH monitoring. It is proposed to support at least that LR is not able to receive signal (s) during the time where MR transmits/receives signals/channels (i.e., Case 2) . As used herein, the term “active time of PDCCH monitoring” may be interchangeably used with the terms “active time for MR” and “active time for PDCCH transmission” .

For RRC CONNECTED mode, minimum time gap between LP-WUS reception and MR to start PDCCH monitoring is introduced considering at least following: LP-WUS processing time, MR transition time for ramp up, and time/frequency synchronization of MR.

For RRC CONNECTED mode, it is proposed to support UE capability report for determination of minimum time gap between LP-WUS reception and MR to start PDCCH monitoring. For RRC CONNECTED mode, UE reports one value for each SCS from X candidate values for the determination of the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring via UE capability reporting via UE capability reporting.

The active time of MR is dynamic since it can be impacted by network indication (e.g., (long) DRX command MAC CE) and various timers (e.g., drx-onDurationTimer, the timer for the second option of LP-WUS CONNECTED mode operation, drx-inactivityTimer, drx-reTransmissionTimer, etc. ) . On the other hand, in the case of LR is in off-state during the active time of MR, it may need some time for LR to start monitoring LP-WUS after the end of the active time of MR, e.g., LR ramp up time, processing time for network indication (e.g., (long) DRX command MAC CE) , the time for LR to obtain synchronization information from MR, etc. In the case of LR doesn’ t monitor LP-WUS during the active time of MR (Case 2) , it’s possible that the duration between the end of the active time of MR and the start of the most recent MO after the active time of MR may be shorter than the required LR transition time/ramp-up time/switch time, causing LR miss the LP-WUS of the most recent MO after the active time of MR. As used herein, the terms “LP-WUS MO” and “MO” may be used interchangeably.

FIGS. 1B through 1C illustrate examples of missing a LP-WUS MO in the first option of LP-WUS CONNECTED mode operation. In the examples of FIG. 1B and FIG. 1C, the UE needs to perform LP-WUS monitoring prior to the drx-onDurationTimer to determine whether to trigger the starting of the drx-onDurationTimer. In the example of FIG. 1B, the previous active time of MR ends when the DRX-InactivityTimer duration expires. In the example of FIG. 1C, the previous active time of MR ends in response to receiving a (long) DRX command MAC CE transmitted by the gNB. The time gap between the end of the previous active time of MR and the LP-WUS MO is less than the LR transition time/ramp-up time/switch time, so the UE will miss the LP-WUS MO and will not be able to know whether the gNB has transmitted the LP-WUS or not, and thus, will not know whether to trigger the starting of the drx-onDurationTimer.

FIG. 1D illustrates an example of missing a LP-WUS MO in the second option of LP-WUS CONNECTED mode operation. In the example of FIG. 1D, the UE needs to perform LP-WUS monitoring at LP-WUS MOs outside the active time of MR. The time gap between the end of the previous active time of MR and the next LP-WUS MO is less than the LR transition time/ramp-up time/switch time, so the UE will miss the LP-WUS MO and will not be able to know whether the gNB has transmitted the LP-WUS or not, and thus, will not know whether to trigger the starting of a timer to monitor PDCCH.

Thus, in the case that LR doesn’ t monitor LP-WUS in the active time of MR, the UE might miss the most recent MO after an active time of MR due to the potential LR ramp-up time. Enhancements are needed to keep alignment between the network and UE considering the potential cases that the UE might miss the LP-WUS MO. As used herein, when referring to ‘most recent MO’ , the LR ramp-up is not considered. i.e., ‘most recent MO’ is the configured MO which is nearest with the end of the active time of MR, no matter whether LR is on or off.

In addition, the UE may be configured with monitoring windows, each containing multiple LP-WUS MOs for monitoring LP-WUS in RRC_CONNECTED mode. FIG. 1E illustrates an example of a LP-WUS monitoring window. In the case that LR doesn’ t monitor LP-WUS in the active time of MR, the UE might miss the LP-WUS MO in the monitoring window due to the potential LR ramp-up time. Enhancements are needed to keep alignment between the network and UE considering the potential cases that the UE might miss the LP-WUS MO in the monitoring window.

In view of the above, embodiments of the present disclosure provide solutions for handling of LP-WUS. In an aspect of the solution, if a determined LP-WUS MO is after a first active time for PDCCH monitoring, the UE determines whether to trigger a second active time for PDCCH monitoring associated with the LP-WUS MO or a monitoring window comprising the LP-WUS MO. The gNB may determine whether the second active time for PDCCH transmission is available following the same rule. In this way, operations of the gNB and the UE may be aligned considering the case that the UE might miss the LP-WUS MO. The communication performance may thus be improved.

Reference is now made to FIG. 2, which illustrates an example signaling chart of a communication process 200 that supports handling of LP-WUS in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to FIG. 1A. The process 200 may involve the UE 104 and the network entity 102 in FIG. 1A. The network entity 102 may be implemented as a base station. The UE 104 may include a MR and a LR. It is to be understood that the steps and the order of the steps in FIG. 2 are merely for illustration, and not for limitation. It is to be understood that process 200 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.

As shown in FIG. 2, the UE 104 performs (204) PDCCH monitoring in the first active time for PDCCH monitoring. Correspondingly, the base station 102 may perform PDCCH transmission to the UE 104 in the first active time. The first active time may end based on a network indication or a timer expiration. The UE 104 determines (205) a MO for LP-WUS located after the first active time for PDCCH transmission. The UE 104 determines (207) whether to trigger a second active time for PDCCH monitoring based on at least one of the following: a time location of the first active time, a time location of the MO for LP-WUS, a time location of a monitoring window comprising the MO for LP-WUS, or an indication related to LP-WUS monitoring received from the base station 102. Similarly, the base station 102 determines (206) the same MO for LP-WUS and determines (208) whether the second active time for PDCCH transmission is available following the same rule. In this way, the UE and the base station may keep alignment on operations regarding LP-WUS/WUR. The communication performance and reliability may thus be improved, and communication latency may be reduced.

In some embodiments, a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is no shorter than a duration threshold. In such cases, the UE 104 and the base station 102 may assume that the MO is not missed by the UE 104. The UE 104 may perform LP-WUS monitoring in the MO, and determine whether to trigger the second active time for PDCCH monitoring associated with the MO based on the LP-WUS monitoring in the MO. Accordingly, the base station 102 may determine whether the second active time for PDCCH transmission is available based on the LP-WUS transmission in the MO. For example, if a LP-WUS indicating wake-up is transmitted in the MO, the UE 104 triggers the second active time for PDCCH monitoring associated with the MO, and the second active time is available for PDCCH transmission.

In some implementations, a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is shorter than the duration threshold. In such cases, the UE 104 and the base station 102 may assume that the MO is missed by the UE 104. In this way, the UE and the network may have a common understanding on whether the MO will be missed by the UE.

In some examples, the duration threshold may be predefined. In other words, the duration threshold may be specified as a fixed value (e.g., 3 ms) . Alternatively, the UE 104 may receive (203) a configuration 202 associated with LP-WUS monitoring from the base station 102, and the configuration may include an indication of the duration threshold. In other words, the duration threshold may be configured by the base station 102. For example, the UE 104 may transmit capability information of the UE 104 to the base station 102. The capability information may include an indication of whether simultaneous operations of the MR and the LR are supported. Alternatively or additionally, the capability information may include a time requirement for the LR to enter an active time for LP-WUS monitoring. The base station 102 may determine the duration threshold based on the capability information of the UE 104, and transmit (201) the configuration 202 including an indication of the duration threshold to the UE 104. In other words, the UE 104 may report its capability to the base station 102, which may include whether LR and MR are able to operate simultaneously and a minimum LR transition time/ramp-up time/switch time. The base station 102 may determine/configure the duration threshold based on the UE reported capability.

Alternatively, the UE 104 may determine the duration threshold based on capability information of the UE 104. The capability information may include an indication of whether simultaneous operations of the MR and the LR are supported. Alternatively or additionally, the capability information may include a time requirement for the LR to enter an active time for LP-WUS monitoring. The UE 104 may transmit an indication of the duration threshold to the base station 102. In other words, the duration threshold may be determined by the UE 104 itself e.g., based on the LR capability of transition time/ramp-up time/switch time.

In some embodiments, a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is shorter than the duration threshold. The second active time for PDCCH monitoring associated with the MO may be triggered. The UE 104 may start a timer associated with the MO, and perform PDCCH monitoring in the second active time for PDCCH monitoring. The second active time for PDCCH monitoring may end at an expiry of the timer or based on an indication of stopping the PDCCH monitoring received from the base station 102. In other words, if the time gap between the end of the previous active time of MR and the start of MO is shorter than the duration threshold, the UE 104 and the base station 102 assume that the UE 104 misses the MO after the previous active time of MR, and start a related timer for PDCCH monitoring after the missed MO to monitor PDCCH. For example, if the first option of LP-WUS CONNECTED mode operation is applied, a drx-onDurationTimer may be started after the missed MO to monitor PDCCH. In another example, if the second option of LP-WUS CONNECTED mode operation is applied, a timer associated with the LP-WUS MO may be started after the missed MO to monitor PDCCH. The duration threshold may be configured by the base station 102 or determined by the UE 104 itself e.g., based on the UE capability of LR transition time/ramp-up time/switch time and whether LR and MR are able to operate simultaneously, or may be predefined. LR and MR are not required to operate simultaneously. LR may be in off-state during the active time of MR and needs to ramp up after the active time of MR ends.

FIG. 3 illustrates an example of operations in case of missing a LP-WUS MO in accordance with some example embodiments of the present disclosure. As shown in FIG. 3, the time point T0 is the duration threshold earlier than the start of a MO. The time point T0 is within an active time of MR, and the MO is after the end of the active time of MR. Thus, the MO will be missed by the UE. A related timer for PDCCH monitoring is then started, and an active time of MR associated with the MO is available. The active time of MR associated with the MO ends at an expiry of the timer or upon receiving an indication of stopping PDCCH monitoring.

In some embodiments, a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is shorter than the duration threshold. The second active time for PDCCH monitoring associated with the MO may be not triggered. In other words, If the time gap between the end of the previous active time of MR and the start of MO is shorter than a duration threshold, the UE 104 and the base station 102 assume that the UE 104 misses the MO after the previous active time of MR, and do not start the related timer after the missed MO. The base station 102 will not transmit PDCCH during the timer associated with the missed MO. The duration threshold may be configured by the base station 102 or determined by the UE 104 itself e.g., based on the UE capability of LR transition time/ramp-up time/switch time and whether LR and MR are able to operate simultaneously, or may be predefined. LR and MR are not required to operate simultaneously. LR may be in off-state during the active time of MR and needs to ramp up after the active time of MR ends.

FIG. 4 illustrates an example of operations in case of missing a LP-WUS MO in accordance with some example embodiments of the present disclosure. As shown in FIG. 4, the time point T0 is the duration threshold earlier than the start of a MO. The time point T0 is within an active time of MR, and the MO is after the end of the active time of MR. Thus, the MO will be missed by the UE. The related timer for PDCCH monitoring is not started, and an active time of MR associated with the MO is unavailable.

In some embodiments, a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is shorter than the duration threshold. The second active time for PDCCH monitoring associated with the MO may be triggered. The UE 104 may perform PDCCH monitoring in the second active time for PDCCH monitoring. If the UE 104 receives an indication of stopping the PDCCH monitoring from the base station 102, the second active time for PDCCH monitoring may end accordingly. In other words, if the time gap between the end of the previous active time of MR and the start of MO is shorter than the duration threshold, the UE 104 and the base station 102 assume that the UE 104 misses the MO after the previous active time of MR. The UE 104 keeps monitoring PDCCH until the base station 102 transmits a stop indication (e.g., (long) DRX command MAC CE) to the UE 104. For example, if there’s traffic for the UE 104, the base station 102 may transmit PDCCH to the UE 104 after the MO. If there’s not traffic for the UE 104, the base station 102 may transmit a stop indication (e.g., (long) DRX command MAC CE) to the UE 104. Upon receiving the stop indication, the UE 104 may stop PDCCH monitoring and start LP-WUS monitoring. The duration threshold may be configured by the base station 102 or determined by the UE 104 itself e.g., based on the UE capability of LR transition time/ramp-up time/switch time and whether LR and MR are able to operate simultaneously, or may be predefined. LR and MR are not required to operate simultaneously. LR may be in off-state during the active time of MR and needs to ramp up after the active time of MR ends.

FIG. 5 illustrates an example of operations in case of missing a LP-WUS MO in accordance with some example embodiments of the present disclosure. As shown in FIG. 5, the time point T0 is the duration threshold earlier than the start of a MO. The time point T0 is within an active time of MR, and the MO is after the end of the active time of MR. Thus, the MO will be missed by the UE. An active time of MR associated with the MO is then available after the MO. The active time of MR associated with the MO ends upon receiving an indication of stopping PDCCH monitoring.

In some embodiments, a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is shorter than the duration threshold. The UE 104 may determine the MO as an invalid MO and skip the MO. Similarly, the base station 102 may skip the MO. The second active time for PDCCH monitoring associated with the invalid MO is not triggered. In other words, a MO before the end of a duration threshold after the previous active time of MR may be regarded as an invalid (or ineffective) MO and may be skipped. The term “skipping the MO” means that the base station does not transmit LP-WUS in the skipped MO, and the UE does not monitor/receive LP-WUS in the MO. The UE only monitors LP-WUS in valid (or effective) MO which is after the duration threshold after the previous active time of MR. The duration threshold may be configured by the base station 102 or determined by the UE 104 itself e.g., based on the UE capability of LR transition time/ramp-up time/switch time, or may be predefined. LR and MR are not required to operate simultaneously. LR may be in off-state during the active time of MR and needs to ramp up after the active time of MR ends.

FIGS. 6A through 6B illustrate examples of operations based on validity of a LP-WUS MO in accordance with some example embodiments of the present disclosure. In the example in FIG. 6A, a MO is after the end of an active time of MR, but before an end of a duration threshold after the end of the active time of MR. Thus, the MO is invalid (or ineffective) and will be skipped. The network device will not transmit LP-WUS in the invalid MO. In the example in FIG. 6B, a MO is after a duration threshold after the end of the active time of MR. Thus, the MO is valid (or effective) . The UE may perform LP-WUS monitoring in the MO.

In some embodiments, the UE 104 may turn on the LR at least before a duration threshold prior to the MO. The UE 104 may support simultaneous operations of the MR and the LR. In other words, LR and MR of the UE 104 can operate simultaneously, and the LR wakes up at least before a time gap duration threshold before each MO, in the case that LR and MR are able to operate simultaneously. The duration threshold may be configured by the base station 102 or determined by the UE 104 itself e.g., based on the UE capability of LR transition time/ramp-up time/switch time and whether LR and MR are able to operate simultaneously, or may be predefined. In some implementations, if the MO is at least partially overlapped with the first active time for PDCCH monitoring. The UE 104 may skip the MO. In other words, if an active time of MR covers the MO, LR doesn’ t monitor LP-WUS during MO. If an active time of MR ends at a time point within MO, LR doesn’ t monitor LP-WUS during the MO. In some implementations, if the MO is outside the first active time for PDCCH monitoring, the UE 104 may perform LP-WUS monitoring in the MO, and determine whether to trigger the second active time for PDCCH monitoring associated with the MO based on the LP-WUS monitoring in the MO. In other words, if an active time of MR ends before the MO, the LR is able to monitor LP-WUS during the MO. In this way, the MO will not be missed.

FIG. 7 illustrates an example of operations of a LP-WUR in accordance with some example embodiments of the present disclosure. As shown in FIG. 7, the LR wakes up and prepares for LP-WUS monitoring at a time point (shown in a dashed line with upward arrow) which is a duration threshold earlier than the start of each MO. The LR may monitor LP-WUS at MOs outside the active time of MR.

In some embodiments, the UE 104 may receive the indication related to LP-WUS monitoring from the base station 102. The indication related to LP-WUS monitoring may be indicative of changing the MO for LP-WUS monitoring. The UE 104 may then determine a changed MO, and perform LP-WUS monitoring in the changed MO. The original MO may be skipped. In other words, the MO location may be dynamically changed based on network signalling. For example, the base station 102 transmits MO change signalling (e.g., MAC CE, DCI) to the UE 104 before the end of an active time of MR to change the location of MO which might be missed.

In some implementations, the indication related to LP-WUS monitoring may include a time domain location of the MO. Alternatively or additionally, the indication related to LP-WUS monitoring may include a time domain location of the changed MO. Alternatively or additionally, the indication related to LP-WUS monitoring may include an indication of the MO. Alternatively or additionally, the indication related to LP-WUS monitoring may include a time offset between the MO and the changed MO. Alternatively, a time offset between the MO and the changed MO may be predefined or preconfigured. For example, the MO change signalling may include the location information of new MO and the location information of original MO. In another example, the MO change signalling may include the location information of original MO and the change value. In a further example, the MO change value may be (pre) configured via a dedicated signalling (e.g., RRC message) or system information, and the MO change signalling may include the location information of original MO.

In some implementations, the UE 104 may transmit capability information of the UE 104 to the base station 102. The capability information may include an indication of whether simultaneous operations of the MR and the LR are supported. Alternatively or additionally, the capability information may include a time requirement for the LR to enter an active time for LP-WUS monitoring. The base station 102 may determine whether the MO will be missed by the UE 104 based on the capability information of the UE 104. For example, the base station 102 determines whether the MO will be missed based on the UE reported capability, which may include whether LR and MR are able to operate simultaneously and minimum LR transition time/ramp-up time/switch time. If the MO will be missed by the UE 104, the base station 102 may transmit, to the UE 104, the indication related to LP-WUS monitoring to indicate changing the MO for LP-WUS transmission. The base station 102 may skip the original MO, and transmit LP-WUS in the new MO if there is traffic.

FIG. 8 illustrates an example of location changing of a LP-WUS MO in accordance with some example embodiments of the present disclosure. As shown in FIG. 8, if the base station determines that a MO might be missed by the UE (e.g., if a time gap between the end of an active time for MR and the start of the MO is shorter than a duration threshold) , the base station may transmit an indication to change the MO location before the active time for MR ends. The LP-WUS monitoring may be performed during the changed MO.

In some embodiments, the MO may be the first MO in the monitoring window, the monitoring window may further include at least one MO after the first MO. In other words, a monitoring window containing multiple MOs may be configured. In some implementations, if the UE 104 receives LP-WUS for the UE 104 in one MO (not the last one) in the monitoring window, the UE 104 doesn’ t need to monitor subsequent MOs in the monitoring window, or the UE 104 doesn’ t need to process the LP-WUS of subsequent MOs in the monitoring window.

In some implementations, a start of the first MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the first MO is no shorter than a duration threshold. In such cases, the UE 104 and the base station 102 may assume that the first MO in the monitoring window is not missed by the UE 104. The UE 104 may perform LP-WUS monitoring in MOs in the monitoring window, and determine whether to trigger the second active time for PDCCH monitoring associated with the monitoring window based on the LP-WUS monitoring in the MOs. Accordingly, the base station 102 may determine whether the second active time for PDCCH transmission is available based on the LP-WUS transmission in the MOs. In some implementations, a start of the first MO may be after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the first MO may be shorter than the duration threshold. In such cases, the UE 104 and the base station 102 may assume that the first MO in the monitoring window is missed by the UE 104. In this way, the UE and the network may have a common understanding on whether the first MO in the monitoring window will be missed by the UE based on the location of the first MO.

In some implementations, a start of the monitoring window is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the monitoring window is no shorter than a duration threshold. In such cases, the UE 104 and the base station 102 may assume that the first MO in the monitoring window is not missed by the UE 104. The UE 104 may perform LP-WUS monitoring in MOs in the monitoring window, and determine whether to trigger the second active time for PDCCH monitoring associated with the monitoring window based on the LP-WUS monitoring in the MOs. Accordingly, the base station 102 may determine whether the second active time for PDCCH transmission is available based on the LP-WUS transmission in the MOs. In some implementations, a start of the monitoring window may be after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the monitoring window may be shorter than the duration threshold. In such cases, the UE 104 and the base station 102 may assume that the first MO in the monitoring window is missed by the UE 104. In this way, the UE and the network may have a common understanding on whether the first MO in the monitoring window will be missed by the UE based on the location of the start of the monitoring window.

FIG. 9 illustrates an example of missing the first LP-WUS MO in a monitoring window in accordance with some example embodiments of the present disclosure. In the example in FIG. 9, the time gap between the end of an active time for MR and the start of the monitoring window (or the start of the first MO in the monitoring window) is shorter than a duration threshold. Thus, the first MO in the monitoring window will be missed by the UE.

In some examples, the second active time for PDCCH monitoring associated with the monitoring window starts after an end of the monitoring window or after an end of a last MO in the monitoring window. In other words, after receiving a LP-WUS indicating wake-up, the UE 104 may start to monitor PDCCH after the end of the monitoring window or the end of the last MO in the monitoring window. In an example implementation, the UE 104 may receive, from the base station 102, an indication of starting PDCCH monitoring after an end of the monitoring window or an indication of starting PDCCH monitoring after an end of the last MO in the monitoring window. In other words, whether to start PDCCH monitoring after the end of monitoring window or the end of the last MO in the monitoring window may be configured by the base station 102. Alternatively, whether to start PDCCH monitoring after the end of monitoring window or the end of the last MO in the monitoring window may be specified.

In some embodiments, a start of the first MO (or a start of the monitoring window) is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the first MO (or the start of the monitoring window) is shorter than the duration threshold. The UE 104 may perform LP-WUS monitoring in the at least one MO after the first MO. In other words, if the UE 104 misses the first MO in the monitoring window after the previous active time of MR, the UE 104 may monitor other MOs in the monitoring window. The duration threshold may be configured by the base station 102 or determined by the UE 104 itself e.g., based on the UE capability of LR transition time/ramp-up time/switch time and whether LR and MR are able to operate simultaneously, or may be predefined.

In some implementations, if a LP-WUS indicating wake-up is received in the at least one MO after the first MO, the UE 104 may trigger the second active time for PDCCH monitoring associated with the monitoring window. In some examples, the reception of the LP-WUS may be indicative wake-up. In some other examples, the LP-WUS may include an indication indicative of wake-up. In other words, if the UE 104 receives LP-WUS for the UE 104 in the other MOs in the same monitoring window, the UE 104 behaves as the received LP-WUS indicated.

In some implementations, no LP-WUS indicating wake-up is received in the at least one MO. In some examples, the second active time for PDCCH monitoring associated with the monitoring window may be triggered. The UE 104 may start a timer associated with the monitoring window and perform PDCCH monitoring in the second active time for PDCCH monitoring associated with the monitoring window. The second active time for PDCCH monitoring may end at an expiry of the timer or based on an indication of stopping the PDCCH monitoring received from the base station 102. In other words, if the UE 104 doesn’ t receive LP-WUS for the UE 104 in the other MOs in the same monitoring window, the UE 104 may start a related timer to monitor PDCCH (e.g., drx-onDurationTimer, or other timers) .

In some other examples, if no LP-WUS indicating wake-up is received in the at least one MO, the second active time for PDCCH monitoring associated with the monitoring window may be not triggered. In other words, if the UE 104 doesn’ t receive LP-WUS for the UE 104 in the other MOs in the same monitoring window, the UE 104 does not start a related timer to monitor PDCCH.

In some further examples, if no LP-WUS indicating wake-up is received in the at least one MO, the second active time for PDCCH monitoring associated with the monitoring window may be triggered. The UE 104 may perform PDCCH monitoring in the second active time for PDCCH monitoring associated with the monitoring window. If the UE 104 receives an indication of stopping the PDCCH monitoring from the base station 102, the second active time for PDCCH monitoring may end accordingly. In other words, if the UE 104 doesn’ t receive LP-WUS for the UE 104 in the other MOs in the same monitoring window, the UE 104 keeps monitoring PDCCH until receiving a stop indication from the network.

In some embodiments, a start of the first MO (or a start of the monitoring window) is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the first MO (or the start of the monitoring window) is shorter than the duration threshold. The UE 104 may skip the at least one MO. In other words, if the UE 104 misses the first MO in the monitoring window after the active time of MR, the UE 104 doesn’ t monitor LP-WUS in other MOs in the same monitoring window. The duration threshold may be configured by the base station 102 or determined by the UE 104 itself e.g., based on the UE capability of LR transition time/ramp-up time/switch time and whether LR and MR are able to operate simultaneously, or may be predefined.

In some examples, the second active time for PDCCH monitoring associated with the monitoring window may be triggered. The UE 104 may start a timer associated with the monitoring window and perform PDCCH monitoring in the second active time for PDCCH monitoring associated with the monitoring window. The second active time for PDCCH monitoring may end at an expiry of the timer or based on an indication of stopping the PDCCH monitoring received from the base station 102. In other words, without monitoring other MOs in the monitoring window, the UE 104 may start a related timer to monitor PDCCH (e.g., drx-onDurationTimer, or other timers) .

In some other examples, if the at least one MO is skipped, the second active time for PDCCH monitoring associated with the monitoring window may be not triggered. In other words, without monitoring other MOs in the monitoring window, the UE 104 does not start a related timer to monitor PDCCH.

In some further examples, if the at least one MO is skipped, the second active time for PDCCH monitoring associated with the monitoring window may be triggered. The UE 104 may perform PDCCH monitoring in the second active time for PDCCH monitoring associated with the monitoring window. If the UE 104 receives an indication of stopping the PDCCH monitoring from the base station 102, the second active time for PDCCH monitoring may end accordingly. In other words, without monitoring other MOs in the monitoring window, the UE 104 keeps monitoring PDCCH until receiving a stop indication from the network.

In some embodiments, the UE 104 may turn on the LR before the duration threshold prior to the monitoring window comprising the MO. The UE 104 may support simultaneous operations of the MR and the LR. In other words, the LR wakes up at least before a time gap duration threshold before each monitoring window, and prepares to monitor PDCCH during the monitoring window, in the case that LR and MR are able to operate simultaneously. The duration threshold may be configured by the base station 102 or determined by the UE 104 itself e.g., based on the UE capability of LR transition time/ramp-up time/switch time, or may be predefined.

In some implementations, if a start of the monitoring window (or a start of the first MO in the monitoring window) is within the first active time for PDCCH monitoring, the second active time for PDCCH monitoring associated with the monitoring window is not triggered. In other words, if the previous active time of MR covers the monitoring window, LR does not monitor LP-WUS in MOs in the monitoring window. In this way, the MO will not be missed. In some implementations, if a start of the monitoring window (or a start of the first MO in the monitoring window) is outside the first active time for PDCCH monitoring, the UE 104 may perform LP-WUS monitoring in at least one MO in the monitoring window, and determine, based on the LP-WUS monitoring, whether to trigger the second active time for PDCCH monitoring associated with the monitoring window. In other words, if the previous active time of MR ends before the monitoring window, LR is able to monitor LP-WUS in MOs in the monitoring window.

FIG. 10 illustrates an example of a device 1000 that supports handling of LP-WUS in accordance with aspects of the present disclosure. The device 1000 may be an example of a UE 104 or a base station 102 as described herein. The device 1000 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 1000 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 1002, a memory 1004, a transceiver 1006, and, optionally, an I/O controller 1008. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1002, the memory 1004, the transceiver 1006, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004) .

In an example, the processor 1002 may support wireless communication at the device 1000 in accordance with examples as disclosed herein. The processor 1002 may be configured to operable to support a means for performing physical downlink control channel (PDCCH) monitoring in a first active time; a means for determining a monitoring occasion (MO) for low-power wakeup signal (LP-WUS) ; and a means for determining whether to trigger a second active time for PDCCH monitoring based on at least one of the following: a time location of the first active time, a time location of the MO for LP-WUS, a time location of a monitoring window comprising the MO for LP-WUS, or an indication related to LP-WUS monitoring received from a network entity.

In another example, the processor 1002 may support wireless communication at the device 1000 in accordance with examples as disclosed herein. The processor 1002 may be configured to operable to support a means for transmitting, to a user equipment (UE) , a configuration associated with low-power wakeup signal (LP-WUS) monitoring by a low-power receiver of the UE; a means for determining a monitoring occasion (MO) for LP-WUS, wherein the MO is after a first active time for physical downlink control channel (PDCCH) transmission; and a means for determining whether a second active time for PDCCH transmission is available based on the configuration associated with LP-WUS monitoring, wherein the second active time for PDCCH transmission is associated with the MO or a monitoring window comprising the MO.

The processor 1002 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 1002 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1004) to cause the device 1000 to perform various functions of the present disclosure such that the device 1000 may perform any process of the disclosure as discussed with reference to FIGS. 2 to 9.

The memory 1004 may include random access memory (RAM) and read-only memory (ROM) . The memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1002 cause the device 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 1002 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 1004 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 1008 may manage input and output signals for the device 1000. The I/O controller 1008 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 1008 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 1008 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 1008 may be implemented as part of a processor, such as the processor 1002. In some implementations, a user may interact with the device 1000 via the I/O controller 1008 or via hardware components controlled by the I/O controller 1008.

In some implementations, the device 1000 may include a single antenna 1010. However, in some other implementations, the device 1000 may have more than one antenna 1010 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1006 may communicate bi-directionally, via the one or more antennas 1010, wired, or wireless links as described herein. For example, the transceiver 1006 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1006 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1010 for transmission, and to demodulate packets received from the one or more antennas 1010. The transceiver 1006 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 1010 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 1010 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

FIG. 10 illustrates an example of a processor 1100 that supports handling of LP-WUS in accordance with aspects of the present disclosure. The processor 1100 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1100 may be implemented in a device or its components as described herein. For example, the device may be an example of a UE 104 or a base station 102 as described herein. The processor 1100 may include a controller 1102 configured to perform various operations in accordance with examples as described herein. The processor 1100 may optionally include at least one memory 1104, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1100 may optionally include one or more arithmetic-logic units (ALUs) 1106. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1100 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1100) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 1102 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. For example, the controller 1102 may operate as a control unit of the processor 1100, generating control signals that manage the operation of various components of the processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1104 and determine subsequent instruction (s) to be executed to cause the processor 1100 to support various operations in accordance with examples as described herein. The controller 1102 may be configured to track memory address of instructions associated with the memory 1104. The controller 1102 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1102 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1102 may be configured to manage flow of data within the processor 1100. The controller 1102 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1100.

The memory 1104 may include one or more caches (e.g., memory local to or included in the processor 1100 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1104 may reside within or on a processor chipset (e.g., local to the processor 1100) . In some other implementations, the memory 1104 may reside external to the processor chipset (e.g., remote to the processor 1100) .

The memory 1104 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1100, cause the processor 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1102 and/or the processor 1100 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the processor 1100 to perform various functions. For example, the processor 1100 and/or the controller 1102 may be coupled with or to the memory 1104, and the processor 1100, the controller 1102, and the memory 1104 may be configured to perform various functions described herein. In some examples, the processor 1100 may include multiple processors and the memory 1104 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 1106 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 1106 may reside within or on a processor chipset (e.g., the processor 1100) . In some other implementations, the one or more ALUs 1106 may reside external to the processor chipset (e.g., the processor 1100) . One or more ALUs 1106 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1106 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1106 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1106 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1106 to handle conditional operations, comparisons, and bitwise operations.

In an example, the processor 1100 may support wireless communication in accordance with examples as disclosed herein. The processor 1100 may be configured to or operable to support a means for performing physical downlink control channel (PDCCH) monitoring in a first active time; a means for determining a monitoring occasion (MO) for low-power wakeup signal (LP-WUS) ; and a means for determining whether to trigger a second active time for PDCCH monitoring based on at least one of the following: a time location of the first active time, a time location of the MO for LP-WUS, a time location of a monitoring window comprising the MO for LP-WUS, or an indication related to LP-WUS monitoring received from a network entity.

In another example, the processor 1100 may support wireless communication in accordance with examples as disclosed herein. The processor 1100 may be configured to or operable to support a means for transmitting, to a user equipment (UE) , a configuration associated with low-power wakeup signal (LP-WUS) monitoring by a low-power receiver of the UE; a means for determining a monitoring occasion (MO) for LP-WUS, wherein the MO is after a first active time for physical downlink control channel (PDCCH) transmission; and a means for determining whether a second active time for PDCCH transmission is available based on the configuration associated with LP-WUS monitoring, wherein the second active time for PDCCH transmission is associated with the MO or a monitoring window comprising the MO.

FIG. 12 illustrates a flowchart of a method 1200 that supports handling of LP-WUS in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a device or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 104 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1205, the method may include performing physical downlink control channel (PDCCH) monitoring in a first active time. The operations of 1205 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1205 may be performed by a device as described with reference to FIG. 1A.

At 1210, the method may include determining a monitoring occasion (MO) for low-power wakeup signal (LP-WUS) . The operations of 1210 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1210 may be performed by a device as described with reference to FIG. 1A.

At 1215, the method may include determining whether to trigger a second active time for PDCCH monitoring based on at least one of the following: a time location of the first active time, a time location of the MO for LP-WUS, a time location of a monitoring window comprising the MO for LP-WUS, or an indication related to LP-WUS monitoring received from a network entity. The operations of 1215 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1215 may be performed by a device as described with reference to FIG. 1A.

FIG. 13 illustrates a flowchart of a method 1300 that supports handling of LP-WUS in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a device or its components as described herein. For example, the operations of the method 1300 may be performed by a base station 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1305, the method may include transmitting, to a user equipment (UE) , a configuration associated with low-power wakeup signal (LP-WUS) monitoring by a low-power receiver of the UE. The operations of 1305 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1305 may be performed by a device as described with reference to FIG. 1A.

At 1310, the method may include determining a monitoring occasion (MO) for LP-WUS, wherein the MO is after a first active time for physical downlink control channel (PDCCH) transmission. The operations of 1310 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1310 may be performed by a device as described with reference to FIG. 1A.

At 1315, the method may include determining whether a second active time for PDCCH transmission is available based on the configuration associated with LP-WUS monitoring, wherein the second active time for PDCCH transmission is associated with the MO or a monitoring window comprising the MO. The operations of 1315 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1315 may be performed by a device as described with reference to FIG. 1A.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the 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 in conjunction with a DSP core, or any other such configuration.

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

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of 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) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) comprising:

a processor; and

a transceiver coupled to the processor, and

wherein the processor is configured to:

perform physical downlink control channel (PDCCH) monitoring in a first active time;

determine a monitoring occasion (MO) for low-power wakeup signal (LP-WUS) ; and

determine whether to trigger a second active time for PDCCH monitoring based on at least one of the following:

a time location of the first active time,

a time location of the MO for LP-WUS,

a time location of a monitoring window comprising the MO for LP-WUS, or

an indication related to LP-WUS monitoring received from a network entity.
The UE of claim 1, wherein a start of the MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the MO is shorter than a duration threshold.
The UE of claim 2, wherein the second active time for PDCCH monitoring associated with the MO is triggered, and wherein the processor is further configured to:

start a timer associated with the MO;

perform PDCCH monitoring in the second active time for PDCCH monitoring; and

end the second active time for PDCCH monitoring at an expiry of the timer or based on an indication of stopping the PDCCH monitoring received from a network entity.
The UE of claim 2, wherein the second active time for PDCCH monitoring associated with the MO is not triggered.
The UE of claim 2, wherein the second active time for PDCCH monitoring associated with the MO is triggered, and wherein the processor is further configured to:

perform PDCCH monitoring in the second active time for PDCCH monitoring;

receive, via the transceiver from a network entity, an indication of stopping the PDCCH monitoring; and

end the second active time for PDCCH monitoring.
The UE of claim 2, wherein the processor is further configured to:

skip the MO, wherein the MO is an invalid MO; and

wherein the second active time for PDCCH monitoring associated with the invalid MO is not triggered.
The UE of claim 1, wherein the UE further comprises a low-power receiver coupled to the processor, and the processor is further configured to:

turn on the low-power receiver before a duration threshold prior to the MO; and

one of the following:

skip the MO, wherein the MO is at least partially overlapped with the first active time for PDCCH monitoring; or

perform LP-WUS monitoring in the MO, wherein the MO is outside the first active time for PDCCH monitoring, and wherein whether to trigger the second active time for PDCCH monitoring associated with the MO is determined based on the LP-WUS monitoring.
The UE of claim 1, wherein the MO is a first MO in the monitoring window, the monitoring window further comprises at least one MO after the first MO, and one of the following:

wherein a start of the first MO is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the first MO is shorter than a duration threshold; or

wherein a start of the monitoring window is after an end of the first active time for PDCCH monitoring, and a time gap between the end of the first active time for PDCCH monitoring and the start of the monitoring window is shorter than a duration threshold.
The UE of claim 8, wherein the processor is further configured to:

perform LP-WUS monitoring in the at least one MO; and

trigger the second active time for PDCCH monitoring associated with the monitoring window, wherein a LP-WUS indicating wake-up is received in the at least one MO.
The UE of claim 8, wherein the processor is further configured to:

perform LP-WUS monitoring in the at least one MO, wherein no LP-WUS indicating wake-up is received in the at least one MO; or

skip the at least one MO.
The UE of claim 10, wherein the second active time for PDCCH monitoring associated with the monitoring window is triggered, and the processor is further configured to:

start a timer associated with the monitoring window;

perform PDCCH monitoring in the second active time for PDCCH monitoring associated with the monitoring window; and

end the second active time for PDCCH monitoring at an expiry of the timer or based on an indication of stopping the PDCCH monitoring received from a network entity.
The UE of claim 10, wherein the second active time for PDCCH monitoring associated with the monitoring window is not triggered.
The UE of claim 1, wherein the UE further comprises a low-power receiver coupled to the processor, and the processor is further configured to:

turn on the low-power receiver before a duration threshold prior to the monitoring window comprising the MO;

perform LP-WUS monitoring in at least one MO in the monitoring window; and

determine, based on the LP-WUS monitoring, whether to trigger the second active time for PDCCH monitoring associated with the monitoring window,

wherein one of the following:

a start of the monitoring window is outside the first active time for PDCCH monitoring, or

the MO is a first MO in the monitoring window, a start of the first MO is outside the first active time for PDCCH monitoring.
The UE of claim 1, wherein the processor is further configured to:

receive, via the transceiver from a network entity, the indication related to LP-WUS monitoring, wherein the indication related to LP-WUS monitoring is indicative of changing the MO for LP-WUS monitoring;

determine a changed MO;

skip the MO; and

perform LP-WUS monitoring in the changed MO.
The UE of claim 14, wherein the indication related to LP-WUS monitoring comprises at least one of the following:

a time domain location of the MO;

a time domain location of the changed MO; or

an indication of the MO, and

wherein a time offset between the MO and the changed MO is comprised in the indication related to LP-WUS monitoring, or is predefined or preconfigured.
A network entity comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

transmit, via the transceiver to a user equipment (UE) , a configuration associated with low-power wakeup signal (LP-WUS) monitoring by a low-power receiver of the UE;

determine a monitoring occasion (MO) for LP-WUS, wherein the MO is after a first active time for physical downlink control channel (PDCCH) transmission; and

determine whether a second active time for PDCCH transmission is available based on the configuration associated with LP-WUS monitoring, wherein the second active time for PDCCH transmission is associated with the MO or a monitoring window comprising the MO.
The network entity of claim 16, wherein the configuration associated with LP-WUS monitoring comprises an indication of a duration threshold for a time gap between the end of the first active time for PDCCH transmission and the start of the monitoring window.
The network entity of claim 17, wherein the processor is further configured to:

receive, via the transceiver from the UE, capability information of the UE; and

determine the duration threshold based on the capability information of the UE,

wherein the capability information comprises at least one of the following:

an indication of whether the UE supports simultaneous operations of a transceiver and the low-power receiver comprised by the UE; or

a time requirement for the low-power receiver of the UE to enter an active time for LP-WUS monitoring.
A method performed by a user equipment (UE) , comprising:

performing physical downlink control channel (PDCCH) monitoring in a first active time;

determining a monitoring occasion (MO) for low-power wakeup signal (LP-WUS) ; and

determining whether to trigger a second active time for PDCCH monitoring based on at least one of the following:

a time location of the first active time,

a time location of the MO for LP-WUS,

a time location of a monitoring window comprising the MO for LP-WUS, or

an indication related to LP-WUS monitoring received from a network entity.
A method performed by a network entity, comprising:

transmitting, to a user equipment (UE) , a configuration associated with low-power wakeup signal (LP-WUS) monitoring by a low-power receiver of the UE;

determining a monitoring occasion (MO) for LP-WUS, wherein the MO is after a first active time for physical downlink control channel (PDCCH) transmission; and

determining whether a second active time for PDCCH transmission is available based on the configuration associated with LP-WUS monitoring, wherein the second active time for PDCCH transmission is associated with the MO or a monitoring window comprising the MO.