3GPP TSG RAN WG1 Meeting #121	R1-2503229
St. Julian’s, Malta, May 19 – 23, 2025
Agenda Item:	9.6.2
Source:	Futurewei
Title:	Remaining Issues on LP-WUS Operation in IDLE/INACTIVE modes
Document for:	Discussion/Decision 

Conclusion
This contribution discusses the remaining issues on LP-WUS/LP-SS configuration during operation in IDLE/INACTIVE state. The following summarizes our observations and proposals.
Observation 1: Determining the LP-WUS MOs based on the actually transmitted SSBs rather than the indicated subset of SSBs associated with LP-WUS/LP-SS may limit the number of LOs that can be configured per PF due to large span of resources needed for an LO.
Proposal 1: Support Alt2 that only LP-WUS MOs are determined assuming the N SSBs associated with LP-WUS/LP-SS which are determined by SIB for LP-WUS configuration.
Observation 2: LP-WUS design may allow for performance improvement using repetitions and longer codewords with more redundancy. Further, LP-SS design is based on same target SNR as LP-WUS, but should allow evaluation of exit condition for LP-WUS monitoring.
Proposal 2: Support Option 2 that separate configurations are provided for LP-WUS and LP-SS.
Observation 3: Given minimum LP-SS period of 160ms, an LP-SS frame-level offset can be more appropriate, which may be used to avoid overlap with SSB transmissions, CORESET-0, and/or Type0-PDCCH search space; and/or reduce inter-cell LP-SS interference.
Proposal 3: Support a frame-level offset along with the periodicity for LP-SS timing configuration.
Observation 4: Agreed LP-SS lengths result in transmission durations in range of 4-8 OFDM symbols, which is comparable to SSB. Therefore, existing SSB patterns within a first or a second half frame and with indicated starting OFDM symbol for candidate SSBs can be reused.
Proposal 4: Support the reuse of SSB patterns to obtain timing for candidate LP-SS within one or two frames depending on the configured LP-SS length and the Case for SSB pattern.
Observation 5: Combination of a fixed time-domain pattern configured by the gNB while utilizing configuration information available for idle/inactive UEs can provide the gNB with scheduling flexibility for other UEs’ signals and traffic without having to identify/indicate a complex time domain pattern that can vary across MOs/LOs.
Proposal 5: Support Alt 3 for UE’s determination of OFDM symbol availability for LP-WUS where a time-domain pattern (i.e., Alt 1B: Per-MO pattern, applicable for all MOs) configured by the gNB and configuration information available for idle/inactive UEs are combined.
Observation 6: With the support of a limited subset of coded bits lengths and Alt 3 for a simple time-domain pattern configuration by the gNB while accounting for potential variability of other signals with configuration known to idle/inactive UEs, then Alt A with a configured nominal MO duration can be supported.
Observation 7: With the support of a limited subset of coded bits lengths, it should be supported for Alt A that if the number of available OFDM symbols for at least a single LP-WUS transmission within the nominal MO duration is less than the minimum supported actual LP-WUS duration, then the MO can be considered as invalid and dropped.
Proposal 6: Support Alt A for the determination of the nominal MO duration with the following addition: If the number of available OFDM symbols for at least a single LP-WUS transmission within the nominal MO duration is less than the minimum supported actual LP-WUS duration, then the MO can be considered as invalid and dropped.
Observation 8: A symbol-level offset granularity can effectively be achieved using configured time-domain pattern per MO and nominal MO duration without the need for an additionally indicated parameter.
Observation 9: For the starting time of subsequent LP-WUS MOs in an LO w.r.t. a first MO, Alt 1 using an indicated offset for each of the subsequent LP-WUS MOs may incur unnecessary signaling overhead.
Observation 10: Existing search space configuration includes a slot-level periodicity and offset where the slot-level periodicity can be equivalent to the single gap in Alt 2A between the start of an MO and a previous MO (or set of previous MOs), and the search space slot-level offset can be equivalent to a slot-level offset for the first LP-WUS MO in an LO.
Observation 11: Existing search space configuration includes a duration and symbol-level pattern within a slot. The search space duration can be equivalent to a nominal MO duration and the symbol-level pattern within a slot can be equivalent to a per-MO time-domain pattern.
Proposal 7: For starting time of subsequent LP-WUS MOs in an LO w.r.t. a first MO, support Alt 2A using a single gap between the start of an MO and a previous MO (or set of previous MOs).
Proposal 8: Support definition of an LP-WUS search space including a slot-level single gap between the start of an MO and a previous MO (or set of previous MOs), a slot-level offset for the first LP-WUS MO in an LO, a nominal MO duration, and a per MO time-domain pattern.
Proposal 9: Support Alt 2 for how to handle UE capability report on the wake-up delay where the UE reports one of 3 capabilities and the exact values for each capability and SSB periodicity can be left to RAN4. 

3GPP TSG-RAN WG1 Meeting #121	R1-2503291
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2
Source:	Huawei, HiSilicon
Title:	Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode
Document for:	Discussion and Decision 

Conclusions
In this contribution, procedure for LP-WUS in idle/inactive are discussed. The following observations and proposals are made:
Observations:
For determination of the available symbol for LP-WUS, Alt 1 only and Alt 4 leads to too much complexity to gNB implementation.
For determination of the available symbol for LP-WUS, Alt 2 cannot avoid the overlap with possible legacy signal, e.g. TRS.
For the determination of starting time locations of the subsequent LP-WUS MOs in a LO, Alt 1 leads to too much signaling overhead.
For the determination of starting time locations of the first LP-WUS MO in a LO, slot-level offset may not be able to indicate the exact starting location of a MO due to the coarse granularity, and slot-level offset is not helpful for reducing signaling overhead.
For the nominal MO duration and actual LP-WUS duration,
Alt A may lead to too short LP-WUS length, where the coverage cannot be guaranteed
Alt C may lead to resource wasting
Alt D leads to too much complexity to gNB implementation
To avoid overlap of different LOs, a maximum duration of nominal LO can be configured/determined.
Transmitting LP-WUS/LP-SS via a subset of all SSB beams can be helpful for reducing the overhead without impacting the functionality of LP-WUS, for both vertical beam scenario and horizon beam scenario.
If gNB transmits LP-WUS/LP-SS via a subset of all SSB beams without notifying UE, the following issue will be introduced
Impact to T/F tracking and RRM measurement based on LP-SS
Impact to UE power saving gain since UE needs to detect LP-WUS in MOs corresponding to all SSB beams to avoid missing LP-WUS
Ping-pong issue for UE to switch between MR and LP-WUR 
Transmitting LP-WUS/LP-SS via a subset of all SSB beams does not impact to entry/exit condition.
RAN4 already agreed that for SSB periodicities smaller than 20ms, 20ms will be used for MR wake up delay. That is, for SSB periodicities smaller than 20ms, the wake-up delay is the ramping time + SSB number * 20ms.
Deploying LP-WUS in only some bands/carriers helps to reduce the cost of LP-WUR and the system overhead of the network, thus the number bands/carriers supported by LP-WUR can be less than for the MR.
Due to legacy frequency priority setting, UE may camp on a frequency without LP-WUS deployment, which leads no power saving gain to UE and resource wasting to gNB.
The effect of Solution 3 highly depends on gNB implementation, and it is difficult to configure a proper time duration during which the UE specific frequency priority list takes effect.
Both Solution 1 and solution 2 can enable UE to fully utilize LP-WUS.
Solution 2 can solve the overload issue, while Solution 1 cannot.
For SSB-based measurement in legacy, the unit of RSRP value is dBm per RE and the unit of RSSI value is dBm per 20RBs, the RSRQ = 20*RSRP/RSSI.
Based on previous agreements, the unit of the LP-RSRP value and the LP-RSSI value are the same, while based on the draft CR, the unit of the LP-RSRP value and the unit of the LP-RSSI value are different.


