Methods for LP-WUS and dynamic po configuration

Abstract

In some implementations, a wireless transmit / receive unit (WTRU) transmits an indication of a first wake-up delay value (WUDV) from a first set of candidate WUDVs, and receives a low-power wake-up signal (LP-WUS) configuration indicating a second set of one or more offset values. A first offset value in the second set is a time offset between a first LP-WUS occasion (LO) and a first reference paging occasion (PO). Based on at least one offset value in the second set being larger than or equal to the first WUDV, the WTRU receives an LP-WUS in a second LO determined based on a second offset value in the second set, and a paging downlink control information in a second reference PO based on the LP-WUS and a corresponding paging message. The second offset value is a smallest value in the second set that is larger than or equal to the first WUDV.

Description

METHODS FOR LP-WUS AND DYNAMIC PO CONFIGURATIONPRIORITY CLAIM AND CROSS-REFERENCE[oooi] This patent application claims priority to U.S. Provisional Application No. 63 / 574,584, filed on April 4, 2024 and entitled “METHODS ON LP-WUS AND DYNAMIC PO CONFIGURATION,” and U.S. Provisional Application No. 63 / 702,335, filed on October 2, 2024 and entitled “METHODS ON LP-WUS MONITORING CONFIGURATION,” which are hereby incorporated by reference herein as if reproduced in their entireties.TECHNICAL FIELD

[0002] The present disclosure relates generally to wireless communication, and in particular embodiments, to a system and method for low-power wake-up signal (LP- WUS) and paging occasion (PO) configuration.BACKGROUND

[0003] Wireless communication networks have evolved to support a w ide range of devices with varying power consumption requirements, particularly with the growth of Internet-of-Things (loT) devices that demand extended battery life. Traditional powersaving mechanisms such as Discontinuous Reception (DRX) and extended DRX (eDRX) allow user equipment (UE) to periodically turn off its receiver circuitry between scheduled monitoring occasions. These mechanisms enable the UE to conserve battery' power while still maintaining connectivity to the network, though they require the UE to wake up at predetermined intervals regardless of whether there is data to be received.

[0004] Recent advancements in receiver technology have explored various architectures for reducing power consumption in wireless devices. These include envelope detection-based architectures that can process simple modulation schemes like On-Off Keying (OOK), as well as linear detection-based architectures capable of handling more complex modulation schemes. These receiver architectures present different tradeoffs between power consumption, sensitivity, and complexity, with components such as RF / IF envelope detectors, low-noise amplifiers, filters, and analog -to-digital converters contributing to the overall power profile. While longer DRX and eDRX cycles provide greater power savings, they also increase the latency for network-initiated communications, creating a fundamental trade-off between power efficiency and responsiveness that network operators must carefully balance based on specific application requirements.SUMMARY

[0005] Technical advantages are generally achieved, by embodiments of this disclosure which describe methods, apparatus, and system for low-power wake-up signal (LP-WUS) and paging occasion (PO) configuration.

[0006] In accordance with implementations, a wireless transmit / receive unit (WTRU) transmits a first indication of a first wake-up delay value from a first set of candidate wake-up delay values. The WTRU receives a low-power wake-up signal (LP- WUS) configuration indicating a second set of one or more offset values. A first offset value in the second set is a time offset between a first LP-WUS occasion (LO) and a first reference paging occasion (PO). Based on at least one offset value in the second set being larger than or equal to the first wake-up delay value, the WTRU receives an LP-WUS in a second LO. The second LO is determined based on a second offset value in the second set. The second offset value is a smallest value in the second set that is larger than or equal to the first wake-up delay value. The WTRU receives a paging downlink control information (DCI) in a second reference PO based on the LP-WUS and a corresponding paging message.

[0007] In some implementations, the first set of candidate wake-up delay values includes wake-up delay values for transitioning from a low-power wake-up radio (LP- WUR) to a main radio of the WTRU.

[0008] In some implementations, receiving the LP-WUS in the second LO includes receiving the LP-WUS in one or more LP-WUS monitoring occasions (MOs) of the second LO.

[0009] In some implementations, the WTRU receives a paging configuration indicating a configured paging frame (PF) offset, a first default paging cycle, and a first user equipment (UE)-specific paging cycle.

[0010] In some implementations, the WTRU determines the first reference PO based on the paging configuration.

[0011] In some implementations, the WTRU determines the second LO and one or more LP-WUS MOs of the second LO based on the second offset value in the second set.

[0012] In some implementations, the first offset value in the second set is a time offset between an end of the first LO and a start of the first reference PO.

[0013] In some implementations, the end of the first LO is an end of a last LP-WUS MO in the first LO.

[0014] In some implementations, the WTRU determines an ithoffset value 0, of the one or more offset values in the second set based on a minimum time offset To, a second UE-specific paging cycle Tspec, and an integer multiple value specific to an ittloffset Ntaccording to 0(= 7 / + NiTspec.

[0015] In some implementations, the first offset value is a largest offset value in the second set.

[0016] In some implementations, the second reference PO is the same as the first reference PO, and the second LO is further determined based on the second offset value and the first reference PO, the second offset value being different from the first offset value.

[0017] In some implementations, the second LO is the same as the first LO, and the second reference PO is further determined based on the second offset value and the first LO, the second offset value being different from the first offset value.

[0018] In some implementations, the first reference PO is a default reference PO, and the second reference PO is a UE-specific reference PO.

[0019] In some implementations, the WTRU determines the second LO is based on at least one offset value in the second set being larger than or equal to the first wake-up delay value.

[0020] In some implementations, before the transmitting the first indication of the first wake-up delay value, the WTRU transmits a second indication of a second wake-up delay value from the first set of candidate wake-up delay values. In some implementations, the WTRU receives a second LP-WUS configuration indicating a third set of one or more offset values. A third offset value in the third set is a time offset between a third LO and a third PO. In some implementations, in response to the one or more offset values in the third set all being smaller than the second wake-up delay value, the WTRU skipps LP-WUS monitoring corresponding to the second LP-WUS configuration and monitoring POs according to the paging configuration. The first wakeup delay value is less than the second wake-up delay value.

[0021] In some implementations, the second wake-up delay value is smaller than or equal to at least one offset value from the one or more offset values in the second set.

[0022] In accordance with implementations, a wireless transmit / receive unit(WTRU) receives a low-power wake-up signal (LP-WUS) configuration, the LP-WUS configuration indicating an LP-WUS monitoring occasion (MO) configuration and a cutoff reference point for paging occasion (PO) monitoring. The WTRU receives a first LP-WUS in a first LP-WUS MO based on the LP-WUS MO configuration. The WTRU receives a paging downlink control information (DCI) in a paging occasion (PO) and a corresponding paging message, in accordance to the first LP-WUS MO occurring before the cutoff reference point for the PO monitoring.

[0023] In some implementations, the LP-WUS MO configuration is part of an LP- WUS occasion (LO) configuration indicating at least one of a reference point, an LO periodicity, one or more offsets from the reference point to one or more initial LP-WUSMOs, a time gap between consecutive LP-WUS MOs in an LP-WUS MO group, a number of the LP-WUS MO groups in the LO, or a periodicity for LP-WUS MO groups in the LO.

[0024] In some implementations, the PO is received outside any of a paging time window (PTW) or an ON period of a default configured idle mode discontinuous reception (I-DRX) cycle.

[0025] In some implementations, the paging DCI has a cyclic redundancy check (CRC) that is scrambled with one of a paging radio network temporaiy identifier (P- RNTI) or an alternative paging RNTI (AP-RNTI).

[0026] In some implementations, the CRC is scrambled with the AP-RNTI, and the AP-RNTI is for user equipment (UE) supporting the PO monitoring.

[0027] In some implementations, the first LP-WUS MO occurring before the cutoff reference point is determined based on a first radio frame number of the first LP-WUS MO being less than a radio frame number corresponding to the cutoff reference point.

[0028] In some implementations, the WTRU transmits a physical random access channel (PRACH) preamble based on the paging DCI and the corresponding paging message.

[0029] In some implementations, the WTRU transmits the PRACH preamble is in response to detection of the WTRU configured or assigned identifier in the corresponding paging message.

[0030] In some implementations, the WTRU receives a second LP-WUS in a second LP-WUS MO based on the LP-WUS MO configuration, and receives a second paging DCI in a legacy PO and a second corresponding paging message, in accordance to the second LP-WUS MO occurring after the cutoff reference point for the PO monitoring.

[0031] In some implementations, the legacy PO is received inside one of a paging time window (PTW) and an ON period of a default configured I-DRX cycle.

[0032] In some implementations, the second LP-WUS MO occurring after the cutoff reference point is determined based on a second radio frame number of the second LP- WUS MO being greater than a radio frame number corresponding to the cutoff reference point.

[0033] In some implementations, the paging DCI has a CRC that is scrambled with a P-RNTI.

[0034] In some implementations, the WTRU transmits a PRACH preamble based on the paging DCI and the corresponding paging message.

[0035] In some implementations, the WTRU transmits the PRACH preamble is in response to detection of the WTRU configured or assigned identifier in the corresponding paging message.

[0036] In accordance w ith implementations, one or more network-side devices receive a first indication of a first wake-up delay value from a first set of candidate wakeup delay values. The one or more network-side devices transmit a low-power wake-up signal (LP-WUS) configuration indicating a second set of one or more offset values. A first offset value in the second set is a time offset between a first LP-WUS occasion (LO) and a first reference paging occasion (PO). Based on at least one offset value in the second set being larger than or equal to the first wake-up delay value, the one or more network-side devices transmit an LP-WUS in a second LO. The second LO is determined based on a second offset value in the second set. The second offset value is a smallest value in the second set that is larger than or equal to the first wake-up delay value. The one or more network-side devices transmit a paging downlink control information (DCI) in a second reference PO based on the LP-WUS and a corresponding paging message.

[0037] In some implementations, the first set of candidate wake-up delay values include wake-up delay values for transitioning from a low-power wake-up radio (LP- WUR) to a main radio of a user equipment.

[0038] In some implementations, transmitting the LP-WUS in the second LO includes transmitting the LP-WUS in one or more LP-WUS monitoring occasions (MOs) of the second LO.

[0039] In some implementations, the one or more network-side devices transmit a paging configuration indicating a configured paging frame (PF) offset, a first default paging cycle, and a first user equipment (UE)-specific paging cycle.

[0040] In some implementations, the first offset value in the second set is a time offset between an end of the first LO and a start of the first reference PO.

[0041] In some implementations, the end of the first LO is an end of a last LP-WUS MO in the first LO.

[0042] In some implementations, the first offset value is a largest offset value in the second set.

[0043] In some implementations, the first reference PO is a default reference PO, and the second reference PO is a UE-specific reference PO.

[0044] In some implementations, before the receiving the first indication of the first wake-up delay value, the one or more network-side devices receive a second indication of a second wake-up delay value from the first set of candidate wake-up delay values, and transmit second LP-WUS configuration indicating a third set of one or more offset values. A third offset value in the third set is a time offset between a third LO and a third PO.

[0045] In some implementations, the second wake-up delay value is smaller than or equal to at least one offset value from the one or more offset values in the second set.

[0046] In some implementations, the one or more network-side devices include one or more base stations, one or more intermediate nodes, or one or more assist nodes.

[0047] In some implementations, the one or more network-side devices include a single base station.

[0048] In accordance with implementations, one or more network-side devices transmit a low-power wake-up signal (LP-WUS) configuration, the LP-WUS configuration indicating an LP-WUS monitoring occasion (MO) configuration and a cutoff reference point for paging occasion (PO) monitoring. The one or more networkside devices transmit a first LP-WUS in a first LP-WUS MO based on the LP-WUS MO configuration. The one or more network-side devices transmit a paging downlink control information (DCI) in a paging occasion (PO) and a corresponding paging message, in accordance to the first LP-WUS MO occurring before the cutoff reference point for the PO monitoring.

[0049] In some implementations, the LP-WUS MO configuration is part of an LP- WUS occasion (LO) configuration indicating at least one of a reference point, an LO periodicity, one or more offsets from the reference point to one or more initial LP-WUS MOs, a time gap between consecutive LP-WUS MOs in an LP-WUS MO group, a number of the LP-WUS MO groups in the LO, or a periodicity for LP-WUS MO groups in the LO.

[0050] In some implementations, the PO is transmitted outside any of a paging time window^ (PTW) or an ON period of a default configured idle mode discontinuous reception (I-DRX) cycle.

[0051] In some implementations, the paging DCI has a cyclic redundancy check (CRC) that is scrambled with one of a paging radio network temporary identifier (P- RNTI) or an alternative paging RNTI (AP-RNTI).

[0052] In some implementations, the CRC is scrambled with the AP-RNTI, and the AP-RNTI is for user equipment (UE) supporting the PO monitoring.

[0053] In some implementations, the first LP-WUS MO occurring before the cutoff reference point is determined based on a first radio frame number of the first LP-WUS MO being less than a radio frame number corresponding to the cutoff reference point.

[0054] In some implementations, the one or more network-side devices receive a physical random access channel (PRACH) preamble based on the paging DCI and the corresponding paging message.

[0055] In some implementations, the one or more network-side devices transmit a second LP-WUS in a second LP-WUS MO based on the LP-WUS MO configuration, and transmit a second paging DCI in a legacy PO and a second corresponding paging message, in accordance to the second LP-WUS MO occurring after the cutoff reference point for the PO monitoring.

[0056] In some implementations, the legacy PO is transmitted inside one of a paging time w indow (PTW) and an ON period of a default configured I-DRX cycle.

[0057] In some implementations, the second LP-WUS MO occurring after the cutoff reference point is determined based on a second radio frame number of the second LP- WUS MO being greater than a radio frame number corresponding to the cutoff reference point.

[0058] In some implementations, the paging DCI has a CRC that is scrambled with a P-RNTI.

[0059] In some implementations, the one or more network-side devices receive a PRACH preamble based on the paging DCI and the corresponding paging message.

[0060] In some implementations, the one or more network-side devices include one or more base stations, one or more intermediate nodes, or one or more assist nodes.

[0061] In some implementations, the one or more network-side devices include a single base station.BRIEF DESCRIPTION OF THE DRAWINGS

[0062] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now7made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0063] Figure 1 illustrates a schematic view of a wireless system, in accordance with some embodiments;

[0064] Figure 2 illustrates an example protocol flow / timeline based onDiscontinuous Reception (DRX) configuration, in accordance with some embodiments;

[0065] Figure 3 illustrates an example protocol flow / timeline based on extendedDiscontinuous Reception (eDRX) configuration, in accordance with some embodiments;

[0066] Figure 4 illustrates an example protocol flow / timeline based on low-power wake up signal (LP-WUS) configuration with UE addressing, in accordance with some embodiments;

[0067] Figure 5 illustrates an example protocol flow / timeline based on LP-WUS configuration with UE group addressing, in accordance with some embodiments;

[0068] Figure 6 illustrates a block diagram for an RF envelope detection receiver architecture, in accordance with some embodiments;

[0069] Figure 7 illustrates a block diagram for an IF envelope detection receiver architecture, in accordance with some embodiments;

[0070] Figure 8 illustrates a block diagram for a BB envelope detection receiver architecture, in accordance with some embodiments;

[0071] Figure 9 illustrates a block diagram for a Linear detection receiver architecture, in accordance with some embodiments;

[0072] Figure 10 illustrates a block diagram for a baseband sequence detector, in accordance w ith some embodiments;

[0073] Figures 11A and 11B are example illustrations of LO and LP-WUS MO configuration options, in accordance with some embodiments;

[0074] Figures 12A-12C are example illustrations of LO configuration and monitoring with eDRX and Dynamic PO, in accordance with some embodiments;

[0075] Figure 13 is an example illustration of LO configuration and monitoring with I-DRX and Dynamic PO, in accordance w ith some embodiments;

[0076] Figures 14A-14D are example illustration of LO reference point(s) and reference PF(s) options / alternatives for single and multiple configured offset values, in accordance with some embodiments;

[0077] Figures 15A-15C are examples of bitmap-based subgroup wake-up indication options for large number of subgroups assuming two subsets of the subgroups, in accordance w ith some embodiments;

[0078] Figures 16A and 16B are illustrations of bitmap-based and ID-based subgroup wake-up indication switching, in accordance with some embodiments;

[0079] Figure 17A is an exemplary flow chart of a method for UE’s switching between Dynamic and legacy PO monitoring based on LP-WUS detection and a dynamic PO cutoff reference, in accordance with some embodiments;

[0080] Figure 17B is an exemplary sequence diagram of a method for UE’s switching between Dynamic and legacy PO monitoring based on LP-WUS detection and a dynamic PO cutoff reference, in accordance with some embodiments;

[0081] Figure 18 is an exemplary flow chart of a method for UE’s switching betweenID-based and bitmap-based subgroup ID detection in an LP-WUS based on preambles, in accordance with some embodiments;

[0082] Figure 19A is an exemplary flow chart of a method for UE’s wake-up delay reporting and procedure upon receiving LO / PO offset values, in accordance with some embodiments;

[0083] Figure 19B is an exemplary sequence diagram of a method for UE’s wake-up delay reporting and procedure upon receiving LO / PO offset values, in accordance with some embodiments;

[0084] Figure 20 is an exemplary flow chart of a method for UE’s wake-up delay reporting and procedure for LO reference point and reference PO / PF determination, in accordance with some embodiments;

[0085] FIG. 21 illustrates an example communications system, in accordance with some embodiments;

[0086] FIG. 22 illustrates an example communication system, in accordance with some embodiments;

[0087] FIGS. 23A and 23B illustrate example devices, in accordance with some embodiments; and

[0088] FIG. 24 shows a block diagram of a computing system, in accordance with some embodiments.

[0089] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated. The figures are drawn to clearly illustrate the relevant aspects of the embodiments and are not necessarily draw n to scale.DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0090] The making and using of embodiments of this disclosure are discussed in detail below. It should be appreciated, however, that the concepts disclosed herein can be embodied in a wide variety of specific contexts, and that the specific embodiments discussed herein are merely illustrative and do not serve to limit the scope of the claims. Further, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of this disclosure as defined by the appended claims.

