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

Agenda item:		8.4.1		
Source:				CATT
Title:				  	Summary of [Post129bis][208][LPWUS] Running CR for 38.304 (CATT)
Document for:	Discussion and Decision

Conclusion
According to feedback on X in UE_ID based subgrouping, we propose:
Proposal 1: RAN2 discuss which option (option 2 or option 3) is adopted for X.
Option 2: X is depended 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).
Option 3: X is 1048576, i.e., the largest UE ID range in all LP_WUS cases is be used for all LP-WUS monitoring cases.

And the following stage 3 open issues of 38.304 running CR for LP-WUS are identified:
RRM relaxation/offloading:
Open issue 38304-1: FFS on the terminology LP-WUS UE.
Open issue 38304-2: FFS (if needed) on enhancements based on R16 criteria (e.g., based on the LR measurements) for the case when MR serving cell measurement results are not available.
Open issue 38304-3: FFS on exit condition for serving cell RRM relaxation, e.g., whether a separate exit condition other than ‘not fulfilling the entry condition’ is needed, or whether exit condition include MR and/or LR-based measurements. (Same as the open issue in RRC, i.e., FFS on exit condition for serving cell RRM relaxation)
Open issue 38304-4: FFS relaxed measurement criteria/RRM offloading criteria is different from LP-WUS monitoring criteria. (Same as the open issue in RRC, i.e., FFS on whether/how to reduce the threshold number for LP-WUS/WUR)
Open issue 38304-6: Whether UE low mobility criterion or stationary criterion should be considered for RRM relaxation/offloading. (Same as the open issue in RRC, i.e., FFS on low mobility criteria)
Open issue 38304-7: Whether Relaxed measurement and offloading measurement can be performed when there is NR inter-frequency and/or NR inter-RAT frequency with reselection priority higher than that of the camped frequency. (Same as the open issue in RRC, i.e., FFS on whether/how RRM relaxation is applicable for high priority frequency)
LP-WUS in idle/inactive mode
Open issue 38304-5: FFS the UEs expecting MBS group notification should monitor its PO to receive the MBS group notification regardless of LP-WUS. 
Open issue 38304-8: Whether LP-WUS is only used in the last used cell or in any cell.

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

Agenda item:	8.4.1
Source:	ZTE Corporation, Sanechips
Title:	Summary of [Post129bis][206] LP-WUS in MR-DC
WID/SID:	NR_LPWUS-Core
Document for:	Discussion and Decision
1	

Conclusion
Based on post-meeting email discussion, the following proposals are given for formal decision:
Proposal: LP-WUS, if supported by UE, can only be configured to be monitored on the PCell, if the MN is a gNB (i.e. for NE-DC and NR-DC) and/or with LP-WUS to be monitored on the PSCell, if the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC).

3GPP TSG-RAN WG2 Meeting #130		R2-2503765
St. Julian’s, Malta, 19th – 23rd May 2025
Source:	vivo
Title:	Discussion summary and list of RRC open issue for LP-WUS WUR 
Agenda Item:	8.4.1
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss some open issues related to RRC running CR for LP-WUS and collect the open issues for LP-WUS in RRC. Based on the discussion, the following proposals have been achieved:
Open issue RRC-1 (essential): whether whether RRM relaxation configuration is provided in SIB2
Proposal 1: (11/11) RRM relaxation / offloading configuration is provided in SIB2.
Open issue RRC-2 (essential): whether entry/exit condition is mandatory or optional
Proposal 2: (8/11) The entry/exit condition for LP-WUS monitoring is mandatorily configured if the network is intended to support the LP-WUS feature
Open issue RRC-11 (essential): how to report the UAI for preferred time offset
Proposal 3: (8/9) RAN2 assumes the design of UAI reporting for preferred time offset is same as the legacy, e.g. including the configuration, procedure, as well as prohibit timer, etc. 
Other open issues:
Proposal 4: RAN2 to consider the above open issues related to RRC for LP-WUS/WUR: RRC-3 to RRC-12.

3GPP TSG-WG2 #	
, Malta, 19 -  23 May 2025

Agenda item:	8.4.1
Source:	Apple
Title:	Report of [Post129bis][210][LPWUS] Running CR for TS 38.321 (Apple)
WID/SID:	NR_LPWUS-Core – Release 19
Document for:	Discussion and Decision
1	

Conclusion
Based on post-meeting email discussion, Rapporteur identify the following stage 3 open issues:
Open issue 1: Whether/How to support the LP-WUS (including Option 1-1 and 1-2) and dual DRX group.
Open issue 2: In Option 1-2,  whether the UE should start the lpwus_PDCCHMonitoringTimer (as if LP-WUS was detected) when the UE is not able to monitor the LP-WUS occasion(s).

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

Agenda item:	8.4.1
Source:	Huawei/HiSilicon
Title:	Summary of [Post129bis][218][LPWUS] UE Capabilities (Huawei)
WID:	NR_LPWUS-Core
Document for:	Discussion and Decision

Conclusions
Based on the inputs from companies, the following proposals are made:
Proposal 1 (10/10): A UE indicating support of LP-WUS reception in IDLE/INACTIVE shall support UE-ID based subgrouping.
Proposal 2 (6/10): RRM measurement relaxation and RRM measurement fully offloading are defined as RAN2 capability without UE capability signalling. Send LS to RAN1 to inform the agreement.
Proposal 3: Way forward on the supported use cases regarding UE supporting LP-WUS reception, and RRM measurement relaxation and fully offloading:
Agree to support “Case 1” (8/10 support Case 1): UE supporting LP-WUS reception shall also support RRM measurement relaxation and RRM measurement fully offloading
Discuss on supporting “Case 2” (2/10 support Case 2): UE supports LP-WUS reception, but does not support RRM measurement relaxation and RRM measurement fully offloading
Preclude “Case 3” (1/10 support Case 3): UE supports RRM measurement relaxation and RRM measurement fully offloading, but does not support LP-WUS reception

Proposal 4: Wait for further discussions in RAN1 and RAN2 for CONNECTED state LP-WUS capability.