3GPP TSG RAN WG1 #120-bis	R1-2501711
Wuhan, China, April 7th – 11th, 2025
Agenda Item:	9.6.2
Source:	Futurewei
Title:	Discussion on LP-WUS Operation in IDLE/INACTIVE modes
Document for:	Discussion/Decision 

Conclusion
This contribution discusses LP-WUS structure and configuration during operation in IDLE/INACTIVE state. The following summarizes our observations and proposals.
Offset Value(s) Configuration
Proposal 1: Support that the gNB can configure 3 offset value(s) between an LO and a reference PO/PF selected from Table 1, e.g., {80,720,1040} ms, along with an LP-WUS/UE-specific paging cycle which can limit LO resource overhead. 
LO and Reference PF(s) Determination
Observation 1: When multiple offset values between a LO and a reference PF are configured, the number of LO reference points per paging cycle T can be smaller than the number of configured offsets if {80, 720, 1040} ms are considered as the offset values.
Observation 2: When multiple offset values between a LO and a reference PF are configured, considering a default reference PF based on paging cycle T and multiple UE-specific reference PFs can result in only one LO reference point per T assuming the offset values of {80, 720, 1040} ms.
Proposal 2: When multiple offset values between a LO and a reference PF are configured, support the UE to determine the LO and the reference PF(s) per paging cycle T using a default reference PF, an LO reference point, and up to X=3 UE-specific reference PFs.
LO to PO mapping and MO Configuration
Observation 3: When Option 1 is supported and the LO is defined as an offset from the reference PO, there may be a constraint on the total duration of an LO or a constraint on the spacing between MOs in an LO, in particular when more than one PO per PF are configured. 
Observation 4: Option B (K LP-WUS MOs for a beam are divided into G groups of R*M LP-WUS MOs) enables the trade-off between scheduling flexibility and UE’s power consumption regardless of the number of supported subgroups within one MO by the LP-WUS design. Further, the support of R>=1 simplifies network support of different coverage targets.
Observation 5: Considering a change in Option B definition such that “A UE monitors all or some of the MO(s) within one group of R*M LP-WUS MOs based on its group or subgroup ID.” can enable the support of Option 2 of the LO to PO mapping which can alleviate the constraint on the total LO duration and avoid the need to explicitly account for the potential overlap between LOs.
Proposal 3: Support Option B (K LP-WUS MOs for a beam are divided into G groups of R*M LP-WUS MOs) and R>=1 when K>1 LP-WUS MOs are configured for each beam in an LO. Further, support Option 2 for LO to PO mapping with 4 as the maximum number of POs per LO.

3GPP TSG RAN WG1 #120bis			R1-2501768
Wuhan, China, April 7th – 11th, 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: Using the same definition of SS-RSRP and SS-RSRQ for OFDM WUR only means the following is reused
SS reference signal received power (SS-RSRP) is defined as the linear average over the power contributions (in [W]) of the resource elements that carry secondary synchronization signals. 
Secondary synchronization signal reference signal received quality (SS-RSRQ) is defined as the ratio of N×SS-RSRP / NR carrier RSSI, where N is the number of resource blocks in the NR carrier RSSI measurement bandwidth.
Observation 2: OFDM WUR only perform serving cell measurement and neighbor cell measurement by WUR is not considered in Rel-19.

Proposals：

Proposal 1: 
SMTC is not needed for OFDM WUR and OOK WUR for serving cell measurement
CSI or DMRS related measurement are not performed by OFDM based WUR.
Serving cell measurement for OFDM-based WUR and OOK-based WUR can be applied for RRC_IDLE intra-frequency and RRC_INACTIVE intra-frequency
Proposal 2: LP-WUS MO should be defined based on number of slots and number of symbols.
Proposal 3: Symbol level gap between MOs are allowed. FFS slot level gap
Proposal 4: Discuss and decide how the MOs organized in time domain
The order for flexible MOs with M>=1, repetition number(if supported), beam index
The gap between MO including beam sweeping
Proposal 5: Support the following for one LO to one PO or one LO to multiple PO mapping
at least one codepoint corresponding to one subgroup
One codepoint corresponding to all the subgroups
FFS the reserved states if any
Proposal 6: Discuss whether the UE decode the all subgroups wake-up on all MOs or a specific MO.
Proposal 7: Discuss and decide how the LP-WUS indicate one subgroup for one LO mapping to multiple POs.
Proposal 8: Option A can be adopted.
Proposal 9: No need to consider other optimization based on different SSB periodicity.
Proposal 10: For eDRX, discuss 
the LO periodicity could be the same as IDRX
the LO periodicity could be the same as eDRX periodicity
Proposal 11: Support LP-WUS deployed in FDD/TDD bands
Proposal 12: The LO and MO definition should be applicable for both FDD and TDD
FFS whether MO could be based on flexible symbols or slots in TDD
Proposal 13: A common configuration of EPRE for LP-WUS and LP-SS can be considered.

3GPP TSG RAN WG1 #120bis	R1-2501815
Wuhan, China, April 7th – 11th, 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: The following impacts caused by adopting Option B or Option 3 should be considered.
To guarantee the FARo from channel noise is <1%, the effect of Option B or Option 3 on saving LP-WUS bit overhead is very limited e.g., only one or even no bit can be saved.
The total required number of MOs per beam increases if adopting Option B or Option 3. And it will accordingly become challenging to reserve sufficient time resource for a LO with large number of LP-WUS MOs.
Option B or Option 3 has negligible effect to reduce the system overhead.
Proposal 1:
UE identifies its subgroup specific codepoint value as follows:
Let  denotes the relative PO index, with starting value of 0, among the POs associated with a LP-WUS:
,
where, ,  and  are defined in clause 7 of TS 38.304. 
 denotes the configured number of PO associated with a LP-WUS and .
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 a UE and .
The common codepoint value corresponding to all the subgroups needs to be checked by all UEs is “0”.
When a UE detects a codepoint value carried by a LP-WUS which is equal to “0” or “”, the UE monitors its PO; otherwise, the UE is not required to monitor PO.
Proposal 2: UE is required to monitor each of M groups per beam until its target LP-WUS is detected.
Proposal 3: Don’t support repetition for OOK based LP-WUS signal i.e., R=1.
Proposal 4: Support Option A with the maximum value of LP-WUS MOs per beam for a LO to be 4 i.e., K<=4.
Proposal 5: A LO contains K beam groups of LP-WUS MOs (K<=4) and for each beam group there is N LP-WUS MOs associated with N SSB beams, respectively.
Proposal 6: Do not support option 3 for LO to PO mapping or option B for MO configuration.
Proposal 7: A LP-WUS MO can be configured considering the follows:
The length of a LP-WUS MO is configured contiguous in time by the network. And a LP-WUS MO is a valid MO, if the available symbols within the MO is no smaller than required number of symbols to transmit LP-WUS according to the configured code block length L.
There is no time gap between adjacent LP-WUS MOs within a LO.
The first LP-WUS MO position of a LO is determined by the slot-level offset.
Proposal 8: Support the number of POs mapped to one LO can be {1, 2, 4}.
The POs associated with one LO should be consecutive POs from the network perspective. And the maximum number of PF associated with one LO is up to 2.
Proposal 9: Don’t consider three offsets between an LO and a reference PO/PF.
Proposal 10: Support the frame-level offset of LP-WUS is to determine the start of the frame for a LO.
Proposal 11: Modify the previous agreement in red on the judgement condition of UE LP-WUS monitoring behavior as follows:

Proposal 12: {8,..,154} 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 13: For the case PO-to-LO association is smaller than Ns, a list of frame-level offset needs to be configured, and each frame-level offset determines the start of a frame for each LO.
Proposal 14: 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 15: Support to define a slot-level offset to determine the start of the first MO for a LO which is relative to the start of the LO frame boundary derived by the frame-level offset.
The value range for the slot-level offset can be {0,…,10*2^}.
Proposal 16: For LP-SS occasion,
gNB configures a number of nominal occasions for LP-SS, wherein the number is no smaller than number of beams for LP-SS/LP-WUS. UE assumes LP-SS transmission with beam sweeping in valid occasions within the configured nominal LP-SS occasions, wherein the valid occasion does not collide with UL symbols. 
gNB configures periodicty and slot-level offset for the first LP-SS occasion, e.g.,  
slot80, INTEGER {0..79}
slot160, INTEGER {0..159}
slot320, INTEGER {0..319}
slot640, INTEGER {0..639}
gNB configures symbol-level offset for the first LP-SS occasion, or the symbol-level offset is pre-defined. 
Remaining LP-SS occasions within a period is in consecutive slots with same symbol-level offset as the first LP-SS occasion. 
Proposal 17: The network configures the measurement time resource for LP-SSS-RSSI, which can be different from NR SMTC.
Proposal 18: It is up to network implementation to transmit smaller number of LP-SS beams compared to SSB beams.
Proposal 19: Support a common EPRE ratio configuration for LP-WUS and LP-SS to SSB.
FFS: whether gNB is restricted to transmit the LP-WUS based on the configured EPRE ratio to SSB.

3GPP TSG RAN WG1 Meeting #120-bis											R1-2501846
Wuhan, China, April 7th –April 11th 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 content and payload of LP-WUS, offset between LO and PO/PF, mapping between LO and POs, UE behavior after receiving LP-WUS, and LP-SS/LP-WUS beam management. We made the following observations and proposals.
Observation 1: The number of information bits in an LP-WUS remains 5 bits per subgroup, whether the number of LP-WUS subgroups per PO is 31 or 32.
Proposal 1: Consider the maximum number of information bits (including CRC) in an LP-WUS as 8 bits for each subgroup.  
Observation 2: 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. 
Observation 3: When an IDLE/INACTIVE UE in LP-WUS monitoring mode moves within a cell or across cells, and may lose the coverage from the previous SSB beam, the UE cannot receive LP-WUS QCled with the previous SSB beam. 
Proposal 1: Consider the maximum number of information bits (including CRC) in an LP-WUS as 8 bits for each subgroup.  

Proposal 2: 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.
Proposal 3: For the offset value(s) between an LO and a reference PO/PF, support 3 offset values. 
Proposal 4: For the additional offset values between an LO and a reference PO/PF, consider symbol-level or slot-level offsets between the LO and the reference PO/PF.
Proposal 5: For K (K>1) LP-WUS MOs configured for each beam in an LO, support option A. 
Proposal 6: For LO-to-PO mapping option 2, support the following:
A maximum of 4 POs per LO.
The mapping of one LO to 1, 2, or 4 POs is determined by the number of POs configured within a PF.

Proposal 7: The maximum number of MOs within an LO that a UE monitors for the same beam is set to at least 44.
Proposal 8: Consider further study on LP-SS based beam management, measured by LP-WUR. 

3GPP TSG RAN WG1 #120bis                                                      R1-2501876
Wuhan, China, April 07th – 11th, 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.
LP-WUS occasion and monitoring occasion
Proposal 1: Option A should be supported for definition of LO and LMO.
Proposal 2: gNB configures 3 offset values should not be supported.
Proposal 3: The max number of POs per LO can be 4.

3GPP TSG RAN WG1 #120bis		                                            R1-2502000
Wuhan, China, April 7th – 11th, 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: If the LP-WUS can support 32 subgroups, Option 3 has additional specification complexity without benefits.
Observation 3: If the LP-WUS can support 32 subgroups, Option B has additional specification complexity without benefits.
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: There is no benefit of assuming SSB periodicities other than 20ms.
Proposal 4: The parameters of the LP-WUS configuration are broadcasted and included in the SIB-1/SIB-X.
Proposal 5: The maximum number of POs per LP-WUS can be 4:
The candidate number of configured PO associated with one LO can be {1, 2, 4}
The number of PO mapping to a LO should be multiple of Ns when the number of PO per LO is larger than Ns, where Ns is the number of paging occasions for a PF.
Proposal 6: The maximum number of PF associated with a LO can be 1 for simplicity.
Proposal 7: Confirm the following working assumption:
Working Assumption
If LP-WUS design support 32 subgroups within one MO, do not support Option 3 for LO to PO mapping or Option B for MO configuration.
Proposal 8: If R>=1 is supported, gNB needs to transmit LP-WUS on every LP-WUS MO to allow UE accumulating the received energy for LP-WUS detection for coverage enhancement. Once the UE detects a LP-WUS to wake up at one of multiple MOs, the UE is not required to monitor the remaining MO(s) associated with the same LO.
Proposal 9: The LP-WUS MO can be by configuring a set of locations of LP-WUS MOs.
Proposal 10: 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, .

3GPP TSG RAN WG1 #120bis	R1-2502008
Wuhan, China, 7th- 11th 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: If Manchester encoding is not applied to the LP-SS and depending on the binary sequence selection for LP-SS, the current definitions might lead to inconsistent results for LP-RSRQ and for LP-RSRQ between different LP-SS sequences 
Proposal: Once LP-SS sequence design has been finalized, verify if the LP-RSRP and LP-RSRQ metric definitions need to be revisited. 
Proposal: LP-RSRP and LP-RSRQ measurements should be associated to a particular beam.
Proposal: For LP-RSRP and LP-RSRQ measurements, it should be possible for theto  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.
Observation: As the intent of the LR based measurements is serving cell evaluation, it would not seem necessary to restrict the measurements within SMTC.
Observation: 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: Additional offset(s) are needed to indicate the LP-WUS MO location(s).
Proposal: LP-WUS MO should be configured based on starting symbol based on symbol level offset from a reference. This offset could be independent or concatenated so that earlier LP-WUS MO starting symbol is a reference for the latter.  
Proposal: Define additional common offset for LP-WUS MO(s) of a LO to enable reducing the size of the LP-WUS MO symbol level offset. This offset could be defined in a slot level or ms level.
Observation: To reduce the range 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.
Observation: Gain from repetitions for non-coherent receivers is very limited.
Observation: Enabling codepoint determination via encoding can provide benefit and allow use of repetitions for incremental redundancy 
Proposal: Consider repetitions only if they can provide significant benefit for the detection performance e.g. via increased redundancy.
Observation: It does not seem necessary to support more than two possible LO configurations/offsets per PO.
Proposal: Support a maximum of two possible LO configurations/offsets per PO. 

