Method for enhancing energy consumption of ues using LP-WUS in RRC_inactive

Abstract

Method for enhancing energy consumption of UEs using LP-WUS in RRC_INACTIVE in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein the Network determines UE- specific LP-WUS configuration.

Description

[0001] TITLE

[0002] Method for enhancing energy consumption of UEs using LP-WUS in RRCJNACTIVE

[0003] TECHNNICAL FIELD

[0004] The present disclosure relates to wireless communication systems and relates more specifically to methods and devices for saving energy on a user equipment, UE side of the wireless communication system.

[0005] Background

[0006] This application is related to the 3GPP Rel. 18 'A study on low-power wake-up signal and receiver for NR (SI)" topic.

[0007] 3GPP has introduced a WuS (Wake-up Signal) mechanism to improve energy efficiency of the UE (User Equipment). The UE will stay in sleep mode and switches off the main radio (MR), until a WuS signal is detected at the secondary radio (WuS receiver). Once the WuS receiver detects a WuS signal, the main radio (MR) is triggered to switch on.

[0008] Here the LPWuS receiver is a low complexity and low power consuming component of a UE, whereas the main radio (MR) is high energy consuming component of the UE. The main radio (MR) is switched off (sleep mode) as much as possible to reduce the energy consumption at the UE.

[0009] To reduce energy consumption, extended discontinuous reception, eDRX, has been introduced in 3GPP (Third Generation Partnership Project) wireless communication systems. Basically, in eDRX, the UE periodically goes to sleep mode for an asleep duration during which a physical downlink control channel, PDCCH, is not monitored before waking up for an awake duration to monitor the PDCCH for possible downlink data. The amount of energy that can be saved depends on how long and how often the UE remains asleep. Of course, the longer the UE remains asleep, the greater the amount of energy saved. However, increasing the asleep duration comes with increased latency, which makes eDRX not suitable for latency-critical use cases or applications.

[0010] 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 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.

[0011] 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.

[0012] 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 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, long eDRX cycle cannot meet the delay requirements. eDRX is apparently not suitable for latency-critical use cases. Thus, the intention is to study ultra-low power mechanism that can support low latency in Rel-18, e.g. lower than eDRX latency.

[0013] Currently, UEs need to periodically wake up once per DRX cycle, which dominates the power consumption in periods with no signaling 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 (MR) and a separate receiver which has the ability to monitor wake-up signal with ultra-low power consumption. Main radio (MR) works for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on.

[0014] 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.

[0015] The study primarily targeted low-power WUS / WUR for power-sensitive, small formfactor devices including loT use cases (such as industrial sensors, controllers) and wearables. Other use cases are not precluded, e.g., XR / smart glasses, smart phones.

[0016] US 2020367168 A1 relates to a method by which a terminal transmits / receives a signal in a wireless communication system and a device therefore and, more particularly, to: a method comprising the steps of receiving configuration information related to the activation or the deactivation of a wake-up signal (WUS), and monitoring the WUS and a channel corresponding to the WUS, when the WUS is activated on the basis of the configuration information, wherein the configuration information related to the activation or the deactivation of the WUS is configured to be terminal-specific; and a device therefor.

[0017] US 2021400584 A1 discloses a user equipment (UE) operable for wake-up signal (WUS) communication in a fifth generation (5G) new radio (NR) network. The UE can be configured to: identify a resource set for a WUS with a repetition level, wherein: the resource set for the WUS includes a mapping of the WUS that associates the WUS with one or more physical resource blocks and one or more orthogonal frequency division multiplexing (OFDM) symbols, and the repetition level identifies a number of base sequences for the WUS in the resource set; and switch to a network access mode (NAM) from a power saving mode (PSM) based on a detection of the WUS in the resource set. WO 2023087163 A1 discloses systems and methods for operating in a low-power state. A wireless communication device may enter a first low-power operating state to monitor for a defined signal. The wireless communication device may monitor for the defined signal, while in the first low-power operating state.

