Low power wake-up radio and main radio on and off mechanism

By introducing the on and off model in the 3GPP system, controlling the state of LP-WUR and MR, the problem of difficulty in optimizing power consumption and delay is solved, and the low power management of UE is realized, which is suitable for applications such as IoT devices.

CN118945776APending Publication Date: 2024-11-12APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410565638.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-09
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The existing low-power wake-up radio components (LP-WUR) and main radio components (MR) are not clearly identified when they are turned on or off, making it difficult to optimize power consumption and delays simultaneously.

Method used

By introducing an open model and a closed model, specifically including the first and second open models and the closed model, the open and off states of LP-WUR and MR are controlled using external and internal trigger events, ensuring that under different network states and battery life requirements Achieve reasonable power management.

Benefits of technology

It effectively reduces the power consumption of user equipment (UE) while maintaining low latency. It is suitable for power-sensitive devices such as IoT devices, extends battery life and improves communication efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945776A_ABST
    Figure CN118945776A_ABST
Patent Text Reader

Abstract

The invention relates to a low power wake-up radio and main radio on and off mechanism. A user equipment (UE) may include a primary radio (MR) and a low power wake-up radio (LR). The UE may coordinate periods for the MR and the LR to turn on and off. For example, the UE may enter a deep sleep state by turning off a primary radio (MR) of the UE and turning on a low power wake-up radio (LR) of the UE. The MR may receive an event indication from the LR to turn on the MR. The MR may start and perform a process according to an event corresponding to the event indication.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates generally to wireless communication systems, including coordination of low power wake-up radio components and main radio components in user equipment devices. Background Art

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless communication devices. For example, wireless communication system standards and protocols may include the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for wireless local area networks (WLANs) (commonly referred to within industry organizations as WLANs). ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) for communication between base stations (sometimes also referred to as RAN nodes, network nodes, or simply nodes) of the RAN and wireless communication devices referred to as user equipment (UE). 3GPP RANs may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN can use one or more radio access technologies (RATs) for communication between base stations and UEs. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes referred to as LTE), and NG-RAN implements NR RAT (the NR RAT is sometimes referred to as 5G RAT, 5G NR RAT, or NR in this document). In some deployments, E-UTRAN may also implement NR RAT. In some deployments, NG-RAN may also implement LTE RAT.

[0005] The base station used by the RAN may correspond to the RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as an evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (also sometimes referred to as a gNodeB or gNB).

[0006] The RAN provides communication services together with external entities through its connection with the Core Network (CN). For example, E-UTRAN may utilize the Evolved Packet Core (EPC) and NG-RAN may utilize the 5G Core Network (5GC). BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0008] Figure 1A A UE including LR and MR modules according to some embodiments is shown.

[0009] Figure 1B Two states of a UE according to some embodiments are shown.

[0010] Figure 2 A simplified signal flow diagram for changing the LR to an open state according to some embodiments is shown.

[0011] Figure 3 A simplified signal flow diagram for entering a deep sleep state (ie, changing the MR to an off state) according to some embodiments is shown.

[0012] Figure 4 A signal flow diagram for leaving a deep sleep state (ie, changing the MR to an on state) based on the LR sending a trigger to the MR is shown according to some embodiments.

[0013] Figure 5 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, turning on MR) based on a LP-WUS from a network node while the UE is in RRC_IDLE / INACTIVE state according to some embodiments.

[0014] Figure 6 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, turning on MR) based on a LP-WUS from a network node while the UE is in a connected state according to some embodiments.

[0015] Figure 7 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, turning on MR) based on LR detecting that the radio quality of a current serving cell is less than a threshold according to some embodiments.

[0016] Figure 8 A simplified signal flow diagram is shown for leaving or entering a deep sleep state (ie, turning the MR on and off) based on the LR detecting the radio quality of the current serving cell according to some embodiments.

[0017] Fig. 9 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, turning on MR) based on the LR determining that a NAS periodic registration timer has expired, according to some embodiments.

[0018] Fig.10 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, turning on MR) based on the LR determining that the AS RNAU timer has expired, according to some embodiments.

[0019] Fig.11 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, turning on MR) based on the LR determining that the DRX On Duration timer has expired according to some embodiments.

[0020] Fig.12 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, turning on MR) based on the state of LR, according to some embodiments.

[0021] Fig.13 A simplified signal flow diagram for leaving a deep sleep state (ie, turning on MR) based on an internal trigger in MR is shown according to some embodiments.

[0022] Fig.14 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, MR on) based on an external trigger from the LR when the UE is in an idle / inactive state according to some embodiments.

[0023] Fig.15 A simplified signal flow diagram is shown for leaving a deep sleep state (ie, MR on) based on an external trigger from the LR while the UE is in a connected state according to some embodiments.

[0024] Fig.16 A simplified signal flow diagram for entering a deep sleep state (ie, turning off MR) based on data activity is shown in accordance with some embodiments.

[0025] Fig.17 A simplified signal flow diagram is shown for entering a deep sleep state (ie, turning off MR) based on a command from a network node according to some embodiments.

[0026] Fig.18 A simplified signal flow diagram for entering a deep sleep state (ie, turning off MR) based on a UE RRC state transition according to some embodiments is shown.

[0027] Fig.19 A simplified signal flow diagram for entering a deep sleep state (ie, turning off MR) based on a DRX off state according to some embodiments is shown.

[0028] Fig. 20 A simplified signal flow diagram is shown in which LP-WUS functionality is enabled / activated based on an indication / configuration from the network side according to some embodiments.

[0029] Fig.21 A simplified signal flow diagram is shown for activating / enabling LP-WUS functionality based on RRC state according to some embodiments.

[0030] Fig. 22 A signal flow diagram for leaving a deep sleep state (ie, turning off LR) based on an indication from MR according to some embodiments is shown.

[0031] Fig.23 A signal flow diagram is shown for leaving a deep sleep state (ie, shutting down LR) when the LP-WUS function is not functioning properly according to some embodiments.

[0032] Fig.24 A flowchart of a method for a UE according to an embodiment of the present invention is shown.

[0033] Fig.25 A flowchart of a method for a UE according to an embodiment of the present invention is shown.

[0034] Fig.26 An exemplary architecture of a wireless communication system according to embodiments disclosed herein is shown.

[0035] Fig. 27 A system for performing signaling between a wireless device and a network device according to embodiments disclosed herein is shown. DETAILED DESCRIPTION

[0036] Various embodiments are described with reference to user equipment (UE). However, reference to UE is provided for illustration purposes only. The exemplary embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, UE as described herein is used to represent any suitable electronic component.

[0037] Two goals of wireless communication systems are to reduce power consumption and reduce latency. In some embodiments, in order to reduce UE power consumption, a discontinuous reception (DRX) cycle with a large value can be used to extend UE battery life. A large value DRX cycle may be referred to as extended DRX (eDRX). Extended DRX allows the UE to remain in a low power state for an extended period of time by reducing the frequency at which the UE communicates with the network. For paging monitoring and radio resource management (RRM) measurements, idle / inactive UEs are only required to wake up once per DRX cycle.

[0038] However, the eDRX mechanism cannot always meet the requirements of both long battery life and low latency. The longer the DRX cycle, the lower the UE power consumption, but it will introduce longer service delays. The extended period between two consecutive network connection attempts may introduce higher latency than expected.

[0039] Therefore, it may be desirable to introduce functionality to wake up the UE when it is paged by a network node. By waking up when paged, the UE power consumption can be significantly reduced while maintaining low latency. This can be achieved by using a wake-up signal (WUS) to trigger the main radio component (MR) and a separate receiver with the ability to monitor the wake-up signal with ultra-low power consumption. The main radio component is used for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on.

[0040] For example, the UE may use a low power wake-up radio (LP-WUR), also referred to herein as LR. LP-WUR is a feature that enables UEs in a wireless network to save power by remaining in a low power sleep state until a wake-up signal is received. When the wake-up signal is detected, the UE wakes up to establish a connection with the network node using the main radio to transmit or receive data, and then returns to its low power state.

[0041] LP-WUR is particularly useful for IoT (Internet of Things) devices, which may need to transmit small amounts of data sporadically and preserve battery life as much as possible. By using LP-WUR, these devices can remain in a low-power state for extended periods of time, saving energy until they need to transmit or receive data.

[0042] Multiple power saving schemes are supported in 3GPP. In 3GPP Release 15, Connected Mode DRX (C-DRX) for the connected state and Idle Mode DRX (I-DRX) for the idle / inactive state were introduced. In 3GPP Release 16, WUS for DRX active time control in the connected state was introduced. A new DCI was introduced to indicate whether the UE needs to wake up at each DRX on duration. If the new UE indicates that the UE does not need to wake up, the UE will not wake up during the associated DRX on duration. In addition, in Release 16, RRM measurement relaxation in the idle / inactive state was introduced. If the UE is in a low mobility state, or the UE is not at the cell edge, the UE can relax the RRM measurements for idle / inactive mobility.

[0043] In 3GPP Release 17, paging optimization (Permanent Equipment Identifier (PEI) and paging subgroups) were introduced. PEI is a DCI used to inform the UE whether there is an actual paging transmission at the associated paging opportunity (PO). For paging subgroups, the UE is further divided into paging subgroups, and the paging subgroup information is carried in the paging scheduling information. In Release 17, radio link monitoring (RLM) and beam failure detection (BFD) relaxation in the connected state are introduced. In addition, the eDRX mechanism is introduced, where the DRX cycle is {2.56sec, 5.12s, 10.24s, 20.48s,…, 1024x1024 (2.91hrs)}.

[0044] Figure 1A A UE 106 including LR 108 and MR 110 modules according to some embodiments is shown. LR 108 enables UE 106 to save power by remaining in a low-power sleep state until it receives a wake-up signal. When the wake-up signal is detected, UE 106 can return to a normal state and communicate with a network node using MR. The low-power wake-up signal of LR 108 can be used for power-sensitive small form factor devices, including IoT use cases (such as industrial sensors, controllers) and wearable devices, extended reality (XR) devices, smart glasses, and smart phones.

[0045] The hardware module may include MR 110 and a separate LR 108. MR 110 may be a transmit and receive module that operates for new radio (NR) signals and channels other than signals and channels related to low power wake-up. LR 108 may be a receive module that operates for receiving and processing signals and channels related to low power wake-up. MR 110 and LR 108 may support multiple RRC states. Both RRC idle / inactive mode and connected mode may be studied as part of low power (LP) WUS / WUR.

[0046] In some embodiments, the LP-WUS may be sent from a network node over a Uu interface. A wireless communication system may include a UE, a radio access network (NG-RAN), and a core network. The main entity of the NG-RAN may be a network node. The radio interface between the network node and the UE may be referred to as a Uu interface.

[0047] Figure 1B Two states of the UE 106 are shown according to some embodiments. In the illustrated embodiment, when the MR 110 is in the on state, the UE 106 is considered to be operating in the normal state 104. When the MR 110 is in the off state, the UE 106 is considered to be operating in the deep sleep state 102.

[0048] Although using LR 108 can reduce power consumption while maintaining latency requirements, there are currently several unresolved issues with using LR 108 and MR 110. For example, it is not yet clear when to turn on / off LR 108 and MR 110. Embodiments herein provide methods, apparatus, and systems that specify a process for turning on and off LR 108 and MR 110.

[0049] Figure 2 A simplified signal flow diagram 200 for turning LR 108 to an open state is shown according to some embodiments. MR open control can be triggered by one or both of an external trigger and an internal trigger. In the illustrated embodiment, LR 108 starts in a closed state 202, and LR 108 is in an open state 208.

[0050] For example, some embodiments may use a first opening model (referred to herein as opening model 1). For embodiments using opening model 1, LR 108 may open only based on an external trigger from LR 108. Thus, in opening model 1, LR 108 may be responsible for determining all events that should trigger LR 108 to enter the open state 204. For example, as shown, LR 108 may detect event trigger 210. Event trigger 210 may correspond to an event, and upon occurrence of the event, LR 108 provides event indication 206 to LR 108.

[0051] For the start-up model 1, there may be several events that can trigger the LR 108 to send the event indication 206. In some embodiments, the event may include when the LR 108 receives an indication from the network side in the Uu interface. The indication may be the LP-WUS of the UE. In some embodiments, the event may include when the LR 108 detects that the radio quality of the current serving cell has deteriorated. In some embodiments, the event may include when the LR 108 detects that some timers have timed out. Therefore, the LR 108 may include some timer functions. In some embodiments, the event may include other events that require the LR 108 to be turned on to work, such as failure or error conditions. When the LR 108 receives the event indication 206, the LR 108 turns on and initiates a process according to the corresponding event (e.g., receiving, transmitting, measuring, etc.).

[0052] Some embodiments may use a second turn-on model (referred to herein as turn-on model 2). For embodiments using turn-on model 2, LR 108 may turn on based on external triggers from LR 108 and internal triggers from the LR itself. For external triggers, LR 108 may determine when a particular event occurs. For example, LR 108 may monitor an indication from the network (e.g., an LP-WUS signal associated with the UE) and provide event indication 206 to LR 108 upon receipt of the indication. In addition, LR 108 may detect when the radio quality of the current serving cell deteriorates and send event indication 206. In some embodiments, LR 108 may detect other events when LR 108 is required to turn on to operate, such as a fault or error condition, and send event indication 206. When LR 108 receives event indication 206, LR 108 turns on and initiates a process according to the corresponding event (e.g., reception, transmission, measurement, etc.).

[0053] For internal triggers, LR 108 may not be completely shut down when in the deep sleep state. For example, during the deep sleep state, LR 108 may maintain some periodic cellular timers. When LR 108 determines that one of these periodic cellular timers has timed out, LR 108 turns on and initiates a process based on the corresponding event (e.g., reception, transmission, measurement, etc.). Thus, LR 108 may enter the turned-on state and determine which process to initiate based on both external triggers and internal situations / triggers.

[0054] Figure 3A simplified signal flow diagram 300 for changing MR 110 to the closed state is shown according to some embodiments. MR closed control can be triggered by the MR itself and / or based on the LR indication. In the illustrated embodiment, MR 110 starts in the open state 304. After occurrence 310, MR 110 sends a MR closed indication 308 to LR 108 and enters the closed state 302. MR closed indication 308 can notify LR 108 that MR 110 is entering the closed state 302, and LR 108 can enter the open state 306 and begin operation.

[0055] Some embodiments may use a first shutdown model (referred to herein as shutdown model 1). For embodiments using shutdown model 1, LR 108 may control when it is shut down. 310 may be caused by multiple events. In some embodiments, the event may include when MR 110 detects that there is no activity and predicts that there will be no activity after a period of time. In some embodiments, the event may include when MR 110 receives a NW command to turn. In some embodiments, the event may include when a UE RRC state transition occurs (e.g., entering an RRC idle / inactive state). When MR 110 detects one of these events, MR 110 sends a MR OFF indication 308, and LR 108 begins to work.

[0056] Some embodiments may use a second shutdown model (referred to herein as shutdown model 2). For embodiments using shutdown model 2, MR 110 may be shut down based on an indication from LR 108. In some embodiments, MR 110 may be shut down based on an external trigger from LR 108 and an internal trigger from the LR itself.

[0057] Figure 4 A signal flow diagram 400 is shown for turning MR 110 on based on LR 108 sending a trigger (e.g., indication 404) to MR 110 according to some embodiments. When MR 110 is off, LR 108 may perform one or more of the following operations. LR 108 may monitor and detect LP-WUS 402. LR 108 may perform measurements based on LP-WUS 402. LR 108 may maintain some access stratum / non-access stratum (AS / NAS) periodic timers.

[0058] In some embodiments, LR 108 sends indication 404 to MR 110 when the following events occur. The first event may be when LR 108 receives a WUS from the UE. The second event may be when LR 108 detects that the radio quality of the current serving cell is less than a threshold. The third event may be when LR 108 detects that a certain timer has expired.

[0059] For the first event, LR 108 may receive LP-WUS 402 of the UE and send an indication to MR 110. MR 110 turns on and starts operating according to the radio resource control (RRC) state. In RRC_CONNECTED, UE MR 110 turns on and enters the DRX on state according to a specific timing or within the next available on duration. In RRC_IDLE / INACTIVE, UE MR 110 turns on and starts receiving paging / PEI and performs measurements according to the PO location of the UE.

[0060] For the second event, LR 108 may detect that the radio quality of the current serving cell is less than a threshold. In some embodiments, LR 108 performs measurements based on LP-WUS 402 signaling. When the quality of LP-WUS 402 is less than a threshold, MR 110 may be turned on for measurement purposes. The threshold may be configured by the network.

[0061] For the third event, LR 108 may maintain a cellular timer and detect a timer timeout condition. For a periodic cellular timer, the timer runs on LR 108, and when the timer times out, LR 108 provides an indication 404 to MR 110 along with the corresponding event. For example, LR 108 may maintain a NAS periodic registration timer, and when the timer times out and MR 110 is turned off, LR 108 indicates the timer timeout event to MR 110, and MR 110 will start and trigger a registration procedure. For another example, when the UE is in an inactive state, LR 108 may maintain a RAN-based Notification Area Update (RNAU) timer, and when the timer times out and MR 110 is turned off, LR 108 indicates the RNAU timer timeout to MR 110, and MR will start and trigger an RNAU procedure. For another example, when the UE is in the connected state, LR 108 maintains the DRX on-duration timer, and when the on-duration timer is about to start and MR 110 is turned off, LR 108 indicates the on-duration timer start event to MR 110, and MR 110 may turn on and enter the DRX on state.

[0062] Figures 5 to 12 A further signal flow diagram of the above events using the opening model 1 is shown. Figures 5 to 12 Any or all embodiments described.

[0063] Figure 5A simplified signal flow diagram 500 is shown for turning on MR 110 based on LP-WUS 504 from network node 502 when the UE is in RRC_IDLE / INACTIVE state. As shown, LR 108 receives LP-WUS 504 from the UE. LP-WUS 504 indicates that the UE should wake up. LR 108 sends indication 506 to MR 110. Indication 506 may inform MR 110 of the receipt of LP-WUS 504. MR 110 turns on and begins operating according to the RRC state. In RRC_IDLE / INACTIVE state, MR 110 turns on and begins receiving paging / PEI from network node 502 and performs measurements according to its PO location. Network node 502 may also send broadcast signals that MR 110 may receive.

[0064] Figure 6 A simplified signal flow diagram 600 for turning on MR 110 based on LP-WUS 602 from network node 502 when the UE is in a connected state is shown. As shown, LR 108 receives LP-WUS 602 from the UE. LP-WUS 602 indicates that the UE should wake up. LR 108 sends an indication 604 to MR 110. Indication 604 may inform MR 110 of the receipt of LP-WUS 602. MR 110 turns on and begins operation according to the RRC state. In the connected state, MR 110 turns on and enters the DRX on state according to a specific timing or within the next available on duration. MR 110 may start PDCCH monitoring and receive UE-specific data transmissions from network node 502.

[0065] Figure 7 A simplified signal flow diagram 700 is shown for turning on MR 110 based on LR 108 detecting that the radio quality of the current serving cell is less than a threshold according to some embodiments. As shown, LR 108 may perform measurements 704 based on LP-WUS 702 from network node 502.

[0066] The trigger condition for turning on MR 110 may be based on how the measurement 704 compares to a threshold. LR 108 may compare the measurement 704 to the threshold. When the quality of LP-WUS 702 is less than the threshold, LR 108 will trigger MR on indication 706. Indication 706 may indicate that LR 108 has detected a low radio quality event.

[0067] The thresholds may be configured by the network node 502. Configuration of LP-WUS based measurements and threshold / condition evaluation may be pre-provided to the LR by the MR 110. For example, before the MR 110 is turned off, the network node 502 may provide the LR 108 with measurement configuration details that the MR 110 may provide.

[0068] Upon receiving the indication 706, MR 110 may turn on and initiate RRM measurements on both the serving cell and the neighboring cells for mobility purposes. In some embodiments, MR 110 first checks the serving cell quality based on SSB / CSI-RS 708 measurements and decides whether to initiate measurements on neighboring cells based on the measurements. In some embodiments, MR 110 directly initiates measurements on neighboring cells.

[0069] Figure 8 A simplified signal flow diagram 800 is shown for turning MR 110 on and off based on radio quality of a current serving cell detected by LR 108 according to some embodiments. As shown, LR 108 may perform measurements 804 based on LP-WUS 802 from network node 502.

[0070] The trigger condition for turning on MR 110 may be based on how the measurement 804 compares to a threshold. LR 108 may compare the measurement 804 to the threshold. When the quality of LP-WUS 802 is less than the threshold, LR 108 will trigger MR on indication 806. Indication 806 may indicate that LR 108 has detected a low radio quality event.

[0071] The thresholds may be configured by the network node 502. Configuration of LP-WUS based measurements and threshold / condition evaluation may be pre-provided to the LR by the MR 110. For example, before the MR 110 is turned off, the network node 502 may provide the LR 108 with measurement configuration details that the MR 110 may provide.

[0072] Upon receiving indication 806, MR 110 may turn on and initiate RRM measurements on both the serving cell and the neighboring cells for mobility purposes. In some embodiments, MR 110 first checks the serving cell quality based on SSB / CSI-RS measurements and decides whether to initiate measurements on neighboring cells based on the measurements. In some embodiments, MR 110 directly initiates measurements on neighboring cells.

[0073] In addition, in some embodiments, LR 108 may continue to monitor LP-WUS 802 (e.g., second measurement 810). When LR 108 detects that the quality of LP-WUS 802 is greater than a threshold value for a period of time, LR 108 may send a second indication 808 to notify MR 110 to cancel the quality event or send an MR shutdown indication. MR 110 may shut down based on the second indication 808.

[0074] Fig. 9A simplified signal flow diagram 900 for enabling MR 110 based on LR 108 determining that a NAS periodic registration timer has expired according to some embodiments is shown. In some embodiments, LR 108 may maintain a cellular timer and detect a timer timeout condition. For example, a periodic cellular timer may run on LR 108. When a timer expires, LR 108 may provide an indication (e.g., indication 906) to MR 110 including a corresponding event.

[0075] For example, as shown, MR 110 may be turned off 902. LR 108 maintains 904 a NAS periodic registration timer. When MR 110 is turned off, LR 108 may determine when the timer expires. LR 108 sends an indication 906 to MR 110, which indicates the timer timeout event to MR 110, and MR 110 may turn on 908 and trigger a registration procedure. MR 110 may initiate 910 a NAS procedure and perform a routing area update / tracking area update (RAU / TAU) procedure 912 with network node 502.

[0076] Fig.10 A simplified signal flow diagram 1000 is shown for turning on MR 110 based on LR 108 determining that the AS RNAU timer has expired according to some embodiments. When the UE is in an inactive state, LR 108 may maintain the RNAU timer, and when the timer expires and MR 110 is turned off, LR 108 may indicate to MR 110 that the RNAU timer has expired, causing MR 110 to turn on and trigger RNAU RNA process 1012.

[0077] For example, as shown, MR 110 may shut down 1002. LR 108 maintains 1004 the AS RNAU timer. When MR 110 shuts down, LR 108 may determine when the timer expires. LR 108 may send an indication 1006 to MR 110 indicating the timer timeout event to MR 110, and MR 110 may start 1008 and trigger the RNAU process. MR 110 may initiate 1010 the RNAU process and perform the RNA process 1012 with the network node 502.

[0078] Fig.11A simplified signal flow diagram 1100 is shown for turning on MR 110 based on LR 108 determining that the DRX on-duration timer has expired according to some embodiments. When the UE is in an active state, LR 108 may maintain a DRX on-duration timer (C-DRX), and when the on-duration timer is about to start and MR 110 is off, LR 108 may indicate an on-duration timer start event to MR 110, and MR 110 may turn on and enter the DRX on state.

[0079] For example, as shown, MR 110 may be turned off 1102. LR 108 may maintain 1104 a C-DRX timer. When MR 110 is turned off, LR 108 may determine when the timer is to be started. LR 108 may send an indication 1106 to MR 110 indicating the timer start event to MR 110, and MR 110 may be turned on 1108 and enter 1110 a DRX on state to perform PDCCH monitoring 1112.

[0080] Fig.12 A simplified signal flow diagram 1200 for turning on MR 110 based on the state of LR 108 is shown. As shown, there may be other events that require MR 110 to turn on to work. For example, when LR 108 has some problems, does not work well, or needs to be turned off 1202, LR 108 can notify MR 110 using LR closed indication 1204. LR closed indication 1204 can notify MR 110 that LR 108 is shutting down and cause MR 110 to turn on. MR 110 can notify network node 502 that LR 108 is shutting down via disable LP-WUS indication 1206 and cause network node 502 to disable LP-WUS function.

[0081] In some cases, LR 108 may shut down before notifying MR 110. Therefore, in some embodiments, MR 110 may detect LR failure on its own. In addition, based on failure detection, MR 110 may turn on to enter a normal working state and notify network node 502 to disable LP-WUS mode.

[0082] In some embodiments, when the UE is in an idle / inactive state, the UE may suspend indication transmission (e.g., disable LP-WUS indication 1206) until the UE resumes / establishes an RRC connection due to other events.

[0083] Figures 13 to 15 An exemplary signal flow diagram using the opening model 2 is shown. The opening model 2 can open the MR based on the LR indication and the MR internal trigger. Figures 13 to 15Any or all embodiments described. As shown in these figures, embodiments can turn on the MR based on an external trigger or an internal trigger from the LR. The internal trigger can be based on a timer. In some embodiments, a timer can be maintained on the MR.

[0084] For example, Fig.13 A simplified signal flow diagram 1300 is shown for turning on MR 110 based on an internal trigger in MR 110. In the illustrated embodiment, the MR 110 internal trigger is based on an RNAU timer 1304 maintained by MR 110. In addition, other timers (e.g., NAS periodic registration timer and C-DRX timer) may be maintained by MR 110. MR 110 is not completely turned off, but still maintains some periodic cellular timers, as well as functionality such as periodic timers that may trigger UE NAS / AS procedures or trigger the UE to enter DRX on state.

[0085] When the UE is in an inactive state, MR 110 may maintain an RNAU timer, and when the timer expires and MR 110 is turned off, MR 110 may turn on. MR 110 may send an indication 1302 to LR 108 indicating that MR 110 is turned on. Based on an internal trigger, MR 110 wakes up and initiates a process associated with the timer. In the illustrated embodiment, MR 110 initiates 1306 an RNAU process and performs an RNA process 1308 with network node 502.

[0086] Fig.14 A simplified signal flow diagram 1400 is shown for MR 110 to turn on based on an external trigger from LR 108 when the UE is in an idle / inactive state according to some embodiments. As shown, MR 110 may be turned off and in an idle / inactive state when LR 108 receives LP-WUS 1402 from network node 502. LP-WUS 1402 indicates that the UE should wake up. LR 108 sends an indication 1404 to MR 110. Indication 1404 may inform MR 110 that LP-WUS 1402 was received.

[0087] Based on the external trigger from LR 108, MR 110 may consider the indication along with its current RRC state or other context to decide the UE action in the Uu interface. As shown, in RRC_IDLE / INACTIVE state, MR 110 may turn on and enable the I-DRX mechanism for paging reception. MR 110 may receive paging / SIB from network node 502.

[0088] Fig.15A simplified signal flow diagram 1500 is shown for MR 110 to start based on an external trigger from LR 108 while the UE is in a connected state according to some embodiments. As shown, MR 110 may maintain a C-DRX timer.

[0089] LR 108 may receive LP-WUS 1502 from the UE. LP-WUS 1502 indicates that the UE should wake up. LR 108 sends indication 1504 to MR 110. Indication 1504 may inform MR 110 of the receipt of LP-WUS 1502. MR 110 turns on and starts operating according to the RRC state. Based on an external trigger from LR 108, MR 110 may consider the indication together with its current RRC state or other context to decide UE actions in the Uu interface. In the connected state, MR 110 turns on and enters the DRX on state according to a specific timing or within the next available on duration. MR 110 may start PDCCH monitoring and receive UE-specific data transmissions from network node 502.

[0090] Figures 16 to 19 Four events that may cause the MR to close are shown. Embodiments may combine one or more of these closing events and opening models described herein to open and close the MR. The MR may be controlled to close itself. For example, in some embodiments, when a Figures 16 to 19 MR may decide to shut down when any of the four events shown in FIG.

[0091] Fig.16 A simplified signal flow diagram 1600 for shutting down MR 110 based on data activity is shown according to some embodiments. A first event 1602 for MR 110 shutting down may occur when MR 110 detects an absence of activity and predicts an absence of activity after a period of time. MR 110 may determine that the first event 1602 has occurred based on a timer at which it detects no further data activity. For example, MR 110 may determine that a data inactivity timer has expired, or that the UE remains in a DRX off state for a period of time, and shut down based on the timer expiring. MR 110 may send an indication 1604 to LR 108 to signal MR 110 shutting down.

[0092] Fig.17A simplified signal flow diagram 1700 for shutting down MR 110 based on a command from network node 502 according to some embodiments is shown. A second event for MR 110 shutting down may occur when MR 110 receives a network command 1702 to shut down. Network node 502 may explicitly indicate that there is no further data transmission, or indicate that the UE will shut down MR 110 or enter a deep sleep state. MR 110 may send an indication 1704 to LR 108 to signal MR 110 shut down.

[0093] Fig.18 A simplified signal flow diagram 1800 for shutting down MR 110 based on a UE RRC state transition according to some embodiments is shown. A third event for shutting down MR 110 may occur based on a UE RRC state transition. For example, when entering an RRC idle / inactive state, MR 110 may be shut down. MR receives RRC release 1802 from network node 502. When the UE enters an RRC idle / inactive state, the UE may shut down MR 110, and this may be explicitly indicated by network node 502 in RRC release. MR 110 may send an indication 1804 to LR 108 to signal that MR 110 is shut down.

[0094] Fig.19 A simplified signal flow diagram 1900 for shutting down MR 110 based on a DRX off state according to some embodiments is shown. A fourth event 1902 for shutting down MR 110 may occur when MR 110 detects that a UE in a connected state enters a DRX off state. When the UE enters the DRX off state, the UE may shut down MR 110. Shutdown based on entering a DRX off state may be configured by a network node. MR 110 may send an indication 1904 to LR 108 to signal that MR 110 is shut down.

[0095] Figure 20 to Figure 23 The situations when the UE can turn LR on and off are shown. The embodiments shown can be combined with each other and with other embodiments discussed herein. In some embodiments, the default LR state can be LR off.

[0096] LR can be turned on based on MR indication. In the first case, LR can be turned on based on MR indication / configuration. For example, when MR receives LP-WUS signal configuration or enable indication, it can trigger the turning on of LR. When MR receives such a trigger, MR can notify LR to turn on. MR can provide LR with LP-WUS configuration for UE's LP-WUS detection and provide events / timers that LR needs to maintain. In the second case, LR can be turned on based on MR status.

[0097] In some embodiments, the LR may be shut down when the LR receives a shutdown indication from the MR. The MR may notify the LR to shut down in the following cases. In the first case, when the UE moves to a new cell that does not support LP-WUS, the MR may notify the LR to shut down. In the second case, when the UE detects / predicts that there will be no activity in the Uu interface for a period of time in the future, the MR may notify the LR to shut down. In the third case, when the UE receives a network indication to shut down the LR, the MR may notify the LR to shut down. In the fourth case, when there is a UE RRC state transition (for example, entering the RRC idle / inactive state), the MR may notify the LR to shut down. In the fifth case, when the UE MR initiates a special process (UE connection reestablishment), the MR may notify the LR to shut down. When the LR receives a shutdown indication from the MR, the LR is shut down.

[0098] In some embodiments, when the LR may not be functioning well, the LR may be turned off. Fig.12 As shown, the LR may shut down and send an indication to the MR.

[0099] Fig. 20 A simplified signal flow diagram 2000 is shown according to some embodiments, wherein LR 108 is turned on based on MR indication / configuration. MR 110 receives a trigger from network node 502 to turn on LR 108. For example, in the illustrated embodiment, MR 110 receives message 2002 from network node 502. Message 2002 may include LP-WUS signal configuration and / or enable indication. MR 110 notifies LR 108 to turn on via LR turn-on indication 2004. In some embodiments, MR 110 provides LR 108 with LP-WUS configuration for LP-WUS detection of UEs and provides events / timers that LR 108 should maintain. These configuration details may be included in LR turn-on indication 2004. When LR 108 receives LR turn-on indication 2004, LR 108 turns on and MR 110 turns off.

[0100] Fig.21 A simplified signal flow diagram 2100 is shown in accordance with some embodiments, wherein LR 108 is turned on based on MR status. MR 110 receives configuration 2102 from network node 502 for LP-WUS. Configuration 2102 may include LP-WUS signal configuration and / or enable indication. MR 110 may send LR enable indication 2104 to LR 108. LR enable indication 2104 may include LP-WUS configuration to LR 108 for LP-WUS detection of the UE, including events / timers that LR 108 should maintain.

[0101] When MR 110 is off, MR 110 will notify LR to turn on. For example, MR 2106 may send an on indication 2106 to LR 108. When LR 108 receives the on indication 2106, LR 108 turns on and MR 110 turns off.

[0102] Fig. 22 A signal flow diagram 2200 is shown for closing LR 108 based on an indication from MR 110 according to some embodiments. As shown, MR 110 turns on and decides 2202 to turn on normal state operation. MR 110 may send an LR close indication 2204 to LR 108 causing LR 108 to close.

[0103] In the following cases, MR 110 may notify LR 108 to shut down. In the first case, when the UE moves to a new cell that does not support LP-WUS, MR 110 may notify LR 108 to shut down. In the second case, when the UE detects / predicts that there will be no activity in the Uu interface for a period of time in the future, MR 110 may notify LR 108 to shut down. In the third case, when the UE receives a network indication to shut down LR 108, MR 110 may notify LR 108 to shut down. In the fourth case, when there is a UE RRC state transition (for example, entering RRC idle / inactive state), MR 110 may notify LR 108 to shut down. In the fifth case, when the UE MR 110 initiates some special procedures (UE connection reestablishment), MR 110 may notify LR 108 to shut down. When LR 108 receives a shutdown indication from MR 110, LR 108 shuts down.

[0104] Fig.23 A signal flow diagram 2300 is shown for shutting down LR 108 when LR 108 may not be functioning properly. As shown, LR 108 may be turned on and MR 110 may be turned off. LR 108 may have a problem 2302 and need to be shut down. LR 108 may send a failure indication 2304 to MR 110. In some embodiments, MR 110 may send a LR shutdown indication 2306 to LR 108. MR 110 may be turned on and LR 108 may be turned off.

[0105] Fig.24 A flow chart of a method 2400 for a UE according to embodiments herein is shown. The method 2400 includes entering 2402 a deep sleep state by turning off a MR of the UE and turning on a LR of the UE.

[0106] The method 2400 also includes receiving 2404 at the MR from the LR an event indication for turning on the MR.

[0107] The method 2400 also includes starting 2406 the MR and executing a process according to an event corresponding to the event indication.

[0108] In some embodiments, the method 2400 further includes receiving, at the LR, a low power wake-up signal from the network node, wherein upon receiving the low power wake-up signal, the LR sends an event indication to the MR.

[0109] In some embodiments, the method 2400 further includes measuring, via the LR, a radio quality of the low power wake-up signal from the network node, wherein when the radio quality is less than a threshold, the LR sends an event indication to the MR.

[0110] In some embodiments, the method 2400 further includes maintaining, via the LR, one or more periodic cellular timers, wherein the LR sends an event indication to the MR when any of the one or more periodic cellular timers expires.

[0111] In some embodiments, method 2400 further includes determining, via the LR, that a failure of the LR has occurred, wherein when the failure occurs, the LR sends an event indication to the MR, and sends, via the MR, a disable low power wake-up signal indication to the network node.

[0112] In some embodiments of method 2400, while in the deep sleep state, the MR maintains one or more periodic cellular timers.

[0113] In some embodiments of method 2400, the MR is turned off when the MR detects an absence of activity and predicts an absence of activity after a period of time.

[0114] In some embodiments of method 2400, the MR is shut down when the MR receives a network command to shut down.

[0115] In some implementations of method 2400, MR is turned off based on a UE RRC state transition.

[0116] In some embodiments, the method 2400 further includes sending an LR on indication to the LR via the MR to turn on the LR.

[0117] In some embodiments, the method 2400 further includes sending an LR closing indication to the LR via the MR to cause the LR to close.

[0118] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of the method 2400. The apparatus may be, for example, an apparatus that is a UE (such as the wireless device 2602 as a UE, as described herein).

[0119] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 2400. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 2606 of wireless device 2602 as a UE, as described herein).

[0120] Embodiments contemplated herein include an apparatus comprising logical components, modules, or circuits for performing one or more elements of the method 2400. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 2602 as a UE, as described herein).

[0121] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 2400. The apparatus may be, for example, an apparatus of a UE (such as wireless device 2602 as a UE, as described herein).

[0122] Embodiments contemplated herein include signals as described in or associated with one or more elements of method 2400 .

[0123] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of the method 2400. The processor may be a processor of a UE (such as the processor 2604 of the wireless device 2602 as a UE, as described herein). These instructions may be located, for example, in a processor and / or on a memory of a UE (such as the memory 2606 of the wireless device 2602 as a UE, as described herein).

[0124] Fig.25 A flow chart of a method 2500 for a UE according to an embodiment of the present invention is shown. The method 2500 includes supporting 2502 a deep sleep state, wherein the UE only monitors and receives a low power wake-up signal (LP-WUS) signal from a network node in a Uu interface. The method 2500 also includes entering 2504 a deep sleep state when a sleep event occurs. The method 2500 also includes leaving 2506 a deep sleep state when a wake-up event occurs.

[0125] In some embodiments of method 2500, the wake-up event includes receiving a LP-WUS from a network node, wherein a low power wake-up signal is sent to the UE or a UE group to which the UE belongs.

[0126] In some embodiments, the method 2500 further includes measuring a radio quality of a LP-WUS from the network node, wherein the wake-up event includes measuring that the radio quality of the LP-WUS is less than a threshold.

[0127] In some embodiments, the method 2500 further includes maintaining one or more periodic cellular timers, wherein the wake event includes determining that any one of the one or more periodic cellular timers has expired.

[0128] In some embodiments, the method 2500 further includes determining that a failure of LP-WUS signaling reception functionality has occurred, wherein the wake-up event includes a failure of LP-WUS signaling reception functionality.

[0129] In some embodiments of the method 2500, determining failure of the LP-WUS signaling function further comprises sending a low power wake-up signal failure and deactivation indication to the network node.

[0130] In some embodiments of method 2500, the UE maintains one or more periodic cellular timers while in a deep sleep state.

[0131] In some embodiments of method 2500, a sleep event occurs when there is no activity and no activity is predicted until a later time.

[0132] In some embodiments of method 2500, the sleep event includes receiving a network command to enter a deep sleep state.

[0133] In some embodiments of method 2500, the sleep event comprises a UE radio resource control (RRC) state transition.

[0134] In some embodiments of method 2500, entering a deep sleep state includes enabling and activating LP-WUS monitoring and receiving functions.

[0135] In some embodiments of method 2500, the wake-up event includes receiving a configuration or indication for deactivating and disabling LP-WUS monitoring and receiving functions.

[0136] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of the method 2500. The apparatus may be, for example, an apparatus that is a UE (such as the wireless device 2702 as a UE, as described herein).

[0137] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 2500. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 2706 of wireless device 2702 as a UE, as described herein).

[0138] Embodiments contemplated herein include an apparatus comprising logical components, modules, or circuits for performing one or more elements of the method 2500. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 2702 as a UE, as described herein).

[0139] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 2500. The apparatus may be, for example, an apparatus of a UE (such as wireless device 2702 as a UE, as described herein).

[0140] Embodiments contemplated herein include signals as described in or associated with one or more elements of method 2500 .

[0141] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of the method 2500. The processor may be a processor of a UE (such as the processor 2704 of the wireless device 2702 as a UE, as described herein). These instructions may be located, for example, in a processor of a UE and / or on a memory (such as the memory 2706 of the wireless device 2702 as a UE, as described herein).

[0142] Fig.26 An exemplary architecture of a wireless communication system 2600 according to an embodiment disclosed herein is shown. The description provided below is for an exemplary wireless communication system 2600 operating in conjunction with the LTE system standard and / or the 5G or NR system standard provided in the 3GPP technical specifications.

[0143] like Fig.26As shown, the wireless communication system 2600 includes UE 2602 and UE 2604 (although any number of UEs may be used). In this example, UE 2602 and UE 2604 are shown as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0144] UE 2602 and UE 2604 may be configured to be communicatively coupled to RAN 2606. In an embodiment, RAN 2606 may be NG-RAN, E-UTRAN, etc. UE 2602 and UE 2604 utilize connections (or channels) (shown as connection 2608 and connection 2610, respectively) with RAN 2606, where each connection (or channel) includes a physical communication interface. RAN 2606 may include one or more base stations (such as base station 2612 and base station 2614) that implement connection 2608 and connection 2610.

[0145] In this example, connection 2608 and connection 2610 are air interfaces to achieve such communication coupling and may conform to the RAT used by RAN 2606, such as LTE and / or NR.

[0146] In some embodiments, UE 2602 and UE 2604 may also directly exchange communication data via side link interface 2616. UE 2604 is shown as being configured to access an access point (shown as AP 2618) via connection 2620. By way of example, connection 2620 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, wherein AP 2618 may include In this example, AP 2618 can connect to another network (eg, the Internet) without going through CN 2624.

[0147] In an embodiment, UE 2602 and UE 2604 may be configured to communicate with each other or with base station 2612 and / or base station 2614 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communication) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiment is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0148] In some embodiments, all or part of the base station 2612 or the base station 2614 may be implemented as one or more software entities running on a server computer as part of a virtual network. In addition, or in other embodiments, the base station 2612 or the base station 2614 may be configured to communicate with each other via the interface 2622. In an embodiment where the wireless communication system 2600 is an LTE system (e.g., when the CN 2624 is an EPC), the interface 2622 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In an embodiment where the wireless communication system 2600 is an NR system (e.g., when the CN 2624 is a 5GC), the interface 2622 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs, etc.) connected to the 5GC, between the base station 2612 (e.g., gNB) and the eNB connected to the 5GC, and / or between two eNBs connected to the 5GC (e.g., CN 2624).

[0149] RAN 2606 is shown as being communicatively coupled to CN 2624. CN 2624 may include one or more network elements 2626 configured to provide various data and telecommunication services to customers / subscribers (e.g., UE 2602 and users of UE 2604) connected to CN 2624 via RAN 2606. Components of CN 2624 may be implemented in one physical device or separate physical devices including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0150] In an embodiment, CN 2624 may be an EPC, and RAN 2606 may be connected to CN 2624 via an S1 interface 2628. In an embodiment, S1 interface 2628 may be divided into two parts: an S1 user plane (S1-U) interface, which carries traffic data between base station 2612 or base station 2614 and a serving gateway (S-GW); and an S1-MME interface, which is a signaling interface between base station 2612 or base station 2614 and a mobility management entity (MME).

[0151] In an embodiment, CN 2624 may be a 5GC, and RAN 2606 may be connected to CN 2624 via an NG interface 2628. In an embodiment, NG interface 2628 may be divided into two parts: an NG user plane (NG-U) interface, which carries traffic data between base station 2612 or base station 2614 and a user plane function (UPF); and an S1 control plane (NG-C) interface, which is a signaling interface between base station 2612 or base station 2614 and an access and mobility management function (AMF).

[0152] Generally speaking, the application server 2630 may be an element that provides applications that use Internet Protocol (IP) bearer resources with the CN 2624 (e.g., packet-switched data services). The application server 2630 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 2602 and UE 2604 via the CN 2624. The application server 2630 may communicate with the CN 2624 via the IP communication interface 2632.

[0153] Fig. 27 A system 2700 for performing signaling 2734 between a wireless device 2702 and a network device 2718 according to embodiments disclosed herein is shown. The system 2700 may be part of a wireless communication system as described herein. The wireless device 2702 may be, for example, a UE of a wireless communication system. The network device 2718 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

[0154] The wireless device 2702 may include one or more processors 2704. The processor 2704 may execute instructions to cause various operations of the wireless device 2702 to be performed, as described herein. The processor 2704 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0155] The wireless device 2702 may include a memory 2706. The memory 2706 may be a non-transitory computer-readable storage medium storing instructions 2708 (which may include, for example, instructions executed by the processor 2704). The instructions 2708 may also be referred to as program code or a computer program. The memory 2706 may also store data used by the processor 2704 and results calculated by the processor.

[0156] The wireless device 2702 may include one or more transceivers 2710, which may include radio frequency (RF) transmitter and / or receiver circuits that use an antenna 2712 of the wireless device 2702 to facilitate signaling (e.g., signaling 2734) transmitted or received by the wireless device 2702 with other devices (e.g., network device 2718) according to a corresponding RAT.

[0157] The wireless device 2702 may include one or more antennas 2712 (e.g., one, two, four, or more). For implementations with multiple antennas 2712, the wireless device 2702 may utilize the spatial diversity of such multiple antennas 2712 to send and / or receive multiple different data streams on the same time-frequency resources. This approach may be referred to as, for example, a multiple-input multiple-output (MIMO) approach (referring to multiple antennas used on the transmitting device and receiving device sides to implement this aspect, respectively). MIMO transmissions by the wireless device 2702 may be implemented based on precoding (or digital beamforming) applied at the wireless device 2702, which multiplexes data streams across antennas 2712 based on known or assumed channel characteristics, so that each data stream is received with appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with the data stream). Certain implementations may use a single-user MIMO (SU-MIMO) approach (where data streams are all directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (where individual data streams may be directed to individual (different) receivers at different locations in the spatial domain).

[0158] In certain embodiments with multiple antennas, the wireless device 2702 may implement analog beamforming techniques whereby the phases of the signals transmitted by the antennas 2712 are relatively adjusted to enable the (joint) transmission of the antennas 2712 to be directional (this is sometimes referred to as beam steering).

[0159] The wireless device 2702 may include one or more interfaces 2714. The interface 2714 may be used to provide input to the wireless device 2702 or provide output from the wireless device. For example, the wireless device 2702 as a UE may include an interface 2714, such as a microphone, a speaker, a touch screen, buttons, etc., to allow a user of the UE to input and / or output to the UE. Other interfaces of such a UE may be composed of transmitters, receivers, and other circuits that allow communication between the UE and other devices (for example, in addition to the transceiver 2710 / antenna 2712 described above), and may be based on known protocols (for example, Wi-Fi). etc.) to perform the operation.

[0160] The wireless device 2702 may include a MR / LR coordination module 2716. The MR / LR coordination module 2716 may be implemented via hardware, software, or a combination thereof. For example, the MR / LR coordination module 2716 may be implemented as a processor, circuit, and / or instructions 2708 stored in the memory 2706 and executed by the processor 2704. In some examples, the MR / LR coordination module 2716 may be integrated within the processor 2704 and / or the transceiver 2710. For example, the MR / LR coordination module 2716 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuit systems) within the processor 2704 or the transceiver 2710.

[0161] MR / LR coordination module 2716 may be used in various aspects of the present disclosure, for example, FIG. Fig.24 The MR / LR coordination module 2716 is configured to turn on and off MR and LR.

[0162] The network device 2718 may include one or more processors 2720. The processor 2720 may execute instructions to cause various operations of the network device 2718 to be performed, as described herein. The processor 2720 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0163] The network device 2718 may include a memory 2722. The memory 2722 may be a non-transitory computer-readable storage medium storing instructions 2724 (which may include, for example, instructions executed by the processor 2720). The instructions 2724 may also be referred to as program code or a computer program. The memory 2722 may also store data used by the processor 2720 and results calculated by the processor.

[0164] The network device 2718 may include one or more transceivers 2726, which may include RF transmitter circuits and / or receiver circuits that use an antenna 2728 of the network device 2718 to facilitate signaling (e.g., signaling 2734) transmitted or received by the network device 2718 with other devices (e.g., wireless device 2702) according to a corresponding RAT.

[0165] The network device 2718 may include one or more antennas 2728 (e.g., one, two, four, or more). In embodiments with multiple antennas 2728, the network device 2718 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc. as described above.

[0166] The network device 2718 may include one or more interfaces 2730. The interface 2730 may be used to provide input to or output from the network device 2718. For example, the network device 2718 as a base station may include an interface 2730 composed of a transmitter, a receiver and other circuits (e.g., in addition to the transceiver 2726 / antenna 2728 described above), which enables the base station to communicate with other equipment in the core network and / or enables the base station to communicate with external networks, computers, databases, etc., in order to achieve the purpose of performing operations, management and maintenance of the base station or other equipment operably connected to the base station.

[0167] The network device 2718 may include a LP-WUS module 2732. The LP-WUS module 2732 may be implemented by hardware, software, or a combination thereof. For example, the LP-WUS module 2732 may be implemented as a processor, circuit, and / or instructions 2724 stored in the memory 2722 and executed by the processor 2720. In some examples, the LP-WUS module 2732 may be integrated within the processor 2720 and / or the transceiver 2726. For example, the LP-WUS module 2732 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuit systems) within the processor 2720 or the transceiver 2726.

[0168] LP-WUS module 2732 may be used in various aspects of the present disclosure, for example, FIG. Fig.24 The LP-WUS module 2732 is configured to send LP-WUS signals, LP-WUS configuration and other commands.

[0169] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods as described herein. For example, the baseband processor described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described herein. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown herein.

[0170] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0171] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0172] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0173] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0174] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for a user equipment (UE), the method comprising: Supporting a deep sleep state, wherein the UE only monitors and receives a low power wake-up signal (LP-WUS) signal from a network node in the Uu interface; Entering the deep sleep state when a sleep event occurs; and The deep sleep state is left when a wake-up event occurs. 2 . The method of claim 1 , wherein the wake-up event comprises receiving the LP-WUS from the network node, wherein the low power wake-up signal is sent to the UE or a UE group to which the UE belongs.

3. The method according to claim 1, further comprising: measuring a radio quality of the LP-WUS from the network node, The wake-up event includes measuring that the radio quality of the LP-WUS is less than a threshold.

4. The method according to claim 1, further comprising: maintaining one or more periodic cellular timers, The wake-up event includes determining that any one of the one or more periodic cellular timers has expired.

5. The method according to claim 1, further comprising: Determining that a failure in the LP-WUS signaling reception function has occurred, The wake-up event includes the failure of the LP-WUS signaling receiving function.

6. The method of claim 5, wherein determining the failure of the LP-WUS signaling function further comprises: A low power wake-up signal failure and deactivation indication is sent to the network node.

7. The method of claim 1, wherein the UE maintains one or more periodic cellular timers while in the deep sleep state. The method of claim 1 , wherein the sleep event occurs when there is no activity and no activity is predicted until a later time.

9. The method of claim 1, wherein the sleep event comprises receiving a network command to enter the deep sleep state.

10. The method of claim 1, wherein the sleep event comprises a UE radio resource control (RRC) state transition.

11. The method of claim 1, wherein entering the deep sleep state comprises enabling and activating LP-WUS monitoring and receiving functions.

12. The method of claim 11, wherein the wake-up event comprises receiving a configuration or indication for deactivating and disabling the LP-WUS monitoring and receiving functions.

13. A user equipment (UE) device, the UE device comprising: processor; and a memory storing instructions that, when executed by the processor, configure the apparatus to: Supporting a deep sleep state, wherein the UE only monitors and receives a low power wake-up signal (LP-WUS) signal from a network node in the Uu interface; Entering the deep sleep state when a sleep event occurs; and The deep sleep state is left when a wake-up event occurs. 14 . The UE device of claim 13 , wherein the wake-up event comprises receiving the LP-WUS from the network node, wherein the low power wake-up signal is sent to the UE or a UE group to which the UE belongs.

15. The UE device of claim 13, wherein the instructions further configure the device to: measure a radio quality of the LP-WUS from the network node, The wake-up event includes measuring that the radio quality of the LP-WUS is less than a threshold.

16. The UE device of claim 13, wherein the instructions further configure the device to: maintain one or more periodic cellular timers, The wake-up event includes determining that any one of the one or more periodic cellular timers has expired.

17. The UE device of claim 13, wherein the instructions further configure the device to: determine that a failure of LP-WUS signaling reception function has occurred, The wake-up event includes the failure of the LP-WUS signal receiving function.

18. The UE device of claim 17, wherein determining the failure of the LP-WUS signal function further comprises: A low power wake-up signal failure and deactivation indication is sent to the network node.

19. The UE apparatus of claim 13, wherein while in the deep sleep state, the UE maintains one or more periodic cellular timers.

20. The UE device of claim 13, wherein the sleep event occurs when there is no activity and no activity is predicted until a later time.

21. The UE device of claim 13, wherein the sleep event comprises receiving a network command to enter the deep sleep state.

22. The UE device of claim 13, wherein the sleep event comprises a UE radio resource control (RRC) state transition.

23. The UE device of claim 13, wherein entering the deep sleep state comprises enabling and activating LP-WUS monitoring and receiving functions.

24. The UE device of claim 23, wherein the wake-up event comprises receiving a configuration or indication for deactivating and disabling the LP-WUS monitoring and receiving functions.

25. A non-transitory computer-readable storage medium comprising instructions that, when executed by a user equipment (UE), cause the UE to: Supporting a deep sleep state, wherein the UE only monitors and receives a low power wake-up signal (LP-WUS) signal from a network node in the Uu interface; Entering the deep sleep state when a sleep event occurs; and The deep sleep state is left when a wake-up event occurs.

26. The computer-readable storage medium of claim 25, wherein the wake-up event comprises receiving the LP-WUS from the network node, wherein the low power wake-up signal is sent to the UE or a UE group to which the UE belongs.

27. The computer-readable storage medium of claim 25, wherein the instructions further configure the computer to: measure a radio quality of the LP-WUS from the network node, The wake-up event includes measuring that the radio quality of the LP-WUS is less than a threshold.

28. The computer-readable storage medium of claim 25, wherein the instructions further configure the UE to: maintain one or more periodic cellular timers, The wake-up event includes determining that any one of the one or more periodic cellular timers has expired.

29. The computer-readable storage medium of claim 25, wherein the instructions further configure the UE to determine that a failure of LP-WUS signaling reception functionality has occurred, wherein the wake-up event comprises the failure of the LP-WUS signal reception functionality.

30. The computer-readable storage medium of claim 29, wherein determining the failure of the LP-WUS signal function further comprises: A low power wake-up signal failure and deactivation indication is sent to the network node.

31. The computer-readable storage medium of claim 25, wherein while in the deep sleep state, the UE maintains one or more periodic cellular timers.

32. The computer-readable storage medium of claim 25, wherein the sleep event occurs when there is no activity and no activity is predicted until a later time.

33. The computer-readable storage medium of claim 25, wherein the sleep event comprises receiving a network command to enter the deep sleep state.

34. The computer-readable storage medium of claim 25, wherein the sleep event comprises a UE radio resource control (RRC) state transition.

35. The computer-readable storage medium of claim 25, wherein entering the deep sleep state comprises enabling and activating LP-WUS monitoring and receiving functions.

36. The computer-readable storage medium of claim 35, wherein the wake-up event comprises receiving a configuration or indication to deactivate and disable the LP-WUS monitoring and receiving functions.