Section 3.2 considers the issues related to the determination of beams association:-
Observation: UE should be able to identify the LP-SS beam association with specific SSB index via time location association. 
Observation: 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: 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: 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:-
Proposal: If more than one PO is mapped to LP-WUS, the information content is identical and equal, so that all POs will have same number of sub-group indications and their own individual ‘wake-up all’ indication.
Proposal: Support configurable mapping of maximum of 4 POs to one LO.
Other aspects related to configuration of LP-WUS and LP-SS is discussed in Section 3.4:-
Observation: 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: For LP-SS the time domain configuration would need to contain periodicity and start time (SFN) possibly with additional e.g. slot level offset. Furthermore, fixed time pattern locations for LP-SS corresponding to SSB would be needed.
Proposal: For LP-SS a reference time can be configured through (sub-frame or radio frame level) offset and periodicity. If only one periodicity is supported, it can be fixed in specification.  
Proposal: Support configuration of the start time for each LP-SS (corresponding to each SSB) at symbol level granularity. The reference time for the symbol level offset could be directly the LP-SS reference time.
Observation: Frequency location of LP-WUS and LP-SS can be determined using existing frequency resource grids/references, such as common resource grid.
Proposal: Supporting configuration of starting PRB on common resource block grid for LP-SS and LP-WUS.
Observation: 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: 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: Consider the maximum frequency separation between SSB and LP-WUS that can be supported by IQ-LR.
Observation: 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. 

In section 4.1 we discuss about methods to reduce the false alarms for the IDLE/Inactive mode UEs:-
Observation: To reduce the energy cost of repeated paging monitoring due to MR wake-ups, UE should be provided assistance information whether it should expect further paging in following paging occasion.
Aspects related to eDRX are presented in Section 4.2:-
Proposal: 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. 

3GPP TSG RAN WG1 #120bis		R1-2502076
Wuhan, China, April 7th – 11th, 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 RRC-IDLE/INACTIVE, the LP-WUS configuration indicates one or more LP-WUS frequency bands in a carrier, and for each LP-WUS frequency band, a periodicity and an offset of LOs are comprised in the configuration.
Proposal 2: Support a MO can span multiple slots.
Proposal 3: For the locations of MOs in an LO, support both periodic and non-periodic MO locations. For the periodic MO locations, a periodicity and an offset should be configured. For the non-periodic MO locations, an offset value for each MO or each MO group relative to the start time of the LO should be configured.

3GPP TSG RAN WG1 #120-bis			R1-2502168
Wuhan, China, April 7th–April 11th, 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 K (K>1) LP-WUS MOs configured for each beam in an LO, support Option A: K LP-WUS MOs for a beam are divided into M (M >=1) groups of R LP-WUS MOs.

Proposal 2. Regarding Option A on LP-WUS MO design:
For detailed UE monitoring behaviour, support:
The UE monitors all M LP-WUS MO group(s) in an LO. 
If the UE detects the LP-WUS that corresponds to its subgroup, it may not need to detect the remaining LP-WUS MO(s) in the LO.
For the exact value of R, support R>= 1.

Proposal 3. Support a LP-SS occasion/LP-WUS MO can go across multiple slots and contiguous in time.
Also support that a LO/LP-SS burst can be contiguous in time.

Proposal 4. RAN1 to discuss the UE behaviour when LP-SS/LP-WUS transmission overlap with existing pattern (e.g. UL slot/symbol, common signal transmission, configuration related to L1/L3 measurement), or when the time interval between LP-SS/LP-WUS transmission and existing pattern is smaller than the RF retuning time (e.g. when LR/MR is deployed in FR2, or when SCS of PRACH is equal or larger than 15kHz).

Proposal 5. Do not introduce the SMTC window for LP-SSS-RSRP/RSSI measurement.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502238
Wuhan, China, April 7th – 11th, 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:
The FAR performance is dominated by noise instead of a LP-WUS for another subgroup.
To meet the FAR performance requirement, 
at least 7 bits are needed for the case a single MO is monitored per LO
at least 8 bits are needed for the case 2 MOs are monitored per LO
at least 9 bits are needed for the case 4 MOs are monitored per LO
Multiple-to-one mapping between LO and PO cannot provide higher power saving gain, since no finer granularity of subgrouping can be provided.
Multiple-to-one mapping between LO and PO leads to higher collision rate and thus larger latency and/or less power saving gain.
Multiple-to-one mapping between LO and PO cannot reduce the signaling overhead (and thus resource overhead) due to FAR requirement.
For the structure of K MOs in a LO, option B can be achieved by multiple-to-one mapping between LO and PO, which 
leads to higher collision rate and thus larger latency and/or less power saving gain.
cannot reduce the resource overhead 
is more complex than option A
In most cases, gNB can know the number of subgroups to be waken up before a LO on which LP-WUS codepoint(s) to be transmitted, and thus usually can transmit the codepoint corresponding to all the subgroups only in the first MO of a LO. 
In the case where SI changes, transmitting the codepoint corresponding to all the subgroups in a MO/LO that is monitored by all UEs in a cell can help to reduce the overhead. 
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, especially for the vertical 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
Resources of MOs for un-transmitted LP-WUS cannot be utilized/reused efficiently, which leads to resource wasting. 
When e-DRX is configured, the power saving gain provided by LP-WUS is not attractive.
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.

Proposals:
For LP-WUS payload size, consider the FAR and MDR requirements, where
For FAR, the requirement is <= 1% per DRX cycle, where the FAR is due to noise
For MDR, the requirement is <= 1% per detection trial
For mapping between LO and PO, Option 3 is not supported.
Note: Option 3 is that UEs monitoring the same PO are divided into multiple sets of subgroups, with UEs within each set of subgroups monitoring the same LO.
For option 2 that UEs corresponding to different POs monitor the same LO, max number of POs per LO is 4.
One LO consists of N sets of K LP-WUS MOs, where,
every K consecutive MOs are mapped into one beam,
Within the K consecutive MOs, the same LP-WUS information can be mapped into multiple consecutive MOs for repetition. 
When K (K>1) LP-WUS MOs are configured for each beam in an LO, support option A: K LP-WUS MOs for a beam are divided into M (M >=1) groups of R LP-WUS MOs. A UE monitors all or some of the MO(s) within the K LP-WUS MOs.
Support to configure the symbol-level offset to determine the MOs of the LO.
Don’t support 3 offset values between an LO and a reference PO/PF.
For MO definition, one MO can be across multiple consecutive slots
This means LP-WUS can be mapped to non-contiguous OFDM symbols, which can be realized by ‘available OFDM symbols’ method.
More than 4 MOs per LO are supported for option 2 (one LO mapped to multiple POs).
For LP-WUS in IDLE/inactive mode, to minimize the number of codepoints per MO for a UE to monitor, the codepoint corresponding to all the subgroups is only monitored in some MOs.
In the MOs above, the maximum number of codepoints for a UE to monitor is 1 or no larger than the number of codepoints monitored in the other MOs.
To reduce the signalling/resource overhead, a MO/LO is configured to be monitored by all the UEs to detect the codepoint corresponding to all the subgroups.
Further discuss how to map subgroup ID to codepoint value, especially for Option 2.
For each MO in the LO, support to configure explicitly an SSB index to associate with the MO.
LP-WUS with e-DRX is deprioritized.
The RRM metrics for OOK-based receiver, including LP-RSRP and LP-RSRQ can be also applied to OFDM-based receiver.
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
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
Capture the updated parameters in Appendix in the RRC parameter list 

