TDoc file reading error

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

Agenda Item:	8.4.4
Source: 	NEC
Title:  	Discussion on LP-WUS in RRC_CONNECTED
Document for:	Discussion and Decision
1 

Conclusions
Proposal-1(MAC-2): for option 1-2, take option 1-1 as baseline, if all LP-WUS monitoring occasion(s) in time domain occurred in Active Time, the UE starts new timer [lpwus_PDCCHMonitoringTimer] from the beginning of the subframe indicated from lower layer. FFS other cases.
Proposal-2: for option 1-2, network can configure whether UE reports periodic CSI/L1-RSRP during the time given by the new timer [lpwus_PDCCHMonitoringTimer] when this timer is not running.
4 

3GPP TSG RAN2 Meeting #130                                                                R2-2503605
19th May – 23rd May 2025, St.Julians, Malta
                                             	
Agenda item:	8.4.4
Source:	Samsung
Title:	Procedures for LP-WUS in RRC Connected Mode
Document for:	Discussion & Decision

Conclusion
RAN2 is requested to discuss and agree to the following proposals:
Observation 1. RAN2 defines when the UE starts monitor PDCCH as follows: 
Option 1-1: If LP-WUS addressed to UE or UE's subgroup is detected and the legacy drx-onDurationTimer is started
Option 1-2: If LP-WUS addressed to UE or UE's subgroup is detected and the new timer is started. FFS on drx-onDurationTimer.
Observation 2. If the above timer for Option 1-2 is the same as drx-onDurationTimer and the LP-WUS periodicity is similar as DRX cycle, the Option 1-2 could be the same as Option 1-1

Proposal 1. When the LP-WUS enabled UE is configured with both Option 1-2 and legacy DRX, then the UE operating with LP-WUS option 1-2 is not required to monitor the PDCCH during the legacy DRX active time.
Proposal 2. RAN2 confirms that the LP-WUS monitoring in RRC Connected mode can be enabled/disabled using RRC signalling. 
Proposal 3. RAN2 needs to discuss whether the LP-WUS monitoring in RRC Connected mode can be enabled/disabled using MAC signalling. 

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

Conclusion
In this contribution, we discuss the remaining issues on LP-WUS triggers PDCCH monitoring in RRC_CONNECTED. Based on the discussion, we have the following observations and proposals.
Observation 1: Data requirements may be different between primary DRX group and secondary DRX group. 
Observation 2: For Option 1-2, within legacy drx-onDurationTimer duration and the MAC entity is not in Active Time, it is up to network configuration to determine whether to report the periodic CSI/L1-RSRP, i.e. same as in Rel-16 DCP.
LP-WUS operation for UE configured with dual DRX(RRC-3) 
Proposal 1: (RRC-3) For both Option 1-1 and Option 1-2, LP-WUS could co-exist with dual DRX. 
LP-WUS can be configured on PCell for primary DRX group and/or an activated SCell for secondary DRX group.
LP-WUS indication for PDCCH monitoring is applicable to all serving cells in the DRX group where LP-WUS is monitored.
Proposal 2: (RRC-3) lpwus-PDCCHMonitoringTimer is configured per DRX group.
Empty UAI on offset for option 1-1 and option 1- (RRC-5)
Proposal 3: (RRC-5) It is allowed to report an empty UAI on time offset for LP-WUS monitoring for both option 1-1 and option 1-2, which means UE has no preference on the time offset between LP-WUS and PDCCH monitoring.
Enable and disable for LP-WUS monitoring
Proposal 4: In RRC_CONNECTED mode, PDCCH monitoring triggered by LP-WUS is enabled/disabled by the corresponding configuration of LP-WUS. No additional assistance information from UE is needed.  
Activation and deactivation procedure for LP-WUS monitoring
Proposal 5: RAN2 assumes UE could monitor LP-WUS upon LP-WUS is configured, no additional indication/condition is needed for activation/deactivation of LP-WUS functionality. The final decision is up to RAN1.
CSI report behaviour within the Active time triggered by LP-WUS
Proposal 6: For LP-WUS Option 1-2, during the timer triggered by LP-WUS is running, periodic CSI/L1-RSRP report and SP CSI report behaviour are the same as legacy drx-onDurationTimer duration without DCP configuration, i.e. always report.
LP-WUS Option3
Proposal 7: RAN2 won’t discuss Option 1-3 unless RAN1 triggers.

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

