Signaling for wake-up indication using low-power wake-up signals

Abstract

The UE includes a transceiver having a first nominal operating power, a low-power (LP) wake-up receiver (LP-WUR) having a second nominal operating power less than the first nominal operating power, and a processor. The LP-WUR is configured to receive an LP wake-up signal (LP-WUS) via an air interface when the transceiver is in a low-power state. The processor is configured to determine that the LP-WUS includes a wake-up indication (WUI) for the UE, and to wake up the transceiver in response to determining that the LP-WUS includes a WUI for the UE.

Description

Technical Field

[0001] This application generally relates to wireless communication systems, including systems, apparatus and methods, wherein a user equipment (UE) may use a low-power (LP) wake-up receiver (LP-WUR) to monitor an LP wake-up signal (LP-WUS). Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between network devices (e.g., base stations, radio heads, etc.) and wireless communication devices. Wireless communication system standards and protocols may include, for example, 3GPP Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs) (often referred to as Wi-Fi within industry organizations). ® ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols can use various radio access networks (RANs) for communication between RAN network equipment (sometimes collectively referred to as RAN nodes, network nodes, or simply nodes) and wireless communication equipment called UEs. 3GPP RANs can include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rate 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 network devices and UEs. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements the NR RAT (sometimes referred to herein as the 5G RAT, 5G NR RAT, or simply NR). In some deployments, E-UTRAN may also implement the NR RAT. In some deployments, NG-RAN may also implement the LTE RAT.

[0005] The network equipment used in a RAN can correspond to that RAN. An example of E-UTRAN network equipment is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB). An example of NG-RAN network equipment is a Next Generation Node B (sometimes also called gNodeB or gNB).

[0006] The RAN provides communication services to external entities through its connection with the core network (CN). For example, E-UTRAN can utilize the evolved packet core (EPC), while NG-RAN can utilize the 5G core network (5GC). Attached Figure Description

[0007] To facilitate the identification of any particular element or action in the discussion, one or more of the most significant digits in the figure reference numerals refer to the figure number in which the element was first introduced.

[0008] Figure 1 An example wireless communication system is shown according to one or more aspects described herein.

[0009] Figure 2 An example method of wireless communication performed by a UE according to one or more aspects described herein is shown.

[0010] Figure 3 An example method of wireless communication performed by a network device according to one or more aspects described herein is shown.

[0011] Figure 4 Example architectures of wireless communication systems based on one or more aspects described herein are illustrated.

[0012] Figure 5 An example system for performing signaling between a wireless device and a network device, according to one or more aspects described herein, is illustrated. Detailed Implementation

[0013] Various implementations are described with reference to user equipment (UE). However, references to UE are provided for illustrative purposes only. Example implementations can be used with any electronic component capable of establishing a connection to a network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Thus, UE as described herein is used to refer to any suitable electronic device (e.g., mobile phone, computer (e.g., laptop computer or tablet computer), wearable device (e.g., electronic watch, fitness device, or head-mounted device), or Internet of Things (IoT) device).

[0014] In some cases, the UE may include a low-power (LP) wake-up receiver (LP-WUR), and network equipment (e.g., a cell of a radio access network (RAN)) may transmit one or more signals over the air interface that are intended to be received by (or capable of being received by) the LP-WUR and that can be decoded by the UE. These signals may include one or more of, for example, an LP wake-up signal (LP-WUS), an LP synchronization signal (LP-SS), or a preamble to the LP-WUS.

[0015] In some cases, when a UE receives a signal at the LP-WUR and determines that the signal addresses the UE or a group of UEs including the UE, the UE may transition the UE’s receiver or transceiver (e.g., a receiver or transceiver that consumes more power than the UE’s LP-WUR (e.g., a main radio that consumes one or two or more orders of power more than the LP-WUR)) from a sleep state (e.g., a low-power state (which may or may not be a shutdown state)) to a wake-up state (e.g., a fully powered or normal operating mode).

[0016] In some cases, the UE may measure the signal to determine information about the cell or about the UE (e.g., its location), or the UE may receive information in the signal. In some cases, a UE including an LP-WUR may be a power-sensitive device, such as a small device (e.g., an IoT device or a wearable device). In some cases, a non-power-sensitive device may include an LP-WUR.

[0017] In a 3GPP context, such as for a UE configured to operate in 3GPP NR mode, LP-WUR can be used in Radio Resource Control (RRC) idle mode or RRC inactive mode (RRC idle / inactive mode) and / or RRC connected mode.

[0018] Currently, there are no regulations specifying what type of payload or information LP-WUS should carry, or how the UE should be woken up by LP-WUS. This document describes options for signaling to the UE that it will be woken up in response to LP-WUS.

[0019] In some implementations described herein, the LP-WUS carries a UE-specific wake-up indication (WUI). The UE-specific WUI may be for a specific UE to be woken up. In some implementations, the UE-specific WUI may be the only WUI carried in the LP-WUS. In some implementations, the UE-specific WUI may be concatenated with one or more other WUIs carried in the LP-WUS. In some implementations, the UE-specific WUI may be carried as part of a group common signaling structure, such as a bitmap, where each bit is a WUI for a different UE or UE group.

[0020] In some implementations described herein, the LP-WUS carries a UE-group-based WUI. The UE-group-based WUI can target a group of UEs to be woken up. Alternatively, if only one UE needs to be woken up, all UEs targeted by the UE-group-based WUI will be woken up.

[0021] The set of implementations described herein pertains to UEs operating in RRC idle mode or RRC inactive mode. Within this set of implementations, a UE-specific WUI or a UE-group-based WUI can be used by LP-WUS for the UE.

[0022] Another set of implementations described herein relates to a UE operating in RRC connection mode. Within this set of implementations, example signaling is provided for UEs operating in single-carrier operation mode and UEs operating in multi-carrier operation mode.

[0023] Figure 1 An example wireless communication system 100 is illustrated. The wireless communication system may include a UE 102 connected over the air to a network (e.g., a 3GPP network). The UE 102 may communicate with the network on one or more uplink (UL) channels and one or more downlink (DL) channels, and more specifically, may communicate with one or more network devices of the RAN (e.g., network devices 104-1 and 104-2, which may take the form of one or more base stations, remote radio heads, etc.) on one or more UL channels and DL channels. Depending on the capabilities of the UE 102 and the network-configured settings of the UE, the UE 102 may communicate simultaneously, concurrently (e.g., in multiple-input multiple-output (MIMO) mode), or sequentially (e.g., during handover) with one or more network devices 104-1, 104-2.

[0024] In some cases, UE 102 can connect to one or both of the first network device 104-1 or the second network device 104-2 in RRC connected mode, RRC idle mode, or RRC inactive mode. In some cases, one or both of network devices 104-1 and 104-2 can be a neighboring cell of UE 102.

[0025] In some implementations, UE 102 may have both a primary radio (or transceiver) and an LP-WUR. When UE 102 has both a primary radio and an LP-WUR, the primary radio and the LP-WUR may be separate physical entities, or alternatively, the primary radio and the LP-WUR may share some or all of the physical infrastructure and be separate logical entities. For example, the transceiver may operate as a primary radio at one power level or as an LP-WUR at another power level; or the LP-WUR may be used as a primary radio in combination with additional physical infrastructure. In some implementations, UE 102 may have only a primary radio or an LP-WUR. In implementations where UE 102 has an LP-WUR, UE 102 may use the LP-WUR to receive signals from a first network device 104-1, a second network device 104-2, and / or other network devices. Each signal may take the form of an LP-WUS, LP-SS, an LP-WUS preamble, or another type of signal intended to be received by (or capable of being received by) the LP-WUR.

[0026] In some cases, signals can be received when UE 102 is in RRC idle mode or RRC inactive mode. Some signals (e.g., LP-WUS addressed to UE 102 or to a group of UEs including UE 102) can enable UE 102 to wake up the primary radio, which is in a low-power state. In some cases, signals can be received when UE 102 is in RRC connected mode. Because the LP-WUS consumes an order of magnitude or more less power than the primary radio, it can operate with negligible additional power consumption when the primary radio is in use. In some implementations, the LP-WUS can be used for radio resource management (RRM) purposes to increase the throughput of the primary radio, such as when using the LP-WUS would enable the primary radio to avoid measurement gaps and / or scheduling constraints.