3GPP TSG RAN WG1 #120bis		                                           R1-2502258
Wuhan, China, April 7th – 11th, 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:
Proposal 1: Additional information (e.g., cell information, SI change and ETWS/CMAS information, tracking area information and RAN area information) are not carried by LP-WUS payload, it can be contained by LP-SS or the overlaid OFDM sequences if needed.
Proposal 2: The time duration of one LP-WUS is desirable to be not longer than one slot.
Proposal 3: Considering maximum number of subgroups per PO supported in Rel-19 is 31, do not support Option B for MO configuration.
Proposal 4: Considering maximum number of POs within one PF is 4, support maximum 4 POs per LO in case of Option 2 (UEs corresponding to different POs monitor the same LO).
Proposal 5: The periodicity of LP-SS can use 320ms as baseline. It can be further supported for 80ms, 160ms and 640ms as additional periodicity.
Proposal 6: On the LO configuration for iDRX, if multiple-level offset values between a LO and a reference PO/PF are supported, similar definition as PEI could be considered, e.g., frame-level offset and symbol-level offset.
Proposal 7: Study the mechanism to switch MR back to sleep when it is wakened up by false alarm.
Proposal 8: The design of LP-SS and LP-WUS would impact the configuration of EPRE ratio.

3GPP TSG RAN WG1 #120bis			R1-2502303
Wuhan, China, April 7th – 11th, 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: A MO is confined within a slot where the MO is contiguous in time. 
Proposal 2: Support repetitions across MOs to handle the limitation of LP-WUS payload design. 
Proposal 3: Support up to 2 POs per LO for Option 2.
Proposal 4: Option 3 (UEs monitoring the same PO are divided into multiple sets of subgroups, with UEs within each set of subgroups monitoring the same LO) is additionally supported to enable the indication of subgroup based on LO/MO location as well as the information delivered by LP-WUS.
Proposal 5: Do not support 3rd offset value between LO and PF.
Proposal 6: Common ERPE ratio for LP-WUS and LP-SS is supported.
Proposal 7: 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.
Proposal 9: Introduce definitions of LP-RSRP and LP-RSRQ for OFDM based LR to support LP-SS based RRM measurement.
Proposal 10: Introduce the following definitions of LP-RSRP and LP-RSRQ for OFDM based LR.
LP-RSRP is defined as the linear average over the power contributions (in [W]) of the resource elements that carry LP-SSs.
LP-RSRQ is defined as the ratio of N×LP-RSRP / LP-RSSI, where N is the number of resource blocks in the LP-RSSI measurement bandwidth.

3GPP TSG RAN WG1 #120-bis				             R1-2502323
Wuhan, China,  7 – 11 April 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 observations and proposals are made:
Observation 1 – configuring the UE to monitor PEI instead of PO after LP-WUS detection leads to additional access latency, higher total power consumption and more complex LP-WUS design and its integration with legacy solution. 
Observation 2 – UEs monitoring different POs monitor the same LO results in increased latency.
Observation 3 – The schemes for LP-WUS MOs configuration, agreed during RAN1#118 to be down selected, leads to unnecessary long LP-WUR monitoring time which results in high power consumption.
Observation 4 – The operation of LP-WUR based on duty-cycling is necessary to reduce the total power consumption. The long transition time to wake-up the main radio from ultra-sleep time together with sleep time of the duty-cycle can prevent some UEs from meeting the delay requirement.
Observation 5 – There could be a case where the LP-WUS is defined to have full cell coverage, still the LP-WUR may not be able to detect the LP-WUS.

Proposal 1 – RAN1 to support to limit the maximum number of POs per LO to 2.
Proposal 2 – RAN1 to investigate new schemes for the LP-WUS MO configuration that supports reduced/limited channel monitoring duration.
Proposal 3 – An MO length needs to be chosen in accordance with LP-WUS duration independent of whether it is longer or shorter than one slot.
Proposal 4 – RAN1 to consider contiguous MO if spanning across multiple slots. 
Proposal 5 – Support time-frequency multiplexing of LP-WUS for different UEs to increase LP-WUS address/identification space.
Proposal 6 – RAN1 should decide on a mechanism for RRC-IDLE and RRC-INACTIVE mode UEs to know the SSB beam to which their LP-WUS will be QCL.
Proposal 7 – Support an adaptive configuration where the UE, depending on its delay requirement, can operate based on an always-on or a duty-cycle scheme.

Proposal 8 – In order to further avoid ping-pong behaviours, a time window can be used in a addition to power level hysteresis.

3GPP TSG RAN WG1 #120bis   		R1-2502376
Wuhan, China, April 7th – 11th, 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: 
Observation 1: Option 3 for LOs:POs mapping may be more resource-efficient than Option B for MO configuration.

