Wake up signal (WUS) coverage adaptation

Abstract

A method implemented in a user equipment (UE) that is configured to communicate with a network node includes: operating a wake up radio (WUR) by one or both of: adjusting a RSRP threshold associated with low-power wake up signal (LP-WUS) monitoring by using an offset value; and indicating, to the network node, a plurality of reference sensitivity (REFSENS) levels, receiving a REFSENS configuration in response to the indicating, and operating the WUR based on the REFSENS configuration.

Description

[0001] WAKE UP SIGNAL (WUS) COVERAGE ADAPTATION

[0002] FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to wake-up signal (WUS) coverage adaptation.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] NR WUR

[0007] Wake-up receiver (WUR), sometimes also referred to as “wake-up radio,” refers to enabling a low-power receiver in UEs, which, in case of the detection of a wake-up signal (WUS), wakes 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 (PO), scheduling the paging message on physical downlink shared channel (PDSCH)) or PDCCH scheduling downlink (DL) data. A benefit of employing WUR is lowering energy consumption and increasing device battery life, or at a fixed energy consumption the downlink latency can be reduced (shorter DRX / duty-cycles and more frequent checks for incoming transmissions).

[0008] In general, there are two approaches for detecting WUS:

[0009] • Using the main receiver:

[0010] o No need for additional dedicated hardware / receiver for monitoring WUS o Coverage of the main receiver is not typically impacted

[0011] o Limited power saving gain as the main receiver monitors WUS

[0012] • Having a dedicated receiver (WUR):

[0013] o Extremely low power, simple and low-cost receiver architecture, relaxed requirements, noisier (i.e., less accurate) clock or oscillator o Significant power saving gain can be achieved by maximizing the time in which the main receiver can be in the sleep modeo Enablers for zero energy / battery-less devices, and energy harvesting operations.

[0014] o There are coverage considerations given the tradeoff between WUR power consumption and sensitivity.

[0015] In 3GPP Release 18 (Rel-18), there has been rather large interest to introduce WUR for NR, with an ambition for achieving more significant energy efficiency improvement compared to solutions already specified in earlier 3 GPP releases. As explained above, the only specification support that may be needed to be able to use a WUR in the UE is a specification of a WUS and a long enough time gap between the WUS and the PDCCH in the PO (to allow the UE to start up the main receiver). Therefore, one difference from 3GPP Release 17 (Rel-17) permanent equipment identifier (PEI) is the WUS in Rel-18 should not be PDCCH-based and allow for a low complexity and low power receiver, i.e., WUR with low complexity modulation and detection techniques (e.g., using on-off keying (OOK) modulation and non-coherent detection).

[0016] The benefit of WUR is to reduce the energy consumption of the UE, such that unless there is any paging and data for the UE it can remain in a power saving state. This will extend the battery life of the UE, or alternatively enable shorter downlink latency (shorter DRX) at a fixed battery life.

[0017] The Rel-18 study item on “low-power wake-up signal and receiver for NR” is completed and the technical report is provided in: 3GPP Technical Report (TR) 38.869, VO.4.0, “Study on low-power Wake-up Signal and Receiver for NR.” Subsequently, there is a 3GPP Release 19 (Rel-19) Work Item to specify the various design aspects of WUS / WUR.

[0018] For Rel-19, a work item has been agreed to specify the wake-up signal for both RRC Idle / Inactive and RRC Connected states: RP-234056, New WID: Low-power wakeup signal and receiver for NR (LP WUS / WUR). The objectives are the following:

[0019]

[0020]

[0021] &

[0022]

[0023] WUS functionality in RRC connected mode

[0024] The relevant 3 GPP Technical Specification Group Radio Access Network (TSGRAN), RAN WG1 (RANI) agreements related to this so far:

[0025] Working Assumption

[0026] Agreement

[0027] Confirm the following working assumption with the addition of the note at the bottom:

[0028] Working Assumption

[0029] From RANI perspective, for the entry / exit conditions for LP-WUS monitoring in IDLE / inactive mode,

[0030] The UE may start LP-WUS monitoring if

[0031] o the serving cell measurement performed by the MR is above entry threshold(s), if configured by the gNB

[0032] o FFS other conditions, and if any, whether all or one or some of the conditions need to be satisfied

[0033] If UE starts LP-WUS monitoring, it may stop the legacy PO monitoring before UE receives LP-WUS indicating wake-up

[0034] The UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if

[0035] o the serving cell measurement performed by the LR is below exit threshold(s), if configured by the gNB

[0036] o FFS other conditions, and if any, whether all or one or some of the conditions need to be satisfied

[0037] - FFS the serving cell measurement metrics

[0038] The entry / exit thresholds can be configured separately for different types of LR It is left to RAN2 discussion whether the threshold(s) are always configured by the gNB.

[0039] - Note: This may be revisited based on the RAN2 / RAN4 discussion.Note: this does not intend to impact any agreements and working assumptions made in RAN1 / RAN2 after the working assumption.

[0040] RAN2 latest agreement related to this so far:

[0041] 8.4.2 Procedure and configuration of LP-WUS in RRC IDLE / INACTIVE Entry / exit condition