[0091] A 3GPP study on low -power wake-up signal (LP-WUS) and receiver (LP-WUR) for New Radio (NR) w as performed. The study covered low-power receiver architectures, signal and protocol design, and evaluation methodology targeting metrics such as power saving gain, latency, coverage availability, coexistence with non-low-power Wake-Up Receiver (WUR) User Equipment (UEs), and network resource overhead. Several receiver architectures, supporting On-Off Keying (OOK) modulation scheme, were agreed and analyzed including architectures with RF envelope detection, heterodyne architecture with IF envelope detection, and homodyne / zero-Intermediate Frequency (IF) architecture with baseband (BB) envelope detection. Another receiver architecture suitable for the reception of Orthogonal Frequency Division Multiple Access (OFDMA)-based signals / channels with reduced power consumption was also agreed.

[0092] The concept of dynamic paging occasion (PO) was proposed and evaluated where a UE may monitor a PO outside of the on duration in a configured duty cycle for UEs with Idle mode Discontinuous Reception (I-DRX) or Extended Discontinuous Reception (eDRX) configuration. The dynamic PO configuration was observed to help improve the paging latency while still providing power saving gain.

[0093] With the conclusion of discussions and evaluations of waveforms and procedures, a work item on Low- Power Wake-Up Signal (LP-WUS) started in 3GPP NR Release 19 with focus on harmonized OOK and OFDM waveform generation, specification of Idle / Inactive modes procedures and configuration for LP-WUS, as well as specification of Connected mode procedures to allow UE Main Radio (MR) Physical Downlink Control Channel (PDCCH) monitoring triggered by LP-WUS.

[0094] The present disclosure provides embodiments for the configuration and procedures of LP-WUS monitoring in RRC Idle / lnactive modes. Some embodiments support Dynamic PO monitoring and enable the support of a large number of paging subgroups with limited impact on LP-WUS coverage and / or resource utilization. Some embodiments can guarantee or improve the power saving gain experienced by LP-WUS monitoring.

[0095] An overview of UE procedures related to power saving in RRC Idle / Inactive states is provided. Then, overviews of LP-WUR architectures and LP-WUS waveform options as discussed in 3GPP RAN1 working group meetings are presented in the latter sections of the application.

[0096] Embodiments of the disclosure provide systems and methods for low-power wake-up signal (LP-WUS) monitoring configuration in wireless communication networks. The LP-WUS approach enables wireless devices to remain in deep sleep or ultra-deep sleep states while using a low-power wake-up receiver (LP-WUR) to monitor for wake-up signals, thereby significantly reducing power consumption. In various embodiments, a wireless device may have multiple power states including a deep sleep state and an ultra-deep sleep state, with the LP-WUR consuming 2-3 orders of magnitude less power than the main radio (MR).

[0097] In one or more embodiments, the system defines LP-WUS occasions (LOs) and LP-WUS monitoring occasions (MOs) that a device can use to efficiently monitor for wake-up signals. The LO configuration may include reference points, offsets, periodicities, and associations with paging occasions (POs) to optimize both power consumption and latency. In various embodiments, the system supports dynamic PO monitoring that allows devices to monitor POs outside of scheduled windows upon receiving an LP-WUS, which can reduce paging latency by 96-98% while still providing significant power savings.

[0098] In an embodiment, a device may report its wake-up delay capabilities, allowing the network to configure appropriate offsets between LOs and reference POs. This approach accommodates different sleep states with varying wake-up times, from deep sleep (io-2oms) to ultra-deep sleep (4oo-8ooms). In various embodiments, the system supports large numbers of paging subgroups with limited impact on coverage and resource utilization through bitmap-based or ID-based subgroup indication methods, with options for subgroup subsets and format switching based on preamble detection.

[0099] The embodiments provide significant advantages over conventional DRX and eDRX approaches by enabling devices to remain in lower power states for longer periods while still maintaining acceptable latency. The LP-WUS design addresses challenges related to timing errors, frequency errors, and false alarms that could otherwise negate power saving benefits. These and additional details are further discussed below.

[0100] Figure 1 illustrates a schematic view of a wireless communication system too, in accordance with some embodiments. The wireless communication system too includes a base station 102 and a User Equipment (UE) 120, which communicate with each other through wireless signals.[oioi] The base station 102 includes a transmitter 104 that is responsible for sending signals to the UE 114. The transmitter 104 may comprise a multiple signal processing components, such as a regular signal encoding and modulation component 106, an LP-WUS signal encoding and modulation component 108, and a conversion to RF, amplification and filtering block 110. These components prepare different types of signals for transmission. In some embodiments, outputs from the regular signal encoding and modulation component 106 and the LP-WUS signal encoding and modulation component 108 are fed into the conversion to RF, amplification and filtering block 110, which prepares the signals for wireless transmission through an antenna 112.

[0102] On the receiving side, in some embodiments, the UE 114 includes two distinct radio components: a main radio (MR) 116 and a low-power wake-up radio (LP- WUR) 118, both connected to an antenna 129. The MR 116 is a conventional receiver that processes regular communication signals but consumes significant power. The LP-WUR 118 is a specialized receiver designed to detect LP-WUS with minimal power consumption.

[0103] In operation, the base station 102 can transmit both regular communication signals (processed by the regular signal encoding and modulation component 106) and low-power wake-up signals (processed by the LP-WUS signal encoding and modulation component 108). During periods when the UE 120 is in a sleep state to conserve power, the MR 116 can be powered down while the LP-WUR 118 remains active, consuming minimal power while monitoring for LP-WUS. When the LP-WUR 118 detects an LP- WUS addressed to the UE 114, it triggers the MR 116 to power up and process subsequent regular communication signals.

[0104] This architecture enables significant power savings in the UE 114 by allowing the MR 116 to remain in a sleep state for extended periods, with only the LP-WUR 118 actively monitoring for potential communications. The wireless communication system too provides an efficient mechanism for balancing power consumption and communication latency in wireless networks.Power saving in RRC IDLE / INACTIVE states

[0105] In some embodiments, a UE can support three Radio Resource Control (RRC) states: RRC_CONNECTED, RRC_IDLE, and RRC_INACTIVE. Further, the UE may’ have several sleep states including deep sleep and ultra-deep sleep states where the power consumption can be lower in the ultra-deep sleep state compared to the deep sleep state. The UE procedures related to power saving in RRC_IDLE / NACTIVE are available in existing 3GPP NR specifications and as discussed in Release 18 study item on LP- WUS.

[0106] In 3GPP, duty-cycled operations in the form of Discontinuous Reception (DRX) and extended Discontinuous Reception (eDRX) are defined for power consumption reduction in NR RRC_IDLE and RRC_INACTIVE states through the reduction of the number of Paging Occasions (POs) monitored by the UE. Further power consumption reduction is achieved through Paging Early Indication (PEI) in NR RRC_IDLE and RRC_INACTIVE states, which is still subject to the duty-cycled operation. Similar power saving techniques are defined for NR RRC_CONNECTED state in the form of connected mode DRX (C-DRX) and Wake-Up Signal (WUS). In some embodiments, both PEI and WUS can be received by UEs as Downlink Control Information (DCIs) over the Physical Downlink Control Channel (PDCCH).

[0107] Figure 2 illustrates an example protocol flow / timeline based onDiscontinuous Reception (DRX) configuration, in accordance with some embodiments. The vertical axis of Figure 2 represents the power profile levels of the UE, while the horizontal axis represents time progression. Figure 2 shows a plurality of PEI occasions (PEI -Os) and / or POs 202 separated by deep sleep intervals 212. The plurality of PEI-Os and / or POs 202 include PEI-Os and / or POs 202A, which represent POs not addressed to the UE, and PEI-Os and / or POs 202B, which represent POs that are addressed to the UE.

[0108] For a UE using DRX in the RRC_IDLE or RRC_INACTIVE state, the UE monitors one PEI occasion (PEI-O) and / or one PO 202 per DRX cycle 204 based on PEI configuration, where a PEI-O / PO 202 consists of a set of PDCCH monitoring occasions (MOs) and can consist of multiple time slots. The UE initiates RRC Connection Establishment or RRC Connection Resume procedures 206 upon reception of a Core Network (CN) initiated or a Radio Access Network (RAN) initiated paging, respectively. The CN initiated and RAN initiated paging may be also referred to as a network event 208. If a PEI is configured, the UE monitors an associated PO 202B in a DRX cycle 204 only if a PEI is detected and the UE’s corresponding subgroup is indicated in the PEI. In some embodiments, each PO 202B is associated with a group of UEs, based on their identifiers (IDs), and that a PEI is used to further address subgroups of the UEs that belong to that group, where the subgrouping can be based on UEs’ IDs or assigned by the network. A time interval LDRX210 denotes the latency from an arrival of the network event 208 at the network to UE’s monitoring of the PO 202B.

[0109] Figure 2 effectively demonstrates how the DRX mechanism works in cellular networks where a UE periodically wakes up to check for paging messages at specific intervals (POs) 202 while remaining in a power-saving sleep state between these occasions. The DRX configuration helps conserve battery power by reducing the frequency of wake-up periods while still ensuring the UE can receive incoming communications.[ono] Figure 3 illustrates an example protocol flow / timeline based on extended Discontinuous Reception (eDRX) configuration, in accordance with some embodiments. The vertical axis of Figure 3 represents the power profile levels of the UE, while the horizontal axis represents time progression. Figure 3 shows a plurality of PEI-Os and / or POs 302 separated by deep sleep intervals 312. Furthermore, groups of PEI-Os and / or POs 302 are separated from other groups of PEI-Os and / or POs 302 by ultra-deep sleep intervals 318. The plurality of PEI-Os and / or POs 302 include PEI-Os and / or POs 302A, which represent POs not addressed to the UE, and PEI-Os and / or POs 302B, which represent POs that are addressed to the UE. Power state transitions 314 indicate power transitions of the UE to / from low power and high power states.

[0111] For a UE using eDRX in RRC_IDLE or RRC_INACTIVE states, the UE monitors one PEI-0 and / or one PO 302 per eDRX cycle 316, based on PEI configuration, as shown in Figure 2 if the configured eDRX cycle 316 is not longer than 1024 radio frames, where the DRX cycle 204 in Error! Reference source not found, becomes the eDRX cycle 316. Otherwise, the UE monitors one PEI-0 and / or one PO 302 per eDRX cycle 316, based on PEI configuration, according to a configured DRX cy cle 304 during a UE -specific and periodic Paging Time Window7(PTW), where the PTW period is determined by the eDRX cycle 316 and the length is configured by upper layers. A time interv al LeDRX310 denotes a latency from an arrival of network event 308 at the network to the UE’s monitoring of a PO 303B. The UE initiates RRC Connection Establishment or RRC Connection Resume procedures 306 upon reception of a CN initiated or RAN initiated paging, respectively. If PEI is configured, the UE monitors an associated PO 303B in a DRX / eDRX cycle if the PEI is detected and the UE’s corresponding subgroup is indicated in the PEI.

[0112] The DRX, eDRX, and C-DRX can provide more power saving gain by increasing the duty cycle duration at the expense of higher latency. In other embodiments, PEI and WUS can provide more power saving gain without an impact on latency, but the gain is limited by the power consumption required to decode a DCI over PDCCH. A new WUS that can be received with significantly lower power consumption than existing PEI / WUS designs may enable new trade-off regions of Latency versus Power but will need a dedicated Low-Power Wake-Up Radio / Receiver (LP-WUR).

[0113] The benefit for using the LP-WUR (e.g., LP-WUR 118 of Figure 1) is to let the MR (e.g., MR 116 of Figure 1), which can consume significant amount of power in range of milliwatts (mWs), stay in a sleep power state for as long as possible and have the LP- WUR, which should consume 2-3 orders of magnitude less power than the MR, monitor for a LP-WUS that acts as a trigger for the MR to wake-up. In some embodiments, there are two options for how the LP-WUR may monitor a LP-WUS and the followingterminology can be used interchangeably to identify each option. “Option 1” can be identified as “Continuous” and “Always-on” monitoring and “Option 2” can be identified as “Discontinuous”, “Periodic”, and “Duty-Cycled” monitoring.

[0114] Further, there may be three different choices for the behavior of a UE (e.g.,UE 114 of Figure 1) in response to the reception of a LP-WUS depending on the content of the LP-WUS and network configuration. In some embodiments, three UE behavior choices, which may be applicable to both LP-WUS monitoring “Option 1” and “Option 2”, are

[0115] UE_Behavior (1): LP-WUS carries a UE ID, and the MR may not be required to monitor the POs;

[0116] UE_Behavior (2): LP-WUS carries a UE ID and / or a UE group ID, and the MR may be required to monitor legacy POs / PFs; and

[0117] UE_Behavior (3): LP-WUS carries a UE ID and / or a UE group ID, and the MR may be required to monitor newly defined POs / PFs.

[0118] Figure 4 illustrates an example protocol flow / timeline based on LP-WUS configuration with UE addressing according to UE_Behavior (1), in accordance with some embodiments. The vertical axis represents the power profile of a UE (e.g., UE 114 of Figure 1), while the horizontal axis represents time progression. In the illustrated embodiment, the LP-WUS 420 carries a UE ID and the main radio (MR) may not be required to monitor the POs. The UE (e.g., UE 114 of Figure 1) initiates RRC Connection Establishment or RRC Connection Resume procedures 406 upon reception of a CN initiated or RAN initiated paging (e.g., based on network event 408), respectively. A time interval LWUR410 denotes a latency from an arrival of a network event 408 at the network to the UE’s transmission of a PRACH on a RO 402. A time interval D 422 denotes a latency from an arrival of LP-WUS 420 at the network to the UE’s transmission of a PRACH on a RO 402. Power state transitions 414 represent the transition of the UE (e.g., network event 408) from a deep sleep or ultra-deep sleep state to an active state upon receiving the LP-WUS 420. This transition period affects the overall latency and power consumption of the system.

[0119] In some embodiments, UE_Behavior (1) may result in the best experienced latency under LP-WUS power saving scheme, especially when continuous monitoring mode (Option 1) is used. This is due to the fact that the UE / LP-WUR may wake-up the MR (e.g., MR 116 of Figure 1) to directly initiate RRC Connection Establishment or RRC Connection Resume procedures upon reception of a CN-initiated or RAN-initiated paging (e.g., network event 408), respectively, as indicated by the LP-WUS 420. This UE behavior also eliminates the need to align the LP-WUR (e.g., LP-WUR 118 of Figure 1) and MR (e.g., MR 116 of Figure 1) duty cycles when periodic LP-WUS monitoring isconsidered. However, this may come at the cost of a large LP-WUS payload size and subsequently a potentially high resource overhead requirement, as the LP-WUS 420 need to carry the full UE ID information.

[0120] The illustrated embodiment demonstrates how the LP-WUS with UE addressing can provide significant improvements in latency compared to traditional DRX or eDRX mechanisms, as the UE (e.g., UE 114 of Figure 1) can respond directly to the wake-up signal without needing to wait for and check specific paging occasions. This approach allows the MR (e.g., MR 116 of Figure 1) to remain in deep sleep for longer periods, while the LP-WUR (e.g., LP-WUR 118 of Figure 1) monitors for specific signals addressed to the UE (e.g., UE 114 of Figure 1), resulting in substantial power savings.

[0121] Figure 5 illustrates an example protocol flow / timeline based on LP-WUS configuration with UE group addressing according to UE_Behavior (1), in accordance with some embodiments. The vertical axis represents the pow er profile of the UE (e.g., UE 114 of Figure 1), while the horizontal axis represents time progression. In the illustrated embodiment, the LP-WUS 520 carries a UE ID and / or a UE group ID, and the MR (e.g., MR 116 of Figure 1) may be required to monitor legacy POs 502. POs 502A represent POs not addressed to the UE (e.g., UE 114 of Figure 1) and POs 502B represent POs that are addressed to the UE (e.g., UE 114 of Figure 1). The UE (e.g., UE 114 of Figure 1) initiates RRC Connection Establishment or RRC Connection Resume procedures 506 upon reception of a CN initiated or RAN initiated paging (e.g., based on network event 508), respectively. A time interval D 522 denotes a latency from an arrival of LP-WUS 520 at the network to the UE’s monitoring of a PO 502B. Power state transitions 514 represent the transition of the UE (e.g., network event 508) from a deep sleep or ultradeep sleep state to an active state upon receiving the LP-WUS 520. This transition period affects the overall latency and power consumption of the system.

[0122] The illustrated embodiment results in an LP-WUS latency performance that is limited by the legacy DRX cycle 504 and may underperform the DRX power saving scheme (with the same DRX cycle configuration) in terms of latency as described above with reference to Figure 2. This is due to the fact that the UE (e.g., UE 114 of Figure 1) will still have to monitor POs using the MR (e.g., MR 116 of Figure 1) upon wake-up in response to the detection of an LP-WUS 520. However, power saving gain is still expected compared to DRX (see Figure 2), depending on the UE group size, and managed LP-WUS resource overhead is possible due to the potential of using UE group IDs instead of UE unique IDs. In some embodiments, the DRX cycle 504 may be greater than or equal to 0.32 seconds, such as 0.32 seconds, 0.64 seconds, 1.28 seconds, or 2.56 seconds.

[0123] The illustrated embodiment demonstrates how the LP-WUS with UE group addressing provides a balance between resource efficiency and latency. By using group addressing rather than individual UE addressing, the system can reduce the LP-WUS payload size and resource overhead, while still providing significant power savings compared to traditional DRX mechanisms. However, this may come at the cost of slightly increased latency compared to the UE_Behavior (1) approach shown in Figure 4, as the UE (e.g., UE 114 of Figure 1) still needs to monitor legacy POs after receiving the LP- WUS.

[0124] UE_Behavior (3) may correspond to the definition of shorter RRC IDLE / INACTIVE state DRX cycles (e.g., less than 320 ms) which may result in a better LP-WUS latency performance compared to UE_Behavior (2) (see Figure 5) without any impact on power consumption due to the use of LP-WUR and a managed LP-WUS resource overhead due to the use of UE group IDs.LP-WUR architectures

[0125] Two categories of LP-WUR architectures were considered in Release 18 LP- WUS SI: (1) envelope detection based architectures, and (2) linear detection based architectures. Envelope detection based architectures can be used to receive simple modulation schemes such as On-Off Keying (OOK) or Frequency Shift Keying (FSK), i.e., w hen receive parallel branches are used. The envelope detection based receiver architectures are divided into RF envelope detection and IF / BB envelope detection architectures.

[0126] Figure 6 illustrates a block diagram for an RF envelope detection receiver architecture 600, in accordance with some embodiments. In this architecture, an RF signal (e.g., LP-WUS) is received by an antenna 602 and is converted directly into baseband (BB) using an RF envelope detector 610. This direct conversion eliminates the need for local oscillators (LOs) or Phase-Locked Loops (PLLs), which helps reduce powder consumption significantly.

[0127] In some embodiments, the signal path begins with the antenna 602 connected to a high-Q matching network 604, which optimizes signal transfer and impedance matching. The signal then passes through an RF bandpass filter (BPF) 606, which helps filter out unwanted signals outside the frequency band of interest. After filtering, the signal can optionally go through an RF Low’ Noise Amplifier (LNA) 608, which amplifies the weak received signal while adding minimal noise. The amplified RF signal then enters the RF envelope detector 610, w hich performs direct conversion from RF to baseband by extracting the envelope of the RF signal. Following envelope detection, the baseband signal may be further amplified by an optional BB Amplifier(AMP) 612. The signal then passes through a BB low pass filter (LPF) 614 to remove high-frequency components and further suppress adjacent channel interference or interference from legacy NR signals and / or other LP-WUS on adjacent subcarriers. For digital processing, the filtered baseband signal is digitized using a 1-bit or multi-bit analog-to-digital converter (ADC) 616. The digitized signal is then processed by digital baseband processing circuits 618, which perform detection and decoding of the LP-WUS information.

[0128] Figure 7 illustrates a block diagram for an Intermediate Frequency (IF) envelope detection receiver architecture 700, in accordance w ith some embodiments. In this architecture, an RF signal (e.g., LP-WUS) received by an antenna 702 is first converted to an IF signal before being converted to baseband, unlike the direct RF-to- baseband conversion in Figure 6. This approach offers certain advantages in terms of selectivity and interference rejection.

[0129] In some embodiments, the signal path begins with the antenna 702 connected to a high-Q matching network 704, w hich optimizes signal transfer and impedance matching. The signal then passes through a RF BPF 706, which helps filter out unwanted signals outside the frequency band of interest. After filtering, the signal can optionally go through an RF LNA 708, which amplifies the weak received signal while adding minimal noise. The amplified RF signal is then mixed with a local oscillator (LO) 722 signal using an RF mixer 720 to convert it to an IF signal. The IF signal passes through an IF BPF 726 to remove unwanted mixing products and adjacent channel interference. The filtered IF signal may be further amplified by an optional IF AMP 724. Following IF filtering and amplification, the signal enters the IF envelope detector 728, which converts the IF signal to a baseband signal by extracting the envelope of the IF signal. The baseband signal may be further amplified by an optional BB AMP 712 and filtered by a BB LPF 714. For digital processing, the filtered baseband signal is digitized using a 1-bit or multi-bit ADC 716. The digitized signal is then processed by digital baseband processing circuits 718, which perform detection and decoding of the LP-WUS information.

[0130] In this architecture, low power consumption is achieved by relaxing the accuracy and stability requirements of the LO 722. The high-Q matching network 704, RF BPF 706, and / or IF BPF 726 are used to suppress adjacent channel interference or interference from legacy NR signals and / or other LP-WUS on adjacent subcarriers. In some embodiments, an image rejection filter or an image rejection mixer may be needed in this architecture to reject the image frequency component that results from the mixing process.

[0131] This IF envelope detection architecture provides a balance between performance and power consumption, offering better selectivity than direct RF envelope detection while still maintaining relatively low power consumption compared to conventional receivers, making it suitable for LP-WUS applications in power-constrained devices.

[0132] Figure 8 illustrates a block diagram for a BB envelope detection receiver architecture 800, in accordance with some embodiments. In this architecture, an RF signal (e.g., LP-WUS) received by an antenna 802 is directly converted to a baseband signal using a LO 822 and an RF mixer 820, in a direct conversion or zero-IF approach. This differs from the IF envelope detection architecture in Figure 7, which uses an intermediate frequency stage.

[0133] In some embodiments, the signal path begins w ith the antenna 802 connected to a high-Q matching network 804, which optimizes signal transfer and impedance matching. The signal then passes through an RF BPF 806, which helps filter out unwanted signals outside the frequency band of interest. After filtering, the signal can optionally go through an RF LNA 808, which amplifies the weak received signal while adding minimal noise. The amplified RF signal is then mixed with the LO 822 signal using the RF mixer 820 to directly convert it to a baseband signal. The baseband signal may be further amplified by an optional BB AMP 812 and filtered by a BB BPF / LPF 830 to remove unwanted mixing products and adjacent channel interference. For digital processing, the filtered baseband signal is digitized using a 1-bit or multi-bit ADC 816. The digitized signal is then processed by digital baseband processing circuits 818, which perform detection and decoding of the LP-WUS information.

[0134] In some embodiments, a high-Q matching network 804, an RF BPF 806, and a BB BPF / LPF 830 may be included to suppress adjacent channel interference or interference from legacy NR signals and / or other LP-WUS on adjacent subcarriers. One significant benefit of this architecture is that an image rejection filter may not be needed, which simplifies the design and reduces power consumption.

[0135] The BB envelope detection architecture represents a compromise between complexity and performance. It offers better performance than the RF envelope detection architecture while being simpler than the IF envelope detection architecture in some respects. This architecture is particularly suitable for applications where direct conversion can be effectively implemented w ithout significant issues related to DC offsets and flicker noise, which are common challenges in direct conversion receivers.

[0136] In other embodiments, linear detection based architectures can be used for complex (i.e. , phase modulated) signals reception and / or complex sequence detection at the expense of potentially higher power consumption. Figure 9 illustrates a block diagram for a linear detection receiver architecture 900, in accordance with someembodiments. In this architecture, an RF signal (e.g., LP-WUS) received by an antenna 902 is converted into baseband using In-phase / Quadrature (I / Q) branches, which preserve both amplitude and phase information of the received signal. This allows for the reception of more complex modulation schemes beyond On-Off Keying (OOK).

[0137] In some embodiments, the signal path begins w ith the antenna 902 connected to a high-Q matching network 904, which optimizes signal transfer and impedance matching. The signal then passes through an RF BPF 906, which helps filter out unwanted signals outside the frequency band of interest. After filtering, the signal can optionally go through an RF LNA 908, which amplifies the weak received signal while adding minimal noise. The amplified RF signal is then split into two parallel processing paths for I and Q components. Each path includes an RF mixer 920 that mixes the RF signal with a local oscillator signal from LO 922. For the I path, the LO signal is used directly, while for the Q path, the LO signal is phase-shifted by 90 degrees (n / 2) to create the quadrature component. This creates the I and Q baseband signals. The I and Q baseband signals are then amplified by BB Amplifiers AMPs 912 and filtered by BB LPFs 914 to remove unwanted mixing products and adjacent channel interference. The filtered I and Q signals are then digitized using ADCs 916. The digitized I and Q signals are then processed by digital baseband processing circuits 918, which perform detection and decoding of the LP-WUS information.

[0138] This linear detection based architecture can be used for complex signals reception and / or complex sequence detection at the expense of potentially higher power consumption compared to envelope detection architectures. Potential power consumption reduction compared to a traditional Orthogonal Frequency Division Multiplexing (OFDM) receiver may come from one or more of the following elements: a lower performance LNA / amplifier, an oscillator / PLL with relaxed performance requirements, an ADC with lower sampling rate and smaller bit-width, and reduced BB processing complexity.

[0139] This architecture provides more flexibility in terms of the types of signals that can be received and detected, making it suitable for applications where more complex modulation schemes or better sensitivity is required, while still allowing to minimize power consumption compared to conventional receivers.

[0140] Figure 10 illustrates a block diagram for a baseband sequence detector 1000, in accordance with some embodiments. The baseband sequence detector 1000 may be used to implement digital BB processing circuits 618, 718, 818, and 918 of Figures 6-9, respectively. In the illustrated embodiment sequence-based signal design is considered for LP-WUS, and the appropriate digital baseband processing is based on time-domain correlation. This approach is particularly useful for detecting specific sequences withgood correlation properties, such as Zadoff-Chu sequences, which can be used to convey information to LP-WURs.

[0141] The baseband sequence detector 1000 consists of several components arranged in a signal processing chain. At the input, the digitized time samples of the received RF signal (after envelope detection or linear detection, depending on the receiver architecture) enter the sequence detector. These input samples are correlated with a locally stored sequence 1002 in the time-domain using an RF mixer 1004. The mixer 1004 performs a multiplication operation between the incoming samples and the locally stored reference sequence 1002. The output of the mixer 1004 is then fed into an integrator 1006, which accumulates the correlation results over a specific time window. This integration process enhances the detection capability by improving the signal-to- noise ratio of the correlation output. The correlation output from the integrator 1006 is then compared to a threshold using a comparator 1008. If the correlation output exceeds the threshold, it indicates that the specific sequence has been detected, which could represent a wake-up signal intended for the device.

[0142] In some embodiments, the correlation output may undergo other baseband processing 1010 before final detection decisions are made. This additional processing could include filtering, timing recovery, or other signal processing functions to improve detection reliability.

[0143] Using this digital baseband processing can enable the detection of sequences with good correlation properties such as Zadoff-Chu sequences. Different sequences and / or cyclic shifts can then be used to convey information to LP-WURs, allowing for efficient and reliable wake-up signal detection while maintaining low power consumption. This sequence detection approach is particularly valuable for LP-WUS applications as it provides robust detection performance even in low signal-to-noise ratio conditions, which is essential for reliable wake-up signal detection while minimizing false alarms that would unnecessarily wake up the main radio and waste power.

[0144] More generally, the architectures described herein can be used to detect LP- WUSs using significantly less power than conventional MRs. For example, an LP-WUS is a signal that can be received using significantly less power than existing NR signals and channel such as the PEI in a DC1 of format 2_7 carried using PDCCH. Similarly, an LP- WUS can be a signal that can be detected using these architectures. More specific examples are provided below.Waveform options and signals for LP-WUS

[0145] Four waveform generation options based on OOK and targeting the envelope detection based LP-WUR architectures discussed below were considered in the LP-WUSstudy. These are Option OOK-t (Single-bit per OFDM symbol), Option 00K-2 (Parallel M-bit OOK), Option OOK-3 (Multi-tone single-bit per OFDM symbol), and Option OOK- 4 (Time-domain transformed M-bit OOK). For all options, the LP-WUS can be frequency multiplexed with other NR signals. Option OOK-1 and Option OOK-4, were selected in the LP-WUS study item conclusion and are being considered for LP-WUS design in the work item.

[0146] In Option OOK-t, a single OOK pulse / bit is transmitted per one OFDM symbol where all the subcarriers, e.g., N, allocated for LP-WUS are modulated to generate a non-zero power signal at the baseband of the LP-WUR for OOK-bit = 1. Alternatively, all the N subcarriers are allocated zero power (from LP-WUR’s baseband of view) for OOK-bit = 0.

[0147] In Option OOK-4, M OOK pulses / bits are packed in a single OFDM symbol by time domain multiplexing followed by signal modification and time-to-frequency domain transformation. For example, the M-bits are converted into N’ samples by adding~1)zerosf°reach bit or by holding the bit value, i.e.,~ 1) samples. If additional shaping for the pulse of each bit is considered, the N’ samples are then passed through a signal generation and modification block. Afterwards, either DFT or least square operation is performed to convert the time-domain signal into a frequency-domain signal of length N’. Then, in case N' is selected to be > N subcarriers allocated for LP-WUS, a truncation step with an optional frequency-domain signal modification is performed. Finally, the N frequency-domain samples are allocated to the LP-WUS’s N subcarriers for further OFDM modulation and transmission.

[0148] Additionally, the LP-WUS study item concluded that knowledge, i.e., specification, of overlaid OFDM sequences that are used to generate the ON waveform of an OOK signal in the OFDMA transmitter can help a linear detection based receiver, i.e., receiver with I / Q branches, improve its performance.

[0149] A Work Item (WI) on LP-WUS started in 3GPP NR Release 19 with focus on a harmonized signal design where an OFDM sequence is overlaid over OOK-1 / OOK-4 waveform options. The harmonized signal design will be used for the generation of LP- WUS which can be received by LP-WUR architectures based on envelope detection only or LP-WUR architectures based on linear detection, i.e., w ith I / Q branches.

[0150] A periodic low-power synchronization signal (LP-SS) is expected to be specified as well for LP-WUR architectures that cannot receive existing PSS / SSS, i.e., architectures based on envelope detection only. The periodic LP-SS can be beneficial for the following functionalities: (a) RRM measurements by LP-WUR, (b) at least coarsetime synchronization of LP-WUR, and (c) at least coarse frequency synchronization of LP-WUR.

[0151] Among the four waveform generation options for LP-WUS examined, only- two of them, Option OOK-t (Single-bit per OFDM symbol) and Option OOK-4 (Timedomain transformed M-bit OOK per OFDM symbol), were selected in the LP-WUS studyitem conclusion.

[0152] It was observed in the LP-WUS study item that the significant saving in power consumption by use of LP-WUR in RRC Idle / Inactive state is enabled by sufficiently keeping the MR in a deep or an ultra-deep sleep (UDS) state for low per UE paging arrival rate. Frequent paging arrival rate in RRC Idle / Inactive state will require the MR to often transition from an UDS state to an active state, which can have a negative impact on power saving experienced by- LP-WUS monitoring. Therefore, a low per-UE paging arrival rate need to be ensured which may require the support of a large number of paging subgroups. However, the large number of paging subgroups can lead to a large LP-WUS payload which can subsequently have an impact on LP-WUS coverage and / or resource utilization.

[0153] Embodiments described below enable the support of the large number of paging subgroups with limited impact on LP-WUS coverage and / or resource utilization. Some embodiments provide such advantages using either subgroup subsets or subgroup ID / bitmap-based wake-up indication switching with preamble / frame-sync based indication. Additional embodiments further enable the configuration of dynamic POs for UEs with LP-WUS and I-DRX or eDRX configuration re-using existing paging frames and occasions. The dynamic PO configuration enables a UE to monitor POs outside I- DRX or eDRX on period which can subsequently enable lower paging latency. Additional embodiments enable efficient allocation of resources for LP-WUS occasions (LOs) as well as lower paging latency using wake-up delay reporting and configured offsets between LO(s) and reference PO(s) / PF(s).LP-WUS payload size / structure

[0154] In TR38.869, the content of LP-WUS was discussed. In some embodiments, example content in RRC IDLE / INACTIVE mode includes information on which user(s) is / are targeted by- the LP-WUS (e.g., UE-group, -subgroup or -ID). In other embodiments, the content of LP-WUS may further include cell information, sy stem information (SI) change and Earthquake and Tsunami Warning Sy stem (ETWS) / Commercial Mobile Alert System (CMAS) information, tracking area information, and Radio Access Network (RAN) area information.

[0155] It was noted during the evaluation of LP-WUS power saving gain that false paging and false alarms can have a negative impact, especially when the MR is configured to enter ultra -deep sleep state in RRC IDLE / INACTIVE state, due to unnecessaiy wake-up of the MR and associated transition energy from the sleep state to active state. Therefore, at least LP-WUS UE subgrouping with an adequate number of subgroups should be considered as concluded by RAN2 in TR38.869, as RAN2 has studied and concluded to support subgrouping for LP-WUS, detailed design depends on the payload of LP-WUS.

[0156] For LP-WUS to carry’ a UE-subgroup in RRC IDLE / INACTIVE mode, the existing UE-subgroup configuration in Rel-17 PEI or Rel-16 GWUS for NB-IoT / LTE-M may be considered as a starting point. Both Rel-17 PEI and Rel-16 GWUS support up to 8 subgroups per PO and mapping of up to 8 and 4 POs is supported by each of them, respectively. Further, the up to 8 POs supported in Rel-17 PEI can be mapped to up to 2 paging frames (PFs). Rel-19 LP-WUS may then be initially designed to support at least a subset of the configurations for either Rel-17 PEI or Rel-16 GWUS, for example, up to 8 subgroups and mapping of up to 2 POs which will require up to 16 bits. The existing CN- assigned and UE-ID based subgrouping methods used for Rel-17 PEI can also initially be reused for Rel-19 LP-WUS, e.g., if Rel-19 PEI is not concurrently configured with Rel-19 LP-WUS. Eventually, a larger number of subgroups than that is supported by PEI can be considered to alleviate the impact of the high transition energy associated with ultradeep sleep state and subsequently guarantee sufficient power saving gain using LP-WUS.

[0157] For LP-WUS to carry a UE-ID in RRC IDLE / INACTIVE mode, a minimum of 24 bits are needed for the short I-RNTI (40 bits for full I-RNTI) supported in RRC INACTIVE mode whereas a 48-bit 5G-S-TMSI might be needed in RRC IDLE mode.

[0158] In TR38.869, two alternatives for carrying LP-WUS information are discussed. In one embodiment, LP-WUS information is carried by sequence(s) detection / selection (Alternative 1). In another embodiment, LP-WUS information is carried by encoded bits (Alternative 2). The sequence-based design (Alternative 1) might limit the amount of information that can be transmitted by the LP-WUS since the sequence detection complexity can increase exponentially with the information size. Therefore, in order to support up to 16 bits for LP-WUS with UE-subgroup based addressing capability or up to 24 bits for LP-WUS with UE-ID based addressing capability in RRC INACTIVE state, at least the alternative to carry LP-WUS information using encoded bits (Alternative 2) should be supported. Further, for a target false alarm rate (FAR) <1%, a Cyclic Redundancy Check (CRC) with minimum length of 8 bits may be needed which can result in a FAR < 2-8« 0.4%. An LP-WUS design w ith 16 bit payload and 8 bit CRC based on OOK-4 waveform option with M=2 was shown toachieve the target coverage of PUSCH for Msg3 when a Subcarrier Spacing (SCS) of 30 kHz, a 4.32 MHz LP-WUS bandwidth, and a 2.6 GHz Urban scenario (TDL-C 300) are considered.

[0159] The need for a preamble (or frame sync field) preceding LP-WUS payload should be determined by the waveform timing error tolerance, LP-SS design, and LP-SS periodicity. In TR38.869, few values for LP-SS periodicity which are not less than 320 ms were considered for evaluation and the value of 320 ms is considered, as a starting point, in the WI. Further, clock options depending on their frequency error / drifting characteristics were considered as listed in Table 1 below. According to an embodiment frequency / time deviation model, the relationship between a drifted frequency error (AF), frequency drift ( F’) over a time (Tt) is AF = ±F’ * Ti.

[0160] When frequency displacement (Fd) reaches max frequency error, it is assumed to be equal to max frequency error. Ti is the time from the previous frequency synchronization. Tt may take different values depending on the chosen frequency synchronization approach. For Model 1 of frequency error, Frequency displacement (Fd), defined as the difference between ideal frequency and frequency due to 1) clock drifting (AF); and 2) residual frequency error from previous synchronization / calibration (Fr), is given as Fd (ppm)=AF (ppm) +Fr (ppm). In some embodiments when MR can assist to calibrate LP-WUR to correct the frequency error or if LP-WUR can only correct the frequency error based on LP-WUS synchronization signal.[oi6i]The relationship between the maximum frequency error (Fe) and corresponding timing drift (AT) over a time (T) is AT = ± Fe* T (linear region). The relationship between a frequency drift ( F’), and corresponding timing drift (AT) over a time (T) is AT = Fr*T ±0.5 * F’ *T2(transient region). The transition between transient and linear region (from synchronization or calibration point / time) occurs at a time Ts= (Fe-Fr) / ( F’). T is the time from the previous time synchronization and may take different values depending on the chosen synchronization approach.

[0162] Time error (Te) before detection of a current sync signal is defined as a sum of the difference between ideal time of the current sync signal and the time error due to 1) clock time drift (AT); and 2) residual time error from previous synchronization / calibration (Tr); and is determined by formula Te= AT+ Tr.Table 1: Frequency error / drifting options

[0163] In RRC Idle / Inactive, considering the case when LP-SS may not be used for frequency error correction and that the RTC clock is used for timing drift and timing error analysis, the following formula to estimate the time error (Te) can be used: Te = AT+ Tr = Fe x T + Tr.

[0164] The residual time error (Tr) depends on the sampling frequency (fs) and the LP-SS design. For example, the median residual time error at a sampling frequency of 11.2 MHz is ~O-35 / zs which represents ~3-92Xsample time (Ts) where Ts = 1 / 11.2 MHz. The maximum time offset between an LP-WUS and the last LP-SS used for synchronization at which a preamble may not be needed is then provided in Table 2 for two LP-WUS settings (i.e., OOK-i and OOK-4 with 4 / zs and 2 / zs timing error tolerance) and three sampling frequencies fs e {3.84, 7.68, 15.35} MHz.Table 2: Maximum tolerable time offset between LP-SS and LP-WUS without preamble

[0165] In some embodiments, a maximum time offset between an LP-SS and an LP- WUS w ithout a preamble should be 74 ms and 174 ms for LP-WUS time error tolerance of 2 ps and 4 ps, respectively, at a sampling frequency of 7.68 MHz and assuming no frequency error correction. Therefore, a preamble should be considered to precede the transmission of an LP-WUS if LP-SS periodicity is > = 320 ms and the time offset between LP-WUS and last LP-SS is, e.g., > 50 ms.

[0166] Summarizing, carrying LP-WUS information using encoded bits may require an 8-bit CRC to target a FAR < 1% and the corresponding overhead may be minimized byconsidering up to 24 bits of information, while noting the impact on LP-WUS coverage and resource overhead. Additionally, a preamble should precede the payload to limit the impact of timing errors.LP-WUS configuration

[0167] In RAN1#116, LP-WUS occasions (LOs) and LP-WUS monitoring occasions (MOs) are defined as follows. Each LO has one or more LP-WUS monitoring occasions (MOs), w here UE can monitor for LP-WUS transmission in each of the LP-WUS MOs. In some embodiments, different LP-WUS MOs may correspond to different beams in multibeam operation. In some embodiments, each LO may or may not be defined as a time window^ that covers the corresponding LP-WUS MOs. In some embodiments, a UE may monitor LOs with a configured periodicity using eDRX, for example.

[0168] When PEI is configured and a UE supports monitoring of PEI, the UE can monitor one PEI occasion (PEI-O) per an I-DRX cycle where a PEI-0 is a set of Physical Downlink Control Channel (PDCCH) MOs and may be associated with two consecutive PFs with Ns POs per PF. The PEI-0 is defined by a reference point, determined by a frame-level offset from the start of the first PF of the PF(s) associated with the PEI-0 (provided by pei-FrameOffset in SIB1), and one or more symbol-level offset(s) provided by firstPDCCf I-MonitoringOccasionOf PEI-0 where the number of symbol-level offsets depend on the number of POs associated with a PEI provided by Np '. The reference point and one of the offsets determine the time of the first PDCCH the UE should start monitoring for a PEI according to a configured search space defined by pei-SearchSpace- ri .

[0169] Similarly, an LO can be defined by a reference point and one or more offsets instead of a search space as it is expected that LP-WUS monitoring configuration will belimited. The one or more offsets can be used to define one or more first LP-WUS MO(s) where the first LP-WUS MO is the starting LP-WUS MO in a group of LP-WUS MOs corresponding to the number of beams in the system in support of the multi-beam operation. Alternatively, a number and periodicity parameter can be used to define the LP-WUS MO groups per LO. Another offset (time gap) can be used to define the time gap between any two LP-WUS MOs in the groups of LP-WUS MOs supporting the multibeam operation.

[0170] Figure 11A illustrates an example of LP-WUS occasion (LO) and LP-WUS monitoring occasion (MO) configuration options using a reference point and offsets, in accordance w ith some embodiments. In particular, Figure 11A shows a configuration that consists of a reference point, Ns x Ng offsets to first LP-WUS MOs, and a time gap. Ng is a number of LP-WUS MO groups per LO and Ns is a number of POs per PF. The figure demonstrates LP-WUS monitoring configuration per Paging Frame (PF), meaning the same configuration applies for every PF, though this can be extended to cover cases where the configuration is associated with one or more PFs. The horizontal axis of Figure 11A represents time progression, while the vertical arrangement shows different monitoring occasions and their relationships. Figure 11A implicitly assumes that the LO periodicity considered by the UE is the same as the configured I-DRX periodicity, although higher LO periodicity (shorter period) can also be considered.

[0171] In the illustrated embodiment, two Paging Occasions (POs) are assumed per PF 1104, where each PO (PO-i 1106-i for ie{i,2}) is associated with an LO (LO-i 1108-i for ie{i,2}). Each of the LOs (LO-1 1108-1 and LO-2 1108-2) comprises two LP-WUS MO groups (LP-WUS MO Group-1 1110-1 and LP-WUS MO Group-2 1110-2), and each of the LP-WUS MO groups (LP-WUS MO Group-1 1110-1 and LP-WUS MO Group-2 1110-2) includes two LP-WUS MOs 1112, corresponding to an example two-beam scenario for multi-beam operation.

[0172] The first LP-WUS MO 1112 of the first LP-WUS MO Group-1 1110-1 of each example LO-i 1108-i is defined by a reference point 1102, defined as multiples of Nfm frame 1114 (e.g., 10 Nfm frame duration = 100 Nfm ms) away from PF 1104, and an offset Oi,i 1116-i for i£{i,2}.

[0173] The first LP-WUS MO 1112 of the second LP-WUS MO Group-2 1110-2 of each example LO-i 1108-i is defined by a reference point 1102, defined as multiples of Nfm frame 1114 (e.g., 10 Nfm frame duration = 100 Nfm ms) away from PF 1104, and an offset 0i,2 1118-i for ie{i,2}.

[0174] Further, the subsequent LP-WUS MOs 1112 per LP-WUS MO group are defined by a time gap 1120 w ith respect to the end of the previous MO, where the number of LP-WUS MOs per group corresponds to the number of beams in the system. The timegap 1120 ensures proper spacing between monitoring occasions to accommodate different beam directions in multi-beam operation.

[0175] This configuration approach provides flexibility in defining when and how a UE monitors for LP-WUS, allowing network operators to optimize the trade-off between power consumption and latency. By properly configuring the reference points, offsets, and time gaps, the network can ensure that UEs monitor for LP-WUS at appropriate times while minimizing unnecessary wake-ups and power consumption. This configuration approach further enables the support of multi-beam operation, w hich is important for ensuring reliable coverage, especially in higher frequency bands where directional transmission and reception become more critical.

[0176] Figure 11B illustrates an example of LP-WUS occasion (LO) and LP-WUS monitoring occasion (MO) configuration options using a reference point, offsets, MO groups number, and periodicity, in accordance with some embodiments. In particular, Figure 11B shows a configuration that consists of a reference point, Ns offsets to first LP- WUS MOs, a number (Ng) and periodicity for LP-WUS MO groups, and a time gap. This approach differs from the configuration shown in Figure 11A in how the additional LP- WUS MO groups are defined within an LO. The horizontal axis of Figure 11B represents time progression, while the vertical arrangement shows different monitoring occasions and their relationships.

[0177] In the illustrated embodiment, two Paging Occasions (POs) are assumed per PF 1104, where each PO (PO-i 1106-i for ie{i,2}) is associated with an LO (LO-i 1108-i for ie{i,2}) . Each of the LOs (LO-1 1108-1 and LO-2 1108-2) comprises two LP-WUS MO groups (LP-WUS MO Group-1 1110-1 and LP-WUS MO Group-2 1110-2), and each of the LP-WUS MO groups (LP-WUS MO Group-1 1110-1 and LP-WUS MO Group-2 1110-2) includes two LP-WUS MOs 1112, corresponding to an example two-beam scenario for multi-beam operation.

[0178] The first LP-WUS MO 1112 of the first LP-WUS MO Group-1 1110-1 of each example LO-i 1108-i is defined by a reference point 1102, defined as multiples of Nfm frame 1114 (e.g., 10 Nfm frame duration = 100 Nfm ms) away from PF 1104, and an offset Oi,i 1116-i for ie{i,2}, similar to configuration shown in Figure 11A.

[0179] In the illustrated embodiment, the first LP-WUS MOs (e.g., the first LP-WUS MOs 1112) of the additional (Ng-1) LP-WUS MO groups (e.g., second LP-WUS MO Group-2 1110-2) in an LO (LO-i 1108-i for ie{i,2}) are defined based on a number (Ng) of LP-WUS MO groups per LO and a periodicity parameter 1122, rather than by individual offsets from the reference point 1102.

[0180] Further, the subsequent LP-WUS MOs 1112 per LP-WUS MO group are defined by a time gap 1120 with respect to the end of the previous MO, w here the numberof LP-WUS MOs per group corresponds to the number of beams in the system. The time gap 1120 ensures proper spacing between monitoring occasions to accommodate different beam directions in multi-beam operation.

[0181] In the illustrated embodiment, the first LP-WUS MO of the first LP-WUS MO group, first LP-WUS MOs of subsequent LP-WUS MO groups are placed at regular intervals determined by the periodicity parameter 1122. Within each LP-WUS MO group, the subsequent LP-WUS MOs are spaced according to a time gap 1120, similar to configuration shown in Figure 11A, where the number of LP-WUS MOs per group corresponds to the number of beams in the system.

[0182] The illustrated embodiment potentially offers a more compact way to define multiple LP-WUS MO groups within an LO, especially when the groups should be regularly spaced. This can reduce signaling overhead in the configuration information sent to the UE, as only a single periodicity parameter is needed instead of multiple individual offsets.

[0183] This configuration approach maintains the flexibility needed to support multi-beam operation while potentially simplifying the configuration information that needs to be signaled to the UE. By properly configuring the reference points, offsets, number of groups, periodicity, and time gaps, the network can ensure that UEs monitor for LP-WUS at appropriate times while minimizing unnecessary wake-ups and power consumption.

[0184] During the RAN 1# 116 discussions and as captured in the agreement on LO and LP-WUS MO definition above, the support of LP-WUS under e-DRX configuration was questioned. In TR 38.869, the impact of supporting LP-WUS under e-DRX configuration was evaluated and the following conclusion was reached: compared with existing eDRX operation, significant paging latency reduction and moderate UE power saving gain is observed, if LP-WUS monitoring and the corresponding paging monitoring after MR wake-up is performed not restricted within existing PTW of eDRX; and significant UE power gain and moderate paging latency increase is observed if LP-WUS monitoring is restricted within existing PTW of eDRX and existing paging occasion determination is reused.

[0185] In Section 8.1.1.4.2 of TR 38.869, a mean latency reduction of 96%~98% was observed when LP-WUS monitoring is not restricted in Paging Time Window (PTW) and dynamic PO determination is considered at an effective per UE paging arrival rate <=1% while a mean power saving gain in the range of 9%~s8% was still observed. Therefore, it can be beneficial to consider LP-WUS under eDRX configuration along with dynamic PO determination to enable lower latency for applications / use cases that still prioritizes power saving.

[0186] Figure 12A illustrates an example of LP-WUS occasion (LO) configuration and monitoring w ith extended Discontinuous Reception (eDRX) and Dynamic Paging Occasion (PO), in accordance with some embodiments. The horizontal axis of Figure 12A represents time progression, while the vertical axis represents the power profile of the UE. The illustrated embodiment shows a configuration where a UE configured with LP- WUS under eDRX configuration may monitor LOs 1202 according to a periodicity higher than the Paging Time Window’s (PTW’s) periodicity. This means the period (LO cycle 1218) between consecutive LOs is smaller than the eDRX cycle 1216, allowing for more frequent monitoring of LP-WUS while still maintaining the power-saving benefits of eDRX.

[0187] In the configuration shown, LOs are defined by a reference point 1208 (e.g., determined by Nfm1210), an offset Oi 1212, and the LO cycle 1218 which can be less than or equal to the eDRX cycle 1216 and greater than or equal to the I-DRX cycle 1214. Furthermore, PFs 1206 within the PTW 1204 are separated by I-DRX cycle 1214. This allows for flexible configuration based on the specific requirements of power saving and latency.

[0188] The configuration shown in Figure 12A enables this improved performance by allowing the UE to monitor for LP-WUS more frequently than the eDRX cycle 1216 would normally permit, and by supporting dynamic PO monitoring that allows the UE to monitor POs outside of the scheduled PTW 1204 upon receiving an LP-WUS, thereby reducing paging latency significantly.

[0189] Figure 12B illustrates an example of LP-WUS detection after a dynamic PO cutoff point, in accordance with some embodiments. The horizontal axis of Figure 12B represents time progression, while the vertical axis represents the power profile of the UE. The illustrated embodiment, the UE detects an LP-WUS in an LO 1202 that is monitored after the dynamic PO cutoff reference point 1220. In some embodiments, the dynamic PO cutoff reference point 1220 may be configured, e.g., using a reference point offset ( / V^m) multiplicative factor Mc, to differentiate between when a UE is expected to monitor a PO / PF 1206 outside of the configured PTW 1204 (i.e., a dynamic PO) versus w hen it is expected to monitor a PO / PF 1206 within the configured PTW 1204.

[0190] In the illustrated embodiment, the UE detects an LP-WUS in an LO 1202A that is monitored after the dynamic PO cutoff reference point 1220. In such embodiments, the UE is not expected to monitor a PO / PF 1206 outside the configured PTW 1204 and should only monitor POs / PFs 1206 within the configured PTW 1204. In some embodiments, since the LP-WUS is detected after the dynamic PO cutoff reference point 1220, the UE may follow7the standard eDRX procedure and monitors POs / PFs1206 only w ithin the configured PTW 1204, resulting in potentially higher latency but maintaining the power-saving benefits of the eDRX configuration.[oi9i]This approach provides a flexible mechanism for balancing power consumption and latency based on the timing of LP-WUS detection relative to the dynamic PO cutoff reference. By configuring the dynamic PO cutoff reference appropriately, network operators can control when UEs should use dynamic POs (for lower latency) versus when they should follow the standard eDRX procedure (for better power efficiency).

[0192] Figure 12C illustrates an example of LP-WUS detection before a dynamic PO cutoff point, in accordance with some embodiments. The horizontal axis of Figure 12C represents time progression, w hile the vertical axis represents the power profile of the UE. The illustrated embodiment, a UE detects an LP-WUS in an LO 1202A monitored before the dynamic PO cutoff reference point 1220. In such embodiments, the UE is expected to monitor at least one PO / PF 1206 outside the configured PTW 1204 using similar configuration to LP-WUS monitoring under I-DRX operation.

[0193] In the illustrated embodiment, since the LP-WUS is detected before the dynamic PO cutoff reference point 1220, the UE monitors a dynamic PO / PF 1206 outside the configured PTW 1204. This allows for significantly reduced latency compared to waiting for the next scheduled PTW 1204. In some embodiments, the UE may then monitor POs within the configured PTW 1204 if a paging DCI is not detected during the at least one dynamic PO or if the at least one dynamic PO is missed, e.g., due to a longer wake-up / ramp-up time of the main radio.

[0194] This approach provides significant latency benefits while still maintaining substantial power savings. By detecting the LP-WUS before the dynamic PO cutoff reference and monitoring a dynamic PO outside the configured PTW, the UE can respond much more quickly to paging messages, reducing the latency by 96-98% according to the evaluations mentioned in the disclosure, while still achieving power saving gains in the range of 9-58%.

[0195] This flexible mechanism allows network operators to balance power consumption and latency requirements based on the specific needs of different applications and use cases, making it particularly valuable for loT and other applications where both power efficiency and timely response to network events are important.

[0196] In RAN1#116, the following proposal was agreed to support UE’s monitoring of legacy PO after LP-WUS detection whereas support of UE’s monitoring of a Dynamic PO is for further study.

[0197] Figure 13 illustrates an example of LP-WUS occasion (LO) configuration and monitoring with Idle mode Discontinuous Reception (I-DRX) and Dynamic Paging Occasion (PO), in accordance with some embodiments. The illustrated embodimentdemonstrates how LP-WUS can be used in conjunction w ith I-DRX to achieve lower latency while still maintaining power saving benefits. The horizontal axis of Figure 13 represents time progression, while the vertical axis represents the power profile of the UE.

[0198] Similar to UEs w ith eDRX configuration, LP-WUS with Dynamic PO can be supported for UEs with I-DRX configuration. However, it should be noted that Dy namic PO support does not necessarily mean that new resources should be allocated for additional POs that are different than what are already allocated for existing / legacy POs. For example, existing PF / PO configuration allows the presence of a PF every {2, 4, 8, 16} radio frames with {1, 2, 4} POs per PF, according to paging configuration in SIB1, when SSB periodicity > 20 ms or SSB / CORESET multiplexing pattern 1 (i.e., TDM configuration) is considered. Therefore, there can already be at least a PF even 160 ms regardless of the configured I-DRX cycle. Currently, this PF periodicity controls the number (N) of PFs per I-DRX paging cycle using RRC parameter nAndPagingFrameOffset where Ne {T, T / 2, T / 4, T / 8, T / 16}. For each UE, the System Frame Number (SFN) carrying the relevant PF in any I-DRX paging cycle (T) is determined using a PF offset value (PF_offset), which is also determined by the RRC parameter nAndPagingFrameOffset.

[0199] The illustrated embodiment shows a plurality LOs 1302 separated by an LO cycle 1316a and a plurality PFs 1306 separated by an PF cycle 1318. In some embodiments, each PF 1306 may comprise one or more POs 1304. In some embodiments, some of PFs 1306 may be legacy PFs 1306A (comprising one or more legacy POs 1304A) and dynamic PFs 1306B (comprising one or more dynamic POs 1304B). Adjacent legacy PFs 1306A are separated by an 1-DRX cycle 1314. SFN_LO 1308 is the first radio frame of the LO 1302A where an LP-WUS is received by the UE and SFN 1310 is the first radio frame of the legacy PF 1306A.

[0200] In the illustrated embodiment, upon detection of an LP-WUS in a configuredLO 1302A, a UE may determine the availability of a dynamic PO 1304B based on the determination of SFN_ LO 1308 < Dynamic PO Cutoff reference 1312. If this condition is met, the UE may monitor the dynamic PO 1304B and consider monitoring the legacy PO 1304A if a Paging DCI is not detected in the dynamic PO 1304B or the dynamic PO 1304B is missed, e.g., due to a long ramp-up time of the main radio.

[0201] On the other hand, if SFN_LO 1308 > Dynamic PO Cutoff reference 1312, the UE may directly monitor the legacy PO 1304A without attempting to monitor a dynamic PO 1304B.

[0202] In some embodiments, SFN 1310 can be determined by introducing a negative dynamic PO offset (DPO_offset) to the UE_ID in existing PF determinationformulation, where DPO_offset may be determined by floor ((SFN - SFN_LO - RU_offset)*(N div T)) for an SFN_LO 1308 determined based on LP-WUS detection and a ramp-up offset (RU_offset) for the MR.

[0203] It should be noted that Figure 13 is not to scale, i.e., time between an LO and corresponding PF may actually be longer to capture the ramp-up time from ultra-deep sleep state. Also, Figure 13 assumes an LO periodicity (LO cycle 1316) similar to the PF periodicity (PF cycle 1318), however, different periodicity is possible. For example, LO cycle 1316 may be larger than PF cycle 1318.

[0204] Initial discussion in RAN1#116 on the periodicity of LO for a UE with I-DRX configuration considered the two options of having LO cycle 1316 (1) the same as; or (2) smaller than the I-DRX cycle 1314. To benefit from the lower paging latency considering the dynamic PO, smaller LO cycle 1316 than the I-DRX cycle 1314 is needed.

[0205] This approach provides a flexible mechanism for balancing power consumption and latency in I-DRX configurations, similar to the approach described for eDRX in Figures 12A-12C, allowing network operators to optimize the trade-off between these parameters based on specific application requirements.

[0206] It is understood that allowing legacy UEs to share their PO with an LP-WUS capable UE from a different UE group may result in higher false alarm for the legacy UEs monitoring the shared PO, i.e., a paging DCI may be sent to only page the UEs with Dynamic PO configuration when legacy UEs monitoring the same PO were not supposed to receive paging. In order to handle this issue, an alternative paging RNTI (e.g., AP- RNTI) may be considered when the paging DCI is intended only for UEs with Dynamic PO configuration, otherwise, legacy P-RNTI is used for the paging DCI. However, this might require the UEs with Dynamic PO configuration to consider both P-RNTI and the alternative paging RNTI during paging DCI detection in the Dynamic PO. In summary, an alternative paging RNTI may be considered for the paging DCI in the Dynamic PO when only UEs with Dynamic PO configuration are to be paged to avoid increasing false paging to legacy UEs.

[0207] In RAN1#118, there was an agreement for the UE to report one value for the wake-up delay from X candidate values. Wake-up delay is minimum gap time between LP-WUS reception and the MR to start PDCCH monitoring. In some embodiments, X may be 2, 3, or 4, which applies for IDLE / INACTIVE mode.

[0208] In TR 38.869, two sleep power states were considered for the evaluation of LP-WUS in RRC IDLE / INACTIVE state (i.e., deep sleep and ultra-deep sleep power states). For the deep sleep state, a ramp-up time in range of 10 ms to 20 ms was considered whereas for the ultra-deep sleep state, the two alternatives of 400 ms and 800 ms were considered for the ramp-up time (in a range of 400 ms to 800 ms).Therefore, a UE may report a wake-up delay value from X=3 candidate values which can be the same set e {20 ms, 400 ms, 800 ms} evaluated in TR38.869 or a new set, e.g., e {80 ms, 400 ms, 720 ms} as discussed later.

[0209] Further, in RAN1#118, multiple offset values between a LO and a reference PO / PF were also considered. Additionally, there was a discussion in RAN1#117 about the mapping between LOs and POs. In RAN1#117, it is supported that UEs monitoring the same PO are divided into multiple subgroups, where LP-WUS can provide wake-up indication for each subgroup. In some embodiments, UEs monitoring the same PO monitor the same LO (Option 1). In other embodiments, UEs corresponding to different POs monitor the same LO (Option 2). In yet other embodiments, UEs monitoring the same PO are divided into multiple sets of subgroups, with UEs within each set of subgroups monitoring the same LO (Option 3). In yet other embodiments, any combinations of Options 1, 2 and 3 can be considered.

[0210] In RAN1#118 on the LO configuration for iDRX, offset value(s) between a LO and a reference PO / PF is / are configured. In some embodiments, one or multiple offset values may be configured. In some embodiments when multiple offset values are supported, a UE may decide which Offset value to use. In some embodiments, the UE may determine LO(s) corresponding to Option 1, 2, and / or 3 discussed above. In some embodiments, for each UE, the periodicity of LO is the same as its iDRX cycle. In some embodiments when a UE receives a wake-up indication in a LP-WUS, the UE monitors the PO (e.g., legacy PO) associated with the offset (Alternative 1). In other embodiments when a UE receives a wake-up indication in a LP-WUS, the UE monitors the first PO (e.g., legacy PO) after its reported wake-up delay (Alternative 2).

[0211] The multiple offset values that can be configured by the network may then be dependent on the reported wake-up delay values and subsequently one or more than one LO reference point(s) can be defined depending on the number of configured offsets as well as the considered reference PO(s) / PF(s).

[0212] Then, up to three offset values from the reference PO(s) / PF(s), corresponding to the X=3 candidate wake-up delay values considered above, may be configured by the network. A UE may select the first offset value, from the set of configured values, which is greater than or equal to its reported wake-up delay value. If the set of configured values are all smaller than the UE’s reported wake-up delay value, one of the following options may be considered:

[0213] (a) The UE follows legacy paging procedure, i.e., PO monitoring. LP-WUS monitoring may be considered only if an updated wake-up delay value from the set of configured values is reported.

[0214] (b) The UE monitors LP-WUS and upon wake-up indication reception, theUE monitors the first PO after its reported wake-up delay (i.e. , Alternative 2 of the RANi#n8 agreement discussed above).

[0215] For option (b) above, the UE may consider the first offset value, from the set of configured values, which is less than the reported wake-up delay value for the determination of LO configuration, e.g., LO reference point, and / or the reference PO / PF.

[0216] In existing specification [TS 38.304], a UE determines the SFN of its PF using the legacy formula(SFN + PF_offset) mod T = (T div N)*(UE_ID mod N), Formula (1) where Ne {T, T / 2, T / 4, T / 8, T / 16} represents the number of PFs per I-DRX paging cycle configured using RRC parameter nAndPagingFrameOffset, PF_offset is a PF offset value that is also determined by the RRC parameter nAndPagingFrameOffset, and T is the I- DRX paging cycle. In some embodiments, the UE determines T as the shortest of the UE specific DRX value(s), if configured by RRC and / or upper layers, and a default DRX value broadcast in system information. In some embodiments when a UE specific DRX is not configured by upper layers, the default value is applied.

[0217] The determination of the LO’s reference point and the reference PF can be, in one technical realization, performed using the legacy formula above for SFN determination and a configured offset value, if a single offset value from the reference PO / PF is configured. In this case, which is illustrated in Figure 14A, both Option 1 and Option 2 of the RAN1#117 agreement on LO / PO mapping are applicable.

[0218] Figure 14A illustrates an example of LP-WUS occasion (LO) reference point (s) and reference Paging Frame(s) (PF(s)) for a single offset value, in accordance with some embodiments. The horizontal axis of Figure 14A represents time progression, while the vertical axis represents the power profile of the UE.

[0219] The illustrated embodiment shows an LO 1402 and a plurality PFs 1406 separated by an 1-DRX cycle 1408. In some embodiments, the reference PF 1406R may be determined using the legacy Formula (1) for SFN determination. The LO reference point 1402 is determined based on the reference PF 1406R and a configured offset 1410, such that offset 1410 represents a time between the reference PF 1406R and the LO reference point 1402. In some embodiments, each PF 1406 may comprise one or more POs 1404. The reference PF 1406R comprises one or more reference POs 1404R. In the illustrated embodiment, a value of the offset 1410 is 800 ms and a value (T) of the I-DRX cycle 1408 is 1.28 s.

[0220] By properly configuring a value of the offset 1410, network operators can ensure that the LP-WUS is transmitted with sufficient lead time before the associatedpaging occasion to accommodate the wake-up delay of the UE's main radio, ensuring that the MR is fully awake and ready to receive the paging message when it arrives.

[0221] In another technical realization and in the case when multiple offset values from reference PO(s) / PF(s) are configured by the network, there can be two alternatives for a UE to determine its LO’s reference point and / or the corresponding reference PF:

[0222] Alt-1: A default reference PF and up to X=3 LOs’ reference points per T; and

[0223] Alt-2: A default reference PF, an LO reference point, and up to X=3 UE- specific reference PFs.

[0224] For Alt-1 above, considering the SFN determination of the reference PF according to the legacy Formula (1) and assuming that the offset values e {20 ms, 400 ms, 800 ms}, similar to the ramp-up times for deep sleep and ultra-deep sleep states considered in TR 38.869, then Option 3 (or combination of Option 1 / 2 and Option 3) of RAN1#117 agreement on LO / PO mapping may be applicable where UEs belonging to the same reference PO / PF are divided into multiple sets of subgroups (based on the multiple reported wake-up delays and corresponding multiple configured offset values) and each set monitors the same LO defined by the corresponding offset from the reference PO / PF. This implies that for each PF in the system, there can be up to X=3 configured LOs which might imply a large LP-WL’S resource overhead and / or subgrouping based on the UEs’ wake-up delay capabilities / state.

[0225] Figure 14B illustrates an example of LO reference point(s) and reference PF(s) for multiple offset values according to Alt-1, in accordance with some embodiments. The horizontal axis of Figure 14B represents time progression, while the vertical axis represents the power profile of the UE.

[0226] The illustrated embodiment shows a plurality PFs 1406 separated by an I- DRX cycle 1408 and a plurality of LOs 1402. In some embodiments, the reference PF 1406R may be determined using the legacy Formula (1) for SFN determination. The LO reference points 1402A-1402C are determined based on the reference PF 1406R and configured offsets 1410A-1410C, such that offsets 1410A-1410C represents times between the reference PF 1406R and the LO reference points 1402A-1402C, respectively. In some embodiments, each PF 1406 may comprise one or more POs 1404. The reference PF 1406R comprises one or more reference POs 1404 R. In the illustrated embodiment, a value of the offset 1410A is 20 ms, a value of the offset 1410B is 400 ms, a value of the offset 1410C is 800 ms, and a value (T) of the default I-DRX cycle 1408 is 640 ms. The default I-DRX cycle 1408 may refer to the default DRX value broadcast in system information or the shortest of the UE-specific DRX value(s) and the default DRX value. In the illustrated embodiments, three offsets result in three LO reference points per I- DRX cycle 1408, regardless of the value (T) of the I-DRX cycle 1408.

[0227] This configuration provides flexibility to accommodate UEs w ith different wake-up delay capabilities, from deep sleep (requiring shorter offsets like 20 ms) to ultra-deep sleep (requiring longer offsets like 800 ms). However, this approach may lead to higher resource overhead due to the multiple LO reference points that need to be configured and monitored.

[0228] Figure 14C illustrates an example of LO reference point(s) and reference PF(s) for multiple offset values according to Alt-1, in accordance with some embodiments. The horizontal axis of Figure 14C represents time progression, while the vertical axis represents the power profile of the UE. The embodiment of Figure 14C is similar to the embodiment of Figure 14B, w ith a distinction in values of offsets 1410A- 1410C. In the illustrated embodiment, a value of the offset 1410A is 80 ms, a value of the offset 1410B is 400 ms, and a value of the offset 1410C is 720 ms.

[0229] In some embodiments, depending on offset values, the number of LO reference points per I-DRX cycle 1408 depends on the value (T) of the I-DRX cycle 1408 and may be smaller than three even if three offset values are configured. In the illustrated embodiment, the number of LO reference points per I-DRX cycle 1408 is equal to 2. Number of LO reference points per paging cycle T (I-DRX cycle) for Alt-1 and Alt-2 and various offset values are shown in Table 3.Table 3: Number ofLO Reference Points per Paging Cycle T forAlt-i andAlt-2

[0230] In some embodiments, the value of the itfloffset in the set of X candidate values may be selected according to the following relationship

[0232] w here Tois a common time offset, Tspecis an LP-WUS specific (w hich can be common or specific to UE(s)) DRX value, and Ntis the Ithmultiplicative factor of the Ithoffset value. In Table 4, exemplary offset values along w ith the corresponding values for the associated parameters are presented.Table 4: Example Offset Values and Corresponding Parameters’ Values

[0233] For Alt-2 above, the SFN of a default reference PF can be determined according to the legacy Formula (1) and using the LP-WUS default paging cycle T. The default reference PF and the largest configured offset value can be used to determine the LO’s reference point. A UE-specific reference PF can then be determined based on the determined LO’s reference point and the configured offset values. The SFN of the UE- specific reference PF can be determined using the legacy formula above and the UE- specific paging cycle, e.g., Tspec= 320ms, as follows(SFN + PF_offset) mod T_spec = (T_spec div N)*(UE_ID mod N) Formula (2)

[0234] Then, considering Alt-2 and assuming the offset values 6 {80 ms, 400 ms, 720 ms}, Option 1 or Option 2 of RAN1#117 agreement on LO / PO mapping may be applicable.

[0235] Figure 14 D illustrates an example of LO reference point (s) and reference PF(s) for multiple offset values according to Alt-2, in accordance with some embodiments. The horizontal axis of Figure 14D represents time progression, while the vertical axis represents the power profile of the UE. The embodiment of Figure 14D is similar to the embodiment of Figure 14C, w ith similar features being labeled using similar numerical references, and descriptions of similar features are not repeated herein.

[0236] In the illustrated embodiment, the SFN of a default reference PF is determined according to the legacy Formula (1) and using the LP-WUS default paging cycle T (default I-DRX cycle 1408). The default reference PF and the largest configured offset value 1410C are used to determine the reference point for LO 1402. UE-specific reference PFs 1406R1-PFS 1406R3 (comprising POs 14O4R1-POS 1404R3, respectively) can then be determined based on the reference point for LO 1402 and the configured offset values 1410A-1410C, respectively. In some embodiments, the SFN of the UE- specific reference PF can be determined using the legacy Formula (2) and the UE-specific paging cycle (UE-specific I-DRX cycle 1412).

[0237] In the illustrated embodiment, a value of the offset 1410A is 80 ms, a value of the offset 1410B is 400 ms, a value of the offset 1410C is 720 ms, a value (T) of the default I-DRX cycle 1408 is 1.28 s, and a value (Tspec) of UE-specific I-DRX cycle 1412 is 320 ms. These configured three offsets result in only one LO reference point per the default I- DRX cycle 1408, regardless of the value (T) of the default I-DRX cycle 1408, with respect to three UE-specific reference PFs 1406R1-PFS 1406R3 corresponding to each of the configured offsets 1410A-1410C.

[0238] By using this approach, network operators can optimize resource utilization while maintaining the flexibility to support UEs with various sleep states and wake-up delay requirements, from deep sleep (requiring shorter offsets like 80 ms) to ultra-deep sleep (requiring longer offsets like 720 ms).Subgroup indication in LP-WUS

[0239] As discussed herein, Rel-17 PEI supports wake-up indication of up to 8 subgroups per PO where the indication is bitmap based allowing the concurrent / simultaneous wake-up indication of multiple subgroups per PEI signaling, i.e., the DCI carried in a PDCCH. Further, it was discussed herein that a larger number of subgroups may be needed to guarantee an LP-WUS power saving gain by limiting the impact of false paging and high transition energy from the ultra-deep sleep state. LP- WUS may then consider similar bitmap-based indication mechanism as for PEI, however, the larger number of subgroups, e.g., up to 24 subgroups, may then require apayload size of at least 24 bits which might have an impact on LP-WUS coverage and / or resource utilization.

[0240] Therefore, for LP-WUS to support the large number of subgroups while limiting the impact on coverage and / or resource utilization, the number of subgroups may be split into multiple (e.g., two) subsets where the bitmap-based wake-up indications of only a single subset of the subgroups may be included in the payload of an LP-WUS. Subsequently, multiple (e.g., two) LP-WUS transmissions may be needed to convey the bitmap based wake-up indications for the multiple (e.g., two) subsets of subgroups, if needed, but the payload size of a single LP-WUS can be shorter than that needed for the total number of subgroups (e.g., 12 bits for each of two subsets rather than 24 bits for the whole set of subgroups) which can limit the impact on LP-WUS coverage (i.e., assuming fixed resource per bit).

[0241] To limit the impact on resource utilization, proper selection of the subsets of the subgroups and / or providing indication of the subset in the LP-WUS may be considered. For proper selection of the subsets of the subgroups, traffic characteristics may be considered. For example, two subsets of the subgroups may be considered where a first subset may be associated with UEs of eDRX configuration, i.e., sparse traffic arrival, and a second subset may be associated with UEs of DRX configuration, i.e., more frequent traffic arrival. Subsequently, the LP-WUS carrying wake-up indications for the first subset of subgroups may be transmitted less often than the LP-WUS carrying wakeup indications for the second subset of subgroups.

[0242] Figure 15A is an example of bitmap-based subgroup wake-up indication options for large number of subgroups assuming two subsets of the subgroups, in accordance with some embodiments. In the illustrated embodiment, the subset indication is implicit such as assigning an LP-WUS MO (e.g., LP-WUS MOs 1504-1 and 1504-2) for each subset (e.g., subsets 1506-1 and 1506-2) in an LO 1502.

[0243] Figure 15B is an example of bitmap-based subgroup wake-up indication options for large number of subgroups assuming two subsets of the subgroups, in accordance with some embodiments. The embodiment of Figure 15B is similar to the embodiment of Figure 15A, with similar features being labeled using similar numerical references, and descriptions of similar features are not repeated herein. In the illustrated embodiment, the subset indication is explicit such as in a header field (e.g., header fields 1508-1 and 1508-2).

[0244] Figure 15C is an example of bitmap-based subgroup wake-up indication options for large number of subgroups assuming two subsets of the subgroups, in accordance with some embodiments. The embodiment of Figure 15C is similar to the embodiment of Figure 15A, with similar features being labeled using similar numericalreferences, and descriptions of similar features are not repeated herein. In the illustrated embodiment, the subset indication is explicit such as in a preamble (e.g., preambles 1510-1 and 1510-2) preceding the LP-WUS payload.

[0245] The header may incur additional resource overhead whereas the preamble indication can be more resource efficient, as a preamble or LP-WUS frame sync field that preceded the LP-WUS payload maybe needed anyway if an LP-SS periodicity >= 320 ms is considered. Further, to limit the preamble detection complexity, the number of subsets of the subgroups may be limited to two subsets and a sequence (S) and its complement (5) can be used for subset indication as shown in Figure 15C. The LP-WUR can differentiate between the two subsets using the sign of the detected peak, e.g., positive peak to indicate a first subset and a negative peak to indicate a second subset. However, more than two subsets may be considered and more sequences may subsequently be considered.

[0246] In the case that LP-WUS is configured only for UEs with sparse traffic arrival, e.g., UEs with eDRX and Dynamic PO configuration, the bitmap-based wake-up indication may not be the appropriate choice all the time as it may unnecessarily lead to an increase in LP-WUS resource utilization whereas subgroup ID-based indication, i.e., an LP-WUS cariying one or more subgroup identifier(s), may be more efficient. In this case, the preamble / frame sync may be used to indicate a bitmap-based (Normal format) or ID-based (Compact format) LP-WUS format depending on the number of subgroups that require a wake-up indication in an LP-WUS, as shown in Figures 16A and 16B. For example, assuming a total number of subgroups of 24, a Compact LP-WUS with ID- based subgroup indication may be used to concurrently indicate wake-up for up to, e.g., 4 subgroups, whereas a Normal LP-WUS with bitmap-based subgroup indication may be used to concurrently indicate wake-up for larger number of subgroups, e.g., more than 4 subgroups.

[0247] Figure 16A is an illustration of bitmap-based and ID-based subgroup wakeup indication switching, in accordance with some embodiments. Unless otherwise indicated, features i6xx of Figure 16A are similar to features 15XX of Figures 15A-15C, and descriptions of similar features are not repeated herein. In the illustrated embodiment, the number of IDs 1612 included in a Compact LP-WUS with ID-based subgroup indication can be determined using a header 1608 preceding the LP-WUS payload.

[0248] Figure 16B is an illustration of bitmap-based and ID-based subgroup wakeup indication switching, in accordance with some embodiments. The embodiment of Figure 16B is similar to the embodiment of Figure 16A, with similar features being labeled using similar numerical references, and descriptions of similar features are notrepeated herein. The number of IDs included in a Compact LP-WUS w ith ID-based subgroup indication can be determined using an end of frame (EoF) delimiter 1614 at the end of the LP-WUS payload.

[0249] Alternatively, a fixed payload size may be considered for the Compact LP- WUS w ith ID-based subgroup indication and depending on the number of IDs to be included in an LP-WUS, padding or null bits may be used. For example, a Compact LP- WUS without a header or an EoF delimiter may have a payload size enough to carry, e.g., three, subgroup IDs and then the LP-WUS may be used to indicate, e.g., two, subgroup IDs for wake-up. The, e.g., two, subgroup IDs may be carried in any of the, e.g., three, subgroup ID fields, i.e., the subgroup IDs do not have to be included in two contiguous fields in LP-WUS. The additional, e.g., one, field(s) that do not carry any subgroup IDs may be set to a fixed value that indicate an invalid value / field or no subgroup indication.

[0250] In summary, the following options for LP-WUS may be considered to support large number of paging subgroups with limited impact on coverage and / or resource utilization:

[0251] Option 1: LP-WUS carrying bitmap-based wake-up indication for subsets of the subgroups;

[0252] Option 1-1: subgroup-subset identification using association with LP-WUS MOs;

[0253] Option 1-2: subgroup-subset identification using a header;

[0254] Option 1-3: subgroup-subset identification using a preamble / frame sync;

[0255] Option 2: LP-WUS switching between bitmap and ID-based subgroup wakeup indication;

[0256] Option 2-1: Number of IDs in LP-WUS determined by a header;

[0257] Option 2-2: Number of IDs in LP-WUS determined by an end of frame delimiter; and

[0258] Option 2-3: Fixed number of IDs in LP-WUS with padding bits, if needed.

[0259] Features of these options can also be modified or combined.Procedures supporting dynamic PO and subgroup indication on dynamic PO and subgroup indication

[0260] Figure 17A illustrates an exemplary flow chart of a method 1700 for a UE's switching between Dynamic and legacy PO monitoring based on LP-WUS detection and a dynamic PO cutoff reference, in accordance with some embodiments. Although shown in a particular sequence, it should be appreciated that the steps of the method 1700 may be performed in any suitable sequence.

[0261] The method 1700 starts with step 1702 when a UE transmits its LP-WUR capability, which may include support of the dynamic PO feature. This capability may be signaled based on a feature group for LP-WUS. The UE receives LP-WUS / LP-WUR configuration using any of RRC and system information signaling. In some embodiments, the LP-WUS / LP-WUR configuration may include: an indication of a dynamic PO cutoff reference point, e.g., radio frame, configured as an offset from a UE configured paging frame; an indication of a reference point for LO monitoring configured as an offset from a UE configured paging frame; a duty cycle (periodicity) for LO monitoring configured as any of an indication to one of a set of preconfigured values, a multiplicative factor (including a fraction) of an I-DRX or eDRX cycle, and a number of, e.g., slots, subframes, frames; one or more offsets from the reference point to one or more initial LP-WUS MOs; a time gap between consecutive LP-WUS MOs within an LP- WUS MO group; a number of LP-WUS MO groups associated with an LO; a periodicity for LP-WUS MO groups within the associated LO; association of an LO to one or more POs; and / or LP-WUS transmission configuration details including any of data rate, coding scheme, coding rate, synchronizing / triggering preamble, payload size, and CRC length.

[0262] In step 1704, the UE determines LOs and / or associated LP-WUS MOs based on the received configuration. In some embodiments, the LOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LOs, the association of an LO to one or more POs, and the duty cycle for LO monitoring.

[0263] In other embodiments, the LP-WUS MOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LP-WUS MO groups, and a time gap between consecutive LP-WUS MOs within an LP-WUS MO group.

[0264] In yet other embodiments, the LP-WUS MOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LOs, the number of LP-WUS MO groups associated with the LOs, the periodicity for LP-WUS MO groups within the associated LOs, and a time gap between consecutive LP-WUS MOs within an LP-WUS MO group.

[0265] In step 1706, the UE (e.g., using LP-WUR) monitors according to the determined LOs and / or LP-WUS MOs and receives a first LP-WUS in a first LP-WUS MO within a first LO. In step 1708, the UE determines whether the first LO and / or the first LP-WUS MO where the first LP-WUS is detected falls before the dynamic PO cutoff reference point. In some embodiments, the determination is based on whether a first radio frame number of the first LO has lower value than the radio frame numbercorresponding to the dynamic PO cutoff reference point. In other embodiments, the determination is based on whether a radio frame number of the first LP-WUS MO, where the first LP-WUS is detected, has lower value than the radio frame number corresponding to the dynamic PO cutoff reference point.

[0266] In response to determining at step 1708 that the first LO and / or the first LP- WUS MO where the first LP-WUS is detected does not fall before the dynamic PO cutoff reference point, the method 1700 proceeds to step 1710. In step 1710, the UE receives a paging DCI in a second PO and a corresponding paging message, where the second PO is a legacy PO received inside any of a PTW and an ON period of an I-DRX cycle. In some embodiments, the paging DCI has a CRC scrambled by a legacy paging radio network temporaiy identifier (P-RNTI). After step 1710, the method 1700 proceeds to step 1714.

[0267] In response to determining at step 1708 that the first LO and / or the first LP- WUS MO where the first LP-WUS is detected falls before the dynamic PO cutoff reference point, the method 1700 proceeds to step 1712. In step 1712, the UE receives a DCI in a first PO and a corresponding paging message, where the first PO is a dynamic PO received outside any of a PTW and an ON period of a default configured I-DRX cycle. In some embodiments, the paging DCI has a CRC that is scrambled by a P-RNTI. In other embodiments, the received paging DCI has a CRC that is scrambled by an alternative paging RNTI (e.g., AP-RNTI) or a dynamic paging RNTI (e.g., DP-RNTI).

[0268] After step 1710 or step 1712, the method 1700 proceeds to step 1714. In step 1714, based on the received paging DCI and paging message, the UE either initiates an RRC connection establishment or resume procedure, or continues operating in RRC Idle / Inactive state. After step 1714, the method 1700 ends.

[0269] In some embodiments when the UE misses the paging DCI when monitoring the first PO (dynamic PO), the UE may monitor and receive the paging DCI in the second PO (legacy PO). In some embodiments, the UE may miss the paging DCI if a DCI with a CRC scrambled by P-RNTI or AP-RNTI is not detected in the first PO. In other embodiments, the UE may miss the paging DCI if the MR wakes up, i.e., UE completes transition from the deep sleep state to the active state, at a later radio subframe or radio frame than that of the first PO.

[0270] The method 1700 illustrates the decision-making process and actions taken by a UE to support dynamic PO monitoring based on LP-WUS detection timing relative to a cutoff reference point, enabling lower latency paging while maintaining power efficiency.

[0271] Figure 17B illustrates an exemplary sequence diagram of the method 1700 (see Figure 17A), in accordance with some embodiments. Although shown in a particular sequence, it should be appreciated that the steps of the sequence diagram may beperformed in any suitable sequence. Arrows between timelines of the UE 114 and one or more network-side devices 1720 indicate directions of signal transmission between the UE 114 and the one or more network-side devices 1720. The one or more network-side devices 1720 may comprise one or more base stations, one or more intermediate nodes, one or more assist nodes, combinations thereof, or the like. In an embodiment, the one or more network-side devices 1720 comprise a single base station (e.g., base station 102 of Figure 1).

[0272] In step 1702, a respective one of the one or more network-side devices 1720 receives from the UE 114 its LP-WUR capability, which may include support of the dynamic PO feature. This capability may be signaled based on a feature group for LP- WUS. A respective one of the one or more network-side devices 1720 transmits to the UE 114 LP-WUS / LP-WUR configuration using any of RRC and system information signaling. In some embodiments, the LP-WUS / LP-WUR configuration may include: an indication of a dynamic PO cutoff reference point, e.g., radio frame, configured as an offset from a UE configured paging frame; an indication of a reference point for LO monitoring configured as an offset from a UE configured paging frame; a duty cycle (periodicity) for LO monitoring configured as any of an indication to one of a set of preconfigured values, a multiplicative factor (including a fraction) of an I-DRX or eDRX cycle, and a number of, e.g., slots, subframes, frames; one or more offsets from the reference point to one or more initial LP-WUS MOs; a time gap between consecutive LP- WUS MOs within an LP-WUS MO group; a number of LP-WUS MO groups associated with an LO; a periodicity for LP-WUS MO groups within the associated LO; association of an LO to one or more POs; and / or LP-WUS transmission configuration details including any of data rate, coding scheme, coding rate, synchronizing / triggering preamble, payload size, and CRC length.

[0273] In step 1704, the UE 114 determines LOs and / or associated LP-WUS MOs based on the received configuration. In some embodiments, the LOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LOs, the association of an LO to one or more POs, and the duty cycle for LO monitoring.

[0274] In other embodiments, the LP-WUS MOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LP-WUS MO groups, and a time gap between consecutive LP-WUS MOs within an LP-WUS MO group.

[0275] In yet other embodiments, the LP-WUS MOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LOs, the number of LP-WUS MO groupsassociated with the LOs, the periodicity for LP-WUS MO groups within the associated LOs, and a time gap between consecutive LP-WUS MOs w ithin an LP-WUS MO group.

[0276] In step 1706, the UE (e.g., using LP-WUR) monitors according to the determined LOs and / or LP-WUS MOs and receives a first LP-WUS in a first LP-WUS MO within a first LO from a respective one of the one or more network-side devices 1720. In step 1708, the UE determines whether the first LO and / or the first LP-WUS MO where the first LP-WUS is detected falls before the dynamic PO cutoff reference point. In some embodiments, the determination is based on whether a first radio frame number of the first LO has lower value than the radio frame number corresponding to the dynamic PO cutoff reference point. In other embodiments, the determination is based on whether a radio frame number of the first LP-WUS MO, where the first LP-WUS is detected, has lower value than the radio frame number corresponding to the dynamic PO cutoff reference point.

[0277] In response to determining at step 1708 that the first LO and / or the first LP- WUS MO where the first LP-WUS is detected does not fall before the dynamic PO cutoff reference point, the method 1700 proceeds to step 1710. In step 1710, a respective one of the one or more network-side devices 1720 transmits to the UE 114 a paging DO in a second PO and a corresponding paging message, where the second PO is a legacy PO received inside any of a PTW and an ON period of an I-DRX cycle. In some embodiments, the paging DCI has a CRC scrambled by a legacy paging radio network temporaiy identifier (P-RNTI). After step 1710, the method 1700 proceeds to step 1714.

[0278] In response to determining at step 1708 that the first LO and / or the first LP- WUS MO where the first LP-WUS is detected falls before the dynamic PO cutoff reference point, the method 1700 proceeds to step 1712. In step 1712, a respective one of the one or more network-side devices 1720 transmits to the UE 114 a DCI in a first PO and a corresponding paging message, where the first PO is a dynamic PO received outside any of a PTW and an ON period of a default configured I-DRX cycle. In some embodiments, the paging DCI has a CRC that is scrambled by a P-RNTI. In other embodiments, the received paging DCI has a CRC that is scrambled by an alternative paging RNTI (e.g., AP-RNTI) or a dynamic paging RNTI (e.g., DP-RNTI).

[0279] After step 1710 or step 1712, the method 1700 proceeds to step 1714. In step 1714, based on the received paging DCI and paging message, the UE 114 either initiates an RRC connection establishment or resume procedure, or continues operating in RRC Idle / Inactive state. After step 1714, the method 1700 ends.

[0280] Figure 18 illustrates an exemplary flow chart of a method 1800 for UE’s switching between ID-based and bitmap-based subgroup ID detection in an LP-WUS based on preambles, in accordance with some embodiments. Although shown in aparticular sequence, it should be appreciated that the steps of the method 1800 may be performed in any suitable sequence.

[0281] The method 1800 starts with step 1802 when a UE transmits its LP-WUR capability, which may include support of the dynamic PO feature. This capability may be signaled based on a feature group for LP-WUS. The UE receives LP-WUS / LP-WUR configuration using any of RRC and system information signaling. In some embodiments, the LP-WUS / LP-WUR configuration may include: an indication of a dynamic PO cutoff reference point, e.g., radio frame, configured as an offset from a UE configured paging frame; an indication of a reference point for LO monitoring configured as an offset from a UE configured paging frame; a duty cycle (periodicity) for LO monitoring configured as any of an indication to one of a set of preconfigured values, a multiplicative factor (including a fraction) of an I-DRX or eDRX cycle, and a number of, e.g., slots, subframes, frames; one or more offsets from the reference point to one or more initial LP-WUS MOs; a time gap between consecutive LP-WUS MOs within an LP- WUS MO group; a number of LP-WUS MO groups associated with an LO; a periodicity for LP-WUS MO groups within the associated LO; association of an LO to one or more POs; LP-WUS transmission configuration details including any of data rate, coding scheme, coding rate, synchronizing / triggering preamble, payload size, and CRC length; and / or one or more preamble(s), e.g., for frame synchronization, and mapping to one or more LP-WUS format(s).

[0282] In step 1804, the UE determines LOs and / or associated LP-WUS MOs based on the received configuration. In some embodiments, the LOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LOs, the association of an LO to one or more POs, and the duty cycle for LO monitoring.

[0283] In other embodiments, the LP-WUS MOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LP-WUS MO groups, and a time gap between consecutive LP-WUS MOs within an LP-WUS MO group.

[0284] In yet other embodiments, the LP-WUS MOs are determined based on the received indication of the reference point, the one or more offsets from the reference point to the one or more initial LP-WUS MOs of LOs, the number of LP-WUS MO groups associated with the LOs, the periodicity for LP-WUS MO groups within the associated LOs, and a time gap between consecutive LP-WUS MOs within an LP-WUS MO group.

[0285] In step 1806, the UE (e.g., using LP-WUR) monitors according to the determined LOs and / or LP-WUS MOs and receives a first preamble preceding a first LP-WUS in an LP-WUS MO w ithin an LO. In step 1808, the UE determines whether the first preamble is ID-based or bitmap-based.

[0286] In response to determining at step 1808 that the first preamble is bitmapbased, the method 1800 proceeds to step 1810. In step 1810, the UE determines a LP- WUS format, i.e., bitmap-based subgroup indication, based on the received first preamble and mapping configuration. In step 1812, the UE detects one or more subgroup ID(s) indicated to wake-up based on the indices of the bits set to value 1 in the payload of the first LP-WUS. After step 1812, the method 1800 proceeds to step 1818.

[0287] In response to determining at step 1808 that the first preamble is ID-based, the method 1800 proceeds to step 1814. In step 1814, the UE determines a LP-WUS format, i.e., ID-based subgroup indication, based on the received first preamble and mapping configuration. In step 1816, UE determines a number of subgroup IDs in the first LP-WUS based on any of a header preceding the first LP-WUS payload, an end of frame (EoF) delimiter succeeding the first LP-WUS payload, and a received configuration. Subsequently, the UE detects one or more subgroup ID(s) in the first LP- WUS based on the determined number of subgroup IDs.

[0288] After step 1812 or 1816, the method 1800 proceeds to step 1818. In step 1818, the UE determines its assigned or configured subgroup ID in the detected one or more subgroup ID(s) and monitors / receives a paging DO and a corresponding paging message. In step 1820, the UE initiates RRC connection establishment or resume procedure or continues operating in RRC Idle / Inactive state based on the received paging DCI and paging message. After step 1820, the method 1800 ends.

[0289] The method 1800 illustrates how a UE can switch between different LP-WUS formats (ID-based or bitmap-based) based on the detected preamble. This approach allows the system to use the most efficient format based on the current paging requirements - the Compact Format with ID-based indication is more efficient when only a small number of subgroups need to be woken up or the Normal Format with bitmapbased indication is more appropriate when a larger number of subgroups need to be woken up. By using the preamble to indicate the format, the system can dynamically adapt to different paging scenarios while minimizing overhead and optimizing resource utilization.On wake-up delay reporting and LO determination

[0290] Figure 19A illustrates an exemplary flow chart of a method 1900 for UE's wake-up delay reporting and procedure upon receiving LO / PO offset values, in accordance w ith some embodiments. Although shown in a particular sequence, it shouldbe appreciated that the steps of the method 1900 may be performed in any suitable sequence.

[0291] The method 1900 starts w ith step 1902 when the UE transmits its LP-WUR capability report including a first wake-up delay value from a first set of candidate values. In step 1904, the UE receives LP-WUS configuration including a second set of offset values between one or more LO(s) and one or more reference PO(s). In other embodiments, the second set may be an ordered list, which includes one or more offset values that correspond to the wake-up delay values. In step 1906, the UE determines whether at least one value in the second set is greater than or equal to the first wake-up delay value.

[0292] In response to at least determining at step 1906 that at least one value in the second set is not greater than or equal to the first wake-up delay value, the method 1900 proceeds to step 1908. In step 1908, the UE skips LP-WUS monitoring and performs PDCCH (e.g., PO) monitoring directly according to a configured paging cycle (i.e., default and / or UE-specific). In other embodiments, the UE may select the offset value corresponding to the first wake-up delay value based on the second set being an ordered list. After step 1908, the method 1900 optionally proceeds back to step 1902. In some embodiments, the UE updates LP-WUR capability report including a second wake-up delay value from the first set of candidate values when proceeding back to step 1902, wherein the second wake-up delay value is larger than or equal to at least the smallest value in the second set. In other embodiments, the second wake-up delay value is larger than or equal to at least the first value in the second set based on the second set being an ordered list starting by the smallest value.

[0293] In response to at least determining at step 1906 that at least one value in the second set is greater than or equal to the first wake-up delay value, the method 1900 proceeds to step 1910. In step 1910, the UE selects the smallest offset value that is greater than or equal to the first wake-up delay value for LO determination and LP-WUS monitoring to trigger PDCCH (e.g., PO) monitoring. In step 1912, the UE determines LOs and / or associated LP_WUS MOs based on the selected smallest offset value and the received configuration. In step 1914, the UE (e.g., using LP-WUR) monitors, according to the determined LOs and / or LP-WUS MOs, and receives an LP-WUS in an LP-WUS MO within the LO. In other embodiments, the UE receives an LP-WUS in the determined LO and skips one or more first PO(s) after a time offset (e.g., from the determined LO) corresponding to the smallest offset value, where the number of one or more first PO(s) may be determined based on any of the first wake-up delay value, the smallest offset value, and the configured paging cycle (default and / or UE-specific). In step 1916, the UE monitors and receives a DCI in a reference PO and a corresponding paging message. Insome embodiments, the received paging DCI has a CRC that is scrambled by a P-RNTI. In step 1918, the UE initiates RRC connection establishment or resume procedure or continues operating in RRC Idle / Inactive state based on the received paging DCI and paging message. After step 1918, the method 1900 ends.

[0294] The method 1900 illustrates how a UE reports its wake-up delay capability and selects appropriate offset values for LP-WUS monitoring based on the relationship between its reported wake-up delay and the configured offset values. This approach ensures that the UE can properly wake up its main radio in time to monitor the appropriate paging occasions after detecting an LP-WUS, while optimizing power efficiency based on the UE's specific wake-up delay characteristics.

[0295] Figure 19B illustrates an exemplary sequence diagram of the method 1900(see Figure 19A), in accordance with some embodiments. Although shown in a particular sequence, it should be appreciated that the steps of the sequence diagram may be performed in any suitable sequence. Arrows between timelines of the UE 114 and one or more network-side devices 1920 indicate directions of signal transmission between the UE 114 and the one or more network-side devices 1920. The one or more network-side devices 1920 may comprise one or more base stations, one or more intermediate nodes, one or more assist nodes, combinations thereof, or the like. In an embodiment, the one or more network-side devices 1920 comprise a single base station (e.g., base station 102 of Figure 1).

[0296] In step 1902, a respective one of the one or more network-side devices 1920 receives from the UE 114 its LP-WUR capability report including a first wake-up delay value from a first set of candidate values. In step 1904, a respective one of the one or more network-side devices 1920 transmits to the UE 114 LP-WUS configuration including a second set of offset values between one or more LO(s) and one or more reference PO(s). In other embodiments, the second set may be an ordered list, which includes one or more offset values that correspond to the wake-up delay values. In step 1906, the UE 114 determines whether at least one value in the second set is greater than or equal to the first wake-up delay value.

[0297] In response to at least determining at step 1906 that at least one value in the second set is not greater than or equal to the first wake-up delay value, the method 1900 proceeds to step 1908. In step 1908, the UE 114 skips LP-WUS monitoring and performs PDCCH (e.g., PO) monitoring directly according to a configured paging cycle (i.e., default and / or UE-specific). In other embodiments, the UE may select the offset value corresponding to the first wake-up delay value based on the second set being an ordered list. After step 1908, the method 1900 optionally proceeds back to step 1902. In some embodiments, the UE 114 updates LP-WUR capability report including a second wake-updelay value from the first set of candidate values when proceeding back to step 1902, wherein the second wake-up delay value is larger than or equal to at least the smallest value in the second set. In other embodiments, the second wake-up delay value is larger than or equal to at least the first value in the second set based on the second set being an ordered list starting by the smallest value.

[0298] In response to at least determining at step 1906 that at least one value in the second set is greater than or equal to the first wake-up delay value, the method 1900 proceeds to step 1910. In step 1910, the UE 114 selects the smallest offset value that is greater than or equal to the first wake-up delay value for LO determination and LP-WUS monitoring to trigger PDCCH (e.g., PO) monitoring. In step 1912, the UE 114 determines LOs and / or associated LP_WUS MOs based on the selected smallest offset value and the received configuration. In step 1914, the UE (e.g., using LP-WUR) monitors, according to the determined LOs and / or LP-WUS MOs, and receives from a respective one of the one or more network-side devices 1920 an LP-WUS in an LP-WUS MO within the LO. In other embodiments, the UE 114 receives from a respective one of the one or more network-side devices 1920 an LP-WUS in the determined LO and skips one or more first PO(s) after a time offset (e.g., from the determined LO) corresponding to the smallest offset value, where the number of one or more first PO(s) may be determined based on any of the first wake-up delay value, the smallest offset value, and the configured paging cycle (default and / or UE-specific). In step 1916, the UE 114 monitors and receives from a respective one of the one or more network-side devices 1920 a DCI in a reference PO and a corresponding paging message. In some embodiments, the received paging DCI has a CRC that is scrambled by a P-RNTI. In step 1918, the UE 114 initiates RRC connection establishment or resume procedure or continues operating in RRC Idle / Inactive state based on the received paging DCI and paging message. After step 1918, the method 1900 ends.

[0299] Figure 20 illustrates an exemplary flow chart of a method 2000 for UE’s wake-up delay reporting and procedure for LO reference point and reference PO / PF determination, in accordance with some embodiments. Although shown in a particular sequence, it should be appreciated that the steps of the method 2000 may be performed in any suitable sequence.

[0300] The method 2000 starts with step 2002 when the UE transmits its LP-WUR capability report including a first wake-up delay value from a first set of candidate values. In step 2004, the UE receives paging and LP-WUS configuration including any of a configured PF offset, a first default paging cycle, a first UE-specific paging cycle, and a second set of offset values between one or more LO(s) and one or more reference PO(s). In some embodiments, the configured PF offset, the first set of candidate values, the firstdefault paging cycle, the first UE-specific paging cycle, and the second set of offset values may be received in any of system information, RRC message, and upper layers.

[0301] In step 2006, the UE determines a first offset value and a second offset value in the second set, where the first offset value is a value greater than or equal to the first wake-up delay value, and where the second offset value is the largest value in the second set. In some embodiments, the UE further determines a second default paging cycle based on any of the first default paging cycle and the first UE-specific paging cycle. In an embodiment, the second default paging cycle is the first default paging cycle. In another embodiment, the second default paging cycle is the shortest of the first default paging cycle and the first UE-specific paging cycle.

[0302] In step 2008, the UE determines a first SFN of a default reference paging Occasion / Frame (PO / PF) based on any of the determined second default paging cycle, a UE ID, and the configured PF offset. In an embodiment, the first SFN is determined based on the legacy formula for determination of the PF’s SFN. In step 2010, the UE determines an LO reference point (e.g., a second SFN that contains the beginning of the LO) based on the determined first SFN and the second offset value.

[0303] In step 2012, the UE determines a third SFN corresponding to a UE-specific reference paging Occasion / Frame (PO / PF) based on the determined LO reference point (e.g., the second SFN) and the first offset value. In another embodiment, the third SFN may be determined based on a second UE-specific paging cycle and the legacy formula for determination of the PF’s SFN, where the second UE-specific paging cycle may be determined based on pre-configuration.

[0304] In step 2014, the UE (e.g., using LP-WUR) monitors, according to the determined LO reference point and LP-WUS configuration, and receives an LP-WUS in an LP-WUS MO within the LO. In step 2016, the UE monitors and receives a DCI in the UE-specific reference PO and a corresponding paging message. In step 2018, the UE initiates RRC connection establishment or resume procedure or continues operating in RRC Idle / Inactive state based on the received paging DCI and paging message. After step 2018, the method 2000 ends.

[0305] The method 2000 ensures that the timing relationship between the LP-WUS occasion and the paging occasion properly accounts for the UE's wake-up delay, allowing the main radio sufficient time to wake up after LP-WUS detection before it needs to monitor the paging occasion. This optimizes both power efficiency and latency while accommodating UEs with different wake-up delay characteristics.

[0306] Figure 21 illustrates an example communications system 2100. Communications system 2100 includes an access node 2110 serving user equipments (UEs) with coverage area 2101, such as UEs 2120. In a first operating mode,communications to and from a UE passes through access node 2110 with a coverage area 2101. The access node 2110 is connected to a backhaul network 2115 for connecting to the internet, operations and management, and so forth. In a second operating mode, communications to and from a UE do not pass through access node 2110, however, access node 2110 typically allocates resources used by the UE to communicate when specific conditions are met. Communications between a pair of UEs 2120 can use a sidelink connection (shown as two separate one-way connections 2125). In Figure 21, the sideline communication is occurring between two UEs operating inside of coverage area 2101. However, sidelink communications, in general, can occur when UEs 2120 are both outside coverage area 2101, both inside coverage area 2101, or one inside and the other outside coverage area 2101. Communication between a UE and access node pair occur over uni-directional communication links, where the communication links between the UE and the access node are referred to as uplinks 2130, and the communication links between the access node and UE is referred to as downlinks 2135.

[0307] Access nodes may also be commonly referred to as Node Bs, evolved Node Bs(eNBs), next generation (NG) Node Bs (gNBs), master eNBs (MeNBs), secondary' eNBs (SeNBs), master gNBs (MgNBs), secondary gNBs (SgNBs), network controllers, control nodes, base stations, access points, transmission points (TPs), transmission-reception points (TRPs), cells, carriers, macro cells, femtocells, pico cells, and so on, while UEs may also be commonly referred to as mobile stations, mobiles, terminals, users, subscribers, stations, and the like. Access nodes may provide wireless access in accordance with one or more wireless communication protocols, e.g., the Third Generation Partnership Project (3GPP) long term evolution (LTE), LTE advanced (LTE- A), 5G, 5G LTE, 5G NR, sixth generation (6G), High Speed Packet Access (HSPA), the IEEE 802.11 family of standards, such as 802.na / b / g / n / ac / ad / ax / ay / be, etc. While it is understood that communications systems may employ multiple access nodes capable of communicating with a number of UEs, only one access node and two UEs are illustrated for simplicity.

[0308] Figure 22 illustrates an example communication system 2200. In general, the system 2200 enables multiple wireless or wired users to transmit and receive data and other content. The system 2200 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0309] In this example, the communication system 2200 includes electronic devices (ED) 22toa-22toc, radio access networks (RANs) 222oa-222ob, a core network 2230, a public switched telephone network (PSTN) 2240, the Internet 2250, and other networks2260. While certain numbers of these components or elements are shown in Figure 22, any number of these components or elements may be included in the system 2200.

[0310] The EDs 22ioa-22ioc are configured to operate or communicate in the system 2200. For example, the EDs 22ioa-22toc are configured to transmit or receive via wireless or wired communication channels. Each ED 22ioa-22ioc represents any suitable end user device and may include such devices (or may be referred to) as a user equipment or device (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, personal digital assistant (PDA), smartphone, laptop, computer, touchpad, wireless sensor, or consumer electronics device.

[0311] The RANs 222oa-222ob here include base stations 227oa-22yob, respectively. Each base station 227oa-22yob is configured to wirelessly interface with one or more of the EDs 22toa-22ioc to enable access to the core network 2230, the PSTN 2240, the Internet 2250, or the other networks 2260. For example, the base stations 227oa-227ob may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNB), a Next Generation (NG) NodeB (gNB), a gNB centralized unit (gNB-CU), a gNB distributed unit (gNB-DU), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router. The EDs 22ioa-22ioc are configured to interface and communicate with the Internet 2250 and may access the core network 2230, the PSTN 2240, or the other networks 2260.

[0312] In the embodiment shown in Figure 22, the base station 2270a forms part of the RAN 2220a, which may include other base stations, elements, or devices. Also, the base station 21270b forms part of the RAN 2220b, which may include other base stations, elements, or devices. Each base station 2270a-2270b operates to transmit or receive wireless signals within a particular geographic region or area, sometimes referred to as a “cell.” In some embodiments, multiple-input multiple-output (MIMO) technology may be employed having multiple transceivers for each cell.

[0313] The base stations 227Oa-227Ob communicate with one or more of the EDs 22ioa-22ioc over one or more air interfaces 2290 using wireless communication links. The air interfaces 2290 may utilize any suitable radio access technology.

[0314] It is contemplated that the system 2200 may use multiple channel access functionality, including such schemes as described above. In particular embodiments, the base stations and EDs implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may be utilized.

[0315] The RANs 2220a-2220b are in communication with the core network 2230 to provide the EDs 22ioa-22ioc with voice, data, application, Voice over InternetProtocol (VoIP), or other services. Understandably, the RANs 222oa-222ob or the core network 2230 may be in direct or indirect communication with one or more other RANs (not shown). The core network 2230 may also se e as a gateway access for other networks (such as the PSTN 2240, the Internet 2250, and the other networks 2260). In addition, some or all of the EDs 22ioa-22ioc may include functionality for communicating w ith different wireless networks over different wireless links using different wireless technologies or protocols. Instead of wireless communication (or in addition thereto), the EDs may communicate via wired communication channels to a service provider or switch (not shown), and to the Internet 2250.

[0316] Although Figure 22 illustrates one example of a communication system, various changes may be made to Figure 22. For example, the communication system 2200 could include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0317] Figures 23A and 23B illustrate example devices that may implement the methods and teachings according to this disclosure. In particular, Figure 23A illustrates an example ED 2310, and Figure 23B illustrates an example base station 2370. These components could be used in the system 2200 or in any other suitable system.

[0318] As shown in Figure 23A, the ED 2310 includes at least one processing unit 2300. The processing unit 2300 implements various processing operations of the ED 2310. For example, the processing unit 2300 could perform signal coding, data processing, power control, input / output processing, or any other functionality enabling the ED 2310 to operate in the system 2200. The processing unit 2300 also supports the methods and teachings described in more detail above. Each processing unit 2300 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 2300 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0319] The ED 2310 also includes at least one transceiver 2302. The transceiver 2302 is configured to modulate data or other content for transmission by at least one antenna or NIC (Network Interface Controller) 2304. The transceiver 2302 is also configured to demodulate data or other content received by the at least one antenna 2304. Each transceiver 2302 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or by wire. Each antenna 2304 includes any suitable structure for transmitting or receiving wireless or wired signals. One or multiple transceivers 2302 could be used in the ED 2310, and one or multiple antennas 2304 could be used in the ED 2310. Although shown as a singlefunctional unit, a transceiver 2302 could also be implemented using at least one transmitter and at least one separate receiver.

[0320] The ED 2310 further includes one or more input / output devices 2306 or interfaces (such as a wired interface to the Internet 2250). The input / output devices 2306 facilitate interaction with a user or other devices (network communications) in the network. Each input / output device 2306 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0321] In addition, the ED 2310 includes at least one memoiy 2308. The memory 2308 stores instructions and data used, generated, or collected by the ED 2310. For example, the memory' 2308 could store software or firmware instructions executed by the processing unit(s) 2300 and data used to reduce or eliminate interference in incoming signals. Each memory 2308 includes any suitable volatile or non-volatile storage and retrieval device(s). Any suitable type of memory may be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and the like.

[0322] As shown in Figure 23B, the base station 2370 includes at least one processing unit 2350, at least one transceiver 2352, which includes functionality for a transmitter and a receiver, one or more antennas 2356, at least one memory 2358, and one or more input / output devices or interfaces 2366. A scheduler, which would be understood by one skilled in the art, is coupled to the processing unit 2350. The scheduler could be included within or operated separately from the base station 2370. The processing unit 2350 implements various processing operations of the base station 2370, such as signal coding, data processing, power control, input / output processing, or any other functionality. The processing unit 2350 can also support the methods and teachings described in more detail above. Each processing unit 2350 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 2350 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0323] Each transceiver 2352 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 2352 further includes any suitable structure for processing signals received wirelessly or by wire from one or more EDs or other devices. Although shown combined as a transceiver 2352, a transmitter and a receiver could be separate components. Each antenna 2356 includes any suitable structure for transmitting or receiving wireless or wired signals. While a common antenna 2356 is shown here as being coupled to thetransceiver 2352, one or more antennas 2356 could be coupled to the transceiver(s) 2352, allowing separate antennas 2356 to be coupled to the transmitter and the receiver if equipped as separate components. Each memoiy 2358 includes any suitable volatile or non-volatile storage and retrieval device(s). Each input / output device 2366 facilitates interaction with a user or other devices (network communications) in the network. Each input / output device 2366 includes any suitable structure for providing information to or receiving / providing information from a user, including network interface communications.

[0324] Figure 24 is a block diagram of a computing system 2400 that may be used for implementing the devices and methods disclosed herein. For example, the computing system can be any entity of UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). Specific devices may utilize all of the components shown or only a subset of the components, and levels of integration may vaiy from device to device. Furthermore, a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 2400 includes a processing unit 2402. The processing unit includes a central processing unit (CPU) 2414, memory72408, and may further include a mass storage device 2404, a video adapter 2410, and an I / O interface 2412 connected to a bus 2420.

[0325] The bus 2420 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. The CPU 2414 may comprise any type of electronic data processor. The memoiy 2408 may comprise any type of non-transitory system memory such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In an embodiment, the memoiy 2408 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.

[0326] The mass storage 2404 may comprise any type of non-transitoiy storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus 2420. The mass storage 2404 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, or an optical disk drive.

[0327] The video adapter 2410 and the I / O interface 2412 provide interfaces to couple external input and output devices to the processing unit 2402. As illustrated, examples of input and output devices include a display 2418 coupled to the video adapter 2410 and a mouse, keyboard, or printer 2416 coupled to the I / O interface 2412. Other devices may be coupled to the processing unit 2402, and additional or fewer interfacecards may be utilized. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for an external device.

[0328] The processing unit 2402 also includes one or more network interfaces 2406, which may comprise wired links, such as an Ethernet cable, or wireless links to access nodes or different networks. The network interfaces 2406 allow the processing unit 2402 to communicate with remote units via the networks. For example, the netw ork interfaces 2406 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In an embodiment, the processing unit 2402 is coupled to a local-area network 2422 or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, or remote storage facilities.

[0329] It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a performing unit or module, a generating unit or module, an obtaining unit or module, a setting unit or module, an adjusting unit or module, an increasing unit or module, a decreasing unit or module, a determining unit or module, a modifying unit or module, a reducing unit or module, a removing unit or module, or a selecting unit or module. The respective units or modules may be hardw are, software, or a combination thereof. For instance, one or more of the units or modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0330] Although the description has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. For example, the technique described in this disclosure may include additional or fewer operations than those shown and described and may be carried out or performed in a different order (e.g., similar steps in the reversed order compared to the described order of operations). For another example, steps described herein apply to various sides of network communications (for example, between a base station and a UE or between two UEs), and where steps for one side are disclosed then corresponding steps on the other side are also understood to be disclosed by those of skill in the art. Moreover, the scope of the disclosure is not intended to be limited to the particular embodiments described herein, as one of ordinary skill in the art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same functionor achieve substantially the same result as the corresponding embodiments described herein. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

Claims

What is Claimed:

1. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: transmitting a first indication of a first wake-up delay value from a first set of candidate wake-up delay values; receiving a low-power wake-up signal (LP-WUS) configuration indicating a second set of one or more offset values, wherein a first offset value in the second set is a time offset between a first LP-WUS occasion (LO) and a first reference paging occasion (PO); based on at least one offset value in the second set being larger than or equal to the first wake-up delay value, receiving an LP-WUS in a second LO, wherein the second LO is determined based on a second offset value in the second set, the second offset value being a smallest value in the second set that is larger than or equal to the first wake-up delay value; and receiving a paging downlink control information (DCI) in a second reference PO based on the LP-WUS and a corresponding paging message.

2. The method of claim t, wherein the first set of candidate wake-up delay values comprise wake-up delay values for transitioning from a low-power wake-up radio (LP- WUR) to a main radio of the WTRU.

3. The method of any of claims 1-2, wherein receiving the LP-WUS in the second LO comprises receiving the LP-WUS in one or more LP-WUS monitoring occasions (MOs) of the second LO.

4. The method of any of claims 1-4, further comprising: receiving a paging configuration indicating a configured paging frame (PF) offset, a first default paging cycle, and a first user equipment (UE)-specific paging cycle.

5. The method of claim 4, further comprising: determining the first reference PO based on the paging configuration.

6. The method of any of claims 1-5, further comprising: determining the second LO and one or more LP-WUS MOs of the second LO based on the second offset value in the second set.

7. The method of any of claims 1-6, wherein the first offset value in the second set is a time offset between an end of the first LO and a start of the first reference PO.

8. The method of claim 7, wherein the end of the first LO is an end of a last LP-WUS MO in the first LO.

9. The method of any of claims 1-8, further comprising: determining an Ithoffset value Oj of the one or more offset val lies in the second set based on a minimum time offset To, a second UE -specific paging cycle Tspec, and an integer multiple value specific to an Ithoffset Ntaccording to 0, = To+ NLTspec.

10. The method of any of claims 1-9, wherein the first offset value is a largest offset value in the second set.

11. The method of any of claims 6-10, wherein the second reference PO is the same as the first reference PO, and the second LO is further determined based on the second offset value and the first reference PO, the second offset value being different from the first offset value.

12. The method of any of claims 6-10, wherein the second LO is the same as the first LO, and the second reference PO is further determined based on the second offset value and the first LO, the second offset value being different from the first offset value.

13. The method of claim 12, wherein the first reference PO is a default reference PO, and the second reference PO is a UE-specific reference PO.

14. The method of any of claims 6-13, wherein the determining the second LO is based on at least one offset value in the second set being larger than or equal to the first wake-up delay value.

15. The method of any of claims 1-14, further comprising, before the transmitting the first indication of the first wake-up delay value: transmitting a second indication of a second wake-up delay value from the first set of candidate wake-up delay values; receiving a second LP-WUS configuration indicating a third set of one or more offset values, wherein a third offset value in the third set is a time offset between a third LO and a third PO; andin response to the one or more offset values in the third set all being smaller than the second wake-up delay value, skipping LP-WUS monitoring corresponding to the second LP-WUS configuration and monitoring POs according to the paging configuration, wherein the first wake-up delay value is less than the second wake-up delay value.

16. The method of claim 15, wherein the second wake-up delay value is smaller than or equal to at least one offset value from the one or more offset values in the second set.

17. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: receiving a low-power wake-up signal (LP-WUS) configuration, the LP-WUS configuration indicating an LP-WUS monitoring occasion (MO) configuration and a cutoff reference point for paging occasion (PO) monitoring; receiving a first LP-WUS in a first LP-WUS MO based on the LP-WUS MO configuration; and receiving a paging downlink control information (DCI) in a paging occasion (PO) and a corresponding paging message, in accordance to the first LP-WUS MO occurring before the cutoff reference point for the PO monitoring.

18. The method of claim 17, wherein the LP-WUS MO configuration is part of an LP- WUS occasion (LO) configuration indicating at least one of a reference point, an LO periodicity, one or more offsets from the reference point to one or more initial LP-WUS MOs, a time gap between consecutive LP-WUS MOs in an LP-WUS MO group, a number of the LP-WUS MO groups in the LO, or a periodicity for LP-WUS MO groups in the LO.

19. The method of any of claims 17-18, wherein the PO is received outside any of a paging time window (PTW) or an ON period of a default configured idle mode discontinuous reception (I-DRX) cycle.

20. The method of any of claims 17-19, wherein the paging DCI has a cyclic redundancy check (CRC) that is scrambled with one of a paging radio network temporary identifier (P-RNT1) or an alternative paging RNT1 (AP-RNT1).

21. The method of claim 20, wherein the CRC is scrambled with the AP-RNTI, and the AP-RNTI is for user equipment (UE) supporting the PO monitoring.

22. The method of any of claims 17-21, wherein the first LP-WUS MO occurring before the cutoff reference point is determined based on a first radio frame number of the first LP-WUS MO being less than a radio frame number corresponding to the cutoff reference point.

23. The method of any of claims 17-22, further comprising: transmitting a physical random access channel (PRACH) preamble based on the paging DCI and the corresponding paging message.

24. The method of claim 23, wherein the transmitting the PRACH preamble is in response to detection of the WTRU configured or assigned identifier in the corresponding paging message.

25. The method of claim 17, further comprising: receiving a second LP-WUS in a second LP-WUS MO based on the LP-WUS MO configuration; and receiving a second paging DCI in a legacy PO and a second corresponding paging message, in accordance to the second LP-WUS MO occurring after the cutoff reference point for the PO monitoring.

26. The method of claim 25, wherein the legacy PO is received inside one of a paging time window (PTW) and an ON period of a default configured I-DRX cycle.

27. The method of any of claims 25-26, wherein the second LP-WUS MO occurring after the cutoff reference point is determined based on a second radio frame number of the second LP-WUS MO being greater than a radio frame number corresponding to the cutoff reference point.

28. The method of any of claims 25-27, wherein the paging DCI has a CRC that is scrambled with a P-RNTI.

29. The method of any of claims 25-28, further comprising: transmitting a PRACH preamble based on the paging DCI and the corresponding paging message.

30. The method of claim 29, wherein the transmitting the PRACH preamble is in response to detection of the WTRU configured or assigned identifier in the corresponding paging message.

31. A method implemented in one or more network-side devices, the method comprising: receiving a first indication of a first wake-up delay value from a first set of candidate wake-up delay values; transmitting a low-power wake-up signal (LP-WUS) configuration indicating a second set of one or more offset values, wherein a first offset value in the second set is a time offset between a first LP-WUS occasion (LO) and a first reference paging occasion (PO); based on at least one offset value in the second set being larger than or equal to the first wake-up delay value, transmitting an LP-WUS in a second LO, wherein the second LO is determined based on a second offset value in the second set, the second offset value being a smallest value in the second set that is larger than or equal to the first wake-up delay value; and transmitting a paging downlink control information (DCI) in a second reference PO based on the LP-WUS and a corresponding paging message.

32. The method of claim 31, wherein the first set of candidate wake-up delay values comprise wake-up delay values for transitioning from a low-power wake-up radio (LP- WUR) to a main radio of a user equipment.

33. The method of any of claims 31-32, wherein transmitting the LP-WUS in the second LO comprises transmitting the LP-WUS in one or more LP-WUS monitoring occasions (MOs) of the second LO.

34. The method of any of claims 31-33, further comprising: transmitting a paging configuration indicating a configured paging frame (PF) offset, a first default paging cycle, and a first user equipment (UE)-specific paging cycle.

35. The method of any of claims 31-34, wherein the first offset value in the second set is a time offset between an end of the first LO and a start of the first reference PO.

36. The method of claim 35, wherein the end of the first LO is an end of a last LP- WUS MO in the first LO.37- The method of any of claims 31-36, wherein the first offset value is a largest offset value in the second set.

38. The method of any of claims 31-37, wherein the first reference PO is a default reference PO, and the second reference PO is a UE-specific reference PO.

39. The method of any of claims 31-38, further comprising, before the receiving the first indication of the first wake-up delay value: receiving a second indication of a second wake-up delay value from the first set of candidate wake-up delay values; and transmitting a second LP-WUS configuration indicating a third set of one or more offset values, wherein a third offset value in the third set is a time offset between a third LO and a third PO.

40. The method of claim 39, wherein the second wake-up delay value is smaller than or equal to at least one offset value from the one or more offset values in the second set.

41. The method of any of claims 31-40, wherein the one or more network-side devices comprise one or more base stations, one or more intermediate nodes, or one or more assist nodes.

42. The method of any of claims 31-41, wherein the one or more network-side devices comprise a single base station.

43. A method implemented in one or more network-side devices, the method comprising: transmitting a low-power wake-up signal (LP-WUS) configuration, the LP-WUS configuration indicating an LP-WUS monitoring occasion (MO) configuration and a cutoff reference point for paging occasion (PO) monitoring; transmitting a first LP-WUS in a first LP-WUS MO based on the LP-WUS MO configuration; and transmitting a paging downlink control information (DC1) in a paging occasion (PO) and a corresponding paging message, in accordance to the first LP-WUS MO occurring before the cutoff reference point for the PO monitoring.44- The method of claim 43, wherein the LP-WUS MO configuration is part of an LP- WUS occasion (LO) configuration indicating at least one of a reference point, an LO periodicity, one or more offsets from the reference point to one or more initial LP-WUS MOs, a time gap between consecutive LP-WUS MOs in an LP-WUS MO group, a number of the LP-WUS MO groups in the LO, or a periodicity for LP-WUS MO groups in the LO.

45. The method of any of claims 43-44, wherein the PO is transmitted outside any of a paging time window (PTW) or an ON period of a default configured idle mode discontinuous reception (I-DRX) cycle.

46. The method of any of claims 43-45, wherein the paging DCI has a cyclic redundancy check (CRC) that is scrambled with one of a paging radio network temporary identifier (P-RNTI) or an alternative paging RNTI (AP-RNTI).

47. The method of claim 46, wherein the CRC is scrambled with the AP-RNTI, and the AP-RNTI is for user equipment (UE) supporting the PO monitoring.

48. The method of any of claims 43-47, wherein the first LP-WUS MO occurring before the cutoff reference point is determined based on a first radio frame number of the first LP-WUS MO being less than a radio frame number corresponding to the cutoff reference point.

49. The method of any of claims 43-48, further comprising: receiving a physical random access channel (PRACH) preamble based on the paging DCI and the corresponding paging message.

50. The method of claim 43, further comprising: transmitting a second LP-WUS in a second LP-WUS MO based on the LP-WUS MO configuration; and transmitting a second paging DCI in a legacy PO and a second corresponding paging message, in accordance to the second LP-WUS MO occurring after the cutoff reference point for the PO monitoring.

51. The method of claim 50, wherein the legacy PO is transmitted inside one of a paging time window (PTW) and an ON period of a default configured I-DRX cycle.

52. The method of any of claims 50-51, wherein the second LP-WUS MO occurring after the cutoff reference point is determined based on a second radio frame number of the second LP-WUS MO being greater than a radio frame number corresponding to the cutoff reference point.

53. The method of any of claims 50-52, wherein the paging DCI has a CRC that is scrambled with a P-RNTI.

54. The method of any of claims 50-53, further comprising: receiving a PRACH preamble based on the paging DCI and the corresponding paging message.

55. The method of any of claims 43-54, wherein the one or more network-side devices comprise one or more base stations, one or more intermediate nodes, or one or more assist nodes.

56. The method of any of claims 43-55, wherein the one or more network-side devices comprise a single base station.

57. A user equipment, comprising: at least one processor; and a non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the user equipment to perform a method according to any of claims 1-16.

58. A user equipment, comprising: at least one processor; and a non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the user equipment to perform a method according to any of claims 17-30.

59. A base station, comprising: at least one processor; and a non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the base station to perform a method according to any of claims 31-42.

60. A base station, comprising: at least one processor; and a non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the base station to perform a method according to any of claims 43-56.

61. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a user equipment, cause the user equipment to perform a method according to any of claims 1-16.

62. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a user equipment, cause the user equipment to perform a method according to any of claims 17-30.

63. A non-transitoiy computer-readable medium having instructions stored thereon that, when executed by a base station, cause the base station to perform a method according to any of claims 31-42.

64. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a base station, cause the base station to perform a method according to any of claims 43-56.

Images