Source:	CATT
Title:	Analysis on LP-WUS for RRC_CONNECTED
Agenda Item:	8.4.4
Document for:	Discussion and Decision

Conclusion
In this document, we analyze the remaining issues in RRC_CONNECTED for LP-WUS, and the following and proposals are provided:
Dual DRX group
Proposal 1A: (RRC-3/MAC-1) For Rel-19 LP-WUS, the dual DRX group and LP-WUS can be configured simultaneously for Option 1-1.
Proposal 1B: (RRC-3/MAC-1) For Rel-19 LP-WUS, the dual DRX group and LP-WUS can be configured simultaneously for for Option 1-2.
Observation 1: Regarding basic capalility in Alt1 in Option 1-1, it is simple with less resource consumption but less flexible.
Observation 2: Advanced capability in Alt1 shows the following properties:
It is friendly to the control flexibility;
It brings extra resource consumption on LP-WUS;
The power saving gain brought by LP-WUS is questionable;
There are some issues on activation/deactivation for the SCell configured LP-WUS, e.g., whether the SCell configured with LP-WUS can be deactivated and if the SCell configured with LP-WUS is allowed to be deactivated, what is the UE behavior.
Observation 3: Alt2 shows more flexiblity on configuration but less power saving gain especially when the UE only supports LP-WUS for primary DRX group or secondary DRX group.
Proposal 2: (RRC-3/MAC-1) For Option 1-1, support basic capability of Alt1, i.e., LP-WUS can be configured only on PCell and LP-WUS indication is applicable to all serving cells of all DRX groups when dual DRX group is configured simultaneously with LP-WUS.
Proposal 3: (RRC-3/MAC-1) For Option 1-2, support LP-WUS can be configured only on PCell and LP-WUS indication is applicable to all serving cells of all DRX groups when dual DRX group is configured simultaneously with LP-WUS.
Proposal 4: For Option 1-2, lpwus_PDCCHMonitoringTimer can be configured per DRX group when dual DRX group is configured simultaneously with LP-WUS.
Proposal 5: For Option 1-2, lpwus_PDCCHMonitoringTimer can be maintained per DRX group when dual DRX group is configured simultaneously with LP-WUS.
UE behavior for the case of potential collision of LP-WUS
Proposal 6: For Basic capability of Alt1 in Option 1-1, the UE starts the drx-onDurationTimer of both primary DRX group and the secondary DRX group, when LP-WUS configured on PCell can’t be monitored.
Proposal 7: In Option 1-2, RAN2 waits RAN1 to decide what is the UE behavior with/without dual DRX group configuration, when the UE is not able to monitor the LP-WUS occasion(s).

LP-WUS enable/disable and activation/deactivation
Proposal 8: UE assistance is not needed to enable/disable PDCCH monitoring triggered by LP-WUS.
Proposal 9: LP-WUS activation, deactivation, or fallback to PDCCH monitoring is not supported in Rel-19.

3GPP TSG-RAN WG2 Meeting #130										R2-2503764
St Julian, Malta, 19th – 23rd May, 2025							Revision of R2-2501961
Agenda item:		8.4.4
Title: 	Procedures for LP-WUS in RRC_CONNECTED
Source: 			ZTE Corporation, Sanechips
Document for: 	Discussion and Decision

