LP-WUS in multiple carrier configuration

Abstract

According to some embodiments, a method is performed by a user equipment (UE) for monitoring a wake-up signal (WUS). The method comprises: monitoring for a WUS on a first carrier; obtaining an indication to monitor for a WUS on a second carrier; and monitoring for a WUS on the second carrier.

Description

LP-WUS in Multiple Carrier ConfigurationTECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to low power wake up signal (LP-WUS) in multiple carrier configuration.BACKGROUND

[0001] Wake-up receiver (WUR), sometimes also referred to as “wake-up radio,” enables a low power receiver in a user equipment (UE), upon detection of a wake-up signal (WUS), to wake up the main (baseband / radio frequency (RF) / less power efficient) receiver to detect an incoming message, typically paging (e.g., physical downlink control channel (PDCCH) in paging occasions (POs), scheduling the paging message on physical downlink shared channel (PDSCH)). A benefit of employing WUR is lowering energy consumption and longer device battery life, or at a fixed energy consumption the downlink latency may be reduced (shorter discontinuous reception (DRX) / duty-cycles and more frequent checks for incoming transmissions).

[0002] Figure 1 is timing diagram illustrating the location of a WUS and the paging occasion to which it is associated. The horizontal axis represents time. The illustrated example includes three occurrences of wake-up signal 10, each followed by associated paging occasion 12.

[0003] In general, there are two approaches for detecting WUS. A first approach uses the main receiver. In this approach, there is no need for additional dedicated hardware / receiver for monitoring WUS. Coverage of the main receiver is not typically impacted, and there is limited power saving gain because the main receiver monitors WUS.

[0004] A second approach uses a dedicated receiver (WUR). This approach is extremely low power, simple and uses a low-cost receiver architecture, relaxed requirements, and a noisier (i.e., less accurate) clock or oscillator. This approach includes significant power saving gains by maximizing the time in which the main receiver can be in the sleep mode. This approach enables zero energy / battery-less devices, and energy harvesting operations. There are coverage considerations given the tradeoff between WUR power consumption and sensitivity.

[0005] As an example, Figure 2 illustrates dedicated wake-up radio (WUR) 20 used for monitoring wake-up signal (WUS) 22. The illustrated example may apply to narrowband Intemet-of-things (NB-IoT) and Long-Term Evolution (LTE) for machine type communication (LTE-M). Once WUR 20 detects the intended WUS 11, WUR 20 wakes up main (baseband / RF / less power efficient) receiver 24 to detect further incoming messages 26.

[0006] Therefore, the main receiver can go to sleep mode and save power until the main receiver is triggered by WUR. Here, the WUR is an ultra-low power and low-complexity receiver that supports simple modulation schemes, such as on-off keying (OOK), frequency-shift keying (FSK), or phase-shift keying (PSK). However, the WUS is transmitted using an orthogonal frequency division multiplexing (OFDM)-based transmitter.

[0007] Third Generation Partnership Project (3GPP) Release 15 specified WUS for NB-IoT and LTE-M. The main motivation was UE energy consumption reduction, because with coverage enhancement a PDCCH may be repeated many times and the WUS is relatively much shorter and thus requires less reception time for the UE. The logic is that a UE checks for a WUS a certain time before its PO, and only if a WUS is detected then the UE continues to check for PDCCH in the PO, and if not, which is most of the time, the UE goes back to a sleep state to conserve energy. Due to the coverage enhancements the WUS can be of variable length depending on the UE’s coverage. An example is illustrated in Figure 3.

[0008] Figure 3 illustrates WUS for NB-IoT and LTE-M.

[0009] A WUS is based on the transmission of a short signal that indicates to the UE that the UE should continue to decode the downlink control channel, e.g. full NPDCCH for NB-IoT. If such signal is absent (DTX i.e. UE does not detect it), then the UE can go back to sleep without decoding the downlink control channel. The decoding time for a WUS is considerably shorter than that of the full NPDCCH because the WUS essentially only needs to contain one bit of information whereas the NPDCCH may contain up to 35 bits of information. This, in turn, reduces UE power consumption and leads to longer UE battery life. The WUS is transmitted only when there is paging for the UE. If there is no paging for the UE, then the WUS will not be transmitted (i.e., implying a discontinuous transmission, DTX) and the UE goes back to deep sleep, e.g. upon detecting DTX instead of WUS. This is illustrated in Figure 1 where white blocks indicate possible WUS and PO positions whereas the black boxes indicate actual WUS and PO positions.

[0010] The specification of Release 15 WUS is spread out over several parts of the LTE 36-series standard, e.g., 36.211, 36.213, 36.304 and 36.331.

[0011] Release 18 includes WUR for New Radio (NR), with a goal for achieving more significant energy efficiency improvement compared to solutions already specified in earlier releases.

[0012] Fifth generation (5G) systems are designed and developed targeting for both mobile telephony and vertical use cases. Besides latency, reliability, and availability, UE energy efficiency is also critical to 5G. Currently, 5G devices may have to be recharged per week or day, depending on individual’s usage time. In general, 5G devices consume tens of milliwatts in Radio ResourceControl (RRC) idle / inactive state and hundreds of milliwatts in RRC connected state. Designs to prolong battery life is a necessity for improving energy efficiency as well as for better user experience.

[0013] Energy efficiency is even more critical for UEs without a continuous energy source, e.g., UEs using small rechargeable and single coin cell batteries. Among vertical use cases, sensors and actuators are deployed extensively for monitoring, measuring, charging, etc. Generally, their batteries are not rechargeable and expected to last at least few years as described in TR 38.875. Wearables include smart watches, rings, eHealth related devices, and medical monitoring devices. With typical battery capacity, it is challenging to sustain up to 1-2 weeks as required.