[0027] Figure 2An example method 200 for wireless communication performed by a UE is illustrated. In one or more embodiments, method 200 supports one or more aspects of low-power communication as described herein. In some cases, the UE may be UE 102, wireless device 502, or one of the other UEs described herein. In some cases, method 200 may be performed by a processor of the UE using a transceiver (e.g., a main radio) of the UE having a first nominal operating power, a second nominal operating power LP-WUR of the UE having a power less than the first nominal operating power, or other components of the UE. The transceiver and LP-WUR may be separate physical entities within the UE, or separate logical entities that may or may not share at least some physical structures. The LP-WUR may be configured to monitor and receive LP-WUR over an air interface when the transceiver is in a low-power state. In some embodiments, the LP-WUR may be configured to monitor and receive other signals and / or monitor and receive signals when the transceiver is operating at or approximately the first nominal operating power.

[0028] At 202, method 200 may include determining that the LP-WUS received by the LP-WUR includes a WUI for the UE. The LP-WUS can be received when the transceiver is in a low-power state.

[0029] At 204, method 200 may include waking up the transceiver in response to determining that LP-WUS includes a WUI for the UE.

[0030] Method 200 may be embodied, extended or modified in various ways, as described in the following paragraphs and elsewhere in this description.

[0031] In some embodiments of method 200, the UE may receive LP-WUS when operating in RRC idle mode, RRC inactive mode, or RRC connected mode. In some embodiments, the manner in which the UE performs method 200 when operating in RRC idle mode or RRC inactive mode may differ from the manner in which the UE performs method 200 when operating in RRC connected mode.

[0032] When the UE operates in RRC idle mode or RRC inactive mode, and in some implementations, the WUI can be a UE-specific WUI (i.e., a WUI specific to only one UE). In some implementations of these implementations, the UE-specific WUI can be or include the UE's complete UE identifier (ID). In some implementations of these implementations, the UE-specific WUI can be or include a portion of the complete UE ID.

[0033] When the UE operates in RRC idle mode or RRC inactive mode, and the WUI is the UE's complete UE ID, the UE can determine at 202 that the LP-WUS includes the WUI for the UE by extracting an indicator of the UE's complete UE ID from the LP-WUS. The complete UE ID can be, for example, a 5G-S-Temporary Mobile Subscription Identifier (5G-S-TMSI), which is a 48-bit long string as defined in 3GPP Technical Specification (TS) 23.501.

[0034] When the UE operates in RRC idle mode or RRC inactive mode, and there is a one-to-one correspondence between the UE's LP-WUS monitoring opportunity (MO) and the UE's paging opportunity (PO), the WUI may be or include a portion of the UE's complete UE ID. The complete UE ID may be defined by a first portion (e.g., the least significant bit (LSB)) and a second portion (e.g., the most significant bit (MSB)). In these embodiments, method 200 may include determining the UE's PO from the first portion of the complete UE ID, such that the first portion of the complete UE ID can be derived from the UE's PO. Method 200 may also include: when the UE operates in RRC idle mode or RRC inactive mode, configuring the LP-WUS to monitor the LP-WUS MO for LP-WUS, and determining that the LP-WUS includes the WUI for the UE by extracting an indicator of the second portion of the complete UE ID from the LP-WUS as the WUI for the UE. In some cases, method 200 may include dividing the complete UE ID by N. s The floor function of *N determines the indicator of the second part of UEID (i.e., UE_ID_WUS).

[0035] UE_ID_WUS = floor(full UE ID / (N s * N))

[0036] Where N s N is the number of POs per paging frame, N is the number of paging frames in a paging cycle, and Ns*N is the number of POs per paging cycle. The MSB of the complete UE ID can be derived from UE_ID_WUS. The MSB of the complete UE ID, combined with the LSB derived from the PO, provides the complete UE ID.

[0037] In other implementations, when the UE operates in RRC idle mode or RRC inactive mode, and the UE's LP-WUS MO is configured separately or does not have a one-to-one correspondence with the UE's PO, the WUI may be or include a portion of the UE's complete UE ID. The complete UE ID may be defined by a first part (e.g., LSB) and a second part (e.g., MSB) of the complete UE ID. In these implementations, method 200 may include determining the timing of the UE's LP-WUS MO from the first part of the complete UE ID, such that the first part of the complete UE ID can be derived from the UE's LP-WUS MO. Method 200 may also include: when the UE operates in RRC idle mode or RRC inactive mode, configuring the LP-WUR to monitor the LP-WUS MO for LP-WUS, and determining that the LP-WUS includes the WUI for the UE by extracting an indicator of the second part of the complete UE ID from the LP-WUS as the WUI for the UE. As an example, there may be a total of K LP-WUS MOs in one cycle, where K=2. M The UE can determine which of the K LP-WUS MOs to monitor based on the set of M MSBs that define the first part of the complete UE ID. The remaining bits of the complete UE ID (i.e., the second part of the UE ID) can be indicated in the LP-WUS.

[0038] As an example of the implementation scheme described last, each UE in the set of UEs communicating with the cell may be configured with a different LP-WUS MO, such that the LP-WUS only needs to carry a unit WUI (for wake-up or non-wake-up) to wake up the UE. As another example, N UEs may be configured with the same LP-WUS MO, and the LP-WUS may include an N-bit bitmap, where each bit is the WUI for the corresponding UE.

[0039] When the UE operates in RRC idle mode or RRC inactive mode, and in some implementations, the WUI can be or include an indicator of the UE group ID (i.e., a WUI for multiple UEs), and the UE group ID can correspond to the UE group that includes that UE. The UE group ID can take various forms.

[0040] In some implementations, the UE group ID may be explicitly assigned by the network (e.g., by an entity (e.g., a network device) of the core network (CN) or radio access network (RAN). For example, a UE group ID may be assigned to multiple UEs, similar to how a subgroup ID is assigned by the CN for Early Paging Indication (PEI) in 3GPP Release 17 (Rel-17). In these implementations, method 200 may include determining the UE group ID assigned to the UE group that includes the UE from transmissions received via a transceiver (e.g., the UE may receive the UE group ID assignment from the network). In some cases, transmissions may be received while the UE is in RRC connected mode. Method 200 may also include: operating the UE in RRC idle mode or RRC inactive mode, and when the UE is operating in RRC idle mode or RRC inactive mode, determining that the LP-WUS includes the WUI for the UE by extracting an indicator of the UE group ID from the LP-WUS as the WUI for the UE.

[0041] In some implementations, the UE group ID can be multiple bits (e.g., a subset of bits) explicitly obtained from the complete UE ID. For example, consider a group ID consisting of bit a. 47 a 46 A complete UE ID consisting of a1, a2, a3, a2, a1, a0, ..., a3, a2, a1, a0, where a1, a2, a3, a2, a3, a2, a3, a4, ... ...4, ..., a3, a2, a3, a4, ..., a3, ..., a4, ..., a3, ..., a4, ..., a3, ..., a4, ..., a3, ..., a3, ..., a4, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3 47It is the MSB, and a0 is the LSB. If there are 8 LP-WUS MOs based on the 3 LSBs of the complete UE ID (i.e., based on bits a2, a1, a0, such that bits a2, a1, a0 can be derived from a specific LP-WUS MO), then the UE group ID can be defined based on bits a6, a5, a4, a3, or any other set of bits from the complete UE ID (other than those from bits a2, a1, a0). A set of four bits, such as bits a6, a5, a4, a3, will support up to sixteen different UE groups. Therefore, in these embodiments, the complete UE ID of the UE may include at least a portion corresponding to the UE group ID; or the complete UE ID of the UE may include at least a first part of the UE ID and a second part of the UE ID, wherein the second part of the UE ID corresponds to the UE group ID. Similarly, in these embodiments, method 200 may include: operating the UE in RRC idle mode or RRC inactive mode; and when the UE is operating in RRC idle mode or RRC inactive mode, determining that the LP-WUS includes a WUI for the UE by extracting an indicator of the UE group ID from the LP-WUS as a WUI for the UE. Alternatively, method 200 may include: determining the LP-WUS MO of the UE from a first portion of the UE ID; operating the UE in RRC idle mode or RRC inactive mode; and when the UE is operating in RRC idle mode or RRC inactive mode, determining that the LP-WUS includes a WUI for the UE by extracting an indicator of the UE group ID from the LP-WUS as a WUI for the UE.

[0042] In some implementations, the WUI may be or include an indicator of the UE group ID of the UE group containing the UE, but the UE group ID may be determined in other ways. For example, the UE group ID may be based at least in part on the UE's complete UE ID and the total number of UE groups in the LP-WUS MO. In some implementations, the UE group ID may additionally or alternatively be based at least in part on the maximum number of UE groups allowed in the LP-WUS MO. For example, when there is a one-to-one correspondence between the LP-WUS MO and the UE's legacy PO, and when the LSB of the UE's complete UE ID is implicitly carried in

[0043] When the UE's PO (i.e., can be derived from the UE's PO), any of the following formulas can be used to determine the UE group IDs for the total L UE groups in the LP-WUS MO and the maximum number L1 UE groups allowed in the LP-WUS MO:

[0044] A. ,

[0045] in

[0046] B. ,

[0047] in

[0048] C.

[0049] in

[0050] D.

[0051] E.

[0052] Option A assigns a UE group ID to multiple UEs, similar to how the CN assigns subgroup IDs to PEIs in 3GPP Rel-17. 1024 is the maximum allowed number of POs in a paging cycle.

[0053] In some implementations, an offset can be applied to the UE group ID determined using any of the methods described above (or to the UE group ID determined using other methods) to obtain the final UE group ID. For example, three UE group IDs may be assigned by the network, and an additional UE group ID may be determined using one of the options A through E above. The offset can then be applied to each of the UE group IDs determined using one of options A through E. In some cases, the offset can be used to ensure that different methods of assigning / determining UE group IDs do not result in duplicate UE group IDs.

[0054] When the UE of method 200 operates in RRC idle mode or RRC inactive mode, the WUI for the UE may take different forms. In some implementations, the WUI may be or include the state of bits in a bitmap, where each bit in the bitmap corresponds to a different UE or UE group that can be woken up within the LP-WUS MO. For example, a UE may be assigned to bit seven of the LP-WUS payload, or a UE may be assigned to a UE group that is assigned to bit seven of the LP-WUS payload. If bit seven of the LP-WUS payload is set (e.g., the bit is logic "1"), then the LP-WUS is considered to include the WUI for the UE. If bit seven of the LP-WUS payload is not set (e.g., the bit is logic "0"), then the LP-WUS is considered not to include the WUI for the UE. The length of the bitmap may be equal to the number of UEs or UE groups in the LP-WUS MO.

[0055] When the UE of method 200 operates in RRC idle mode or RRC inactive mode, and in some embodiments, the WUI in method 200 may be part or all of the UE's complete UE ID, or part or all of the complete UE group ID of the UE group that includes the UE, and may be explicitly carried as part or all of the LP-WUS payload. For example, the WUI may be the complete UE ID or a part of the complete UE ID, as described herein. The LP-WUS payload may be further encoded and modulated before transmission.

[0056] When the UE of method 200 is operating in RRC idle mode or RRC inactive mode, and in some embodiments, the WUI in method 200 may be or include one or more sequences in the time domain and / or frequency domain (i.e., on a set of multiple subcarriers on which the LP-WUS is received) as defined by the bit set carried by the LP-WUS. In these embodiments, method 200 may include: when the UE is operating in RRC connected mode, determining that the LP-WUS includes the WUI for the UE by determining that one or more sequences in the time domain and / or frequency domain are defined by the bit set carried by the LP-WUS, and mapping the sequences to at least a portion of the complete UE ID of the UE or at least a portion of the UE group ID of the UE group that includes the UE.

[0057] In any of the above embodiments, the LP-WUS may carry a WUI for one or more UEs or UE groups, or a WUI for a UE, UE group, or a mixture of UEs and UE groups (e.g., in a bitmap, or in a cascading indicator for UEs and / or UE groups).

[0058] When the UE operates in RRC connection mode, it is expected that LP-WUS will control the UE's Physical Downlink Control Channel (PDCCH) monitoring behavior. Therefore, when the UE of method 200 operates in RRC connection mode, it may be preferable to select or format the UE's WUI as a UE-specific WUI.

[0059] When the UE of method 200 operates in RRC connection mode, and in some embodiments, the UE may be configured for single-carrier operation with network devices (i.e., in single-carrier mode). In other embodiments, the UE may be configured for multi-carrier operation with one or more network devices (e.g., using two or more carriers associated with one or more cells in multi-carrier mode or carrier aggregation (CA) mode).

[0060] When a UE operates in RRC connected mode and is configured for single-carrier operation, and in some implementations, the WUI for the UE may be or include the UE's Cell Radio Network Temporary Identifier (C-RNTI), a 16-bit value. The C-RNTI may be explicitly carried by the LP-WUS (e.g., as a set of bits in the LP-WUS payload) or implicitly carried by the LP-WUS (e.g., for scrambling Cyclic Redundancy Check (CRC) included in the LP-WUS payload). In some cases, the LP-WUS may carry the C-RNTIs (i.e., WUIs) of multiple UEs.

[0061] When a UE operates in RRC connected mode and is configured for single-carrier operation, and in some implementations, the UE may be configured with a UE-specific UE ID for LP-WUS (or more generally, for low-power signaling). In these implementations, the WUI for the UE may carry the UE-specific UE ID. In some cases, the UE-specific UE ID may be shorter than the C-RNTI. For example, the network may consider the number of connected UEs that need to rely on LP-WUS signaling in a cell or other area and may determine the number of bits (or length) required to assign a unique UE-specific UE ID to that number of connected UEs. The UE-specific UE ID may be explicitly carried by LP-WUS (e.g., as a set of bits in the LP-WUS payload) or implicitly carried by LP-WUS (e.g., for scrambling Cyclic Redundancy Check (CRC) included in the LP-WUS payload). In some cases, LP-WUS may carry the UE-specific UE IDs (i.e., WUIs) of multiple UEs. In these implementations, method 200 may include: receiving a UE-specific UE ID of the UE from the network, and when the UE is operating in RRC connection mode, determining that the LP-WUS includes a WUI for the UE by extracting the UE-specific UE ID of the UE from the LP-WUS.

[0062] When a UE operates in RRC connected mode and is configured for single-carrier operation, in some implementations, the UE may be configured with bit positions in the LP-WUS payload. For example, the WUI may be or include the state of bits in a bitmap, where each bit in the bitmap corresponds to a different UE that can be woken up within the LP-WUS MO. For example, a UE may be assigned to bit seven of the LP-WUS payload. If bit seven of the LP-WUS payload is set (e.g., the bit is logic "1"), then the LP-WUS is considered to include a WUI for the UE. If bit seven of the LP-WUS payload is not set (e.g., the bit is logic "0"), then the LP-WUS is considered not to include a WUI for the UE. The length of the bitmap may be equal to the number of UEs in the LP-WUS MO. This is a form of group common signaling that carries UE-specific WUIs for multiple UEs.

[0063] When a UE operates in RRC connected mode and is configured for single-carrier operation, and in some embodiments, a UE-specific set of one or more resources of LP-WUS may be assigned to the UE, and different UE-specific sets of one or more resources of LP-WUS may be assigned to different UEs. Each UE-specific set of resources may include different time-frequency resources, or different sequences on shared time-frequency resources. The state of one or more UE-specific sets of resources can provide a WUI for the UE. In these embodiments, method 200 may include: receiving an indication from the network of a UE-specific set of one or more resources of LP-WUS, and, when the UE is operating in RRC connected mode, determining that LP-WUS includes a WUI for the UE by identifying the predetermined or configuration state of the UE-specific set of one or more resources of LP-WUS from LP-WUS.