Conclusion
Proposal 1: LP-WUS for RRC_CONNECTED is activated or deactivated by MAC CEl.
Proposal 1a: Network configures LP-WUS monitoring entry and exit condition (e.g. configure RSRP and optional RSRQ threshold by RRCReconfiguration message) to UE in RRC_CONNECTED state.
Proposal 1b: UE reports LP-WUS activation/deactivation assistance information to network, e.g. by UEAssistanceInformation message.
Observation 1: In the current MAC specification, the drx-onDurationTimer is started per DRX group, and DRX Active Time is maintained per DRX group. It is feasible technically to configure LP-WUS with secondary DRX group simultaneously for option 1-1.
Proposal 2: The LP-WUS can be configured with secondary DRX group simultaneously for option 1-1.
Proposal 3: The LP-WUS can be configured with secondary DRX group simultaneously for option 1-2.
Proposal 4: When LP-WUS is configured with secondary DRX Group simultaneously, one LP-WUS subgroup can only be configured for one DRX group, i.e. one LP-WUS subgroup is configured with one DRX group while another LP-WUS subgroup is configured for the other DRX group, so that the LP-WUS will only activate one DRX group.
Proposal 5: For UE in RRC_CONNECTED state, if LP-WUS is monitored but not detected, the legacy drx-onDurationTimer is not started for option 1-1 and the newly defined timer (e.g. lpwus_PDCCHMonitoringTimer) is not started for option 1-2.
Proposal 6: For Option 1-2, RAN2 confirms that one single LP-WUS cycle is defined to determine the LP-WUS monitoring occasion.
Proposal 6a: For Option 1-2, RAN2 confirms that small granularity of LP-WUS cycle (e.g. ms) is defined to match the non-integer traffic periodicity, and no non-integer LP-WUS cycle is defined.
Proposal 7: For option1-2, when LP-WUS is configured with secondary DRX Group simultaneously, one LP-WUS monitoring configuration (LP-WUS cycle, timeOffset) is configured per cell group, LP-WUS subgroup number and lpwus_PDCCHMonitoringTimer is configured per DRX group.
Proposal 8: For Option 1-2, RAN2 confirms that drx-startOffset - timeOffset is used as the LP-WUS startOffset to determine the LP-WUS monitoring occasion. Wherein the timeOffset is the time GAP between the LP-WUS reception and the start of newly defined timer (e.g. the new timer triggered by LPWUS).
Proposal 9: For Option 1-2, The LP-WUS monitoring occasion can be determined using the similar formula as that to determine the start of drx-onDurationTimer, e.g. For UE in RRC_CONNECTED state, if LP-WUS is activated, the UE monitors LP-WUS if:
[(SFN × 10) + subframe number-(drx-StartOffset - timeOffset)] modulo (LP-WUS-cycle)) = 0.
Observation 1: Option 1-3 can also reduce UE power consumption, meanwhile keep small data transmission latency, but the UE performance and the PDCCH monitoring delay caused for LP-WUS monitoring should be evaluated by RAN1.

TDoc file reading error

3GPP TSG-RAN2#130 	R2-2503819
St. Julian’s, Malta, 19th May – 23th May, 2025	
	

Agenda item:		8.4.4 (NR_LPWUS-Core)
Source:	LG Electronics Inc.
Title: 	Remainng issues on LP-WUS in RRC_CONNECTED
Document for:	Discussion and Decision
1.	