[0014] The power consumption depends on the configured length of wake-up periods, e.g., paging cycle. To meet the battery life requirements above, eDRX cycle with large value is expected to be used, resulting in high latency, which is not suitable for such services with requirements of both long battery life and low latency. For example, in a fire detection and extinguishment use case, fire shutters shall be closed, and fire sprinklers shall be turned on by the actuators within 1 to 2 seconds from the time the fire is detected by sensors. A long eDRX cycle cannot meet the delay requirements. Thus, eDRX is not suitable for latency-critical use cases. The intention is to study ultra-low power mechanisms that can support low latency in Release 18, e.g. lower than eDRX latency.

[0015] Currently, UEs need to periodically wake up once per DRX cycle, which dominates the power consumption in periods with no signalling or data traffic. If UEs are able to wake up only when they are triggered, e.g., paging, power consumption could be dramatically reduced. This can be achieved by using a wake-up signal to trigger the main radio and a separate receiver which has the ability to monitor wake-up signal with ultra-low power consumption. The main radio works for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on.

[0016] The power consumption for monitoring wake-up signal depends on the wake-up signal design and the hardware module of the wake-up receiver used for signal detecting and processing.

[0017] The Release 18 study item on “low-power wake-up signal and receiver for NR” is completed and the technical report is provided in: TR 38.869, V0.4.0, “Study on low-power Wakeup Signal and Receiver for NR”. While the scope of Release 19 Work Item is still under discussion, it is likely that the following proposal will be considered regarding the signal design.

[0018] When a UE is configured with carrier aggregation (CA) without dual discontinuous reception (DRX) groups in RRC CONNECTED mode, LP-WUS can be configured on a servingcell and / or LP-WUS indication is applicable to all serving cells. There is no impact to PDCCH monitoring behavior related to SCell dormancy / activation / deactivation.

[0019] When a UE is configured with NR dual connectivity (NR-DC) with CA without dual DRX groups or without CA in RRC CONNECTED mode, LP-WUS can be configured on a serving cell per cell-group. This does not imply that LP-WUS has to be configured on both cell groups. LP-WUS indication is applicable to all serving cells in the cell-group. There is no impact to PDCCH monitoring behaviour related to SCell dormancy / activation / deactivation.

[0020] There currently exist certain challenges. For example, while 3GPP is actively working on LP-WUS standardization in 3GPP Release 19, detailed agreements or specifications for multiple-carrier operation are still under discussion.SUMMARY

[0021] As described above, certain challenges currently exist with low power wake up signal (LP-WUS) in multiple carrier configuration. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments configure and manage LP-WUS monitoring by a user equipment (UE) in various network scenarios, e.g., multiple carrier configuration. The UE may monitor LP-WUS on the Primary Cell (PCell) by default, but may be reconfigured by the network to monitor LP-WUS on alternative secondary cells (SCells) through Radio Resource Control (RRC) signaling. The network may dynamically reassign LP-WUS monitoring from one or more than one cell to another cell or cells, including but not limited to carrier aggregation and dual connectivity configurations. The UE may adapt LP-WUS monitoring with respect to the indication by the network.

[0022] According to some embodiments, the network determines on which carrier or cell to configure LP-WUS. If no specific indication is provided, LP-WUS may be configured on the PCell. The network may indicate assigning LP-WUS to one or more SCells. The network may indicate the LP-WUS monitoring in one particular carrier frequency based on certain conditions. In one example, the carrier is PCell or PSCell. In another example, the carrier is any activated SCell. In another example, the carrier is any carrier of a multiple carrier system.

[0023] According to some embodiments, the network may redirect / update the LP-WUS monitoring cell / carrier based on certain rules / conditions. The network dynamically indicates the UE to monitor the LP-WUS transmission from one cell / carrier to another based on certain conditions. In one example, if an SCell becomes deactivated, dormant or unavailable, LP-WUS is automatically moved to another cell, e.g., PCell, PScell or an active Scell. In another example, the SCell enters the network energy saving mode (NES), such as network goes to cell discontinuoustransmission (DTX). In another example, if UE only supports LP-WUS monitoring in active bandwidth part (BWP), then there is no LP-WUS signaling in the BWP after BWP switching.

[0024] Some embodiments include UE embodiments. By default, a UE may monitor LP-WUS on the Primary Cell (PCell). No additional configuration is required unless specified by the network.

[0025] The UE switches LP-WUS monitoring to the indicated PCell or SCell(s) as instructed provided that the network explicitly indicates that the UE should monitor LP-WUS on a different carrier or cell.

[0026] If the UE determines that the configured LP-WUS cell / carrier has become dormant (e.g., deactivated SCell) or receives an updated LP-WUS indication instructing the UE to monitor another active cell / carrier, then the UE discontinues LP-WUS monitoring on the dormant cell / carrier and shifts to the newly assigned cell / carrier.

[0027] According to some embodiments, a method is performed by a UE for monitoring a WUS. The method comprises: monitoring for a WUS on a first carrier; obtaining an indication to monitor for a WUS on a second carrier; and monitoring for a WUS on the second carrier.

[0028] In particular embodiments, obtaining the indication to monitor for a WUS on the second carrier comprises receiving the indication from a network node. In other embodiments, obtaining the indication to monitor for a WUS on the second carrier comprises autonomously determining to monitor for a WUS on the second carrier.

[0029] For example, autonomously determining to monitor for a WUS on the second carrier may comprise determining the first carrier is no longer suitable for monitoring. Determining that the first carrier is no longer suitable for monitoring may comprise determining one or more of: a cell associated with the first carrier is deactivated, dormant, or in a power saving mode; a traffic load in the first carrier; a WUS is not detected on the first carrier; a signal quality associated with the first carrier is below a threshold; a signal quality associated the second carrier is above a threshold; and a bandwidth part (BWP) associated with the first carrier is deactivated or no WUS is transmitted in the BWP.

[0030] In particular embodiments, the indication to monitor for a WUS on the second carrier comprises an explicit indication of the second carrier. In other embodiments, the indication to monitor for a WUS on the second carrier comprises an implicit indication for the UE to select the second carrier. In particular embodiments, the UE selects the second carrier based on carrier priority and / or based on a list of carriers.

[0031] In particular embodiments, the first carrier comprises a default carrier.

[0032] According to some embodiments, a user equipment comprises processing circuitry operable to perform any of the user equipment methods described above.

[0033] According to some embodiments, a method is performed by a network node for WUS configuration. The method comprises: transmitting to a UE an indication for the UE to monitor for WUS on a first carrier; determining the UE should monitor for a WUS on a second carrier; and transmitting to the UE an indication for the UE to monitor for WUS on the second carrier.

[0034] In particular embodiments, determining the UE should monitor for a WUS on the second carrier comprises determining that the first carrier is no longer suitable for monitoring. Determining that the first carrier is no longer suitable for monitoring may comprise determining one or more of: a cell associated with the first carrier is deactivated, dormant, or in a power saving mode; a traffic load in the first carrier; a WUS is not transmitted on the first carrier; a signal quality associated with the first carrier is below a threshold; a signal quality associated the second carrier is above a threshold; a number of UEs monitoring for a WUS on the first carrier is above a threshold; and a bandwidth part (BWP) associated with the first carrier is deactivated or no WUS is transmitted in the BWP.

[0035] In particular embodiments, the indication to monitor for a WUS on the second carrier comprises an implicit indication for the UE to select the second carrier. For example, the implicit indication may comprise one or more of a command to switch a BWP or a command to activate or deactivate a carrier.

[0036] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0037] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the user equipment described above.

[0038] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

[0039] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments improve power efficiency because a UE only monitors LP-WUS where needed, reducing unnecessary monitoring occasions. Particular embodiments enhance flexibility, LP-WUS can be applied to the cells / carriers that UE support LP-WUS; moreover, particular embodiments distribute UE on different cells / carriers.BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:Figure 1 is timing diagram illustrating the location of a wake-up signal (WUS) and the paging occasion to which it is associated;Figure 2 illustrates a dedicated wake up radio (WUR) used for monitoring a wake-up signal (WUS);Figure 3 illustrates WUS for narrowband Intemet-of-things (NB-IoT) and Long-Term Evolution (LTE);Figure 4 shows an example of a communication system, according to certain embodiments; Figure 5 shows a user equipment (UE), according to certain embodiments;Figure 6 shows a network node, according to certain embodiments;Figure 7 is a block diagram illustrating a virtualization environment, according to certain embodiments;Figure 8 is a flowchart illustrating an example method in a user equipment, according to certain embodiments; andFigure 9 is a flowchart illustrating an example method in a network node, according to certain embodiments.DETAILED DESCRIPTION

[0041] As described above, certain challenges currently exist with low power wake up signal (LP-WUS) in multiple carrier configuration. For example, while Third Generation Partnership Project (3GPP) is actively working on LP-WUS standardization in Release 19, detailed agreements or specifications for its application in multiple-carrier configurations are still under discussion.

[0042] One of the challenges in applying LP-WUS in multiple-carrier configurations (such as carrier aggregation (CA) or dual connectivity (DC)) is determining on which cell / carrier the LP-WUS is configured. From carrier selection perspective, it is unclear whether LP-WUS can be configured only, for example, on the primary cell (PCell), or whether LP-WUS can also be configured on one of the secondary cells (SCell).

[0043] In CA, for example, PCell is typically the main control carrier, making it a natural choice for LP-WUS transmission. However, applying LP-WUS to SCells may improve flexibility but may also introduce synchronization and resource allocation complexities.

[0044] In DC, for example, the UE is connected to two different nodes (master node and secondary node). If LP-WUS is transmitted only on the master node, the secondary node may experience delays in re-establishing the connection. If LP-WUS is applied separately on each node, interference and power coordination must be carefully managed.

[0045] Another challenge is that not all UEs may support LP-WUS across all carriers.

[0046] Although particular examples may refer to multiple-carrier configurations such as DC and CA, the embodiments described herein apply to any multiple-carrier configuration where a user equipment (UE) is able to receive signals on more than one carrier.

[0047] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments configure and manage LP-WUS monitoring by a user equipment (UE) in various network scenarios, e.g., multiple carrier configuration.

[0048] Particular embodiments are described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0049] The term node may refer to a network node or a user equipment (UE). Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), central unit (e.g., in a gNB), distributed unit (e.g., in a gNB), baseband unit, centralized baseband, C-RAN, access point (AP), transmission points, transmission nodes, transmission reception point (TRP), remote radio unit (RRU), remote radio head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. mobile switching center (MSC), mobility management entity (MME), etc.), O&M, OSS, SON, positioning node (e.g. E-SMLC), etc.

[0050] The non-limiting term UE refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), universal serial bus (USB) dongles, etc.

[0051] The term radio access technology, or RAT, may refer to any RAT e.g. UTRA, E-UTRA, narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NewRadio (NR), 4G, 5G, etc. Any of the equipment denoted by the term node, network node or radio network node may be capable of supporting a single or multiple RATs.

[0052] The term signal or radio signal used herein can be any physical signal or physical channel. Examples of downlink physical signals are reference signal (RS) such as primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS) signals in synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB), discovery reference signal (DRS), CRS, positioning reference signal (PRS), etc. RS may be periodic, e.g. RS occasion carrying one or more RSs may occur with certain periodicity, e.g. 20 ms, 40 ms, etc. The RS may also be aperiodic. Each SSB carries NR-PSS, NR-SSS and NR-PBCH in 4 successive symbols. One or multiple SSBs are transmit in one SSB burst which is repeated with certain periodicity, e.g. 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations.

[0053] The SMTC configuration comprises parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with respect to reference time (e.g., serving cell’s system frame number (SFN)), etc. Therefore, SMTC occasion may also occur with certain periodicity, e.g. 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms.

[0054] Examples of uplink physical signals are reference signal such as sounding reference signal (SRS), DMRS, etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are PBCH, NPBCH, PDCCH, PDSCH, sPUCCH, sPDSCH. sPUCCH. sPUSCH, MPDCCH, NPDCCH, NPDSCH, E-PDCCH, PUSCH, PUCCH, NPUSCH, etc.

[0055] The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, sub-slot, mini-slot, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, frame, SFN cycle, hyper-SFN cycle, etc.

[0056] In multicarrier (MC) operation, a UE may operate with at least two serving cells belonging to their respective serving carrier frequencies. In other examples, the UE may operate with at least two carriers, which may belong to the same cell or different cells, and the cell need not be a serving cell. As used herein, multicarrier operation / configuration refers to a UE that is able to receive signals on more than one carrier.

[0057] Some examples of MC operations are carrier aggregation (CA), dual connectivity (DC), multi-connectivity (MuC), etc. The carrier frequency is also referred to as component carrier(CC), frequency layer, serving carrier, frequency channel, etc. Examples of serving cells are special cell (sPCell), secondary cell (SCell), etc. Examples of serving cells are special cell (sPCell), secondary cell (SCell), etc. Examples of SpCell are primary cell (PCell), primary secondary cell (PSCell), etc. The carrier frequencies of SpCell, SCell, PCell and PSCell are referred to as special CC (SpCC) or simply SpC, secondary CC (SCC), primary CC (PCC) and primary secondary CC (PSCC) or simply PSC respectively.

[0058] In CA, the UE is configured with one primary serving cell (called PCell) and one or more secondary serving cells (SCells).

[0059] In DC, the UE is configured with a master cell group (MCG), which contains at least a PCell and a secondary cell group (SCG) which contains at least a PSCell. Each of MCG and SCG may further contain one or more SCells. The PCell manages (e.g., configures, changes, release, etc.) all SCells in MCG and PSCell in SCG. PSCell manages all SCells in SCG. The cells in MCG and SCG may belong to the same RAT (e.g., all cells are NR in both MCG and SCG like in NR-DC) or they may belong to different RATs (e.g., LTE cells in MCG and NR cells in SCG like in EN-DC or NR cells in MCG and LTE cells in SCG like in NE-DC).

[0060] NR CA and MR-DC (Multiple-Radio Dual Connectivity, including NR-DC, EN-DC, and NE-DC) are examples of multiple-carrier operation in NR.

[0061] Some embodiments include network node embodiments. In some embodiments, a network entity (e.g., gNB) configures a UE with a LP-WUS in a multiple-carrier configuration. The network applies LP-WUS in a carrier aggregation (CA) configuration or a dual connectivity (DC) configuration where multiple component carriers (CCs) are assigned to a UE. The LP-WUS may be transmitted on either the PCell or PSCell or one or more SCells, depending on network conditions.

[0062] By default, the LP-WUS may be transmitted on the primary cell (PCell / PSCell), and the network indicates the UE to monitor LP-WUS on the PCell through broadcasting or dedicated signaling or by default if UE reports to support LP-WUS in the carrier frequency of primary cell.

[0063] In some embodiments, the network explicitly indicates an alternative LP-WUS carrier or cell.

[0064] Alternatively, the network may further indicate the LP-WUS monitoring bandwidth part (BWP). In other words, the network may not transmit LP-WUS in all configured BWPs to the UE. When the UE enters the active BWP, which is indicated by the network can monitor LP-WUS, the UE will enter the low power mode to monitor the LP-WUS.

[0065] In some embodiments, the network provides the UE with an indication specifying one or more other cells (may be PSCell and / or Secondary Cells (SCells)) for LP-WUS monitoring.Upon receiving the indication, the UE modifies its wake-up procedure and monitors the designated cells for LP-WUS instead of or in addition to the PCell. For example, when the UE reports that it only supports LP-WUS in a frequency that is not the frequency of the PCell, the network may indicate to the UE to monitor the LP-WUS in that frequency / cell if the network transmits LP-WUS in that frequency / cell.

[0066] The indication may comprise RRC signaling, such as an RRC Reconfiguration or system information block (SIB) update, or layer one (LI) signaling (e.g., on the physical channel PDCCH), or layer two (L2) signaling (e.g., on the medium access control (MAC) layer, e.g., MAC control element (CE)).

[0067] The indication may be transmitted in a particular cell / carrier, e.g., PCell or a specific active SCell determined by the network.

[0068] Alternatively, if the UE reports a capability for supporting LP-WUS on certain carriers / cells, the network may indicate at least one of the carriers / cells from the reported carriers / cells for LP-WUS transmission. Furthermore, if the UE indicates the preferred carriers ) / cell(s) among all carriers / cells for LP-WUS reception, the network may indicate the preferred carriers ) / cell(s) for LP-WUS transmission.

[0069] In some embodiments, the network dynamically reassigns / redirects / updates the LP-WUS transmission from one cell / carrier to another based on certain conditions.

[0070] One condition is the availability of the original LP-WUS cell / carrier. If the originally assigned cell / carrier becomes dormant, deactivated, or enters the network energy saving mode (NES)mode due to network reconfiguration, energy-saving mechanisms, or interference conditions, the network indicates the UE to switch LP-WUS monitoring to an alternate active cell / carrier where the reassignment signaling may be RRC signaling, such as an RRC Reconfiguration or SIB update, or LI signaling (e.g., on the physical channel PDCCH), or L2 signaling (e.g., on the MAC layer, e.g., MAC CE).

[0071] Another condition is the network status. For example, if the network detects the traffic loading constraint in the PCell due to a massive number of UEs using LP-WUS camping on the frequency and decides to perform offloading on the PCell, then the network indicates to some UEs to monitor the LP-WUS in other cells, such as SCells.

[0072] Another condition is the channel quality. For example, if a UE detects the channel quality of the assigned SCell is not good enough, the UE may request to switch the WUS monitoring to another specific cell.

[0073] Another condition is the UE capability to monitor LP-WUS in active BWP. For example, if a UE reports to only support monitoring LP-WUS in active BWP, and after BWPswitching, there is no LP-WUS transmission in the active BWP of the WUS monitoring cell, the network may indicate the next LP-WUS monitoring carrier.

[0074] In some embodiments, the network applies LP-WUS in a Dual Connectivity (DC) configuration where the UE is connected to both a Master Node (MN) and a Secondary Node (SN). The LP-WUS may be managed separately for each node, with independent wake-up configurations for different frequency bands or coverage areas.

[0075] In an example scenario, a UE operating with three carriers (PCell + SCell# 1 + SCell#2) is configured by the network to monitor LP-WUS on SCell# 1 instead of the default PCell. This configuration is chosen to optimize wake-up performance in cases where the PCell is on a high-frequency band with limited coverage. If SCell# 1 is later deactivated, the network instructs the UE to revert LP-WUS monitoring to the PCell or another active SCell.

[0076] In some embodiments, the network implements an adaptive LP-WUS strategy that adjusts the LP-WUS transmission parameters based on traffic patterns, mobility state, or UE capability.

[0077] In an example scenario, the network may configure the LP-WUS transmission patterns, e.g., periodicity or frequency, differently for different carriers / cells.

[0078] Some embodiments include UE embodiments. In some embodiments, the UE may be configured by the network to monitor LP-WUS in a CA or DC configuration, where multiple component carriers (CCs) are assigned to the UE. The LP-WUS may be transmitted on either the PCell or PSCell or one or more SCells, depending on network conditions.

[0079] In some embodiments, the UE shall monitor the LP-WUS on the PCell, unless otherwise indicated by the network. Upon receiving such a signaling message, the UE shall modify its wake-up procedure and monitor the designated cells (e.g., may be PScell and / or SCell(s)) for LP-WUS, instead of, or in addition to, the PCell.

[0080] In some embodiments, the network may signal the UE to switch LP-WUS monitoring to an alternate active cell. Upon receiving such a signal, the UE shall discontinue monitoring LP-WUS on the deactivated cell and begin monitoring LP-WUS on the newly assigned active cell.

[0081] Optionally or additionally, the UE may manage monitoring LP-WUS sequentially provided that more than one carriers / cells are indicated by the network. One approach is that the UE first tries monitoring LP-WUS on the first carrier / cell among all carriers / cells indicated by the network. If the UE cannot detect LP-WUS, then the UE may switch monitoring LP-WUS on another carrier / cell. The order of carriers / cells for monitoring LP-WUS may be indicated by the network or determined by the UE or with respect to a pre-defined rule. Some examples of such rules are as follows.

[0082] In one example, the UE shall first monitor LP-WUS on carriers / cells on lower frequencies, e.g., frequency range one (FR1), then higher frequencies, e.g., frequency range two (FR2). Or the UE shall first monitor LP-WUS on carriers / cells on higher frequencies, e.g., FR2, then lower frequencies, e.g., FR1.

[0083] In one example, the UE shall first monitor LP-WUS on high priority carriers / cells, then low priority carriers / cells, where the priority list is provided by the network.

[0084] In one example, the UE shall first monitor LP-WUS on carriers / cells with higher signal quantity or quality based on received RSRP, RSRQ or SINR, then carriers / cells with lower signal quantity or quality.

[0085] In some embodiments, the UE may revert to monitoring LP-WUS on the PCell or another cell (e.g., PSCell or an active SCell), in one or more of the below conditions:• The cell indicated for LP-WUS monitoring is deactivated or dormant and no indication from the network requesting the UE switch LP-WUS monitoring to an alternate cell. • The UE cannot detect LP-WUS on the cell that indicated by the network for LP-WUS monitoring.• The UE detects the current cell has poor signal quantity or quality based on received RSRP, RSRQ or SINR.• The UE detects another cell that has better signal quantity or quality based on received RSRP, RSRQ or SINR, than the current cell.• The UE prefers to adopt another cell for LP-WUS monitoring other than the indicated cells.

[0086] In some embodiments, in a DC configuration, where the UE is connected to both a MN and a SN, the UE may independently manage LP-WUS monitoring for each node. The network may configure the UE to monitor LP-WUS on the SN. If the SN is deactivated, the UE shall stop monitoring LP-WUS on the SN and rely solely on the MN for wake-up signaling.

[0087] Figure 4 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0088] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0089] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0090] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0091] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102 and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving andcompiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0092] As a whole, the communication system 100 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0093] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0094] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0095] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 forthe UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0096] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0097] Figure 5 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rdGeneration Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0098] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0099] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0100] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0101] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive displaymay include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0102] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0103] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0104] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, suchas one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0105] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0106] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0107] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0108] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or theswitch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0109] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, amotion detector, a thermostat, asmoke detector, adoor / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in Figure 2.

[0110] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.[oni] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities describedabove. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0112] Figure 6 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0113] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0114] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0115] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., aNodeB component and aRNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components maybe duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0116] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0117] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC).In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0118] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0119] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0120] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0121] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0122] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly,the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0123] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0124] Embodiments of the network node 300 may include additional components beyond those shown in Figure 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0125] Figure 7 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 500includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0126] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0127] Hardware 504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.

[0128] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0129] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.

[0130] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization.Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.

[0131] Figure 8 is a flowchart illustrating an example method 800 in a user equipment, according to certain embodiments. In particular embodiments, one or more steps of Figure 8 may be performed by UE 200 described with respect to Figure 5. The UE is capable of monitoring a wake-up signal (WUS), and the UE is capable of operating with multiple carriers.

[0132] The method begins at step 812, where the user equipment (e.g., UE 200) monitors for a WUS on a first carrier.

[0133] In particular embodiments, the first carrier comprises a default carrier. For example, the UE may monitor for WUS on a PCell by default. In other embodiments, the default carrier may comprise any carrier of a multiple carrier system.

[0134] In particular embodiment, the UE may monitor the first carrier according to any of the examples and embodiments described herein.

[0135] At step 814, the UE obtains an indication to monitor for a WUS on a second carrier. In particular embodiments, obtaining the indication to monitor for a WUS on the second carrier comprises receiving the indication from a network node. For example, the network node may transmit a message to the UE. The message may comprise an identifier of a carrier. The message may comprise an RRC message, MAC CE, broadcast message, etc.

[0136] In other embodiments, obtaining the indication to monitor for a WUS on the second carrier comprises autonomously determining to monitor for a WUS on the second carrier. For example, autonomously determining to monitor for a WUS on the second carrier may comprise the UE determining the first carrier is no longer suitable for monitoring. Determining that the first carrier is no longer suitable for monitoring may comprise determining one or more of: a cell associated with the first carrier is deactivated, dormant, or in a power saving mode; a traffic load in the first carrier (e.g., switch to second carrier for load balancing); a WUS is not detected on the first carrier; a signal quality (e.g., RSRP, RSRQ, etc.) associated with the first carrier is below athreshold; a signal quality (e.g., RSRP, RSRQ, etc.) associated the second carrier is above a threshold; and a BWP associated with the first carrier is deactivated or no WUS is transmitted in the BWP.

[0137] In particular embodiments, the indication to monitor for a WUS on the second carrier comprises an explicit indication of the second carrier (e.g., includes an explicit identifier for a carrier or cell (e.g., PCell, SCell)). In other embodiments, the indication to monitor for a WUS on the second carrier comprises an implicit indication for the UE to select the second carrier. For example, the indication instructs the UE to switch carriers for monitoring for WUS, but does not explicitly indicate which carrier. The UE determines which carrier based on one or more conditions. In particular embodiments, the UE selects the second carrier based on carrier priority and / or based on a list of carriers. The UE may have previously received a list of carriers, e.g., via broadcast information or specific configuration message. A more complete list and description of the conditions are described with respect to the embodiments and examples described herein.

[0138] In particular embodiments, the UE obtains the indication to monitor for a WUS on a second carrier according to any of the examples and embodiments described herein.

[0139] At step 816, the UE monitors for a WUS on the second carrier. Steps 814 and 816 may be repeated as network conditions change and the UE receives another indication to switch carriers for WUS monitoring or autonomously determines to switch carriers for WUS monitoring.

[0140] Modifications, additions, or omissions may be made to method 800 of Figure 8. Additionally, one or more steps in the method of Figure 8 may be performed in parallel or in any suitable order.

[0141] Figure 9 is a flowchart illustrating an example method 900 in a network node, according to certain embodiments. In particular embodiments, one or more steps of Figure 9 may be performed by network node 300 described with respect to Figure 6.

[0142] The method begins at step 912, where the network node (e.g., network node 300) transmits to a UE an indication for the UE to monitor for WUS on a first carrier. For example, the network node may transmit a message to the UE. The message may comprise an identifier of a carrier. The message may comprise an RRC message, MAC CE, broadcast message, etc.

[0143] In particular embodiments, the indication may indicate a default carrier.

[0144] At step 914, the network node determines the UE should monitor for a WUS on a second carrier. In particular embodiments, determining the UE should monitor for a WUS on the second carrier comprises determining that the first carrier is no longer suitable for monitoring. Determining that the first carrier is no longer suitable for monitoring may comprise determining one or more of: a cell associated with the first carrier is deactivated, dormant, or in a power savingmode; a traffic load in the first carrier; a WUS is not transmitted on the first carrier; a signal quality associated with the first carrier is below a threshold; a signal quality associated the second carrier is above a threshold; a number of UEs monitoring for a WUS on the first carrier is above a threshold; and a bandwidth part (BWP) associated with the first carrier is deactivated or no WUS is transmitted in the BWP.

[0145] In particular embodiments, the network node determines the UE should monitor for a WUS on a second carrier based on one or more conditions, which are described in more detail according to any of the examples and embodiments described herein.

[0146] At step 916, the network node transmits to the UE an indication for the UE to monitor for WUS on the second carrier. For example, the network node may transmit a message to the UE. The message may comprise an identifier of a carrier. The message may comprise an RRC message, MAC CE, broadcast message, etc.

[0147] In particular embodiments, the indication to monitor for a WUS on the second carrier comprises an implicit indication for the UE to select the second carrier. For example, the implicit indication may comprise one or more of a command to switch a BWP or a command to activate or deactivate a carrier.

[0148] Modifications, additions, or omissions may be made to method 900 of Figure 9. Additionally, one or more steps in the method of Figure 9 may be performed in parallel or in any suitable order.

[0149] Some example embodiments are described below.Group A Embodiments1. A method performed by a user equipment (UE) for monitoring a wakeup signal (WUS), the method comprising:monitoring for a WUS on a first carrier;obtaining an indication to monitor for a WUS on a second carrier; andmonitoring for a WUS on the second carrier.2. The method of the previous embodiment, wherein obtaining the indication to monitor for the WUS on the second carrier comprising receiving the indication from a network node.3. The method of embodiment 1, wherein obtaining the indication to monitor for the WUS on the second carrier comprises determining that the first carrier is no longer suitable for monitoring.4. The method of the previous embodiment, wherein determining that the first carrier is nolonger suitable for monitoring comprises determining one or more of:a cell associated with the first carrier is deactivated or dormant;a WUS is not detected on the first carrier;a signal quality associated with the first carrier is below a threshold; anda signal quality associated with another carrier is better than a signal quality associated with the first carrier.5. The method of any one of the previous embodiments, wherein the indication comprises an explicit indication of the second carrier.6 The method of any one of embodiments 1 -4, wherein the indication comprises an implicit indication for the UE to select the second carrier.7. The method of the previous embodiment, wherein the UE selects the second carrier based on carrier priority.8. The method of embodiment 7, wherein the UE selects the second carrier based on a preconfigured list of carriers.9. The method of any one of the previous embodiments, wherein the first carrier comprises a default carrier.10. A method performed by a wireless device, the method comprising:any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.11. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.Group B Embodiments12. A method performed by a network node for wakeup signal (WUS) configuration, the method comprising:transmitting to a wireless device an indication of a first carrier for the wireless device to monitor for WUS;determining the wireless device should monitor for a WUS on a second carrier; and transmitting to the wireless device an indication of a second carrier for the wireless device to monitor for WUS.13. The method of the previous embodiment, determining the wireless device should monitor for the WUS on the second carrier comprises determining that the first carrier is no longer suitable for monitoring.14. The method of the previous embodiment, wherein determining that the first carrier is no longer suitable for monitoring comprises determining one or more of:a cell associated with the first carrier is deactivated or dormant;a WUS is not detected on the first carrier;a signal quality associated with the first carrier is below a threshold; anda signal quality associated with another carrier is better than a signal quality associated with the first carrier.15. The method of any one of the previous three embodiments, wherein the indication comprises an explicit indication of the second carrier.16 The method of any one of embodiments 12-14, wherein the indication comprises an implicit indication for the UE to select the second carrier.17. A method performed by a network node, the method comprising:any of the steps, features, or functions described above with respect to a network node, either alone or in combination with other steps, features, or functions described above.18. The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above.Group C Embodiments19. A user equipment comprising:processing circuitry configured to perform any of the steps of any of the Group A embodiments; andpower supply circuitry configured to supply power to the processing circuitry.20. A network node comprising:processing circuitry configured to perform any of the steps of any of the Group B embodiments;power supply circuitry configured to supply power to the processing circuitry.21. A user equipment (UE) comprising:an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda battery connected to the processing circuitry and configured to supply power to the UE.

[0150] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0151] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. 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 implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0152] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Otherchanges, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

Claims

Claims1. A method (800) performed by a user equipment (UE) for monitoring a wake-up signal (WUS), the method comprising:monitoring (812) for a WUS on a first carrier;obtaining (814) an indication to monitor for a WUS on a second carrier; and monitoring (816) for a WUS on the second carrier.

2. The method of claim 1, wherein obtaining the indication to monitor for a WUS on the second carrier comprises receiving the indication from a network node.

3. The method of claim 1, wherein obtaining the indication to monitor for a WUS on the second carrier comprises autonomously determining to monitor for a WUS on the second carrier.

4. The method of claim 3, wherein autonomously determining to monitor for a WUS on the second carrier comprises determining the first carrier is no longer suitable for monitoring.

5. The method of claim 4, wherein determining that the first carrier is no longer suitable for monitoring comprises determining one or more of:a cell associated with the first carrier is deactivated, dormant, or in a power saving mode; traffic load in the first carrier;a WUS is not detected on the first carrier;a signal quality associated with the first carrier is below a threshold;a signal quality associated the second carrier is above a threshold; anda bandwidth part (BWP) associated with the first carrier is deactivated or no WUS is transmitted in the BWP.

6. The method of any one of claims 1-5, wherein the indication to monitor for a WUS on the second carrier comprises an explicit indication of the second carrier.

7. The method of any one of claims 1-6, wherein the indication to monitor for a WUS on the second carrier comprises an implicit indication for the UE to select the second carrier.

8. The method of claim 7, wherein the UE selects the second carrier based on carrierpriority.