Proposal 1: For RRC_IDLE/RRC_INACTIVE mode, the maximum number of information bits in a LP-WUS can be 6 bits if 6 bits are supported for RRC CONNECTED mode, otherwise, 5 bits are enough. The code block length for one LP-WUS is decided according to the code with rate matching, the number of information bits and M value.
Proposal 2: Considering to support LP-WUS transmission across slots to satisfy the FAR and coverage targets.
Proposal 3: A common EPRE ratio can be configured for LP-WUS and LP-SS.
Proposal 4: The association relationship between LP-WUS/LP-SS beams and SSB beams can be determined by an explicit indication for simplicity.
Proposal 5: Support UE not monitoring the next X LOs after it detect a LP-WUS in one LO and the LP-WUS provides a wake-up indication. The number of skipped LOs X can be discussed further.
Proposal 6: To support multiple POs to one LO mapping, the max number of POs per LO can be limited to 2 if 5 information bits are supported. Otherwise, the max number of POs per LO can be limited to 4 if 6 information bits are supported.
Proposal 7: The condition for mapping multiple POs to one LO can be when the number of subgroups of configured POs is less than or equal to 31 if 5 bits are supported or 63 if 6 bits are supported. If the number of subgroups of configured POs is larger than 31 or 63, option 2 is not supported and UE will fall back to monitor the LO associated with the corresponding PO.
Proposal 8: For the mapping relationship between LO and PO, a revised option 3 can be considered to reduce the resource overhead from network perspective, which is 
From network perspective, UEs monitoring the multiple POs are divided into multiple sets of subgroups, with UEs within each set of subgroups monitoring the same LO. 
Proposal 9: To support the revised Option 3, the number of LOs can be determined by configuration, and the maximum number of LOs associated with multiple POs should be limited to 2 to avoid excessive increase in paging latency.
Proposal 10: The configuration of LO can be provided to the UE by system information for RRC_IDLE and RRC_INACTIVE mode.
Proposal 11: At least a slot-level offset should also be supported for the offset values between an LO and a reference PO/PF since LP-WUS in the MO can be transmitted in a slot-level.
Proposal 12: For the offset value(s) between an LO and a reference PO/PF, do not support to configure 3 offset values considering the resource overhead.
Proposal 13: Do not support repetitions of LP-WUS in multiple MOs corresponding to the same beam in a LO (i.e., R>1 is not supported).
Proposal 14: The time domain resources in one MO can be contiguous in time when LP-WUS transmission across more than one slot. Whether non-contiguous LP-WUS transmission is supported or not can be discussed further.
Proposal 15: If there is an UL transmission during LP-WUS monitoring, UE should at least suspend LP-WUS monitoring.
FFS: whether LP-WUS monitoring should be stopped or postponed or dropped can be further discussed.

TDoc file reading error

3GPP TSG RAN WG1 #120bis					  R1-2502482
Wuhan, China, April 7th – 11th, 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: For UEs corresponding to different POs monitor the same LO, following options can be considered:
Option 1: a single offset is configured for a PF and the UE wake-up delay capability.
Option 2: a single offset is configured for one or more PF and the UE wake-up delay capability. Offset is applied based on the first PF
Proposal #2: To support one-to-one mapping between LO and PO  where multiple POs are configured in a PF, multiple offset can be configured for each PO, for a given PF(s) and UE wake-up capability.
Proposal #3: To avoid the overlapping between adjacent two LOs, introduce RRC parameter to configure the duration of a LO.
Proposal #4: 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 #5: Consider these options for structuring the LP-WUS payload when multiple POs/PFs corresponds to a single LO:
Option 1: Use the same structure regardless of the number of PO/PF.
All UEs in indicated subgroups across all mapped POs need to wake up
Option 2: Different LP-WUS MOs within a LO correspond to different POs/PFs
Each MO within the LO maps to a specific single PO/PF
Proposal #6: Introduce additional symbol or slot offset as well as frame offset for determination of the first LP-WUS monitoring occasion within a LO.
Proposal #7: For remaining LP-WUS monitoring occasion within an LO, the sequential allocation methods shall be supported by one of following options:
Option 1: LMOs are allocated in consecutive OFDM symbols
Option 2: LMOs are allocated sequentially within slot boundaries
If an LMO would cross a slot boundary, it starts at the beginning of the next slot
Option 3: Introduce pre-defined or configured LP-WUS starting points within each slot
Proposal #8: For sequential allocation of N*K LP-WUS MOs, the following ordering approaches can be considered:
Option 1: 
first, in increasing order of R 
second, in increasing order of G
third, in increasing order of M
fourth, in increasing order of N 
Option 2:
first, in increasing order of R 
second, in increasing order of G
third, in increasing order of N
fourth, in increasing order of M
Option 3: 
first, in increasing order of R 
second, in increasing order of N
third, in increasing order of G
fourth, in increasing order of M 
Proposal #9: The network shall determine the number of LP-WUS MOs for each beam in an LO using one of the following alternatives:
Alt. 1: Individual configuration of G, R, and M parameters 
Network configures G, R, and M parameters
Total number of LMOs is determined as G * R * M
Alt. 2: Hybrid configuration with total LMO constraint 
Network configures G and R parameters
Total number of LMOs K is also configured separately
M is derived from K/(G * R)
Alt. 3: Bounded configuration approach 
Network configures G, R, and M parameters
Total number of LMOs K_max is determined by LO periodicity and LMO duration. Actual LMOs is bounded by K_max
Proposal #10: For repetition and multiple information support, adopt one of the following approaches:
Alt. 1: Network ensures either R>1 with M=1, or M>1 with R=1
Alt. 2: It is up to UE capability to support values for R and M parameters that can be simultaneously greater than 1 
Alt. 3: UE reports set of supported (R, M) value combinations
Proposal #11: Either Option B or Option 3 shall be adopted for LP-WUS MO
Proposal #12: For UE capability report on the wake-up delay, consider following options to derive sets of 3 candidate value for different SSB periodicities:
Option 1: Reporting alternative wake-up delay assuming larger SSB periodicities: 
Support that UEs additionally reports wake-up delays assuming alternative SSB periodicities (e.g., 40ms, 80ms or 160ms). If a non-reported SSB periodicity is configured, use the reported value corresponding to the closest configured SSB period to derive actual wake-up delay.
Option 2: Table-Based Reporting: 
This option maintains Alt. 1 structure by utilizing pre-defined table indices linked to SSB periodicity ranges. UEs report an index (Low/Mid/High) only and use the index with the current SSB periodicity to determine the wake-up delay from a predefined table.
Proposal #13: UEs with different wake-up delay should be assigned to different UE subgroups
Proposal #14: 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 #15: 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. 

TDoc file reading error

3GPP TSG RAN WG1 #120bis			R1-2502581
Wuhan, China, April 7th – 11th, 2025

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

Conclusion
From RAN1 perspective, there is no consensus on the following proposal:
UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if	the UE has not received LP-WUS for a long time.


For future meetings:
Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.

Agreements from RAN1#120 meeting
Agreement
The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.
FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement
For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.
The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.
FFS other offset value(s) to determine the MOs of the LO

Agreement
The previous agreement in RAN1#119 is updated as follows:
Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement
Confirm the following working assumption with the additional text in red:
Working Assumption
From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.
Above is applicable for both time-domain processing or frequency-domain processing
Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications
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.
The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.
FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.



Agreement
For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).
This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO. 

Agreement
For UE capability report on the wake-up delay:
Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.
The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization. 
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities
Send an LS to RAN4 after the down-selection to confirm the number of SSBs. Final LS in R1-2501624.

Agreement
For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.
gNB can configure 1 or 2 offset values.
FFS whether gNB can configure 3 offset values
If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.
Note: if a single offset value is configured, UE behaviour is according to Option 1-1. 
All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

Agreement
Confirm the following working assumption with the modification:
Working Assumption
The maximum number of subgroups per PO supported in Rel-19 is 31 32. 

3GPP TSG RAN WG1 #120bis	                                         	           R1-2502616
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.6.2

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

Conclusion
From RAN1 perspective, there is no consensus on the following proposal:
UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if	the UE has not received LP-WUS for a long time.