[0042] • RAN2 will further discuss the details about LP-WUS monitoring entry / exit conditions based on RANl’s existing working assumptions.

[0043] • The LP-WUS related configuration in SIB at least include the following information for IDLE / INACTIVE:

[0044] LP-SS configuration

[0045] LP-WUS configuration

[0046] Entry / exit condition for LP-WUS monitoring (FFS if it is always configured)

[0047] • Baseline for entry condition definition: If the serving cell quality, e.g.

[0048] RSRP, RSRQ from MR, is above threshold(s) (if configured), UE may start to monitor LP-WUS, if UE monitors LP-WUS, it may stop monitoring the legacy PO. FFS if any measurement from LR is needed.

[0049] • Baseline for exit condition definition: If the serving cell measurement result based on LR is below a threshold (if configured), UE monitors PO as in legacy and it may stop monitoring the LP-WUS.

[0050] RANI has reached the below agreement after the study of the coverage aspect for LP-WUS:

[0051] Agreement

[0052] For evaluation of LP-WUS and LP-SS design to achieve coverage of PUSCH for messages from RANI perspective, at least the following SNR values should be considered:

[0053] • SNR=-3dB for noise figure (NF) of LR = NF of MR+ 8dB

[0054] • SNR= -0.5dB for NF of LR = NF of MR+ 5dB

[0055] • SNR=2dB for NF of LR = NF of MR+ 2dB

[0056] • Note 1 : The NF of MR is assumed as 7dB

[0057] • LR is low power receiver (WUR)

[0058] • MR is the main receiver

[0059] In RAN4, the latest NF and REFSENS discussion is below

[0060] Issue 2-2-3: companies input on SNR, NF and IM value for FR1 OOK-based LR

[0061] >

[0062]

[0063] Note: the SNR value may be updated based on new simulation results. RANI waveform design is not finalized as of this WF.

[0064] Issue 2-2-4: companies input on SNR, NF and IM value for FR1 OFDM-based LR

[0065] >

[0066]

[0067] Some companies want to specify different NF for different power saving target with below discussion.

[0068] Agreements:

[0069] o On how to handle the NF values:

[0070] ■ Option 1 : For NF whether average value can be adopted.■ Option 2: two sets NFs for different LP-WUR types with different power consumption target

[0071] ■ Option 3: also consider coverage

[0072] According to the RANI and 3GPP Technical Specification Group Radio Access Network (TSG RAN), RAN WG2 (RAN2), current agreements on the coverage of low power WUS (LP-WUS), the network will configure the Reference Signal Received Power (RSRP) of the serving (e.g., serving cell measurement performed by the LR (or UE) is below exit threshold(s), if configured by the network node) for all UE supporting WUR. The RSRP may relate to the noise figure of WUR, as the SNR operating point is defined accordingly from RANI study. The noise figure (NF) implementation includes a specific design parameter. Some UE vendors may have a better NF, but other UE vendors may not. When an RSPR is configured by the network to be the same for all WUR UEs, coverage of the LP-WUS will be the same for all WUR UE regardless of the NF possibly being different between different UE vendors.

[0073] However, the WUR with a better NF can provide better coverage of the LP-WUS than a WUR with a worse NF. Setting the same RSRP threshold of a serving cell does not use the potential of a WUR hardware and therefore has penalties on the power saving performance for the UE with more powerful WUR.

[0074] SUMMARY

[0075] The power saving gain can be maximum for a UE at the cell edge as the low-noise amplifier (LNA) may need to operate in the highest gain mode to receive a low serving cell signal.

[0076] Hence, a solution is needed to realize the full power saving potential for a WUR with different capabilities and with different NFs in design.

[0077] Some embodiments advantageously provide methods, systems, and apparatuses for WUS coverage adaptation.

[0078] In some embodiments, the WUR will be specified with different reference sensitivity power level (REFSENS) level with different NFs. For example, one baseline REFSENS with a baseline NF and one tightened / worsened REFSENS with a comparatively better or worse NF design. For a UE that can pass the tightened REFSENS, the UE is allowed to have an offset compensation on the RSRP threshold of LP-WUS signal configured in the serving cell.A UE can report a capability with a better or worse REFSENS performance. The reported value could be a delta dB representing a performance difference compared to the baseline REFSENS, or it could be absolute REFSENS performance. It may also be that a UE reports more than one REFSENS capability, which correspond to different energy saving levels in the receiver.

[0079] For the UE with the capability of different REFSENS performance compared to the baseline, it may be allowed to associate a value X to the RSPR threshold setting on the LP-WUS monitoring entry / exit condition:

[0080] o Applying this value X as a compensation factor on the RSRP threshold configured for WUR for entry / exist condition

[0081] The value mentioned above may be derived from the performance difference between the UE supporting new capability providing a performance difference to a baseline performance. One example of the performance difference is the REFSENS requirement specified, e.g., in 3GPP Technical Specification (TS) 38.101-1 for WUR. Alternatively, the value may be an absolute REFSENS value, and the network may configure an RSRP threshold based on knowing the absolute REFSENS performance.

