EP4652777A1

EP4652777A1 - Subgroup identifier for a low-power wake-up signal

Info

Publication number: EP4652777A1
Application number: EP24869431.7A
Authority: EP
Inventors: Sigen Ye; Dawei Zhang; Wei Zeng; Fangli Xu; Seyed Ali Akbar Fakoorian; Dan Wu; Weidong Yang; Oghenekome Oteri
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2024-04-05
Filing date: 2024-04-05
Publication date: 2025-11-26
Also published as: EP4652777A4; WO2025212098A1

Abstract

The present application relates to devices and components including apparatus, systems, and methods to use a subgroup identifier (ID) for a low-power wake-up signal (LP-WUS). In an example, a user equipment (UE) can be configured with an LP-WUS configuration separately from a paging early indication (PEI) configuration. The LP-WUS configuration can indicate a first subgroup ID for LP-WUS, whereas the PEI configuration can indicate a second subgroup ID for PEI. A network can wake up a subgroup of UEs associated with the first subgroup ID by using an LP-WUS and can indicate to these UEs that a paging occasion is to be monitored, where this indication can via a PEI that indicates the second subgroup ID.

Description

SUBGROUP IDENTIFIER FOR A LOW-POWER WAKE-UP SIGNAL

BACKGROUND

[0001] Fifth generation mobile network (5G) is a wireless standard that aims to improve upon data transmission speed, reliability, availability, and more. This standard, while still developing, includes numerous details related to, for instance, a user equipment (UE) communicating with a network to send and receive data. In an example, the UE can operate in different modes to reduce its power consumption and switch between the modes based on signaling from the network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] FIG. 1 illustrates an example of a network environment in accordance with some embodiments.

[0003] FIG. 2 illustrates an example of using a low-power wake-up signal (LP-WUS) and a paging early indication (PEI) in accordance with some embodiments.

[0004] FIG. 3 illustrates an example of a sequence diagram for using an LP-WUS and a PEI in accordance with some embodiments.

[0005] FIG. 4 illustrates an example of an operational flow/algorithmic structure for determining a subgroup identifier (ID) in accordance with some embodiments.

[0006] FIG. 5 illustrates an example of flow/algorithmic structure for using subgroup IDs for LP-WUS and PEI in accordance with some embodiments.

[0007] FIG. 6 illustrates another example of flow/algorithmic structure for using subgroup IDs for LP-WUS and PEI in accordance with some embodiments.

[0008] FIG. 7 illustrates an example of receive components in accordance with some embodiments.

[0009] FIG. 8 illustrates an example of a user equipment (UE) in accordance with some embodiments.

[0010] FIG. 9 illustrates an example of a base station in accordance with some embodiments. DETAILED DESCRIPTION

[0011] Embodiments of the present disclosure relate to, among other things, using a subgroup identifier (ID) for a low-power wake-up signal (LP-WUS). In an example, a user equipment (UE) can be configured with an LP-WUS configuration separately from a paging early indication (PEI) configuration. The LP-WUS configuration can indicate a first subgroup ID for LP-WUS, whereas the PEI configuration can indicate a second subgroup ID for PEI. The two subgroup IDs can be used in conjunction to improve the power consumption of the UE (e.g., increase its power saving). For example, when a network needs to page a subgroup of UEs, the network transmits a LP-WUS indicating a 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 foregoes going back to sleep and receives the PEI. Upon determining the second subgroup ID, the UE continues to receive paging physical downlink control channel (PDCCH). Conversely, assume that the PEI indicated paging monitoring for a different subgroup ID. In this case, the UE would have gone back to sleep and would have foregone receiving the paging PDCCH. Similarly, assume that the LP-WUS indicated wake-up for a different subgroup ID. In this case, the UE would have gone back to sleep after receiving the LP-WUS. In both situations, the network can control the paging of UEs at a granular level of two subgroups, while enabling power savings.

[0012] In an example, a subgroup ID for LP-WUS can correspond to a core network assigned subgrouping. In another example, the subgroup ID for LP-WUS can correspond to a UE ID based subgrouping. In the latter case, the subgroup ID for LP-WUS can be different from, and yet correlated or uncorrelated with, a subgroup ID for PEI. These and other features are further described herein below.

[0013] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present 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] The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group), an application specific integrated circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable system-on-a-chip (SoC)), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0016] The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data. The term “processor circuitry” may refer an application processor, baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triplecore processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes. The term “processor circuitry” may be used synonymously with the term “processing circuitry.”

[0017] The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, or the like.

[0018] The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, 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. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

[0019] The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.

[0020] The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, or the like. A “hardware resource” may refer to compute, storage, or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/sy stems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0021] The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio-frequency carrier,” or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices for the purpose of transmitting and receiving information.

[0022] The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

[0023] The term “connected” may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.

[0024] The term “network element” as used herein 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 to or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, or the like.

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

[0026] The term “based at least in part on” as used herein may indicate that an item is based solely on another item and/or an item is based on another item and one or more additional items. For example, item 1 being determined based at least in part on item 2 may indicate that item 1 is determined based solely on item 2 and/or is determined based on item 2 and one or more other items in embodiments.

[0027] FIG. 1 illustrates a network environment 100 in accordance with some embodiments. The network environment 100 may include a UE 104 communicatively coupled with a base station 108 of a radio access network (RAN) 110. The UE 104 and the base station 108 may communicate over air interfaces compatible with 3GPP TSs such as those that define a Fifth Generation (5G) new radio (NR) system or a later system. The base station 108 may provide user plane and control plane protocol terminations toward the UE 104. The base station 108 can generate and transmit an LP-WUS to the UE 104. In turn, the UE 104 can receive the LP-WUS, detect its payload and, depending on the payload, switch an operational mode (e.g., to wake up the main radio to monitor paging).

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

[0029] The network environment 100 may further include a core network 112. For example, the core network 112 may comprise a 5^th Generation Core network (5GC) or later generation core network. The core network 112 may be coupled to the base station 108 via a fiber optic or wireless backhaul. The core network 112 may provide functions for the UE 104 via the base station 108. These functions may include managing subscriber profile information, subscriber location, authentication of services, or switching functions for voice and data sessions.

[0030] In some embodiments, the network environment 100 may also include UE 106. The UE 106 may be coupled with the UE 104 via a sidelink interface. In some embodiments, the UE 106 may act as a relay node to communicatively couple the UE 104 to the RAN 110. In other embodiments, the UE 106 and the UE 104 may represent end nodes of a communication link. For example, the UEs 104 and 106 may exchange data with one another.

[0031] The base station 108 may transmit information (for example, data and control signaling) in the downlink direction by mapping logical channels on the transport channels and transport channels onto physical channels. The logical channels may transfer data between a radio link control (RLC) and MAC layers; the transport channels may transfer data between the MAC and PHY layers; and the physical channels may transfer information across the air interface. The physical channels may include a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), and a physical downlink shared channel (PDSCH).

[0032] The PBCH may be used to broadcast system information that the UE 104 may use for initial access to a serving cell. The PBCH may be transmitted along with physical synchronization signals (PSS) and secondary synchronization signals (SSS) in an SSB. The SSBs may be used by the UE 104 during a cell search procedure (including cell selection and reselection) and for beam selection.