Proposals:
If gNB configures  POs mapped to one LO, and  subgroups per PO, for the determination of codepoint value, down-select between the following options
Option 1:
For a subgroup whose subgroupID =  and relative PO index = , the codepoint value of this subgroup is . 
The common codepoint value for PO index =  is .
Option 2:
For a subgroup whose subgroupID =  and relative PO index = , the codepoint value of this subgroup is .
The common codepoint value for PO index =  is  
Option 3:
PO index is mapped into the most significant bits of codepoints while subgroupID is mapped into the rest  bits and the common codepoint is mapped into the rest  bits with all bit value ‘1”.
Note:  is 0 ~ ,  is 0 ~ 
For determination of the available symbol for LP-WUS, support Alt 3, i.e., based on both a time-domain pattern configured by the gNB and the information from existing configuration
The time-domain pattern is a periodic time domain pattern (i.e. Alt. 1A). The pattern can reuse the mechanism of rate matching pattern.
The existing configuration includes SSB, Type-0 CSS, TDD DL/UL configuration
The LP WUS should not overlap with LP SS and the minimum gap between LP-SS and LP WUS should be 2 symbols.
If LP WUS MO overlaps with LP-SS, the LP WUS MO is postponed until there is at least 2 symbols gap between LP-SS and LP-WUS.
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO
The starting time location of the first LP-WUS MO in a LO is indicated by a symbol-level offset w.r.t. the reference point.
The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO
Within a MO, support to reserve one OFDM symbol after the LP WUS transmission.
Actual LP-WUS duration L is configured
Additionally, the maximum duration of nominal LO is either explicitly configured or implicitly determined, which is used for avoid overlapping between different LOs from network perspective.
The nominal LO include both the available and unavailable symbols within a LO.
The available symbols of a LO is equally divided into N set (corresponding to N beams), and the number of available MOs for each beam is floor(floor(Y/N)/L), where Y is the total number of available symbols within the maximum duration of nominal LO.
It is supported that gNB transmits LP-WUS/LP-SS associated with SSB indexes, and it is configured by gNB in the SIB for LP-WUS configuration on whether LP-WUS/LP-SS transmission is present or not for each SSB index.
The detailed signaling design is up to RAN2
For the MO location determination for LP-WUS/LP-SS, the same LP-WUS/LP-SS is transmitted repeatedly in N MOs via N beams, respectively, where N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1, and gNB can transmits LP-WUS/LP-SS in a subset of the N MOs according to the SIB for LP-WUS configuration
The LP-SS based LP-RSRP/LP-RSRQ definition can be used for OFDM-based LP-WUR also for the case when overlaid OFDM sequence is not configured (M=1)
For UE capability report on the 3 wake-up delays, from RAN1 perspective, the number of SSBs need for synchronization are confirmed to be {3,5,5}, respectively.
70ms is the minimum value of the wake-up delay assuming UE’s MR wakes up from deep sleep mode in IDLE mode, and for different SSB periodicities other than 20ms:
70ms is kept for SSB periodicity of 5ms and 10ms;
The wake-up delay is translated for SSB periodicities larger than 20ms, i.e. wake-up delay = 10ms+3*SSB_periodicity
For UE capability report on the wake-up delay assuming UE’s MR wakes up from ultra-deep sleep mode in IDLE mode, and for different SSB periodicities other than 20ms, the wake-up delay is {400ms, 800ms} +5*max(20ms, SSB_periodicity).
It is confirmed that the MR and LR of a UE operate in the same band/carrier
Support UE to report which band/frequency/carrier to monitor LP-WUS.
A new frequency priority list is configured for LP-WUS capable UEs, where the frequency with LP-WUS deployment is set with higher priority
If a UE receives a LP-WUS and a paging message for itself, it evaluates cell re-selection criteria according to legacy frequency priority list before RACH procedure
A UE can be informed in which band/frequency/cell LP-WUS feature is enabled
RAN1 concludes that both the unit of the LP-RSRP value and the LP-RSSI value is dBm per 11 RBs. 
Capture the updated parameters in Appendix C in the RRC parameter list 

3GPP TSG RAN WG1 #121			R1-2503319
St Julian’s, Malta, May 19th – 23rd, 2025

Source: 	ZTE Corporation, Sanechips
Title:	Discussion on LP-WUS operation in IDLE/INACTIVE mode
Agenda item: 	9.6.2
Document for:	Discussion and decision

Conclusions 
In this contribution, we have discussed issues on LP-WUS operation in IDLE/INACTIVE modes. We make the following observations and proposals:
Observations: 
Observation 1: If a slot level periodicity for the pattern is defined to determine available symbols, the system overhead for bitmap indication would be acceptable, but it may not be able to skip the UL slots for TDD case.
Observation 2: if a slot level bitmap for frame level periodicity of a pattern is defined to determine available slots, nominal MO and actual LP-WUS duration definition is needed.
Observation 3: If search space set-like pattern is defined, the periodicity could be aligned with LO/paging
nominal MO consisting one or more slots is defined
actually LP-WUS duration within nominal MO could be based on per MO pattern.

Proposals：

Proposal 1: The OFDM WUR can measure LP-SS even if overlaid OFDM sequence is not configured.
FFS whether OFDM WUR could detect LP-WUS ON-OFF pattern when overlaid sequence does not carry information.

Proposal 2: It should be up to gNB to configure whether OFDM WUR use the LP-SS for measurement.
Proposal 3: 
use search space like pattern to determine the (nominal) MO location
use per MO pattern to determine the actual LP-WUS duration within each (nominal) MO 

Proposal 4: Alt D can be together considered with search space like pattern.
Proposal 5: Alt1 is supported
Alt 1: Do not report wake-up delay for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Proposal 6: For eDRX, the LO periodicity could be the same as IDRX
FFS how to align with PTW to save LO monitoring
Proposal 7: A common configuration of EPRE for LP-WUS and LP-SS can be considered.
FFS: if LP-WUS configured with M=1 and LP-SS configured with larger M valueLP-WUS 

3GPP TSG RAN WG1 #121	R1-2503370
Malta, MT, 19th – 23rd May, 2025

Source:	vivo
Title:	Remaining issues on LP-WUS operation in IDLE/INACTIVE modes
Agenda Item:	9.6.2
Document for:	Discussion and Decision

Conclusion
In this contribution, the procedure of LP-WUS monitoring in RRC idle/inactive mode is discussion on the aspect of LP-WUS subgrouping and LP-WUS monitoring configuration etc., with the following observations and proposals:
Observation 1: For the case that LO and PO to be 1: multiple mapping, there is no need to explicitly indicate the target PO index in a LP-WUS.
Observation 2: By applying alt 2 (i.e., information from existing configurations), the above NR channel/signals can be avoided to collide with LP-WUS transmission.
Observation 3: In addition to alt 2, alt1 can also be configured by the network to rate match e.g., the NR signal/channel transmission for RRC connected mode UE which is treated as unavailable symbol for LP-WUS transmission.
Observation 4: It would be quite challenge to find a unified per-MO pattern to avoid collision with existing NR signals/channels while efficiently provide sufficient resource for LP-WUS transmission in each MO by Alt 1B.
Observation 5: For Alt A, the detection performance of LP-WUS cannot be guaranteed, since there is insufficient time resource for a MO to do actual LP-WUS transmission, and it increases RM decoding complexity for variable code block length.
Observation 6: For Alt B without the constraint of nominal MO duration length, the following two drawbacks need to be considered:
A LP-WUS transmission may span a long time period exceeding the coherence length, resulting in degradation of LP-WUS detection performance due to the change of the channel condition.
The floating MO start time and the variable MO duration increase the complexity of scheduling management for the network. 
Observation 7: For Alt C, since both nominal MO duration and actual MO duration are configured, there are no issues of LP-WUS scheduling complexity and performance degradation of LP-WUS.
Observation 8: For Alt C, by deferring an invalid MO instead of dropping an invalid MO, there will be no such a case that no valid MO for a LP-WUS beam.
Observation 9: For Alt C, even dropping an invalid MO, there still can be 2 or 3 valid MOs per beam in a typical slot-structure configurations, assuming 4 LP-WUS MOs are configured per beam.
Observation 10: For Alt D which is combinedly used with alt1B, it is challenge to find a unified per-MO pattern for all MOs to avoid collision with existing NR signals/channels while efficiently provide sufficient resource for LP-WUS transmission in each MO.
Observation 11: Both Alt 1 and Alt 2B will cause huge signaling overhead e.g., hundreds of bits.
Observation 12: The LR processing time will be a value at the symbol level rather than at the millisecond level and it can be covered by the nominal MO duration.
Observation 13: To address the case that PO-to-LO association < Ns, configuring a list of slot-level offsets will cause more signaling overhead e.g., additional dozens of bits than configurating a list of frame-level offsets.
Observation 14: The designs of 1) determination of the available symbol, 2) actual/nominal duration and 3) determination of subsequent MOs for LP-WUS MO can be reused for LP-SS transmission.
Proposal 1:
UE identifies its subgroup specific codepoint value as follows:
Let  denotes the PO index associated with a LP-WUS of the UE, with starting value of 0:
,
where, ,  and  are defined in clause 7 of TS 38.304. 
 denotes the configured number of PO associated with a LP-WUS.