[0082] If a UE is capable of achieving different REFSENS levels, the UE may report multiple potential REFSENS levels, and the network may configure a specific REFSENS level for the UE. The network may then set an RSRP threshold based on the REFSENS level.

[0083] Alternatively, if the UE has a capability for several REFSENS levels, the network may configure a REFSENS level that is suitable for the particular cell / deployment so that the UE may achieve coverage within the RSRP threshold set or expected for the cell, without setting an RSRP threshold specific to the UE.

[0084] A UE may be allowed to either compensate the RSRP threshold set for LP-WUS monitoring entry / exit condition with an offset value derived from performance deviation comparing to the baseline performance, e.g., as defined in 3GPP TS 38.101-1. Such compensation value can be derived from capability reporting by the UE. One example of the such performance is REFSENS, which tests the minimum received power level that a WUR must meet. Or as an alternative, the UE may report several potential REFSENS levels (or other types of levels), and the network configures a UE REFSENS level (or other type of level) that is suitable for the RSRP range of a particular cell.

[0085] Examples of embodiments described herein include mechanisms to adapt the WUS coverage with different noise figure designs and thereby realize the power saving gain fora WUR for better coverage with better noise figure. Embodiments can also avoid unnecessary MR and WUR switch.

[0086] According to one aspect of the present disclosure, a method in a network node is provided. The method includes configuring the UE to operate a WUR by one or both of: causing the UE to adjust a RSRP threshold associated with LP-WUS monitoring by using an offset value; and receiving, from the UE, a plurality of REFSENS levels, selecting a REFSENS configuration in response to receiving the plurality of REFSENS levels, and transmitting the REFSENS configuration to the UE to cause the UE to operate the WUR based on the REFSENS configuration.

[0087] According to another aspect of the present disclosure, a network node is provided. The network node is configured to configure the UE to operate a WUR by one or both of: causing the UE to adjust a RSRP threshold associated with LP-WUS monitoring by using an offset value; and receiving, from the UE, a plurality of REFSENS levels, selecting a REFSENS configuration in response to receiving the plurality of REFSENS levels, and transmitting the REFSENS configuration to the UE to cause the UE to operate the WUR based on the REFSENS configuration.

[0088] According to another aspect of the present disclosure, a method in a UE is provided. The method includes operating a WUR by one or both of: adjusting a RSRP threshold associated with LP-WUS monitoring by using an offset value; and indicating, to the network node, a plurality of REFSENS levels, receiving a REFSENS configuration in response to the indicating, and operating the WUR based on the REFSENS configuration.

[0089] According to another aspect of the present disclosure, a UE is provided. UE is configured to operate a WUR by one or both of: adjusting a RSRP threshold associated with LP-WUS monitoring by using an offset value; and indicating, to the network node, a plurality of REFSENS levels, receiving a REFSENS configuration in response to the indicating, and operating the WUR based on the REFSENS configuration.

[0090] BRIEF DESCRIPTION OF THE DRAWINGS

[0091] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0092] FIG. l is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;FIG. 2 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;

[0093] FIG. 3 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;

[0094] FIG. 4 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0095] FIG. 5 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;

[0096] FIG. 6 is a flowchart of another example process in a network node according to some embodiments of the present disclosure; and

[0097] FIG. 7 is a flowchart of another example process in a user equipment according to some embodiments of the present disclosure.

[0098] DETAILED DESCRIPTION

[0099] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to WUS coverage adaptation. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0100] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0101] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0102] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0103] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi -cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0104] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radiosignals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0105] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0106] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0107] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0108] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in thecontext of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0109] Some embodiments are directed to WUS coverage adaptation.

[0110] Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. The core network 14 includes one or more network nodes 15. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0111] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 16 support (or the same access network nodes 16 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, communication system 10 may support multiple generations of related communication standards (e.g., 4G, 5G and 6G 3 GPP communication standards) and, as a result, may include an access network 12 and / or a core network 14 that supports multiple different standard generations or may include multiple access networks 12 and / or multiple core networks 14 with individual networks supporting different standards generations.

[0112] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dualconnectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTEZE-UTRAN, a gNB for NR / NG-RAN (i.e. being configured for multiradio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC) and / or Wi-Fi.

[0113] A network node 16 (eNB or gNB) is configured to include a configuration unit 24 which is configured to perform one or more network node 16 functions described herein, including functions related to WUS coverage adaptation. A user equipment 22 is configured to include an implementation unit 26 which is configured to perform one or more UE 22 functions described herein, including functions related to WUS coverage adaptation.

[0114] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 2.

[0115] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a communication interface 29 comprising a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0116] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16.

[0117] Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include configuration unit 24 which is configured to perform one or more network node 16 functions described herein, including functions related to WUS coverage adaptation.

[0118] The network node 16 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 16 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities 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 16 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 40 or portions of memory 40 for different RATs) and some components may be reused (e.g., a same antenna may be shared by different RATs). The network node 16 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 16, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 16.

