3GPP TSG-RAN WG2 Meeting #130	 R2- 2503568
St Julian’s, Malta, May 19-23, 2025

Agenda Item:	8.4.2
Source: 	NEC
Title:  	Discussion on LP-WUS in RRC_IDLE INACTIVE
Document for:	Discussion and Decision
1 

Conclusions
Proposal-1: RAN2 to make down selection between the following options for value of X:
Option-1: UE_ID: 5G-S-TMSI mod X, where X is 1048576 (20 bits).
Option-2: UE_ID: 5G-S-TMSI mod X, where X is 1048576 (20 bits), if eDRX is applied; otherwise, X is 262144 (18 bits).
Proposal-2(RRC-12): support dedicated enable/disable indication in RRCRelease to indicate whether the UE needs to apply LP-WUS feature or not during RRC_IDLE/INACTIVE.
Proposal-3(RRC-12): the UE who receives dedicated enable indication in RRCRelease still can apply LP-WUS feature in different LP-WUS supporting cell, i.e., mobility case is supported.
Proposal-4: down-select between the following solutions for OFDM-based LR which is capable of measuring both SSB and LP-SS:
Solution-1: introduce one indication (e.g., RS-Type) in LP-WUS configuration to indicate which reference signal (SSB or LP-SS) is used for condition evaluation by the UE.
Solution-2: SSB is always used for condition evaluation if the SSB-based condition is available.
Proposal-5: RAN2 is suggested to consider optimization on cell reselection, e.g., LP-WUS supporting information of neighbour cell is provided in serving cell to optimize cell reselection.
4 

3GPP TSG RAN2 Meeting #130                                                                R2-2503603
19th May – 23rd May 2025, St.Julians, Malta
                                             	
Agenda item:	8.4.2
Source:	Samsung
Title:	Procedure and Configuration of LP-WUS in RRC Idle /
Inactive Mode
Document for:	Discussion & Decision

Conclusion
RAN2 is requested to discuss and agree to the following proposals:

Proposal 1: The entry/exit conditions of LP-WUS monitoring may optionally include low mobility criterion based on serving cell quality from MR (FFS LR)

Proposal 2: In case PEI is configured in the cell and UE supports PEI:
If the gap between the monitored LO and the UE’s PEI-O is >= the wake-up delay, UE monitors PEI-O after receiving LPWUS. Otherwise, UE does not monitor PEI-O after receiving LPWUS.