A UE determines its subgroup specific codepoint value as “”, where
 denotes the configured number of LP-WUS subgroup per PO and ;
 is the LP-WUS subgroup ID per PO for the UE and .
For a UE with PO index , its common codepoint value is “”.
When a UE detects a codepoint value carried by a LP-WUS which is equal to “” or “”, the UE monitors its PO; otherwise, the UE is not required to monitor PO.
Proposal 2: Support Alt3 by combining alt 1A and alt2.
For Alt 1A, support to partially reuse the mechanism of rate matching pattern (i.e., reuse bitmaps including symbolsInResourceBlock and periodicityAndPattern). And the network can configure a rate matching pattern for LP-WUS transmission accordingly.
For Alt 2, SSB indicated by ssb-PositionsInBurst, CORESET/Type-0 CSS and UL symbols indicated by TDD DL/UL configuration which are overlapped with LP-WUS transmission are considered as unavailable symbols. 
Proposal 3: Support Alt C i.e., both nominal MO duration and actual MO duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped or deferred.
Proposal 4: Support Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly based on the previous LP-WUS MO i.e., the LP-WUS MOs are located back-to-back.
Proposal 5: Modify the previous agreement in red on the judgement condition of UE LP-WUS monitoring behavior as below.

Proposal 6: {8,..,191} can be the starting point of the frame-level offset value range for 20ms SSB periodicity. FFS: the frame-level offset value range for other SSB periodicity.
Proposal 7: For the case PO-to-LO association is smaller than Ns, a list of frame-level offsets needs to be configured, and each frame-level offset value determines the start of a frame for each LO.
Proposal 8: A UE applies the -th value out of  values of the frame-level offset list, wherein  is the associated PO index of the UE,  is the configured number of PO per LO.
Proposal 9: The value range for the slot-level offset can be {0,…,10*2^}.
Proposal 10: The POs associated with one LO should be consecutive POs from the network perspective.
Proposal 11: If one LO is associated with POs of two or four PFs, these associated PFs are consecutive PFs calculated by the parameters PF_offset, T, Ns, and N. The first PF of the PFs associated with the LO is provided by (SFN for PF) - floor (iPO/Ns)*T/N, where SFN for PF is determined in clause 7.1 of TS 38.304, iPO is defined as the associated PO index for a LO, T, Ns, and N are determined in clause 7.1 of TS 38.304.
Proposal 12: For LP-SS transmission, support the following designs:
LP-SS reuses the available symbol determination method defined for LP-WUS.
Nominal LP-SS occasion needs to be configured. 
Actual LP-SS transmission duration is derived by the configured LP-SS sequence length.
If the number of consecutive available OFDM symbols within the nominal LP-SS occasion is less than the actual LP-SS transmission duration, the occasion is considered as invalid (no LP-SS monitoring in this occasion) and deferred it to the next valid occasion.
Two adjacent nominal LP-SS occasions are placed back-to-back i.e., no gap between them.
gNB configures LP-SS periodicity and a slot-level offset for the first nominal LP-SS occasion, e.g.,  
slot160, INTEGER {0..159}
slot320, INTEGER {0..319}
Proposal 13: The set of SSB for LP-SSS-RSRP/RSRQ measurement is determined by ssb-PositionsInBurst in SIB1 rather than SSB-ToMeasure.
Proposal 14: The number of LP-WUS/LP-SS beams is the same as the number of SSB beams determined by ssb-PositionsInBurst in SIB1.
Proposal 15: Support separate EPRE ratio configuration for LP-WUS and LP-SS to SSB.
Proposal 16: Adopt the TP given in section 5 with modification in red.

3GPP TSG RAN WG1 #121                                                       R1-2503523
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	9.6.2
Source:	Spreadtrum, UNISOC
Title: 	Discussion on LP-WUS operation in IDLE/INACTIVE modes
Document for:	Discussion and decision

Conclusion
We have the following proposals.
Proposal 1: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Proposal 2: The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point using symbol level offset should be supported.
Proposal 3: the start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO. 
Proposal 4: The starting time location of the first LP-SS occasion is configured w.r.t. the reference point provided by as LP-SS_periodicityoffset, using a symbol-level offset
Proposal 5: The starting time location of the subsequent LP-SS occasion(s) is implicitly derived based on the time location of the first LP-SS occasion (i.e., Option 1)
Proposal 6: Do not report for SSB periodicities other than 20ms (i.e., Alt 1).
Proposal 7: gNB needs to inform UE which SSB beams are used to transmit LP-WUS/LP-SS.
Proposal 8: A common EPRE ratio configuration for LP-WUS and LP-SS to SSB should be supported.

3GPP TSG RAN WG1 #121   		R1-2503574
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:    9.6.2
Source:	Samsung
Title:	Discussion on LP-WUS operation in IDLE/INACTIVE modes
Document for:	Discussion and decision

Conclusion
This contribution discusses the solutions for LP-WUS operation in RRC_IDLE/RRC_INACTIVE modes. Proposals are summarized as follows: 
Proposal 1: Support Alt 2 to determine the available symbol(s) for LP-WUS in each MO.
Proposal 2: If the RBs for LP-WUS including the guard RBsare overlapping with other signals/channels in frequency domain, the symbols are not available for LP-WUS. Otherwise, the symbols can be determined as available symbols for LP-WUS according to the information configured in SIB1.
Proposal 3: Slot-level offset can be used to determine the starting time location of the first LP-WUS MO since the available symbol(s) for LP-WUS can be determined by UE according to the information configured in SIB1. For the starting time locations of the subsequent LP-WUS MOs, Alt 2A can be supported considering the signaling overhead.
Proposal 4: Support Alt B to determine the actual LP-WUS duration.
Proposal 5: How to handle the UE capability report on the wake-up delay for SSB periodicity should be determined by RAN4 (Alt 3).
Proposal 6: A separate EPRE ratio can be configured for LP-WUS and LP-SS.

3GPP TSG RAN WG1 Meeting #121                                                                                     R1-2503643
St Julian’s, Malta, May 19 – May 23 2025

Agenda Item:	9.6.2
Source:	TCL  
Title:	LP-WUS operation in IDLE/INACTVE states 
Document for:	Discussion and Decision 

Conclusion
In this contribution, we discussed the maximum length of LP-WUS MOs, nominal and actual duration of MO, time resources configuration of LP-WUS MO, and LP-WUS detection enhancement. We made the following observations and proposals.
Observation 1: If the number of subgroups per PO increases (e.g., from 32 to 256), the LP-WUS payload size grows significantly, leading to higher LP-WUR power consumption and increased complexity in LP-WUS decoding. 

Proposal 1: The maximum length of an LP-WUS MO can be up to 4 slots, and the LP-WUS MOs can span across non-contiguous symbols. 
Proposal 2: For nominal MO duration and actual MO duration, support Alt B: Actual LP-WUS duration is configured (e.g. in unit of OFDM symbols, or M and L values). 
Proposal 3: To enable the UE to determine whether a symbol is available for LP-WUS, support Alt 1: Time-domain pattern configured by the gNB.
Proposal 4: For the starting time location of the first LP-WUS MO within a LO, support both slot-level and symbol-level offsets relative to the reference point.
Proposal 5: For the starting time locations of subsequent LP-WUS MOs within a LO, support Alt 2, where the start time location of a subsequent LP-WUS MO is determined implicitly, at least based on the previous LP-WUS MO.
Proposal 6: RAN1 to consider LP-WUS detection optimizations, such as distributing the LP-WUS payload across blocks, MOs, or beams, enabling UEs to decode only relevant segments and enhance power efficiency.

3GPP TSG RAN WG1 #121	R1-2503695
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda item:		9.6.2
Title:					LP-WUS operation in IDLE/Inactive mode
Source:				Nokia
Document for:		Discussion and Decision