[0119] In certain alternative embodiments, network node 16 may be capable of wireless communication but does not include separate radio front-end circuitry, instead, theprocessing circuitry 36 includes radio front-end circuitry and is connected to the antenna 34. Similarly, in some embodiments, all or some of the RF receivers, transmitters and / or transceivers are part of the radio interface 30. In still other embodiments, the communication interface 29 includes one or more ports or terminals, the radio interface 30, and the RF receiver, transmitter and / or transceiver, and the communication interface 31 communicates with baseband processing circuitry, which is part of a digital unit (not shown).

[0120] The antenna 34 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 34 may be coupled to the radio front-end circuitry in radio interface 30 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 34 is separate from the network node 16 and connectable to the network node 16 through one or more interfaces or ports.

[0121] Network node 15 can include one or more components described above with respect to network node 16, e.g., communication interface 29, radio interface 30, antenna 34, ports, processing circuitry 36, processor 38, memory 40 and software 42. These elements of network node 15 can be arranged such that network node 15 can perform various core network functions. Network node 15 can communicate wirelessly or via a wired connection with network nodes 16 via communication link 59.

[0122] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0123] Communication functions of the radio interface 46 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 according to one or more communication protocols and / or standards, such as IEEE 802.11, Code DivisionMultiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0124] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0125] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.

[0126] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the user equipment 22 may include implementation unit 26 which is configured to perform one or more UE 22 functions described herein, including functions related to WUS coverage adaptation.In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

[0127] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0128] Although FIGS. 1 and 2 show various “units” such as configuration unit 24 and implementation unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0129] FIG. 3 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 3 includes multiple access points (APs) 60 (with four example APs 60a, 60b, 60c, and 60d being depicted) and multiple wireless devices, referred to in the context of communication system 10 of FIG. 3 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 62b and STA 62c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served by AP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like, including UEs 22 that are shown and described with respect to FIGS. 1 and 2. In other words, in some embodiment, STA 62 is a UE 22. Further, stations 62 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0130] Each of STAs 62 may connect through a radio link to one of APs 60. For example, depending on location or channel conditions experienced by a given STA 62, the STAmay select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0131] Each AP 60 may provide data connectivity to STAs 62 connected to a particular AP 60. As illustrated, APs 60 may be connected to a data network 66. In this way, APs 60 may also provide data connectivity between STAs 62 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like.

[0132] Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 3 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62.

[0133] FIG. 4 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 configured to configure the UE 22 to operate a WUR by one or both of: causing the UE 22 to adjust a RSRP threshold associated with LP-WUS monitoring by using an offset value; and receiving, from the UE 22, a plurality of REFSENS levels and transmitting a REFSENS configuration to the UE22 in response to cause the UE22 to operate the WUR based on the REFSENS configuration (Block S100).

[0134] In some embodiments, network node 16 is further configured to receive REFSENS information from the UE indicating one or more REFSENS capabilities of the UE

[0135] In some embodiments, the REFSENS configuration is associated with one of a cell and a network deployment

[0136] FIG. 5 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more ofprocessing circuitry 50 (including the implementation unit 26), processor 52, and / or radio interface 46. User equipment 22 is configured to operate a WUR by one or both of adjusting a RSRP threshold associated with LP-WUS monitoring by using an offset value; and indicating, to the network node 16, a plurality of REFSENS levels, receiving a REFSENS configuration in response, and operating the WUR based on the REFSENS configuration.

[0137] In some embodiments, UE 22 is further configured to transmit REFSENS information to the network node 16 indicating one or more REFSENS capabilities of the UE 22.

[0138] In some embodiments, the REFSENS configuration is associated with one of a cell and a network deployment.

[0139] FIG. 6 is another flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. The network node 16 configured to configure (Block S104) the UE 22 to operate a WUR by one or both of causing the UE 22 to adjust a RSRP threshold associated with LP-WUS monitoring by using an offset value; and receiving, from the UE 22, a plurality of REFSENS levels, selecting a REFSENS configuration in response to receiving the plurality of REFSENS levels, and transmitting the REFSENS configuration to the UE 22 to cause the UE 22 to operate the WUR based on the REFSENS configuration.

[0140] In some embodiments, the network node 16 is further configured to receive REFSENS information indicating one or more REFSENS capabilities of the UE 22.

[0141] In some embodiments, the one or more REFSENS capabilities of the UE 22 comprise a capability corresponding to each of a plurality of energy saving levels.

[0142] In some embodiments, the network node 16 is further configured to receive an indication of a difference between a REFSENS performance capability of the UE 22 and a baseline REFSENS value.

[0143] In some embodiments, the offset value is one of a plurality of offset values, each of the plurality of offset value being associated with one or both of a radio resource control, RRC, state; and a frequency range.

[0144] In some embodiments, the REFSENS configuration is associated with one of a cell and a network deployment.In some embodiments, the network node 16 is further configured to indicate to the UE 22 whether the adjustment of the RSRP threshold of the LP-WUS monitoring is allowed.

[0145] In some embodiments, the indication comprises one or both of a maximum value and a minimum value the allowed adjustment of the RSRP threshold.

[0146] FIG. 7 is another flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the implementation unit 26), processor 52, and / or radio interface 46. UE 22 is configured to operate (Block SI 06) a WUR by one or both of: adjusting a RSRP threshold associated with LP-WUS monitoring by using an offset value; and indicating, to the network node 16, a plurality of REFSENS levels, receiving a REFSENS configuration in response to the indicating, and operating the WUR based on the REFSENS configuration.

[0147] In some embodiments, the UE 22 is further configured to transmit REFSENS information to the network node 16 indicating one or more REFSENS capabilities of the UE 22.

[0148] In some embodiments, the one or more REFSENS capabilities of the UE 22 comprise a capability corresponding to each of a plurality of energy saving levels.

[0149] In some embodiments, the UE 22 is further configured to indicate, to the network node 16, a difference between a REFSENS performance capability of the UE 22 and a baseline REFSENS value.

[0150] In some embodiments, the offset value is one of a plurality of offset values, each of the plurality of offset value being associated with one or both of: a radio resource control, RRC, state; and a frequency range.

[0151] In some embodiments, the offset value is one of a plurality of offset values, each of the plurality of offset value being mapped to one or more of: REFSENS, signal-to-noise ratio, SNR, decoding threshold, and noise figure.

[0152] In some embodiments, the offset value triggers one or both of starting and stopping the LP-WUS monitoring.

[0153] In some embodiments, the REFSENS configuration is associated with one of a cell and a network deployment.

[0154] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing theprocesses and functions of the disclosure, the sections below provide details and examples of arrangements for WUS coverage adaptation.

[0155] Example Embodiments for different RSRP thresholds

[0156] In at least one embodiment, the UE 22 may have capability to support a different REFSENS performance for the WUR as compared the baseline REFSENS for a certain type of WUR, e.g., either OOK WUR or OFDM WUR. As an example, UE 22 can report a delta dB (e.g., 3 dB or 6 dB) to represent a REFSENS performance improvement / degradation compared with the baseline REFSENS specified in RF specification. A UE 22 supporting this capability can be tested with new REFSENS based on the reported delta value. The reported value can be based on one of the designated parameters as listed below:

[0157] 1. Noise figure of a certain type of WUR, either OOK WUR or OFDM WUR

[0158] 2. Noise figure of certain type of OOK WUR implementation / architecture such as: a. Architecture with RF envelope detection

[0159] b. Heterodyne architecture with IF envelope detection

[0160] c. Homodyne / zero-IF architecture with baseband envelope detection RF envelope detector, zero-IF

[0161] d. Number of the receiver branches, e.g., 2 receiver or 1 receiver

[0162] 3. The design margin of the REFSENS required for a WUR hardware

[0163] 4. The SNR decoding difference between a baseline SNR and implementation specific SNR

[0164] UE supporting the new capability can have an offset compensation on the RSRP threshold of LP-WUS signal configured for exist condition of LP-WUS monitoring:

[0165] RSRP new = RSRP configured + Offset

[0166] Examples of Offset values are: {2, 3, 6, 8,9,10, 12} dB.

[0167] In some embodiments, for a UE 22, multiple offset values are used for RSRP threshold adjustments. This allows RSRP adjustment for different implementations of a UE 22 (e.g., UE 22 may activate / inactivate certain components which affects the overall noise figure):

[0168] • RSRP newl = RSRP configured + Offsetl

[0169] • RSRP_new2 = RSRP configured + Offset2

[0170] In at least one embodiment, the offset can be associated with radio resource control (RRC) states, e.g., different offset for different RRC states, e.g., offset 1 for RRC idle, offset 2 for RRC inactive and offset 3 for RRC connected.In some embodiments, different offset values are used for FR1 and FR2. For example, Offset frl and Offset_fr2 are used for FR1 and FR2 frequency ranges, respectively.

[0171] In at least one embodiment, the offset value to apply as compensation value to RSRP can be defined as below. The scenario comprises of at least two UEs 22, a first UE (UE1) and a second UE (UE2), served by cell 1 which is managed or served by network node #1 (e.g., a network node 16). UE1 and UE2 may have WUR with different performance critical parameters, e.g., REFSENS, signal-to-noise ratio (SNR) decoding threshold, and / or NF. Below the NF is used as an example, but can be replaced by any performance critical parameters mentioned above, e.g., UE1 and UE2 support WUR NF1 and WUR NF2 respectively.

[0172] NN1 (Network node #1) (e.g., network node 16) determines the signal strength threshold (S) based on a relation or mapping between NFs and one or more thresholds. The relation or mapping can be pre-defined or configured by NN1 (e.g., network node 16). This is explained with several examples below:

[0173] 1. A general example of the relation between n number of NFs and corresponding WUR thresholds is shown in Table 1. Each threshold value (e.g. SI, S2,.. ,,Sn) may belong to a range of values.

[0174] In an example, value range for all thresholds may be the same. In another example, value range for all thresholds may be different. In another example, value range for subset of thresholds may be the same and different for the remaining ones.

[0175] According to an embodiment implemented in NN1 (e.g., network node 16), NN1 obtains information about the WUR NF types in at least two UEs 22 (UE1 and UE2) served by cell 1. If different NFs are reported by UE1 and UE2, then based on the obtained NF information NN1 further determines at least two signal strength thresholds (e.g. SI and S2) and transmits information about the determined values of S (e.g. SI and S2) to the at least UEs (e.g. UE1 and UE2).

[0176] S may be pre-defined or configured by the network node 16. Each value of S may further depend on one or more of: cell size, type of noise figures for which the UE 22 uses WUR, UE physical or geographical location in cell 1 etc. The UE 22 uses the S for performing one or more radio operations, e.g., for entering / exiting of the monitoring the LP-WUS signal using WUR etc.The values of S (e.g. SI and S2) may be transmitted to the UE 22 in a broadcast message or individually to each UE 22 in a UE-specific (e.g., dedicated) message via DCI, MAC-CE or RRC signaling.

[0177] Table 1: A general example of relation between UE noise figures and signal strength threshold

[0178]

[0179] 2. Another example of the relation between n different noise figures and corresponding thresholds is shown in Table 2. In this example, SO and SI, ... Sn are related by one or combination of functions. Examples of function are sum, maximum, minimum, product, x-th percentile, etc. For example, NN1 (e.g., network node 16) may configure the UE 22: with SO when the UE is configured with noise figurel, and with SI and Dg when the UE 22 is configured with noise figure2. In the latter case the UE 22 may derive SI based on a function relating SI and SO e.g. S l=f(S 1 , Ds). In one example Sl= S0+ Ds. In another example S1=SO- Ds. In this case, the UE 22 may always be configured with SO to facilitate derivation of SI from SO and Ds when UE 22 uses NF2.

[0180] a. Ds could for example be based on the difference in inaccuracy between the WUR noise figures. Assuming the same measurement samples, higher NF are subject to more bias (e.g. ±6.5 dB error) compared to measurements done using lower NF (e.g. ±4.5 dB error), Ds to be applied could e.g. be hardcoded to be 2 dB in this case. Therefore, the following derivation would be used: SI = SO ± 2dB.

[0181] b. Ds could for example be based on both the inaccuracy of measurement for each WUR noise figure (e.g. 2 dB bias) and the measurement strength difference, such as 3dB. Therefore, the following derivation would be used: Sl = S0 ± 5dB.

[0182] In some embodiments NN1 (e.g., network node 16) obtains information about the WUR NF types in at least two UEs 22 (UE1 and UE2) served by cell 1. If different NF s are reported by UE1 and UE2, then based on the obtained NF information a signal strength threshold is determined (e.g., by the network node 16) with Ds table (e.g. SI and S2) andinformation about the determined values of S (e.g. SI) is transmitted (e.g., by the network node 16) to the UEs 22 (e.g. UE1 and UE2).

[0183] The values of S may be transmitted to the UE 22 in a broadcast message or individually to each UE 22 in a UE-specific (e.g. dedicated) message via downlink control information (DCI), medium access control control element (MAC-CE) or RRC signaling.

[0184] The values of Ds may be predefined in the specification or broadcast message or individually to each UE 22 in a UE-specific (e.g. dedicated) message via DCI, MAC-CE or RRC signaling or reported by the UE 22 via UE assistance information (UAI), capability etc.

[0185] Table 2: A specific example of relation between two UE receiver type and signal strength threshold

[0186]

[0187] In at least one embodiment, a UE 22 may be capable of several REFSENS levels that correspond to different energy saving states. The network (e.g., via network node 16) may configure a REFSENS level and then an RSRP threshold related to the REFSENS level.

[0188] In at least one embodiment, a UE 22 may be capable of several REFSENS levels that correspond to different energy saving states. Each REFSENS level may be suitable for a particular cell type. For example, one REFSENS level may be suitable for small, indoor cells where coverage is not critical, and energy saving can be targeted. A second REFSENS level may be suitable for, e.g., a hotspot cell, where somewhat larger coverage is needed than a small indoor cell, but less than a wide cell. A third REFSENS level may be suitable for large, outdoor cells. Each REFSENS level may be associated with a different amount of energy saving. On receiving the UE 22 capability report, the network (e.g., network node 16) may configure a REFSENS level that is suitable for the type of cell that the UE 22 is in. For example, if the UE 22 is in an indoor cell, the least sensitive REFSELS level may be configured, that enables maximum energy saving. In this embodiment, the network may not configure an RSRP threshold for the individual UE 22,but rather configures a UE REFSENS level that is suitable for the type of cell and associated RSRP range.

[0189] Example embodiments at network to configure WUS coverage considering the UE capability report

[0190] UE 22 reports the capability to support a better or worse performance critical parameter, e.g., REFSENS or noise figure. Such reporting could be a value representing an increased or decreased LP-WUS coverage compared to a UE 22 that does not support such capability. At the same time, network (e.g., network node 16) could set a different RSRP threshold for the serving cell coverage of main receiver. The coverage difference between LP-WUS and normal signal could be represent by a power level difference between the minimum required RX level of NR cell reference signal (e.g., synchronization signal block (SSB)) in the serving cell and the min required receiving (Rx) level of LP-WUS in the same cell.

[0191] In at least one embodiment, network (e.g., network node 16) signals to the UE 22 with the min and / or max of the allowed compensation of the RSRP threshold set for the entry / exit condition of the LP-WUS monitoring. This may ensure that the WUR with configured max compensation of the RSRP will not be moved outside of the main receiver coverage.

[0192] In at least one embodiment, network (e.g., network node 16) signals to the UE 22 as to whether the additional compensation on the RSRP threshold for entry / exit condition of LP-WUS monitoring is allowed. This could be corresponding to a case a small cell is deployed.

[0193] Example Embodiments:

[0194] Example Al . A method implemented in UE 22 that is configured to communicate with a network node 16, the method comprising: operating a wake up radio, WUR, by one or both of: adjusting a RSRP threshold associated with low-power wake up signal, LP-WUS, monitoring by using an offset value; and indicating, to the network node 16, a plurality of reference sensitivity, REFSENS, levels, receiving a REFSENS configuration in response, and operating the WUR based on the REFSENS configuration.

[0195] Example A2. The method of Example Al, further comprising transmitting REFSENS information to the network node indicating one or more REFSENS capabilities oftheUE 22.

[0196] Example A3. The method of Example Al, wherein the REFSENS configuration is associated with one of a cell and a network deployment.Example Bl. A UE 22 configured to communicate with a network node 16, the UE 22 configured to, and / or comprising a radio interface and / or processing circuitry configured to: operate a wake up radio, WUR, by one or both of adjusting a RSRP threshold associated with low-power wake up signal, LP-WUS, monitoring by using an offset value; and indicating, to the network node 16, a plurality of reference sensitivity, REFSENS, levels, receiving a REFSENS configuration in response, and operating the WUR based on the REFSENS configuration.

[0197] Example B2. The UE 22 of Example Bl, further configured to transmit REFSENS information to the network node indicating one or more REFSENS capabilities oftheUE 22.

[0198] Example B3. The UE 22 of Example Bl, wherein the REFSENS configuration is associated with one of a cell and a network deployment.

[0199] Example Cl . A method implemented in a network node 16 that is configured to communicate with a UE 22, the method comprising: configuring the UE 22 to operate a wake up radio, WUR, by one or both of: causing the UE 22 to adjust a RSRP threshold associated with low-power wake up signal, LP-WUS, monitoring by using an offset value; and receiving, from the UE 22, a plurality of reference sensitivity, REFSENS, levels, and transmitting a REFSENS configuration to the UE 22 in response to cause the UE 22 to operate the WUR based on the REFSENS configuration.

[0200] Example C2. The method of Example Cl, further comprising receiving REFSENS information from the UE 22 indicating one or more REFSENS capabilities of the UE 22.

[0201] Example C3. The method of Example Cl, wherein the REFSENS configuration is associated with one of a cell and a network deployment

[0202] Example DI . A network node 16 configured to communicate with a UE 22, the network node 16 configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: configure the UE 22 to operate a wake up radio, WUR, by one or both of: causing the UE 22 to adjust a RSRP threshold associated with low-power wake up signal, LP-WUS, monitoring by using an offset value; and receiving, from the UE 22, a plurality of reference sensitivity, REFSENS, levels, and transmitting a REFSENS configuration to the UE 22 in response to cause the UE to operate the WUR based on the REFSENS configuration.Example D2. The network node 16 of Example DI, further configured to receive REFSENS information from the UE 22 indicating one or more REFSENS capabilities of the UE 22.

[0203] Example D3. The network node 16 of Example DI, wherein the REFSENS configuration is associated with one of a cell and a network deployment.

[0204] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0205] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0206] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructionmeans which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0207] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0208] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0209] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0210] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process ofmaking and using them, and shall support claims to any such combination or subcombination.

