Method for improving energy efficiency of UE by using LP-WUS under RRCINACTIVE

Abstract

A method for improving the energy efficiency of a UE using LP-WUS under RRCINACTIVE in a wireless communication system is implemented by a wireless device of the wireless communication system in which a network determines a UE-specific LP-WUS configuration.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically to methods and apparatus for saving energy on the user equipment (UE) side of a wireless communication system. Background Technology

[0002] This application relates to the topic of 3GPP Rel. 18 “Study on low-power wake-up signals and receivers for NR (SI)”.

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

[0004] Here, the LPWuS receiver is a low-complexity and low-power component of the UE, while the main radio (MR) is a high-power component of the UE. The main radio (MR) is turned off as much as possible (sleep mode) to reduce power consumption at the UE.

[0005] To reduce energy consumption, Extended Discontinuous Reception (eDRX) has been introduced in 3GPP (3rd Generation Partnership Project) wireless communication systems. Essentially, under eDRX, the UE periodically enters a sleep mode and remains asleep for a specified duration, during which time it does not monitor the Physical Downlink Control Channel (PDCCH). It then wakes up and remains awake for a specified duration to monitor the PDCCH to obtain possible downlink data. The amount of energy saved depends on the duration and frequency of the UE's sleep state. Naturally, the longer the UE remains asleep, the greater the energy savings. However, increased sleep duration is accompanied by increased latency, making eDRX unsuitable for latency-critical use cases or applications.

[0006] 5G systems are designed and developed for both mobile phones and vertical industry use cases. Besides latency, reliability, and availability, UE energy efficiency is also crucial for 5G. Currently, 5G devices may need to be recharged weekly or daily, depending on individual usage time. Generally, 5G devices consume tens of milliwatts in RRC idle / inactive mode and hundreds of milliwatts in RRC connected mode. Designs aimed at extending battery life are essential for improving energy efficiency and achieving a better user experience.

[0007] Energy efficiency is even more critical for UEs without a continuous power source (e.g., UEs using small rechargeable batteries and single coin cells). In vertical industry use cases, sensors and actuators are widely deployed for monitoring, measurement, charging, and more. Generally, their batteries are not rechargeable and are expected to last for at least several years, as described in TR 38.875. Wearable devices include smartwatches, rings, electronic health-related devices, and medical monitoring devices. Achieving a battery life of 1 to 2 weeks on demand, given typical battery capacities, is challenging.

[0008] Power consumption depends on the configured wake-up period length, such as the paging cycle. To meet the aforementioned battery life requirements, it is anticipated that eDRX cycles with large values ​​will be used, resulting in high latency, which is unsuitable for services requiring both long battery life and low latency. For example, in fire detection and suppression use cases, the actuator should close the fireproof roller shutter and activate the automatic sprinkler system within 1 to 2 seconds after the sensor detects a fire; a long eDRX cycle cannot meet the latency requirements. Clearly, eDRX is unsuitable for latency-critical use cases. Therefore, the intention is to investigate ultra-low power mechanisms capable of supporting low latency (e.g., lower than eDRX latency) in Rel-18.

[0009] Currently, UEs need to be woken up periodically every DRX cycle, which becomes a major cause of power consumption during periods without signaling or data traffic. Power consumption could be significantly reduced if UEs could only be woken up when triggered (e.g., paging). This can be achieved by using a wake-up signal to trigger the main radio (MR) and a separate receiver capable of monitoring the wake-up signal with ultra-low power. The MR is used for data transmission and reception and can be turned off or put into deep sleep unless enabled.

[0010] The power consumption used to monitor the wake-up signal depends on the design of the wake-up signal and the hardware module of the wake-up receiver used for signal detection and processing.

[0011] This research primarily focuses on low-power WUS / WUR for power-sensitive, small-form-factor devices, including IoT use cases such as industrial sensors and controllers, and wearable devices. Other use cases, such as XR / smart glasses and smartphones, are also included.