Conclusion
In this contribution we have discussed aspects related to the LP-WUS operation in IDLE/Inactive mode.
In Section 2.1 we discuss the LR measurement quantities, with following observation and proposals:-
Observation 1: It would appear possible for OFDM-based WUR to emulate envelope detector, thus LP-SS based metrics would also be applicable when M=1. 
Observation 2: There should be no RAN4 requirement impact supporting this scenario. 
Proposal 1: Support LP-SS based metrics also for OFDM-based WUR when M=1.
Proposal 2: If both LP-SS based and SSB based thresholds are configured, OFDM-based WUR is assumed to apply the SSB-based threshold (and metric) for evaluation.
Observation 3: For the OFDM-based WUR, the time domain resources for RSSI in the SS-RSRQ would need to be defined. 
Proposal 3: For OFDM-based WUR SS-RSRQ measurement metric, clarify that measurementSlots and endSymbol are not applicable and that RSSI is measured over the fixed set of symbols in the slots containing the SSB(s). Down select among following options for the RSSI measurement symbols:
same symbols as for the SSB, or
symbols as determined for configuration endSymbol=1 (i.e. {0,1,2..,11} for SCS<480kHz) is the slot where SSB is received.
Proposal 4: LP-RSRP and LP-RSRQ measurements should be associated to a particular beam. Update the LP-RSRP and LP-RSRQ metric definitions for example as follows: “LP-RSRP shall be measured only among the reference signals corresponding to LP-SS associated with the same SS/PBCH block index.”
Proposal 5: For LP-RSRP and LP-RSRQ measurements, it should be possible for the network to configure a sub-set of LP-SS’s from which LP-RSRP and LP-RSRQ can be measured, similarly as done for SSBs with SSB-ToMeasure.
Observation 4: It is expected that performance requirements will ensure consistent reporting from different UEs.

In Section 3.1 we consider the aspects related to the LP-WUS monitoring configuration:-
Observation 5: Based on evaluation results, puncturing can have non-negligible impact to the LP-WUS detection performance especially when the LP-WUS codeword length is shorter.
Observation 6: To achieve consistent LP-WUS performance, assuming constant number of actual LP-WUS symbols is preferred.
Observation 7: CONNECTED mode UEs can be configured to avoid the collision between assumed PDCCH and PDSCH resources with LP-WUS through different means thus it is not necessary to configure LP-WUS to avoid all. 
Observation 8: CSI-RS and IDLE/Inactive mode UEs cannot be made to avoid LP-WUS in a as straight forward manner.
Observation 9: To avoid the collision with legacy NR channels, LP-WUR may need to accumulate the actual LP-WUS symbols over longer time than the number of encoded LP-WUS symbols would imply. 
Proposal 6: UE accumulates the actual number of (configured) LP-WUS symbols over longer absolute time than indicated by the number of actual LP-WUS symbols.
Proposal 7: At least Type0-CSS and CORESET#0 configuration are accounted by UE when determining the actually available symbols for LP-WUS in a slot/MO. I.e. in slots where Type0-CSS is present, symbols covered by CORESET#0 are not available for LP-WUS.
Observation 10: If the available symbols are to be indicated in slot level, either symbol level bitmap or pre-defined (symbol level) patterns in a table could be used to indicate the available symbols for LP-WUS. 
Proposal 8: Use default PDSCH TDRA table to indicate the available symbols in a slot(s) (in a MO) for LP-WUS. FFS whether this would be common indication for all slots, or slot/MO specific indication.
Observation 11: To enable the indication of reserved TRS symbols in a slot, as symbols not available for LP-WUS, partially re-using the Rel-17 IDLE TRS configuration could be considered.  
Proposal 9: To support indication of TRS resource, consider re-using the resource indication approach defined for Rel-17 IDLE mode TRS. FFS whether this would be common indication for all slots, or slot/MO specific indication.
Observation 12: As slots containing SSBs or UL symbols may have very limited, or no, symbols available for LP-WUS, it would be preferable to be able to avoid these in MO configuration.
Proposal 10: Consider search space style MO starting symbol/slot pattern definition, where period (with offset) and duration (number of slots/MOs) is used to determine the pattern of candidate MO locations. Based on collision e.g. with UL slots, candidate MO locations can be determined as valid or invalid. 
Observation 13: To reduce the range of values needed for the PF-LO offset, making the applied value range dependent on the SSB periodicity could be considered, similarly as for the configuration of first paging PDCCH monitoring occasion is dependent on the applied sub-carrier spacing.

Section 3.2 considers the issues related to the determination of beams association:-
Observation 14: UE should be able to identify the LP-SS beam association with specific SSB index via time location association. 
Observation 15: To close the loop in UE LP-WUS beam selection, LP-WUS MOs association to LP-SS/SSB beam should be identifiable via time location association.
Proposal 11: Define that there is one-to-one association between LP-SS and LP-WUS MO time locations and SSB beams. This can be done as logical indexing. 
Observation 16: As the LP-SS can provide sufficient synchronisation accuracy for LP-WUS detection in equal power levels, it does not seem necessary to have separate EPRE offsets for LP-WUS and LP-SS.

In Section 3.3 we discuss LP-WUS content presenting some analysis results and make following observations and proposals:-
Observation 17: The information bit determination before encoding the codepoints determination needs to consider also the PO common codepoint and sharing the codepoint space to multiple POs.
Observation 18: It might be more straight forward to determine the information bit codepoint association fully in RAN1 specification.
Proposal 12: Adjusting the higher layer information bits to account PO common codepoint(s) and multiple PO(s) as follows:
When subgroupNumber PO_LPWUS >1 the physical layer information bits corresponding subgroup ID n, can be defined as:
,
			where  is the information bits corresponding to the subgroup ID n.
The information bits corresponding to the PO common codepoint as:
				.

Proposal 13: Same approach used to adjust the information bits for a codepoint is used to determine the information bits for overlay sequence.

Other aspects related to configuration of LP-WUS and LP-SS is discussed in Section 3.4:-
Observation 19: Both LP-WUS and LP-SS time and frequency resources need to be provided for the IDLE/Inactive mode UE. Delivery method is up to RAN2.
Observation 20: For LP-SS the time domain configuration would need to contain periodicity and start time (SFN) possibly with additional e.g. slot level offset. 
Proposal 13: For LP-SS a reference time can be configured through (sub-frame or radio frame level) offset and periodicity.  
Proposal 14: Support configuration of the start time of LP-SS (corresponding to each SSB) in a slot. Consider either fixed pattern or indication of start symbol in sub-set of symbols. 
Observation 21: Frequency location of LP-WUS and LP-SS can be determined using existing frequency resource grids/references, such as common resource grid.
Proposal 15: Supporting configuration of starting PRB on common resource block grid for LP-SS and LP-WUS.
Observation 22: For frequency domain configuration, it would be beneficial to agree whether LP-SS/LP-WUS configuration needs to have some relation to UE active BWP and in relation to each other and/or SSB.
Observation 23: For placement of LP-WUS and SSB for IQ-LR, two cases could be considered: if SSB and LP-WUS are sufficiently close, SSB can be used for tracking, ad if SSB is further apart, IQ-LR could use LP-SS.

Proposal 16: Consider the maximum frequency separation between SSB and LP-WUS that can be supported by OFDM-based WUR.
Observation 24: For placement of LP-SS and SSB for ED-LR, as ED-LR does not need to consider SSB, there does not appear to be strong reason to restrict the relative placement in frequency domain. 

Aspects related to eDRX and UE capability indication are presented in Section 4:-
Proposal 17: If LP-WS operation with eDRX is supported and UE is configured with eDRX and LP-WUS, the LP-WUS monitoring is determined based on paging occasions so that UE can monitor LP-WUS associated to the POs that are within the PTW. 
Proposal 18: For UE wake-up delay capability reporting for different SSB periodicities, select Alt 2, where UE reports one capability (1,2,3) that contains corresponding values for different SSB periodicities. 

3GPP TSG RAN WG1 #121		                                            R1-2503801
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	CATT
Title:	System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes
Agenda Item:	9.6.2
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss aspects of UE capability, configuration of LP-WUS, subgrouping, the LP-WUS monition procedures and LP-WUS detection for RRC_IDLE/INACTIVE modes and give the following observations and proposals:
Observation 1: If the UE capability of the wake-up delay is reported through RRC signaling procedure, UE is required to transition from RRC_ IDLE/INACTIVE modes to RRC_CONNECTED mode. 
Observation 2: A LO can be associated with multiple PF with following configurations:  
Config#1: Ns=1，=2
Config#2: Ns=1, =4
Config#3: Ns=2, =4
In where  the number of POs per LO, Ns is the number of POs per PF. 
Proposal 1: UE capability of the supporting of LP-WUS can be indicated during UE registration procedure through NAS procedure.
Proposal 2：The UE capability of the wake-up delay can be reported during UE registration procedure through NAS procedure.
Proposal 3: Support Alt 1: Do not report for SSB periodicities other than 20ms.
Proposal 4: A time gap i.e. Z should be specified for indicating the time gap between the start of two neighbor PFs associated with the LO, the first PF of the PFs associated with the LO can be provided by:
(SFN for PF) - floor (/Ns)T/N*Z.
where =floor{Y/X}* Ns +i_s, Y=, X= (Ns*N)/(/Ns). SFN for PF, T, Ns, and N are determined are defined in TS 38.304. Z and can be configured in SIB1.
Proposal 5: Support a symbol-level of offset is indicated for each of the subsequent LP-WUS MOs.
Proposal 6: Support Alt B: Actual LP-WUS duration is configured.
Proposal 7: For all subgroup indexes in a PO, the codepoint corresponding to all subgroups index is {()}, where  is the number of subgroup per PO,  is the number of PO per LO,  is the PO index, 0.
Proposal 8: When eDRX is configured, LP-WUS should be monitored within PTW.

3GPP TSG RAN WG1 #121			R1-2503839
Malta, MT, May 19th–May 23th, 2025

Source: 	CMCC
Title:	Discussion on LP-WUS operation in IDLE/INACTIVE mode
Agenda item:	9.6.2
Document for:	Discussion & Decision

Conclusions
In this contribution, we discussed the LP-WUS operation in IDLE/INACTIVE mode, and the following proposal are made.
Proposal 1. For available resource determination of LP-WUS, support Alt 3 (Combination of Alt 1 and Alt 2).
Support Alt 1A within Alt 1.
Further consider the case when the time gap between LP-WUS occasion and DL/UL transmission is smaller than a threshold/predefined value.

Proposal 2. For starting time location determination of LP-WUS, support Alt 2 (The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO).
Support Alt 2A within Alt 2.

Proposal 3. For terminology definition of LP-WUS, support Alt B (Actual LP-WUS duration is configured. From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration).

Proposal 4. For design on LP-SS, support to reuse the mechanism in LP-WUS MO/resource determination as much as possible.
Support Alt 3 (Alt 1A within Alt 1) for available resource determination.
Support Alt 2 (Alt 2A within Alt 2) for starting time location determination.
Support Alt B for terminology definition.

Proposal 5. For UE capability report on the wake-up delay, support Alt 3 (It is up to RAN4).

TDoc file reading error

3GPP TSG RAN WG1 #121		R1-2503939
St Julian’s, Malta, May 19th – 23th, 2025


Agenda item:	9.6.2
Source:	NEC
Title:              	Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the LP-WUS operations in RRC IDLE/INACTIVE modes, and the following observations and proposals are made:
Proposal 1: for option 2 (i.e., multiple POs associated with an LO), UE does not expect the number of MOs in an LO is smaller than the number of POs associated with the LO.
Proposal 2: for the codepoint value(s) of common codepoint(s) for PO(s), support one of the following three options: 
Option 1: the first or last N codepoint values are used for the N common codepoints for N POs respectively. 
Option 2: (Nsg+1) consecutive codepoint values are used for a PO, wherein the first/last codepoint value in the (Nsg+1) codepoint values is used for the common codepoint for the PO, and the rest Nsg codepoint values are used for Nsg subgroups. 
Option 3: only one codepoint value (e.g., the first or last codepoint value) is used for the common codepoint of N POs, UE further determines which PO is indicated based on in which MO the common codepoint is detected. 

3GPP TSG RAN WG1 #121			R1-2503965
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2
Source:	InterDigital, Inc.
Title:	Discussion on LP-WUS operation in IDLE/INACTIVE modes
Document for:	Discussion

Summary
In this contribution, we discussed LP-WUS operation in IDLE/INACTIVE modes. Based on the discussion, we made the following proposals. 
Proposal 1: Support indication on a subset of SSB beams for LP-WUS operation with Alt1 (S is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1, and LP-WUS MOs and LP-SS occasions are determined assuming S beams) for the MO and LP-SS occasion determination.
Proposal 2: Support entry/exit conditions considering measurement of both LP-SS and SSB for OFDM based LR.
Proposal 3: For determination of symbols available for LP-WUS, support Alt 2 (information from existing configurations available for IDLE/INACTIVE UEs).
If there’s any information that is not provided to the UE, Alt 3 (combination of Alt 1 and Alt 2) can be additionally considered. 
Proposal 4: For the configuration of LP-WUS duration, support Alt A (nominal MO duration is configured). 
Proposal 5: For the starting time locations of the subsequent MOs in a LO, support Alt 1 (An offset is indicated for each of the subsequent LP-WUS MOs).
Symbol-level offset is supported. 
Proposal 6: For the UE capability report on the wake-up delay, support Alt 3 (up to RAN4). 
Proposal 7: Common ERPE ratio for LP-WUS and LP-SS is supported.
Proposal 8: Each LP-WUS is QCLed with LP-SS in QCL Type A and QCL Type D (when applicable).
Proposal 8: LP-SS based RRM measurement is supported for OFDM based LR.

3GPP TSG-RAN WG1 Meeting #121	R1-2504019
St. Julian’s, Malta, May 19th – May 23rd, 2025
Agenda Item:	9.6.2
Source:	Ericsson
Title:	LP-WUS operation in IDLE and INACTIVE modes
Document for:	Discussion
1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	From an eco-system support point of view, it would be beneficial to allow NW to configure the type of WUS operation(s) which are supported in a cell.
Based on the discussion in the previous sections we propose the following:
Proposal 1	For LP-WUS operation in RRC-IDLE and INACTIVE, LP-WUS is used to trigger paging monitoring of the UE, i.e., monitoring of DCI format 1_0 with CRC scrambled by P-RNTI.
Proposal 2	Paging misdetection performance of the UE should not be impacted when LP-WUS is used by the UE for power savings.
Proposal 3	LP-WUS and LP-SS configuration is provided to the UE in a cell by system information. Further details of higher layer mechanisms can be discussed in RAN 2.
Proposal 4	Type of WUS capability supported in the cell, e.g., support for both OFDM and OOK-based or OFDM-based WUS only, should be configurable by the NW.
Proposal 5	When LP-SS is not configured by gNB, LP-WUS operation in the cell is supported only for UEs that support SSB based RRM measurement.
Proposal 6	It should be possible for NW to configure flexibly the placement of LP-WUS and LP-SS resources in frequency and time to minimize overhead and NW energy efficiency impact.
Proposal 7	LP-WUS and LP-SS frequency domain resource allocations can be separately configured.
Proposal 8	Support separate configurations of EPRE ratio between LP-WUS and SSB and that of LP-SS and SSB. The ratio is limited to be within a certain range.
Proposal 9	For UE capability report on the wake-up delay, support different sets of 3 candidate values for different SSB periodicities greater or equal to 20 ms. For SSB periodicity below 20 ms, the same wake-up delay as for the 20-ms periodicity is assumed.
Proposal 10	For the first MO in a LO, both slot level and symbol level offset can be supported in addition to already agreed frame-level offset.
Proposal 11	For subsequent MOs, UE determines the LP-WUS MO positions it has to monitor in a LO based on a) Starting position of the LO (including any other offsets, if agreed, to determine the first LP-WUS MO of the LO) b) number of LP-WUS MOs configured and LP-WUSMO duration c) position of LP-WUS MO(s) corresponding to the SSB based on which the UE monitors paging PDCCH within the LO.
Proposal 12	Do not support additional configuration to control the subsequent MO locations.
Proposal 13	Support a configuration of Bitmap1 (slot-level bitmap) indicating whether slots in a number of frames (N) are available for LP-WUS MOs. The slot-level bitmap repeats every N frames. The value of N can be 4.
Proposal 14	Support a configuration of Bitmap2 (symbol-level bitmap per MO) indicating whether symbols in a MO are available for LP-WUS. Bitmap2 is the same for every MO.
Proposal 15	Support a configuration of (nominal) LP-WUS MO duration. Symbols used for LP-WUS are determined from Bitmap1 and Bitmap 2. Separate configuration of actual LP-WUS duration is not required.
Proposal 16	If a RE of any available symbol of a MO overlaps with a SSB/LP-SS RE, the UE may skip LP-WUS monitoring for that MO.
Proposal 17	Introduce following RRC parameters
Number of LP-WUS MOs per beam
Value range: {1, 2, 3, 4}
LP-WUS MO duration for RRC Idle
Value range: {1sym, 2sym, 3sym, 4sym, 6sym, 7sym, 1slot, 2slots, 3slots, 4slots, 6slots,12slots, 15slots} (‘sym’ refers to number of OFDM symbols, >3slots only allowed if repetition is configured)
Note: This parameter corresponds to ‘nominal MO duration’ in RAN1#120bis agreement
Bitmap1 (slot-level, spanning 4 frames) to indicate available slots for LP-WUS MOs
If this parameter is not configured, UE assumes all non-UL slots are available
Bitmap length: 40 bits
Bitmap2 (symbol-level, spanning MO duration) to indicate available OFDM symbols for LP-WUS in a MO
If this parameter is not configured, UE assumes all non-UL symbols in MO are available
Bitmap length: equal to number of OFDM symbols in LP-WUS MO duration

Proposal 18	Parameter related to LP-WUS MOs such as the maximum number of MOs UE should monitor for LP-WUS can be configured as part of the WUS configuration.
Proposal 19	Support one-to-one beam association for LP-SS/LP-WUS based on the SSB beam time-domain index. That is, the k-th LP-SS/LP-WUS occasion/beam corresponds to the k-th transmitted SSB/SSB beam, where k = 1, 2, …, N, and N is the number of actual transmitted SSBs.
Proposal 20	Support only configuration of duty-cycled WUR monitoring in Rel-19.
Proposal 21	Entry/exit conditions should be configurable, e.g., as part of the LP-WUS configuration.
Proposal 22	It should be possible to configure different entry/exit conditions based on supported WUR types, if any.
Proposal 23	If serving cell RRM using LP-SS is supported, only scenarios that are suitable for operation with low LP-SS overhead and NW energy impact should be considered for RRM.
Proposal 24	Support that OFDM receiver can measure LP-SS even if overlaid OFDM sequence is not configured (M=1).

3GPP TSG RAN WG1 #121				             R1-2504067
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item 	:	9.6.2
Source 	:	Sony 
Title 	:	LP-WUS operation in IDLE/INACTIVE mode
Document for 	:	Discussion and decision

Conclusion
This document has considered aspects related to LP-WUS operation in IDLE/INACTIVE mode. The following proposals were made. Proposal 1 – RAN1 to consider Alt4, i.e., NW ensures LP-WUS configuration without collision with existing signal(s), for LP-WUS configuration.
Proposal 2 – RAN1 to consider Alt2, if NW cannot ensure LP-WUS configuration without collision with existing signal(s), for LP-WUS configuration.
Proposal 3 – RAN1 to avoid solutions which requires additional configuration and therefore additional signalling and power consumption at the UEs.
Proposal 4 – RAN1 to consider Alt B for determination of Nominal MO duration and actual LP-WUS duration.
Proposal 5 – RAN 1 to select the first LP-WUS monitoring occasion in an LO by a symbol-level offset w.r.t. the reference point.
Proposal 6 – RAN 1 to select Alt2 where the start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.

TDoc file reading error

3GPP TSG RAN WG1 #121		                                           R1-2504188
St Julian’s, Malta, May 19th – 23rd, 2025
Source:	OPPO
Title:		Further consideration on LP-WUS operation in RRC_IDLE/INACTIVE modes
Agenda Item:	9.6.2
Document for:	Discussion and Decision

Conclusion
In this contribution, LP-WUS operation in IDLE/INACTIVE mode is discussed with following proposals:
Based on the agreement, no further mapping rule between POs and MOs in case of multiple POs associated with one LO.
For the power saving gain, avoid the case that non-target subgroup(s) are waked up by LP-WUS in case of multiple POs associated with one LO.
Support the PO indication in LP-WUS.
Introducing PO indication field won’t change the maximum number of LP-WUS information bits.
Introducing PO indication field could achieve the early termination for non-target PO’s UE.
If no PO indication field, it needs to increase the number of bits for codepoint. The total bits for LP-WUS are same.
Support PO indication field in LP-WUS, i.e., LP-WUS consist of 2 fields, one is used to indicate the associated PO, the other one is used to indicate the codepoint.
Support Alt2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Support symbol-level offset on the determination of the starting time location of the first LP-WUS MO in a LO.
Support Alt2B: configuration of candidate starting locations for MOs, similar to search space configuration.
Alt A would cause different LP-WUS detection performance in different MOs.
Alt B could ensure the performance of LP-WUS detection, and make full use of available symbols for LP-WUS transmission.
Compared with Alt B, Alt C would significantly decrease the resource utilization, and needs more discussion on the UE behavior.
Alt D is similar as Alt C, would cause the waste of resource.
Support Alt B: Actual LP-WUS duration is configured.
Study the mechanism to switch MR back to sleep when it is wakened up by false alarm.
In case of M>1, no matter for LP-WUS or LP-SS, the time duration of OOK-ON symbols within one OFDM symbol is always half of one OFDM symbol.
Support common configured EPRE ratio for LP-WUS and LP-SS.
For Wake-up delay, both Alt 2 and Alt 3 is OK. We prefer Alt 3: It is up to RAN4.

3GPP TSG RAN WG1 #121			R1-2504238
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	9.6.2
Source:	Panasonic
Title:	Discussion on LP-WUS operation in IDLE/INACTIVE modes
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  


Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.



Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.



Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO



Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time


Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.  

3GPP TSG RAN WG1 #121					  R1-2504251
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item:	9.6.2
Source: 	LG Electronics
Title: 	Discussion on LP-WUS operation in IDLE/INACTIVE modes
Document for:	Discussion and decision

Conclusion
In this contribution, we shared our views on the LP-WUS operation in IDLE/INACTIVE modes. Followings are proposed for LP-WUS operation in IDLE/INACTIVE modes:
Proposal 1: Support Alt. 2 for TDD handling
Proposal 2: For further flexibility, Alt. 1A can be considered in addition to Alt. 2. 
For Alt. 1A, re-use the structure of RateMatchPattern or invalidSymbolPattern
Proposal 3: Support Alt 1 or Alt. 2B for starting position determination of LP-WUS MO
Proposal 4: Deprioritize Alt. D for LP-WUS MO duration determination
Proposal 5: Consider following alternatives for LP-WUS MO duration determination:
Alt. A
Alt. B with a time window as a termination condition. 
The time window can be configured per MO or per LO
Proposal 6: To avoid the overlapping between adjacent two LOs, introduce RRC parameter to configure the duration of a LO.
Proposal 7: For LP-WUS operation in TDD configurations, 
If multiple LMO (for repetitions) are configured per beam, skip/drop the LP-WUS monitoring opportunity when it overlaps with UL symbols.
Otherwise, postpone the LP-WUS monitoring opportunity for N*K LP-WUS MO when it overlaps with UL symbols.
Proposal 8: Consider following options for clarification on procedures to determine the start of monitoring for LP-WUS MOs with invalid symbols
When potential starting points of LP-WUS MO are configured: 
Option 1-1: If a configured potential starting point is associated with an invalid LP-WUS MO, the UE drops this starting point and evaluates subsequent configured potential starting points to identify the next valid MO.
Option 1-2: If nominal MO duration is configured and an LP-WUS MO at a given potential starting point is invalid, the UE finds the next configured potential starting point that occurs after the nominal end of this invalidated MO.
Option 1-3: If actual MO duration with a termination window is configured and an LP-WUS MO at a potential starting point is invalid or its duration adjusted, the UE identifies the next configured potential starting point occurring after the termination window of the preceding MO.
In a back-to-back operation scenario: 
Option 2-1: If nominal MO duration is configured, an LP-WUS MO following an invalid MO starts at the beginning of the next nominal MO period.
Option 2-2: If actual MO duration with a termination window is configured, an LP-WUS MO following a completed or invalid MO starts from the first available valid symbol occurring after the end of the termination window of the preceding MO.
Proposal 9: Consider following alternatives for clarification on procedures to determine the start of monitoring for LP-WUS MOs with invalid symbols
Alt. 1: LP-WUS MOs are primarily intended to occur sequentially at their configured potential starting points. 

Proposal 10: Support Alt. 2 for UE capability reporting on wake-up delay for different SSB periodicities
For current SSB periodicity not in the UE's reported capability, the UE shall use the wake-up delay value corresponding to the next larger SSB periodicity available 
Proposal 11: UEs with different wake-up delay should be assigned to different UE subgroups
Proposal 12: UEs having shorter wake-up delay can be assigned to a specific subgroup(s) separately
The number of those subgroups can be separately configured
Wake-up delays below a certain threshold are considered as shorter wake-up delay
Proposal 13: Introduce separated parameters of EPRE ratio to SSS between LP-WUS and LP-SS
For both of parameters, the value range is same as existing parameters: ENUMERATED{db-3, db0, db3, db6}
For the description of EPRE ratio of LP-WUS RE, 
Power offset (dB) of LP-WUS RE to SSS RE. 
For the description of EPRE ratio of LP-SS RE, 
Power offset (dB) of LP-SS RE to SSS RE. 

3GPP TSG RAN WG1 #121							R1-2504266
St Julian’s, Malta, May 19th – 23th, 2025

Source:	MediaTek Inc.
Title:	LP-WUS operation in IDLE/INACTIVE modes
Agenda item:	9.6.2
Document for:	Discussion and decision

Summary
In this contribution, the following proposals are provided:

Proposal 1: Updated MO Configuration:
MONumPerLOPerBeam: 1-4 (corresponds to K).
subgroupNumberPO_LPWUS: Max 32 subgroups/PO.   
PO-to-LO-Association: List of up to 4 PO indices per LO.
LO_OffsetConfiguration: 
frameLevelOffset: Single value.
additionalFrameOffsets (Optional): 0 or 1 value.
firstMO_Offset: Symbol-level offset for 1st MO.
subsequentMO_OffsetPattern: e.g., moGapDuration (implicit).
MO_AvailableSymbolsPattern: Defines available symbols (e.g., periodic bitmap).
MO_DurationDefinition: 
actualLPWUS_SymbolLength: Configured actual symbol count.
maxNominalMO_DurationSlots (Optional): Max MO window.

Proposal 2: Updated LP-SS Configuration:
LP-SS_Mvalue: {1, 2, 4}.
LP-SS_SequenceLength: Configured based on M (e.g., for M=1, L from {6,8}).
LP-SS_Binary_Seq_Index: 0-3.
LP-WUS-LP-SS_StartRB: Starting PRB index.
LP-SS_Periodicity: {160ms (for M=1,2), 320ms}.
LP-SS_OverlaidSequence_Enable: Boolean.

Proposal 3: Configuration Design for LP-WUS/LP-SS beam association with SSBs
NumLP_WUS_SS_Beams: Number of LP-WUS/LP-SS beams (N).
explicitSSB_AssociationList (Optional): List of N SSB indices, one for each LP-WUS/LP-SS beam. If absent, implicit 1-to-1 ordered mapping to SSBs assumed.
LP_WUS_SS_QCL_Type: Configures QCL Type ('typeA' or 'typeC'), aligning with final RAN1 decision.

Proposal 4: Support separate EPRE ratios.
Reasoning: LP-WUS (information carrier) and LP-SS (sync/RRM) have different needs. Separate ratios allow independent optimization for coverage, reliability (e.g., power boosting on LP-WUS for larger payloads), and power saving.
Configuration design: 
epreRatioLP_WUS_to_SSB: Configures the EPRE ratio of LP-WUS to SSB.
epreRatioLP_SS_to_SSB: Configures the EPRE ratio of LP-SS to SSB.

Proposal 5: UE Capability for Wake-up Delay
Reporting: UE reports one index. Each index corresponds to a set of pre-defined wake-up delay values for a standardized list of different SSB periodicities, .
Derivation: These standardized delay values should be based on consistent underlying parameters for each capability: (​: base ramp-up/processing time, : needed​ SSBs for sync). 
Index 0: ()
Index 1: () 
Index 2: () 
The wake-up delay for a given ​ would be 
 ​

3GPP TSG RAN WG1 #121	                                         	           R1-2504329
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2

Source:	Apple Inc.
Title:	LP-WUS operation in IDLE/INACTIVE modes
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  

Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.

Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO

Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time

Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.  

3GPP TSG RAN WG1 #121	                                         	           R1-2504331
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2

Source:	Moderator (Apple)
Title:	Summary #1 on LP-WUS operation in IDLE/INACTIVE mode
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  

Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.

Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO

Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time

Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.  

3GPP TSG RAN WG1 #121	                                         	           R1-2504332
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2

Source:	Moderator (Apple)
Title:	Summary #2 on LP-WUS operation in IDLE/INACTIVE mode
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  

Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.

Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO

Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time

Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.  

3GPP TSG RAN WG1 #121	                                         	           R1-2504333
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2

Source:	Moderator (Apple)
Title:	Summary #3 on LP-WUS operation in IDLE/INACTIVE mode
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  

Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.

Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO

Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time

Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.  

3GPP TSG RAN WG1 #121	                                         	           R1-2504334
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2

Source:	Moderator (Apple)
Title:	Summary #4 on LP-WUS operation in IDLE/INACTIVE mode
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  

Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.

Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO

Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time

Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.  

3GPP TSG RAN WG1 #121	                                         	           R1-2504335
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2

Source:	Moderator (Apple)
Title:	Summary #5 on LP-WUS operation in IDLE/INACTIVE mode
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  

Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.

Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO

Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time

Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.  

3GPP TSG RAN WG1 #121			R1-2504402
St Julian’s, Malta, May 19th – 23th, 2025
	
Agenda item:	9.6.2
Source: 	Qualcomm Incorporated
Title: 	LP-WUR Operation in Idle and Inactive Modes
Document for:	Discussion and Decision

Conclusions
In this contribution, we have provided the following observations and proposals:
Proposal 1: Support slot-level offset w.r.t. the reference frame to determine the starting time location of the first LP-WUS MO in the LO. The starting symbol of LP-WUS MO is the first available symbol in the determined slot.
Observation 1: Alt 1 for offset configuration for subsequent LP-WUS MOs provides more configuration flexibility to avoid the situation that no MO contains enough available symbols for LP-WUS transmission in a beam.
Proposal 2: Support Alt 1 to indicate an offset for each subsequent LP-WUS MO.
Proposal 3: LP-WUS detection/processing time is determined by RAN4. 
RAN1 asks RAN4 for LP-WUS processing time and whether LP-WUR can process the LP-WUS in one MO and receive LP-WUS in the next MO simultaneously.
Proposal 4: Define UE capability for the time gap between MOs with at least two candidate values. One value corresponds to the concurrent reception and processing of LP-WUS from different MOs and the other value corresponds to the sequential reception and processing of LP-WUS from different MOs.
Observation 2: Determination of available symbols for LP-WUS depends on both gNB implementation and UE implementation capabilities
For gNB, whether concurrent transmission and reception is supported, whether symbols are reserved for important PDCCHs such as paging PDCCH, and whether it can simultaneously transmit two signals in different beams, etc.
For UE, whether FDM’ed reception of LP-WUS/LP-SS and SSB is supported.
Proposal 5: Determination of available symbols for LP-WUS transmission should be based on simple rules, e.g., if an existing NR signal is considered as higher priority than LP-WUS, LP-WUS is not transmitted in symbols configured for the existing signal irrespective of the frequency gap between the existing signal and LP-WUS.
Proposal 6: Support Alt 3 for the determination of available symbols for LP-WUS
The periodic time-domain pattern is based on mechanism of NR rate matching pattern.
Proposal 7: Clarify whether available symbols are determined between LP-WUS and NR signals within the same beam or across beams
For Rel-19, we prefer “across beams” for a simpler design.
Proposal 8: LP-SS transmission for each beam is confined in the same slot
Discuss how to determine the starting symbol of LP-SS transmission in the slot.
Proposal 9: Support Alt C - Both nominal MO duration and actual LP-WUS duration are configured
Network ensures that there is at least one valid MO for each beam based on separately configured offsets w.r.t. the reference point for all MOs in the LO.
Proposal 10: At least for M=1, OFDM receiver can measure LP-SS based LP-RSRP/LP-RSRQ if overlaid OFDM sequence is not configured.
Proposal 11: The number of codepoints configured for LP-WUS is equal to
(1 + number of UE subgroups per PO) * number of POs mapped to a LO
Codepoint value is from 0 to number of codepoints configured for LP-WUS - 1
Proposal 12: Within a LP-WUS MO, the codepoint values are sequentially allocated for the common codepoint for each PO followed by codepoints for individual UE subgroups for each PO of all POs associated with the LO.
Observation 3: Considering different LP-WUR implementations, it is preferrable that LP-WUS and LP-SS have the same EPRE (i.e., average power in OFDM symbol duration) and the same average power in OOK ON chips.
Proposal 13: The same EPRE ratio is configured for LP-WUS and LP-SS.
Proposal 14: LP-SS should be always transmitted at the configured EPRE so that detection threshold can be reliably determined for the LP-WUS.
If this cannot be guaranteed, network needs to transmits preamble before LP-WUS.
Observation 4: For M=4, when the EPRE (i.e., average power in OFDM symbol duration) is fixed, more OOK ON chips in the OFDM symbol results in lower average power in the OOK On chip, and vice versa.
Proposal 15: Do not support different number of OOK ON symbols in different OFDM symbols
LP-SS does not have this problem
Only support a code block length for LP-WUS that does not have this problem.
Observation 5: An issue similar to the different number of OOK ON symbols in different OFDM symbols for M=4 also exists for M=1 for LP-WUS and M>1 for LP-SS.
Proposal 16: If M=1 is configured for one of LP-WUS and LP-SS, M=1 is configured for both
This issue is also discussed in agenda 9.6.1.
Observation 6: Joint subgrouping of LP-WUS and PEI improves the subgrouping granularity and reduces UE false paging probability.
Proposal 17: Support UE monitoring PEI after receiving LP-WUS to enhance the UE subgrouping granularity.

