Methods, devices, and systems for paging LP-WUS compatible UEs.

Abstract

This disclosure relates, in general, to methods, devices, and systems for congestion control in a wireless network. One method, implemented by a first network element, is disclosed. The method may include the steps of: receiving a first message from a second network element or wireless device, which carries low-power wake-up signal (LP-WUS) auxiliary information associated with a wireless device, wherein the LP-WUS auxiliary information indicates paging information for paging the wireless device; and determining the paging information based on the LP-WUS auxiliary information.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication, and more particularly, to methods, devices, and systems for paging user equipment (UE) within a wireless network.

Background Art

[0002] Controlling power consumption and reducing energy costs are important for developing and deploying wireless communication networks. Energy-saving technologies are important for achieving this goal. With the development of wireless communication technologies, more and more wireless devices and user equipment are powered by small rechargeable or small footprint batteries such as single coin cell batteries. Therefore, it is important to control power consumption in various network elements such as UEs and base stations while still having the ability to meet performance requirements.

Summary of the Invention

Means for Solving the Problems

[0003] This disclosure relates to methods, devices, and systems for paging a UE (e.g., a UE that supports a low power wake-up signal (LP-WUS)) within a wireless network.

[0004] In some embodiments, a method implemented by a first network element is disclosed. The method includes receiving, from a second network element or a wireless device, a first message carrying low power wake-up signal (LP-WUS) assistance information associated with the wireless device, the LP-WUS assistance information indicating paging information for paging the wireless device; and determining paging information based on the LP-WUS assistance information.

[0005] Note: There seems to be a tag mismatch in the original text where ID=17 is "

課題を解決するための手段

Means for Solving the Problems

[0006] In some embodiments, there exists a network element or wireless device comprising a processor and memory, wherein the processor is configured to read code from memory and implement any method enumerated in any of the embodiments.

[0007] In some embodiments, a computer program product comprises computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the methods enumerated in any of the embodiments.

[0008] The above embodiments and other aspects and alternatives of their implementation are described in more detail in the following drawings, description, and claims. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows an exemplary wireless communication network. [Figure 2] Figure 2 shows an example of a wireless network node. [Figure 3] Figure 3 shows an example of user equipment. [Figure 4] Figure 4 shows an exemplary paging scenario in which the core network provides LP-WUS auxiliary information. [Figure 5] Figure 5 shows another exemplary paging scenario in which the core network provides LP-WUS auxiliary information. [Figure 6] Figure 6 shows an exemplary paging scenario in which the UE provides LP-WUS auxiliary information to the base station. [Figure 7] Figure 7 shows an exemplary message flow for exchanging and updating LP-WUS auxiliary information among various network elements for a UE in an inactive state or an idle state. [Figure 8] Figure 8 shows an exemplary XnAP RAN paging scenario in which LP-WUS auxiliary information is transmitted from one base station to another. [Figure 9] Figure 9 shows an exemplary F1AP RAN paging scenario in which LP-WUS auxiliary information is transmitted from the CU to the DU. [Modes for carrying out the invention]

[0010] Detailed explanation (Wireless communication network) Figure 1 shows an exemplary radio communication network 100, which includes a core network 110 and a radio access network (RAN) 120. The core network 110 further includes at least one mobility management entity (MME) 112 and / or at least one access and mobility management function (AMF). Other functions that may be included within the core network 110 are not shown in Figure 1. The RAN 120 further includes several base stations, e.g., base stations 122 and 124. The base stations may include at least one evolved NodeB (eNB) for 4G LTE, an enhanced LTE eNB (ng-eNB), or a next-generation NodeB (gNB) for 5G new radio (NR), or any other type of signal transmission / reception device such as a UMTS NodeB. The eNB 122 communicates with the MME 112 via the S1 interface. Both the eNB 122 and the gNB 124 may be connected to the AMF 114 via the Ng interface. Each base station manages and supports at least one cell. For example, the base station gNB124 may be configured to manage and support cell 1, cell 2, and cell 3.

[0011] The gNB124 may include a central unit (CU) and at least one distributed unit (DU). The CU and DU may be located together in the same location, or they may be separated into different locations. The CU and DU may be connected via an F1 interface. As an alternative, with respect to an eNB that can be connected to a 5G network, this may also be similarly divided into a CU and at least one DU, referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and ng-eNB-DU may be connected via a W1 interface.

[0012] The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1, labeled as 140, includes cell 1, cell 2, and cell 3, and may include more cells, which may be managed by other base stations and are not shown in Figure 1. The wireless communication network 100 may also include at least one UE 160. The UE may select a cell from among several cells supported by the base station to communicate with the base station through an over-the-air (OTA) wireless communication interface and resources, and this may be re-selected for communication as the UE 160 progresses within the wireless communication network 100. For example, the UE 160 may initially select cell 1 to communicate with base station 124, and this may then be re-selected for cell 2 at some later point in time. Cell selection or re-selection by the UE 160 may be based on the radio signal strength / quality of the various cells and other factors.

[0013] The wireless communication network 100 may be implemented as, for example, a 2G, 3G, 4G / LTE, or 5G cellular communication network. Correspondingly, base stations 122 and 124 may be implemented as a 2G base station, a 3G NodeB, an LTE eNB, or a 5G NR gNB. The UE 160 may be implemented as a mobile or fixed communication device capable of accessing the wireless communication network 100. The UE 160 may include, but is not limited to, mobile phones, laptop computers, tablets, personal digital assistants, wearable devices, Internet of Things (IoT) devices, MTC / eMTC devices, distributed remote sensor devices, roadside assistance equipment, XR devices, and desktop computers. The UE 160 may also be generally referred to as a wireless communication device or wireless terminal. The UE 160 may support sidelink communication to another UE via the PC5 interface.

[0014] The following explanation focuses on cellular wireless communication systems, as shown in Figure 1, but the underlying principles are applicable to other types of wireless communication systems for paging wireless devices. These other wireless systems may include, but are not limited to, Wi-Fi, Bluetooth®, Zigbee®, and WiMAX networks.

[0015] Figure 2 shows an embodiment of an electronic device 200 for implementing a network base station (e.g., a radio access network node), a core network (CN), and / or operation and maintenance (OAM). Optionally, in one implementation, the exemplary electronic device 200 may include a radio transmission / reception (Tx / Rx) network 208 for transmitting / receiving communications with UEs and / or other base stations. Optionally, in one implementation, the electronic device 200 may also include a network interface network 209 for communication between the base station and other base stations and / or core networks, e.g., optical or wired interconnects, Ethernet®, and / or other data transmission media / protocols. Optionally, the electronic device 200 may include an input / output (I / O) interface 206 for communication with an operator or equivalent.

[0016] The electronic device 200 may also include a system network 204. The system network 204 may include a processor 221 and / or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more of the processors 221 to perform the functions of a network node. Parameters 228 may include parameters to support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0017] Figure 3 shows an embodiment of an electronic device for implementing a terminal device 300 (e.g., a user device (UE)). The UE 300 may be a mobile device, such as a smartphone or a mobile communication module, located in a vehicle. The UE 300 may include some or all of the following: a communication interface 302, a system network 304, an input / output interface (I / O) 306, a display network 308, and a storage device 309. The display network may include a user interface 310. The system network 304 may include any combination of hardware, software, firmware, or other logic / circuit networks. The system network 304 may be implemented together with, for example, one or more system-on-a-chip (SOCs), application-specific integrated circuits (ASICs), discrete analog and discrete digital circuits, and other networks. The system network 304 may be part of the implementation of any desired functionality within the UE 300. In this regard, the system circuitry 304 may, in an embodiment, include logic to facilitate music and video decoding and playback, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback, application startup, user input approval, application data storage and retrieval, establishing, maintaining, and terminating cellular telephone calls or data connections for Internet connectivity, establishing, maintaining, and terminating wireless network connections, Bluetooth® connections, or other connections, and displaying relevant information about the user interface 310. The user interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch sensor display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements.Additional embodiments of the I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0018] Referring to Figure 3, the communication interface 302 may include a radio frequency (RF) transmission (Tx) and reception (Rx) network 316, which handles the transmission and reception of signals through one or more antennas 314. The communication interface 302 may also include one or more transceivers. The transceivers may be wireless transceivers including a modulation / demodulation network, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmission and reception through one or more antennas or (with respect to some devices) through a physical (e.g., wired) medium. The transmitted and received signals may conform to any of the following diverse array formats, protocols, modulation (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As one specific embodiment, the communication interface 302 may include transceivers that support transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA)+, 4G / Long-Term Evolution (LTE), and 5G standards. However, the techniques described below are also applicable to other wireless communication technologies, whether they originate from the Third Generation Partnership Project (3GPP®), the GSM® Association, 3GPP2, IEEE, or other partnerships or standards bodies.

[0019] Referring to FIG. 3, the system circuit network 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 for performing the desired functionality for the UE 300. The parameters 328 may provide and define the configuration and operation options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will transmit or has received through the communication interface 302. In various implementations, the system power for the UE 300 may be supplied by a power storage device such as a battery or a transformer. (Low Power Wake-up Signal (LP-WUS) and LP-WUS-Compatible UE)

[0020] In a wireless communication network, a UE may constantly listen / monitor a network (e.g., a base station such as a gNodeB) and check whether there is new downlink data with transmission pending.

[0021] Energy efficiency is always an important factor when designing various wireless devices and / or base stations. As more and more use cases are introduced, energy efficiency becomes particularly more important for UEs without a sustainable energy source, such as small rechargeable and single coin-cell battery-using UEs. In vertical use cases, sensors and actuators are widely deployed for monitoring, measurement, billing / charging, etc. Generally, the batteries in these devices are not rechargeable and are expected to last at least several years. In addition, for wearable devices including smartwatches, rings, electronic health-related devices, and medical monitoring devices, typically it is required that their battery capacity can last up to 1 - 2 weeks at most, which is a challenge.

[0022] Power consumption largely depends on the length of the device wake-up period. This length can consist, for example, of a paging cycle. During each paging cycle, the device may wake up and monitor paging requests. The device will become active if paging is required, and otherwise, to conserve energy, return to sleep mode. When the device is active, hardware components such as radio frequency (RF) circuits, RF chains, and RF modules are turned on to receive / transmit data (e.g., signaling, payload data). In exemplary implementations, intermittent receive (DRX) mode, or extended DRX (eDRX) mode with longer cycles than the DRX cycle, may be used to meet the battery life requirements described above. In DRX or eDRX mode, the UE may need to periodically wake up once per DRX / eDRX cycle to monitor paging signaling, which accounts for the majority of power consumption during periods without paging signaling or data traffic. In other words, for most of the time, the UE may wake up only to find that there are no pending tasks (e.g., paging, pending data, etc.), and then return to sleep again. Power consumption can be dramatically reduced if the UE can only wake up when triggered (e.g., by an external signal) or when needed, for example, when the UE needs to be paged or when there is pending data for the UE. In this case, the UE wake-up may be called trigger-based wake-up or need-based wake-up, compared to unconditional wake-up, which is required in each cycle (e.g., DRX / eDRX cycle, paging cycle).

[0023] In some exemplary implementations, a multilevel sleep mechanism may be implemented to achieve the aforementioned trigger-based or need-based wake-up. In such a mechanism, the UE may be designed with a main radio (MR) (or main radio unit, main radio chain) that typically handles signaling (e.g., paging signaling) and / or data (e.g., uplink data or downlink data), as well as a separate receiver capable of monitoring a wake-up signal (WUS). The WUS acts as an external trigger signal transmitted from the network (e.g., a base station) to wake up the UE. Compared to the main radio, the separate receiver is lightweight and requires very little energy to operate. Using such a design, the UE can enter an ultra-deep sleep mode by shutting down its main radio, but can receive the wake-up signal using only the separate lightweight receiver. The WUS is used as a trigger to cause the UE to turn on its main radio to perform subsequent tasks such as receiving paging signaling, receiving data, etc. Ultra-low power consumption on the UE can be achieved by operating only a lightweight receiver and receiving trigger signals when the UE is operating in ultra-deep sleep mode.

[0024] In some exemplary implementations, in ultra-deep sleep mode, the UE may turn off or shut down the main radio to reduce power consumption and not periodically monitor the legacy paging signal. Instead, the UE may monitor a wake-up signal transmitted from the network using a separate receiver characterized by ultra-low power consumption. Only when a wake-up signal is detected will the UE periodically turn on the main radio and monitor the paging signal. For example, the UE may turn on its main radio per DRX cycle or eDRX cycle. Thus, unless a wake-up signal is detected, the UE's main radio can remain off for extended periods, resulting in a dramatic reduction in power consumption. In contrast, in normal sleep mode (not ultra-deep sleep mode), even when the UE turns off the radio or main radio, it still has to periodically turn on the radio or main radio and monitor the paging signal (e.g., per DRX cycle, eDRX cycle). This results in increased power consumption.

[0025] If a UE is equipped with the aforementioned separate receiver capable of monitoring the wake-up signal, and the UE is in an ultra-deep sleep mode with ultra-low power consumption, the UE may be referred to as a Low-Power Wake-Up-Signal (LP-WUS) Compatible UE or simply an LP-WUS UE. Generally, an LP-WUS UE is equipped with a main radio and a separate receiver for monitoring the trigger signal. The separate receiver is lightweight, features ultra-low power consumption, and can operate independently when the main radio is in sleep mode and turned off. It should be noted that the trigger signal is also preferably lightweight and should require minimal power and effort to detect.

[0026] In Radio Resource Control (RRC) idle, RRC inactive, or other inactive or idle states, the LP-WUS UE may enter ultra-deep sleep mode to conserve power. In ultra-deep sleep mode, the UE will turn off the main radio (MR) and monitor the LP-WUS transmitted by the network using a separate low-power radio receiver.

[0027] For LP-WUS-enabled UEs, once the UE detects an LP-WUS signal (e.g., by using a separate lightweight receiver), the UE may need some time to wake up from ultra-deep sleep mode to monitor subsequent signaling, such as paging signaling. This period is called ramp-up time. Ramp-up time can be considered the delay from receiving a trigger signal (e.g., LP-WUS) until the main radio becomes operational / active. Ramp-up time may be determined by, or associated with, the speed at which the UE responds to the trigger signal and / or the speed at which the UE is able to turn on its main radio and make it operational / active.

[0028] To utilize the ultra-deep sleep mode, the UE not only needs to be LP-WUS compliant, but coordination is also required between the LP-WUS compliant UE and the network (e.g., base station, core network). For example, when an LP-WUS compliant UE is in an RRC idle state, RRC inactive state, or other inactive / idle state, the UE can enter ultra-deep mode. At this point, if the network needs to page the UE, the network may not know whether the UE is a legacy UE or an LP-WUS compliant UE, and it may be impossible for the network to first send a wake-up signal to the UE and then determine whether it needs to page the UE, or it may page the UE directly, resulting in delays or further failures in pageping the UE.

[0029] The network may leverage UE support for LP-WUS by using LP-WUS paging. Compared to conventional paging, where the network can directly send a paging signal to the UE and there is no need to wake up the UE, LP-WUS paging can be considered a two-step process. In the first step, the network may need to send a trigger signal (e.g., LP-WUS) to wake up the UE, so that the UE can turn on its main radio. In the second step, the network proceeds to send a paging signal to the UE, and the UE can receive the paging signal using its main radio. It should be noted that the second step is performed with a delay after the first step, mainly because the network needs to ensure that the UE's main radio is ready to receive the paging signal. On the UE side, when the UE is in LP-WUS paging mode, and the UE is idle or inactive, the UE may enter an ultra-deep sleep mode and only LP-WUS needs to be monitored. LP-WUS monitoring may be periodic. The UE will only wake up and receive the paging signal when triggered by LP-WUS.

[0030] This disclosure describes various embodiments focused on supporting and utilizing LP-WUS-enabled UEs within a network. Support may include coordination between the LP-WUS UE and the network. Unless otherwise specified, wake-up signaling in this disclosure refers to LP-WUS.

[0031] It should be noted that the embodiments in this disclosure are for illustrative purposes only. Descriptions of embodiments may include multiple steps, and corresponding methods may include all steps or simply some of all steps. Additional steps are not excluded from the method unless expressly stated. Different embodiments and the steps in each embodiment may be combined in any order where there is no conflict.

[0032] Further details regarding these embodiments are described below. (Embodiment 1: The core network provides LP-WUS auxiliary information)

[0033] In this embodiment, the core network (CN) (or a specific core network node) is responsible for passing / providing LP-WUS auxiliary information of the UE to base stations such as gNodeB (gNB). Specifically, the CN may pass LP-WUS auxiliary information during the NGAP paging procedure. Figure 4 shows an exemplary message flow for the method according to this embodiment. The method may include some or all of the following steps, as shown in Figure 4.

[0034] LP-WUS supplementary information may be used by the UE and network to determine the paging information (or paging configuration, paging scheme) that indicates the paging style. For example, whether LP-WUS paging should be used to paging the UE, or whether legacy paging should be used (without LP-WUS). If LP-WUS paging is selected, parameters related to LP-WUS paging may be included or indicated by the paging information. Step 1:

[0035] An LP-WUS-enabled UE may negotiate its LP-WUS capabilities with the core network, for example, through non-accessible layer (NAS) messages. Negotiation may occur when the UE registers with the network or when the UE attempts initial access to the network. The CN may store the LP-WUS capabilities negotiated with respect to the UE. After negotiation, the UE may be released into an idle / inactive state (e.g., RRC idle state, RRC inactive state) at some point. Step 2:

[0036] If a CN needs to page a UE, the CN may determine LP-WUS auxiliary information based on the negotiated LP-WUS capability of the UE. The CN may then send a paging message to the base station, for example, via the NG interface. The paging message may carry the LP-WUS auxiliary information. Alternatively, the CN may send the LP-WUS auxiliary information to the base station using a different message prior to paging the UE.

[0037] In some implementations, LP-WUS auxiliary information may include or indicate at least one of the following paging information: • Indication whether LP-WUS is supported by UE • Indication whether it is preferable for LP-WUS (or LP-WUS paging) to be enabled for the UE. • Indication whether LP-WUS (or LP-WUS paging) is applied only within the last serving cell of the UE. • Ramp-up time: Indicates the time it takes for the UE to wake up from ultra-deep sleep mode. • LP-WUS subgroup ID (identifier) ​​indicating the LP-WUS subgroup of the UE. • Paging subgroup ID indicating the UE paging subgroup

[0038] Paging information can be considered a paging configuration, which may be used by the UE and / or network to determine the format of how the UE is paged.

[0039] In some implementations, UEs may be static, so as to be allocated or arranged in fixed locations. For example, UEs for environmental sensing and monitoring. Therefore, the last serving cell (the one the UE was most recently served in) is still likely to be serving the UE when the UE is woken up. In this case, LP-WUS paging may need to be applied only to the last serving cell. Optionally, legacy paging may be applied to other cells so that paging signals / messages are sent without directly sending LP-WUS.

[0040] In some implementations, to further reduce power consumption caused by false paging alarms, the UE may be divided into multiple subgroups. The subgroups may be organized by paging opportunities or wake-up signaling opportunities. UEs within the same paging subgroup (or paging opportunity subgroup) will monitor the same paging opportunities, and UEs within the same wake-up signaling subgroup (or wake-up signaling opportunity subgroup) will monitor the same wake-up signaling opportunities. By using subgrouping, a UE only needs to monitor its own paging opportunities and / or wake-up signaling opportunities based on its paging subgroup ID or wake-up signaling subgroup ID, and does not monitor other paging opportunities or wake-up signaling opportunities belonging to other subgroups.

[0041] In some exemplary implementations, ramp-up time indicates the time it takes for the UE to wake up from an ultra-deep sleep mode. For example, it could represent the time interval between when the UE receives an LP-WUS signal and when the UE turns on its main radio.

[0042] In some exemplary implementations, the ramp-up time may be determined by the time it takes for the UE to wake up from ultra-deep sleep mode, or it may be associated with the time it takes for the UE to wake up from ultra-deep sleep mode. For example, the ramp-up time may be a predefined value that is equal to or greater than the time required for the UE to wake up from ultra-deep sleep mode.

[0043] Note that when the LP-WUS function for an LP-WUS-compatible UE is enabled, the UE's main radio is allowed to enter ultra-deep sleep mode, and the UE can monitor the LP-WUS signal using a separate lightweight receiver. Conversely, when LP-WUS for an LP-WUS-compatible UE is disabled, the UE's main radio is prevented from entering ultra-deep sleep mode. Step 3:

[0044] The base station receives LP-WUS auxiliary information transmitted by the CN, and the base station may page LP-WUS-enabled UEs based on the LP-WUS auxiliary information. The base station may determine a format for the method of page UEs. For example, the base station may take at least one of the following actions:

[0045] (1) If LP-WUS is not supported by the UE, the base station shall not apply LP-WUS paging to the UE. For example, the base station does not have to send a wake-up signal to the UE. In this case, conventional paging may be used, i.e., the base station may page the UE by directly sending a paging signal (or paging message).

[0046] (2) If it is preferable that LP-WUS be enabled for the UE, the base station shall apply LP-WUS paging. That is, the base station may first send a wake-up signal to the UE and then page the UE using a paging signal.

[0047] (3) In some implementations, LP-WUS may be applied only within the last serving cell of the UE. The last serving may include the cell that most recently served the UE. In this case, the base station sends the wake-up signal only to the UE in the last serving cell. In some other implementations, such a restriction does not apply, and the base station sends the wake-up signal to the UEs in all paging cells (not just the last serving cell of the UE).

[0048] (4) Based on the indicated ramp-up time, the base station may determine a waiting period after transmitting the wake-up signal and before transmitting the corresponding paging signal. This period reflects the delay required for transmitting the paging signal. This delay is required so that the UE's main radio is turned on and therefore ready to receive the paging signal. In some implementations, the delay is at least equal to the UE's ramp-up time.

[0049] (5) To further reduce power consumption caused by false paging alarms, the UE may be divided into multiple subgroups. UEs within the same subgroup will monitor the same paging opportunity or wake-up signal opportunity. By using subgrouping, a UE will only need to monitor its own paging opportunity and / or wake-up signal opportunity based on the paging subgroup ID or wake-up signal subgroup ID, and will not monitor other paging opportunities or wake-up signal opportunities belonging to other subgroups. The base station may determine the paging subgroup or wake-up signal subgroup for a UE based on the LP-WUS subgroup ID or paging subgroup ID. If the LP-WUS subgroup ID is not present in the LP-WUS auxiliary information, the base station may independently determine the LP-WUS subgroup for the UE. If the paging subgroup ID is not present in the LP-WUS auxiliary information, the base station may independently determine the paging subgroup for the UE.

[0050] If it is preferable for LP-WUS to be enabled for the UE, the base station may send a wake-up signal to the UE in the last serving cell or in all paging cells. Step 4:

[0051] After the standby period, the UE is woken up (for example, the UE's main radio becomes operational / active at this point) and begins monitoring paging signals from the network (for example, the base station). Step 5:

[0052] The base station sends a paging message (e.g., an RRC paging message) to the UE within the paging cell. Step 6:

[0053] The UE is successfully paged and subsequently establishes its connection to the network. (Embodiment 2: The core network provides LP-WUS auxiliary information)

[0054] In this embodiment, the core network (CN) (or a specific core network node) is responsible for passing / providing LP-WUS auxiliary information to a base station such as a gNodeB (gNB). Specifically, the CN may pass LP-WUS auxiliary information during the UE context setup / modification procedure, and thus the base station may create or modify the LP-WUS auxiliary information. The base station will store the newly created or modified LP-WUS auxiliary information locally. Figure 5 shows an exemplary message flow for the method according to this embodiment. The method may include some or all of the following steps, as shown in Figure 5. Step 1:

[0055] An LP-WUS-enabled UE may negotiate its LP-WUS capabilities with the core network, for example, through NAS messages. Negotiation may occur when the UE registers with the network or when the UE attempts initial access to the network. The UE may then initiate a protocol data unit (PDU) session setup procedure between the UE, the base station, and the CN.

[0056] In addition, or alternatively, if a PDU session already exists with respect to the UE, the UE may renegotiate its LP-WUS capability with the core network, for example, through NAS messages. Step 2:

[0057] If a UE context has not yet been set for a UE, the CN may request the base station to set the UE context, for example, by sending an NGAP initial UE context setting request message to the base station. The NGAP initial UE context setting request message may carry LP-WUS auxiliary information. The LP-WUS auxiliary information is defined in the same manner as in Embodiment 1. Step 3:

[0058] The base station stores LP-WUS auxiliary information that is carried within the initial UE context setting request message for the UE.

[0059] In some implementations, LP-WUS auxiliary information stored by the base station may be updated, for example, by the CN. For example, if a UE context is already configured for the UE and / or a PDU session for the UE is already established, the UE may renegotiate the relevant LP-WUS capabilities with the Core Network (CN), for example, through a NAS message. After renegotiation, the LP-WUS auxiliary information is updated on the CN side. The CN may further need to update the LP-WUS auxiliary information stored within the RAN network. This may be achieved by the CN sending a UE context modification request message to the base station. The UE context modification request message may carry the updated LP-WUS auxiliary information.

[0060] If a base station receives updated LP-WUS auxiliary information, for example, carried in a UE context modification request message, the base station may update its stored LP-WUS auxiliary information as appropriate. For example, the base station may update the UE context in which the LP-WUS auxiliary information is stored. (Embodiment 3: The UE provides LP-WUS auxiliary information)

[0061] In this embodiment, the UE is responsible for passing / providing LP-WUS auxiliary information to a base station such as a gNodeB (gNB). Specifically, the UE may be connected or active and may already have a connection with a base station. Figure 6 shows an exemplary message flow for the method according to this embodiment. The method may include some or all of the following steps, as shown in Figure 6. Step 1:

[0062] The UE is connected to the network in a connected or active state (e.g., RRC connected state). The core network does not provide LP-WUS auxiliary information to the base station. Step 2:

[0063] The UE transmits an RRC message, such as a UE auxiliary information message, to the base station. The message carries LP-WUS auxiliary information. The LP-WUS auxiliary information is defined in the same manner as in Embodiment 1. Step 3:

[0064] The base station stores LP-WUS auxiliary information within the UE context. (Embodiment 4: RAN optimizes LP-WUS auxiliary information)

[0065] In this embodiment, the radio access network (RAN), such as a base station, may further optimize / adjust the LP-WUS auxiliary information. This embodiment also covers scenarios in which UEs are paged in an idle state and scenarios in which UEs are paged in an inactive state. Figure 7 shows an exemplary message flow for the method according to this embodiment. The method may include some or all of the following steps, as shown in Figure 7. Step 1:

[0066] When the UE is connected to the network in a connected or active state (e.g., RRC connected state), the core network may provide LP-WUS auxiliary information to the base station, for example, during the NGAP UE context setup / modification procedure. Alternatively, the UE may provide LP-WUS auxiliary information to the base station, for example, via RRC messages. The gNB stores this information within the UE context. The LP-WUS auxiliary information is defined in the same manner as in Embodiment 1. Step 2:

[0067] This step is optional. Based on the LP-WUS auxiliary information stored within the UE context, the base station may further optimize / adjust the LP-WUS auxiliary information or take further actions based on the LP-WUS auxiliary information.

[0068] For example, the base station may decide whether to enable or disable LP-WUS for the UE.

[0069] In another embodiment, the base station may determine an optimized ramp-up time for a UE based on the cell configuration of the cell to which the UE is accessing or camping on. The initial ramp-up time may be determined based on the UE's capabilities, such as speed, after receiving the LP-WUS signal, so that the UE can turn on or activate its main radio, but it should be noted that this does not take into account the cell configuration of the cell to which the UE is accessing or camping on. The base station may further adjust / optimize the ramp-up time to take the cell configuration into account. For example, with respect to paging UEs belonging to the same LP-WUS subgroup or paging subgroup, the cell may want these UEs to be woken up simultaneously or nearly simultaneously, for example, within the same wake-up window, within adjacent wake-up windows, at the same opportunity within one DRX / eDRX cycle, or at adjacent opportunities within one DRX / eDRX cycle, in order to avoid missing the paging signal. Therefore, the base station may configure the same ramp-up time for these UEs. In another embodiment, with respect to certain types of UEs, such as environmental sensor devices, the cell may desire that these devices wake up at similar or identical times in order to coordinate or synchronize positioning services or collaborative sensing services using multiple sensors within different UEs, and may configure identical ramp-up times for these UEs. In yet another embodiment, to reduce paging or random access channel (RACH) contention, the cell may assign identical or different ramp-up times to different UEs to control the access rate of the UEs. In yet another embodiment for network power saving, the cell may configure different ramp-up times under different power saving modes of the cell to reduce the paging frequency.

[0070] In some implementations, the cell configuration for optimizing ramp-up time includes at least one of the following, supported by the UE: a configured / optimized ramp-up time for a specific service, a configured / optimized ramp-up time for a specific type of UE, a configured / optimized ramp-up time for a specific wake-up signal subgroup, a configured / optimized ramp-up time for a specific paging subgroup, or a configured / optimized ramp-up time for a specific cell power saving mode.

[0071] In another embodiment, the base station may decide whether to restrict LP-WUS paging to the last serving cell of the UE. After the decision, the base station will update the LP-WUS information stored in the UE context.

[0072] In some implementations, the network (e.g., base station, core network) can control the use of LP-WUS. In other words, only when the network enables the LP-WUS function (or enables LP-WUS mode) for an LP-WUS-enabled UE is the UE's main radio allowed to enter ultra-deep sleep mode, and the UE can monitor the LP-WUS signal. On the other hand, if the network disables LP-WUS for an LP-WUS-enabled UE, the UE's main radio is not allowed to enter ultra-deep sleep mode to conserve power. Step 3:

[0073] If the base station decides to release the UE into an idle or inactive state (e.g., RRC idle or RRC inactive), the base station may, for example, send an RRC release message to the UE. If the base station has optimized / adjusted the LP-WUS auxiliary information, the updated LP-WUS auxiliary information may be carried in this message. When the UE is in an idle or inactive state, the UE shall monitor paging messages / signaling based on the received LP-WUS auxiliary information as follows (at least one of the following actions may be performed by the UE):

[0074] If LP-WUS is preferably enabled for the UE, the UE shall, in order to conserve power, turn off (shut down) its main radio, enter ultra-deep sleep mode, and monitor the wake-up signal transmitted by the network. If LP-WUS is applied only within the UE's last serving cell (the one the UE most recently served), the UE will only monitor wake-up signals transmitted by the network in that last serving cell. Otherwise, the UE will monitor wake-up signals transmitted by the network in all cells the UE has accessed or camped on (cells the UE has accessed or camped on). If the UE detects a wake-up signal, the UE shall turn on the main radio and exit ultra-deep sleep mode before the ramp-up period expires, and then monitor for paging opportunities. If a paging subgroup ID is presented or indicated within the LP-WUS supplementary information, the UE will monitor paging opportunities that belong to or are associated with the paging subgroup identified by the paging subgroup ID. If an LP-WUS subgroup ID is presented or indicated within the LP-WUS supplementary information, the UE will monitor LP-WUS opportunities that belong to or are associated with the LP-WUS subgroup identified by the LP-WUS subgroup ID. Step 4:

[0075] Step 4 may also apply if the UE is released into an idle state (e.g., RRC idle state). Step 4.1:

[0076] If an LP-WUS-enabled UE provides LP-WUS auxiliary information to a base station, the UE will not negotiate the associated LP-WUS capabilities with the CN via NAS messages when registering with the network. In this case, if the base station requests the CN to release the UE-related NGAP resources, the base station may add the LP-WUS auxiliary information to the request message, such as the UE context release message.

[0077] If a base station has optimized the LP-WUS auxiliary information provided by the CN, it may pass the optimized LP-WUS auxiliary information to the CN when requesting the CN to release UE-related NGAP resources by adding the optimized LP-WUS auxiliary information to a request message such as a UE context release message. Step 4.2:

[0078] The CN will store / update LP-WUS auxiliary information as needed. The CN will use the LP-WUS auxiliary information for subsequent paging of the UE in idle state. Step 4.3:

[0079] If the CN decides to page an UE in an idle state, the CN may send an NGAP paging message to the base station, including the latest LP-WUS auxiliary information in the message.

[0080] Note that when a UE is released to an idle state, the base station may discard the corresponding UE context for that UE. Step 5:

[0081] Step 5 may apply when the UE is released into an inactive state (e.g., RRC inactive state). The base station decides to page the UE in an inactive state (e.g., RRC inactive state) based on the latest LP-WUS auxiliary information stored within the UE context, which is maintained within the base station. Step 6:

[0082] When the UE is idle, the base station receives LP-WUS auxiliary information from NGAP paging messages transmitted by the CN. When the UE is inactive, the base station recognizes the LP-WUS auxiliary information because it is stored within the UE context maintained within the base station. Step 7:

[0083] Based on the LP-WUS auxiliary information, the base station determines a method for paging the UE. For example, based on whether LP-WUS paging is limited to the last serving cell of the UE, the base station may choose to send the WUS signal to the UE in the last serving cell or to all paging cells. In another embodiment, if LP-WUS paging is preferred, the base station first sends the WUS signal, and then, after the UE has woken up (which may be measured by a ramp-up period or a desired waiting period before sending the paging message (see details in Embodiment 1)), the base station sends the paging message to the UE. (Embodiment 5: RAN paging from one base station through another base station)

[0084] In this embodiment, RAN paging is used to page the UEs. In RAN paging, one base station may page the UEs through another base station, for example, via an Xn interface. Figure 8 shows an exemplary message flow for the method according to this embodiment. The method may include some or all of the following steps, as shown in Figure 8. Step 1:

[0085] If the UE is in an idle state (e.g., RRC idle state), base station 1 receives LP-WUS auxiliary information from, for example, an NGAP paging message transmitted by the CN.

[0086] If the UE is in an inactive state (e.g., RRC inactive state), base station 1 recognizes the LP-WUS auxiliary information because it is stored within the UE context. Step 2:

[0087] If a base station decides to page a UE via another base station, base station 1 may send a paging message, such as an XnAP RAN paging message, to base station 2. The XnAP RAN paging message may carry LP-WUS auxiliary information. Note that the LP-WUS auxiliary information is defined in the same manner as in Embodiment 1. Step 3:

[0088] Base station 2 may determine a method for paging the UE based on the received LP-WUS auxiliary information. For example, based on whether LP-WUS paging is limited to the last serving cell of the UE, base station 2 may choose to send the WUS signal to the UE in the last serving cell or to all paging cells. In another embodiment, if LP-WUS paging is preferred, base station 2 first sends a WUS signal, and then, after the UE has been woken up by the WUS signal (which may be measured by a ramp-up period or a desired waiting period before sending a paging message (see details in Embodiment 1)), base station 2 sends a paging message to the UE. (Embodiment 6: F1 paging via distributed units (DU))

[0089] In this embodiment, the base station has a distributed architecture comprising a central unit (CU) and one or more distributed units (DUs) controlled by the CU. For example, the base station is a gNB, which includes one gNB-CU and one or more DUs. F1 paging is used to page the UE. In F1AP paging, the CU triggers the DU to send a paging message / signaling to the UE. Figure 9 shows an exemplary message flow for the method according to this embodiment. The method may include some or all of the following steps, as shown in Figure 9. Step 1:

[0090] If the UE is in an idle state (e.g., RRC idle state), the gNB-CU receives LP-WUS auxiliary information from NGAP paging messages sent by the CN, for example.

[0091] If the UE is in an inactive state (e.g., RRC inactive state), the gNB-CU recognizes the LP-WUS auxiliary information because it is stored within the UE context. Step 2:

[0092] If the gNB-CU decides to page the UE via the gNB-DU, base station 1 may send a paging message, such as an F1AP RAN paging message, to the gNB-DU. Figure 9 shows one gNB-DU as an example, but there may be more than one gNB-DU. The F1AP RAN paging message may carry LP-WUS auxiliary information. Note that the LP-WUS auxiliary information is defined in the same way as in Embodiment 1. Step 3:

[0093] The gNB-DU may determine a method for paging the UE based on the received LP-WUS auxiliary information. For example, based on whether LP-WUS paging is limited to the last serving cell of the UE, the gNB-DU may choose to send the WUS signal to the UE in the last serving cell or to all paging cells. In another embodiment, if LP-WUS paging is preferred, the gNB-DU first sends the WUS signal, and then, after the UE has been woken up by the WUS signal (which may be measured by a ramp-up period or a desired waiting period before sending the paging message (see details in Embodiment 1)), the gNB-DU sends the paging message to the UE.

[0094] The above description and accompanying drawings provide specific exemplary embodiments and implementations. However, the subject matter described may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any exemplary embodiments described herein. A reasonably broad scope for the claimed or covered subject matter is intended. In particular, for example, the subject matter may be embodied as a method, device, component, system, or non-temporary computer-readable medium for storing computer code. Thus, embodiments may take the form of, for example, hardware, software, firmware, storage medium, or any combination thereof. For example, the method embodiments described above may be implemented by a component, device, or system including memory and a processor by executing computer code stored in memory.

[0095] Throughout this specification and the claims, terms may have nuances implied or suggested in context beyond their explicitly stated meaning. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, the claimed subject matter is intended to include a combination of exemplary embodiments, whether in whole or in part.

[0096] In general, technical terms can be understood, at least in part, from their use in context. For example, terms such as “and,” “or,” or “and / or,” as used herein, can have various meanings, at least in part, depending on the context in which such terms are used. Typically, when “or” is used to relate a list such as “A, B, or C,” it is intended to mean both “A, B, and C,” used here in an inclusive sense, and “A, B, or C,” used here in an exclusive sense. In addition, as used herein, the term “one or more” can be used, at least in part, depending on the context, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can be understood, at least in part, depending on the context, to convey a single usage or to convey multiple usages. Furthermore, the term "based on" can be understood not as necessarily intended to convey an exclusive set of factors, but rather, again, at least partially, depending on the context, as it may allow for the presence of additional factors that are not necessarily explicitly explained.

[0097] Throughout this specification, references to features, benefits, or similar terms do not imply that all features and benefits that can be realized using the Solution should be included in any single implementation thereof, or are included in any single implementation thereof. Rather, terms referring to features and benefits should be understood to mean that specific features, benefits, or characteristics described in relation to a particular embodiment are included in at least one embodiment of the Solution. Accordingly, discussions of features and benefits, as well as similar terms, throughout this specification may, but not necessarily, refer to the same embodiment.

[0098] The embodiments in this disclosure are for illustrative purposes only. Descriptions of embodiments may include multiple steps, and corresponding methods may include all steps or only a portion of all steps. Additional steps are not excluded from the method unless expressly stated. Different embodiments and the steps in each embodiment may be combined in any order where there is no conflict.

[0099] Furthermore, the described features, benefits, and characteristics of this solution may be combined in any preferred manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that this solution may be practiced without one or more of the specific features or benefits of a particular embodiment. In other instances, additional features and benefits that may not be present in all embodiments of this solution may be recognized in certain embodiments.

Claims

1. A method for wireless communication carried out by a first network element, wherein the method is Receiving a first message from a second network element or wireless device that carries low-power wake-up signal (LP-WUS) auxiliary information associated with the wireless device, wherein the LP-WUS auxiliary information indicates paging information for paging the wireless device. Based on the LP-WUS auxiliary information, the paging information is determined. Methods that include...

2. The aforementioned LP-WUS auxiliary information is, An indication of whether LP-WUS is supported by the wireless device, An indication of whether it is preferable for LP-WUS to be enabled for the wireless device, An indication of whether LP-WUS is applied only within the last serving cell of the wireless device. The ramp-up time indicates the time it takes for the wireless device to wake up from ultra-deep sleep mode. An LP-WUS subgroup identifier indicating an LP-WUS subgroup of the wireless device, wherein the wireless device monitors the LP-WUS based on the LP-WUS subgroup, and the LP-WUS is used to wake up the wireless device, or Paging subgroup identifier indicating the paging subgroup of the aforementioned wireless device The method according to claim 1, comprising at least one of the following.

3. The second network element comprises a core network node, The first message mentioned above is, An NG Application Protocol (NGAP) initial UE context setting request message for requesting UE context setting for the aforementioned wireless device, An NGAP UE context modification request message for requesting a UE context modification for the wireless device, or NGAP paging message for paging the aforementioned wireless device Includes at least one of the following: Receiving the first message means that The method according to claim 1, comprising receiving the first message carrying the LP-WUS auxiliary information from the core network node.

4. Receiving the first message means that The method according to claim 1, comprising receiving a radio resource control (RRC) UE auxiliary information message from the wireless device for reporting information about the wireless device, wherein the RRC UE auxiliary information message carries the LP-WUS auxiliary information.

5. The process further includes optimizing or correcting the LP-WUS auxiliary information and obtaining updated LP-WUS auxiliary information, wherein the updated LP-WUS auxiliary information is Whether or not enabling LP-WUS mode for the aforementioned wireless device is required, Whether it is necessary to disable the LP-WUS mode for the wireless device, An optimized ramp-up time for the wireless device based on the cell configuration of the cell to which the wireless device is accessing or camp-on, or Whether LP-WUS paging is limited to the last serving cell of the wireless device. The method according to claim 1, wherein at least one of the following is shown.

6. The optimized ramp-up time is The cell configuration of the cell to which the wireless device is accessing or camp-on, The power saving mode of the cell that the wireless device is accessing or camping on, Services associated with the aforementioned wireless device, The type of the aforementioned wireless device, The LP-WUS subgroup to which the aforementioned wireless device belongs, or Paging subgroup to which the aforementioned wireless device belongs The method according to claim 5, determined based on at least one of the following.

7. The method according to claim 5, further comprising storing the updated LP-WUS auxiliary information in the UE context of the wireless device.

8. The second network element comprises a core network node, The above method further, The method of claim 5, comprising transmitting a second message to the second network element requesting the second network element to release the wireless device, the second message carrying the updated LP-WUS auxiliary information.

9. The method according to claim 8, wherein the second message includes a UE context release message.

10. Sending the second message means This includes transmitting the second message to the second network element requesting the second network element to release the wireless device into an idle state, the second message carrying the updated LP-WUS auxiliary information, The above method further, Receiving a paging message from the second network element, wherein the paging message carries the updated LP-WUS auxiliary information. Based on the updated LP-WUS auxiliary information, the wireless device is paged. The method according to claim 8, including the method described in claim 8.

11. The first network element comprises a first base station, and the method further comprises The method according to claim 1, comprising transmitting a paging message to a second base station that carries the LP-WUS auxiliary information, the paging message triggering the second base station to page the radio device based on the LP-WUS auxiliary information.

12. The first network element comprises a base station central unit (CU), and the method further comprises The method according to claim 1, comprising transmitting a paging message to a distributed unit (DU) of the base station, the paging message triggering the DU to page the radio devices based on the LP-WUS auxiliary information.

13. Determining the paging information based on the LP-WUS auxiliary information means that In response to the LP-WUS auxiliary information indicating that the wireless device does not support LP-WUS, it is decided not to use LP-WUS paging to page the wireless device. In response to the LP-WUS auxiliary information indicating that the LP-WUS paging is preferred by the wireless device, it is decided to use the LP-WUS paging to paging the wireless device. In response to the LP-WUS auxiliary information indicating that the LP-WUS paging is limited to the last serving cell of the wireless device, it is decided to use the LP-WUS paging to page the wireless device only within the last serving cell, or otherwise to use the LP-WUS paging to page the wireless device within all paging cells. Based on the LP-WUS auxiliary information, a waiting period is determined, and after transmitting the LP-WUS to the wireless device, a paging message is transmitted to the wireless device with a delay, wherein the delay is equal to or greater than the waiting period. Based on the LP-WUS auxiliary information, determine the LP-WUS subgroup to which the wireless device belongs, and the wireless device monitors the LP-WUS based on the LP-WUS subgroup, or Based on the LP-WUS auxiliary information, the paging subgroup to which the wireless device belongs is determined, and the wireless device monitors the paging messages based on the paging subgroup. The method according to claim 1, comprising at least one of the following.

14. The method according to claim 13, wherein the LP-WUS is used to wake up the radio device by triggering the radio device to turn on the main radio, and the main radio is used to receive the paging message.

15. The method of claim 5, further comprising sending a third message to the wireless device to trigger the wireless device to transition to an idle or inactive state, wherein the third message carries the updated LP-WUS auxiliary information.

16. The method according to claim 15, wherein the third message includes an RRC release message.

17. The first network element comprises a base station, and the base station is gNodeB (gNB), eNodeB (eNB), ng-eNodeB (ng-eNB), or NodeB The method according to claim 1, comprising one of the following.

18. A method for wireless communication performed by a wireless device, wherein the method is The first network element includes transmitting a first message that carries low-power wake-up signal (LP-WUS) auxiliary information associated with the wireless device, wherein the LP-WUS auxiliary information indicates paging information for paging the wireless device, and the LP-WUS auxiliary information is An indication of whether LP-WUS is supported by the wireless device, An indication of whether it is preferable for LP-WUS to be enabled for the wireless device, An indication of whether LP-WUS is applied only within the last serving cell of the wireless device. The ramp-up time indicates the time it takes for the wireless device to wake up from ultra-deep sleep mode. An LP-WUS subgroup identifier indicating an LP-WUS subgroup of the wireless device, wherein the wireless device monitors the LP-WUS based on the LP-WUS subgroup, and the LP-WUS is used to wake up the wireless device, or Paging subgroup identifier indicating the paging subgroup of the aforementioned wireless device A method that includes at least one of the following.

19. The method according to claim 18, wherein the first message includes an RRC UE auxiliary message.

20. The aforementioned paging information is, LP-WUS paging using LP-WUS, Paging without using LP-WUS The LP-WUS paging is limited to the last serving cell of the wireless device. The LP-WUS paging is not limited to the last serving cell of the wireless device. The LP-WUS subgroup associated with the aforementioned wireless device, The paging subgroup associated with the aforementioned wireless device, or The ramp-up time of the wireless device, wherein the ramp-up time is the period from when the wireless device receives the LP-WUS until the main wireless of the wireless device is turned on. The method according to claim 18, wherein at least one of the following is shown.

21. The method according to claim 18, further comprising receiving a second message from the first network element, which includes updated LP-WUS auxiliary information optimized by the first network element based on the LP-WUS auxiliary information.

22. The method according to claim 21, wherein the second message includes an RRC release message.

23. Receiving an LP-WUS from the first network element that triggers the wireless device to wake up from sleep mode, The first network element receives a paging message, which is received with a delay after the LP-WUS is received. The method according to claim 18, further comprising:

24. The method according to claim 23, wherein the delay is determined by or associated with the ramp-up time, and the delay is equal to or greater than the ramp-up time.

25. After receiving the LP-WUS, the method further includes turning on the main radio of the wireless device. Receiving the paging message includes receiving the paging message by using the main radio. The method according to claim 23.

26. The wireless device is in an idle or inactive state, and the method further, In response to the wireless device supporting or preferring LP-WUS paging, The main radio of the aforementioned wireless device is turned off and enters ultra-deep sleep mode, To monitor the aforementioned LP-WUS, In response to the LP-WUS paging being applied only to the last serving cell of the wireless device, To monitor the LP-WUS only within the last serving cell, In response to the fact that the LP-WUS paging is not limited to the last serving cell of the wireless device, The LP-WUS is monitored in all cells that the wireless device accesses or camps on. In response to the wireless device belonging to the LP-WUS subgroup, Monitoring the LP-WUS based on the LP-WUS subgroup, or In response to the wireless device belonging to a paging subgroup, Based on the aforementioned paging subgroups, monitor the paging messages. The method according to claim 18, further comprising one of the following.

27. A device for wireless communication comprising a memory for storing computer instructions and a processor for communicating with the memory, wherein when the processor executes the computer instructions, the processor is configured to implement the method according to any one of claims 1 to 26.

28. A computer program product comprising a non-temporary computer-readable program medium, wherein computer code is stored on the non-temporary computer-readable program medium, and the computer code, when executed by one or more processors, causes the one or more processors to implement the method according to any one of claims 1 to 26.

Images