[0033] The PDSCH may be used to transfer end-user application data, signaling radio bearer (SRB) messages, system information messages (other than, for example, MIB), and Sis.

[0034] The PDCCH may transfer downlink control information (DCI) that is used by a scheduler of the base station 108 to allocate both uplink and downlink resources. The DCI may also be used to provide uplink power control commands, configure a slot format, or indicate that preemption has occurred.

[0035] The base station 108 may also transmit various reference signals to the UE 104. The reference signals may include demodulation reference signals (DMRSs) for the PBCH, PDCCH, and PDSCH. The UE 104 may compare a received version of the DMRS with a known DMRS sequence that was transmitted to estimate an impact of the propagation channel. The UE 104 may then apply an inverse of the propagation channel during a demodulation process of a corresponding physical channel transmission.

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

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

[0038] The UE 104 may transmit data and control information to the base station 108 using physical uplink channels. Different types of physical uplink channels are possible including, for instance, a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH). Whereas the PUCCH carries control information from the UE 104 to the base station 108, such as uplink control information (UCI), the PUSCH carries data traffic (e.g., end-user application data) and can carry UCI.

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

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

[0041] The UE 104 can operate in an idle mode when not needed to conserve power. When the UE 104 is needed by the network, the network (e.g., through the base station 108) can send a paging message to the UE 104. The UE 104 periodically monitors for paging messages. For example, the UE 104 wakes-up at the defined paging occasion (PO) and monitors for the paging messages. The paging messages include a temporary mobile subscriber identity (TMSI) value for the UE 104. If the UE 104 does not find the TMSI of the UE 104 inside the paging messages, the UE 104 assumes that it is not paged, and it will go back to idle mode. However, if the UE 104 finds the TMSI for the UE 104 in one of the paging messages, the UE determines 104 that the page is addressed to it and initiates a radio resource control connection. Alternatively, the UE may monitor a wake up signal (WUS). If a WUS is received for the UE, the UE wakes up and monitors the page messages.

[0042] A low-power WUS (LP-WUS) can represent a type of WUS enabling a receiver (referred to as low-power wake-up receiver (LP-WUR)) to monitor and detect the WUS signaling of a network using a relatively lower power than the regular signal reception. A paging early indication (PEI) can represent a paging enhancement for UE power saving, which transmits an indication on whether a UE needs to monitor the subsequent paging occasion. Embodiments described herein in association LP-WUS and/or PEI enable at least power savings.

[0043] In an example, the base station 108 sends configuration information 150 to the UE 104 (e.g., via radio resource control (RRC) signaling). The configuration information 150 can indicate an LP-WUS configuration 130 and a PEI configuration 140. The two configurations can be separate 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 the two configurations are separate, their specific values can be equal, different, uncorrelated from each other, or correlated with each other (e.g., values of the LP-WUS configuration 130 can be derived from values of the PEI configuration 140). The LP-WUS configuration 130 can indicate a first subgroup ID associated with a first sub grouping of UEs. The UE 104 is configured with the first subgroup ID such that, for the purpose of LP-WUS, the UE 104 belongs to the first subgrouping of UEs. In other words, upon reception of an LP-WUS indicating a wake-up for the first subgroup ID, the UE 104 can determine that the LP-WUS wakes up the UE 104. Similarly, the PEI configuration 140 can indicate a second subgroup ID associated with a second subgrouping of UEs. The UE 104 is configured with the second subgroup ID such that, for the purpose of PEI, the UE 104 belongs to the second subgrouping of UEs. In other words, upon reception of a PEI indicating paging monitoring for the second subgroup ID, the UE 104 can determine that the UE 104 is to monitor a paging occasion. The two UE subgroupings can be different.

[0044] To illustrate, consider the following scenario. The UE 104 and the UE 106 are configured with “subgroup ID 3” for LP-WUS, but UE 104 is configured with “subgroup ID 1” and the UE 106 is configured with “subgroup ID 2” for PEI. When paging the UE 104 but not the UE 106 is needed, the network (e.g., the base station 108) transmits a wake-up indication for “subgroup ID 3” in LP-WUS and transmits an indication for “subgroup ID 2” in PEI. The LP-WUS wakes up both the UEs 104 and 106. After the UEs 104 and 106 wake up and receive PEI, the UE 104 continues to receive paging PDCCH, but the UE 106 does not need to receive paging PDCCH and can go back to sleep immediately. [0045] As explained herein above, each one of the LP-WUS configuration 130 and PEI configuration 140 indicates a subgroup ID. For LP-WUS, the subgroup ID can correspond to a core network assigned subgrouping (e.g., the first subgrouping of UEs that is assigned by the core network 112). Alternatively, for LP-WUS, the subgroup ID can correspond to a UE ID based subgrouping (e.g., an ID that the UE derives from parameters of the LP-WUS configuration 130). Similarly, for PEI, the subgroup ID can correspond to a core network assigned subgrouping (e.g., the second subgrouping of UEs that is assigned by the core network 112). Alternatively, for PEI, the subgroup ID can correspond to aUE ID based subgrouping (e.g., an ID that the UE derives from parameters of the PEI configuration 140). It is possible that the types of subgroup IDs (e.g., whether core network-assigned or UE ID- based) can be different between the two configurations 130 and 140. For example, the UE 104 can use a core network assigned subgroup ID for PEI, while using UE ID based subgroup ID for LP- WUS (or vice versa). In another example, the UE 104 can use a core network assigned subgroup IDs for both LP-WUS and PEI, with separate parameters configured. In yet another example, the UR 104 can use UE ID based subgroup IDs for both LP-WUS and PEI, but the subgroup IDs are derived differently or separately.

[0046] FIG. 2 illustrates an example 200 of using a LP-WUS and a PEI in accordance with some embodiments. In 3GPP Release-17, PEI was specified. Generally, PEI supports subgroup-based indications. When a UE receives a positive indication for its subgroup in PEI, the UE continues to receive a paging DCI; Otherwise, may go back to sleep. In 3GPP Release-18, a study item on low-power wake-up signal and receiver (LP WUS/WUR) for NR was completed. LP-WUS is considered for additional objectives including for IDLE and INACTIVE modes. Particularly, the LP-WUS may be usable to trigger or indicate paging monitoring. In this case, LP-WUS can also support subgroup-based wakeup indication. As illustrated in example 200, a possible UE behavior after receiving LP-WUS is to wake up and receive PEI, if PEI is configured. Assuming that PEI is configured and depending on this configuration, the UE can then monitor a paging occasion. In such situations, the subgroup ID for LP-WUS can be designed to work together with the subgroup-based indication in PEI.

[0047] Typically, the UE needs to periodically monitor the configured paging channels to detect upcoming traffic. Periodic paging occasions (Pos) can be configured for the UE. When operating in an IDLE mode or INACTIVE mode, the UE monitors the Pos. A PO 230 is defined by a PDCCH search space (shown as paging PDCCH 232) and an associated paging PDSCH record (shown as paging PDSCH 234). The UE monitors the paging PDCCH 232. If a paging indication is present, the UE receives and decodes the paging PDSCH 234, decode the paging record (PDSCH) and become aware of listed identifiers that are actually paged (e.g., a radio network temporary identifier (RNTI), a temporary mobile subscriber identity (TMSI), etc.). If paged, the UE triggers a connection establishment procedure. Otherwise, the UE transitions back to a deep sleep state.

[0048] PEI 220 enhances the paging by at least reducing the UE’ s power consumption. The PEI 220 can involve a limited-size DCI search space or a sequence, transmitted prior to each PO 230. When operating in the IDLE mode or the INACTIVE mode, the UE monitors the search space of PEI 220. When a PEI indication is present in the search space, the UE can monitor the next PO 230. Otherwise, the UE can back to a deep sleep and skip detecting the PO 230. Additionally, the PEI 220 can be indicated for a certain subgroup of IDLE and/or INACTIVE UEs. UEs can be grouped in paging subgroups. Each paging subgroup can have a subgroup ID for PEI. The PEI 220 can indicate a paging monitoring for a particular subgroup ID (e.g., an ID corresponding to one of the subgroups of IDLE and/or INACTIVE UEs).

[0049] LP-WUS 210 can also be another enhancement to paging. The UE may monitor a wake up signal (WUS). If the LP-WUS 210 is received and indicated to be for the UE (e.g., by indicating the relevant subgroup ID), the UE wakes up and monitors paging messages in the next PO 230. Otherwise, the UE can remain in a sleep state (e.g., as part of operating in the IDLE or INACTIVE mode). Generally, the LP-WUS 210 can represent a type of a wakeup signal enabling a receiver (referred to as low-power wake-up receiver (LP-WUR)) to monitor and detect the WUS signaling of a network using a relatively lower power than the regular signal reception. The LP-WUS 210 can support subgroup-based wakeup indication. Particularly, the LP-WUS 210 can be indicated for a certain subgroup of IDLE and/or INACTIVE UEs. UEs can be grouped in paging subgroups (which may be the same or different than those of PEIs). Here also, each paging subgroup can have a subgroup ID for LP-WUS. The LP-WUS 210 can indicate a wake-up for a particular subgroup ID (e.g., an ID corresponding to one of the subgroups of IDLE and/or INACTIVE UEs).

[0050] In example 200, three scenarios are shown, from the top to the bottom of FIG. 2. In all three scenarios, a UE (e.g., an example of the UE 104) is configured with a first subgroup ID 212 for LP-WUS and a second subgroup ID 222 for PEI. [0051] In the first scenario (the top of FIG. 2), the UE is paged. As illustrated, the UE receives and processes an LP-WUS 210. The LP-WUS 210 indicates wake-up for the first subgroup ID 212. Accordingly, the UE does not go back to sleep. Instead, the UE receives and processes a PEI 220. Here, the PEI 220 indicates paging monitoring for the second subgroup ID 222. Accordingly, the UE monitors the next PO 230 rather than going to sleep.

[0052] In the second scenario (the middle of FIG. 2), the UE is not paged. Here, the UE receives and processes an LP-WUS 210. However, the LP-WUS indicates wake-up for a different subgroup ID for LP-WUS (e.g., different than the first subgroup ID 212). Accordingly, the UE goes back to sleep 250 (e.g., transitions back to a sleep state of a sleep cycle, such as a deep sleep state or a light sleep state, in which one or more components of the UE including radio frequency components are deactivated or powered OFF). A subsequent PEI 220 and a subsequent PO 230 are not monitored because the UE is in the sleep state. There is no need to wake up the main radio in this case.

[0053] In the third scenario (the bottom of FIG. 2), the UE is not paged. Here, the UE receives and processes an LP-WUS 210. The LP-WUS 210 indicates wake-up for the first subgroup ID 212. Accordingly, the UE does not go back to sleep. Instead, the UE receives and processes a PEI 220. Here, however, the PEI 220 indicates paging monitoring for a different subgroup ID for PEI (e.g., different than the second subgroup ID 222). Accordingly, the UE goes back to sleep 250. A subsequent PO 230 is not monitored because the UE is in the sleep state.

[0054] FIG. 3 illustrates an example of a sequence diagram 300 for using an LP-WUS and a PEI in accordance with some embodiments. A base station 308 and a UE 104 are involved in the sequence diagram 300 and are examples of the base station 108 and the UE 104 of FIG.

1. In a first step of the sequence diagram 300, the base station 308 sends configuration information to the UE 304 (similar to the configuration information 150) such that the 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 sent via RRC signaling. Example parameters of the LP-WUS configuration and the PEI configuration are described herein below. The configuration information can also include information related to configuring POs for the UE.

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

[0056] In a third step of the sequence diagram 300, the base station 308 can send a LP- WUS indicating wake-up for the subgroup ID. The LP-WUS can be carried by DCI. At least a portion of the LP-WUS can indicate that UEs associated with the first subgroup ID are to be woken up for paging monitoring. For instance, this LP-WUS can include the first subgroup ID explicitly, or include a positive indication for the first subgroup ID. The LP-WUS need indicate a subgroup ID explicitly. It can indicate whether a subgroup should wake up or not by including, for example, a bitmap, with one bit for each subgroup.

[0057] In a fourth step of the sequence diagram 300, the base station 308 can send PEI indicating whether to monitor paging for the subgroup ID. The PEI can be carried by DCI. At least a portion of the DCI can represent a PEI and can indicate that UEs associated with the second subgroup ID are to monitor a next configured paging occasion. For instance, this DCI can include the second subgroup ID explicitly, or include a positive indication for the first subgroup ID. The PEI need indicate a subgroup ID explicitly. It can use a bitmap, where each bit can correspond to a subgroup.

[0058] In a fifth step of the sequence diagram 300, the base station 308 can schedule a next PO by sending a paging indication in a paging PDCCH and paging messages in a configured paging PDSCH. Here, if the UE determines positive indication for the first subgroup ID and the second subgroup ID, the UE can monitor the PO (as in the first scenario of FIG. 2). Otherwise, no monitoring is performed (as in the second or third scenario of FIG. 2 as the case may be).

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

[0060] In another example, the subgroup ID for LP-WUS corresponds to a UE ID based subgrouping for LP-WUS. Here, the subgroup ID for LP-WUS can be different from the subgroup ID for PEI (which can correspond to a core network assigned subgrouping for PEI or to a UE ID based subgrouping for PEI). Generally, whether core network assigned subgrouping or UE ID based subgrouping is used for LP-WUS for a UE is the same as the one used for PEI depends on the configurations. 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 can include at least one of: a total number of subgroups configured per paging occasion (PO) for LP-WUS (referred to as “ subgroup sNumPerPOLpwus” indicating the total number of subgroups for LP-WUS) or a number of subgroups configured for the UE ID based subgrouping for LP-WUS (referred to as “subgroupsNumForUEIDLpwus” indicating the number of subgroups for LP-WUS for UE ID based subgrouping). For instance, the LP-WUS configuration supporting the subgrouping can be expressed as:

SubgroupConfigLpwus ::= SEQUENCE { subgroupsNumPerPOLpwus INTEGER (L. maxNrofPagingSubgroupsLpwus-rl7), subgroupsNumForUEIDLpwus INTEGER (L. maxNrofPagingSubgroupsLpwus-rl7) OPTIONAL, - Need S

}

[0061] As explained herein above, the subgroup ID for PEI can correspond to a UE ID based subgrouping for PEI. Here, the subgroup ID for PEI can be configured using a set of parameters (referred to herein as PEI parameters). This set can include at least one of: a total number of subgroups per PO for the UE to read subgroups indication from physical-layer signaling (referred to as “ subgroup sNumPerPO”) or a number of subgroups per PO for the UE to read subgroups indication from physical-layer signaling (referred to as “subgroupsNumForUEID” indicating the number of subgroups for UE ID based subgrouping in a PO, which is broadcasted in system information). For instance, the PEI configuration supporting the subgrouping can be expressed as: SubgroupConfig-rl7 ::= SEQUENCE { subgroupsNumPerPO-rl7 INTEGER (L. maxNrofPagingSubgroups-r!7), subgroupsNumForUEID-rl7 INTEGER ( I .. maxNrofPagingSubgroups-rl7) OPTIONAL, - Need S

}

[0062] 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/(N * Ns)) mod subgroupsNumforUEID) + subgroupsNumPerPO — subgroupsNumforUEID), which can be found in 3GPP, TS 38.304, V18. 1.0 (2024-03), the content of which is incorporated herein by reference in its entirety. In this formula, “subgroupsNumPerPO” and “subgroupsNumForUEID” are configured. “N” is the number of total paging frames in T, which is the discontinuous reception (DRX) cycle of RRC IDLE state. “Ns” is the number of paging occasion for a PF. “UE ID” can be the 5G-S-TMSI mod X, where X is 32768, if eDRX is applied; otherwise, X is 8192.

[0063] Referring back to 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 formula(s) generally use(s) the LP-WUS parameters. The specific formula that is used can reflect a particular design approach. In a first design approach, the subgroup IDs of a UE used for LP-WUS and PEI are closely correlated. Here, one set of formulas is possible. In a second design approach, the subgroup IDs of a UE used for LP-WUS and PEI are largely independent or uncorrelated. Here, a different set of formulas is possible. Such formulas are described herein next.

[0064] The following notations are introduced to explain the options for UE ID based subgrouping for LP-WUS. “subgroupsNumPerPOLpwus” can refer to the total number of subgroups configured for LP-WUS. “subgroupsNumForUEIDLpwus” can refer 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” can refer to the maximum number of subgroups that can be supported for LP-WUS. Let “K = ceil(log2(Nmax))”, which represents the number of bits needed for representing “Nmax” (e.g., if there are a maximum of eight subgroups for LP-WUS, then “K” is equal to three). “Lmax” can refer to the maximum number of subgroups that can be supported for PEI. Let “M = ceil(log2(Lmax))”, which represents the number of bits needed for representing “Lmax” (e.g. if there are a maximum of eight subgroups for PEI, “M” is equal to three).

[0065] In a first example, the subgroup IDs of a UE used for LP-WUS and PEI are closely correlated. Particularly, the first subgroup ID for LP-WUS is different from the second subgroup ID for PEI, is correlated with the second subgroup ID for PEI, and corresponds to a UE ID based subgrouping. Here, the first subgroup ID can be determined based on a first parameter common to a determination of the second subgroup ID and a second parameter unused in the determination of the second subgroup ID. The first parameter can include a UE ID that is used in the determination of the second subgroup ID (e.g., the same “UE ID” shown in the above formula). Alternatively, the first parameter can include a first UE ID (shown as “UE ID” in the formulas below) that overlaps (partially or fully) with a second UE ID (shown as “UE ID” in the above formula) used in the determination of the second subgroup ID (where the two UE IDs are different from each other by at least one bit). The second parameter can include a number of subgroups configured for the UE ID based subgrouping for LP-WUS (e.g., “subgroupsNumForUEIDLpwus”). Furthermore, the first subgroup ID can be determined based on a difference between a total number of subgroups configured per PO for LP-WUS and a number of subgroups configured for the UE ID based subgrouping for LP-WUS (e.g., “ subgroup sNumPerPoLpwus - subgroupsNumF orUEIDLpwus”).

[0066] As such, the subgroup ID for LP-WUS can be calculated based on a UE ID that is the same as or overlapping with the UE ID used for the subgroup ID calculation for PEI. A first possible formula is “SubgrouplDLpwus = (floor(UEJD/(N *

Ns)) mod subgroupsNumForUEIDLpwus”. Here, the “UE ID” is the same as the UE ID used for PEI in the above formula for PEI. This approach can work if LP-WUS has a smaller number of subgroups for UE ID based subgrouping than PEI. For instance, if “subgroupsNumForUEIDLpwus” is equal to four and the “subgroupsNumForUEID” is equal to eight, the subgroup ID for LP WUS is the two least significant bits (LSBs) of the subgroup ID for PEI. A second possible formula is “SubgrouplDLpwus = floor(UEJD / (N * Ns)) mod subgroupsNumForUEIDLpwus, where UEJD = 5G — S — TMS1 mod (X * Nmax)”. Here “X” can be different from what is used in the above formula for PEL For instance, “X” can be equal to 4,096 if eDRX (extended DRX) is applied, or 1,024 otherwise. To illustrate how this formula impacts the ID bits, consider the case where “subgroupsNumForUEIDLpwus” is equal to “Nmax” of sixteen “subgroupsNumForUEID” is equal to “Lmax” of eight. The UE IDs for LP-WUS and PEI have three overlapping bits, and the subgroup ID for PEI is the three LSBs of the subgroup ID for LP-WUS. In both formulas for LP-WUS, an additional offset of “subgroup sNumPerPoLpwus - subgroupsNumForUEIDLpwus” may be added to the calculated subgroup ID to obtain the final subgroup ID for LP-WUS.

[0067] In the example above, the subgroup IDs for LP-WUS and PEI can have overlapping bits. As such, the first subgroup ID for LP-WUS can be indicated by first bits, the second subgroup ID can be indicated by second bits, and either: first bits include the second bits additional bits (as in when the second formula is used), or the second bits include the second bits and the additional bits (as in when the first formula is used). In one implementation, the UE uses one of the two formulas for LP-WUS to derive the subgroup ID for LP-WUS. Alternatively, the UE determines first the second subgroup ID for PEI (e.g., by using the relevant formula) and determines the first subgroup ID for LP-WUS based on the overlapping bits rather than a formula calculation (or vice versa).

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

[0069] A first possible formula in this second example is “SubgrouplDLpwus = floor(UEJD/(N * Ns * subgroupsNumForUElD)) mod subgroupsNumForUEIDLpwus”. Here, the “UE ID “can be calculated in different ways, with a few examples as follows. The “UE ID” can be equal to “5G — S — TMSI mod X”, where “X is 32768 * Nmax ” if eDRX is applied, or “8192*Nmax” otherwise. This can correspond to “(15+K)” LSBs of 5G-S-TMSI if eDRX is applied, or “(13+K)” LSBs otherwise. The “UE ID” can be equal to “5G — S — TMS1 mod (N * Ns * Lmax * Nmax)”. The “UE ID” can be equal to “5G — S —

TMS1 mod (N * Ns * subgroupsNumForUElD * subgroupsNumForUElDLpwus)”. The “UE ID” cab be the full 5G-S-TMSI. Or the “UE ID” can be the thirty-two (or some other number of) LSBs of 5G-S-TMSI (e.g., the 32-bit 5G-TMSI).

[0070] A first possible formula in this second example is “SubgrouplDLpwus = UEJD mod subgroupsNumForUElDLpwus”. Here, the “UE ID” the sixteenth LSB to “(15+K)-th” LSB of 5G-S-TMSI if eDRX is applied, or the fourteenth LSB to “(13+K)-th” LSB otherwise. Alternatively, the “UE ID” can be any “K” bits of 5G-S-TMSI other than the fifteen or thirteen LSBs.

[0071] In both formulas for LP-WUS, the “UE IDs” for LP-WUS and PEI are calculated using different parts of 5G-S-TMSI. As such, the resulting subgroup IDs are mostly uncorrelated. For all the examples, an additional offset of “subgroupsNumPerPoLpwus - subgroupsNumForUElDLpwus” can be added to the calculated subgroup ID to obtain the final subgroup ID for LP-WUS.

[0072] Independent or uncorrelated subgroup ID allocation for a UE for LP-WUS and PEI can reduce the false paging probability, which is the probability of a UE waking up to receive paging PDSCH but there is no UE ID match in the paging PDSCH. False paging is due to the paging for other UEs in the same PO and/or the same subgroup. To illustrate, consider the following scenario. A first UE and a second UE both have “subgroup ID 3” for LP-WUS, but the first UE has “subgroup ID 1” and the second UE has “subgroup ID 2” for PEI. When the network needs to page the second UE, it transmits a wake-up indication for “subgroup ID 3” in LP-WUS and transmits PEI for “subgroup ID 2”. The LP-WUS wakes up both the first UE and the second UE. After the first UE and the second UE wake up and receive PEI, the second UE continues to receive paging PDCCH, but the first UE does not need to receive paging PDCCH and can go back to sleep immediately. This means the false paging probability for the first UE is reduced when it monitors both LP-WUS and PEI compared to the case when it monitors LP-WUS alone.

[0073] If the subgroup ID for LP-WUS is decoupled from the subgroup ID for PEI as much as possible, UEs sharing the same subgroup ID for LP-WUS can be mapped to different subgroup IDs for PEI. In this case, the UE may be mapped to different subgroup IDs for PEI as evenly as possible. [0074] Herein next, are illustrative use cases based on the above approaches where the subgroup ID for LP-WUS and PEI can be largely independent. These approaches can be beneficial for reducing the false paging probability if the UE monitors both LP-WUS and PEI. In a first use case, a UE can use core network assigned subgroup ID for PEI, while using UE ID based subgroup ID for LP-WUS (or vice versa). In this case, “subgroupsNumPerPOLpwus” and “subgroupsNumForUEIDLpwus” are separately configured for LP-WUS. The subgroup ID for PEI is the one assigned by the core network. ► The subgroup ID for LP-WUS is the one calculated based on “subgroupsNumPerPOLpwus,” “subgroupsNumForUEIDLpwus,” and the UE’s own 5G-S-TMSI using any of the above formulas.

[0075] In a second use case, a UE can use a core network assigned subgroup ID for both LP-WUS and PEI, with separate parameters configured. A specific LP-WUS parameter is used for the core network assigned subgroup ID for LP-WUS. A different parameter is used for the core network assigned subgroup ID for PEI.

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

[0077] FIG. 4 illustrates an example of an operational flow/algorithmic structure 400 for determining a subgroup ID in accordance with some embodiments. The operational flow/algorithmic structure 400 can be implemented by a UE (e.g., performed by components thereof including, for example, processors of the UE). The UE can be any of the UE described herein. In some embodiments, the operational flow/algorithmic structure 400 may be implemented by executing instructions stored in a tangible, non-transitory, computer- readable storage medium, such as a memory of the UE. While the operational flow/algorithmic structure 400 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be omitted or not performed altogether.

[0078] In an example, the operational flow/algorithmic structure 400 includes, at 402, determining whether a first parameter is configured. When the operational flow/algorithmic structure 400 is used to determine a subgroup ID for LP-WUS, the first parameter can be a first LP-WUS parameter, such as “subgroupsNumForUEIDLpwus.” When the operational flow/algorithmic structure 400 is used to determine a subgroup ID for PEI, the first parameter can be a first PEI parameter, such as “subgroupsNumForUEID.” If the first parameter is not configured, the operational flow/algorithmic structure 400 can proceed to 404. Otherwise, the operational flow/algorithmic structure 400 can proceed to 408.

[0079] In an example, the operational flow/algorithmic structure 400 includes, at 404, determining whether a subgroup ID has been assigned by the core network. When the operational flow/algorithmic structure 400 is used to determine the subgroup ID for LP- WUS, this core network assignment can be for LP-WUS. When the operational flow/algorithmic structure 400 is used to determine a subgroup ID for PEI, this core network assignment canbe for PEI. In both cases, the RRC configuration for LP-WUS (in the first case) and/or PEI (in the second case) are checked. If this subgroup ID is not assigned by the core network, the operational flow/algorithmic structure 400 can result in determining that the UE is not part of a subgroup of UEs (e.g., for LP-WUS in the first case and/or PEI in the second case). Otherwise, the operational flow/algorithmic structure 400 can proceed to 406.

[0080] In an example, the operational flow/algorithmic structure 400 includes, at 406, using the core network assigned subgrouping. When the operational flow/algorithmic structure 400 is used to determine the subgroup ID for LP-WUS, the configured LP-WUS parameter indicates the value for the subgroup ID for LP-WUS. When the operational flow/algorithmic structure 400 is used to determine a subgroup ID for PEI, the configured PEI parameter indicates the value for the subgroup ID for PEI.

[0081] In an example, the operational flow/algorithmic structure 400 includes, at 408, determining whether the first parameter and a second parameter are configured. When the operational flow/algorithmic structure 400 is used to determine a subgroup ID for LP-WUS, the second parameter can be a second LP-WUS parameter, such as “subgroupsNumPerPOLpwus.” When the operational flow/algorithmic structure 400 is used to determine a 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 operational flow/algorithmic structure 400 can result in determining that the UE is not part of a subgroup of UEs (e.g., for LP-WUS in the first case and/or PEI in the second case). Otherwise, the operational flow/algorithmic structure 400 can proceed to 410.

[0082] In an example, the operational flow/algorithmic structure 400 includes, at 410, determining whether the parameters are equal to each other. For instance, the values of the two parameters can be compared. If they are not equal, the operational flow/algorithmic structure 400 can proceed to 414. Otherwise, the operational flow/algorithmic structure 400 can proceed to 412.

[0083] In an example, the operational flow/algorithmic structure 400 includes, at 412, using a UE ID based subgrouping. When the operational flow/algorithmic structure 400 is used 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 the operational flow/algorithmic structure 400 is used to determine a subgroup ID for PEI, the formula above for PEI can be used to derive the subgroup ID.

[0084] In an example, the operational flow/algorithmic structure 400 includes, at 414, determining whether a subgroup ID has been assigned by the core network. When the operational flow/algorithmic structure 400 is used to determine the subgroup ID for LP- WUS, this core network assignment can be for LP-WUS. When the operational flow/algorithmic structure 400 is used to determine a subgroup ID for PEI, this core network assignment can be for PEI. In both cases, the RRC configuration for LP-WUS (in the first case) and/or PEI (in the second case) are checked. If this subgroup ID is not assigned by the core network, the operational flow/algorithmic structure 400 can proceed to 418. Otherwise, the operational flow/algorithmic structure 400 can proceed to 416.

[0085] In an example, the operational flow/algorithmic structure 400 includes, at 416, using the core network assigned subgrouping. When the operational flow/algorithmic structure 400 is used to determine the subgroup ID for LP-WUS, the configured LP-WUS parameter indicates the value for the subgroup ID for LP-WUS. When the operational flow/algorithmic structure 400 is used to determine a subgroup ID for PEI, the configured PEI parameter indicates the value for the subgroup ID for PEI.

[0086] In an example, the operational flow/algorithmic structure 400 includes, at 418, using the UE ID based subgrouping. When the operational flow/algorithmic structure 400 is used 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 the operational flow/algorithmic structure 400 is used to determine a subgroup ID for PEI, the formula above for PEI can be used to derive the subgroup ID.

[0087] FIG. 5 illustrates an example of flow/algorithmic structure 500 for using subgroup IDs for LP-WUS and PEI in accordance with some embodiments. The operational flow/algorithmic structure 500 can be implemented by a UE (e.g., performed by components thereof including, for example, processors of the UE). The UE can be any of the UE described herein. In some embodiments, the operational flow/algorithmic structure 500 may be implemented by executing instructions stored in a tangible, non-transitory, computer- readable storage medium, such as a memory of the UE. While the operational flow/algorithmic structure 500 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be omitted or not performed altogether.

[0088] In an example, the operational flow/algorithmic structure 500 includes, at 502, processing configuration information indicating an LP-WUS configuration and a PEI configuration. The configuration information is received based RRC signaling. The LP-WUS configuration is separate from the PEI configuration and indicates a first subgroup ID for LP- WUS. The first subgroup ID corresponds to a core network assigned sub grouping for LP- WUS or a UE ID based subgrouping for LP-WUS. The PEI configuration indicates a second subgroup ID for PEI.

[0089] In an example, the operational flow/algorithmic structure 500 includes, at 504, determining that a received LP-WUS indicates wake-up for the first subgroup ID. For example, the LP-WUS is received and processed to determine that it includes a wake-up indication and the first subgroup ID. Here, the UE can determine that the indicated first subgroup ID applies to it (matches the configured subgroup ID for LP-WUS) and wakes up the main radio to monitor PEI and/or paging occasion.

[0090] In an example, the operational flow/algorithmic structure 500 includes, at 506, determining that a PEI indicates paging monitoring for the second subgroup ID. The PEI is received based on the received LP-WUS indicating the first subgroup ID. Particularly, because the UE wakes up the main radio, the UE is capable of receiving and processing the PEI. The processing can result in determining that the PEI indicates that paging monitoring is to be performed by UEs associated with the second subgroup ID. Here, the UE can determine that the indicated second subgroup ID applies to it (matches the configured subgroup ID for PEI) and does not transition back to a sleep state.

[0091] In an example, the operational flow/algorithmic structure 500 includes, at 508, processing a paging occasion based on the PEI indicating the second subgroup ID. for example PDDCH paging is processed indicating that paging PDSCH is to be monitored. Thereafter, paging PDSCH is processed.

[0092] FIG. 6 illustrates another example of flow/algorithmic structure 600 for using subgroup IDs for LP-WUS and PEI in accordance with some embodiments. The operational flow/algorithmic structure 600 can be implemented by a network (e.g., by a base station thereof, a core network thereof, processors of the base station, and/or processors of the core network). The network can be any of the networks described herein. In some embodiments, the operational flow/algorithmic structure 600 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable storage medium, such as a memory of the base station. While the operational flow/algorithmic structure 600 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be omitted or not performed altogether.

[0093] In an example, the operational flow/algorithmic structure 600 includes, at 602, sending, to a UE, RRC signaling indicating configuration information for an LP-WUS configuration and a 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 core network assigned subgrouping for LP-WUS or a UE ID based subgrouping for LP-WUS. The PEI configuration indicates a second subgroup ID for PEI.

[0094] In an example, the operational flow/algorithmic structure 600 includes, at 604, sending, to the UE, a LP-WUS that indicates wake-up for the first subgroup ID. For instance, DCI can be sent and at least a portion thereof can represent the LP-WUS.

[0095] In an example, the operational flow/algorithmic structure 600 includes, at 606, sending, to the UE, a PEI that indicates paging monitoring for the second subgroup ID. The PEI is sent based on the LP-WUS indicating the first subgroup ID. For instance, DCI is sent and at least a portion thereof can represent the PEI. This DCI is sent given that the DCI for LP-WUS was sent to wake up UEs associated with the first subgroup ID.

[0096] In an example, the operational flow/algorithmic structure 600 includes, at 608, scheduling a paging occasion for the UE based on the PEI indicating the second subgroup ID. For example, a configured PO can be used and can include paging PDCCH and paging PDSCH. Given that the PEI was sent for indicating a paging applicable to a subgroup of UEs, the padding PDCCH can include an indication to monitor the paging PDSCH, and the paging PDSCH can include padding messages applicable to one or more of such UEs.

[0097] FIG. 7 illustrates receive components 700 of a UE (e.g., the UE 104 of FIG. 1 and any other UE described herein capable of receiving and processing an LP-WUS and a PEI), in accordance with some embodiments. The receive components 700 may include an antenna panel 704 that includes a number of antenna elements. The panel 704 is shown with four antenna elements, but other embodiments may include other numbers. Multiple antenna panels may also be included.

[0098] The antenna panel 704 may be coupled to analog beamforming (BF) components that include a number of phase shifters 708(l)-708(4). The phase shifters 708(l)-708(4) may be coupled with a radio-frequency (RF) chain 709. The RF chain 709 may amplify a receive analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal to a digital baseband signal that may be provided to a baseband processor for further processing.

[0099] In various embodiments, control circuitry, which may reside in a baseband processor, may provide BF weights (for example W1-W4), which may represent phase shift values to the phase shifters 708(l)-708(4) to provide a receive beam at the antenna panel 704. These BF weights may be determined based on the channel-based beamforming. As further described herein below, the baseband processor can detect the payload of the LP- WUS and control an operational mode of the UE.

[0100] FIG. 8 illustrates a UE 800 in accordance with some embodiments. The UE 800 may be similar to and substantially interchangeable with the UE 104 or 106 or any UE described herein capable of receiving and processing an LP-WUS and a PEI. For example, the UE 800 can receive configuration information indicating an LP-WUS configuration separate from a PEI configuration, where each configuration indicates a subgroup ID usable to wake up and perform paging monitoring if the UE 800 belongs to the UE subgroups indicated by the subgroup IDs.

[0101] The UE 800 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, electric voltage/current meters, or actuators), video surveillance/monitoring devices (for example, cameras or video cameras), wearable devices (for example, a smart watch), or Intemet-of- things devices.

[0102] The UE 800 may include processors 804, RF interface circuitry 808, memory/storage 812, user interface 816, sensors 820, driver circuitry 822, power management integrated circuit (PMIC) 824, antenna 826, and battery 828. The components of the UE 800 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 8 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 arrangement of the components shown may occur in other implementations.

[0103] The components of the UE 800 may be coupled with various other components over one or more interconnects 832, which may represent any type of interface, input/output, bus (local, system, or expansion), transmission line, trace, or optical connection that allows various circuit components (on common or different chips or chipsets) to interact with one another.

[0104] The processors 804 may include processor circuitry such as, for example, baseband processor circuitry (BB) 804A, central processor unit circuitry (CPU) 804B, and graphics processor unit circuitry (GPU) 804C. The processors 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 812 to cause the UE 800 to perform delay-adaptive operations as described herein. The processors 804 may also include interface circuitry 804D to communicatively couple the processor circuitry with one or more other components of the UE 800. Any or a combination of the processors 804 can be configured to detect a payload of the LP-WUS. Particularly, while the UE 800 is in an RRC IDLE or RRC IN ACTIVE mode, the LP-WUS signal can be received and processed by the UE’ s 800 receive path to generate bits. The bits are passed to the processor(s) that can perform operations thereon as previously described, including the ones described in FIG. 14, to process the bits and determine the payload. Based on the payload, the processor(s) can trigger the UE 800 to switch to an RRC CONNECTED mode.

[0105] In some embodiments, the baseband processor circuitry 804A may access a communication protocol stack 836 in the memory/storage 812 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 804A may access the communication protocol stack 836 to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a NAS layer. In some embodiments, the PHY layer operations may additionally/altematively be performed by the components of the RF interface circuitry 808.

[0106] The baseband processor circuitry 804A may generate or process baseband signals or waveforms that carry information in 3 GPP-compatible networks. In some embodiments, the waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0107] The memory/storage 812 may include one or more non-transitory, computer- readable media that includes instructions (for example, communication protocol stack 836) that may be executed by one or more of the processors 804 to cause the UE 800 to perform various delay-adaptive operations described herein.

[0108] The memory/storage 812 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 800. In some embodiments, some of the memory/storage 812 may be located on the processors 804 themselves (for example, memory/storage 812 may be part of a chipset that corresponds to the baseband processor circuitry 804A), while other memory/storage 812 is external to the processors 804 but accessible thereto via a memory interface. The memory/storage 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.

[0109] The RF interface circuitry 808 may include transceiver circuitry and a radio frequency front module (RFEM) that allows the UE 800 to communicate with other devices over a radio access network. The RF interface circuitry 808 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0110] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna 826 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 804.

[oni] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna 826.

[0112] In various embodiments, the RF interface circuitry 808 may be configured to transmit/receive signals in a manner compatible with NR access technologies.

[0113] The antenna 826 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna 826 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna 826 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna 826 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.

[0114] The user interface 816 includes various input/output (VO) devices designed to enable user interaction with the UE 800. The user interface 816 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 800.

[0115] The sensors 820 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and send the information (sensor data) about the detected events to some other device, module, or subsystem. Examples of such sensors include inertia measurement units comprising accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3 -axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (for example, cameras or lensless apertures); light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other like audio capture devices.

[0116] The driver circuitry 822 may include software and hardware elements that operate to control particular devices that are embedded in the UE 800, attached to the UE 800, or otherwise communicatively coupled with the UE 800. The driver circuitry 822 may include individual drivers allowing other components to interact with or control various input/output (VO) devices that may be present within, or connected to, the UE 800. For example, driver circuitry 822 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensors 820 and control and allow access to sensors 820, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

[0117] The PMIC 824 may manage power provided to various components of the UE 800. In particular, with respect to the processors 804, the PMIC 824 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

[0118] A battery 828 may power the UE 800, although in some examples the UE 800 may be mounted deployed in a fixed location and may have a power supply coupled to an electrical grid. The 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, and the like. In some implementations, such as in vehicle-based applications, the battery 828 may be a typical lead- acid automotive battery.

[0119] FIG. 9 illustrates a network device 900 in accordance with some embodiments. The network device 900 may be similar to and substantially interchangeable with base station 108 or a device of the core network 112 or external data network 120 capable of generating and/or transmitting an LP-WUS and a PEI. For example, the network device 9100 can send configuration information indicating an LP-WUS configuration separate from a PEI configuration, where each configuration indicates a subgroup ID usable to wake up and page UE subgroups indicated by the subgroup IDs.

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

[0121] The components of the network device 900 may be coupled with various other components over one or more interconnects 928.

[0122] The processors 904, RF interface circuitry 908, memory/storage circuitry 912 (including communication protocol stack 910), antenna structure 926, and interconnects 928 may be similar to like-named elements shown and described with respect to FIG. 8.

[0123] The processors 904 may include processor circuitry such as, for example, baseband processor circuitry (BB) 904A, central processor unit circuitry (CPU) 904B, and graphics processor unit circuitry (GPU) 904C. The processors 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 circuitry 912 to cause the network device 900 to perform operations described herein. The processors 904 may also include interface circuitry 904D to communicatively couple the processor circuitry with one or more other components of the network device 900. Any or a combination of the processors 904 can be configured to generate a payload of the LP-WUS. Particularly, the processor(s) can generate information bits, encode them using a particular encoding schemes, extend the encoded bits, modulate the encoded bits using an OOK modulation, map the encoded bits to sequences, and carry the sequences in OFDM symbols or parts thereof) corresponding to OOK bits of “1”.

[0124] The CN interface circuitry 914 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to/from the network device 900 via a fiber optic or wireless backhaul. The CN interface circuitry 914 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 914 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0125] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0126] For one or more embodiments, at least one of the components set forth in one or more of the preceding FIG.s may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding FIG.s may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding FIG.s may be configured to operate in accordance with one or more of the examples set forth below in the example section.

Examples

[0127] In the following sections, further exemplary embodiments are provided.

[0128] 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 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 core network assigned sub grouping for LP-WUS or a user equipment (UE) ID based subgrouping for LP-WUS, the PEI configuration indicating a second subgroup ID; determining that a received LP-WUS indicates wake-up for the first subgroup ID; determining that a PEI indicates paging monitoring for the second subgroup ID, the PEI received based on the received LP-WUS indicating the first subgroup ID; and processing a paging occasion based on the PEI indicating the second subgroup ID. [0129] Example 2 includes a method comprising: sending, to a UE, radio resource control (RRC) signaling indicating configuration information for 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 core network assigned subgrouping for LP-WUS or a user equipment (UE) ID based subgrouping for LP-WUS, the PEI configuration indicating a second subgroup ID; sending, to the UE, a LP-WUS that indicates wake-up for the first subgroup ID; sending, to the UE, a PEI that indicates paging monitoring for the second subgroup ID, the PEI sent based on the LP-WUS indicating the first subgroup ID; and scheduling a paging occasion for the UE based on the PEI indicating the second subgroup ID.

[0130] Example 3 includes the method of any preceding example 1-2, 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 a core network.

[0131] Example 4 includes the method of any preceding example 1-3, wherein the RRC signaling indicates the second subgroup ID but not the first subgroup ID, and further comprising: setting the first subgroup ID of the LP-WUS configuration, or causing the first subgroup ID to be set, to have a same value as the second subgroup ID based on the RRC signaling.

[0132] Example 5 includes the method of any preceding example 1-2, 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 a core network.

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

[0134] Example 7 includes the method of example 6, wherein the set of parameters includes at least one of a total number of subgroups configured per paging occasion (PO) for LP-WUS or a number of subgroups configured for the UE ID based subgrouping for LP- WUS. [0135] Example 8 includes the method of any preceding example 1-2 or 7, wherein the first subgroup ID is different from the second subgroup ID, is correlated with the second subgroup ID, and corresponds to the UE ID based subgrouping.

[0136] Example 9 includes the method of example 8, further comprising: determining the first subgroup ID, or causing the first subgroup ID to be determined, based on a first parameter common to a determination of the second subgroup ID and a second parameter unused in the determination of the second subgroup ID.

[0137] Example 10 includes the method of example 9, wherein the first parameter includes a UE ID that is used in the determination of the second subgroup ID, and the second parameter includes a number of subgroups configured for the UE ID based subgrouping for LP-WUS.

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

[0139] Example 12 includes the method of any preceding example 8-11, wherein the first subgroup ID is indicated by first bits, wherein the second subgroup ID is indicated by second bits, and wherein either: first bits include the second bits and additional bits, or the second bits include the second bits and the additional bits.

[0140] Example 13 includes the method of any preceding example 8-12, further comprising: determining the first subgroup ID, or causing the first subgroup ID to be determined, based on a difference between a total number of subgroups configured per paging occasion (PO) for LP-WUS and a number of subgroups configured for the UE ID based subgrouping for LP-WUS.

[0141] Example 14 includes the method of any preceding example 1-2 or 7, wherein the first subgroup ID is different from the second subgroup ID, is uncorrelated with the second subgroup ID, and corresponds to the UE ID based subgrouping.

[0142] Example 15 includes the method of 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 unassociated with the second UE. [0143] Example 16 includes the method of any preceding example, 14-15, further comprising: determining the first subgroup ID, or causing the first subgroup ID to be determined, based on a first UE ID that is different from a second UE ID used in a determination of the second subgroup ID.

[0144] Example 17 includes the method of any preceding example, 14-16, further comprising: determining the first subgroup ID, or causing the first subgroup ID to be determined, based on a first formula that is different from a second formula used in a determination of the second subgroup ID.

[0145] Example 18 includes the method of any preceding example, 14-17, wherein the first subgroup ID is different from the second subgroup ID, is uncorrelated with the second subgroup ID, corresponds to the UE ID based subgrouping, and is determined based on a first part of a temporary mobile subscriber identity (TMSI) different from a second part of the TMSI, wherein the second part is used in a determination of the second subgroup ID.

[0146] Example 19 includes the method of of any preceding example, 14-18, wherein the first subgroup ID is different from the second subgroup ID, is uncorrelated with the second subgroup ID, corresponds to the UE ID based subgrouping, and is determined based on a difference between a total number of subgroups configured per paging occasion (PO) for LP- WUS and a number of subgroups configured for the UE ID based subgrouping for LP-WUS.

[0147] Example 20 includes a user equipment (UE) or an apparatus comprising: one or more processors; and one or more memory storing instructions that, upon execution by the one or more processors, configure the UE or the apparatus to perform a method described in or related to any of the preceding examples.

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

[0149] Example 22 includes an apparatus comprising means to perform one or more elements of a method described in or related to any of the preceding examples.

[0150] Example 23 includes one or more non-transitory computer-readable media comprising instructions to cause an apparatus, upon execution of the instructions by one or more processors of the apparatus, to perform one or more elements of a method described in or related to any of the preceding examples.

[0151] Example 24 includes an apparatus comprising logic, modules, or processing circuitry configured to perform one or more elements of a method described in or related to any of the preceding examples.

[0152] Example 25 includes an apparatus, a network, a base station, or a system comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of a method described in or related to any of the preceding examples.

[0153] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0154] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

CLAIMS What is claimed is:

1. 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 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 core network assigned subgrouping for LP-WUS or a user equipment (UE) ID based subgrouping for LP-WUS, the PEI configuration indicating a second subgroup ID; determining that a received LP-WUS indicates wake-up for the first subgroup ID; determining that a PEI indicates paging monitoring for the second subgroup ID, the PEI received based on the received LP-WUS indicating the first subgroup ID; and processing a paging occasion 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 a core network.

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

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 a 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 subgrouping, 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 set of parameters includes at least one of a total number of subgroups configured per paging occasion (PO) for LP-WUS or a number of subgroups configured for the UE ID based subgrouping for LP-WUS.

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

8. The method of claim 7, further comprising: determining the first subgroup ID based on a first parameter common to a determination of the second subgroup ID and a second parameter unused in the determination of the second subgroup ID.

9. The method of claim 8, wherein the first parameter includes a UE ID that is used in the determination of the second subgroup ID, and the second parameter includes a number of subgroups configured for the UE ID based sub grouping for LP-WUS.

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

11. The method of claim 7, wherein the first subgroup ID is indicated by first bits, wherein the second subgroup ID is indicated by second bits, and wherein either: first bits include the second bits and additional bits, or the second bits include the second bits and the additional bits.

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

13. An apparatus comprising: a receiver; a transmitter; and processing circuitry communicatively couple with the receiver and the transmitter and configured to: process configuration information indicating a low-power wake-up signal (LP- WUS) configuration and a paging early indication (PEI) configuration, the configuration information 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 core network assigned subgrouping for LP-WUS or a user equipment (UE) ID based subgrouping for LP-WUS, the PEI configuration indicating a second subgroup ID; determine that a received LP-WUS indicates wake-up for the first subgroup ID; determine that a PEI indicates paging monitoring for the second subgroup ID, the PEI received based on the received LP-WUS indicating the first subgroup ID; and process a paging occasion 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 uncorrelated with the second subgroup ID, and corresponds to the UE ID based subgrouping.

15. The apparatus of claim 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 unassociated with the second UE.

16. The apparatus of claim 14, wherein the processing circuitry is further configured to: determine the first subgroup ID based on a first UE ID that is different from a second

UE ID used in a determination of the second subgroup ID.

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

18. A method comprising: sending, to a UE, radio resource control (RRC) signaling indicating configuration information for 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 core network assigned sub grouping for LP-WUS or a user equipment (UE) ID based subgrouping for LP-WUS, the PEI configuration indicating a second subgroup ID; sending, to the UE, a LP-WUS that indicates wake-up for the first subgroup ID; sending, to the UE, a PEI that indicates paging monitoring for the second subgroup ID, the PEI sent based on the LP-WUS indicating the first subgroup ID; and scheduling a paging occasion for the UE 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 uncorrelated with the second subgroup ID, corresponds to the UE ID based subgrouping, and is determined based on a first part of a temporary mobile subscriber identity (TMSI) different from a second part of the TMSI, wherein the second part is used in a determination of the second subgroup ID.

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