3GPP TSG-RAN WG2 Meeting #130		R2-2503613
St. Julian’s, Malta, 19th – 23rd May 2025
Source:	vivo
Title:	Discussion on LP-WUS/WUR in RRC_IDLE/INACTIVE
Agenda Item:	8.4.2
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the remaining issues for RRC_IDLE/ INACTIVE procedures with LP-WUR. Based on the discussion, we have the following observations and proposals.
Observation 1: It could achieve some power saving gain to introduce the per UE enable/disable mechanism with dedicated signaling in some special case. 
Observation 2: According to the RAN1 agreement, when UE supports PEI and PEI is configured by the gNB, after the UE receives LP-WUS indicating wake-up, it is up to UE implementation whether to monitor PEI or not.
Observation 3: Introduce separate UE capabilities for CN assigned subgrouping and UE_ID based subgrouping for LP-WUS, similar as PEI design.
Observation 4: UE capability for supporting LP-WUS (assuming capability for OFDM-based WUR or OOK-based WUR), indicates supporting of UE_ID based subgrouping, i.e. capability supporting LP-WUS and UE_ID based subgrouping is one capability, similar as PEI design. 
Enable/disable LP-WUS(RRC-12)
Proposal 1: (RRC-12) Using NAS signalling to enable/disable the LP-WUS functionality per UE for UEs supporting LP-WUS. 
Proposal 2: If the network supports the OOK-based WUR, the LP-SS configuration should always be provided.
Coexistence between MBS group notification and LP-WUS (38304-5)
Proposal 3: (38304-5) UEs expecting MBS group notification should monitor its PO to receive the MBS group notification regardless of LP-WUS.
LP-WUS in last used cell (38304-8)
Proposal 4: (38304-8) UE could use LP-WUS in any cell, i.e. there is no need to introduce lastUsedCellOnly.
Value range of configured threshold (RRC-6 related)
Proposal 5: (RRC-6) The value range for the threshold on the measured RSRP/RSRP via LR could refer to the absolute measured values for MR. Details could be discussed in the running CR. 
Coexistence between eDRX and LP-WUS
Proposal 6: Following the same mechanism as the coexistence between PEI and eDRX, for LP-WUS:
When eDRX is configured to be longer than 10.24s, LP-WUS is used to control PO monitoring within the PTW. 
When eDRX is configured to be 5.12s or 10.24s, LP-WUS is used to control the PO monitoring.
Entry/exit condition for LP-WUS monitoring
Proposal 7: RAN2 assumes the entry/exit thresholds for LP-WUS monitoring for OFDM-based WUR measuring LP-SS only are the same as that for OOK-based WUR measuring LP-SS. It can be revisited based on RAN1/RAN4 process, if any. Network is allowed to provide either OOK based threshold or OFDM based WUR measuring SSB threshold or both. 
Proposal 8: RAN2 confirms the MR thresholds of entry/exit condition for LP-WUS monitoring can be configured separately for different types of LR if a cell supports both types of LRs (can revisit based on RAN1 and RAN4 progress, if any), similar as criteria for RRM relaxation.
Other wake up conditions
Proposal 9: MR should wake up for UE-initiated UL transmission, e.g. RACH/MO-SDT, due to UL data and signaling arrival when monitoring LP-WUS. And no specification impact is foreseen.
UE monitors both LP-WUS and PEI
Proposal 10: No need to introduce a network indication to indicate UE to monitor both LP-WUS and PEI or not. 
Emergency PDU session
Proposal 11: Follow the same principle as SA2 on emergency PDU session with LP-WUS, i.e., UE could monitor LP-WUS when there is an active emergency PDU Session in RRC_IDLE/RRC_INACTIVE.
UE capability
Proposal 12: RAN2 assumes separate UE capabilities for different LR types, i.e. OFDM-based WUR and OOK-based WUR, should be introduced and reported to the network. Final decision is up to RAN1.
Proposal 13: The capability reporting design for PEI is reused for LP-WUS, i.e. UE reports capability of supporting the CN assigned subgrouping to CN during the registration request or TAU procedure; UE reports the combined capability to indicate supporting LP-WUS and UE_ID based subgrouping to RAN via UE-RadioPagingInfo IE in the RRC UECapabilityInformation message.
Proposal 14: Whether a UE supports serving cell/neighboring cell RRM relaxation and serving cell RRM offloading should be defined as two components (one is for serving cell/neighboring cell RRM relaxation, the other is for serving cell RRM offloading) of the basic feature for LP-WUS. 

TDoc file reading error

3GPP TSG-RAN WG2 Meeting #130                                                                    R2-2503659
St. Julian’s, Malta, 19th – 23rd May 2025

		
Source:	CATT 
Title:	Remaining issues on LP-WUS in IDLE and INACTIVE
Agenda Item:	8.4.2
Document for:	Discussion and Decision

Conclusion
According to the analysis in Section 2, we propose:
Proposal 1: (RRC-12) Enabling/disabling LP-WUS monitoring in IDLE/INACTIVE per UE is supported.
Proposal 2: (RRC-12) RAN2 consider UE to determine whether to enable/disable LP-WUS monitoring in IDLE/INACTIVE based on latency requirement (i.e., i-DRX cycle of the UE).
Proposal 3: X is dependent on if eDRX is applied without considering different cases of Np
If eDRX is not applied, X=262144 (256*4*8*32).
If eDRX is applied, X= 1048576 (1024*4*8*32).

3GPP TSG-RAN WG2 Meeting #130										R2-2503763
St Julian, Malta, 19th – 23rd May, 2025                               		Revision of R2-2501960
Agenda item:		8.4.2
Title: 	Procedure and configuration of LP-WUS for IDLE and INACTIVE mode
Source: 			ZTE Corporation, Sanechips
Document for: 	Discussion and Decision