Conclusion
In this document, we discuss issues on LP-WUS in RRC_CONNECTED, and make proposals as follows.
Proposal 1. RAN2 supports to enable dual DRX groups and LP-WUS simultaneously. 
Proposal 2. When dual DRX groups and LP-WUS are enabled simultaneously, LP-WUS is monitored in PCell of the primary DRX group.
Proposal 3. If LP-WUS occasion is not overlapped with Active time of any DRX group, 
the UE monitors LP-WUS on LP-WUS occasion 
the UE starts drx-onDurationTimer and lpwus_PDCCHMonitoringTimer for both DRX groups based on LP-WUS
Proposal 4. If LP-WUS is monitored in default DRX group and LP-WUS occasion is overlapped with Active time of default DRX group, 
the UE does not monitor LP-WUS occasion
the UE starts drx-onDurationTimer for both DRX groups as if LP-WUS is detected. FFS for lpwus_PDCCHMonitoringTimer.
Proposal 5. For the case where LP-WUS is monitored in default DRX group and LP-WUS occasion is not overlapped with Active time of default DRX group but overlapped with Active time of secondary DRX group, RAN2 would discuss later based on RAN1 response.
Proposal 6. If LP-WUS is monitored in default DRX group and LP-WUS occasion is overlapped with Active time of both DRX groups, 
the UE does not monitor LP-WUS occasion
the UE starts drx-onDurationTimer for both DRX groups as if LP-WUS is detected. FFS for lpwus_PDCCHMonitoringTimer.
Proposal 7. LP-WUS functionality is enabled/disabled by RRC signaling only.
Proposal 8. No additional method to activate/deactivate LP-WUS functionality and no UE assistance information are needed.
Proposal 9. LP-WUS is not impacted to SPS/CG operation.

4.	

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


Agenda item:	8.4.4
Source:	InterDigital
Title:	LP-WUS in CONNECTED mode
WID/SID:	NR_LPWUS-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion
This document has made the following observations and proposals:
Proposal 1: The UE capability signaling on minimum time gap between LP-WUS reception and MR to start PDCCH monitoring per SCS indicates support for LP-WUS in RRC_CONNECTED.  
Proposal 2: As a baseline, support the same entry/exit condition criteria based on serving cell quality to activate/deactivate LP-WUS monitoring in RRC_CONNECTED mode as agreed for RRC_IDLE/INACTIVE mode.
Proposal 3: UE can be configured with a threshold number of LP-WUS receptions for determining LP-WUS in coverage (e.g., successful reception) and out-of-coverage (e.g., reception failure).
Proposal 4: Support a timer as additional condition to activate/deactivate LP-WUS monitoring.
Proposal 5: UE reports the events of autonomous deactivation of LP-WUS monitoring to the gNB.
Proposal 6: When two DRX groups are configured with LP-WUS, UE starts the drx-onDurationTimer (Option 1-1) or the new timer (Option 1-2) for both of the DRX groups upon LP-WUS indication.
Proposal 7: Support a configuration where the LP-WUS is configured on the PCell/PSCell of the MCG/SCG when two DRX groups are configured with LP-WUS.

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

Conclusion
Proposal 1: Support LP-WUS monitoring when dual DRX groups are configured
Proposal 2: LP-WUS monitoring is configured only in PCell/PSCell and upon receiving LP-WUS, the corresponding DRX timer (legacy onDurationTimer option 1-1and timer related to option 1-2) is started in cells associated to both the DRX groups
Proposal 3: LP-WUS feature is enabled implicit at UE if it receives LP-WUS configuration via RRC. Proposal 4: LP-WUS feature is disabled at UE by network when the LP-WUS configuration is released with a RRC signaling.  
Proposal 5: A new indication is configured by network to indicate the UE to start drx-ondurationTimer when UE does not detect a LP-WUS or LR is not able to monitor the LP-WUS monitoring occasion.
Proposal 5: A new indication is configured by network to indicate the UE to start drx-ondurationTimer (option 1-1) or lpwus_PDCCHMonitoringTimer (option 1-2) when UE does not detect a LP-WUS or LR is not able to monitor the LP-WUS monitoring occasion.  

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

Agenda item:	8.4.4
Source:	Huawei, HiSilicon
Title:	Further discussion on LP-WUS for RRC_CONNECTED mode
Document for:	Discussion and Decision