[0064] When the UE of method 200 operates in RRC connected mode and is configured for multi-carrier operation, configuring the UE to monitor LP-WUS on only one or a few cells may be useful. This reduces UE complexity and saves power. If method 200 includes monitoring LP-WUS on only a single cell, that cell may be predefined (e.g., in 3GPP TS) as the UE's primary cell. Alternatively, the single cell on which the UE monitors LP-WUS may be configured by the network. In some embodiments, this single cell may be configured as the UE's serving cell (e.g., the serving cell of the UE's transceiver (or primary radio)). In some embodiments, this single cell may be configured as a non-serving cell of the UE.

[0065] When the UE operates in RRC connected mode and is configured for multi-carrier operation, and in some implementations, method 200 may include: after waking up the transceiver at 204, monitoring the PDCCH on a single carrier or cell, as predefined in 3GPPTS or as configured by the network. Alternatively, method 200 may include monitoring the PDCCH on each (or a set of carriers) of the carriers associated with multi-carrier operation (i.e., all carriers associated with multi-carrier operation), or monitoring the PDCCH from all (or a set of cells) of the cells associated with multi-carrier operation (i.e., all cells associated with multi-carrier operation). That is, the WUI may be applied to a single predefined or configured carrier or cell, or the WUI may be applied to all carriers or cells (or a set of carriers or cells). In these implementations, all the options described herein for single-carrier operation may be applied to the UE, LP-WUS, and / or WUI.

[0066] When the UE operates in RRC connected mode and is configured for multi-carrier operation, and in some implementations, the WUI may be provided per carrier or per cell. In these implementations, method 200 may include: after waking up the transceiver at 204, monitoring the PDCCH on one or more carriers or cells associated with multi-carrier operation. That is, the WUI determined at 202 to be included in the LP-WUS may be applied only to a single carrier or cell. In some implementations, the UE may be configured to monitor multiple WUIs, where each WUI corresponds to a different carrier or cell. If the UE is to monitor the PDCCH on more than one carrier or from more than one cell, method 200 may include: receiving via the transceiver one or more indications of which LP-WUS MOs are to be monitored on which carriers or cells; configuring the LP-WUS MO to monitor the indicated LP-WUS MOs for each carrier or cell's WUI; and causing the transceiver to monitor the PDCCH on each carrier (or from each cell) from which the WUI is received. Different LP-WUS MOs may occupy different time-frequency resources or use different sequences on the same time-frequency resources.

[0067] As another example, if the UE is to monitor the PDCCH on more than one carrier or from more than one cell, method 200 may include: determining that the LP-WUS includes the UE's C-RNTI or a UE-specific UE ID for the LP-WUS. Determining that the LP-WUS includes a WUI for the UE may then include: determining that the UE's C-RNTI or the UE-specific UE ID for the LP-WUS is associated with one or more WUIs. Each WUI may indicate whether the UE wants to wake up the transceiver and monitor the PDCCH on a different carrier or cell. In some cases, each WUI may be a single bit that indicates whether the UE wants to monitor the PDCCH on a particular carrier or cell (e.g., if the bit is a logic "1") or whether the UE will not monitor the PDCCH on a particular carrier or cell (e.g., if the bit is a logic "0").

[0068] As another example, if a UE needs to monitor PDCCH on more than one carrier or from more than one cell, method 200 may include: receiving via a transceiver an indication of which LP-WUS resources (or MOs) to monitor for a WUI, wherein each WUI corresponds to a different carrier or cell; configuring an LP-WUR to monitor the indicated LP-WUS resources for each carrier or cell's WUI; and causing the transceiver to monitor PDCCH on each carrier (or from each cell) for which the WUI is received. Each WUI may be a single bit indicating whether the transceiver should monitor PDCCH on the corresponding carrier or cell. WUIs for multiple UEs may be carried in the same LP-WUS. Different WUIs may correspond to different UEs.

[0069] When the UE operates in RRC connected mode and is configured for multi-carrier operation, and in some implementations, a WUI may be provided per carrier group or per cell group. In these implementations, method 200 may include: after waking up the transceiver at 204, monitoring the PDCCH on each of the carriers or cells within one or more carrier groups or cell groups associated with multi-carrier operation. That is, the WUI determined at 202 to be included in the LP-WUS may be applied to the carrier group or cell group. If the UE is to monitor the PDCCH on more than one carrier group or cell group, method 200 may include: receiving via the transceiver one or more indications of which LP-WUS MOs of which carrier groups or cell groups to monitor; configuring the LP-WUS to monitor the indicated LP-WUS MOs for the WUI of each carrier group or cell group; and causing the transceiver to monitor the PDCCH on each carrier group (or for each cell group) where the WUI is received. Different LP-WUS MOs may occupy different time-frequency resources or use different sequences on the same time-frequency resources.

[0070] As another example, if the UE is to monitor the PDCCH on more than one carrier group or from more than one cell group, method 200 may include: determining that the LP-WUS includes the UE's C-RNTI or a UE-specific UE ID for the LP-WUS. Determining that the LP-WUS includes a WUI for the UE may then include: determining that the UE's C-RNTI or the UE-specific UE ID for the LP-WUS is associated with one or more WUIs. Each WUI may indicate that the UE wants to wake up the transceiver and monitor the PDCCH on each carrier or cell within a particular carrier group or cell group. In some cases, each WUI may be a single bit that indicates whether the UE wants to monitor the PDCCH on a particular carrier group or cell group (e.g., if the bit is a logic "1") or whether the UE will not monitor the PDCCH on a particular carrier group or cell group (e.g., if the bit is a logic "0").

[0071] As another example, if a UE needs to monitor PDCCH on more than one carrier group or from more than one cell group, method 200 may include: receiving via a transceiver an indication of which LP-WUS resources (or MOs) to monitor for a WUI, wherein each WUI corresponds to a different carrier or cell; configuring an LP-WUR to monitor the indicated LP-WUS resources for each carrier group or cell group's WUI; and causing the transceiver to monitor PDCCH on each of the carriers or cells within the carrier group (or cell group) from which the WUI was received. Each WUI may be a single bit indicating whether the transceiver should monitor PDCCH for the corresponding carrier group or cell group. WUIs for multiple UEs may be carried in the same LP-WUS. Different WUIs may correspond to different UEs.

[0072] In each of the above cell group monitoring scenarios, the cell group, primary cell group, or one of the cell groups may be the same as the UE's Connectivity Discontinuous Receive (C-DRX) cell group. Alternatively, the cell group, primary cell group, or one of the cell groups may be a dormant group as defined in 3GPP Rel-16. Alternatively, one or more cell groups may be configured by the network and used for LP-WUS purposes. When more than one cell group is defined, the different cell groups may overlap or not. For example, for a UE configured to operate with three cells (e.g., CC0, CC1, and CC2), the first cell group (e.g., cell group 1) may be defined to include CC0, and the second cell group (e.g., cell group 2) may be defined to include CC0, CC1, and CC2.

[0073] Figure 3An example method 300 for wireless communication performed by a network device (e.g., a network device of a RAN) is illustrated. In one or more embodiments, method 300 supports one or more aspects of low-power communication as described herein. In some cases, the network device may be one of network device 104, network device 520, or other network devices described herein. In some cases, method 300 may be executed by a processor using the transceiver of the network device or other components of the network device.

[0074] At 302, method 300 may include selecting, formatting, or configuring the WUI for the UE.

[0075] At 304, method 300 may include transmitting (or broadcasting) LP-WUS via an air interface and using the transceiver of a network device. LP-WUS may include a WUI for the UE. In some cases, LP-WUS may be transmitted when the UE's transceiver is in a low-power state.

[0076] At 306, method 300 may include sending to and / or receiving from the UE. This is done over the air using the transceiver of the network device. Sending to or receiving from the UE may occur after a waiting period following the transmission of LP-WUS.

[0077] Method 300 can be embodied, extended, or modified in various ways, as described in the following paragraphs and elsewhere in this description.

[0078] In some embodiments of method 300, LP-WUS may be sent (or broadcast) to the UE when the UE is operating in RRC idle mode, RRC inactive mode, or RRC connected mode. In some embodiments, the way the network device performs method 300 when the UE is operating in RRC idle mode or RRC inactive mode may differ from the way the network device performs method 300 when the UE is operating in RRC connected mode.

[0079] When the UE operates in RRC idle mode or RRC inactive mode, and in some implementations, the WUI can be selected, formatted, or configured as a UE-specific WUI (i.e., a WUI specific to only one UE). In some implementations of these implementations, the UE-specific WUI may be or include the UE's complete UE ID. In some implementations of these implementations, the UE-specific WUI may be or include a portion of the complete UE ID.

[0080] When the UE is operating in RRC idle mode or RRC inactive mode, and the WUI is the UE's complete UE ID, method 300 may include formatting the LP-WUS as an indicator that includes the UE's complete UE ID. The complete UE ID may be, for example, 5G-S-TMSI.

[0081] When the UE operates in RRC idle mode or RRC inactive mode, and the UE's LP-WUS MO has a one-to-one correspondence with the UE's PO, the WUI can be or includes a portion of the UE's complete UE ID. The complete UE ID can be defined by a first part (e.g., LSB) and a second part (e.g., MSB) of the complete UE ID. In these embodiments, method 300 may include configuring the UE's PO to explicitly or implicitly include the first part of the complete UE ID, such that the UE can derive the first part of the complete UE ID from the UE's PO. Method 300 may also include an indicator formatting the LP-WUS to include the second part of the complete UE ID. In some cases, method 300 may include a method based on dividing the complete UE ID by N. s The floor function of *N determines the indicator of the second part of UEID (i.e., UE_ID_WUS).

[0082] UE_ID_WUS = floor(full UE ID / (N s * N))

[0083] Where N s N is the number of POs per paging frame, N is the number of paging frames in a paging cycle, and Ns*N is the number of POs per paging cycle. The MSB of the complete UE ID can be derived from UE_ID_WUS. The MSB of the complete UE ID, combined with the LSB derived from the PO, provides the complete UE ID.

[0084] In other implementations, when the UE operates in RRC idle mode or RRC inactive mode, and the UE's LP-WUS MO is configured separately or does not have a one-to-one correspondence with the UE's PO, the network device may select, format, or configure the WUI as part of the UE's complete UE ID. The complete UE ID may be defined by a first part (e.g., LSB) and a second part (e.g., MSB) of the complete UE ID. In these implementations, method 300 may include configuring the UE's LP-WUS MO timing from the first part of the complete UE ID, such that the first part of the complete UE ID can be derived from the UE's LP-WUS MO. Method 300 may also include configuring the WUI for the UE to include an indicator that includes the second part of the complete UE ID. As an example, there may be a total of K LP-WUS MOs in one cycle, where K=2. M The UE can determine which of the K LP-WUS MOs to monitor based on the set of M MSBs that define the first part of the complete UE ID. The remaining bits of the complete UE ID (i.e., the second part of the UE ID) can be indicated in the LP-WUS.

[0085] As an example of the implementation scheme described last, each UE in the set of UEs communicating with the cell may be configured by the network device with a different LP-WUS MO, such that the LP-WUS only needs to carry a unit WUI (for wake-up or non-wake-up) to wake up the UE. As another example, N UEs may be configured with the same LP-WUS MO, and the LP-WUS may be formatted or configured to include an N-bit bitmap, where each bit is the WUI for the corresponding UE.

[0086] When a UE operates in RRC idle mode or RRC inactive mode, and in some implementations, the network device may select, format, or configure the WUI as an indicator of the UE group ID (i.e., the WUI for multiple UEs), and the UE group ID may correspond to the UE group that includes that UE. The UE group ID may take various forms.

[0087] In some implementations, the UE group ID may be explicitly assigned by the network (e.g., by a network device). For example, the UE group ID may be assigned to multiple UEs, similar to how a CN assigns a subgroup ID to a PEI in 3GPP Rel-17. In these implementations, method 300 may include transmitting the UE group ID assigned to the UE group that includes the UE via a transceiver and over the air interface to the UE. In some cases, this transmission may be sent while the UE is in RRC connected mode. Method 300 may also include selecting, formatting, or configuring the WUI for the UE to include an indicator of the UE group ID.

[0088] In some implementations, the UE group ID may be or include multiple bits (e.g., a subset of bits) explicitly obtained from the complete UE ID. For example, consider a group ID consisting of bit a. 47 a 46 A complete UE ID consisting of a1, a2, a3, a2, a1, a0, ..., a3, a2, a1, a0, where a1, a2, a3, a2, a3, a2, a3, a4, ... ...4, ..., a3, a2, a3, a4, ..., a3, ..., a4, ..., a3, ..., a4, ..., a3, ..., a4, ..., a3, ..., a3, ..., a4, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3, ..., a3 47 It is the MSB, and a0 is the LSB. If there are 8 LP-WUS MOs based on the three LSBs of the complete UE ID (i.e., based on bits a2, a1, a0, such that bits a2, a1, a0 are derived from a specific LP-WUS MO), then the UE group ID can be defined based on bits a6, a5, a4, a3, or any other set of bits from the complete UE ID (other than those from bits a2, a1, a0). A set of four bits, such as bits a6, a5, a4, a3, will support up to sixteen different UE groups. Therefore, in these embodiments, the complete UE ID of the UE may include at least a portion corresponding to the UE group ID; or the complete UE ID of the UE may include at least a first part of the UE ID and a second part of the UE ID, wherein the second part of the UE ID corresponds to the UE group ID of the UE group that includes the UE. Also in these embodiments, method 300 may include an indicator for selecting, formatting, or configuring the WUI for the UE to include the UE group ID.

[0089] In some implementations, the WUI may be or include an indicator of the UE group ID containing the UE group, but the UE group ID may be determined in other ways. For example, the UE group ID may be based at least in part on the UE's complete UE ID and the total number of UE groups in the LP-WUS MO. In some implementations, the UE group ID may additionally or alternatively be based at least in part on the maximum number of UE groups allowed in the LP-WUS MO. For example, when there is a one-to-one correspondence between the LP-WUS MO and the UE's legacy PO, and when the LSB of the UE's complete UE ID is implicitly carried in the UE's PO (i.e., can be derived from the UE's PO), the UE group ID for the total L UE groups in the LP-WUS MO and the maximum number L1 UE groups allowed in the LP-WUS MO may be determined (e.g., by the network device) using any of the following formulas:

[0090] A. ,

[0091] in

[0092] B. ,

[0093] in

[0094] C.

[0095] in

[0096] D.

[0097] E.

[0098] Option A assigns a UE group ID to multiple UEs, similar to how the CN assigns subgroup IDs to PEIs in 3GPP Rel-17. 1024 is the maximum allowed number of POs in a paging cycle.

[0099] In some implementations, an offset can be applied to the UE group ID determined using any of the methods described above (or to the UE group ID determined using other methods) to obtain the final UE group ID. For example, three UE group IDs may be assigned by the network (e.g., by a network device), and an additional UE group ID may be determined using one of the options A through E above. The offset can then be applied to each of the UE group IDs determined using one of options A through E. In some cases, the offset can be used to ensure that different methods of assigning / determining UE group IDs do not result in duplicate UE group IDs.

[0100] When the UE of method 300 operates in RRC idle mode or RRC inactive mode, the WUI for the UE can be selected, formatted, or configured to take a different form. In some implementations, the WUI can be or include the state of bits in a bitmap, where each bit in the bitmap corresponds to a different UE or UE group that can be woken up within the LP-WUS MO. For example, a UE can be assigned to bit seven of the LP-WUS payload, or a UE can be assigned to a UE group that is assigned to bit seven of the LP-WUS payload. If bit seven of the LP-WUS payload is set (e.g., the bit is logic "1"), then LP-WUS is considered to include the WUI for the UE. If bit seven of the LP-WUS payload is not set (e.g., the bit is logic "0"), then LP-WUS is considered not to include the WUI for the UE. The length of the bitmap can be equal to the number of UEs or UE groups in the LP-WUS MO.

[0101] When the UE of method 300 operates in RRC idle mode or RRC inactive mode, and in some embodiments, the WUI in method 300 may be selected, formatted, or configured as part or all of the UE's complete UE ID, or part or all of the complete UE group ID of the UE group that includes the UE, and may be explicitly included as part or all of the LP-WUS payload. For example, the WUI may be the complete UE ID or a part of the complete UE ID, as described herein. The LP-WUS payload may be further encoded and modulated before transmission.

[0102] When the UE of method 300 operates in RRC idle mode or RRC inactive mode, and in some embodiments, the WUI in method 300 may be selected, formatted, or configured as one or more sequences in the time and / or frequency domain (i.e., on a set of multiple subcarriers on which the LP-WUS is received) defined by the bit set carried by the LP-WUS. In these embodiments, method 200 may include: when the UE operates in RRC connected mode, formatting the LP-WUS to include a WUI for the UE by using one or more sequences in the time and / or frequency domain defined by the bit set carried by the LP-WUS. The sequences may be mapped to at least a portion of the UE's complete UE ID or at least a portion of the UE group ID of a UE group that includes the UE.

[0103] In any of the above embodiments of method 300, the LP-WUS may carry a WUI for one or more UEs or UE groups, or a WUI for a UE, UE group, or a mixture of UEs and UE groups (e.g., in a bitmap, or in a cascading indicator for UEs and / or UE groups).

[0104] When the UE operates in RRC connection mode, it is expected that LP-WUS will control the UE's PDCCH monitoring behavior. Therefore, when the UE of method 300 operates in RRC connection mode, it may be preferable to select, format, or configure the UE-specific WUI.

[0105] When the UE of method 300 operates in RRC connection mode, and in some embodiments, the UE may be configured for single-carrier operation with network devices (i.e., in single-carrier mode). In other embodiments, the UE may be configured for multi-carrier operation with one or more network devices (e.g., using two or more carriers associated with one or more cells in multi-carrier mode or CA mode).

[0106] When the UE operates in RRC connected mode and is configured for single-carrier operation, and in some implementations, the WUI for the UE can be selected, formatted, or configured as the UE's C-RNTI, i.e., a 16-bit value. The C-RNTI can be explicitly carried by LP-WUS (e.g., as a set of bits in the LP-WUS payload) or implicitly carried by LP-WUS (e.g., for scrambling CRC included in the LP-WUS payload). In some cases, LP-WUS can carry multiple UE C-RNTIs (i.e., WUIs).

[0107] When a UE operates in RRC connected mode and is configured for single-carrier operation, and in some implementations, the UE may be configured with a UE-specific UE ID for LP-WUS (or more generally, for low-power signaling). In these implementations, the WUI for the UE may carry the UE-specific UE ID. In some cases, the UE-specific UE ID may be shorter than the C-RNTI. For example, the network may consider the number of connected UEs that need to rely on LP-WUS signaling in a cell or other area and may determine the number of bits (or length) required to assign a unique UE-specific UE ID to that number of connected UEs. The UE-specific UE ID may be explicitly carried by LP-WUS (e.g., as a set of bits in the LP-WUS payload) or implicitly carried by LP-WUS (e.g., for scrambling CRC included in the LP-WUS payload). In some cases, LP-WUS may carry the UE-specific UE IDs (i.e., WUIs) of multiple UEs. In these implementations, method 300 may include selecting, formatting, or configuring the WUI for the UE as the UE's UE-specific UE ID.

[0108] When a UE operates in RRC connected mode and is configured for single-carrier operation, and in some implementations, the network device may assign bit positions (for the WUI) to the UE in the LP-WUS payload. For example, the WUI may be or include the state of bits in a bitmap, where each bit in the bitmap corresponds to a different UE that can be woken up within the LP-WUS MO (or corresponds to a different carrier or cell for the UE). For example, a UE may be assigned to bit seven of the LP-WUS payload. If bit seven of the LP-WUS payload is set (e.g., the bit is logic "1"), then the LP-WUS is considered to include the WUI for the UE. If bit seven of the LP-WUS payload is not set (e.g., the bit is logic "0"), then the LP-WUS is considered not to include the WUI for the UE. The length of the bitmap may be equal to the number of UEs in the LP-WUS MO. This is a form of group common signaling that carries UE-specific WUIs for multiple UEs.

[0109] When a UE operates in RRC connected mode and is configured for single-carrier operation, and in some embodiments, the network device may assign one or more UE-specific sets of LP-WUS resources to the UE, and may assign different UE-specific sets of one or more LP-WUS resources to different UEs (or different carriers or cells of the UE). Each UE-specific set of resources may include different time-frequency resources, or different sequences on shared time-frequency resources. The state of one or more UE-specific sets of resources provides a WUI for the UE. In these embodiments, method 300 may include: sending an indication to the UE of one or more UE-specific sets of LP-WUS resources, and, when the UE operates in RRC connected mode, selecting, formatting, or configuring the WUI as a predetermined or configured state of one or more UE-specific sets of LP-WUS resources.

[0110] When the UE of method 300 operates in RRC connected mode and is configured for multi-carrier operation, it may be useful to configure the UE to monitor LP-WUS on only one or a few cells. This reduces the complexity of the UE and saves power. In some cases, the single cell for which LP-WUS is to be monitored can be predefined (e.g., in 3GPP TS) as the UE's primary cell. Alternatively, the single cell for which the UE is to monitor LP-WUS can be configured by the network (e.g., by network equipment). In some implementations, the single cell can be configured as the UE's serving cell. In some implementations, the single cell can be configured as the UE's non-serving cell.

[0111] When the UE operates in RRC connectivity mode and is configured for multi-carrier operation, and in various implementations, method 300 may include configuring the UE to monitor the PDCCH on a single carrier or cell, or on one or more carriers or from one or more cells, or on each carrier or cell in one or more carrier groups or cell groups, as referenced. Figure 2 As described.

[0112] The embodiments contemplated herein include one or more non-transitory computer-readable media storing 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 200 or 300. In the context of method 200, the non-transitory computer-readable medium may be, for example, the memory of a UE (such as memory 506 of a wireless device 502 as a UE, as described herein). In the context of method 300, the non-transitory computer-readable medium may be, for example, the memory of a network device (such as memory 524 of a network device 520, as described herein).

[0113] The embodiments contemplated herein include an apparatus having logic components, modules, or circuitry for performing one or more elements of method 200 or 300. In the context of method 200, the apparatus may be, for example, a UE (such as wireless device 502 as a UE). In the context of method 300, the apparatus may be, for example, a network device (such as network device 520, as described herein).

[0114] The embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media that use or store instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 200 or 300. In the context of method 200, the apparatus may be, for example, a UE (such as wireless device 502 as a UE, as described herein). In the context of method 300, the apparatus may be, for example, a network device (such as network device 520, as described herein).

[0115] The implementation schemes envisioned herein include signals as described or associated with one or more elements of method 200 or 300.

[0116] The embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of method 200 or 300. In the context of method 200, the processor may be a processor of a UE (such as processor 504 of wireless device 502 as a UE, as described herein), and the instructions may be located, for example, in the processor and / or in the memory of the UE (such as memory 506 of wireless device 502 as a UE, as described herein). In the context of method 300, the processor may be a processor of a network device (such as processor 522 of network device 520, as described herein), and the instructions may be located, for example, in the processor and / or in the memory of the network device (such as memory 524 of network device 520, as described herein).

[0117] Figure 4 An example architecture of a wireless communication system according to the implementation scheme described herein is illustrated. The following description is provided for example wireless communication system 400, which operates in conjunction with LTE system standards or specifications and / or 5G or NR system standards or specifications as provided by 3GPP technical specifications.

[0118] As shown in the figure, the wireless communication system 400 includes UE 402 and UE 404 (but any number of UEs may be used). In this example, UE 402 and UE 404 are exemplified as smartphones (e.g., handheld touchscreen 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.

[0119] UE 402 and UE 404 can be configured to communicatively couple with RAN 406. In implementations, RAN 406 can be NG-RAN, E-UTRAN, etc. UE 402 and UE 404 utilize connections (or channels) with RAN 406 (shown as connection 408 and connection 410, respectively), each of these connections including a physical communication interface. RAN 406 may include one or more network devices (such as base station 412 and base station 414) implementing connection 408 and connection 410.

[0120] In this example, Connection 408 and Connection 410 are air interfaces that enable this type of communication coupling and are compliant with the RAT used by RAN 406, such as LTE and / or NR, for example.

[0121] In some implementations, UE 402 and UE 404 may also exchange communication data directly via sidelink interface 416. UE 404 is shown configured to access an access point (shown as AP 418) via connection 420. By way of example, connection 420 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, while AP 418 may include Wi-Fi. ® Router. In this example, AP 418 can connect to another network (e.g., the Internet) without going through CN 424.

[0122] In the implementation, UE 402 and UE 404 may be configured to communicate with each other or with base station 412 and / or base station 414 via a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication)). However, the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0123] In some implementations, all or some of the base stations in base station 412 or base station 414 may be implemented as one or more software entities running on a server computer as part of a virtual network. Furthermore, or in other implementations, base station 412 or base station 414 may be configured to communicate with each other via interface 422. In implementations where the wireless communication system 400 is an LTE system (e.g., when CN 424 is an EPC), interface 422 may be an X2 interface. This X2 interface may be defined between two or more network devices (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In implementations where the wireless communication system 400 is an NR system (e.g., when CN 424 is a 5GC), interface 422 may be an Xn interface. This Xn interface may be defined between two or more network devices (e.g., two or more gNBs, etc.) connected to the 5GC, between base station 412 (e.g., gNB) and eNB connected to the 5GC, and / or between two eNBs connected to the 5GC (e.g., CN 424).

[0124] RAN 406 is shown communicatively coupled to CN 424. CN 424 may include one or more network elements 426 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 402 and UE 404) connected to CN 424 via RAN 406. Components of CN 424 may be implemented in a single physical device or a separate physical device including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media).