[0018] Fig. 1 depicts UE RRC States. In both RRCJDLE and RRCJNACTIVE, UE performs measurements of neighboring cells and can perform cell re-selection. In RRC_CONNECTED, UE mobility is controlled by the network and handovers can be initiated. In RRCJDLE, UE paging is initiated by the CN. In RRCJNACTIVE, UE paging is initiated by NG-RAN. To page a UE, it's location must be known. In RRCJDLE, this is the Tracking Area (RA). In RRCJNACTIVE, this is the RAN-based Notification Area (RNA) and UE may initiate RNA updates. The UE performs a RAN- based notification area update (RNAU) periodically or when the UE selects a cell that does not belong to the configured RNA. If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it. If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is performed. In RRCJNACTIVE state, if the new cell does not belong to the configured RNA, an RNA update procedure is performed. Fig. 2 shows SDT procedure and Fig. 3 shows the subsequent transmissions of SDT.

[0019] UEs in RRCJNACTIVE may temporarily measure LP-WUS reference signal below threshold, e.g., due to temporary blockage or poor receive conditions. As a consequence, the UE will activate its main radio (MR) unnecessarily or too early and waste energy.

[0020] Technical Tasks

[0021] This application gives a solution to the cited problem as the UEs in RRCJNACTIVE may temporarily measure LP-WUS reference signal below threshold, e.g., due to temporary blockage or poor receive conditions.

[0022] Technical Solutions

[0023] Network determines UE-specific LP-WUS configuration, e.g., based on UE’s QoS profile. The UE-specific configuration is provided via RRC release message (sent by gNB for transferring UE into RRCJNACTIVE mode). The LP-WUS configuration includes UE-specific measurement counter limit and timer value. Alternatively, an additional measurement offset is configured for prioritizing certain UEs. UEs with low offset will earlier activate MR. Potentially, there are higher energy savings for UEs with configured measurement offset. Further, measurement offsets result in delay. Thus, UEs with delay-sensitive services may be configured with lower offset values. When in RRCJNACTIVE mode, the UE applies the provided LP-WuS configuration and measures LP-WUS reference signal.

[0024] If the measured LP-WUS reference signal is below a configured threshold, measurement counter will be increased, and the UE-specific timer will be started.

[0025] If the measurement counter reaches the configured measurement counter limit, the UE activates its MR and resets its timer.

[0026] If the timer expires, the UE activates its MR and resets its timer.

[0027] If the measurement counter has not reached the configured measurement counter limit yet, the UE keeps on measuring the LP-WuS reference signal (and, if configured, applies an additional measurement offset).

[0028] Furthermore, there is a further approach while the UE moves in RRCJNACTIVE, it may leave its original RNA. When detecting a new RNA (e.g., decoding SIB of new gNB), UE performs RNA update procedure.

[0029] UE receives the updated LP-WUS configuration information from the network during the RNA update procedure e.g., RNA update procedure response message. While in RRCJNACTIVE, the UE may perform RA-SDT or CG-SDT procedure.

[0030] The network can provide an updated LP-WUS configuration via another RRC release message.

[0031] The beneficial result of both approaches, which can be combined, too, is the increased energy savings for UE in RRCJNACTIVE mode when using LP-WUS feature, thus, extended battery lifetime and improved mobility support in RRCJNACTIVE. The cited problem is solved by the described and proposed embodiments.

[0032] The present disclosure solves the cited problem by the proposed embodiments and describes a method for enhancing energy consumption of UEs using LP-WUS in RRCJNACTIVE in a wireless communication system, wherein the Network determines UE-specific LP-WUS configuration.

[0033] In some embodiments of the method according to the first aspect, the method is characterized by, that the UE-specific configuration is based on UE’s QoS profile.

[0034] For example, the network is aware of which services were used and / or requested by a UE and can classify UEs according to their service usage and determine a corresponding QoS profile, e.g., differentiating between UEs with respect to usage of delay-sensitive vs. delay-tolerant services.

[0035] In some embodiments of the method according to the first aspect, the method is characterized by, that that the UE-specific configuration is provided via RRC release message sent by gNB for transferring UE into RRCJNACTIVE mode.

[0036] In some embodiments of the method according to the first aspect, the method is characterized by, that the LP-WUS configuration includes UE-specific measurement counter limit and timer value.

[0037] In some embodiments of the method according to the first aspect, the method is characterized by, that an additional measurement offset is configured for prioritizing certain UEs.

[0038] In some embodiments of the method according to the first aspect, the method is characterized by, that when in RRCJNACTIVE mode, the UE applies the provided LP-WuS configuration and measures LP-WUS reference signal.

[0039] In some embodiments of the method according to the first aspect, the method is characterized by, if the measured LP-WUS reference signal is below a configured threshold, the measurement counter will be increased and the UE-specific timer will be started.

[0040] In some embodiments of the method according to the first aspect, the method is characterized by, if the measurement counter reaches the configured measurement counter limit, the UE activates its MR and resets its timer.

[0041] In some embodiments of the method according to the first aspect, the method is characterized by, that if the timer expires, the UE activates its MR and resets its timer.

[0042] In some embodiments of the method according to the first aspect, the method is characterized by, that if the measurement counter has not reached the configured measurement counter limit yet, the UE keeps on measuring the LP-WuS reference signal and, if configured, applies an additional measurement offset.

[0043] In some embodiments of the method according to the first aspect, the method is characterized by, that the method being implemented by a wireless device of the wireless communication system, while the UE moves in RRCJNACTIVE, it leaves its original RNA and when detecting a new RNA, e.g., decoding the SIB of the new gNB, UE performs RNA update procedure.

[0044] In some embodiments of the method according to the first aspect, the method is characterized by, that UE receives the updated LP-WUS configuration information from the network during the RNA update procedure (e.g., RNA update procedure response message).

[0045] In some embodiments of the method according to the first aspect, the method is characterized by, that while in RRCJNACTIVE, the UE performs RA-SDT or CG- SDT procedure.

[0046] In some embodiments of the method according to the first aspect, the method is characterized by, that network provides an updated LP-WUS configuration via another RRC release message. According to a second aspect, the present disclosure relates to a wireless device comprising at least one memory and at least one processor configured to carry out a method according to the first aspect of this application.

[0047] According to a third aspect, the present disclosure relates to a UE, comprising a wireless device according to the second aspect of this application.

[0048] According to a fourth aspect, the present disclosure relates to base station (BS), the base station (BS) comprising at least one memory and at least one processor configured to carry out a method according the first aspect of this application.

[0049] According to a fifth aspect, the present disclosure relates to a wireless communication system comprising at least one base station according the fourth aspect and at least one user equipment according to the third aspect of this application.

[0050] According to a sixth aspect, the present disclosure relates to a computer program product comprising instructions which, when executed by at least one processor, configure said at least one processor to carry out a method according to the first aspect of this application.

[0051] According to the seventh aspect, the present disclosure relates to a computer- readable storage medium comprising instructions which, when executed by at least one processor, configure said at least one processor to carry out a method according to the fist aspect of this application.

[0052] BRIEF DESCRIPTION OF THE FIGURES

[0053] Fig. 1 shows the UE RRC States

[0054] Fig. 2 shows different types of SDT

[0055] Fig. 3 shows subsequent transmission(s) of SDT

[0056] Fig. 4 shows the UE flow chart for the first embodiment

[0057] Fig. 5 shows the gNB flow chart for the first embodiment

[0058] Fig. 6 shows the UE flow chart for the second embodiment Fig. 7 shows the gNB flow chart for the second embodiment

[0059] DETAILED DESCRIPTION

[0060] The detailed description set forth below, with reference to annexed drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In particular, although terminology from 3GPP 5G NR may be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the invention.

[0061] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0062] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0063] In some embodiments, a more general term “network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and / or with another network node. Examples of network nodes are NodeB, MeNB, eNB, a network node belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc), Operations & Maintenance (O&M), Operations Support System (OSS), Self Optimized Network (SON), positioning node (e.g. Evolved- Serving Mobile Location Centre (E-SMLC)), Minimization of Drive Tests (MDT), test equipment (physical node or software), etc.

[0064] In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used and may refer 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, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.

[0065] Additionally, terminologies such as base station / gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general, “gNodeB” could be considered as device 1 and “UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNodeB (gNB), or UE. As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.

[0066] For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off- the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.

[0067] Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and / or program code, referred hereafter as code. The storage devices may be tangible, non- transitory, and / or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0068] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0069] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0070] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and / or machine languages such as assembly languages. The 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 or server. In the latter scenario, the remote computer may be connected to the user’s computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), 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 (“ISP”)).

[0071] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment. Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0072] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and / or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and / or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-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 diagrams and / or block diagrams.

[0073] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function / act specified in the flowchart diagrams and / or block diagrams.

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

[0075] The flowchart diagrams and / or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0076] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. 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 involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0077] Although various arrow types and line types may be employed in the flowchart and / or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0078] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements. Used abbreviations besides the one cited in the appendix are: LPWuS: Low Power Wake-up Signal

[0079] RSRP: Reference Signal Received Power

[0080] RSRQ: Reference Signal Received Quality DRX: Discontinuous Reception.

[0081] The Fig. 1 , Fig. 2 and Fig. 3 have been described in the introduction of this application.

[0082] Fig. 4 shows the UE flow chart for the first embodiment. The UE checks, if it moves to RRCJNACTIVE. If this is the case, the UE receives LP-WUS configuration through dedicated signaling message, e.g., RRC release message, and checks if RNA update procedure is triggered. If this is the case, the UE receives updated LPWUS configuration through dedicated signaling message.

[0083] Fig. 5 shows the gNB flow chart for the first embodiment, here the gNB determines, if the UE should move to RRCJNACTIVE. If this is the case, the gNB provides LPWUS configuration in RRC release message, and checks if the RNA update procedure is triggered. If this is the case, the gNB provides a potentially updated LPWUS configuration in another RRC release message.

[0084] Fig. 6 shows the UE flow chart for the second embodiment. The UE checks, if it moves to RRCJNACTIVE. If this is the case, the UE receives LP-WUS configuration through dedicated signaling message and checks, if RA-SDT / CG-SDT procedure is triggered. If this is the case, it receives updated LP-WUS configuration through another dedicated signaling message.

[0085] Fig. 7 shows the gNB flow chart for the second embodiment. Here the gNB determines, if the UE should move to RRCJNACTIVE. If this is the case, it provides LP-WUS configuration in RRC release message and checks, if RA-SDT / CG-SDT procedure is triggered. If this is the case gNB provides a potentially updated LP-WUS configuration in RRC release message. Abbreviations

[0086] BWP Bandwidth part

[0087] CBG Code block group

[0088] CLI Cross Link Interference

[0089] CP Cyclic prefix

[0090] CPU CSI processing unit

[0091] CQI Channel quality indicator

[0092] CRB Common resource block

[0093] CRC Cyclic redundancy check

[0094] CRI CSI-RS Resource Indicator

[0095] CSI Channel state information

[0096] CSI-RS Channel state information reference signal

[0097] CSI-RSRP CSI reference signal received power

[0098] CSI-RSRQ CSI reference signal received quality

[0099] CSI-SINR CSI signal-to-noise and interference ratio

[0100] CW Codeword

[0101] DCI Downlink control information

[0102] DL Downlink

[0103] DM-RS Demodulation reference signals

[0104] DRX Discontinuous Reception

[0105] EPRE Energy per resource element

[0106] IAB-MT Integrated Access and Backhaul - Mobile Terminal