Conclusion
The following proposals are given based on the above analysis:
Provision of LP-WUS related configuration
Observation 1: More power saving gain can be achieved if LP-WUS monitoring and RRM Relaxation/Offloading are performed simultaneously.
Proposal 1: UE monitors LP-WUS only when it is in serving cell offloading state or in Rel-19 RRM relaxation state, i.e. the entry/exit condition for serving cell offloading and relaxation can be reused for LP-WUS monitoring without configuring separate thresholds.
Activation/deactivation of LP-WUS
Observation 2: LP-WUS monitoring may result in additional latency compared to legacy paging procedure and hence, it is useful to support per UE activation of LP-WUS monitoring in addition to the per cell configuration.
Observation 3: CN does not know the radio resource configuration status and UE’s capability, it is difficult for CN to decide whether the LP-WUS is suitable for the UE.
Proposal 2: In addition to the SIB signaling for LP-WUS configuration, dedicated activation/deactivation of LP-WUS per UE is supported. 
Proposal 2a: If activation/deactivation of LP-WUS in IDLE/INACTIVE modes by UE dedicated signaling is supported, send LS to RAN3 to provide LP-WUS activation/deactivation indication to the paging gNB, e.g., via NGAP Signaling, NGAP PAGING and RAN PAGING message.
Time offset between LP-WUS and PO
Proposal 3a: Introduce UE reporting wake-up delay as part of the UE capability, which is also an implicit indication of UE supporting LP-WUS in RRC_IDLE/RRC_INACTIVE state.
Proposal 3b: Network configures time offset(s) that can be used between LO and MR PDCCH monitoring.
Proposal 3c: UE determine the time offset to be used based on its reported wake-up delay as part of the UE capability and the time offset(s) configured by network, e.g. select the minimal time offset configured by network that is larger than or equal to its reported wake-up delay. If there is no time offset configured by network that is larger than or equal to its reported wake-up delay, the UE does not monitor LP-WUS.
Proposal 4: The UE reported wake-up delay is included in ue-RadioPagingInfo-r17 IE of UECapabilityInformation message, so that it can be delivered to paging gNB transparently.
Proposal 5: When one LO associates with multiple continuous POs, the time offset is relative to the reference PO. And how to determine the reference PO require more RAN1 input.
LP-WUS and eDRX  
Proposal 6: When eDRX is configured, UE only monitors LP-WUS during the PTW and/or shortly before the start of the PTW, e.g. with a time offset before the PO to be monitored.
Proposal 6a: UE monitors LP-WUS with a time offset before the reference PO, no matter whether the eDRX is configured or not. 
Whether LP-WUS is only used in the last used cell or in any cell
Proposal 7: An indication (e.g. lastUsedCellOnly_LPWUS) is introduced to control whether UE only monitors LP-WUS in the cell where the latest RRCRelease without noLastCellUpdate is received.

3GPP TSG-RAN WG2 Meeting #129bis                                                                        R2-2503790
Malta, May 19th – 23rd , 2025
Agenda item:	8.4.2
Source:	China Telecom
Title:	Discussion on LP-WUS in RRC_IDLE and INACTIVE
Document for:	Discussion

Conclusions
Based on the discussion in the previous sections, we provide the following proposals:
Proposal 1: RAN2 to introduce the entry/exit conditions of LP-WUS monitoring as Rel-16 the low mobility criterion.
Proposal 2: Measurement results derived from LR can represent serving cell quality for LP-WUS monitoring to ensure alignment and applicability.
Proposal 3: A new configurable time window need to be introduced in addition to the existing threshold-based entry conditions for LP-WUS monitoring.

TDoc file reading error

3GPP TSG-RAN WG2 Meeting #130			         R2-2503837
St.Julians, Malta, May 19th – 23rd, 2025
Agenda Item:	8.4.2
Source: 	LG Electronics Inc.
Title:         	Remaining issues on LP-WUS in RRC IDLE or INACTIVE
Document for: 	Discussion and Decision