For future meetings:
Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.
RAN1#120 agreements
Agreement
The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.
FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement
For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.
The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.
FFS other offset value(s) to determine the MOs of the LO

Agreement
The previous agreement in RAN1#119 is updated as follows:
Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement
Confirm the following working assumption with the additional text in red:
Working Assumption
From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.
Above is applicable for both time-domain processing or frequency-domain processing
Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications
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.
The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.
FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.

Agreement
For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).
This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO. 

Agreement
For UE capability report on the wake-up delay:
Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.
The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization. 
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities
Send an LS to RAN4 after the down-selection to confirm the number of SSBs. Final LS in R1-2501624.

Agreement
For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.
gNB can configure 1 or 2 offset values.
FFS whether gNB can configure 3 offset values
If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.
Note: if a single offset value is configured, UE behaviour is according to Option 1-1. 
All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

Agreement
Confirm the following working assumption with the modification:
Working Assumption
The maximum number of subgroups per PO supported in Rel-19 is 31 32. 

3GPP TSG RAN WG1 #120bis	                                         	           R1-2502618
Wuhan, China, April 7th – 11th, 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
From RAN1 perspective, there is no consensus on the following proposal:
UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if	the UE has not received LP-WUS for a long time.

For future meetings:
Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.

RAN1#120 agreements
Agreement
The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.
FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement
For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.
The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.
FFS other offset value(s) to determine the MOs of the LO

Agreement
The previous agreement in RAN1#119 is updated as follows:
Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement
Confirm the following working assumption with the additional text in red:
Working Assumption
From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.
Above is applicable for both time-domain processing or frequency-domain processing
Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications
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.
The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.
FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.

Agreement
For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).
This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO. 

Agreement
For UE capability report on the wake-up delay:
Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.
The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization. 
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities
Send an LS to RAN4 after the down-selection to confirm the number of SSBs. Final LS in R1-2501624.

Agreement
For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.
gNB can configure 1 or 2 offset values.
FFS whether gNB can configure 3 offset values
If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.
Note: if a single offset value is configured, UE behaviour is according to Option 1-1. 
All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

Agreement
Confirm the following working assumption with the modification:
Working Assumption
The maximum number of subgroups per PO supported in Rel-19 is 31 32. 

3GPP TSG RAN WG1 #120bis	                                         	           R1-2502619
Wuhan, China, April 7th – 11th, 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
From RAN1 perspective, there is no consensus on the following proposal:
UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if	the UE has not received LP-WUS for a long time.

For future meetings:
Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.

RAN1#120 agreements
Agreement
The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.
FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement
For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.
The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.
FFS other offset value(s) to determine the MOs of the LO

Agreement
The previous agreement in RAN1#119 is updated as follows:
Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement
Confirm the following working assumption with the additional text in red:
Working Assumption
From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.
Above is applicable for both time-domain processing or frequency-domain processing
Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications
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.
The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.
FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.

Agreement
For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).
This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO. 

Agreement
For UE capability report on the wake-up delay:
Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.
The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization. 
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities
Send an LS to RAN4 after the down-selection to confirm the number of SSBs. Final LS in R1-2501624.

Agreement
For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.
gNB can configure 1 or 2 offset values.
FFS whether gNB can configure 3 offset values
If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.
Note: if a single offset value is configured, UE behaviour is according to Option 1-1. 
All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

Agreement
Confirm the following working assumption with the modification:
Working Assumption
The maximum number of subgroups per PO supported in Rel-19 is 31 32. 

3GPP TSG RAN WG1 #120bis	                                         	           R1-2502620
Wuhan, China, April 7th – 11th, 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
From RAN1 perspective, there is no consensus on the following proposal:
UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if	the UE has not received LP-WUS for a long time.

For future meetings:
Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.

RAN1#120 agreements
Agreement
The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.
FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement
For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.
The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.
FFS other offset value(s) to determine the MOs of the LO

Agreement
The previous agreement in RAN1#119 is updated as follows:
Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement
Confirm the following working assumption with the additional text in red:
Working Assumption
From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.
Above is applicable for both time-domain processing or frequency-domain processing
Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications
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.
The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.
FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.

Agreement
For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).
This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO. 

Agreement
For UE capability report on the wake-up delay:
Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.
The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization. 
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities
Send an LS to RAN4 after the down-selection to confirm the number of SSBs. Final LS in R1-2501624.

Agreement
For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.
gNB can configure 1 or 2 offset values.
FFS whether gNB can configure 3 offset values
If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.
Note: if a single offset value is configured, UE behaviour is according to Option 1-1. 
All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

Agreement
Confirm the following working assumption with the modification:
Working Assumption
The maximum number of subgroups per PO supported in Rel-19 is 31 32. 

3GPP TSG RAN WG1 #120bis	                                         	           R1-2502621
Wuhan, China, April 7th – 11th, 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
From RAN1 perspective, there is no consensus on the following proposal:
UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if	the UE has not received LP-WUS for a long time.

For future meetings:
Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.

RAN1#120 agreements
Agreement
The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.
FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement
For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.
The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.
FFS other offset value(s) to determine the MOs of the LO

Agreement
The previous agreement in RAN1#119 is updated as follows:
Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement
Confirm the following working assumption with the additional text in red:
Working Assumption
From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.
Above is applicable for both time-domain processing or frequency-domain processing
Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications
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.
The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.
FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.

Agreement
For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).
This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO. 

Agreement
For UE capability report on the wake-up delay:
Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.
The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization. 
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities
Send an LS to RAN4 after the down-selection to confirm the number of SSBs. Final LS in R1-2501624.

Agreement
For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.
gNB can configure 1 or 2 offset values.
FFS whether gNB can configure 3 offset values
If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.
Note: if a single offset value is configured, UE behaviour is according to Option 1-1. 
All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

Agreement
Confirm the following working assumption with the modification:
Working Assumption
The maximum number of subgroups per PO supported in Rel-19 is 31 32. 

3GPP TSG RAN WG1 #120bis	                                         	           R1-2502622
Wuhan, China, April 7th – 11th, 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
From RAN1 perspective, there is no consensus on the following proposal:
UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if	the UE has not received LP-WUS for a long time.

For future meetings:
Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.

RAN1#120 agreements
Agreement
The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.
FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement
For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.
The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.
FFS other offset value(s) to determine the MOs of the LO

Agreement
The previous agreement in RAN1#119 is updated as follows:
Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement
Confirm the following working assumption with the additional text in red:
Working Assumption
From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.
Above is applicable for both time-domain processing or frequency-domain processing
Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications
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.
The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.
FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.

Agreement
For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).
This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO. 

Agreement
For UE capability report on the wake-up delay:
Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.
The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization. 
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities
Send an LS to RAN4 after the down-selection to confirm the number of SSBs. Final LS in R1-2501624.