Conclusion
In this paper, we discuss higher layer design for CONNECTED mode, and have the following proposals.
Configuration for LP-WUS
Proposal 1: UE can send assistance information to the network indicating to disable the LP-WUS functionality or whether the LP-WUS can be enabled again.
Proposal 2: When to send the assistance information is up to UE implementation, without additional configuration to the UE.
Proposal 3: The UE considers the LP-WUS is enabled and starts to use the LP-WUS functionality after receiving LP-WUS configuration by RRC signaling. Separate activation/deactivation signaling is not supported.
Proposal 4: RAN2 to further discuss the following alternatives:
Alt1: UE starts LP-WUS monitoring immediately after it receives the LP-WUS configuration, alignment of the starting point for LP-WUS monitoring needs to be further studied;
Alt2: UE stays in MR (C-DRX Active Time) after it receives the LP-WUS configuration, UE goes back to LP-WUS monitoring after C-DRX Active Time ends according to the agreed UE’s behavior.
UE behavior in case of LP-WUS not detected
Proposal 5: (MAC-2) For Option 1-2, when the UE is not able to monitor the LP-WUS occasion(s), the UE starts the new timer (similar to DCP).
Proposal 6: If the LP-WUS is monitored but not detected for a configured LP-WUS occasion, UE does not start the drx-OnDurationTimer (for Option 1-1) or the new timer (for Option 1-2).
LP-WUS with DC/CA
Proposal 7: (MAC-1, RRC-3) For both Option 1-1 and Option 1-2, LP-WUS can be configured in PCell with secondary DRX at the same time, and LP-WUS indication is applicable to all serving cells in both DRX groups of the cell-group, without separate control for different DRX groups.
Coexistence with other features
Proposal 8: Legacy DCP and Option 1-2 are not configured simultaneously for the same UE.
Proposal 9: DL SPS is not impacted by LP-WUS, i.e. UE still needs to wake up MR for reception on DL SPS resources.
Proposal 10: For UL configured resources, RAN2 to discuss whether UE can skip UL configured resource if the UE is operating with LP-WUR and does not have the UL data for transmission.

TDoc file reading error

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

	
Agenda Item:	8.4.4 Procedures for LP-WUS in RRC_CONNECTED
Source: 	Ericsson
Title:  	LP-WUS in Connected
Document for:	Discussion and Decision

Conclusion
There is no consensus in RAN1 on whether to introduce any enhancements of PDCCH skipping indication for the interaction with LP-WUS in RRC connected mode in Rel-19.

Agreement
For RRC CONNECTED mode when LP-WUS is configured with Cell DTX, during Cell DTX inactive time, the UE is not expected to monitor LP-WUS both for Option 1-1 and 1-2

R1-2503102	FL summary #4 on LP-WUS operation in CONNECTED mode	Moderator (NTT DOCOMO)

Agreement
The case where a UE does NOT supports Rel-17 unified TCI framework but supports LP-WUS is supported in Rel-19. For the TCI state of LP-WUS in RRC CONNECTED mode, select one of the following in RAN1#121 for this case:
Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS
Alt2: RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them
The case where a UE supports Rel-17 unified TCI framework and supports LP-WUS is supported in Rel-19. For the TCI state of LP-WUS in RRC CONNECTED mode,
When Rel-17 unified TCI framework is configured, LP-WUS follows the activated/indicated TCI-state by MAC-CE/DCI, same as other DL channels/signals (no change to DCI format)
When Rel-17 unified TCI framework is NOT configured, select one of the following in RAN1#121 for this case
Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS
Alt2: RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them
Same alternative to be chosen for both cases.

R1-2503120	FL summary #5 on LP-WUS operation in CONNECTED mode	Moderator (NTT DOCOMO)

Agreement
Update previous agreement in red:
Agreement
For LP-WUS monitoring in RRC CONNECTED mode, SSB and/or CSI-RS can be the QCL source of LP-WUS QCL type(s) is {Type A or Type C – for down-selection} and Type D, when applicable