[0125] In the implementation scheme, CN 424 may be an EPC, and RAN 406 may be connected to CN 424 via S1 interface 428. In the implementation scheme, S1 interface 428 may be divided into two parts: an S1 user plane (S1-U) interface, which carries service data between base station 412 or base station 414 and the service gateway (S-GW); and an S1-MME interface, which is the signaling interface between base station 412 or base station 414 and the mobility management entity (MME).

[0126] In the implementation scheme, CN 424 may be a 5GC, and RAN 406 may be connected to CN 424 via NG interface 428. In the implementation scheme, NG interface 428 may be divided into two parts: an NG user plane (NG-U) interface, which carries service data between base station 412 or base station 414 and user plane function (UPF); and an S1 control plane (NG-C) interface, which is the signaling interface between base station 412 or base station 414 and access and mobility management function (AMF).

[0127] Generally, application server 430 may be an element that provides applications (e.g., packet-switched data services) that use Internet Protocol (IP) bearer resources with CN 424. Application server 430 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for UE 402 and UE 404 via CN 424. Application server 430 can communicate with CN 424 through IP communication interface 432.

[0128] Figure 5 An example system 500 for performing signaling 538 between a wireless device 502 and a network device 520 according to an embodiment described herein is illustrated. System 500 may be part of a wireless communication system as described herein. Wireless device 502 may be, for example, a UE of a wireless communication system. Network device 520 may be, for example, a base station (e.g., an eNB or gNB) or a radio headend of a wireless communication system.

[0129] Wireless device 502 may include one or more processors 504. Processor 504 is executable instructions that cause various operations of wireless device 502 to be performed as described herein. Processor 504 may include one or more baseband processors, which are implemented using, for example, a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), controller, field-programmable gate array (FPGA) device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0130] Wireless device 502 may include memory 506. Memory 506 may be a non-transitory computer-readable storage medium that stores instructions 508, which may include, for example, instructions executed by processor 504. Instructions 508 may also be referred to as program code or a computer program. Memory 506 may also store data used by processor 504 and results calculated by the processor.

[0131] Wireless device 502 may include one or more transceivers 510 (also collectively referred to as transceiver 510), which may include radio frequency (RF) transmitter and / or receiver circuitry that uses antenna 512 of wireless device 502 to facilitate to-and-for and / or signaling from wireless device 502 to other devices (e.g., network device 520) and / or from wireless device 502 according to a corresponding RAT (e.g., signaling 538). Wireless device 502 may also include LP-WUR 514 that enables wireless device 502 to use antenna 512 to detect and / or measure LP-WUS received from one or more other devices.

[0132] Wireless device 502 may include one or more antennas 512 (e.g., one, two, four, eight, or more). In embodiments with multiple antennas 512, wireless device 502 may fully utilize the spatial diversity of such multiple antennas 512 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, MIMO behavior (referring to multiple antennas used at each of the transmitting and receiving devices to implement this aspect). MIMO transmission by wireless device 502 may be implemented according to pre-decoding (or digital beamforming) applied to wireless device 502, which multiplexes the data streams among antennas 512 based on known or assumed channel characteristics, such that each data stream is received with appropriate signal strength relative to the other streams at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream). Some embodiments may use a single-user MIMO (SU-MIMO) method (where all data streams are directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) method (where individual data streams may be directed to individual (different) receivers at different locations in the spatial domain).

[0133] In some implementations with multiple antennas, wireless device 502 can implement analog beamforming technology, whereby the phase of the signal transmitted by antenna 512 is relatively adjusted so that the (joint) transmission of antenna 512 can be directed (this is sometimes referred to as beam control).

[0134] Wireless device 502 may include one or more interfaces 516. Interfaces 516 can be used to provide input to or from wireless device 502. For example, wireless device 502 as a UE may include interfaces 516 such as a microphone, speaker, touchscreen, buttons, etc., to allow input and / or output from a user of the UE to the UE. Other interfaces of such UEs may consist of transmitters, receivers, and other circuitry (e.g., in addition to the transceiver 510 / antenna 512 already described), allowing communication between the UE and other devices, and can be configured according to known protocols (e.g., Wi-Fi). ®,Bluetooth ® (etc.) to perform the operation.

[0135] Wireless device 502 may include LP-WUS and WUI processing modules 518. LP-WUS and WUI processing modules 518 may be implemented via hardware, software, or a combination thereof. For example, LP-WUS and WUI processing modules 518 may be implemented as a processor, circuitry, and / or instructions 508 stored in memory 506 and executed by processor 504. In some examples, LP-WUS and WUI processing modules 518 may be integrated within processor 504 and / or transceiver 510. For example, LP-WUS and WUI processing modules 518 may be implemented via a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 504 or transceiver 510.

[0136] From the perspective of a wireless device or UE, the LP-WUS and WUI processing module 518 can be used in various aspects of this disclosure, for example, Figures 1 to 3 All aspects. The LP-WUS and WUI processing module 518 can be configured, for example, to enable the LP-WUS to monitor the LP-WUS received from the network device 520 (or other network device) and to determine whether the LP-WUS includes a WUI for the wireless device 502.

[0137] Network device 520 may include one or more processors 522. Processor 522 may execute instructions to perform various operations of network device 520 as described herein. Processor 522 may include one or more baseband processors, which may be implemented using, for example, a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0138] Network device 520 may include memory 524. Memory 524 may be a non-transitory computer-readable storage medium that stores instructions 526, which may include, for example, instructions executed by processor 522. Instructions 526 may also be referred to as program code or a computer program. Memory 524 may also store data used by processor 522 and results calculated by the processor.

[0139] Network device 520 may include one or more transceivers 528 (also collectively referred to as transceiver 528), which may include RF transmitter and / or receiver circuitry that uses antenna 530 of network device 520 to facilitate to-and / or signaling from network device 520 to other devices (e.g., wireless device 502) and / or from network device 520 (e.g., signaling 538) in accordance with the corresponding RAT.

[0140] Network device 520 may include one or more antennas 530 (e.g., one, two, four or more). In embodiments having multiple antennas 530, network device 520 may perform MIMO, digital beamforming, analog beamforming, beam control, etc., as described.

[0141] Network device 520 may include one or more interfaces 532. Interface 532 can be used to provide input to or output to network device 520. For example, RAN network device 520 (e.g., base station, radio head, etc.) may include interfaces 532 consisting of transmitters, receivers, and other circuitry (e.g., in addition to the transceiver 528 / antenna 530 described), which enable network device 520 to communicate with other equipment in the network and / or enable network device 520 to communicate with external networks, computers, databases, etc., for the purpose of operating, managing, and maintaining network device 520 or other equipment operatively connected to it.

[0142] Network device 520 may include one or more LP-WUS and WUI formatting modules 534. The LP-WUS and WUI formatting modules 534 may be implemented via hardware, software, or a combination thereof. For example, the LP-WUS and WUI formatting modules 534 may be implemented as a processor, circuitry, and / or instructions 526 stored in memory 524 and executed by processor 522. In some examples, the LP-WUS and WUI formatting modules 534 may be integrated within processor 522 and / or transceiver 528. For example, the LP-WUS and WUI formatting modules 534 may be implemented via a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 522 or transceiver 528.

[0143] From the perspective of network devices, the LP-WUS and WUI formatting module 534 can be used in various aspects of this disclosure, for example, Figures 1 to 3 The LP-WUS and WUI formatting module 534 can be configured, for example, to select, format, or configure a WUI for a UE or a group of UEs, and to format an LP-WUS to carry that WUI (or multiple WUIs). The processor 522 can transmit the LP-WUS using the transceiver 528 and the antenna 530 (to the wireless device 502, to one or more other wireless devices, or in broadcast mode).

[0144] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor (or processor) as 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 presented herein. Similarly, circuitry associated with a UE, network device, network element, etc., as 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 presented herein.

[0145] 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 embodiments provides illustrative and descriptive information, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form described. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from the practice of various embodiments.

[0146] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical parts for performing the operations; or may include a combination of hardware, software, and / or firmware.

[0147] The systems described herein relate to specific implementations but are provided as examples. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in one implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be understood that, unless expressly stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0148] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 any permitted use should be clearly explained to the user.

[0149] Although the foregoing has been described in considerable detail for clarity, it will be apparent that changes and modifications can be made without departing from the principles of the invention. It should be noted that many alternative ways exist to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this description is not limited to the details given herein, but can be modified within the scope and equivalents of the appended claims.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: A transceiver having a first nominal operating power; A low-power (LP) wake-up receiver (LP-WUR) having a second nominal operating power less than the first nominal operating power, the LP-WUR being configured to receive an LP wake-up signal (LP-WUS) via an air interface when the transceiver is in a low-power state; and Processor, the processor being configured to: It is determined that the LP-WUS includes a wake-up indication (WUI) for the UE; and The transceiver is woken up in response to determining that the LP-WUS includes the WUI for the UE.

2. The UE according to claim 1, wherein: The processor is configured to: The UE operates in Radio Resource Control (RRC) idle mode or RRC inactive mode; and When the UE is operated in the RRC idle mode or the RRC inactive mode, the LP-WUS is determined to include the WUI for the UE by extracting an indicator of the complete UE identifier (ID) of the UE from the LP-WUS.

3. The UE according to claim 1, wherein: The complete UE identifier (ID) of the UE is defined by the first part of the complete UE ID and the second part of the complete UE ID; and The processor is configured to: The paging timing (PO) of the UE is determined from the first part of the complete UE ID; The UE operates in Radio Resource Control (RRC) idle mode or RRC inactive mode; as well as When the UE is operated in the RRC idle mode or the RRC inactive mode The LP-WUR is configured to monitor the LP-WUS monitoring time (MO) for the LP-WUS, the LP-WUS MO corresponding to the PO; as well as The LP-WUS is determined to include the WUI for the UE by extracting the indicator of the second part of the complete UE ID from the LP-WUS as the WUI for the UE.

4. The UE of claim 3, wherein the processor is configured to determine the second part of the UE ID based on a floor function of the complete UE ID divided by Ns*N, where Ns is the number of POs per paging frame and N is the number of paging frames in a paging cycle.

5. The UE according to claim 1, wherein: The complete UE identifier (ID) of the UE is defined by the first part of the complete UE ID and the second part of the complete UE ID; and The processor is configured to: The LP-WUS monitoring timing (MO) of the UE is determined from the first part of the UE ID; The UE operates in Radio Resource Control (RRC) idle mode or RRC inactive mode; as well as When the UE is operated in the RRC idle mode or the RRC inactive mode Configure the LP-WUR to monitor the LP-WUS MO used by the LP-WUS; and The LP-WUS is determined to include the WUI for the UE by extracting the indicator of the second part of the UE ID from the LP-WUS as the WUI for the UE.

6. The UE according to claim 1, wherein: The processor is configured to: Determine the UE group identifier (ID) assigned to the UE group including the UE from the transmissions received via the transceiver; The UE operates in Radio Resource Control (RRC) idle mode or RRC inactive mode; as well as When the UE is operated in the RRC idle mode or the RRC inactive mode, the LP-WUS is determined to include the WUI for the UE by extracting the indicator of the UE group ID from the LP-WUS as the WUI for the UE.

7. The UE according to claim 1, wherein: The complete UE identifier (ID) of the UE includes at least a portion corresponding to the UE group ID of the UE group that includes the UE; and The processor is configured to: The UE operates in Radio Resource Control (RRC) idle mode or RRC inactive mode; as well as When the UE is operated in the RRC idle mode or the RRC inactive mode, the LP-WUS is determined to include the WUI for the UE by extracting the indicator of the UE group ID from the LP-WUS as the WUI for the UE.

8. The UE according to claim 1, wherein: The WUI includes an indicator of the UE group identifier (ID) containing the UE group of the UE; and The UE group ID is based at least in part on the complete UE ID of the UE and the total number of UE groups in the LP-WUS monitoring time (MO).

9. The UE of claim 8, wherein the UE group ID is further based at least in part on the maximum number of UE groups allowed in the LP-WUS MO.

10. The UE according to claim 1, wherein: The processor is configured to operate the UE in Radio Resource Control (RRC) idle mode or RRC inactive mode; and The WUI includes the state of bits in a bitmap, where each bit corresponds to a different UE or a different UE group ID.

11. The UE according to claim 1, wherein: The processor is configured to operate the UE in Radio Resource Control (RRC) idle mode or RRC inactive mode; and The WUI includes at least a portion of the complete UE identifier (ID) of the UE or at least a portion of the complete UE group ID of the UE group of the UE.

12. The UE according to claim 1, wherein: The processor is configured to: The UE operates in Radio Resource Control (RRC) idle mode or RRC inactive mode; and When the UE is operated in the RRC idle mode or the RRC inactive mode, the LP-WUS is determined to include the WUI for the UE in the following manner: Determine one or more sequences in at least one of the time or frequency domains as defined by the bit set carried by the LP-WUS; and Map the one or more sequences to at least a portion of the complete UE identifier (ID) of the UE or at least a portion of the complete UE group ID of a UE group that includes the UE.

13. The UE according to claim 1, wherein: The processor is configured to: The UE operates in Radio Resource Control (RRC) connection mode when configured for single-carrier operation; as well as When the UE is operating in the RRC connection mode, the LP-WUS is determined to include the WUI for the UE by extracting the UE's Cell Radio Network Temporary Identifier (C-RNTI) from the LP-WUS.

14. The UE according to claim 1, wherein: The processor is configured to: Receive the UE-specific UE identifier (ID) of the UE from the network; The UE operates in Radio Resource Control (RRC) connection mode when configured for single-carrier operation; as well as When the UE is operating in the RRC connection mode, the LP-WUS is determined to include the WUI for the UE by extracting the UE-specific UE ID of the UE from the LP-WUS.

15. The UE according to claim 1, wherein: The processor is configured to operate the UE in Radio Resource Control (RRC) connection mode when configured for single-carrier operation; and The WUI includes the state of bits in a bitmap, where each bit in the bitmap corresponds to a different UE.

16. The UE according to claim 1, wherein: The processor is configured to: Receive from the network an indication of a UE-specific set of one or more resources of the LP-WUS; The UE operates in Radio Resource Control (RRC) connection mode when configured for single-carrier operation; as well as When the UE is operating in the RRC connection mode, the LP-WUS is determined to include the WUI for the UE by identifying the predetermined or configuration state of the UE-specific set of one or more resources of the LP-WUS from the LP-WUS.

17. The UE according to claim 1, wherein: The processor is configured to: The UE operates in Radio Resource Control (RRC) connection mode when configured for multi-carrier operation; and When the UE is operating in the RRC connection mode, and after waking the transceiver in response to determining that the LP-WUS includes the WUI for the UE, the Physical Downlink Control Channel (PDCCH) is monitored on at least one of the following: All carriers associated with the multi-carrier operation; or All cells associated with the multicarrier operation.

18. The UE according to claim 1, wherein: The WUI for the UE is associated with a carrier or cell; The processor is configured to: The UE operates in Radio Resource Control (RRC) connection mode when configured for multi-carrier operation; as well as When the UE is operating in the RRC connection mode, and after waking up the transceiver in response to determining that the LP-WUS includes the WUI for the UE, the physical downlink control channel (PDCCH) is monitored on the carrier or the cell.

19. The UE according to claim 1, wherein: The WUI for the UE is associated with a carrier group or cell group; The processor is configured to: The UE operates in Radio Resource Control (RRC) connection mode when configured for multi-carrier operation; as well as When the UE is operating in the RRC connection mode, and after waking up the transceiver in response to determining that the LP-WUS includes the WUI for the UE, the physical downlink control channel (PDCCH) is monitored on each of the carriers or cells in the carrier group or the cell group.

20. A network device, the network device comprising: transceiver; and Processor, the processor being configured to: Select, format, or configure the wake-up indication (WUI) for user equipment (UE); Transmit or broadcast, via the air interface and using the transceiver, a low-power (LP) wake-up signal (LP-WUS) for the WUI of the UE; and The transceiver is used over the air to perform at least one of sending to or receiving from the UE, after a waiting period following the transmission of the LP-WUS.

Images