Subgroup identifier for low power wake-up signal

Abstract

This application relates to devices and assemblies, including apparatuses, systems, and methods, that use sub-group identifiers (IDs) for low power wake-up signals (LP-WUSs). In an example, a LP-WUS configuration can be configured to a user equipment (UE) separately from a paging early indication (PEI) configuration. The LP-WUS configuration can indicate a first sub-group ID for a LP-WUS, while the PEI configuration can indicate a second sub-group ID for a PEI. A network can wake up a sub-group of UEs associated with the first sub-group ID by using a LP-WUS, and can indicate to the UEs to monitor a paging occasion, where the indication can be via a PEI indicating the second sub-group ID.

Description

Background Technology

[0001] Fifth-generation mobile networks (5G) are a wireless standard designed to improve data transmission speed, reliability, availability, and more. While still under development, the standard includes numerous details related to, for example, user equipment (UE) communicating with the network to transmit and receive data. In one example, the UE can operate in different modes to reduce its power consumption and switch between these modes based on signaling from the network. Attached Figure Description

[0002] Figure 1 Examples of network environments based on some implementation schemes are shown.

[0003] Figure 2 Examples of using low-power wake-up signal (LP-WUS) and paging early indication (PEI) according to some implementation schemes are illustrated.

[0004] Figure 3 Examples of sequence diagrams for using LP-WUS and PEI according to some implementation schemes are illustrated.

[0005] Figure 4 Examples of operational flow / algorithm structures for determining subgroup identifiers (IDs) are illustrated according to some implementation schemes.

[0006] Figure 5 Examples of flow / algorithm structures for using subgroup IDs for LP-WUS and PEI, according to some implementation schemes, are illustrated.

[0007] Figure 6 Another example of a process / algorithm structure for using subgroup IDs for LP-WUS and PEI, according to some implementation schemes, is illustrated.

[0008] Figure 7 Examples of receiving components according to some implementation schemes are shown.

[0009] Figure 8 Examples of user equipment (UE) according to some implementation schemes are illustrated.

[0010] Figure 9 Examples of base stations based on some implementation schemes are shown. Detailed Implementation

[0011] Implementations of this disclosure particularly relate to using a subgroup identifier (ID) for a low-power wake-up signal (LP-WUS). In one example, the LP-WUS configuration can be configured to the user equipment (UE) separately from the early paging indication (PEI) configuration. The LP-WUS configuration may indicate a first subgroup ID for the LP-WUS, while the PEI configuration may indicate a second subgroup ID for the PEI. These two subgroup IDs can be used together to improve the UE's power consumption (e.g., increase its power savings). For example, when the network needs to paging a UE subgroup, the network sends an LP-WUS indicating wake-up for the first subgroup ID, followed by a PEI indicating paging monitoring for the second subgroup ID. The LP-WUS wakes up the UE. Upon determining the first subgroup ID, the UE abandons returning to sleep and receives the PEI. After determining the second subgroup ID, the UE continues to receive the paging physical downlink control channel (PDCCH). Conversely, suppose the PEI indicates paging monitoring for a different subgroup ID. In this case, the UE will return to sleep and will abandon receiving the paging PDCCH. Similarly, suppose the LP-WUS instruction indicates a wake-up for a different subgroup ID. In this case, the UE will return to sleep after receiving the LP-WUS. In both scenarios, the network can control UE paging at the granular level of two subgroups while achieving power savings.

[0012] In one example, the subgroup ID used for LP-WUS may correspond to a subgroup assigned by the core network. In another example, the subgroup ID used for LP-WUS may correspond to a subgroup based on the UE ID. In the latter case, the subgroup ID used for LP-WUS may be different from, but related to, or unrelated to, the subgroup ID used for PEI. These and other characteristics are further described below.

[0013] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and not limiting purposes in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some instances, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0014] The following is a glossary of terms that may be used in this disclosure.

[0015] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), digital signal processors (DSPs), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the aforementioned functionalities. The term "circuit" may also refer to a combination of one or more hardware elements and program code for executing the functionality (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0016] As used herein, the term "processor circuit" means, is part of, or includes: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" can refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures). The term "processor circuit" may be used synonymously with the term "processing circuit."

[0017] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0018] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0019] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0020] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources accessible to computer devices / systems via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0021] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0022] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0023] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0024] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0025] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0026] As used herein, the term "at least partially based on" can indicate that an item is based solely on another item and / or on an item of another item plus one or more additional items. For example, in an embodiment, determining item 1 based at least partially on item 2 can indicate determining item 1 based solely on item 2 and / or determining item 1 based on item 2 and one or more other items.

[0027] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include a UE 104 communicatively coupled to a base station 108 of a radio access network (RAN) 110. UE 104 and base station 108 may communicate via an air interface compatible with 3GPP TS, such as those defining fifth-generation (5G) new radio (NR) systems or higher. Base station 108 may provide user plane and control plane protocol termination to UE 104. Base station 108 may generate an LP-WUS and send it to UE 104. UE 104 may then receive the LP-WUS, detect its payload, and switch operating modes based on the payload (e.g., wake up the primary radio to monitor paging).

[0028] In some implementations, UE 104 and base station 108 may establish a data radio bearer (DRB) to support data transmission over a radio link between the two nodes. In one example, these DRBs may be used for services from extended reality (XR) applications that contain large amounts of data conveying real and virtual images and audio for presentation to a user.

[0029] Network environment 100 may also include core network 112. For example, core network 112 may include a 5th generation core network (5GC) or a newer generation core network. Core network 112 may be coupled to base station 108 via fiber optic or wireless backhaul. Core network 112 may provide functions to UE 104 via base station 108. These functions may include managing subscriber profile information, subscriber location, service authentication, or handover of voice and data sessions.

[0030] In some implementations, network environment 100 may further include UE 106. UE 106 may be coupled to UE 104 via a sidelink interface. In some implementations, UE 106 may act as a relay node to communicatively couple UE 104 to RAN 110. In other implementations, UE 106 and UE 104 may represent terminating nodes of a communication link. For example, UE 104 and 106 may exchange data with each other.

[0031] Base station 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels to transport channels and mapping transport channels to physical channels. Logical channels can transmit data between the Radio Link Control (RLC) and MAC layers; transport channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface. Physical channels may include the Physical Broadcast Channel (PBCH), the Physical Downlink Control Channel (PDCCH), and the Physical Downlink Shared Channel (PDSCH).

[0032] The PBCH can be used to broadcast system information that UE 104 can use for initial access to the serving cell. The PBCH can be transmitted in the SSB along with the Physical Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS). The SSB can be used by UE 104 during the cell search process (including cell selection and reselection) and for beam selection.

[0033] PDSCH can be used to transmit end-user application data, signaling radio bearer (SRB) messages, system information messages (other than MIBs), and SIs.

[0034] The PDCCH can transmit downlink control information (DCI), which is used by the scheduler of network node 108 to allocate both uplink and downlink resources. The DCI can also be used to provide uplink power control commands, configure time slot formats, or indicate that preemption has occurred.

[0035] Network node 108 can also send various reference signals to UE 104. These reference signals may include demodulation reference signals (DMRS) for PBCH, PDCCH, and PDSCH. UE 104 can compare the received version of the DMRS with a known sequence of transmitted DMRS to estimate the impact of the propagation channel. UE 104 can then apply the inverse channel of the propagation channel during the demodulation process transmitted on the corresponding physical channel.

[0036] Reference signals may also include Channel State Information Reference Signals (CSI-RS). The CSI-RS can be a multi-purpose downlink transmit signal used for CSI reporting, beam management, connection mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization. Similarly, the UE may transmit reference signals to base station 108 for measurements to be performed by base station 108 (e.g., in use cases where reciprocity is not assumed between downlink and uplink channels). These reference signals may include, for example, sounding reference signals (SRS).

[0037] Reference signals and information from the physical channel can be mapped to resources in the resource grid. For a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink), there exists a resource grid. The basic unit of the NR downlink resource grid can be a resource element, which can be defined by a subcarrier in the frequency domain and an orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include a PRB in the frequency domain and an OFDM symbol in the time domain, for example, twelve resource elements. A control channel element (CCE) can represent a resource group used to transmit the PDCCH. One CCE can be mapped to multiple REGs, for example, six REGs.

[0038] UE 104 can use physical uplink channels to send data and control information to base station 108. Different types of physical uplink channels are possible, including, for example, the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH). The PUCCH carries control information from UE 104 to base station 108, such as uplink control information (UCI), while the PUSCH carries data services (e.g., end-user application data) and may carry UCI.

[0039] UE 104 and base station 108 can perform beam management operations to identify and maintain desired beams for transmission in both the uplink and downlink directions. Beam management can be applied to both PDSCH and PDCCH in the downlink direction, and both PUSCH and PUCCH in the uplink direction.

[0040] In one example, communication with base station 108 may use channels in frequency range 1 (FR1), frequency range 2 (FR2), and / or higher frequency ranges (FRH). The FR1 band includes licensed and unlicensed frequency bands. The NR unlicensed band (NR-U) includes spectrum shared with other types of radio access technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A listen-before-speak (LBT) process can be used to avoid or minimize collisions between different RATs in the NR-U, whereby the device should apply a free channel assessment (CCA) check before using the channel.

[0041] When power saving is not required, UE 104 can operate in idle mode. When the network needs UE 104, the network (e.g., via base station 108) can send a paging message to UE 104. UE 104 periodically monitors the paging messages. For example, UE 104 wakes up at a defined paging time (PO) and monitors the paging messages. The paging message includes UE 104's Temporary Mobile Subscriber Identity (TMSI) value. If UE 104 does not find UE 104's TMSI within the paging message, UE 104 assumes it has not been paged and returns to idle mode. However, if UE 104 finds UE 104's TMSI within a paging message, the UE determines that the paging is addressed to it and initiates a radio resource control connection. Alternatively, the UE can monitor a wake-up signal (WUS). If a WUS is received for the UE, the UE wakes up and monitors the paging messages.

[0042] Low-power WUS (LP-WUS) can refer to a type of WUS that enables a receiver (referred to as a low-power wake-up receiver (LP-WUR)) to monitor and detect WUS signaling in the network using relatively lower power than conventional signal reception. Early Paging Indication (PEI) can refer to a paging enhancement for UE power saving, which sends an indication about whether the UE needs to monitor subsequent paging times. The implementation described herein in conjunction with LP-WUS and / or PEI at least achieves power saving.

[0043] In one example, base station 108 transmits configuration information 150 to UE 104 (e.g., via Radio Resource Control (RRC) signaling). Configuration information 150 may indicate LP-WUS configuration 130 and PEI configuration 140. These two configurations can be separated from each other by each including its own set of parameters (e.g., one set of parameters for LP-WUS and a separate set of parameters for PEI). Although these two configurations are separate, their specific values ​​can be equal, different, unrelated, or related (e.g., the value of LP-WUS configuration 130 can be derived from the value of PEI configuration 140). LP-WUS configuration 130 may indicate a first subgroup ID associated with a first UE subgroup. Configuring the first subgroup ID to UE 104 such that UE 104 belongs to the first UE subgroup for LP-WUS purposes. In other words, upon receiving an LP-WUS wake-up notification indicating the first subgroup ID, UE 104 can determine that LP-WUS wakes up UE 104. Similarly, PEI configuration 140 can indicate a second subgroup ID associated with the second UE subgroup. UE 104 is configured with a second subgroup ID such that, for the purposes of the PEI, UE 104 belongs to the second UE subgroup. In other words, upon receiving a PEI indicating paging monitoring for the second subgroup ID, UE 104 can determine when it will monitor for paging. The two UE subgroups can be different.

[0044] For illustration, consider the following scenario. For LP-WUS, "Subgroup ID 3" is configured for UE 104 and UE 106, but for PEI, "Subgroup ID 1" is configured for UE 104 and "Subgroup ID 2" is configured for UE 106. When paging UE 104 is required instead of UE 106, the network (e.g., base station 108) sends a wake-up indication for "Subgroup ID 3" in LP-WUS and an indication for "Subgroup ID 2" in PEI. LP-WUS wakes up both UE 104 and 106. After UE 104 and 106 wake up and receive PEI, UE 104 continues to receive paging PDCCH, but UE 106 does not need to receive paging PDCCH and can immediately return to sleep.

[0045] As explained above, each of the LP-WUS configuration 130 and PEI configuration 140 indicates a subgroup ID. For LP-WUS, the subgroup ID may correspond to a subgroup assigned by the core network (e.g., a first UE subgroup assigned by core network 112). Alternatively, for LP-WUS, the subgroup ID may correspond to a subgroup based on the UE ID (e.g., an ID derived by the UE from parameters of LP-WUS configuration 130). Similarly, for PEI, the subgroup ID may correspond to a subgroup assigned by the core network (e.g., a second UE subgroup assigned by core network 112). Alternatively, for PEI, the subgroup ID may correspond to a subgroup based on the UE ID (e.g., an ID derived by the UE from parameters of PEI configuration 140). It is possible that the type of subgroup ID (e.g., whether it is assigned by the core network or based on the UE ID) may differ between the two configurations 130 and 140. For example, UE 104 can use the subgroup ID assigned by the core network for PEI, while using a subgroup ID based on the UE ID for LP-WUS (or vice versa). In another example, UE 104 can use the subgroup ID assigned by the core network for both LP-WUS and PEI, where separate parameters are configured. In yet another example, UE 104 can use the subgroup ID based on the UE ID for both LP-WUS and PEI, but derive the subgroup ID differently or separately.

[0046] Figure 2 Example 200 illustrates the use of LP-WUS and PEI in some implementation schemes. PEI is specified in 3GPP Release 17. Typically, PEI supports subgroup-based indication. When the UE receives a positive indication for its subgroup in the PEI, the UE continues to receive paging DCI; otherwise, it may return to sleep. In 3GPP Release 18, a research project on Low Power Wake-up Signals and Receivers (LP WUS / WUR) for NR was completed. LP-WUS is considered for additional purposes, including for idle and inactive modes. In particular, LP-WUS can be used to trigger or indicate paging monitoring. In this case, LP-WUS can also support subgroup-based wake-up indication. As illustrated in Example 200, if PEI is configured, the possible UE behavior after receiving LP-WUS would be to wake up and receive PEI. Assuming PEI is configured and according to this configuration, the UE can then monitor paging opportunities. In this case, the subgroup ID used for LP-WUS can be designed to work in conjunction with the subgroup-based indication in the PEI.

[0047] Typically, a UE needs to periodically monitor the configured paging channel to detect upcoming traffic. A periodic paging opportunity (Po) can be configured for the UE. The UE monitors Po when operating in idle or inactive mode. Po 230 is defined by the PDCCH search space (denoted as paging PDCCH 232) and the associated paging PDSCH record (denoted as paging PDSCH 234). The UE monitors paging PDCCH 232. If a paging indication is present, the UE receives and decodes paging PDSCH 234, decodes the paging record (PDSCH), and learns the listed identifier of the actual paged entity (e.g., Radio Network Temporary Identifier (RNTI), Temporary Mobile Subscriber Identity (TMSI), etc.). If paged, the UE triggers a connection establishment procedure. Otherwise, the UE returns to deep sleep.

[0048] PEI 220 enhances paging by at least reducing the power consumption of the UE. PEI 220 may involve a finite-sized DCI search space or sequence transmitted before each PO 230. When operating in idle or inactive mode, the UE monitors the search space of PEI 220. When a PEI indication is present in the search space, the UE may monitor the next PO 230. Otherwise, the UE may return to deep sleep and skip detecting PO 230. Additionally, PEI 220 may be indicated for a specific idle and / or inactive UE subgroup. UEs may be grouped into paging subgroups. Each paging subgroup may have a subgroup ID for PEI. PEI 220 may indicate paging monitoring for a specific subgroup ID (e.g., the ID corresponding to an idle and / or inactive UE subgroup within an idle and / or inactive UE subgroup).

[0049] LP-WUS210 can also be another enhancement to paging. The UE can monitor a wake-up signal (WUS). If LP-WUS210 is received and indicated for the UE (e.g., by indicating a relevant subgroup ID), the UE wakes up in the next PO 230 and monitors the paging message. Otherwise, the UE can remain in a dormant state (e.g., as part of operation in an idle or inactive mode). Typically, LP-WUS210 can represent a type of wake-up signal that enables a receiver (called a low-power wake-up receiver (LP-WUR)) to monitor and detect WUS signaling of the network using relatively low power than conventional signal reception. LP-WUS210 can support subgroup-based wake-up indication. Specifically, LP-WUS210 can be indicated for a specific subgroup of idle and / or inactive UEs. UEs can be grouped into paging subgroups (which may be the same as or different from the PEI subgroups). Again, each paging subgroup can have a subgroup ID for LP-WUS. The LP-WUS210 can instruct wake-up for a specific subgroup ID (e.g., the ID of an idle and / or inactive UE subgroup corresponding to an idle and / or inactive UE subgroup).

[0050] In Example 200, from Figure 2 The top to bottom shows three scenarios. In all three scenarios, the UE (e.g., the example of UE 104) is configured with the first subgroup ID 212 for LP-WUS and the second subgroup ID 222 for PEI.

[0051] First Scene ( Figure 2 At the top of the page, the UE is paged. As shown, the UE receives and processes LP-WUS210. LP-WUS210 indicates a wake-up for the first subgroup ID 212. Therefore, the UE does not return to sleep. Instead, the UE receives and processes PEI 220. Here, PEI 220 indicates paging detection for the second subgroup ID 222. Therefore, the UE detects the next PO 230 instead of going to sleep.

[0052] In the second scene ( Figure 2 In the middle of this process, the UE is not paged. Here, the UE receives and processes LP-WUS 210. However, LP-WUS indicates a wake-up for a different subgroup ID used for LP-WUS (e.g., different from the first subgroup ID 212). Therefore, the UE returns to sleep 250 (e.g., transitions back to a sleep state in a sleep cycle, such as deep sleep or shallow sleep, where one or more components of the UE's radio frequency components are deactivated or powered off). Subsequent PEI 220 and subsequent PO 230 are not monitored because the UE is in sleep mode. In this case, there is no need to wake up the main radio.

[0053] In the third scenario ( Figure 2 At the bottom, the UE is not paged. Here, the UE receives and processes LP-WUS210. LP-WUS210 indicates a wake-up for the first subgroup ID 212. Therefore, the UE does not return to sleep. Instead, the UE receives and processes PEI 220. However, here, PEI 220 indicates paging monitoring for a different subgroup ID used for PEI (e.g., different from the second subgroup ID 222). Therefore, the UE returns to sleep 250. Subsequent PO 230 is not monitored because the UE is in sleep mode.

[0054] Figure 3 An example of sequence diagram 300 for using LP-WUS and PEI according to some implementation schemes is illustrated. Sequence diagram 300 involves base station 308 and UE 104, and they are... Figure 1 Examples of base station 108 and UE 104 are provided. In the first step of sequence diagram 300, base station 308 transmits configuration information (similar to configuration information 150) to UE 304, such that UE 304 is configured for LP-WUS using a first subgroup ID and for PEI using a second subgroup ID. The configuration information can be transmitted via RRC signaling. Example parameters for LP-WUS configuration and PEI configuration are described below. The configuration information may also include information related to configuring PO for the UE.

[0055] In the second step of sequence diagram 300, the UE may determine a first subgroup ID for LP-WUS and a second subgroup ID for PEI based on configuration information. In one example, each of the two subgroup IDs may correspond to a sub-packet assigned by the core network (e.g., one for LP-WUS and one for PEI) or a sub-packet based on the UE ID (e.g., one for LP-WUS and one for PEI). An example procedure for determining the subgroup IDs is further described in the following diagram.

[0056] In the third step of sequence diagram 300, base station 308 may transmit an LP-WUS indicating wake-up for a subgroup ID. The LP-WUS may be carried by DCI. At least a portion of the LP-WUS may indicate that the UE associated with the first subgroup ID will be woken up for paging monitoring. For example, the LP-WUS may explicitly include the first subgroup ID, or include a positive indication for the first subgroup ID. The LP-WUS needs to explicitly indicate the subgroup ID. It can indicate whether a subgroup should wake up by including, for example, a bitmap, where one bit is for each subgroup.

[0057] In the fourth step of sequence diagram 300, base station 308 may transmit a PEI indicating whether paging for a subgroup ID is being monitored. The PEI may be carried by a DCI. At least a portion of the DCI may represent the PEI and may indicate the timing of the next configured paging event for the UE associated with the second subgroup ID. For example, the DCI may explicitly include the second subgroup ID or include a positive indication for the first subgroup ID. The PEI needs to explicitly indicate the subgroup ID. It may use a bitmap, where each bit may correspond to a subgroup.

[0058] In the fifth step of sequence diagram 300, base station 308 can schedule the next PO by transmitting a paging indication in the paging PDCCH and a paging message in the configured paging PDSCH. Here, if the UE determines a positive indication for the first subgroup ID and the second subgroup ID, the UE can monitor the PO (e.g., in...). Figure 2 In the first scenario). Otherwise, no monitoring is performed (as in...). Figure 2 In the second or third scenario, depending on the situation.

[0059] In one example, the subgroup ID for LP-WUS corresponds to a subgroup assigned by the core network for LP-WUS. In this example, a parameter can be introduced as part of the LP-WUS Non-Access Stratum (NAS) signaling for the core network to assign the subgroup ID for LP-WUS to UE 304. Similarly, the subgroup ID for PEI corresponds to a subgroup assigned by the core network for PEI. Here, a parameter can also be introduced as part of the PEI Non-Access Stratum (NAS) signaling for the core network to assign the subgroup ID for PEI to UE 304. The core network has the flexibility to assign the same or different subgroup ID values ​​for PEI and LP-WUS to the UE. If the LP-WUS parameter is not configured for the UE (but the PEI parameter is configured), UE 304 can assume that the same subgroup ID is used for PEI and LP-WUS. Alternatively, the UE can assume that the core network has not assigned a subgroup ID for LP-WUS.

[0060] In another example, the subgroup ID for LP-WUS corresponds to the UE ID-based subgroup for LP-WUS. Here, the subgroup ID for LP-WUS may differ from the subgroup ID for PEI (which may correspond to a core network-assigned subgroup for PEI or a UE ID-based subgroup for PEI). Generally, whether the core network-assigned subgroup or the UE ID-based subgroup is the same for LP-WUS for the UE and for PEI depends on the configuration. In this example, the subgroup ID for LP-WUS can be configured using a set of parameters (referred to herein as LP-WUS parameters). This set may include at least one of the following: the total number of subgroups configured for LP-WUS by paging time (PO) (referred to as "subgroupsNumPerPOLpwus", indicating the total number of subgroups for LP-WUS), or the number of subgroups configured for LP-WUS based on UE ID (referred to as "subgroupsNumForUEIDLpwus", indicating the number of LP-WUS subgroups for UEID-based subgroups). For example, an LP-WUS configuration supporting subgroups can be expressed as:

[0061]

[0062] As explained above, the subgroup ID used for PEI can correspond to a UE ID-based subgroup used for PEI. Here, a set of parameters (referred to herein as PEI parameters) can be used to configure the subgroup ID used for PEI. This set can include at least one of the following: the total number of subgroups per PO for which the UE reads the subgroup indication from physical layer signaling (referred to as “subgroupsNumPerPO”), or the number of subgroups per PO for which the UE reads the subgroup indication from physical layer signaling (referred to as “subgroupsNumForUEID”, which indicates the number of subgroups for UE ID-based subgroups in the PO broadcast in the system information). For example, a PEI configuration supporting subgroups can be expressed as:

[0063]

[0064] In the above example of UE ID-based subgrouping for PEI, the UE can determine the subgroup ID for PEI from the PEI parameters. For example, the UE can use the following formula: subgroupID = (floor(UE ID) ... IDThe formula / (N*Ns))modsubgroupsNumforUEID)+(subgroupsNumPerPO-subgroupsNumforUEID) is available in 3GPP, TS 38.304, V18.1.0 (2024-03), whose entire content is incorporated herein by reference. In this formula, “subgroupsNumPerPO” and “subgroupsNumForUEID” are configured. “N” is the total number of paging frames in T, where T is the discontinuous reception (DRX) period in the RRC_IDLE state. “Ns” is the number of paging opportunities for the PF. “UE_ID” can be 5G-S-TMSImod X, where X is 32768 if eDRX is applied; otherwise, X is 8192.

[0065] By re-referencing UE ID-based subgrouping for LP-WUS, one or more formulas can be used to derive the UE ID-based subgroup ID for LP-WUS. The formulas typically use LP-WUS parameters. The specific formula used reflects a particular design methodology. In a first design methodology, the UE subgroup IDs for LP-WUS and PEI are closely related. Here, a set of formulas is possible. In a second design methodology, the UE subgroup IDs for LP-WUS and PEI are largely independent or unrelated. Here, different sets of formulas are possible. Such formulas are described below.

[0066] The following notation is introduced to explain the options for UE ID-based subgrouping for LP-WUS. "subgroupsNumPerPOLpwus" refers to the total number of subgroups configured for LP-WUS. "subgroupsNumForUEIDLpwus" refers to the number of subgroups configured for UE ID-based subgrouping for LP-WUS. Depending on the LP-WUS and PEI configurations, the value of "subgroupsNumPerPOLpwus" can be equal to the value of "subgroupsNumPerPO". Similarly, the value of "subgroupsNumForUEIDLpwus" can be equal to the value of "subgroupsNumForUEID". "Nmax" refers to the maximum number of subgroups that LP-WUS can support. Let "K = ceil(log2(Nmax))", which represents the number of bits required to represent "Nmax" (e.g., if there are a maximum of eight subgroups for LP-WUS, then "K" equals three). "Lmax" refers to the maximum number of subgroups that PEI can support. Let “M = ceil(log2(Lmax))”, which represents the number of bits required to represent “Lmax” (e.g., “M” equals three if there are at most eight subgroups for PEI).

[0067] In the first example, the subgroup IDs for UEs used in LP-WUS and PEI are closely related. Specifically, the first subgroup ID for LP-WUS is different from, related to, and corresponds to a UE ID-based subgroup. Here, the first subgroup ID can be determined based on a first parameter shared with the determination of the second subgroup ID and a second parameter not used in the determination of the second subgroup ID. The first parameter may include the UE ID used in the determination of the second subgroup ID (e.g., the same as "UE_ID" shown in the above formula). Alternatively, the first parameter may include a first UE ID (shown as "UE_ID" in the following formula) that overlaps (partially or completely) with the second UE ID used in the determination of the second subgroup ID (shown as "UE_ID" in the above formula) (where the two UE_IDs differ from each other by at least one bit). The second parameter may include the number of subgroups configured for UE ID-based subgroups used in LP-WUS (e.g., "subgroupsNumForUEIDLpwus"). In addition, the first subgroup ID can be determined based on the difference between the total number of subgroups configured per PO for LP-WUS and the number of subgroups configured based on UE ID for LP-WUS (e.g., “subgroupsNumPerPoLpwus-subgroupsNumForUEIDLpwus”).

[0068] Therefore, the subgroup ID for LP-WUS can be calculated based on a UE ID that is the same as or overlaps with the UE ID used to calculate the subgroup ID for PEI. A first possible formula is “SubgroupIDLpwus = (floor(UE_ID / (N*Ns)) mod subgroupsNumForUEIDLpwus”. Here, “UE_ID” is the same as the UE_ID used for PEI in the above formula. This method works if LP-WUS has fewer subgroups for UE ID-based subgroupings than PEI. For example, if “subgroupsNumForUEIDLpwus” equals four and “subgroupsNumForUEID” equals eight, then the subgroup ID for LP-WUS is the two least significant bits (LSBs) of the subgroup ID used for PEI. A second possible formula is “SubgroupIDLpwus = floor(UE_ID / (N*Ns)) mod subgroupsNumForUEIDLpwus, where UE_ID = 5G-S-TMSI”. "mod(X*Nmax)". Here, "X" can be different from the X used for PEI in the formula above. For example, if eDRX (extended DRX) is applied, "X" can be equal to 4096, otherwise it is equal to 1024. To illustrate how this formula affects the ID bits, consider the case where "subgroupsNumForUEIDLpwus" equals "Nmax" x six and "subgroupsNumForUEID" equals "Lmax" octet. The UE_ID for LP-WUS and PEI has three overlapping bits, and the subgroup ID for PEI is three LSBs of the subgroup ID for LP-WUS. In both formulas for LP-WUS, an additional offset of "subgroupsNumPerPoLpwus-subgroupsNumForUEIDLpwus" can be added to the calculated subgroup ID to obtain the final subgroup ID for LP-WUS.

[0069] In the example above, the subgroup IDs for LP-WUS and PEI may have overlapping bits. Thus, the first subgroup ID for LP-WUS may be indicated by the first bit, and the second subgroup ID may be indicated by the second bit, and: the first bit includes the second bit and additional bits (as when using the second formula), or the second bit includes the second bit and additional bits (as when using the first formula). In one implementation, the UE derives the subgroup ID for LP-WUS using one of the two formulas for LP-WUS. Alternatively, the UE first determines the second subgroup ID for PEI (e.g., by using a relevant formula) and determines the first subgroup ID for LP-WUS based on the overlapping bits rather than formula calculation (or vice versa).

[0070] In the second example, the subgroup IDs for UEs used in LP-WUS and PEI are largely independent or unrelated. Specifically, the first subgroup ID for LP-WUS is different from, unrelated to, the second subgroup ID for PEI, and corresponds to a subgroup based on the UE ID. Here, the first subgroup ID can be determined based on a first UE ID that is different from the second UE ID used in determining the second subgroup ID and / or based on a first formula that is different from the second formula used in determining the second subgroup ID. For example, the first subgroup ID can be determined based on a first part of the TMSI that is different from the second part used in determining the second subgroup ID. In all these variations, the first subgroup ID for LP-WUS can be further determined based on the difference between the total number of subgroups configured per PO for LP-WUS and the number of subgroups configured for UE ID-based subgroups for LP-WUS (e.g., “subgroupsNumPerPoLpwus-subgroupsNumForUEIDLpwus”).

[0071] The first possible formula in the second example is "SubgroupIDLpwus=floor(UE_ID / (N*Ns*subgroupsNumForUEID))mod subgroupsNumForUEIDLpwus". Here, "UE_ID" can be calculated in different ways, with several examples as follows. "UE_ID" can be equal to "5G-S-TMSI mod X", where "X is 32768*Nmax" if eDRX is applied, otherwise "8192*Nmax". If eDRX is applied, this corresponds to "(15+K)" LSBs of 5G-S-TMSI, otherwise "(13+K)" LSBs. "UE_ID" can be equal to "5G-S-TMSI mod(N*Ns*Lmax*Nmax)". "UE_ID" can be equal to "5G-S-TMSI mod(N*Ns*subgroupsNumForUEID*subgroupsNumForUEIDLpwus)". "UE_ID" can be the full 5G-S-TMSI. Alternatively, "UE_ID" can be thirty-two (or some other number of) LSBs of 5G-S-TMSI (e.g., 32-bit 5G-TMSI).

[0072] The first possible formula in the second example is “SubgroupIDLpwus=UE_ID modsubgroupsNumForUEIDLpwus”. Here, if eDRX is applied, “UE_ID” is the sixteenth LSB to the “(15+K)” LSB of the 5G-S-TMSI, otherwise it is the fourteenth LSB to the “(13+K)” LSB. Alternatively, “UE_ID” can be any “K” digit of the 5G-S-TMSI other than the fifteenth or thirteenth LSB.

[0073] In the two formulas used for LP-WUS, different parts of 5G-S-TMSI are used to calculate the "UE_ID" for LP-WUS and PEI. Therefore, the resulting subgroup IDs are largely irrelevant. For all examples, an additional offset of "subgroupsNumPerPoLpwus-subgroupsNumForUEIDLpwus" can be added to the calculated subgroup ID to obtain the final subgroup ID for LP-WUS.

[0074] Assigning independent or unrelated subgroup IDs for UEs in LP-WUS and PEI can reduce the probability of erroneous paging, which is the probability that a UE wakes up to receive a paging PDSCH but no UE ID match exists in the paging PDSCH. Erroneous paging occurs due to paging of other UEs in the same PO and / or the same subgroup. For illustration, consider the following scenario. Both UE 1 and UE 2 have a “subgroup ID 3” for LP-WUS, but UE 1 has a “subgroup ID 1” for PEI and UE 2 has a “subgroup ID 2” for PEI. When the network needs to page UE 2, it sends a wake-up indication for “subgroup ID 3” in LP-WUS and a PEI for “subgroup ID 2”. LP-WUS wakes up both UE 1 and UE 2. After UE 1 and UE 2 wake up and receive the PEI, UE 2 continues to receive paging PDSCH, but UE 1 does not need to receive paging PDSCH and can immediately return to sleep. This means that when the first UE monitors both LP-WUS and PEI, the probability of false paging for the first UE is reduced compared to when the first UE only monitors LP-WUS.

[0075] If the subgroup ID used for LP-WUS is decoupled as much as possible from the subgroup ID used for PEI, then UEs sharing the same subgroup ID used for LP-WUS can be mapped to different subgroup IDs used for PEI. In this case, UEs can be mapped to different subgroup IDs used for PEI as evenly as possible.

[0076] The following section provides illustrative use cases based on the methods described above, where the subgroup IDs used for LP-WUS and PEI can be largely independent. These methods are beneficial for reducing the probability of false paging if the UE monitors both LP-WUS and PEI. In the first use case, the UE can use the subgroup ID assigned by the core network for PEI, and the subgroup ID based on the UE ID for LP-WUS (or vice versa). In this case, “subgroupsNumPerPOLpwus” and “subgroupsNumForUEIDLpwus” are configured separately for LP-WUS. The subgroup ID used for PEI is the subgroup ID assigned by the core network. The subgroup ID used for LP-WUS is a subgroup ID calculated using any of the formulas above based on "subgroupsNumPerPOLpwus", "subgroupsNumForUEIDLpwus", and the UE's own 5G-S-TMSI.

[0077] In the second use case, the UE can use the subgroup ID assigned by the core network for both LP-WUS and PEI, with separate parameters configured. Specific LP-WUS parameters are used for the core network-assigned subgroup ID for LP-WUS. Different parameters are used for the core network-assigned subgroup ID used for PEI.

[0078] In the third use case, the UE can use a subgroup ID based on the UE ID for both LP-WUS and PEI. Here, the subgroup ID for LP-WUS is calculated according to one of the formulas in the second example above, such that it is different from and unrelated to the subgroup ID for PEI.

[0079] Figure 4 Examples of operational flow / algorithm structures 400 for determining subgroup IDs according to some embodiments are illustrated. Operational flow / algorithm structures 400 may be implemented by a UE (e.g., executed by its components, including, for example, a processor of the UE). The UE can be any UE described herein. In some embodiments, operational flow / algorithm structures 400 may be implemented by executing instructions stored in a tangible, non-transitory computer-readable medium such as the memory of the UE. Although operational flow / algorithm structures 400 are described using steps in a specific order, it should be understood that the steps described herein contemplate being performed in a different order than illustrated, and that some described steps may be skipped or not performed at all.

[0080] In one example, the operation flow / algorithm structure 400 includes determining at 402 whether a first parameter is configured. When using the operation flow / algorithm structure 400 to determine the subgroup ID for LP-WUS, the first parameter can be a first LP-WUS parameter, such as "subgroupsNumForUEIDLpwus". When using the operation flow / algorithm structure 400 to determine the subgroup ID for PEI, the first parameter can be a first PEI parameter, such as "subgroupsNumForUEID". If the first parameter is not configured, the operation flow / algorithm structure 400 may proceed to 404. Otherwise, the operation flow / algorithm structure 400 proceeds to 408.

[0081] In one example, the operation flow / algorithm structure 400 includes determining at 404 whether a subgroup ID has been assigned by the core network. When the operation flow / algorithm structure 400 is used to determine a subgroup ID for LP-WUS, this core network assignment is available for LP-WUS. When the operation flow / algorithm structure 400 is used to determine a subgroup ID for PEI, this core network assignment is available for PEI. In both cases, the RRC configuration for LP-WUS (in the first case) and / or PEI (in the second case) is checked. If the subgroup ID was not assigned by the core network, the operation flow / algorithm structure 400 may result in determining that the UE is not part of a UE subgroup (e.g., for LP-WUS in the first case and / or PEI in the second case). Otherwise, the operation flow / algorithm structure 400 proceeds to 406.

[0082] In one example, the operational procedure / algorithm structure 400 includes using a sub-packet assigned by the core network at 406. When the operational procedure / algorithm structure 400 is used to determine the sub-packet ID for LP-WUS, the configured LP-WUS parameters indicate the value of the sub-packet ID for LP-WUS. When the operational procedure / algorithm structure 400 is used to determine the sub-packet ID for PEI, the configured PEI parameters indicate the value of the sub-packet ID for PEI.

[0083] In one example, the operation flow / algorithm structure 400 includes determining at 408 whether a first parameter and a second parameter are configured. When using the operation flow / algorithm structure 400 to determine the subgroup ID for LP-WUS, the second parameter can be a second LP-WUS parameter, such as “subgroupsNumPerPOLpwus”. When using the operation flow / algorithm structure 400 to determine the subgroup ID for PEI, the first parameter can be a first PEI parameter, such as “subgroupsNumPerPO”. If both parameters (or at least the second parameter) are not configured, the operation flow / algorithm structure 400 may result in determining that the UE is not part of a UE subgroup (e.g., for LP-WUS in the first case and / or for PEI in the second case). Otherwise, the operation flow / algorithm structure 400 proceeds to 410.

[0084] In one example, the operation flow / algorithm structure 400 includes determining at 410 whether the parameters are equal to each other. For example, the values ​​of the two parameters can be compared. If they are not equal, the operation flow / algorithm structure 400 can proceed to 414. Otherwise, the operation flow / algorithm structure 400 proceeds to 412.

[0085] In one example, the operation flow / algorithm structure 400 includes using UE ID-based subgroups at 412. When using the operation flow / algorithm structure 400 to determine the subgroup ID for LP-WUS, one or more of the formulas above for LP-WUS can be used to derive the subgroup ID. When using the operation flow / algorithm structure 400 to determine the subgroup ID for PEI, the formulas above for PEI can be used to derive the subgroup ID.

[0086] In one example, the operation flow / algorithm structure 400 includes determining at 414 whether a subgroup ID has been assigned by the core network. When the operation flow / algorithm structure 400 is used to determine a subgroup ID for LP-WUS, this core network assignment is available for LP-WUS. When the operation flow / algorithm structure 400 is used to determine a subgroup ID for PEI, this core network assignment is available for PEI. In both cases, the RRC configuration for LP-WUS (in the first case) and / or PEI (in the second case) is checked. If the subgroup ID was not assigned by the core network, the operation flow / algorithm structure 400 may proceed to 418. Otherwise, the operation flow / algorithm structure 400 proceeds to 416.

[0087] In one example, the operational procedure / algorithm structure 400 includes using a sub-packet assigned by the core network at 416. When the operational procedure / algorithm structure 400 is used to determine the sub-packet ID for LP-WUS, the configured LP-WUS parameter indicates the value of the sub-packet ID for LP-WUS. When the operational procedure / algorithm structure 400 is used to determine the sub-packet ID for PEI, the configured PEI parameter indicates the value of the sub-packet ID for PEI.

[0088] In one example, the operation flow / algorithm structure 400 includes using UE ID-based subgroups at 418. When using the operation flow / algorithm structure 400 to determine the subgroup ID for LP-WUS, one or more of the formulas above for LP-WUS can be used to derive the subgroup ID. When using the operation flow / algorithm structure 400 to determine the subgroup ID for PEI, the formulas above for PEI can be used to derive the subgroup ID.

[0089] Figure 5Examples of a process / algorithm structure 500 for using subgroup IDs of LP-WUS and PEI according to some embodiments are illustrated. The operation process / algorithm structure 500 may be implemented by a UE (e.g., executed by its components, including, for example, the UE's processor). The UE can be any UE described herein. In some embodiments, the operation process / algorithm structure 500 may be implemented by executing instructions stored in a tangible, non-transitory computer-readable medium such as the memory of the UE. Although the operation process / algorithm structure 500 is described using steps in a specific order, it should be understood that the steps described herein contemplate being performed in a different order than illustrated, and that some described steps may be skipped or not performed at all.

[0090] In one example, the operation flow / algorithm structure 500 includes processing configuration information at 502 indicating LP-WUS configuration and PEI configuration. The configuration information can be received based on RRC signaling. The LP-WUS configuration is separate from the PEI configuration and indicates the first subgroup ID for LP-WUS. The first subgroup ID corresponds to a sub-packet assigned by the core network for LP-WUS or a UE ID-based sub-packet for LP-WUS. The PEI configuration indicates the second subgroup ID for PEI.

[0091] In one example, the operation flow / algorithm structure 500 includes determining at 504 that the received LP-WUS indication is a wake-up for a first subgroup ID. For example, the LP-WUS is received and processed to determine that it includes a wake-up indication and a first subgroup ID. Here, the UE may determine that the indicated first subgroup ID applies to it (matches the subgroup ID configured for the LP-WUS) and wake up the main radio to monitor the PEI and / or paging timing.

[0092] In one example, the operation flow / algorithm structure 500 includes determining at 506 that the PEI indicates paging monitoring for a second subgroup ID. The PEI is received based on the received LP-WUS indication of a first subgroup ID. Specifically, because the UE wakes up the primary radio, the UE is able to receive and process the PEI. This processing can result in the UE determining that the PEI indicates the second subgroup ID associated with it should perform paging monitoring. Here, the UE can determine that the indicated second subgroup ID applies to it (matches the subgroup ID configured for the PEI) and does not transition back to a sleep state.

[0093] In one example, the operation flow / algorithm structure 500 includes processing the paging timing at 508 based on the PEI indicating the second subgroup ID, for example, processing the PDDCH paging to indicate that paging PDSCH should be monitored. Afterwards, processing of the paging PDSCH is performed.

[0094] Figure 6Another example of a flow / algorithm structure 600 for using subgroup IDs of LP-WUS and PEI, according to some embodiments, is illustrated. The operation flow / algorithm structure 600 may be implemented by a network (e.g., by its base station, its core network, the processor of the base station, and / or the processor of the core network). The network can be any network described herein. In some embodiments, the operation flow / algorithm structure 600 may be implemented by executing instructions stored in a tangible, non-transitory computer-readable medium such as the memory of a base station. Although the operation flow / algorithm structure 600 is described using steps in a specific order, it should be understood that the steps described herein are contemplated to be performed in a different order than illustrated, and that some described steps may be skipped or not performed at all.

[0095] In one example, the operation flow / algorithm structure 600 includes transmitting RRC signaling at 602 to the UE indicating configuration information for LP-WUS configuration and PEI configuration. The LP-WUS configuration is separate from the PEI configuration and indicates a first subgroup identifier ID for LP-WUS. The first subgroup ID corresponds to a sub-packet assigned by the core network for LP-WUS or a UE ID-based sub-packet for LP-WUS. The PEI configuration indicates a second subgroup ID for PEI.

[0096] In one example, the operation flow / algorithm structure 600 includes transmitting at 604 an LP-WUS indicating wake-up for a first subgroup ID to the UE. For example, a DCI may be transmitted, and at least a portion of it may represent the LP-WUS.

[0097] In one example, the operation flow / algorithm structure 600 may include transmitting a PEI indicating paging monitoring for a second subgroup ID to the UE at 606. The PEI is transmitted based on the LP-WUS indicating the first subgroup ID. For example, a DCI is transmitted, and at least a portion of it may represent the PEI. The DCI is transmitted given that a DCI for the LP-WUS is transmitted to wake up the UE associated with the first subgroup ID.

[0098] In one example, the operation flow / algorithm structure 600 includes scheduling paging timing for the UE at 608 based on the PEI indicating the second subgroup ID. For example, a configured PO may be used and may include a paging PDCCH and a paging PDSCH. Given that a PEI is transmitted to indicate paging applicable to a UE subgroup, the paging PDCCH may include an indication of monitoring the paging PDSCH, and the paging PDSCH may include a paging message applicable to one or more such UEs.

[0099] Figure 7 Examples of UEs according to some implementation schemes (e.g., Figure 1The receiving component 700 (UE 104 and any other UE described herein capable of receiving and processing LP-WUS and PEI) may include an antenna panel 704 comprising a plurality of antenna elements. Panel 704 is shown as having four antenna elements, but other embodiments may include other numbers. Multiple antenna panels may also be included.

[0100] Antenna panel 704 may be coupled to an analog beamforming (BF) assembly including a plurality of phase shifters 708(1) to 708(4). Phase shifters 708(1) to 708(4) may be coupled to a radio frequency (RF) chain 709. RF chain 709 may amplify received analog RF signals, down-convert RF signals to baseband, and convert analog baseband signals into digital baseband signals that can be provided to a baseband processor for further processing.

[0101] In various implementations, control circuitry residing in the baseband processor may provide BF weights (e.g., W1 to W4) to phase shifters 708(1) to 708(4) to provide a receive beam at antenna panel 704; these BF weights may represent phase shift values. These BF weights may be determined based on channel-based beamforming. As further described below, the baseband processor may detect the LP-WUS payload and control the operating mode of the UE.

[0102] Figure 8 UE 800 is illustrated according to some implementation schemes. UE 800 may be similar to and substantially interchangeable with UE 104 or 106 or any UE described herein capable of receiving and processing LP-WUS and PEI. For example, UE 800 may receive configuration information indicating an LP-WUS configuration separate from the PEI configuration, wherein each configuration indication can be used to wake up and perform paging monitoring if UE 800 belongs to a UE subgroup indicated by a subgroup ID.

[0103] UE 800 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, stock sensor, voltmeter / ammeter, or actuator), video surveillance / monitoring device (e.g., camera or camcorder), wearable device (e.g., smartwatch), or Internet of Things device.

[0104] UE 800 may include a processor 804, RF interface circuitry 808, memory / storage device 812, user interface 816, sensor 820, drive circuitry 822, power management integrated circuit (PMIC) 824, antenna 826, and battery 828. The components of UE 800 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 8 The block diagram is intended to show a high-level view of some of the components of the UE 800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0105] The components of UE 800 can be coupled to a variety of other components via one or more interconnects 832, which can represent any type of interface, input / output, bus (local, system, or extension), transmit line, trace, or optical connector, allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0106] Processor 804 may include processor circuitry, such as baseband processor circuitry (BB) 804A, central processing unit circuitry (CPU) 804B, and graphics processing unit circuitry (GPU) 804C. Processor 804 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 812) to cause UE 800 to perform the operations described herein. Processor 804 may also include interface circuitry 804D for communicatively coupling the processor circuitry to one or more other components of UE 800. Any or a combination of processors 804 may be configured to detect the payload of LP-WUS. Specifically, when UE 800 is in RRC_IDLE or RRC_INACTIVE mode, the LP-WUS signal may be received and processed by the receive path of UE 800 to generate a bit. This bit is passed to a processor capable of performing the operations previously described (including those described in FIG. 14) to process the bit and determine the payload. Based on this payload, the processor can trigger UE 800 to switch to RRC_CONNECTED mode.

[0107] In some implementations, the baseband processor circuit 804A can access the communication protocol stack 836 in the memory / storage device 812 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 804A can access the communication protocol stack 836 to: perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and perform control plane functions at the PHY, MAC, RLC, PDCP, RRC, and NAS layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 808.

[0108] The baseband processor circuit 804A can generate or process baseband signals or waveforms carrying information in 3GPP-compliant networks. In some implementations, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0109] The memory / storage device 812 may include one or more non-transitory computer-readable media, which include instructions (e.g., a communication protocol stack 836) that can be executed by one or more processors in processor 804 to cause UE 800 to perform the various operations described herein.

[0110] The memory / storage device 812 includes any type of volatile or non-volatile memory that can be distributed throughout the UE 800. In some embodiments, some of the memory / storage devices 812 may be located on the processor 804 itself (e.g., the memory / storage device 812 may be part of a chipset corresponding to the baseband processor circuitry 804A), while other memory / storage devices 812 are located external to the processor 804 but are accessible via a memory interface. The memory / storage device 812 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0111] RF interface circuitry 808 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows UE 800 to communicate with other devices via a radio access network. RF interface circuitry 808 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0112] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 826 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the transceiver's receiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 804.

[0113] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 826.

[0114] In various implementations, the RF interface circuit 808 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0115] Antenna 826 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 826 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 826 may include a microstrip antenna, a printed antenna fabricated on the surface of one or more printed circuit boards, a patch antenna, or a phased array antenna. Antenna 826 may have one or more panels designed for a specific frequency band (including bands in FR1 or FR2).

[0116] User interface 816 includes various input / output (I / O) devices designed to enable user interaction with UE 800. User interface 816 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, or a headset. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), where the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 800.

[0117] Sensor 820 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other similar audio capture devices.

[0118] The driving circuit 822 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 800. The driving circuit 822 may include a single driver that allows other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 800. For example, the driving circuit 822 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings of a sensor 820 and controlling and allowing access to the sensor 820; a driver for obtaining actuator positioning of an electromechanical component or controlling and allowing access to an electromechanical component; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0119] The PMIC 824 manages the power supplied to various components of the UE 800. Specifically, relative to the processor 804, the PMIC 824 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0120] Battery 828 can power UE 800, but in some examples, UE 800 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 828 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 828 may be a typical lead-acid automotive battery.

[0121] Figure 9Network device 900 is illustrated according to some implementation schemes. Network device 900 may be similar to and substantially interchangeable with devices capable of generating and / or transmitting LP-WUS and PEI, such as base station 108, core network 112, or external data network 120. For example, network device 9100 may transmit configuration information indicating LP-WUS configuration separate from PEI configuration, wherein each configuration indication can be used to wake up and page a UE subgroup ID indicated by a subgroup ID.

[0122] Network device 900 may include processor 904, RF interface circuitry 908 (if implemented as a base station), core network (CN) interface circuitry 914, memory / storage device circuitry 912, and antenna structure 926.

[0123] The components of network device 900 can be coupled to various other components via one or more interconnectors 928.

[0124] The processor 904, RF interface circuit 908, memory / storage device circuit 912 (including communication protocol stack 910), antenna structure 926, and interconnect 928 are similar to those in the reference. Figure 8 Similar named elements are shown and described.

[0125] Processor 904 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 904A, central processing unit circuitry (CPU) 904B, and graphics processing unit circuitry (GPU) 904C. Processor 904 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device circuitry 912) to cause network device 900 to perform the operations described herein. Processor 904 may also include interface circuitry 904D for communicatively coupling processor circuitry to one or more other components of network device 900. Any or a combination of processors 904 may be configured to generate an LP-WUS payload. Specifically, the processor may generate information bits, encode them using a specific encoding scheme, extend the encoded bits, modulate the encoded bits using OOK modulation, map the encoded bits to a sequence, and carry the sequence in OFDM symbols or portions thereof corresponding to OOK bits “1”.

[0126] The CN interface circuit 914 can provide connectivity to a core network (e.g., a 5GC using a fifth-generation core network (5GC) compatible network interface protocol, such as Carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from network device 900 via fiber optic or wireless backhaul. The CN interface circuit 914 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 914 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0127] 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 authorized use should be clearly explained to users.

[0128] For one or more embodiments, at least one component of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more examples described below. Similarly, circuitry 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 examples described in the Examples section below.

[0129] Example

[0130] Further exemplary implementations are provided in the following sections.

[0131] Example 1 includes a method comprising: processing configuration information indicating a Low Power Wake-up Signal (LP-WUS) configuration and a Paging Early Indication (PEI) configuration, the configuration information being received based on Radio Resource Control (RRC) signaling, the LP-WUS configuration being separate from the PEI configuration and indicating a first subgroup identifier (ID), the first subgroup ID corresponding to a subgroup assigned by the core network for LP-WUS or a subgroup based on a User Equipment (UE) ID for LP-WUS, the PEI configuration indicating a second subgroup ID; determining a received LP-WUS indication for wake-up for the first subgroup ID; determining a PEI indication for paging monitoring for the second subgroup ID, the PEI being received based on the received LP-WUS indication for the first subgroup ID; and processing paging timing based on the PEI indication for the second subgroup ID.

[0132] Example 2 includes a method comprising: transmitting to a UE radio resource control (RRC) signaling configuration information indicating a low-power wake-up signal (LP-WUS) configuration and a paging early indication (PEI) configuration, the LP-WUS configuration being separate from the PEI configuration and indicating a first subgroup identifier (ID), the first subgroup ID corresponding to a sub-packet assigned by the core network for LP-WUS or a sub-packet based on a user equipment (UE) ID for LP-WUS, the PEI configuration indicating a second subgroup ID; transmitting to the UE an LP-WUS indicating wake-up for the first subgroup ID; transmitting to the UE a PEI indicating paging monitoring for the second subgroup ID, the PEI being transmitted based on the LP-WUS indicating the first subgroup ID; and scheduling paging timing for the UE based on the PEI indicating the second subgroup ID.

[0133] Example 3 includes the method according to any one of Examples 1 to 2 above, wherein the first subgroup ID is the same as the second subgroup ID, and both the first subgroup ID and the second subgroup ID are assigned by the core network.

[0134] Example 4 includes the method according to any one of Examples 1 to 3 above, wherein the RRC signaling indicates the second subgroup ID but not the first subgroup ID, and the method further includes: setting or causing the first subgroup ID configured by the LP-WUS to have the same value as the second subgroup ID based on the RRC signaling.

[0135] Example 5 includes the method according to any one of Examples 1 to 2 above, wherein the first subgroup ID is different from the second subgroup ID, and both the first subgroup ID and the second subgroup ID are assigned by the core network.

[0136] Example 6 includes the method according to any one of Examples 1 to 2 above, wherein the first subgroup ID is different from the second subgroup ID, corresponds to the UE ID-based subgroup, and is determined based on a set of parameters indicated by the RRC signaling and specific to the LP-WUS configuration.

[0137] Example 7 includes the method according to Example 6, wherein the parameter set includes at least one of the total number of subgroups configured for LP-WUS per paging timing (PO) or the number of subgroups configured for LP-WUS based on UE ID.

[0138] Example 8 includes the method according to any one of Examples 1 to 2 or 7 above, wherein the first subgroup ID is different from the second subgroup ID, is related to the second subgroup ID, and corresponds to the subgroup based on the UE ID.

[0139] Example 9 includes the method according to Example 8, the method further comprising: determining the first subgroup ID based on a first parameter shared with the determination of the second subgroup ID and a second parameter not used in the determination of the second subgroup ID.

[0140] Example 10 includes the method according to Example 9, wherein the first parameter includes the UE ID used in the determination of the second subgroup ID, and the second parameter includes the number of subgroups for the UE ID-based subgroup configuration for LP-WUS.

[0141] Example 11 includes the method according to Example 9, wherein the first parameter includes a first UE ID that overlaps with the second UE ID used in the determination of the second subgroup ID, and the second parameter includes the number of subgroups for the UE ID-based subgroup configuration for LP-WUS.

[0142] Example 12 includes the method according to any one of Examples 8 to 11 above, wherein the first subgroup ID is indicated by a first bit, wherein the second subgroup ID is indicated by a second bit, and wherein: the first bit includes the second bit and an additional bit, or the second bit includes the second bit and the additional bit.

[0143] Example 13 includes the method according to any one of Examples 8 to 12 above, the method further comprising: determining the first subgroup ID based on the difference between the total number of subgroups configured per paging time (PO) for LP-WUS and the number of subgroups configured for LP-WUS based on the UE ID, or causing the first subgroup ID to be determined based on the difference.

[0144] Example 14 includes the method according to any one of Examples 1 to 2 or 7 above, wherein the first subgroup ID is different from the second subgroup ID, is unrelated to the second subgroup ID, and corresponds to the subgroup based on the UE ID.

[0145] Example 15 includes the method according to Example 14, wherein the first subgroup ID is associated with a first UE and a second UE, and wherein the second subgroup ID is associated with the first UE and not with the second UE.

[0146] Example 16 includes the method according to any one of Examples 14 to 15 above, the method further comprising: determining the first subgroup ID based on a first parameter common to the determination of the second subgroup ID and a second parameter not used in the determination of the second subgroup ID, or causing the first subgroup ID to be determined based on the first parameter and the second parameter.

[0147] Example 17 includes the method according to any one of Examples 14 to 16 above, the method further comprising: determining the first subgroup ID based on a first formula different from the second formula used in determining the second subgroup ID, or causing the first subgroup ID to be determined based on the first formula.

[0148] Example 18 includes the method according to any one of Examples 14 to 17 above, wherein the first subgroup ID is different from the second subgroup ID, is unrelated to the second subgroup ID, corresponds to the UE ID-based subgroup, and is determined based on a first portion of the TMSI that is different from a second portion of the Temporary Mobile Subscriber Identity (TMSI), wherein the second portion is used in the determination of the second subgroup ID.

[0149] Example 19 includes the method according to any one of Examples 14 to 18 above, wherein the first subgroup ID is different from the second subgroup ID, is unrelated to the second subgroup ID, corresponds to the UE ID-based subgroup, and is determined based on the difference between the total number of subgroups configured for LP-WUS per paging timing (PO) and the number of subgroups configured for LP-WUS based on the UE ID.

[0150] Example 20 includes a user equipment (UE) or device, the UE or device comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, configure the UE or device to perform the methods described in or related to any of the foregoing embodiments.

[0151] Example 21 includes one or more computer-readable media storing instructions that, when executed on a user equipment (UE) or device, cause the UE or device to perform operations including those operations described in or related to any of the preceding examples.

[0152] Example 22 includes an apparatus comprising one or more elements for performing the methods described or associated with any of the foregoing embodiments.

[0153] Example 23 includes one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of the device, cause the device to perform one or more elements of the methods described in or related to any of the foregoing embodiments.

[0154] Example 24 includes an apparatus comprising logic, modules, or processing circuitry comprising one or more elements for performing the methods described or associated with any of the foregoing embodiments.

[0155] Example 25 includes an apparatus, network, base station, or system comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the methods described in or related to any of the foregoing embodiments.

[0156] 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 illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0157] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method, the method comprising: The system processes configuration information indicating Low Power Wake-up Signal (LP-WUS) configuration and Early Paging Indication (PEI) configuration, the configuration information being received based on Radio Resource Control (RRC) signaling, the LP-WUS configuration being separate from the PEI configuration and indicating a first subgroup identifier (ID), the first subgroup ID corresponding to a subgroup assigned by the core network for LP-WUS or a subgroup based on the User Equipment (UE) ID for LP-WUS, the PEI configuration indicating a second subgroup ID; Determine the received LP-WUS indication for wake-up of the first subgroup ID; Determine the PEI indication for paging monitoring for the second subgroup ID, wherein the PEI is received based on the received LP-WUS indication for the first subgroup ID; as well as The paging timing is processed based on the PEI indicating the second subgroup ID.

2. The method of claim 1, wherein the first subgroup ID is the same as the second subgroup ID, and both the first subgroup ID and the second subgroup ID are assigned by the core network.

3. The method of claim 1, wherein the RRC signaling indicates the second subgroup ID but not the first subgroup ID, and the method further comprises: Based on the RRC signaling, the first subgroup ID of the LP-WUS configuration is set to have the same value as the second subgroup ID.

4. The method of claim 1, wherein the first subgroup ID is different from the second subgroup ID, and both the first subgroup ID and the second subgroup ID are assigned by the core network.

5. The method of claim 1, wherein the first subgroup ID is different from the second subgroup ID, corresponds to the UE ID-based subgroup, and is determined based on a set of parameters indicated by the RRC signaling and specific to the LP-WUS configuration.

6. The method of claim 5, wherein the parameter set includes at least one of the total number of subgroups configured for LP-WUS per paging timing (PO) or the number of subgroups configured for LP-WUS based on UE ID.

7. The method of claim 1, wherein the first subgroup ID is different from the second subgroup ID, is related to the second subgroup ID, and corresponds to the subgroup based on the UE ID.

8. The method according to claim 7, further comprising: The first subgroup ID is determined based on a first parameter shared with the determination of the second subgroup ID and a second parameter not used in the determination of the second subgroup ID.

9. The method of claim 8, wherein the first parameter includes the UEID used in the determination of the second subgroup ID, and the second parameter includes the number of subgroups for the UE ID-based subgroup configuration for LP-WUS.

10. The method of claim 8, wherein the first parameter includes a first UE ID that overlaps with the second UE ID used in the determination of the second subgroup ID, and the second parameter includes the number of subgroups for the UE ID-based subgroup configuration for LP-WUS.

11. The method of claim 7, wherein the first subgroup ID is indicated by a first bit, wherein the second subgroup ID is indicated by a second bit, and wherein: The first bit includes the second bit and the additional bit, or the second bit includes the second bit and the additional bit.

12. The method of claim 7, further comprising: The first subgroup ID is determined based on the difference between the total number of subgroups configured for LP-WUS per paging time (PO) and the number of subgroups configured for LP-WUS based on the UE ID.

13. An apparatus comprising: Receiver; Transmitter; and A processing circuit, communicatively coupled to the receiver and the transmitter, and configured to: The system processes configuration information indicating Low Power Wake-up Signal (LP-WUS) configuration and Early Paging Indication (PEI) configuration, the configuration information being received based on Radio Resource Control (RRC) signaling, the LP-WUS configuration being separate from the PEI configuration and indicating a first subgroup identifier (ID), the first subgroup ID corresponding to a subgroup assigned by the core network for LP-WUS or a subgroup based on the User Equipment (UE) ID for LP-WUS, the PEI configuration indicating a second subgroup ID; Determine the received LP-WUS indication for wake-up of the first subgroup ID; Determine the PEI indication for paging monitoring for the second subgroup ID, wherein the PEI is received based on the received LP-WUS indication for the first subgroup ID; as well as The paging timing is processed based on the PEI indicating the second subgroup ID.

14. The apparatus of claim 13, wherein the first subgroup ID is different from the second subgroup ID, is unrelated to the second subgroup ID, and corresponds to the UE ID-based subgroup.

15. The apparatus of claim 14, wherein the first subgroup ID is associated with the first UE and the second UE, and wherein the second subgroup ID is associated with the first UE and not with the second UE.

16. The apparatus of claim 14, wherein the processing circuit is further configured to: The first subgroup ID is determined based on a first UE ID that is different from the second UE ID used in determining the second subgroup ID.

17. The apparatus of claim 14, wherein the processing circuit is further configured to: The first subgroup ID is determined based on a first formula that is different from the second formula used in determining the second subgroup ID.

18. A method, the method comprising: Radio resource control (RRC) signaling is transmitted to the UE to indicate configuration information for Low Power Wake-up Signal (LP-WUS) configuration and Early Paging Indication (PEI) configuration, wherein the LP-WUS configuration is separate from the PEI configuration and indicates a first subgroup identifier (ID), the first subgroup ID corresponding to a subgroup assigned by the core network for LP-WUS or a subgroup based on the user equipment (UE) ID for LP-WUS, and the PEI configuration indicating a second subgroup ID; Transmit an LP-WUS indicating wake-up for the first subgroup ID to the UE; Transmit to the UE a PEI indicating paging monitoring for the second subgroup ID, the PEI being transmitted based on the LP-WUS indicating the first subgroup ID; as well as The paging timing for the UE is scheduled based on the PEI indicating the second subgroup ID.

19. The method of claim 18, wherein the first subgroup ID is different from the second subgroup ID, is unrelated to the second subgroup ID, corresponds to the UEID-based subgroup, and is determined based on a first portion of the TMSI that is different from a second portion of the Temporary Mobile Subscriber Identity (TMSI), wherein the second portion is used in determining the second subgroup ID.

20. The method of claim 18, wherein the first subgroup ID is different from the second subgroup ID, is unrelated to the second subgroup ID, corresponds to the UEID-based subgroup, and is determined based on the difference between the total number of subgroups configured for LP-WUS per paging timing (PO) and the number of subgroups configured for the UEID-based subgroup for LP-WUS.

Images