RAN2 agreements (selection)
On short DRX cycle
For Option 1-1, the UE does not monitor LP-WUS when Short DRX cycle is used.
Working assumption: For option 1-2, it is up to network configuring short DRX cycle with LP-WUS. The UE monitors LP-WUS outside the Active Time regardless of if Short DRX cycle or Long DRX cycle is used.
Send an LS to RAN1 to inform the above conclusions, can revisit if needed based on RAN1 feedback. 

Other aspects related to the procedure (e.g., collision handling, UAI, etc.)
Working assumption for the case of potential collision (if any): In Option 1-1, when the UE is not able to monitor the LP-WUS occasion(s) the UE should start the drx-OnDurationTimer (as if LP-WUS was detected). FFS for Option 1-2.
Send LS to inform this working assumption, can also ask a) what are the cases when UE cannot monitor LP-WUS, b) whether UE can monitor LR and MR simultaneously.
If configured, the UE can signal a preferred time offset via UAI signalling.
Ask RAN1 for further information regarding their conclusions. 

Dual DRX group
FFS whether/how to support LP-WUS (including Option 1-1 and 1-2) and dual DRX group

MRDC
For NR-DC, the LP-WUS can be configured to be monitored at least on the PCell and PSCell. Wait for RAN1 progress on whether to allow LP-WUS configuration and monitoring on other Cells.
For NR-DC, the LP-WUS in MCG and SCG can be configured independently.
Apart from NR-DC, LP-WUS can also be supported in NE-DC, EN-DC, NGEN-DC. And proposal 1 and 2 also apply to NE-DC, EN-DC, NGEN-DC.

[Post129bis][203][LPWUS] LS to R1 LP-WUS in RRC_CONNECTED (InterDigital)
Agreed LS in R2-2503187

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

	
Agenda Item:	8.4.4 Procedures for LP-WUS in RRC_CONNECTED
Source: 	Ericsson, Huawei, HiSilicon, NEC, LGE, Apple, InterDigital, OPPO, CATT
Title:  	LP-WUS and secondary DRX
Document for:	Discussion and Decision

Conclusion
For the case when UE is configured with CA with dual DRX groups in RRC CONNECTED mode, at least for LP-WUS procedure Option 1-1, there is no consensus in RAN1 which of the following options to support for this case in Rel-19.
Alt1
Basic capability
LP-WUS can be configured only on PCell
LP-WUS indication is applicable to all serving cells of all DRX groups.
Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation
Advanced capability
LP-WUS can be configured on PCell for primary DRX group and an activated SCell for secondary DRX group
LP-WUS indication is applicable to all serving cells in the DRX group where LP-WUS is monitored
Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation
This capability has prerequisite of the above basic capability
Alt2
LP-WUS can be configured on PCell for primary DRX group and/or an activated SCell for secondary DRX group
LP-WUS indication is applicable to all serving cells in the DRX group where LP-WUS is monitored
Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation
This capability has candidate values for the LP-WUS configuration with {primary DRX group, secondary DRX, both}

3GPP TSG-RAN WG2 Meeting #130	R2-2504385
St.Julians, Malta,  May 19th – 23rd , 2025
Agenda item:	8.4.4
Source:	CMCC
Title:	Discussion on LP-WUS operation in CONNECTED mode
Document for:	Discussion, Decision