Agreement
For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.
gNB can configure 1 or 2 offset values.
FFS whether gNB can configure 3 offset values
If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.
Note: if a single offset value is configured, UE behaviour is according to Option 1-1. 
All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

Agreement
Confirm the following working assumption with the modification:
Working Assumption
The maximum number of subgroups per PO supported in Rel-19 is 31 32. 

3GPP TSG RAN WG1 #120bis	                           R1-2502676
Wuhan, China, April 7th – 11th, 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:
Proposal 1: A LO can be associated with POs in one PF, and the max number of associated POs per LO can be Ns.
Proposal 2: Confirm the working assumption that Option 3 and Option B are not needed if the LP-WUS design supports 32 subgroups within one LP-WUS MO.
Proposal 3: Support option3 if the maximum number of subgroups within one LP-WUS MO is less than 32.
Proposal 4: Support simple repetition of the same LP-WUS information within an LP-WUS occasion.
Proposal 5: Consider the use of a slot-level offset to determine the start point for MOs in an LO.
Proposal 6: The gap between offset values should be a multiple of paging cycles.
Proposal 7: Consider two options for providing LP-WUS QCL information:
Implicitly, using the beam index within the LP-WUS monitoring occasion
Configured LP-WUS resources with TCI state for each beam.

3GPP TSG RAN WG1 Meeting #120-bis	R1-2502712
Wuhan, China, April 7th – 11th, 2025

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

Summary
In this contribution, the following observations and proposals are provided:
Observation 1: Limiting MOs to a single contiguous slot simplifies implementation; moderate repetition enhances detection reliability without excessive overhead; multiple MOs configured via RRC provide clarity and flexibility.

Proposal 1: Fix MOs to a single slot, allow up to two identical repetitions per LO, and ensure explicit RRC-based configuration of multiple MOs for straightforward management.

Observation 2: Multiple POs per LO can enhance eDRX flexibility but should be limited to two to balance power savings and paging coverage; coordination with RAN2 is vital for smooth scheduling alignment.

Proposal 2: Permit up to two POs per LO to maintain efficient power usage, with possible expansion to four if justified; coordinate with RAN2 for consistent RRC configuration and paging schedules.

Observation 3: A third offset adds complexity without benefit; the existing two offsets adequately cover latency and alignment needs.

Proposal 3: Retain only two offsets, clarify their usage, and coordinate with RAN2 to support flexible wake-up scenarios.

Observation 4: Granting separate EPRE settings for LP-WUS and LP-SS helps balance power efficiency and measurement accuracy, yielding optimal configuration flexibility.

Proposal 4: Configure EPRE separately for LP-WUS and LP-SS, with distinct RRC and RF parameters enabling independent optimization for power efficiency and measurement reliability.

Observation 5: Independent LP-SS measurement timing significantly enhances flexibility, energy efficiency, and measurement reliability compared to strict SMTC-based approaches.

Proposal 5: Eliminate SMTC-based constraints, enabling standalone LP-SS timing that is RRC-configurable and optimally aligned with actual LP-SS transmissions for improved power saving and monitoring.

Observation 6: Existing LP-SS-based measurements apply directly to OFDM-based WUR; improved processing offers potential accuracy gains without altering fundamental definitions.

Proposal 6: Confirm unchanged measurement definitions for OFDM-based WUR; coordinate with RAN4 to address performance-validation criteria instead of redefining measurements.

Observation 7: Using QCL-Type C and D for LP-WUS/LP-SS signals and mapping them one-to-one to SSB beams simplifies beam detection and avoids unnecessary dynamic signaling.

Proposal 7: Fix QCL-Type C and D for stable beam association, use implicit one-to-one LP-WUS/LP-SS to SSB mapping, and add RRC signaling if partial coverage is required.

Observation 8: Enforcing one-to-one mapping avoids detection ambiguity, enhances beamforming gains, and ensures consistent beam coverage.

Proposal 8: Mandate a strictly one-to-one beam mapping to preserve reliability, streamline beam management, and simplify UE/network implementations.

3GPP TSG RAN WG1 #120bis			R1-2502774
Wuhan, China, April 7th – 11th, 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 observations and proposals were made:
Observation 1:
Overlapping of LO resources configuration would cause higher FAR since LP-WUS could be transmitted to UEs belonging to different LOs
Observation 2:
In case of 8 symbols per MO without FDM operation, the total time duration of LOs in 1 I-DRX cycle could be larger than I-DRX cycle
Observation 3:
LO resources are overlapped when time duration of PFs associated with a LO is shorter than the LO time duration at least in case of number of PFs in I-DRX cycle, N=T and SCS 15kHz
Observation 4:
Option 3 (UEs corresponding to the same POs monitor the different LO) and Option B (TDMed solution) cannot provide enough better coverage since option 3 and option B cannot reduce information bit due to FAR requirements
Proposal 1:
Support FDM of multiple LOs
FFS: How UE determines frequency resource of LO
Do not support FDM of MOs within the same LO
Proposal 2:
I-DRX cycle should be larger than wake-up delay values

Proposal 3:
If trs-ResourceSetConfig is provided, the UE can receive TRS resource set(s) after wake-up indication
Proposal 4:
No conditions/restrictions for mapping multiple POs to one LO
Proposal 5:
Support 4 for max number of POs per LO in option 2 if FDM of multiple LOs is not supported
Proposal 6:
Confirm WA with following modification
If LP-WUS design support 31 subgroups within one MO, do not support Option 3 for LO to PO mapping or Option B for MO configuration
Proposal 7:
3 time offset values between a LO and a reference PO/PF should not be supported
Proposal 8:
The start of LO and the start of first MO should be same
Time gap between two consecutive MOs should not be supported
Proposal 9:
Further consider independent LP-WUS subgrouping from PEI subgrouping
Proposal 10:
Support only duty cycle monitoring for LP-WUS
Proposal 11:
RAN1 firstly discuss LP-WUS operation with I-DRX before eDRX
Proposal 12: 
For idle/inactive mode, RAN1 does not discuss further carrying additional information other than subgroup-based wake-up indication and ETWS/CMAS notification
If entry/exit procedure for LP-WUS monitoring can ensure that paging misdetection performance is not impacted by LP-WUS detection, ETWS/CMAS notification should not be conveyed by LP-WUS payload
Note: LP-SS may or may not carry the cell ID information, and LP-SS or other sequence generation may or may not be associated with PCIs
Proposal 13:
For RRM based on OFDM-based LP-WUR, SMTC window for measurement time resources(s) restriction is not applicable for LP-SSS-RSRP/RSSI measurement. 
Proposal 14:
Before discussing the details on [LP-WUS/LP-SS_startRB_IDLE/INACTIVE] in higher layer parameters list, followings should be firstly discussed
Whether to support FDM of LOs
Proposal 15:
The maximum number of [MONumPerLO] in higher layer parameters list should be 4
Proposal 16:
[subgroupNumber PO_LPWUS] should be discussed/determined in RAN1
Proposal 17:
The maximum number of [PO-to-LO association] in higher layer parameters list should be 4 if FDM of LOs is not supported
Proposal 18:
For [LO_offset] in higher layer parameters list,
Up to 2 time offset values in frame level between a LO and a reference PO/PF can be configured
do not support symbol level offset values
Proposal 19:
[Entry/Exit_condition_OOK/OFDM] should not be captured in RAN1 RRC parameter list

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502806
Wuhan, China, April 7th – April 11th, 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.
Observation 2	Using LP-WUS together with very long DRX duty cycle may have little power saving gain but negative paging latency impact.
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 within the initial DL BWP.
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.
Proposal 10	For the offset value configured by gNB, support maximum 2 configured values.
Proposal 11	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-WUS MO 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	Support Option A for configuration of LP-WUS MOs for the same beam in an LO.
o	UE monitors up to K MOs.
o	R =1 (i.e., K = R*M = M)
Proposal 13	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 WUR configuration.
Proposal 14	Support only configuration of duty-cycled WUR monitoring in Rel-19.
Proposal 15	The number of POs addressable by LP-WUS monitored in a MO is up to 2. More than one PO is only configured if the number of configured UE subgroups per PO is less than 16
Proposal 16	Entry/exit conditions should be configurable, e.g., as part of the LP-WUS configuration.
Proposal 17	It should be possible to configure different entry/exit conditions based on supported WUR types, if any.
Proposal 18	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.

3GPP TSG RAN WG1 #120-bis			R1-2502847
Wuhan, China, April 7th – 11th, 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: Specify symbol-level offset from the start of the frame determined by the frame level offset to the start of the first LP-WUS MO of the LO. This can follow firstPDCCH-MonitoringOccasionOfPEI-O for PEI.
Proposal 2: Support network configures up to 3 offset values.
Proposal 3: For the UE to monitor PEI after it receives LP-WUS, the gap between the end of the last LP-WUS MO the UE monitors in the LO and the start of the PEI occasion is configured to be no less than the wake-up delay supported by the UE.
Proposal 4: Support 4 for max number of POs per LO.
Observation 1: There is generally no integer multiple relationship between the number of codepoints per LP-WUS and the number of UE subgroups per PO. 
Proposal 5: Support sequential mapping of the common codepoint and UE subgroup specific codepoints to codepoints provided by LP-WUS in MOs of the LO. 
Proposal 6: Support only configuring the common codepoint indicating all UE subgroups associated with the LO in the first LP-WUS MO of the LO. 
Proposal 7: Support configuring the common codepoint as the last codepoint provided by the LP-WUS in the LP-WUS MO. 
Proposal 8: support same EPRE ratio configuration for LP-WUS and LP-SS.
Proposal 9: Do not support different number of OOK ON symbols in different OFDM symbols.
Proposal 10: RAN1 asks RAN4 whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.
Observation 2: For the typical 1% to 3% per UE subgroup paging rate and 32 UE subgroups, about 0.5 to 1.2 LP-WUS MOs are needed to fully convey the paging information in each iDRX cycle. 
Observation 3: 4 LP-WUS MOs consume 6 to 15 times the resources for paging PDCCH transmission in SCS 30 kHz. 
Observation 4: For users without strict paging delay requirement, more resource efficient LP-WUS MO configuration solutions exist to reduce the LP-WUS resource overhead.
Observation 5: Overlaid sequences allow LP-WUS and LP-SS to achieve full cell coverage. 
Proposal 11: LP-WUS and LP-SS are transmitted in all beams of the transmitted SSBs in a cell.
Observation 6: Independent subgrouping between LP-WUS and PEI improves the subgrouping granularity.
Proposal 12: Support the UE monitoring PEI after receiving LP-WUS indicating wakeup to enhance the UE subgrouping granularity.

3GPP TSG RAN WG1 #120b	R1-2502879
Wuhan, China, Apr 7th - Apr 12th, 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:
Observation-1: Whether 32 sub-groups can be supported by all possible configurations of LP-WUS is not yet clear.
Proposal-1: LP-WUS repetitions (if any) are defined within a MO, i.e. R=1. Each LP-WUS repetition is confined within a slot. Repetitions can be separated by “short”gaps.

Proposal-2: Support separate EPRE offset for LP-SS and LP-WUS.  
Proposal-3: Maximum number of POs per LO is 4, POs are consecutive POs of the same paging frame.
Proposal-4: Do not support 3rd offset value.
Proposal-5: 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 Meeting #120-bis	     R1-2502907
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.6.2
Source:	Lenovo
Title:	Discussion on LP-WUS operation in Idle/Inactive modes
Document for:	Discussion

Conclusions
In this contribution, considerations of LP-WUS operation in idle mode/inactive modes are provided. 
Proposal 1: Discuss LPWUS sub-band blocks FDMed with multiple MOs and how the LPWUS subgroup IDs in MOs are mapped to the FDMed LPWUS sub-band blocks to reduce network power consumption. 
Proposal 2: Support UEs corresponding to different POs monitor the different LO, LOs are separated according to the wakeup delay or resource offset from PO.
Proposal 3: UEs monitoring the same or different PO are divided into multiple sets of subgroup according to the wakeup delay or resource offset from PO, with UEs within each set of subgroups monitoring the same LO.
Proposal 4: Support option 2A - A UE does not expect that the gap between the LO associated with the largest offset and the corresponding PO is less than the wake-up delay the UE supports. The UE monitors the LO associated with one offset that has a gap between the LO and the corresponding PO no less than the wake-up delay. 
Proposal 5: For gNB can configure UEs of different wake up delays to different LOs.  
Proposal 6: LO periodicity can be separated based on their wake-up delay offsets. 
UEs with shorter wakeup delay monitor LO frequently 
UEs with longer wakeup delay monitor LO less frequently  

3GPP TSG RAN WG1 #120bis	                                         	           R1-2503147
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.6.2

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

Conclusion
From RAN1 perspective, there is no consensus on the following proposal:
UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if	the UE has not received LP-WUS for a long time.

For future meetings:
Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.

RAN1#120 agreements
Agreement
The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.
FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement
For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.
The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.
FFS other offset value(s) to determine the MOs of the LO

Agreement
The previous agreement in RAN1#119 is updated as follows:
Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement
Confirm the following working assumption with the additional text in red:
Working Assumption
From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.
Above is applicable for both time-domain processing or frequency-domain processing
Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications
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.
The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.
FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.

Agreement
For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).
This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO. 

Agreement
For UE capability report on the wake-up delay:
Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.
The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization. 
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities
Send an LS to RAN4 after the down-selection to confirm the number of SSBs. Final LS in R1-2501624.

Agreement
For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.
gNB can configure 1 or 2 offset values.
FFS whether gNB can configure 3 offset values
If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.
Note: if a single offset value is configured, UE behaviour is according to Option 1-1. 
All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

Agreement
Confirm the following working assumption with the modification:
Working Assumption
The maximum number of subgroups per PO supported in Rel-19 is 31 32.