3GPP TSG RAN WG1 #121	                              R1-2504438
St Julian’s, Malta, May 19th – 23th, 2025

Source:	Sharp
Title:	Discussion on LP-WUS operation in IDLE/INACTIVE modes
Agenda Item:	9.6.2
Document for:	Discussion and decision

Conclusion
In this contribution, we have the following observations and proposals:
Observation: Both alternatives can be supported, depending on details of LP-WUS MO structure.

Proposal 1: Codepoints should be evenly allocated across each PO associated with a given LO.
Proposal 2: Each UE monitors two codepoint values. In cases where only one subgroup per PO configured, both codepoints may carry the same value.
Proposal 3: UL slot and SSB resource collisions should be considered in determining the available symbols for LP-WUS transmission.
Proposal 4: Support Alternative C as the preferred method for LP-WUS MO configuration.
Proposal 5: The gap between offset values should be a multiple of paging cycles.

3GPP TSG RAN WG1 #121			R1-2504509
MT, Malta, May 19th – 23rd, 2025

Source:	NTT DOCOMO, INC.
Title:	Discussion on LP-WUS operation in IDLE/INACTIVE modes
Agenda Item:	9.6.2
Document for:	Discussion and decision

Conclusion
In this contribution, we discussed LP-WUS operation in IDLE/INACTIVE modes. Based on the discussion, the following proposals were made:

Proposal 1:
For how UE determines whether a symbol is available for LP-WUS, support Alt 3 with Alt 1A
Alt 3: Combination of Alt 1 and Alt 2
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc]
Proposal 2:
Support Alt B with supporting maximum gap between available LP-WUS symbols
If consecutive unavailable symbols for LP-WUS among available symbols for LP-WUS within MO is larger than the maximum gap, LP-WUS is not transmitted before the unavailable symbols within MO
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration.
Proposal 3:
Support slot-level offset to determine the starting time location of the first LP-WUS MO in a LO
Proposal 4:
For the starting time locations of the subsequent LP-WUS MOs in a LO, support Alt 2 with no FFS
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly based on the previous LP-WUS MO
Proposal 5:
Clarify whether “LP-WUS MO” indicates nominal MO duration or actual LP-WUS duration in the following agreement
A LP-WUS MO can span across multiple slots. 
FFS the limitation on the maximum length for an LP-WUS MO
If nominal MO duration is indicated, limitation on the maximum length for an LP-WUS MO should be further discussed
Proposal 6:
For how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, support Alt 1 in RAN1 perspective
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Ask RAN4 whether to support SSB periodicities other than 20ms
Proposal 7:
The value range of MONumPerLO in higher layer parameters list should be {1, 2, 3, 4}
Proposal 8:
For LO_frame_offset(s) in higher layer parameters list, delete 3 offset values parts
Proposal 9:
Support new RRC parameter for slot level offset in higher layer parameters list
Proposal 10:
Entry/Exit_condition_OOK/OFDM should not be captured in RAN1 higher layer parameters list

3GPP TSG RAN WG1 #121	R1-2504574
St. Julian’s, Malta, May 19th 23rd, 2025

Agenda item:		9.6.2
Source:	Nordic Semiconductor ASA
Title:					On LP-WUS operation in IDLE/Inactive
Document for:		Discussion and Decision

Conclusions 
In this contribution we discussed issues related to LP-WUS IDLE mode procedures:
Proposal-1: 
UE determines whether a symbol is available for LP-WUS based on information from sub-set of existing configurations available for idle/inactive UEs 
TYPE#0/TYPE#2 CSS and associated CORESET(s), and
transmitted SSBs indicated in SIB1 on a camping cell.
A symbol is not available for LP-WUS if it collides, at least partially in frequency, with any of above configurations.
A symbol is not available for LP-WUS if it is indicated as UL slot by tdd-UL-DL-configuration.

Proposal-2: Nominal MO duration and actual LP-WUS duration, if defined, are determined according to Alt C. 

Proposal-3: Support separate EPRE offset for LP-SS and LP-WUS.  
Proposal-4: On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Proposal-5: 
The starting time location of the first LP-WUS MO in a LO is indicated by a slot offset w.r.t. the reference point.
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly and start from the slot boundary after the end of previous LP-WUS MO

Proposal-6: Consider (at least for overlaid design) one more codepoint/sub-group to be dedicated to early termination of monitoring for the UEs.

3GPP TSG RAN WG1 #121	                                         	           R1-2504891
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2

Source:	Moderator (Apple)
Title:	Summary #6 on LP-WUS operation in IDLE/INACTIVE mode
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  

Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.

Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO

Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time

Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.  

3GPP TSG RAN WG1 #121	                                         	           R1-2504892
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.6.2

Source:	Moderator (Apple)
Title:	Summary #7 (Final) on LP-WUS operation in IDLE/INACTIVE mode
Document for:	Discussion/Decision

Conclusion
For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement
The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.  

Agreement
For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement
For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.
The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)
Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement
For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.
FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement
For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.
Send an LS to RAN4 to confirm the above agreement. Final LS in R1-2503103.

Agreement
LS on the RRM measurement metrics for OFDM-based LP-WUR is agreed. Final LS in R1-2503103.
Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

Agreement
For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.
For codepoint corresponding to more than one subgroups:
Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO 

Agreement
For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is 
7 for the case where 4 POs are mapped to one LO
15 for the case where 2 POs are mapped to one LO

Agreement
Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO

Agreement
UE determines whether a symbol is available for LP-WUS based on:
Alt 1: Time-domain pattern configured by the gNB
Alt 1A: Periodic time-domain pattern
E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern
Alt 1B: Per-MO pattern, applicable for all Mos
Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s)

Agreement
For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO, 
A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.
FFS slot-level or symbol-level offset
The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:
Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.
FFS slot-level or symbol-level offset
Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.
FFS additional configuration to control the subsequent MO locations, e.g.,
Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration
FFS restriction on MO locations, e.g. only on DL slots
FFS minimum gap is needed between two MOs to ensure LR processing time

Agreement
Terminology definition
Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE
Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:
Alt A: Nominal MO duration is configured. (e.g. in unit of slots)
Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.
Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)
From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration. 
FFS: Additional termination condition such as time window
Alt C: Both nominal MO duration and actual LP-WUS duration are configured.
If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.
FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors
Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.
Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement
On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.
Alt 1: Do not report for SSB periodicities other than 20ms
Note: LP-WUS is not supported for SSB periodicities larger than 20ms
Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):
Alt 3: It is up to RAN4

Agreement
Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.