Conclusions
In this contribution, we discuss the LP-WUS operation in RRC_CONNECTED mode, and following are the proposals and observations:
Proposals:
Proposal 1: RAN2 confirms the working assumption that “for option 1-2, it is up to network configuring short DRX cycle with LP-WUS. The UE monitors LP-WUS outside the Active Time regardless of if Short DRX cycle or Long DRX cycle is used” to progress the LP-WUS discussion.
Proposal 2: LP-WUS with dual DRX groups is not supported in Rel-19.
Proposal 3: For NR-DC (without dual DRX group), the LP-WUS can only be configured to be monitored on the PCell and PSCell:
For the case when UE is configured with CA without dual DRX groups in RRC CONNECTED mode, LP-WUS can be configured only on PCell
For the case when UE is configured with NR-DC with CA without dual DRX groups or without CA in RRC CONNECTED mode, LP-WUS can be configured only on PCell/PSCell per cell-group
Proposal 4: UE only monitors the Option 1-3 LP-WUS indication within the legacy drx-onDurationTimer duration.
Proposal 5: If Option 1-3 is supported, it can be configured together with Option 1-1 or Option 1-2.
Proposal 6: RAN2 confirms RAN1’s working assumption that Option 1-3 is deprioritized for RRC_CONNECTED UE.
Proposal 7: RRC signalling based approach is used to enable LP-WUS monitoring in RRC_CONNECTED.
Proposal 8: Once the UE receives LP-WUS monitoring configuration, it start LP-WUS monitoring based on the configuration. 
Proposal 9: No additional indication/condition are introduced for activation/deactivation of LP-WUS monitoring. LP-WUS monitoring is only enabled(activated) or disable(deactivated) by RRC signalling.
Proposal 10: UE assistance information can be introduced to assist gNB to enable/disable the LP-WUS monitoring. 
Proposal 11: There’s no need to configure or activate DCP and any LP-WUS options for RRC_CONNECTED PDCCH monitoring simultaneously.
Observations:
Observation 1: For Option 1-2, UE’s PDCCH monitoring has no relationship with DRX cycle, regardless it’s Short DRX cycle or Long DRX cycle.
Observation 2: For Option 1-2, DRX is mainly related to UE’s periodic CSI/L1-RSRP reporting.

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

Agenda Item:	8.4.4
Source:	HONOR
Title:	Discussion on LP-WUS in RRC_CONNECTED
Document for:	Discussion and Decision
1. 

Conclusions
In this contribution, we discussed fallback mechanism of LP-WUS monitoring. The proposal is summarised as below.
Proposal 1: (MAC-2) For Option 1-2, UE should fall back to the legacy CDRX monitoring mechanism if it does not receive any LP-WUS targeted to itself within N LP-WUS cycles.
4. 

3GPP TSG-RAN WG2 Meeting #130	R2- 2504514
Saint Julian’s, Malta, 19 – 23 May 2025		

Agenda item:	8.4.4
Source:	Nokia, Nokia Shanghai Bell
Title:	LP-WUS in RRC_CONNECTED
WID/SID:	NR_LPWUS-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion
We discussed the secondary DRX group aspect and untouched issues for uplink, and proposed the followings:
Proposal 1: LP-WUS can be configured with secondary DRX group.
Proposal 2: When a secondary DRX group configured, the LP-WUS is configured only on the PCell.
Proposal 3: With a secondary DRX group, the UE starts PDCCH monitoring in both primary and secondary DRX group upon receiving LP-WUS on the PCell.
Proposal 4: With a secondary DRX group, the UE starts LP-WUS monitoring when active time ends in both primary and secondary DRX groups. 
Proposal 5: With secondary DRX group, lpwus-PDCCHMonitoringTimer can be separately configured for the secondary DRX group. 
Observation 1: If the UE monitors LP-WUS instead of PDCCH while SR is pending, reception of LP-WUS would need to be considered as a response to SR. 
Observation 2: Monitoring both LP-WUS and PDCCH simultaneously while SR is pending would need to be confirmed by RAN1.
Proposal 6: RAN2 confirms that the UE stops LP-WUS monitoring when SR is pending.
Proposal 7: In option 1-2, when the UE starts LP-WUS monitoring, SPS and CG are kept as it is unless activated or deactivated by the network explicitly.

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