[0012] US 2020367168 A1 relates to a method and apparatus for a terminal to transmit / receive signals in a wireless communication system, and more specifically, to: a method comprising the steps of: receiving configuration information related to the activation or deactivation of a wake-up signal (WUS); and when the WUS is activated based on the configuration information, monitoring the WUS and a channel corresponding to the WUS, wherein the configuration information related to the activation or deactivation of the WUS is configured to be terminal-specific; and apparatus thereof.

[0013] US 2021400584 A1 discloses a user equipment (UE) for use in 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 WUS with a certain repetition level, wherein: the resource set for WUS includes a mapping of WUS that associates WUS with one or more physical resource blocks and one or more orthogonal frequency division multiplexing (OFDM) symbols, and the repetition level identifies the number of basic sequences for WUS in the resource set; and switch from power saving mode (PSM) to network access mode (NAM) based on the detection of WUS in the resource set.

[0014] WO 2023087163 A1 discloses a system and method for operating in a low-power state. A wireless communication device can enter a first low-power operating state to monitor a defined signal. When in the first low-power operating state, the wireless communication device can monitor the defined signal.

[0015] Figure 1 This describes the UE's RRC state. Under both RRC_IDLE and RRC_INACTIVE, the UE performs neighbor cell measurements and can perform cell reselection. Under RRC_CONNECTED, UE mobility is controlled by the network, and handover can be initiated. Under RRC_IDLE, UE paging is initiated by the CN. Under RRC_INACTIVE, UE paging is initiated by the NG-RAN. To page the UE, its location must be known. Under RRC_IDLE, this is the Tracking Area (RA). Under RRC_INACTIVE, this is the RAN-based Notification Area (RNA), and the UE can initiate RNA updates. The UE periodically performs RAN-based Notification Area Updates (RNAU) and performs RAN-based Notification Area Updates (RNAU) when the UE selects a cell that does not belong to a configured RNA. If the UE finds a more suitable cell, it will reselect to that cell and camp on it according to the cell reselection criteria. If the new cell does not belong to at least one of the tracking areas to which the UE is registered, location registration is performed. In the RRC_INACTIVE state, if the new cell does not belong to the configured RNA, the RNA update process is executed. Figure 2 The SDT process is shown, and Figure 3 The subsequent transmission of SDT is shown.

[0016] A UE in RRC_INACTIVE mode may temporarily measure the LP-WUS reference signal below a threshold, for example, due to temporary signal obstruction or poor reception conditions. Therefore, the UE will unnecessarily or prematurely activate its main radio (MR) and waste energy.

[0017] Technical tasks

[0018] This application provides a solution to the aforementioned problem, because a UE in RRC_INACTIVE state may temporarily measure the LP-WUS reference signal below a threshold, for example, due to temporary congestion or poor reception conditions. Summary of the Invention

[0019] The network determines a UE-specific LP-WUS configuration, for example, based on the UE's QoS profile. This UE-specific configuration is provided via an RRC release message (sent by the gNB to transition the UE to RRC_INACTIVE mode). The LP-WUS configuration includes UE-specific measurement counter limits and timer values. Optionally, additional measurement offsets are configured to prioritize specific UEs. UEs with lower offsets will activate MR earlier. Higher energy efficiency may be achieved for UEs with configured measurement offsets. Furthermore, measurement offsets contribute to latency. Therefore, UEs with latency-sensitive services can be configured with lower offset values.

[0020] When in RRC_INACTIVE mode, the UE application provides the LP-WuS configuration and measures the LP-WUS reference signal.

[0021] If the measured LP-WUS reference signal is lower than the configured threshold, the measurement counter will increment and a UE-specific timer will start.

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

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

[0024] If the measurement counter has not yet reached the configured measurement counter limit, the UE continues to measure the LP-WuS reference signal (and if an additional measurement offset has been configured, the additional measurement offset is applied).

[0025] Alternatively, when the UE moves under RRC_INACTIVE, it may leave its original RNA. When new RNA is detected (e.g., decoding the SIB of a new gNB), the UE performs an RNA update process.

[0026] During the RNA update process, the UE receives updated LP-WUS configuration information from the network, such as the RNA update process response message. When in RRC_INACTIVE mode, the UE can perform either the RA-SDT or CG-SDT procedure.

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

[0028] The beneficial result of these two methods (which can be combined) is that the UE in RRC_INACTIVE mode is more energy-efficient when using the LP-WUS function, thus extending battery life and improving mobility support under RRC_INACTIVE.

[0029] The problem is solved by the described and proposed embodiments.

[0030] This disclosure addresses the aforementioned problems through the proposed embodiments and describes a method for improving the energy efficiency of a UE using LP-WUS under RRC_INACTIVE in a wireless communication system, wherein the network determines a UE-specific LP-WUS configuration.

[0031] In some embodiments of the method according to the first aspect, the method is characterized in that the UE-specific configuration is based on the UE's QoS profile. For example, the network knows which services the UE uses and / or requests, and can classify them according to the UE's service usage and determine the corresponding QoS profile, for example, distinguishing between the UE's usage of latency-sensitive services and latency-tolerant services.

[0032] In some embodiments of the method according to the first aspect, the method is characterized in that a UE-specific configuration is provided via an RRC release message sent by the gNB for causing the UE to transition to RRC_INACTIVE mode.

[0033] In some embodiments of the method according to the first aspect, the method is characterized in that the LP-WUS configuration includes UE-specific measurement counter limits and timer values.

[0034] In some embodiments of the method according to the first aspect, the method is characterized by configuring additional measurement offsets to set priorities for a particular UE.

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

[0036] In some embodiments of the method according to the first aspect, the method is characterized in that if the measured LP-WUS reference signal is lower than a configured threshold, a measurement counter will increment and a UE-specific timer will be started.

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

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

[0039] In some embodiments of the method according to the first aspect, the method is characterized in that if the measurement counter has not yet reached the configured measurement counter limit, the UE continues to measure the LP-WuS reference signal, and if an additional measurement offset has been configured, an additional measurement offset is applied.

[0040] In some embodiments of the method according to the first aspect, the method is characterized in that the method is implemented by a wireless device of a wireless communication system, wherein when the UE moves under RRC_INACTIVE, it may leave its original RNA, and when a new RNA is detected, for example, by decoding the SIB of a new gNB, the UE performs an RNA update process.

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

[0042] In some embodiments of the method according to the first aspect, the method is characterized in that, when in RRC_INACTIVE, the UE performs a RA-SDT or CG-SDT procedure.

[0043] In some embodiments of the method according to the first aspect, the method is characterized in that the network provides an updated LP-WUS configuration via another RRC release message.

[0044] According to a second aspect, this disclosure relates to a wireless device including at least one memory and at least one processor configured to implement the method according to the first aspect of this application.

[0045] According to a third aspect, this disclosure relates to a UE that includes a wireless device according to a second aspect of this application.

[0046] According to the fourth aspect, this disclosure relates to a base station (BS) including at least one memory and at least one processor configured to implement the method according to the first aspect of this application.

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

[0048] According to a sixth aspect, this disclosure relates to a computer program product comprising instructions that, when executed by at least one processor, configure the at least one processor to implement the method according to the first aspect of this application.

[0049] According to a seventh aspect, this disclosure relates to a computer-readable storage medium including instructions that, when executed by at least one processor, configure the at least one processor to implement the method according to a first aspect of this application. Attached Figure Description

[0050] Figure 1 The UE RRC status is shown.

[0051] Figure 2 Different types of SDT are shown.

[0052] Figure 3 The subsequent transmission of SDT is shown.

[0053] Figure 4 A UE flowchart of the first embodiment is shown.

[0054] Figure 5 A flowchart of the gNB of the first embodiment is shown.

[0055] Figure 6 A UE flowchart of the second embodiment is shown.

[0056] Figure 7 A flowchart of the gNB in ​​the second embodiment is shown. Detailed Implementation

[0057] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations and are not intended to represent only configurations in which the concepts described herein can be practiced. The detailed description includes specific details and is intended to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In particular, although terms from 3GPP 5G NR may be used in this disclosure to exemplify embodiments herein, this should not be construed as limiting the scope of the invention.

[0058] Some embodiments of the ideas contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are also included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to 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.

[0059] Generally, all terms used herein should be interpreted according to their common meaning in the relevant art, unless a different meaning is expressly given and / or implied in the context of their use. Unless otherwise expressly stated, all references to an (a) / an / element, device, component, element, step, etc., should be openly interpreted as referring to at least one instance of that element, device, component, element, step, etc. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as occurring after or before another step and / or where an implicit step must occur after or before another step. Where appropriate, any feature of any embodiment of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment of these embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0060] In some embodiments, the more general term "network node" may be used, and it can correspond to any type of radio network node or any network node that communicates with the UE (directly or via another node) and / or another network node. Examples of network nodes are NodeB, MeNB, eNB, network nodes belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio nodes (such as MSR BS), eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node control relay, base transceiver (BTS), access point (AP), transport point, transport node, RRU, RRH, nodes in distributed antenna system (DAS), core network nodes (e.g., mobile switching center (MSC), mobility management entity (MME), etc.), operation and maintenance (O&M), operations support system (OSS), self-optimizing network (SON), location node (e.g., evolved serving mobile location center (E-SMLC)), minimized drive test (MDT), test equipment (physical node or software), etc.

[0061] In some embodiments, the non-limiting terms User Equipment (UE) or Wireless Device may be used, and the term may refer to any type of wireless device that communicates with a network node and / or with another UE in a cellular or mobile communication system. Examples of UEs include target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, PDAs, PADs, tablet computers, mobile terminals, smartphones, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, UE class M1, UE class M2, ProSe UE, V2V UE, V2X UE, etc.

[0062] Furthermore, terms such as base station / gNodeB and UE should be considered non-restrictive and, in particular, do not imply any hierarchical relationship between them; generally speaking, "gNodeB" can be considered device 1 and "UE" can be considered device 2, and the two devices communicate with each other through a radio channel. And in the following text, the transmitter or receiver can be either a gNodeB (gNB) or a UE.

[0063] As those skilled in the art will understand, aspects of the embodiments can be embodied as systems, devices, methods, or program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0064] For example, the disclosed embodiments can be implemented as hardware circuitry, including custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors, or other discrete components). The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0065] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices, which store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not contain signals. In one embodiment, the storage device uses only signals to access the code.

[0066] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing.

[0067] Further specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires; portable computer floppy disks; hard disks; random access memory (“RAM”); read-only memory (“ROM”); erasable programmable read-only memory (“EPROM” or flash memory); portable optical disc read-only memory (“CD-ROM”); optical storage devices; magnetic storage devices; or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store programs for use by or in conjunction with an instruction execution system, device, or apparatus.

[0068] The code used to implement the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Python, Ruby, Java, Smalltalk, C++, etc.), as well as conventional procedural programming languages ​​(such as the "C" programming language, etc.) and / or machine languages ​​(such as assembly language). The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network (including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet using an Internet service provider ("ISP").

[0069] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments. Throughout this specification, references to “an embodiment,” “embodiment,” or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly specified otherwise, the phrases “in one embodiment,” “in an embodiment,” and similar language appearing throughout this specification may, but not necessarily all, refer to the same embodiment, but rather mean “one or more, but not all, embodiments.” Unless expressly specified otherwise, the terms “comprising,” “including,” “having,” and variations thereof mean “including, but not limited to,” “including.” Unless expressly specified otherwise, the enumerated list of items does not imply that any or all of these items are mutually exclusive. Unless otherwise expressly specified, the terms “a,” “an,” and “the” also mean “one or more.”

[0070] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It should be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can 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 instructions executable via the processor of the computer or other programmable data processing apparatus establish components for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0071] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art, including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0072] The code may also be loaded onto a computer, other programmable data processing device or other apparatus to produce a series of operational steps to be performed on the computer, other programmable device or other apparatus, such that the code to be executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0073] The flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each box in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of that code for implementing the specified logical function.

[0074] It should also be noted that in some alternative implementations, the functions indicated in the boxes may not occur in the order shown in the diagram. For example, depending on the functionality involved, two boxes shown consecutively may actually be executed substantially concurrently, or these boxes may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectically equivalent to one or more boxes or portions thereof in the diagram shown can be envisioned.

[0075] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connecting symbols may be used to indicate only the logical flow of the depicted embodiment. For example, arrows may indicate waiting or monitoring periods of unspecified duration between enumerated steps of the depicted embodiment. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0076] The description of elements in each figure can be referenced to elements in the preceding figures. In all figures, similar designations refer to similar elements, including alternative embodiments of similar elements. In addition to the abbreviations listed in the appendix, the following abbreviations are also used:

[0077] LPWuS: Low-Power Wake-Up Signal

[0078] RSRP: Reference Signal Received Power

[0079] RSRQ: Reference Signal Reception Quality

[0080] DRX: Discontinuous Receiver

[0081] Figure 1 , Figure 2 and Figure 3 As described in the introduction of this application.

[0082] Figure 4 A UE flowchart for the first embodiment is shown. The UE checks whether it has moved to RRC_INACTIVE. If so, the UE receives the LP-WUS configuration via a dedicated signaling message (e.g., an RRC release message) and checks whether the RNA update process has been triggered. If so, the UE receives the updated LP-WUS configuration via a dedicated signaling message.

[0083] Figure 5 A gNB flowchart of the first embodiment is shown, where the gNB determines whether the UE should move to RRC_INACTIVE. If so, the gNB provides the LP-WUS configuration in the RRC release message and checks whether the RNA update process has been triggered. If so, the gNB provides a potentially updated LP-WUS configuration in another RRC release message.

[0084] Figure 6 A UE flowchart for the second embodiment is shown. The UE checks whether it has moved to RRC_INACTIVE. If so, the UE receives the LP-WUS configuration via a dedicated signaling message and checks whether the RA-SDT / CG-SDT procedure has been triggered. If so, it receives the updated LP-WUS configuration via another dedicated signaling message.

[0085] Figure 7A gNB flowchart of the second embodiment is shown. Here, the gNB determines whether the UE should move to RRC_INACTIVE. If so, it provides the LP-WUS configuration in the RRC release message and checks whether the RA-SDT / CG-SDT procedure has been triggered. If so, the gNB provides a potentially updated LP-WUS configuration in the RRC release message.

[0086] abbreviation

[0087] BWP bandwidth portion

[0088] CBG code block group

[0089] CLI Cross-Link Interference

[0090] CP loop prefix

[0091] CPUCSI processing unit

[0092] CQI Channel Quality Indicator

[0093] CRB Public Resource Block

[0094] CRC Cyclic Redundancy Check

[0095] CRICSI-RS resource indicator

[0096] CSI Channel Status Information

[0097] CSI-RS Channel State Information Reference Signal

[0098] CSI-RSRPCSI Reference Signal Received Power

[0099] CSI-RSRQCSI reference signal reception quality

[0100] CSI-SINRCSI Signal-to-Interference-Noise Ratio

[0101] CW code

[0102] DCI downlink control information

[0103] DL downlink

[0104] DM-RS demodulation reference signal

[0105] DRX discontinuous reception

[0106] EPRE Energy per Resource Unit

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

[0108] L1-RSRP Layer 1 Reference Signal Received Power

[0109] LI layer indicator

[0110] LP-WUR Low Power Wake-up Receiver

[0111] LP-WUS Low Power Wake-up Signal

[0112] MCS Modulation and Coding Scheme

[0113] MR main radio

[0114] PDCCH Physical Downlink Control Channel

[0115] PDCCH Physical Downlink Control Channel