[0107] L1-RSRP Layer 1 reference signal received power

[0108] LI Layer Indicator

[0109] LP-WUR Low power wake up receiver

[0110] LP-WUS Low power wake up signal MCS Modulation and coding scheme MR Main radio

[0111] PDCCH Physical Downlink Control Channel

[0112] PDCCH Physical downlink control channel

[0113] PDSCH Physical downlink shared channel

[0114] PMI Precoding Matrix Indicator PRB Physical resource block PRG Precoding resource block group PRS Positioning reference signal PSS Primary Synchronisation signal PT-RS Phase-tracking reference signal PUCCH Physical uplink control channel QCL Quasi co-location RB Resource block RBG Resource block group Rl Rank Indicator RIV Resource indicator value RS Reference signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality

[0115] SCI Sidelink control information SLIV Start and length indicator value SR Scheduling Request SRS Sounding reference signal SS Synchronisation signal SS-RSRP SS reference signal received power SS-RSRQ SS reference signal received quality SSS Secondary Synchronisation signal SS-SINR SS signal-to-noise and interference ratio TB Transport Block TCI Transmission Configuration Indicator TDM Time division multiplexing UE User equipment UL Uplink

Claims

Claims1. Method for enhancing energy consumption of UEs using LP-WUS in RRCJNACTIVE in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein the Network determines UE-specific LP-WUS configuration.

2. The method according to claim 1 , comprising that the UE-specific configuration is based on UE’s QoS profile.

3. The method according to claim 1 or 2, comprising that the UE-specific configuration is provided via RRC release message sent by gNB for transferring UE into RRCJNACTIVE mode.

4. The method according to claim 1 to 3, comprising that the LP-WUS configuration includes UE-specific measurement counter limit and timer value.

5. The method according to claim 1 to 4, an additional measurement offset is configured for prioritizing certain UEs.

6. Method according to any of the preceding claims, wherein when in RRCJNACTIVE mode, the UE applies the provided LP-WuS configuration and measures LP-WUS reference signal.

7. Method according to any of the preceding claims, wherein if the measured LP- WUS reference signal is below a configured threshold, measurement counter will be increased and the UE-specific timer will be started.

8. Method according to any of the preceding claims, wherein if the measurement counter reaches the configured measurement counter limit, the UE activates its MR and resets its timer.

9. Method according to any of the preceding claims, wherein if the timer expires, the UE activates its MR and resets its timer.

10. Method according to any of the preceding claims, wherein if the measurement counter has not reached the configured measurement counter limit yet, the UE keeps on measuring the LP-WuS reference signal and, if configured, applies an additional measurement offset.

11. Method for enhancing energy consumption of UEs using LP-WUS in RRCJNACTIVE in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, while the UE moves in RRCJNACTIVE, it leaves its original RNA and when detecting a new RNA, UE performs RNA update procedure.

12. Method according to claim 11 , wherein UE receives the updated LP-WUS configuration information from the network during the RNA update procedure (e.g., RNA update procedure response message).

13. Method according to claims 11 to 12, wherein while in RRCJNACTIVE, the UE may perform RA-SDT or CG-SDT procedure.

14. Method according to claims 11 to 13, wherein network can provide an updated LP-WUS configuration via another RRC release message.

15. Wireless device comprising at least one memory and at least one processor configured to carry out a method according to any one of the preceding claims.

16. User equipment, UE, comprising a wireless device according to claim 15.

17. Base station, BS comprising at least one memory and at least one processor configured to carry out a method according to any one of claim 1 to 14.

18. Wireless communication system comprising at least one base station according to claim 17 and at least one user equipment according to claim 16.

19. Computer program product comprising instructions which, when executed by at least one processor, configure said at least one processor to carry out a methodaccording to any one of claims 1 to 14.

20. Computer-readable storage medium comprising instructions which, when executed by at least one processor, configure said at least one processor to carry out a method according to any one of claims 1 to 14.

Images