Conclusion
LP-WUS in DC/CA
Observation 1: If one single LP-WUS monitoring is applied for both DRX groups, it is power waste for the UE to wake up the MR on the DRX group in which there is no DL scheduling.
Observation 2: If separate LP-WUS monitoring is applied for each DRX group, UE only needs to wake up MR on the DRX group in which there is DL scheduling.
For a UE configured with CA with dual-DRX groups, support LP-WUS monitoring on a serving cell per DRX group. The LP-WUS configurations are independent for each DRX group. LP-WUS monitored on a cell within a DRX group triggers PDCCH monitoring on the cells of the DRX group.
Support maintenance of lpwus_PDCCHMonitoringTimer is per DRX group.
Introduce UE capability to support separate LP-WUS monitoring on a serving cell per each DRX group.
Switching between LP-WUS and legacy PDCCH monitoring 
Observation 3: When UE is using LP-WUS option 1-1 and fallback to MR PDCCH monitoring with/without DCP configured, it is beneficial that UE reports to the gNB so that gNB can stop sending LP-WUS indication and enable DCP functionality if configured.
Observation 4: When UE is using LP-WUS option 1-2 and fallback to MR PDCCH monitoring with/without DCP configured, it is beneficial that UE reports to the gNB so that gNB and the UE can be aligned on PDCCH monitoring to avoid potential PDCCH missing.
Observation 5: When UE is using legacy PDCCH monitoring and enters LP-WUS, it is beneficial that UE reports to the gNB so that gNB and the UE can be aligned on LP-WUS enable to avoid potential PDCCH missing.
For both of Option 1-1 and Option 1-2, UE needs to indicate to the gNB when the UE enters or leave LP-WUS mode.
For option 1-1, the UE switches from LP-WUS mode to legacy PDCCH monitoring, RAN2 discusses whether gNB needs to send a switching command to UE.
For option 1-2, gNB needs to send a switching command to UE in order for UE switching from LP-WUS mode to legacy PDCCH monitoring with/without DCP.
LP-WUS activation/deactivation 
gNB can configure multiple LP-WUS configurations to the UE and activate one of the configurations to the UE via MAC CE.
Paging monitoring
It is up to UE implementation to monitor paging using legacy paging or LP-WUS monitoring if the UE is in CONNECTED state.

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

Agenda item:		8.4.4
Source:		Lenovo
Title:		 LP-WUS in RRC Connected Mode
Document for:		Discussion and Decision

Conclusion
Proposal 1: (MAC-2) RAN2 to confirm when the UE is not able to monitor the LP-WUS occasion(s) the UE should start the drx-OnDurationTimer for Option 1-1, and same principle can be applied to option 1-2. FFS whether such behaviour is RRC configurable.
Proposal 2: (MAC-1) RAN2 to wait for RAN1’s conclusion on whether to support LP-WUS and dual DRX group simultaneously.
Proposal 3: (MAC-1) If RAN1 confirms that LP-WUS can be configured with dual DRX group simultaneously, a single LP-WUS is configured on the PCell of the default DRX group. FFS if the LP-WUS wakes up all cells of the default DRX group only, or if the LP-WUS wakes up all cells across both DRX groups.
Proposal 4: (MAC-1) If RAN1 confirms that LP-WUS can be configured with dual DRX group simultaneously and both DRX groups can be woken up by a single LP-WUS configuration, the default DRX group and secondary DRX groups are both configured with the same LP-WUS DRX Option (i.e., either Option 1-1 or Option 1-2).
Proposal 5: (MAC-1) If LP-WUS Option 1-2 can be configured with dual DRX group simultaneously and both DRX groups can be woken up by a single LP-WUS configuration, the secondary DRX group is configured with a shorter lpwus_PDCCHMonitoringTimer and the DRX Cycle start and length remain the same for both DRX groups. 
Proposal 6: In the case of LP-WUS monitoring is enabled in RRC_CONNECTED mode, UE behaviours on the configured SPS/CG resources are not impacted.
Observation 1: Frequent wake-up of MR caused by UL transmission can lead to a reduction in the power saving gain offered by LP-WUR configuration. 
Proposal 7: RAN2 to discuss means of improving MR sleep time, e.g., by delaying (non-urgent) UL transmissions.
This document discusses some procedures for a LR capable UE in the RRC Connected Mode. Following are the proposals and observations made in this document: