WO2025236737A1

WO2025236737A1 - Communication of lp-wus

Info

Publication number: WO2025236737A1
Application number: PCT/CN2025/072131
Authority: WO
Inventors: Jie Hu; Jing HAN; Lianhai WU; Haiming Wang; Luning Liu
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2025-01-13
Filing date: 2025-01-13
Publication date: 2025-11-20
Anticipated expiration: 2027-07-13

Abstract

Various aspects of the present disclosure relate to communication of LP-WUS. In one aspect, a network entity transmits, to a UE, at least one LP-WUS configuration on at least one serving cell in a cell group. In turn, the network entity transmits, to the UE, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration.

Description

COMMUNICATION OF LP-WUS

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to user equipment (UE) , network entities and methods supporting communication 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) ) .

A UE may be equipped with a main radio (MR) and a low power-wake up receiver (LP-WUR, LR) . The MR may comprise or may be a transmission (Tx) /reception (Rx) module operating for new radio (NR) signals/channels apart from signals/channel related to low-power wake-up. The LR may comprise or may be an Rx module operating for receiving/processing signals/channel related to low-power wake-up. The MR of the UE can be in a sleep state while the LR remains active to monitor LP-WUS, and when LP-WUS is received by LR, it will trigger the MR to wake up to monitor Physical Downlink Control Channel (PDCCH) in radio resource control (RRC) -CONNECTED mode. As LR would adopt a minimalistic design, the power consumption of LR is expected to be significantly lower than legacy PDCCH based signaling using the MR in some cases. In this way, LP-WUS in RRC_CONNECTED can potentially further reduce the UE energy consumption by being able to monitor the downlink with an LR such that the MR used for PDCCH monitoring can be kept in a sleep state.

LP-WUS is at least supported for the case where a UE is configured with carrier aggregation (CA) in RRC-CONNECTED mode, and also supported when the UE is configured with new radio (NR) dual-connectivity (DC) in RRC CONNECTED mode. In the case where CA and/or DC is configured, the LP-WUS configuration should consider the impacts on multiple carriers and different cell groups, including how to provide the LP-WUS configuration and corresponding PDCCH monitoring behaviors from UE side.

SUMMARY

The present disclosure relates to UE, network entities and methods that support communication of LP-WUS. With the present disclosure, LP-WUS transmission and reception operation in CA case and/or DC case can be achieved.

Some implementations of a network entity described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to:transmit, via the transceiver to a UE, at least one LP-WUS configuration on at least one serving cell in a cell group; and transmit, via the transceiver to the UE, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration.

In some implementations, the processor is configured to transmit the at least one LP-WUS configuration by: transmitting a first LP-WUS configuration on a first serving cell in the cell group.

In some implementations, the first LP-WUS configuration is associated with both a default discontinuous reception (DRX) group and a secondary DRX group if the secondary DRX group is configured.

In some implementations, the first serving cell is associated with the default DRX group.

In some implementations, the first serving cell is a primary cell (PCell) in the cell group.

In some implementations, the first serving cell is associated with the secondary DRX group.

In some implementations, the first serving cell is an activated secondary cell (SCell) .

In some implementations, the first LP-WUS configuration is deactivated or released along with deactivation or release of the activated SCell.

In some implementations, the first serving cell comprises a deactivated SCell.

In some implementations, the first LP-WUS configuration is activated when the deactivated SCell is activated.

In some implementations, the processor is configured to transmit the at least one LP-WUS configuration by: transmitting a first LP-WUS configuration on a first serving cell in the cell group; and transmitting a second LP-WUS configuration on a second serving cell in the cell group.

In some implementations, the first LP-WUS configuration is associated with a default DRX group, and the second LP-WUS configuration is associated with a secondary DRX group.

In some implementations, the first serving cell is a PCell in the cell group, and the second serving cell comprises an SCell in the cell group.

In some implementations, each of the first serving cell and the second serving cell is an SCell in the cell group.

In some implementations, the processor is configured to transmit the at least one LP-WUS configuration by: transmitting multiple LP-WUS configurations on multiple serving cells in the cell group.

In some implementations, each of the multiple LP-WUS configurations is associated with one of the multiple serving cells, and each of the multiple serving cells is associated with a default DRX group or a secondary DRX group.

In some implementations, the cell group comprises a master cell group (MCG) or a secondary cell group (SCG) if the SCG is configured.

Some implementations of a UE described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver from a network entity, at least one LP-WUS configuration on at least one serving cell in a cell group; receive, via the transceiver from the network entity, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration; and perform physical downlink control channel (PDCCH) monitoring on the at least one serving cell.

In some implementations, the processor is configured to receive the at least one LP-WUS configuration by: receiving a first LP-WUS configuration on a first serving cell in the cell group.

In some implementations, the first serving cell is a PCell in the cell group. In such implementations, the processor is configured to perform PDCCH monitoring by: performing PDCCH monitoring on all activated serving cells in the cell group.

In some implementations, the processor is configured to perform PDCCH monitoring by: performing PDCCH monitoring on the first serving cell; or performing PDCCH monitoring on all activated serving cells in the cell group.

In some implementations, the first serving cell is an activated SCell.

In some implementations, the first serving cell is a deactivated SCell.

In some implementations, the processor is configured to receive the at least one LP-WUS configuration by: receiving a first LP-WUS configuration on a first serving cell in the cell group; and receiving a second LP-WUS configuration on a second serving cell in the cell group. In such implementations, the processor is configured to perform PDCCH monitoring by at least one of the following: performing PDCCH monitoring on the first serving cell based on determining that a first LP-WUS is received on the first serving cell; or performing PDCCH monitoring on the second serving cell based on determining that a second LP-WUS is received on the second serving cell.

In some implementations, the processor is configured to receive the at least one LP-WUS configuration by: receiving a first LP-WUS configuration on a PCell in the cell group; and receiving a second LP-WUS configuration on an SCell in the cell group. In such implementations, the processor is configured to perform PDCCH monitoring by: performing PDCCH monitoring on all activated serving cells in the cell group based on determining that a first LP-WUS is received on the PCell.

In some implementations, the processor is further configured to: receive, via the transceiver from the network entity, information about the at least one serving cell on which PDCCH monitoring is to be performed.

In some implementations, the first LP-WUS configuration is associated with both a default DRX group and a secondary DRX group if the secondary DRX group is configured.

In some implementations, the first serving cell is a PCell in the cell group.

In some implementations, the processor is configured to perform PDCCH monitoring by: performing PDCCH monitoring on all activated serving cells in the cell group based on determining that a first LP-WUS is received on the first serving cell.

In some implementations, the first LP-WUS configuration is associated with the first serving cell, and the first serving cell is associated with a default DRX group or a secondary DRX group if the secondary DRX group is configured.

In some implementations, the processor is configured to receive the at least one LP-WUS configuration by: receiving a first LP-WUS configuration on a first serving cell in the cell group; and receiving a second LP-WUS configuration on a second serving cell in the cell group.

In some implementations, the first LP-WUS configuration is associated with a default DRX group, and the second LP-WUS configuration is associated with a secondary DRX group if the secondary DRX group is configured.

In some implementations, the first serving cell is a PCell in the cell group, and the second serving cell is an SCell in the cell group.

In some implementations, the first LP-WUS configuration is associated with the first serving cell, the second LP-WUS configuration is associated with the second serving cell, and each of the first serving cell and the second serving cell is associated with a default DRX group or a secondary DRX group.

In some implementations, the processor is configured to perform PDCCH monitoring by at least one of the following: performing PDCCH monitoring on all activated serving cells associated with the default DRX group based on determining that a first LP-WUS is received on the first serving cell; or performing PDCCH monitoring on all activated serving cells associated with the secondary DRX group based on determining that a second LP-WUS is received on the second serving cell.

In some implementations, the network entity comprises a master node (MN) , and the cell group comprises a master cell group (MCG) .

In some implementations, the processor is further configured to: receive, via the transceiver from a secondary node (SN) , at least one further LP-WUS configuration on at least one further serving cell in a secondary cell group (SCG) ; receive, via the transceiver from the SN, at least one further LP-WUS on the at least one further serving cell based on the at least one further LP-WUS configuration; and perform PDCCH monitoring on the at least one further serving cell.

Some implementations of a first network entity described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: transmit, via the transceiver to a second network entity, a first message related to a LP-WUS configuration; or receive, via the transceiver from the second network entity, a second message related to the LP-WUS configuration.

In some implementations, the first message comprises a first request for capability of the second network entity, and wherein the capability indicates at least one of the following: whether the second network entity supports an LP-WUS transmission operation, or a type of the LP-WUS configuration supported by the second network entity.

In some implementations, the processor is further configured to: receive a first response via the transceiver from the second network entity, wherein the first response comprises the capability on the support of LP-WUS transmission operation.

In some implementations, the second message comprises capability of the second network entity, and wherein the capability indicates at least one of the following: whether the second network entity supports an LP-WUS transmission operation, or a type of the LP-WUS configuration supported by the second network entity.

In some implementations, the first message comprises a second request indicating at least one of the following: the LP-WUS configuration is to be transmitted from the second network entity to a UE; or a type of the LP-WUS configuration.

In some implementations, the processor is further configured to receive a second response via the transceiver from the second network entity, wherein the second response indicates determination on whether to transmit the LP-WUS configuration to the UE, and the type of the LP-WUS configuration if the second network entity determines to transmit the LP-WUS configuration.

In some implementations, the first message comprises the LP-WUS configuration to be transmitted from the first network entity to a UE.

Some implementations of a second network entity described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver from a first network entity, a first message related to a LP-WUS configuration; or transmit, via the transceiver to the first network entity, a second message related to the LP-WUS configuration.

In some implementations, the processor is further configured to: transmit a first response via the transceiver to the first network entity, wherein the first response comprises the capability on the support of the LP-WUS transmission operation.

In some implementations, the processor is further configured to: determine whether to transmit the LP-WUS configuration to the UE based on the second request; and transmit a second response via the transceiver to the first network entity, wherein the second response indicates the determination on whether to transmit the LP-WUS configuration to the UE, and the type of the LP-WUS configuration if the second network entity determines to transmit the LP-WUS configuration.

In some implementations, the processor is further configured to: determine whether to transmit the LP-WUS configuration to the UE based on the first message; and transmit a third response via the transceiver to the first network entity, wherein the third response indicates whether the LP-WUS configuration is transmitted to the UE.

Some implementations of a method described herein may include: transmitting, to a UE, at least one LP-WUS configuration on at least one serving cell in a cell group; and transmitting, to the UE, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration.

Some implementations of a method described herein may include: receiving, from a network entity, at least one LP-WUS configuration on at least one serving cell in a cell group; receiving, from the network entity, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration; and performing PDCCH monitoring on the at least one serving cell.

Some implementations of a method described herein may include: transmitting, to a second network entity, a first message related to a LP-WUS configuration; or receiving, from the second network entity, a second message related to the LP-WUS configuration.

Some implementations of a method described herein may include: receiving, from a first network entity, a first message related to a LP-WUS configuration; or transmitting, to the first network entity, a second message related to the LP-WUS configuration.

Some implementations of a processor described herein may include at least one memory and a controller coupled with the at least one memory and configured to cause the controller to: receive, via a transceiver from a network entity, at least one LP-WUS configuration on at least one serving cell in a cell group; receive, via the transceiver from the network entity, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration; and perform PDCCH monitoring on the at least one serving cell.

It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 illustrates an example of a wireless communications system that supports communication of LP-WUS in accordance with aspects of the present disclosure;

Figs. 2A and 2B illustrate an example of a wireless communications system that supports communication of LP-WUS in accordance with aspects of the present disclosure, respectively;

Figs. 3, 4 and 5 illustrates a signaling diagram illustrating an example process that supports communication of LP-WUS in accordance with aspects of the present disclosure, respectively;

Fig. 6 illustrates an example of a device that supports communication of LP-WUS in accordance with aspects of the present disclosure;

Fig. 7 illustrates an example of a processor that supports communication of LP-WUS in accordance with aspects of the present disclosure; and

Figs. 8, 9, 10 and 11 illustrate a flowchart of a method that supports communication of LP-WUS in accordance with aspects of the present disclosure.

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.

As described above, a UE may be configured with CA. In this case, there is a need to study how to support the LP-WUS transmission and reception operation.

In addition, a UE may be configured with DC. In this case, there is a need to study how to support the LP-WUS transmission and reception operation.

In view of the above, the present disclosure provides a solution that supports communication of LP-WUS. In this solution, a network entity transmits, to a UE, at least one LP-WUS configuration on at least one serving cell in a cell group. In turn, the network entity transmits, to the UE, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration. With this solution, LP-WUS transmission and reception operation in CA case and/or DC case can be achieved.

Aspects of the present disclosure are described in the context of a wireless communications system.

Fig. 1 illustrates an example of a wireless communications system 100 that supports communication of LP-WUS in accordance with aspects of the present disclosure. The wireless communications system 100 may include one at least one of network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or 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 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 (BS) , a network element, a radio access network (RAN) node, 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. The network entities 102 may be collectively referred to as network entities 102 or individually referred to as a network entity 102. For example, the network entities 102 may comprise a first network entity 102-1 and a second network entity 102-2. Hereinafter, the first network entity 102-1 and the second network entity 102-2 may be collectively referred to as network entities 102 or individually referred to as a network entity 102.

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. 1. 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. 1. 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 radio access network (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.

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.

Fig. 2A illustrates an example of a wireless communications system 200A that supports communication of LP-WUS in accordance with aspects of the present disclosure in accordance with aspects of the present disclosure. The wireless communications system 200A may be considered as an example implementation of the wireless communications system 100.

As shown in Fig. 2A, the wireless communications system 200A may comprise the network entity 102 and the UE 104 in Fig. 1. The UE 104 may be configured with CA, and multiple carriers or multiple serving cells with different frequencies may be configured. For example, a cell group may be configured. The cell group may comprise a primary cell (PCell) and one or more secondary cells (SCells) . For example, the one or more SCells may comprise an SCell #1, an SCell #2, …, an SCell #n. Serving Cells of a MAC entity may be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all Serving Cells belong to that one DRX group (also referred to as a default DRX group) . When two DRX groups are configured, each Serving Cell is uniquely assigned to one of the two groups. The DRX parameters that are separately configured for each DRX group are on-duration and inactivity-timer.

Fig. 2B illustrates an example of a wireless communications system 200B that supports communication of LP-WUS in accordance with aspects of the present disclosure in accordance with aspects of the present disclosure. The wireless communications system 200B may be considered as another example implementation of the wireless communications system 100.

As shown in Fig. 2B, the wireless communications system 200B may comprise the first network entity 102-1, the second network entity 102-2 and the UE 104. The UE 104 may be in dual-connectivity (DC) with the first network entity 102-1 and the second network entity 102-2.

In some implementations, the first network entity 102-1 and the second network entity 102-2 may be collectively implemented as one of the following: a gNB, a base station, a network element, a RAN entity, a base transceiver station, an access point, a NodeB, or an eNB.

Alternatively, in some implementations, each of the first network entity 102-1 and the second network entity 102-2 may be implemented as one of the following: a gNB, a base station, a network element, a RAN entity, a base transceiver station, an access point, a NodeB, or an eNB.

In some implementations, the first network entity 102-1 may be implemented as a master node (MN) , and the second network entity 102-2 may be implemented as a secondary node (SN) . The first network entity 102-1 may provide a master cell group (MCG) and the second network entity 102-2 may provide a secondary cell group (SCG) .

In some implementations, the MCG may comprise a PCell and one or more SCells. For example, the one or more SCells may comprise an SCell #1, an SCell #2, …, an SCell #n, where n is an integer equal to or greater than one.

In some implementations, the SCG may comprise a PCell and one or more SCells. For example, the one or more SCells may comprise an SCell #1, …, an SCell #n-1, …, an SCell #n. The PCell of the SCG also referred to as a primary secondary cell (PSCell) .

Fig. 3 illustrates a signaling diagram illustrating an example process 300 that supports communication of LP-WUS in accordance with aspects of the present disclosure. For the purpose of discussion, the process 300 will be described with reference to Fig. 1. The process 300 may involve the UE 104 and the network entity 102 in Fig. 1.

As shown in Fig. 3, the network entity 102 transmits 310, to the UE 104, at least one LP-WUS configuration on at least one serving cell in a cell group.

In turn, the network entity 102 transmits 320, to the UE 104, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration.

In some implementations, the at least one serving cell supports an LP-WUS transmission operation.

Upon receiving the at least one LP-WUS on the at least one serving cell, the UE 104 performs 330 PDCCH monitoring on the at least one serving cell.

With the process 300, LP-WUS transmission and reception operation in CA case and/or DC case can be achieved.

In some implementations, the LP-WUS is not configured with a second discontinuous reception (DRX) group simultaneously. That is, only a default DRX group is configured for the UE 104. In this case, all serving cells associated with the default DRX group are configured with same DRX parameters. The LP-WUS is configured to be associated with the common Connected-Discontinuous Reception (C-DRX configuration) . The network entity 102 can determine to provide the LP-WUS configuration on one or multiple serving cells in the cell group. In such implementations, one of the following options 1 and 2 will be performed.

In option 1, the network entity 102 may transmit one LP-WUS configuration on one of the serving cells in the cell group. For example, the network entity 102 may transmit a first LP-WUS configuration on a first serving cell in the cell group.

In some implementations of option 1, the first serving cell is a PCell in the cell group. In such implementations, the network entity 102 may transmit the first LP-WUS configuration only on the PCell in the cell group. In such implementations, the first LP-WUS configuration may be provided with a PCell configuration. For example, the first LP-WUS configuration may be included in an information element (IE) of PhysicalCellGroupConfig by RRC signalling. If the UE 104 receives an LP-WUS from the PCell based on the first LP-WUS configuration, the UE 104 may perform PDCCH monitoring on all activated serving cells in the cell group.

Alternatively, in some other implementations of option 1, the first serving cell is an SCell in the cell group. In other words, the network entity 102 may transmit the first LP-WUS configuration on an SCell in the cell group. In such implementations, the first LP-WUS configuration may be included in an associated SCell configuration if the SCell is configured with the LP-WUS. In such implementations, the first LP-WUS configuration may be provided with a SCell configuration. For example, the first LP-WUS configuration may be included in an information element (IE) of ScellConfig by RRC signalling. If the network entity 102 may transmit the first LP-WUS configuration on an SCell in the cell group (i.e., if the SCell is configured with LP-WUS) , there may be the following alternatives.

In a first alternative, only one or more activated SCells can be configured with LP-WUS by the network entity 102. The first LP-WUS configuration is deactivated or released along with the SCell configuration. In the case where the SCell is deactivated or released, the first LP-WUS configuration is also be deactivated or released.

In the first alternative, the network entity 102 may guarantee the SCell with the first LP-WUS configuration will not be deactivated or released, or the UE 104 is not expected to be configured with the LP-WUS from a serving cell which will be deactivated or released.

In a second alternative, one or more deactivated SCells can also be configured with LP-WUS by the network entity 102.

In one option of the second alternative, the first LP-WUS configuration is pre-configured on a deactivated SCell and can be activated when the deactivated SCell is re-activated.

In another option of the second alternative, the deactivated SCell is activated in the case where the LP-WUS is newly configured on the SCell.

In some other implementations of option 1, if the UE 104 receives an LP-WUS from the SCell based on the first LP-WUS configuration, the UE 104 may perform PDCCH monitoring only on the SCell with the first LP-WUS configuration. Alternatively, if the UE 104 receives an LP-WUS from the SCell based on the first LP-WUS configuration, the UE 104 may perform PDCCH monitoring on all activated serving cells in the cell group.

In option 2, the network entity 102 may transmit multiple LP-WUS configurations on multiple serving cells in the cell group to achieve per serving cell PDCCH monitoring control for flexibility and power saving purpose.

In option 2, if the network entity 102 transmits a first LP-WUS configuration on the PCell in the cell group, the first LP-WUS configuration may be included in the PCell configuration. If the network entity 102 transmits a second LP-WUS configuration on an SCell in the cell group, the second LP-WUS configuration may be included in the SCell configuration.

In option 2, if the network entity 102 may transmit the second LP-WUS configuration on the SCell in the cell group (i.e., if the SCell is configured with LP-WUS) , there may be the following alternatives.

In a first alternative, only one or more activated SCells can be configured with LP-WUS by the network entity 102. The second LP-WUS configuration is deactivated or released along with the SCell configuration. In the case where the SCell is deactivated or released, the second LP-WUS configuration is also be deactivated or released.

In the first alternative, the network entity 102 may guarantee the SCell with the second LP-WUS configuration will not be deactivated or released, or the UE 104 is not expected to be configured with the LP-WUS from a serving cell which will be deactivated or released.

In one option of the second alternative, the second LP-WUS configuration is pre-configured on a deactivated SCell and can be activated when the deactivated SCell is re-activated.

In option 2, the network entity 102 may transmit multiple LP-WUS configurations on multiple serving cells, there may be scenarios that the network entity 102 transmits multiple LP-WUS configurations on both PCell and at least one SCell, or only on multiple SCells. Then, how the UE 104 performs PDCCH monitoring based on the multiple LP-WUS configurations should be considered.

In some case, the UE 104 performs PDCCH monitoring based on per serving cell control, and PDCCH monitoring is triggered on a serving cell if LP-WUS is received from the serving cell.

Specifically, in one example, if the network entity 102 transmits the multiple LP-WUS configurations on both PCell and at least one SCell, the UE 104 may perform PDCCH monitoring on PCell when receiving the LP-WUS from the PCell and perform PDCCH monitoring on the at least one SCell when receiving the LP-WUS from the at least one SCell. For example, the UE 104 may perform PDCCH monitoring on a first SCell when receiving the LP-WUS from the first SCell and perform PDCCH monitoring on a second SCell when receiving the LP-WUS from the second SCell.

In another example, if the network entity 102 transmits the multiple LP-WUS configurations only on multiple SCells, the UE 104 may perform PDCCH monitoring on one of the multiple SCells when receiving the LP-WUS from a respective one of the multiple SCells. For example, the network entity 102 transmits an LP-WUS configuration on a first SCell and another LP-WUS configuration on a second SCell. The UE 104 may perform PDCCH monitoring on the first SCell when receiving the LP-WUS from the first SCell and perform PDCCH monitoring on the second SCell when receiving the LP-WUS from the second SCell.

In another case, the UE 104 performs PDCCH monitoring based on PCell control, PDCCH monitoring is triggered on all activated serving cells when the configured LP-WUS from the PCell is received.

Specifically, in one example, if the PCell is configured with LP-WUS, the LP-WUS from the PCell triggers PDCCH monitoring for all activated serving cells in the cell group, regardless of the LP-WUS configuration in SCells. For example, the network entity 102 transmits an LP-WUS configuration on the PCell and another LP-WUS configuration on an SCell. The UE 104 may perform PDCCH monitoring on all activated serving cells in the cell group when receiving the LP-WUS from the PCell.

In another example, if the PCell is not configured with LP-WUS, PDCCH monitoring is triggered on an SCell if LP-WUS is received from the SCell. For example, the network entity 102 transmits an LP-WUS configuration on a first SCell and another LP-WUS configuration on a second SCell. The UE 104 may perform PDCCH monitoring on the first SCell when receiving the LP-WUS from the first SCell and perform PDCCH monitoring on the second SCell when receiving the LP-WUS from the second SCell.

In some implementations, for option 1 and option 2, the network entity 102 may further transmit, to the UE 104, information about the at least one serving cell on which PDCCH monitoring is to be performed.

In some implementations, the information about the at least one serving cell may comprise at least one identity of the at least one serving cell.

In some implementations, the information about the at least one serving cell may be included in the at least one LP-WUS configuration explicitly.

Alternatively, in some implementations, the information about the at least one serving cell may be transmitted with the LP-WUS and carried in the LP-WUS sequence or signal. It requires LP-WUS to carry multi-bits information. For example, the network entity 102 may configure the LP-WUS from an SCell to trigger the PDCCH monitoring for the SCell and the PCell.

Additionally, for option 1 and option 2, the network entity 102 may determine to activate, deactivate or release the LP-WUS configuration on any serving cells.

In some implementations, the network entity 102 may determine to release the LP-WUS configuration for a serving cell by transmitting a release message.

In some implementations, the network entity 102 may determine to activate or deactivate the LP-WUS configuration for one or more serving cells, e.g., stop to perform LP-WUS monitoring.

In some implementations, whether to activate, deactivate, release the LP-WUS configuration is left to implementation of the network entity 102.

In some implementations, the LP-WUS is configured with the second DRX group simultaneously. That is, both the default DRX group and the second DRX group are configured for the UE 104. In such implementations, serving cells of a MAC entity may be configured by RRC in the two DRX groups with separate DRX parameters. The DRX parameters that are separately configured for each of the two DRX groups are on-duration and inactivity timer. Then, the network entity 102 needs to determine how to configure the LP-WUS in one or more serving cells associated with the two DRX groups. In such implementations, one of the following options 3, 4 and 5 will be performed.

In option 3, the network entity 102 may transmit one LP-WUS configuration on one of the serving cells in the cell group. The one LP-WUS configuration is applied for the two DRX groups. For example, the network entity 102 may transmit a first LP-WUS configuration on a first serving cell in the cell group. The first LP-WUS configuration is associated with both the default DRX group and the secondary DRX group. If the UE 104 receives an LP-WUS from the first serving cell based on the first LP-WUS configuration, the UE 104 may perform PDCCH monitoring on all activated serving cells in the cell group.

In some implementations of option 3, the first serving cell is a PCell in the cell group. In such implementations, the network entity 102 may transmit the first LP-WUS configuration only on the PCell in the cell group. The PCell is associated with the default DRX group. In such implementations, the first LP-WUS configuration may be provided with a PCell configuration. For example, the first LP-WUS configuration may be included in an IE of PhysicalCellGroupConfig by RRC signalling. If the UE 104 receives an LP-WUS from the PCell based on the first LP-WUS configuration, the UE 104 may perform PDCCH monitoring on all activated serving cells in the cell group.

Alternatively, in some other implementations of option 3, the first serving cell is an SCell in the cell group. In other words, the network entity 102 may transmit the first LP-WUS configuration on an SCell in the cell group. The SCell is associated with the default DRX group.

Alternatively, in still other implementations of option 3, the network entity 102 may transmit the first LP-WUS configuration on the first serving cell in the cell group. The first serving cell is associated with the default DRX group or the secondary DRX group. If the first serving cell is the PCell in the cell group, the first LP-WUS configuration may be provided with a PCell configuration. For example, the first LP-WUS configuration may be included in an IE of PhysicalCellGroupConfig by RRC signalling. If the first serving cell is an SCell in the cell group, the first LP-WUS configuration may be provided with an SCell configuration.

In still other implementations of option 3, if the network entity 102 may transmit the first LP-WUS configuration on the SCell in the cell group and the SCell is associated with the default DRX group or the secondary DRX group, there may be the following alternatives.

In option 4, LP-WUS configuration is configured for each DRX group. For example, the network entity 102 may transmit a first LP-WUS configuration on a first serving cell in the cell group and transmit a second LP-WUS configuration on a second serving cell in the cell group. The first LP-WUS configuration is associated with the default DRX group, and the second LP-WUS configuration is associated with the secondary DRX group.

In some implementations of option 4, the first serving cell is the PCell in the cell group, and the second serving cell is an SCell in the cell group. In such implementations, if the network entity 102 transmits the second LP-WUS configuration on the SCell and the second LP-WUS configuration is associated with the secondary DRX group, there may be the following alternatives.

In option 4, if the UE 104 receives an LP-WUS from the first serving cell based on the first LP-WUS configuration associated with the default DRX group, the UE 104 may perform PDCCH monitoring on the first serving cell. If the UE 104 receives an LP-WUS from the second serving cell based on the second LP-WUS configuration associated with the secondary DRX group, the UE 104 may perform PDCCH monitoring on the second serving cell.

In option 5, the LP-WUS is configured per serving cell, i.e., multiple LP-WUS configurations may be configured within each of the two DRX groups. In other words, the network entity 102 may transmit multiple LP-WUS configurations on multiple serving cells in the cell group. Each of the multiple LP-WUS configurations is associated with one of the multiple serving cells, and each of the multiple serving cells is associated with the default DRX group or the secondary DRX group. There may be scenarios that both PCell and at least one SCell are configured with LP-WUS in a DRX group, or only multiple SCells are configured with LP-WUS in the DRX group. Then, the solutions as described in option 2 may be reused for each of the two DRX groups. Details of the solutions are omitted for brevity.

In option 5, if the UE 104 receives an LP-WUS from a serving cell associated with the default DRX group or the secondary DRX group based on an LP-WUS configuration, the UE 104 may perform PDCCH monitoring on the serving cell.

As described with reference to Fig. 2B, the UE 104 may be in dual-connectivity with the first network entity 102-1 and the second network entity 102-2. The first network entity 102-1 may be implemented as an MN, and the second network entity 102-2 may be implemented as an SN. The first network entity 102-1 may provide an MCG and the second network entity 102-2 may provide an SCG.

In some implementations, for each of the MCG and SCG, one or multiple carriers may also be supported. Then, how the LP-WUS operation is configured and applied for the NR-DC case should be considered.

In some implementations, the LP-WUS configuration may be configured per cell group, i.e., the LP-WUS may be configured for the MCG and SCG separately.

For example, the UE 104 may receive, from the MN, at least one LP-WUS configuration on at least one serving cell in the MCG. The UE 104 may receive, from the MN, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration. In turn, the UE 104 may perform PDCCH monitoring on the at least one serving cell in the MCG. In addition, the UE 104 may receive, from the SN, at least one further LP-WUS configuration on at least one further serving cell in the SCG. The UE 104 may receive, from the SN, at least one further LP-WUS on the at least one further serving cell based on the at least one further LP-WUS configuration. In turn, the UE 104 may perform PDCCH monitoring on the at least one further serving cell in the SCG.

In some implementations, for each of the MCG and SCG, there may be different options for the LP-WUS configuration. The above options 1 to 5 on LP-WUS configuration and PDCCH monitoring can be applied to MCG and SCG separately.

In some implementations, there may be Option 1-1 and Option 1-2 for LP-WUS configuration in RRC-CONNECTED mode.

In Option 1-1, the UE 104 may perform LP-WUS monitoring according to the LP-WUS monitoring configuration before drx-onDurationTimer to trigger the starting of the drx-onDurationTimer.

In Option 1-1, the UE 104 is configured with legacy C-DRX configurations. For periodic CSI/L1-RSRP reporting, the UE 104 can be configured with one of the following:
● Periodic channel state information (CSI) /L1-reference signal received
power (RSRP) is not reported during the time given by the configured drx-onDurationTimer if the UE 104 is not indicated to wake-up
● Periodic CSI/L1-RSRP is periodically reported during the time given by
the configured drx-onDurationTimer regardless if the UE 104 is indicated to wake-up or not.

In Option 1-2, the UE 104 may perform LP-WUS monitoring outside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.

In Option 1-2, the UE 104 is configured with legacy C-DRX configurations. The UE 104 is expected to be configured with LP-WUS monitoring configuration (periodicity and offset can be different from those from C-DRX configuration) . LP-WUS triggers the start of a timer during which the UE 104 monitors PDCCH. For periodic CSI/L1-RSRP reporting, the UE 104 can be configured with one of the following:
● Periodic CSI/L1-RSRP is not reported if the UE 104 is not indicated to
wake-up
● Periodic CSI/L1-RSRP is periodically reported regardless of if the UE
104 is indicated to wake-up or not.

In Option 1-2, PDCCH monitoring is not triggered by legacy C-DRX cycle and drx-onDurationTimer when monitoring LP-WUS.

In some implementations, LP-WUS configuration on Option 1-1 and Option 1-2 for RRC-CONNECTED mode cannot be configured simultaneously for the same UE. Then, for the UE 104 configured with NR-DC, the cross-node coordination between the MN and the SN on LP-WUS configuration is needed to align the support of LP-WUS operation and specific LP-WUS configurations. This will be described with reference to Fig. 4.

Fig. 4 illustrates a signaling diagram illustrating an example process 400 that supports communication of LP-WUS in accordance with aspects of the present disclosure. For the purpose of discussion, the process 400 will be described with reference to Fig. 1. The process 400 may involve the first network entity 102-1 and the second network entity 102-2 in Fig. 1.

Generally, in the process 400, the UE 104 is in dual-connectivity with the first network entity 102-1 and the second network entity 102-2. The first network entity 102-1 may be implemented as an MN, and the second network entity 102-2 may be implemented as an SN.

As shown in Fig. 4, the first network entity 102-1 transmits 410, to the second network entity 102-2, a first message related to an LP-WUS configuration.

In some implementations, the first network entity 102-1 may consider whether the second network entity 102-2 supports the LP-WUS transmission operation or not, the first network entity 102-1 may give priority to the nodes which support LP-WUS transmission operation as the SN during the SN addition/SN change procedures. Hereinafter, a node (such as SN) supporting LP-WUS transmission operation is also referred to as a node with LP-WUS capability.

In some implementations, the first network entity 102-1 may request the second network entity 102-2 to provide the capability on the support of LP-WUS transmission operation by transmitting the first message. In such implementations, the first message may comprise a first request for capability of the second network entity 102-2, and the capability indicates whether the second network entity 102-2 supports an LP-WUS transmission operation. For example, the first network entity 102-1 may transmits the first message during the SN addition procedure, e.g., by SN Addition Request message from the first network entity 102-1 to the second network entity 102-2.

Alternatively or additionally, the first network entity 102-1 may request the second network entity 102-2 to provide a type of the LP-WUS configuration supported by the second network entity 102-2 by transmitting the first message. In such implementations, the first message may comprise a first request for capability of the second network entity 102-2, and the capability indicates the type of the LP-WUS configuration supported by the second network entity 102-2.

In some implementations, the type of the LP-WUS configuration may comprise a first type of the LP-WUS configuration related to Option 1-1 as described above. In the first type of the LP-WUS configuration, the UE 104 may perform LP-WUS monitoring according to the LP-WUS monitoring configuration before drx-onDurationTimer to trigger the starting of the drx-onDurationTimer.

Alternatively, in some implementations, the type of the LP-WUS configuration may comprise a second type of the LP-WUS configuration related to Option 1-2 as described above. In the second type of the LP-WUS configuration, the UE 104 may perform LP-WUS monitoring outside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.

In some implementations, the first network entity 102-1 may change a source SN which does not support LP-WUS transmission operation to a target SN which supports LP-WUS transmission operation, and the first network entity 102-1 may request the target SN to provide the capability on the support of LP-WUS transmission operation by transmitting the first message to the target SN. In such implementations, the second network entity 102-2 may act as the target SN. For example, the first network entity 102-1 may transmit the first message to the second network entity 102-2 during the SN change procedure, e.g., by SN Addition request message from the first network entity 102-1 (MN) to the second network entity 102-2 (target SN) .

In some implementations, the second network entity 102-2 may transmit 420 a first response to the first network entity 102-1. The first response comprises the capability on the support of LP-WUS transmission operation. For example, the second network entity 102-2 may transmit the first response by transmitting an SN Addition Request Acknowledge message during SN Addition procedure, or by transmitting an SN Addition Request Acknowledge message from a target SN to the MN during SN change procedure.

In some implementations, the first network entity 102-1 may request the second network entity 102-2 supporting LP-WUS transmission operation or with LP-WUS capability to provide an LP-WUS configuration to align the configuration between the first network entity 102-1 and the second network entity 102-2 in RRC_CONNECTED mode during the SN addition/modification/change procedure.

In one example, in the case where the first network entity 102-1 initiates the SN addition procedure, the first network entity 102-1 may request the second network entity 102-2 to configure the LP-WUS. In this example, the first message may comprise a second request indicating that the LP-WUS configuration is to be transmitted from the second network entity 102-2 to the UE 104. The first network entity 102-1 may further request the specific LP-WUS configuration if configured. In this example, the second request may further indicate a type of the LP-WUS configuration to be transmitted from the second network entity 102-2 to the UE 104. The type of the LP-WUS configuration may be the first type or the second type as described above. For example, the first network entity 102-1 may transmit the first message during the SN addition procedure, e.g., by the SN Addition Request message from the first network entity 102-1 to the second network entity 102-2.

Upon receiving the second request, the second network entity 102-2 may determine whether to transmit the LP-WUS configuration to the UE 104 based on the second request. Then, the second network entity 102-2 may transmit a second response to the first network entity 102-1. The second response indicates the determination on whether to transmit the LP-WUS configuration to the UE 104, and the type of the LP-WUS configuration if the second network entity 102-2 determines to transmit the LP-WUS configuration. For example, the second network entity 102-2 may transmit the second response by an SN Addition Request Acknowledge message during the SN Addition procedure.

In another example, in the case where current SN has not been configured with LP-WUS or the configured LP-WUS is not aligned with the LP-WUS configuration with the first network entity 102-1, e.g., the first network entity 102-1 is configured with the first type of LP-WUS configuration while the second network entity 102-2 is configured with the second type of LP-WUS configuration for RRC-CONNECTED mode, the first network entity 102-1 may request the second network entity 102-2 to modify the LP-WUS configuration. In this example, the first message may comprise a request for modifying or updating the LP-WUS configuration. For example, the first network entity 102-1 may transmit the first message during the SN modification procedure, e.g., by an SN Modification Request message from the first network entity 102-1 to the second network entity 102-2.

Upon receiving the first message, the second network entity 102-2 may determine whether to modify or update the LP-WUS configuration e.g., from the second type to the first type. In other words, the second network entity 102-2 may determine whether to transmit the LP-WUS configuration to the UE 104. Then, the second network entity 102-2 may transmit a second response to the first network entity 102-1. The second response indicates the determination on whether to transmit the LP-WUS configuration to the UE 104, and the type of the LP-WUS configuration if the second network entity 102-2 determines to transmit the LP-WUS configuration. For example, the second network entity 102-2 may transmit the second response by an SN Modification Request Acknowledge message during SN Modification procedure.

In a further example, in the case where current SN has not been configured with LP-WUS or the configured LP-WUS is not aligned with the LP-WUS configuration with the first network entity 102-1, the first network entity 102-1 may determine to change to a new SN which is configured with LP-WUS and/or the configured LP-WUS is aligned with the first network entity 102-1, and also release the source SN without LP-WUS configuration. The first network entity 102-1 may request the target SN (i.e., the second network entity 102-2) to configure the LP-WUS if supported, and further request the specific LP-WUS configuration if configured. In this example, the first message may comprise a second request indicating a type of the LP-WUS configuration to be transmitted from the second network entity 102-2 to the UE 104. The type of the LP-WUS configuration may be the first type or the second type as described above. For example, the first network entity 102-1 may transmit the first message during the SN change procedure e.g., by an SN Addition request message from the first network entity 102-1 to the second network entity 102-2.

Upon receiving the first message, the target SN (i.e., the second network entity 102-2) may determine whether to transmit an LP-WUS configuration to the UE 104 and a specific LP-WUS configuration to be transmitted. Then, the second network entity 102-2 may transmit a second response to the first network entity 102-1. The second response indicates the determination on whether to transmit the LP-WUS configuration to the UE 104, and the type of the LP-WUS configuration if the second network entity 102-2 determines to transmit the LP-WUS configuration. For example, the second network entity 102-2 may transmit the second response by an SN Addition Request Acknowledge message during the SN Change procedure.

In some implementations, the first network entity 102-1 may just indicate the LP-WUS configuration (e.g., the first type or the second type of LP-WUS configuration for RRC-CONNECTED mode) if configured. In such implementations, the first message may comprise the LP-WUS configuration to be transmitted from the second network entity 102-2 to the UE 104. For example, the first network entity 102-1 may transmit the first message by the SN addition/SN change procedure without explicit request.

Upon receiving the first message, the second network entity 102-2 may determine whether to configure LP-WUS and what type of LP-WUS configuration is configured by itself. In other words, the second network entity 102-2 may determine whether to transmit the LP-WUS configuration to the UE 104 and the type of the LP-WUS configuration to be transmitted. Then, the second network entity 102-2 may transmit a third response to the first network entity 102-1. The third response indicates whether the LP-WUS configuration is transmitted to the UE 104.

In some implementations, the second network entity 102-2 may indicate to the first network entity 102-1 if it is configured with LP-WUS and/or specific LP-WUS configuration unsolicited. Which means whenever SCG is configured with LP-WUS but MCG is not configured with LP-WUS, the second network entity 102-2 may indicate the LP-WUS configuration to the first network entity 102-1. This will be described with reference to Fig. 5.

Fig. 5 illustrates a signaling diagram illustrating an example process 500 that supports communication of LP-WUS in accordance with aspects of the present disclosure. For the purpose of discussion, the process 500 will be described with reference to Fig. 1. The process 500 may involve the first network entity 102-1 and the second network entity 102-2 in Fig. 1.

Generally, in the process 500, the UE 104 is in dual-connectivity with the first network entity 102-1 and the second network entity 102-2. The first network entity 102-1 may be implemented as an MN, and the second network entity 102-2 may be implemented as an SN.

As shown in Fig. 5, the second network entity 102-2 transmits 510, to the first network entity 102-1, a second message related to the LP-WUS configuration.

In some implementations, the second message comprises capability of the second network entity 102-2. The capability indicates at least one of the following: whether the second network entity 102-2 supports an LP-WUS transmission operation, or a type of the LP-WUS configuration supported by the second network entity 102-2.

For example, the second network entity 102-2 may transmit the second message to the first network entity 102-1 during the SN addition/SN change procedures.

Fig. 6 illustrates an example of a device 600 that supports paging monitoring triggered by LP-WUS in accordance with aspects of the present disclosure. The device 600 may be an example of a network entity 102 or a UE 104 as described herein. The device 600 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 600 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 602, a memory 604, a transceiver 606, and, optionally, an I/O controller 608. 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 602, the memory 604, the transceiver 606, 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 602, the memory 604, the transceiver 606, 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 602, the memory 604, the transceiver 606, 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 602 and the memory 604 coupled with the processor 602 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604) .

For example, the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 602 may be configured to operable to support a means for performing the following: transmitting, to a UE, at least one LP-WUS configuration on at least one serving cell in a cell group; and transmitting, to the UE, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration.

Alternatively, the processor 602 may be configured to operable to support a means for performing the following: receiving, from a network entity, at least one LP-WUS configuration on at least one serving cell in a cell group; receiving, from the network entity, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration; and performing PDCCH monitoring on the at least one serving cell.

Alternatively, the processor 602 may be configured to operable to support a means for performing the following: transmitting, to a second network entity, a first message related to a LP-WUS configuration; or receiving, from the second network entity, a second message related to the LP-WUS configuration.

Alternatively, the processor 602 may be configured to operable to support a means for performing the following: receiving, from a first network entity, a first message related to a LP-WUS configuration; or transmitting, to the first network entity, a second message related to the LP-WUS configuration.

The processor 602 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 602 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 602. The processor 602 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 604) to cause the device 600 to perform various functions of the present disclosure.

The memory 604 may include random access memory (RAM) and read-only memory (ROM) . The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602 cause the device 600 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 602 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 604 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 608 may manage input and output signals for the device 600. The I/O controller 608 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 608 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 608 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 608 may be implemented as part of a processor, such as the processor 606. In some implementations, a user may interact with the device 600 via the I/O controller 608 or via hardware components controlled by the I/O controller 608.

In some implementations, the device 600 may include a single antenna 610. However, in some other implementations, the device 600 may have more than one antenna 610 (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 606 may communicate bi-directionally, via the one or more antennas 610, wired, or wireless links as described herein. For example, the transceiver 606 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 606 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 610 for transmission, and to demodulate packets received from the one or more antennas 610. The transceiver 606 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 610 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 610 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. 7 illustrates an example of a processor 700 that supports paging monitoring triggered by LP-WUS in accordance with aspects of the present disclosure. The processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein. The processor 700 may optionally include at least one memory 704, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 706. 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 700 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 700) 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 702 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 700 to cause the processor 700 to support various operations in accordance with examples as described herein. For example, the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

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

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

The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 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 702 and/or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions. For example, the processor 700 and/or the controller 702 may be coupled with or to the memory 704, the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein. In some examples, the processor 700 may include multiple processors and the memory 704 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 706 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 706 may reside within or on a processor chipset (e.g., the processor 700) . In some other implementations, the one or more ALUs 706 may reside external to the processor chipset (e.g., the processor 700) . One or more ALUs 706 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 706 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 706 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 706 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 706 to handle conditional operations, comparisons, and bitwise operations.

The processor 700 may be configured to operable to support a means for performing the following: transmitting, to a UE, at least one LP-WUS configuration on at least one serving cell in a cell group; and transmitting, to the UE, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration.

Alternatively, the processor 700 may be configured to operable to support a means for performing the following: receiving, from a network entity, at least one LP-WUS configuration on at least one serving cell in a cell group; receiving, from the network entity, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration; and performing PDCCH monitoring on the at least one serving cell.

Alternatively, the processor 700 may be configured to operable to support a means for performing the following: transmitting, to a second network entity, a first message related to a LP-WUS configuration; or receiving, from the second network entity, a second message related to the LP-WUS configuration.

Alternatively, the processor 700 may be configured to operable to support a means for performing the following: receiving, from a first network entity, a first message related to a LP-WUS configuration; or transmitting, to the first network entity, a second message related to the LP-WUS configuration.

Fig. 8 illustrates a flowchart of a method 800 that supports communication of LP-WUS in accordance with aspects of the present disclosure. The operations of the method 800 may be implemented by a device or its components as described herein. For example, the operations of the method 800 may be performed by the network entity 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 810, the method may include transmitting, to a UE, at least one LP-WUS configuration on at least one serving cell in a cell group. The operations of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a device as described with reference to Fig. 1, 2A or 2B.

At 820, the method may include transmitting, to the UE, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration. The operations of 820 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 820 may be performed by a device as described with reference to Fig. 1, 2A or 2B.

Fig. 9 illustrates a flowchart of a method 900 that supports communication of LP-WUS in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a device or its components as described herein. For example, the operations of the method 900 may be performed by the 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 910, the method may include receiving, from a network entity, at least one LP-WUS configuration on at least one serving cell in a cell group. The operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a device as described with reference to Fig. 1, 2A or 2B.

At 920, the method may include receiving, from the network entity, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration. The operations of 920 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 920 may be performed by a device as described with reference to Fig. 1, 2A or 2B.

At 930, the method may include performing PDCCH monitoring on the at least one serving cell. The operations of 930 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 930 may be performed by a device as described with reference to Fig. 1, 2A or 2B.

Fig. 10 illustrates a flowchart of a method 1000 that supports communication of LP-WUS in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a device or its components as described herein. For example, the operations of the method 1000 may be performed by the network entity 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 1010, the method may include transmitting, to a second network entity, a first message related to a LP-WUS configuration; or receiving, from the second network entity, a second message related to the LP-WUS configuration. The operations of 1010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by a device as described with reference to Fig. 1, 2A or 2B.

Fig. 11 illustrates a flowchart of a method 1100 that supports communication of LP-WUS in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by the network entity 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 1110, the method may include receiving, from a first network entity, a first message related to a LP-WUS configuration; or transmitting, to the first network entity, a second message related to the LP-WUS configuration. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to Fig. 1, 2A or 2B.

It shall be noted that implementations of the present disclosure which have been described with reference to Figs. 1 to 5 are also applicable to the device 600, the processor 700 as well as the methods 800, 900, 1000 and 1100.

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 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) , at least one low power-wake up signal (LP-WUS) configuration on at least one serving cell in a cell group; and

transmit, via the transceiver to the UE, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration.
The network entity of claim 1, wherein the processor is configured to transmit the at least one LP-WUS configuration by:

transmitting a first LP-WUS configuration on a first serving cell in the cell group.
The network entity of claim 2, wherein the first LP-WUS configuration is associated with both a default discontinuous reception (DRX) group and a secondary DRX group if the secondary DRX group is configured.
The network entity of claim 3, wherein the first serving cell is associated with the default DRX group.
The network entity of claim 2 or 4, wherein the first serving cell is a primary cell (PCell) in the cell group.
The network entity of claim 3, wherein the first serving cell is associated with the secondary DRX group.
The network entity of claim 1, wherein the processor is configured to transmit the at least one LP-WUS configuration by:

transmitting a first LP-WUS configuration on a first serving cell in the cell group; and

transmitting a second LP-WUS configuration on a second serving cell in the cell group.
The network entity of claim 7, wherein the first LP-WUS configuration is associated with a default discontinuous reception (DRX) group, and the second LP-WUS configuration is associated with a secondary DRX group.
The network entity of claim 8, wherein the first serving cell is a primary cell (PCell) in the cell group, and the second serving cell is a secondary cell (SCell) in the cell group.
The network entity of claim 8, wherein each of the first serving cell and the second serving cell is a secondary cell (SCell) in the cell group.
The network entity of claim 1, wherein the processor is configured to transmit the at least one LP-WUS configuration by:

transmitting multiple LP-WUS configurations on multiple serving cells in the cell group, wherein each of the multiple LP-WUS configurations is associated with one of the multiple serving cells, and each of the multiple serving cells is associated with a default discontinuous reception (DRX) group or a secondary DRX group.
A user equipment (UE) , comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

receive, via the transceiver from a network entity, at least one low power-wake up signal (LP-WUS) configuration on at least one serving cell in a cell group;

receive, via the transceiver from the network entity, at least one LP-WUS on the at least one serving cell based on the at least one LP-WUS configuration; and

perform physical downlink control channel (PDCCH) monitoring on the at least one serving cell.
The UE of claim 12, wherein the processor is configured to receive the at least one LP-WUS configuration by:

receiving a first LP-WUS configuration on a first serving cell in the cell group.
The UE of claim 13, wherein the processor is configured to perform PDCCH monitoring by:

performing PDCCH monitoring on the first serving cell; or

performing PDCCH monitoring on all activated serving cells in the cell group.
The UE of claim 12, wherein the processor is configured to receive the at least one LP-WUS configuration by:

receiving a first LP-WUS configuration on a first serving cell in the cell group; and

receiving a second LP-WUS configuration on a second serving cell in the cell group; and

wherein the processor is configured to perform PDCCH monitoring by at least one of the following:

performing PDCCH monitoring on the first serving cell based on determining that a first LP-WUS is received on the first serving cell; or

performing PDCCH monitoring on the second serving cell based on determining that a second LP-WUS is received on the second serving cell.
The UE of claim 12, wherein the processor is configured to receive the at least one LP-WUS configuration by:

receiving a first LP-WUS configuration on a primary cell (PCell) in the cell group; and

receiving a second LP-WUS configuration on a secondary cell (SCell) in the cell group; and

wherein the processor is configured to perform PDCCH monitoring by:

performing PDCCH monitoring on all activated serving cells in the cell group based on determining that a first LP-WUS is received on the PCell.
The UE of claim 12, wherein the processor is further configured to:

receive, via the transceiver from the network entity, information about the at least one serving cell on which PDCCH monitoring is to be performed.
The UE of claim 12, wherein the network entity comprises a master node (MN) , and the cell group comprises a master cell group (MCG) .
A first network entity, comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

transmit, via the transceiver to a second network entity, a first message related to a low power-wake up signal (LP-WUS) configuration; or

receive, via the transceiver from the second network entity, a second message related to the LP-WUS configuration.
A second network entity, comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

receive, via the transceiver from a first network entity, a first message related to a low power-wake up signal (LP-WUS) configuration; or

transmit, via the transceiver to the first network entity, a second message related to the LP-WUS configuration.