Conclusion
Proposal 1	UEs expecting MBS group notification does not monitor LP-WUS.
Proposal 2	Support a unified entry condition for LP-WUS monitoring and Rel-19 RRM relaxation. 
Proposal 3	Do not unify the entry/exit condition for LP-WUS monitoring and RRM offloading. (I.e. when network configures LP-WUS monitoring and RRM offloading without Rel-19 RRM relaxation, separate entry/exit conditions are configured for those two features.)
Proposal 4	The entry/exit condition for LP-WUS monitoring is mandatory in LP-WUS configuration.
Proposal 5	Support LP-WUS monitoring de-activation per UE via NAS signalling.

3GPP TSG-RAN WG2 Meeting #130										R2-2503867
St Julian’s, Malta, 19 – 23 May 2025
Agenda item		: 8.4.2
Title				: Open issues on LP-WUS in IDLE/INACTIVE mode
Source				: Tejas Networks Limited
Document for		: Discussion and Decision

Conclusion
Proposal 1: In UE_ID based LP-WUS subgrouping, UE_ID is calculated as 5G-S-TMSI mod X, X is 1048576.
Proposal 2: UE is not expected to use LP-WUS (if supported and configured) , if UE is expecting/monitoring for a group paging notification. 
Proposal 3: RAN2 to consider evaluation time period for which the entry/exit conditions needs to be satisfied to switch between LR/MR. 
Proposal 4: Entry/Exit condition is mandatorily present as part of the LP-WUS configuration broadcasted by network to enable LP-WUS feature

TDoc file reading error

3GPP TSG-RAN WG2 Meeting #130	R2-2503900
Malta, May 19th – 23th, 2025

Agenda item:	8.4.2
Source:	Huawei, HiSilicon
Title:	Further discussion on the LP-WUS in RRC_IDLE/INACTIVE mode
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss procedure and configuration of LP-WUS for IDLE/INACTIVE modes, and have the following proposals:
Proposal 1: The UE_ID in the formula of UE_ID based subgrouping for LP-WUS is determined by UE_ID = 5G-S-TMSI mod X, where X is 1048576, if eDRX is applied; otherwise, X is 262144.
Proposal 2: (RRC-12) The CN indicates whether LP-WUS capable UE(s) is/are allowed to use the LP-WUS functionality by NAS signaling: the absence of indication means UE is allowed to use LP-WUS functionality, and presence of indication to disable means UE is not allowed to use LP-WUS functionality. 
Proposal 2a: If above proposal is agreed, send LS to SA2/CT1/RAN3 to inform the agreement and to update the signalling between CN and RAN.
Proposal 3: It is up to NW implementation to configure LP-SS for OOK-based and/or OFDM-based LP-WUR.
Proposal 4: If the LP-WUS entry threshold based on LP-WUR is configured, it is up to UE implementation how to obtain the LP-WUR measurement results used for LP-WUS entry condition.

3GPP TSG-RAN WG2 Meeting #130	R2-2503953
St.Julians, Malta, May 19th – 23rd, 2025

Agenda item:	8.4.2
Source:	Huawei, HiSilicon, vivo, CMCC, CATT, Nokia, Samsung, LG Electronics Inc., Apple, Ericsson, OPPO, Sharp, NEC
Title:	Discussion on prioritizing the frequencies supporting LP-WUS
Document for:	Discussion and Decision

Conclusion
In this paper, we discuss to prioritize the frequencies supporting LP-WUS, and suggest to agree the following proposal.
Proposal 1: Support 1-bit flag for each inter-frequency in SIB. If the flag is set to true for a frequency and UE supports LP-WUS on this frequency, UE can consider this frequency to be the highest priority.

TDoc file unavailable

3GPP TSG RAN WG2#130	R2-2504264
St Julian’s, Malta, 19th - 23rd May 2025


Agenda item:	8.4.2
Source:	Nokia
Title:	LP-WUS in IDLE and INACTIVE
WID/SID:	NR_LPWUS-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion

The following is proposed based on the discussion:

Proposal 1: Cell (re)selection rules are enhanced so that LP-WUS UE prioritizes bands supporting LP-WUS
Proposal 2: If both LP-SS based and SSB based thresholds are configured for LP-WUS monitoring, OFDM-based WUR applies the SSB-based threshold (and metric) for evaluation.
Proposal 3: LP-WUS UE may support MO-SDT and/or MT-SDT
Proposal 4: The UE can initiate MO-SDT while UE is monitoring LP-WUS
Proposal 5: NW can initiate MT-SDT while UE is monitoring LP-WUS
Proposal 6: UE monitors the legacy PEI and/or PO after receiving LP-WUS indicating wake-up and no changes to the paging occasion to be monitored are supported.
Proposal 7: It is specified when the UE supporting LP-WUS shall monitor LP-WUS and when legacy PO.
Proposal 8: The UE supporting LP-WUS shall start LP-WUS monitoring when LP-WUS monitoring entry condition (better than threshold) is fulfilled.  
Proposal 9: The UE supporting LP-WUS shall stop LP-WUS monitoring when LP-WUS monitoring exit condition (worse than threshold) is fulfilled. In this case the UE shall monitor legacy PO instead of LP-WUS. 


4	

3GPP TSG-RAN2 Meeting #130	R2-2504288
St Julian’s, Malta, 19 – 23 May 2025	Revision of R2-2502910

	
Agenda Item:	8.4.2 Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE
Source: 	Ericsson
Title:  	LP-WUS in Idle and Inactive
Document for:	Discussion and Decision

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

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

R1-2502619	Summary #2 on LP-WUS operation in IDLE/INACTIVE mode	Moderator (Apple)

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

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

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

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

R1-2503087	Draft LS on the RRM measurement metrics for OFDM-based LP-WUR	Moderator (Apple)

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

R1-2502620	Summary #3 on LP-WUS operation in IDLE/INACTIVE mode	Moderator (Apple)

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

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

R1-2502621	Summary #4 on LP-WUS operation in IDLE/INACTIVE mode	Moderator (Apple)

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

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

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

R1-2502622	Summary #5 on LP-WUS operation in IDLE/INACTIVE mode	Moderator (Apple)

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

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

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

RAN2 agreements (selection)
Sub-grouping related aspects
 LP-WUS is supported with eDRX, FFS on exact impact if any 
Use 5G-S-TMSI to determine the UE_ID in the formula of UE_ID based subgrouping for LP-WUS, i.e., UE_ID=5G-S-TMSI mod X. 
X is based on 32 subgrouping number. Details can be discussed in the running CR. 
Send LS to RAN3 (CC SA2/SA3) to inform our agreements on UE ID based subgrouping.
Correct the typo as following for the previous agreed formula of UE_ID based subgrouping for LP-WUS:
Np is the number of subgroupsNumForUEID for PEI, if configured and UE supports PEI; otherwise, Np is 1.
Confirm the principle for determining CN assigned subgrouping or UE_ID based subgrouping for PEI is reused for LP-WUS subgrouping. Details will be discussed in the running CR. 

[Post129bis][217][LPWUS] LS to RAN3 (CC SA2/SA3) to inform agreements on UE ID based subgrouping (NEC)
Agreed LS in R2-2503182

LPWUS configuration 
All the LP-WUS related configurations except for measurement configurations are provided in SIB1. FFS the details on measurement configurations.
Dedicated configuration in RRC signaling is not needed for providing LP-WUS related configuration in RRC_IDLE/INACTIVE modes.

Entry/exit condition of LPWUS monitoring
Use existing Srxlev/Squal for all MR measurement based entry/exit condition evaluation.
Use measured value for all LR measurement based entry/exit condition evaluation.

3GPP TSG-RAN WG2 Meeting #130	R2-2504363
St.Julians, Malta, May 19th – 23rd, 2025
Agenda Item:	8.4.2
Source:	InterDigital, Inc.
Title:	Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes
Document for:	Discussion
1. 

Conclusion
In this contribution, the following proposals were made:
Proposal 1: Support (de-)activation indication LP-WUS monitoring per UE via RRC release message.
Proposal 2: Upon cell reselection, a UE can reactivate LP-WUS monitoring once LP-WUS entry condition is satisfied with the reselected cell.
Proposal 3: For satisfying LP-WUS entry condition, support to use MR measurement only with LR measurement relaxation (i.e., skipping LR measurement). Detail condition is FFS.
Proposal 4: For satisfying LP-WUS exit condition, support a number of LP-WUS reception failures. 

Proposal 5: To avoid ping-pong effect, support to measure a quality of LP-WUS reception during a period time.
Proposal 6: For OFDM-based WUS, support measuring both NR-SS and LP-SS quality measurement for entry/exit conditions of LP-WUS monitoring. How to use two different metrics (e.g., NR-SS and LP-SS) for decision is further discussed.
Proposal 7: Information on neighboring cells (e.g., LP-WUS capable) should be supported.
4. 

TDoc file reading error

3GPP RAN WG2 Meeting #130	R2-2504468
St Julians, Malta, May 19th – 23rd, 2025

Agenda Item:	8.4.2
Source:	HONOR
Title:	Discussion on LP-WUS in RRC_IDLE/INACTIVE
Document for:	Discussion and Decision
1. 

Conclusions
The proposals are summarised as below.
Proposal 1：(Other open issue) UE can determine whether to disable UE-ID based subgrouping based on the wake-up delay it supports when it has an emergency PDU session.
Proposal 2: (Other issue) UE reports wake-up delay and band lists that LP-WUR supports to RAN via UE-RadioPagingInfo IE in the RRC UECapabilityInformation message.
Proposal 3: (Other issue) UE does not report LP-WUR type in UE capability message.
Proposal 4: (Other issue) RAN2 consider a finer granularity of paging probability (e.g. 1% or <1%) for LP-WUS for reporting to CN.
4. 

3GPP TSG-WG2 Meeting #130                                        			            R2-2504555
St.Julians, Malta,  May 19th – 23rd , 2025
Source:                      Qualcomm Incorporated 
Title:                          Open issues on LP-WUS operation in IDLE/Inactive state
Agenda Item:	8.4.2
Document for:	Discussion and Decision
Introduction & 

Conclusion
LP-WUS mode control 
It is up to UE implementation to choose which measurement type is used for entry/exit condition if both of SSB based measurement, OOK based LP-SS measurement types conditions are configured.
It is up to UE implementation to determine the entry/exit condition if there is no entry/exit condition configured for the supported measurement type.
eDRX support
LP-WUS is only used for eDRX with cycle no longer than 10.24s, and send LS to RAN4.
Emergency PDU session handling
RAN2 does not specify specific LP-WUS handling when the UE has an emergency PDU session. 

3GPP TSG-RAN WG2 Meeting#130	R2-2504603
St Julian, Malta, May 19th-23rd, 2025

Agenda item:		8.4.2
Source:		Lenovo
Title:		 Procedure and Configuration of LP-WUS in RRC Idle/ Inactive
Document for:		Discussion and Decision

Conclusion

This document discusses some procedures for a LR capable UE in the RRC_IDLE/ RRC_INACTIVE Mode. Following are the proposals and observations made in this document:
(RRC-3) RAN2 does not additionally specify any signaling for enable/ disable of LP-WUS feature in Idle/ Inactive modes. 
(38304-5) UEs expecting MBS group notification shall monitor its PO to receive the MBS group notification regardless of whether LP-WUS is received or not. 
(38304-8) LP-WUS is only used in the last used cell when lastUsedCellOnly  is configured in SIB.
UE may re-enter LP-WUS monitoring mode in case no paging is received in target PO(s) after being woken up by LP-WUS provided that at least the entry condition for LP-WUS monitoring is satisfied.
In the case that UE fails to monitor PEI occasion (if configured) after being woken up by LP-WUS, UE continues to monitor for the associated PO.

3GPP TSG-RAN WG2 #130	R2-2504643
Malta, MT, 19 – 23 May 2025

Source:	NTT DOCOMO, INC.
Title:	Discussion on the LP-WUS deactivation with RRC dedicated message
Document for:	Discussion and decision
Agenda Item:	8.4.2

Summary and proposal
Observation 1: NAS control cannot take the RAN implementation for LP-WUS deactivation into account.
Observation 2: To enable the gNB to implement an appropriate LP-WUS deactivation with taking RAN implementation into account, it should be possible to deactivate LP-WUS via the dedicated RRC signal i.e. RRC Connection Release.
Proposal 1: gNB control the UE to deactivate UE LP-WUS capability with dedicated signal