[0116] PDSCH Physical Downlink Shared Channel

[0117] PMI Precoding Matrix Indicator

[0118] PRB Physical Resource Block

[0119] PRG precoded resource block group

[0120] PRS positioning reference signal

[0121] PSS master synchronization signal

[0122] PT-RS phase tracking reference signal

[0123] PUCCH (Physical Uplink Control Channel)

[0124] QCL Quasi-co-addressable

[0125] RB resource blocks

[0126] RBG resource block group

[0127] RI rank indicator

[0128] RIV resource indicator value

[0129] RS reference signal

[0130] RSRP reference signal received power

[0131] RSRQ reference signal reception quality

[0132] SCI sidelink control information

[0133] SLIV start and length indicators

[0134] SR scheduling request

[0135] SRS detection reference signal

[0136] SS Synchronization Signal

[0137] SS-RSRP SS reference signal received power

[0138] SS-RSRQSS reference signal reception quality

[0139] SSS auxiliary synchronization signal

[0140] SS-SINR (Signal-to-Interference-Ratio)

[0141] TB transport block

[0142] TCI Transport Configuration Indicator

[0143] TDM Time Division Multiplexing

[0144] UE User Equipment

[0145] UL uplink

Claims

1. A method for improving the energy efficiency of a UE using LP-WUS under RRC_INACTIVE in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein the network determines a UE-specific LP-WUS configuration.

2. The method of claim 1, wherein the method comprises: The UE-specific configuration is based on the UE's QoS profile.

3. The method as described in claim 1 or 2, wherein the method comprises: The UE-specific configuration is provided via an RRC release message sent by the gNB to enable the UE to switch to RRC_INACTIVE mode.

4. The method according to claims 1 to 3, wherein the method comprises: The LP-WUS configuration includes UE-specific measurement counter limits and timer values.

5. The method as described in claims 1 to 4, wherein additional measurement offsets are configured to prioritize a specific UE.

6. The method as described in any of the preceding claims, wherein when in RRC_INACTIVE mode, the UE applies the provided LP-WuS configuration and measures the LP-WUS reference signal.

7. The method as described in any of the preceding claims, wherein if the measured LP-WUS reference signal is below a configured threshold, the measurement counter will increment and a UE-specific timer will be started.

8. The method as described in 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. The method as described in any of the preceding claims, wherein if the timer expires, the UE activates its MR and resets its timer.

10. The method as claimed in any of the preceding claims, wherein if the measurement counter does not reach the configured measurement counter limit, the UE continues to measure the LP-WuS reference signal, and if an additional measurement offset has been configured, an additional measurement offset is applied.

11. A method for improving the energy efficiency of a UE using LP-WUS under RRC_INACTIVE in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein when the UE moves under RRC_INACTIVE, the UE leaves its original RNA, and when a new RNA is detected, the UE performs an RNA update process.

12. The method of claim 11, wherein the UE receives updated LP-WUS configuration information (e.g., an RNA update process response message) from the network during the RNA update process.

13. The method of claims 11 to 12, wherein when in RRC_INACTIVE, the UE is capable of performing RA-SDT or CG-SDT procedures.

14. The method of claims 11 to 13, wherein the network is capable of providing an updated LP-WUS configuration via another RRC release message.

15. A wireless device comprising at least one memory and at least one processor, the at least one processor being configured to perform the method as described in any of the preceding claims.

16. A user equipment (UE) comprising the wireless means as described in claim 15.

17. A base station (BS), the base station comprising at least one memory and at least one processor, the at least one processor being configured to implement the method as claimed in any one of claims 1 to 14.

18. A wireless communication system comprising at least one base station as claimed in claim 17 and at least one user equipment as claimed in claim 16.

19. A computer program product comprising instructions that, when executed by at least one processor, configure the at least one processor to perform the method as claimed in any one of claims 1 to 14.

20. A computer-readable storage medium comprising instructions that, when executed by at least one processor, configure the at least one processor to perform the method as claimed in any one of claims 1 to 14.

Images