9. The method of any one of claims 7-8, wherein the UE selects the second carrier based on a list of carriers.

10. The method of any one of claims 1-9, wherein the first carrier comprises a default carrier.

11. A user equipment (200) capable of monitoring a wake-up signal (WUS), the user equipment (UE) comprising processing circuitry (202) operable to:monitor for a WUS on a first carrier;obtain an indication to monitor for a WUS on a second carrier; andmonitor for a WUS on the second carrier.

12. The UE of claim 11, wherein the processing circuitry is operable to obtain the indication to monitor for a WUS on the second carrier by receiving the indication from a network node.

13. The UE of claim 11, wherein the processing circuitry is operable to obtain the indication to monitor for a WUS on the second carrier by autonomously determining to monitor for a WUS on the second carrier.

14. The UE of claim 13, wherein the processing circuitry is operable to autonomously determine to monitor for a WUS on the second carrier by determining the first carrier is no longer suitable for monitoring.

15. The UE of claim 14, wherein the processing circuitry is operable to determine that the first carrier is no longer suitable for monitoring by determining one or more of:a cell associated with the first carrier is deactivated, dormant, or in a power saving mode; a traffic load in the first carrier;a WUS is not detected on the first carrier;a signal quality associated with the first carrier is below a threshold;a signal quality associated the second carrier is above a threshold; anda bandwidth part (BWP) associated with the first carrier is deactivated or no WUS istransmitted in the BWP.

16. The UE of any one of claims 11-15, wherein the indication to monitor for a WUS on the second carrier comprises an explicit indication of the second carrier.

17. The UE of any one of claims 11-16, wherein the indication to monitor for a WUS on the second carrier comprises an implicit indication for the UE to select the second carrier.

18. The UE of claim 17, wherein the UE selects the second carrier based on carrier priority.

19. The UE of any one of claims 17-18, wherein the UE selects the second carrier based on a list of carriers.

20. The UE of any one of claims 11-19, wherein the first carrier comprises a default carrier.

21. A method (900) performed by a network node for wake-up signal (WUS) configuration, the method comprising:transmitting (912) to a user equipment (UE) an indication for the UE to monitor for WUS on a first carrier;determining (914) the UE should monitor for a WUS on a second carrier; and transmitting (916) to the UE an indication for the UE to monitor for WUS on the second carrier.

22. The method of claim 21, wherein determining the UE should monitor for a WUS on the second carrier comprises determining that the first carrier is no longer suitable for monitoring.

23. The method of claim 22, wherein determining that the first carrier is no longer suitable for monitoring comprises determining one or more of:a cell associated with the first carrier is deactivated, dormant, or in a power saving mode; a traffic load in the first carrier;a WUS is not transmitted on the first carrier;a signal quality associated with the first carrier is below a threshold;a signal quality associated the second carrier is above a threshold;a number of UEs monitoring for a WUS on the first carrier is above a threshold; anda bandwidth part (BWP) associated with the first carrier is deactivated or no WUS is transmitted in the BWP.

24. The method of any one of claims 21-23, wherein the indication to monitor for a WUS on the second carrier comprises an explicit indication of the second carrier.

25. The method of claim 24, wherein the explicit indication comprises a list of carriers.

26. The method of claim 25, wherein the list of carriers is ordered based on carrier priority.

27. The method of any one of claims 25-26, wherein the list of carriers is ordered based on carrier frequency.

28. The method of any one of claims 21-23, wherein the indication to monitor for a WUS on the second carrier comprises an implicit indication for the UE to select the second carrier.

29. The method of claim 28, wherein the implicit indication comprises one or more of a command to switch a bandwidth part (BWP) or a command to activate or deactivate a carrier.

30. The method of any one of claims 21-29, wherein the first carrier comprises a default carrier.

31. A network node (300) wake-up signal (WUS) configuration, the network node comprising processing circuitry (302) operable to:transmit to a user equipment (UE) an indication for the UE (200) to monitor for WUS on a first carrier;determine the UE should monitor for a WUS on a second carrier; andtransmit to the UE an indication for the UE to monitor for WUS on the second carrier.

32. The network node of claim 31, wherein the processing circuitry is operable to determine the UE should monitor for a WUS on the second carrier by determining that the first carrier is no longer suitable for monitoring.

33. The network node of claim 32, wherein the processing circuitry is operable todetermine that the first carrier is no longer suitable for monitoring by determining one or more of: a cell associated with the first carrier is deactivated, dormant, or in a power saving mode; a traffic load in the first carrier;a WUS is not transmitted on the first carrier;a signal quality associated with the first carrier is below a threshold;a signal quality associated the second carrier is above a threshold;a number of UEs monitoring for a WUS on the first carrier is above a threshold; and a bandwidth part (BWP) associated with the first carrier is deactivated or no WUS is transmitted in the BWP.

34. The network node of any one of claims 31-33, wherein the indication to monitor for a WUS on the second carrier comprises an explicit indication of the second carrier.

35. The network node of claim 34, wherein the explicit indication comprises a list of carriers.

36. The network node of claim 35, wherein the list of carriers is ordered based on carrier priority.

37. The network node of any one of claims 35-36, wherein the list of carriers is ordered based on carrier frequency.

38. The network node of any one of claims 31-33, wherein the indication to monitor for a WUS on the second carrier comprises an implicit indication for the UE to select the second carrier.

39. The network node of claim 38, wherein the implicit indication comprises one or more of a command to switch a bandwidth part (BWP) or a command to activate or deactivate a carrier.

40. The network node of any one of claims 31-39, wherein the first carrier comprises a default carrier.

Images