[0211] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings and in view of the following claims.

Claims

What is claimed is:

1. A method implemented in a user equipment, UE, (22) that is configured to communicate with a network node (16), the method comprising:operating (SI 06) a wake up radio, WUR, by one or both of:adjusting a RSRP threshold associated with low-power wake up signal, LP-WUS, monitoring by using an offset value; andindicating, to the network node (16), a plurality of reference sensitivity, REFSENS, levels, receiving a REFSENS configuration in response to the indicating, and operating the WUR based on the REFSENS configuration.

2. The method of Claim 1, further comprising transmitting REFSENS information to the network node (16) indicating one or more REFSENS capabilities of the UE (22).

3. The method of Claim 2, wherein the one or more REFSENS capabilities of the UE (22) comprise a capability corresponding to each of a plurality of energy saving levels.

4. The method of any of Claims 1-3, further comprising indicating, to the network node (16), a difference between a REFSENS performance capability of the UE (22) and a baseline REFSENS value.

5. The method of any of Claims 1-4, wherein the offset value is one of a plurality of offset values, each of the plurality of offset value being associated with one or both of: a radio resource control, RRC, state; and a frequency range.

6. The method of any of Claims 1-5, wherein the offset value is one of a plurality of offset values, each of the plurality of offset value being mapped to one or more of: REFSENS, signal -to-noise ratio, SNR, decoding threshold, and noise figure.

7. The method of any of Claims 1-6, wherein the offset value triggers one or both of starting and stopping the LP-WUS monitoring.

8. The method of any of Claims 1-7, wherein the REFSENS configuration is associated with one of a cell and a network deployment.

9. A user equipment, UE, (22) in communication with a network node (16), the UE (22) comprising processing circuitry (50) configured to:operate a wake up radio, WUR, by one or both of:adjusting a RSRP threshold associated with low-power wake up signal, LP-WUS, monitoring by using an offset value; andindicating, to the network node (16), a plurality of reference sensitivity, REFSENS, levels, receiving a REFSENS configuration in response to the indicating, and operating the WUR based on the REFSENS configuration.

10. The UE (22) of Claim 9, wherein the processing circuitry (50) is further configured to transmit REFSENS information to the network node (16) indicating one or more REFSENS capabilities of the UE (22).

11. The UE (22) of Claim 10, wherein the one or more REFSENS capabilities of the UE (22) comprise a capability corresponding to each of a plurality of energy saving levels.

12. The UE (22) of any of Claims 9-11, wherein the processing circuitry (50) is further configured to indicate, to the network node (16), a difference between a REFSENS performance capability of the UE (22) and a baseline REFSENS value.

13. The UE (22) of any of Claims 9-12, wherein the offset value is one of a plurality of offset values, each of the plurality of offset value being associated with one or both of: a radio resource control, RRC, state; and a frequency range.

14. The UE (22) of any of Claims 9-13, wherein the offset value is one of a plurality of offset values, each of the plurality of offset value being mapped to one or more of: REFSENS, signal -to-noise ratio, SNR, decoding threshold, and noise figure.

15. The UE (22) of any of Claims 9-14, wherein the offset value triggers one or both of starting and stopping the LP-WUS monitoring.

16. The UE (22) of any of Claims 9-15, wherein the REFSENS configuration is associated with one of a cell and a network deployment.

17. A method implemented in a network node (16) that is configured to communicate with a user equipment, UE, (22), the method comprising:configuring (SI 04) the UE (22) to operate a wake up radio, WUR, by one or both of:causing the UE (22) to adjust a RSRP threshold associated with low-power wake up signal, LP-WUS, monitoring by using an offset value; andreceiving, from the UE (22), a plurality of reference sensitivity, REFSENS, levels, selecting a REFSENS configuration in response to receiving the plurality of REFSENS levels, and transmitting the REFSENS configuration to the UE (22) to cause the UE (22) to operate the WUR based on the REFSENS configuration.

18. The method of Claim 17, further comprising receiving REFSENS information indicating one or more REFSENS capabilities of the UE (22).

19. The method of Claim 18, wherein the one or more REFSENS capabilities of the UE (22) comprise a capability corresponding to each of a plurality of energy saving levels.

20. The method of any of Claims 17-19, further comprising receiving an indication of a difference between a REFSENS performance capability of the UE (22) and a baseline REFSENS value.

21. The method of any of Claims 17-20, wherein the offset value is one of a plurality of offset values, each of the plurality of offset value being associated with one or both of: a radio resource control, RRC, state; and a frequency range.

22. The method of any of Claims 17-21, wherein the REFSENS configuration is associated with one of a cell and a network deployment.

23. The method of any of Claims 17-22, further comprising indicating to the UE whether the adjustment of the RSRP threshold of the LP-WUS monitoring is allowed.

24. The method of Claim 23, wherein the indication comprises one or both of a maximum value and a minimum value the allowed adjustment of the RSRP threshold.

25. A network node (16) in communicating with a user equipment, UE, (22), the network node (16) comprising processing circuitry (36) configured to:configure the UE (22) to operate a wake up radio, WUR, by one or both of:causing the UE (22) to adjust a RSRP threshold associated with low-power wake up signal, LP-WUS, monitoring by using an offset value; andreceiving, from the UE (22), a plurality of reference sensitivity, REF SENS, levels, selecting a REFSENS configuration in response to receiving the plurality of REFSENS levels, and transmitting the REFSENS configuration to the UE (22) to cause the UE (22) to operate the WUR based on the REFSENS configuration.

26. The network node (16) of Claim 25, wherein the processing circuitry (36) is further configured to receive REFSENS information indicating one or more REFSENS capabilities of the UE (22).

27. The network node (16) of Claim 26, wherein the one or more REFSENS capabilities of the UE (22) comprise a capability corresponding to each of a plurality of energy saving levels.

28. The network node (16) of any of Claims 25-27, wherein the processing circuitry (36) is further configured to receive an indication of a difference between a REFSENS performance capability of the UE (22) and a baseline REFSENS value.

29. The network node (16) of any of Claims 25-28, wherein the offset value is one of a plurality of offset values, each of the plurality of offset value being associated with one or both of: a radio resource control, RRC, state; and a frequency range.

30. The network node (16) of any of Claims 25-29, wherein the REFSENS configuration is associated with one of a cell and a network deployment.

31. The network node (16) of any of Claims 25-30, wherein the processing circuitry (36) is further configured to indicate to the UE whether the adjustment of the RSRP threshold of the LP-WUS monitoring is allowed.

32. The network node (16) of Claim 31, wherein the indication comprises one or both of a maximum value and a minimum value the allowed adjustment of the RSRP threshold.

Images