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

Agenda Item:	9.6.3
Source:	Huawei, HiSilicon
Title:	Procedures and functionalities of LP-WUS in CONNECTED mode
Document for:	Discussion and Decision

Conclusions
In this contribution, the procedures and functionalities of LP-WUS in CONNECTED mode are discussed. Based on the analysis, the following observations and proposals are provided:
The impact due to miss-detection/falsely-detection of LP-WUS activation/deactivation signaling should be minimized/avoided for CONNECTED mode UEs.
The following is adopted for a UE that reports the baseline capability of FG 62-2/2a:
LP-WUR is NOT able to receive signal(s) during the time where MR transmits/receives signals/channels.
If LP-WUS monitoring collides with measurements and/or periodic CSI/L1-RSRP transmission, measurements are prioritized.
If LP-WUS monitoring collides with SPS/CG resources, SPS/CG reception/transmission is prioritized.
LP-WUS monitoring collides with interruption caused by RAR window monitoring for BFR, PDCCH monitoring within RAR window monitoring for BFR is prioritized.
FFS how to let gNB and UE have the common understanding on where the UE performs measurement.
Additional UE capability of simultaneous operation between LP-WUR and MR can be considered in UE feature discussion.
For the X = 3 candidate values for the UE capability report on the minimum time gap for each SCS, adopt {V1=3, V2=20, V3=42}ms:
Same values are used for OOK-based WUR and OFDM-based WUR;
Candidate values for UAI are same as candidate values for UE capability.
UE does not expect gNB to configure a time offset that is shorter than the duration reported from the three candidate values:
The value indicated by UAI is not smaller than the duration reported in the UE capability reporting;
If a LP-WUS triggering a PDCCH monitoring received by the UE ends at symbol n, the UE is not expected to monitor a PDCCH before symbol n+Y where Y is the configured time offset. 
In CONNECTED mode, support UE fallback to legacy C-DRX PDCCH monitoring when UE monitors LP-WUS based on timer for both Option 1-1 and Option 1-2 to let gNB always know the working state of UE.
UE report an explicit feedback signaling to gNB after the wake-up from LP-WUS monitoring.
SR resource is used for the feedback signaling to gNB.
The basic capability for the maximum number of codepoints checked per MO by a UE is 2.
If UE is configured with LP-WUS and Rel-17 SSSG switching simultaneously, after LP-WUS monitoring is activated, the UE should stop/suspend the Rel-17 SSSG switching related timers.
Adopt the Alt1 in RAN1#120bis agreement, i.e. RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS in case of the following two cases:
The case where UE supports LP-WUS but not supports Rel-17 unified TCI framework;
The case where UE supports both LP-WUS and Rel-17 unified TCI framework but Rel-17 unified TCI framework is NOT configured.
Capture the parameter in appendix in the RRC parameter list.
In CONNECTED mode, monitoring parameters of LP-WUS can be adjusted by MR signaling and/or pre-defined rules at least for different coverage requirement.

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

Source: 	ZTE Corporation, Sanechips
Title:	Discussion on LP-WUS operation in CONNECTED mode
Agenda item: 	9.6.3
Document for:	Discussion and decision

Conclusions 
In this contribution, we have discussed issues on LP-WUS operation in CONNECTED mode. We make the following observations and proposals:
Observations:
Observation 1: Monitoring DCI for LP-WUS activation, compared with RRC activation, causes more power consumption.

Proposals:
Proposal 1: RRC activation/deactivation is the baseline
DCI deactivation and fallback mechanism based on the condition that UE does not received LP-WUS for a long time can be considered.
The motivation for L2 activation/deactivation should be further clarified if L1 deactivation is introduced.
Option 4 is not considered for activation/deactivation of LP-WUS monitoring.

Proposal 2: If the UE does not receive LP-WUS for a long time which is configurable,, the UE would return to C-DRX PDCCH monitoring
new active time is overlapping with legacy active time for option 1-2
if the UE does not receive PDCCH scheduling after fallback, the UE keep monitoring PDCCH
if the UE receives PDCCH scheduling after fallback, the UE can go back to LP-WUS monitoring according to the configuration

Proposal 3:For both option 1-1 and option 1-2
the same periodicity configuration is shared.
the same configuration is shared for offset 1 and offset 3
the same number of MOs configuration is shared 

Proposal 4: Outside new or legacy active time, reusing legacy mechanism as DCP for Searchspace monitoring.
Proposal 5: The LP-WUS is used to indicate wake-up for PDCCH monitoring
Target all the configured searchspaces in the active DL BWP
Proposal 6: Alt 2 is selected for both cases.
Proposal 7: When Rel-17 unified TCI framework is configured, LP-WUS follows the activated/indicated TCI-state by DCI, same as PDSCH (no change to DCI format)
Proposal 8: The candidate value is defined based on different WUR type

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

Source:	vivo
Title:	Remaining issues on LP-WUS operation in CONNECTED modes 
Agenda Item:	9.6.3
Document for:	Discussion and Decision

Conclusions
In this contribution, we provide our views on LP-WUS operation for UEs in RRC CONNECTED modes. The proposals are summarized as follows.
Proposal 1: 
LP-WUR and MR cannot work simultaneously should be UE basic capability.
LP-WUR and MR can work simultaneously can be optionally supported based on UE capability. 
FFS how fast the switching can be done between the MR and LR.
Proposal 2: The understanding on “UE is not able to monitor LP-WUS” in RAN2’s LS is because MR is active and UE does not support LP-WUR and MR work simultaneously. Based on this understanding, RAN1 agree the cases/scenarios listed in RAN2’s LS with adding one more case as following:
Such cases/scenarios resulting UE is not able to monitor LP-WUS include collision with Active Time, measurement gap, interruption caused by BWP switching, and RAR window monitoring for BFR, PDCCH monitoring associated with PDCCH CSS sets except for a Type3-PDCCH CSS set. 
Proposal 3: A UE does not start the drx-OnDurationTimer for LP-WUS connected mode operation Option 1-1 or LPWUS_PDCCHMonitoringTimer for LP-WUS connected mode operation Option 1-2 when the LP-WUS monitoring occasion(s) collide with DTX inactive period for the primary cell. 
Proposal 4: For LP-WUS connected mode Option 1-2, for the cases/scenarios on when the UE is not able to monitor the LP-WUS occasion(s), the UE does not start the LP-WUS_PDCCHMonitoringTimer . 
Proposal 5: The preferred time offset indicated via UAI value(s) should be equal to or longer than the minimum time gap reported by UE capability.
Proposal 6: Adopt the following update for TS 38.214: 

Proposal 7: 
Support V1=[3+TWUS-processing-time]ms, V2=[10+TWUS-processing-time]ms and V3=[30+TWUS-processing-time]ms, where TWUS-processing-time is the LP-WUS processsing time, as candidate values for the minimum time gap reported by the UE capability.
LP-WUS processsing time, i.e., TWUS-processing-time is less than 3ms, up to 1ms can be the considered.  
The same set of values is applied for different receiver types. 
Proposal 8: When LP-WUS monitoring is enabled for RRC CONNECTED mode, UE by implementation can fallback to PDCCH monitoring when UE monitors LP-WUS without any specification work. 
No need to specify any condition for the fallback
No need to have indication from UE when it falls back to PDCCH monitoring.  
For LP-WUS operation option 1-1, the fallback behavior for PDCCH monitoring can be according to the C-DRX configuration
For LP-WUS operation option 1-2, the fallback behavior for PDCCH monitoring can be always-on PDCCH monitoring. 

Proposal 9: Use Table 1 as starting point to discuss the Type of per BWP or per cell group configuration for WUS parameters used for connected mode operation.
Table 1 Views on the Type (per BWP or per cell group) for WUS Parameters in connected mode 

Proposal 10: For LP-WUS MOs in connected mode for Option 1-1, 
The LP-WUS periodicityMO-Option 1-1 and offsetMO-Option 1-1 provide the periodicity and offset of the LP-WUS MO, following candidate values can be considered:
sl1, NULL,
sl2, INTEGER {0..1},
sl4, INTEGER {0..3},
sl5, INTEGER {0..4},
sl8 INTEGER {0..7}
sl10, INTEGER {0..9}
sl16, INTEGER {0..15}
sl20, INTEGER {0..19}
sl40, INTEGER {0..39}
sl80, INTEGER {0..79}
sl160, INTEGER {0..159}
sl320, INTEGER {0..319}
sl640, INTEGER {0..639}
sl1280, INTEGER {0..1279}
sl2560, INTEGER {0..2559}
timeOffsetCONNECTEDOption1-1 indicates a time offset where the UE starts monitoring LP-WUS at LP-WUS MO(s), prior to a slot where the drx-onDurationTimer would start
The values for timeOffsetCONNECTEDOption1-1 is in multiples of 0.125ms (milliseconds), INTEGER (25..424). 
UE monitors the first LP-WUS MO(s) provided by numMO-Option 1-1 at or after Time offset2 (determined by timeOffsetCONNECTEDOption1-1).
The candidate values on the numMO-Option 1-1 is: INTEGER {1..4} 
Proposal 11: For LP-WUS MOs in connected mode for Option 1-2, 
The LP-WUS periodicityMO-Option 1-2 and offsetMO-Option 1-2 provide the periodicity and offset of the LP-WUS MO, following candidate values can be considered:
sl1, NULL,
sl2, INTEGER {0..1},
sl4, INTEGER {0..3},
sl5, INTEGER {0..4},
sl8 INTEGER {0..7}
sl10, INTEGER {0..9}
sl16, INTEGER {0..15}
sl20, INTEGER {0..19}
sl40, INTEGER {0..39}
sl80, INTEGER {0..79}
The candidate values for numMO-Option 1-2 is INTEGER {1..4}
The timeOffsetCONNECTEDOption1-2 indicates a time,  after which the UE starts lpwus-PDCCHMonitoringTimer with respect to the start of the first WUS monitoring occasion from the number of numMO-Option 1-2 WUS monitoring occasions per periodicity. 
The candidate values for timeOffsetCONNECTEDOption1-2 is in multiples of 0.125ms (milliseconds), INTEGER (25..424). 
The candidate values for lpwus-PDCCHMonitoringTimer can be ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60
Proposal 12: For the case where a UE does NOT support Rel-17 unified TCI framework and the case where a UE supports Rel-17 unified TCI framework but is not configured with Rel-17 unified TCI, for the TCI state of LP-WUS in RRC CONNECTED mode, select Alt2 that RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them.
For Alt.2, following new RRC parameters for configuring K TCI states for LP-WUS from the TCI states defined in pdsch-Config with tci-StatesToAddModList is needed.
tci-StatesWUS-ToAddList SEQUENCE (SIZE(1..maxNrofTCI-StatesWUS)) OF TCI-StateId  
tci-StatesWUS-ToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-StatesWUS)) OF TCI-StateId 
maxNrofTCI-StateWUS = K = 64 
Proposal 13: Adopt the TP suggested below with modification in red.

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

Agenda Item:	9.6.3
Source:	Spreadtrum, UNISOC
Title:	Discussion on LP-WUS operation in CONNECTED modes 
Document for:	Discussion and decision

Conclusion
In summary, we have following proposals:
Proposal 1: The condition of fall backing to PDCCH monitoring when UE monitors LP-WUS is not needed.
Proposal 2: The same value can be selected for OOK-based WUR and OFDM-based WUR.
Proposal 3: No matter CA case or non-CA case, the value of the minimum time gap should keep same.
Proposal 4: Candidate values for UAI should be same as candidate values for UE capability.
Proposal 5: For the case where a UE does NOT supports Rel-17 unified TCI framework but supports LP-WUS is supported in Rel-19, we prefer that RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them (i.e., Alt2).
Proposal 6: For the case where a UE supports Rel-17 unified TCI framework and supports LP-WUS is supported in Rel-19 and when Rel-17 unified TCI framework is NOT configured, we prefer that RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them (i.e., Alt2).

3GPP TSG RAN WG1 #121		R1-2503575
St Julian's, Malta, 19th – 23rd May, 2025
Agenda item:	9.6.3
Source:	Samsung
Title:	Discussion on LP-WUS operation in CONNECTED modes
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

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.

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

3GPP TSG RAN WG1#121		            					R1-2503696
St Julian's, Malta, 19th-23th May, 2025

Agenda item:		9.6.3
Title:			LP-WUS operation in CONNECTED mode
Source:		Nokia
Document for:		Discussion and Decision

1. 

PROPOSALS

Proposal 1:  	Candidate values for the minimum time gap are {V1=[3], V2=[13], V3=[33]}

Proposal 2:  	The same candidate values for the minimum time gap, are used for different WUR types.

Proposal 3:	For UEs that support the Rel-17 unified TCI framework and for UEs that do not support the Rel-17 unified TCI framework, RRC configures K TCI states for LP-WUS and a new MAC-CE for TCI activation activates one of them.

Proposal 4:	RAN1 discuss asking RAN2 to extend operation of option 1-1 operation to short-DRX.

Proposal 5:	For RRC connected mode, LP-WUS monitoring is not expected outside C-DRX active time when the MR is active.

Proposal 6:	For RRC connected mode, LP-WUS monitoring is not expected during measurement gaps.

Proposal 7:	For RRC connected mode, LP-WUS monitoring is not expected during BWP switching.

Proposal 8:	For RRC connected mode, LP-WUS monitoring is not expected during the BFR procedure.

Proposal 9:	The UE can use the UAI procedure to signal any value from the original 3 value candidate set.




4.   

3GPP TSG RAN WG1 #121			R1-2503748
Malta, MT, May 19th – 23rd, 2025
Agenda Item:	9.6.3
Source:	Panasonic
Title:	Discussion on LP-WUS operation in CONNECTED mode
Document for:	Discussion/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,
For Option 1-1, the UE is expected to monitor LP-WUS
For Option 1-2, the UE is not expected to monitor LP-WUS both for Option 1-1 and 1-2

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.

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

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

Source:	CATT
Title:	System design and procedure of LP-WUS operation for UE in CONNECTED Modes 
Agenda Item:	9.6.3
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the aspects of the timeline between LP-WUS reception/detection and PDCCH monitoring, LP-WUS monitoring occasion (LP-WUS MO), QCL/TCI-state and CA/DC with LP-WUS for RRC_CONNECTED mode and give the following proposals.
Proposal 1: The minimum time gap of LP-WUS should take into account the time of MR in preparation of channel tracking for PDCCH coherent demodulation when LP-WUS triggers UE wakeup.
Proposal 2: For RRC CONNECTED mode, support V2=20ms.
Proposal 3: For LP-WUS MO in for UE in CONNECTED mode, the periodicity and offset is configured in slot-level and the first symbol for LP-WUS MO in a slot can be determined by an RRC parameter. 
The candidate value of periodicity and time offset1 can be same as that of monitoringSlotPeriodicityAndOffset.
Proposal 4: It should be supported that 20ms is one of the candidate values of offset2 for Option1-1. 
Proposal 5: The candidate values for periodicity, time offset3, time offset4 and the reference time for the time offset3 of Option1-2 are similar to periodicity, time offset1, time offset2 and the reference time for the time offset1 of Option1-1. 
Proposal 6: For the case where a UE supports Rel-17 unified TCI framework and Rel-17 unified TCI framework is NOT configured and the case where a UE does NOT supports Rel-17 unified TCI framework, support Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS.
One LP-WUS is configured to be QCLed with the RS associated with each of the TCI states of the CORESETs in order to trigger the PDCCH monitoring at the associated CORESETs when LP-WUS is detected. 

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

Source: 	CMCC
Title:	Discussion on LP-WUS operation in CONNECTED mode
Agenda item:	9.6.3
Document for:	Discussion & Decision

Conclusions
In this contribution, we discussed the LP-WUS operation in RRC_CONNECTED mode, and the following observation and proposals are made.
Proposal 1. For the candidate values of minimum time gap, do not introduce separate values for OOK-based WUR and OFDM-based WUR.

Proposal 2. When a UE does not support/configure Rel-17 unified TCI framework, support Alt 1 (RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS).

Proposal 3. Do not support to introduce additional activation/deactivation mechanism for LP-WUS monitoring.

Proposal 4. For LP-SS MO/LO determination in CONNECTED mode, support to reuse the mechanism in AI 9.6.2 as much as possible and at least includes the followings:
Available resource determination for LP-SS/LP-WUS.
Starting time location determination for LP-SS.
Terminology definition for LP-SS/LP-WUS.

TDoc file reading error

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


Agenda item:	9.6.3
Source:	NEC
Title:              	Discussion on LP-WUS operation in RRC CONNECTED mode
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the LP-WUS operation in RRC CONNECTED mode, and the following proposals are made:
Proposal 1: support LP-WUS in combination with DCP to further reduce power consumption without introducing too much overhead. 

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

Agenda Item:	9.6.3
Source:	InterDigital, Inc.
Title:	Discussion on RRC CONNECTED Mode LP-WUS Monitoring
Document for:	Discussion

Summary
In this contribution, we discussed LP-WUS operation in RRC CONNECTED mode. Based on the discussion, we made the following observations and the proposals. 
Observation 1: LP-WUS monitoring configuration should be selected to match the conditions UE is experiencing. 
Observation 2: Higher power saving can be achieved by activating LP-WUS monitoring only when UE is in appropriate conditions. 
Observation 3: gNB is unable to select all the appropriate LP-WUS monitoring configuration and activate/deactivate LP-WUS monitoring without UE assistance. 
Observation 4: Due to limited coverage, LP-WUS is susceptible to variations in the radio channel. 
Observation 5: Based on prior agreements, LP-WUS monitoring by UE should be known to gNB. 
Observation 6: Supporting fallback from LP-WUS monitoring based on UE implementation can result in undesired UE behavior in RRC CONNECTED state.
Observation 7: Limited coverage is one of the key reasons to support a fallback behavior for LP-WUS monitoring. 
Observation 8: Time/frequency synchronization of MR is not impacted by RRC CONNTECTED mode LP-WUS monitoring. 
Observation 9: Configuration of periodic CSI/L1-RSRP reporting mechanism can be inefficient in case of long inactive durations.

Proposal 1: PDCCH monitoring triggered by LP-WUS is enabled/disabled or activated/deactivated with UE assistance. 
Proposal 2: For LP-WUS monitoring enabled UE, support activating/deactivating LP-WUS monitoring based on at least following preconfigured conditions.
For activating LP-WUS monitoring: Signal quality based on MR and LR measurements. 
For deactivating LP-WUS monitoring: Signal quality based on LP-WUR measurements.
Proposal 3:  For OFDM based LP-WUR, support activating/deactivating LP-WUS monitoring based on both NR-SS (existing SSB) and LP-SS based signal/channel quality measurements.
Proposal 4: For RRC CONNECTED mode LP-WUS monitoring, support fallback from LP-WUS monitoring based on a gNB configured timer that tracks time duration that UE does not detect LP-WUS targeting the UE.
Proposal 5: For both LP-WUS monitoring Option 1-1 and Option 1-2 in RRC CONNECTED mode, upon fallback from LP-WUS monitoring, UE follow legacy DRX behavior and indicates its decision to gNB.  
Proposal 6: For RRC CONNECTED mode LP-WUS monitoring, translation of reported minimum time gap for different SSB periodicities is not supported. 
Proposal 7: In RRC CONNECTED mode LP-WUS monitoring, for minimum time gap between LP-WUS reception to starting PDCCH monitoring, different sets of candidates are used for OOK-based WUR and OFDM-based WUR. 

Proposal 8: For RRC CONNECTED mode LP-WUS monitoring, introduce a mechanism to support CSI/L1-RSRP reporting triggered when inactivity periods exceed a preconfigured threshold. 
Proposal 9: LP-SS is supported for RRC CONNECTED mode LP-WUS monitoring. 
Proposal 10: When a UE does NOT support Rel-17 unified TCI framework, or UE supports Rel-17 unified TCI framework but NOT configured, for TCI state of LP-WUS, support Alt 2. 
Alt2: RRC configures K TCI states for LP-WUS and a new MAC-CE for TCI activation activates one of them.

3GPP TSG-RAN WG1 Meeting #121	R1-2504020
St. Julian’s, Malta, May 19th – May 23rd, 2025
Agenda Item:	9.6.3
Source:	Ericsson
Title:	LP-WUS operation in CONNECTED mode
Document for:	Discussion
1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	OOK-based LP-WUS (with ≤2 slots duration) is less reliable than PDCCH for following cases
	PDCCH 1Rx reception for PDCCH aggregation levels 8,16
	PDCCH 2Rx reception for PDCCH aggregation levels 4,8,16
	PDCCH 4Rx reception for PDCCH aggregation levels 2,4,8,16
Observation 2: For Alt2, a default UE behaviour is needed until a valid TCI state is received.
Based on the discussion in the previous sections we propose the following:
Proposal 1	Considering the need to minimize overhead and latency, LP-WUS duration used for connected mode should be limited to at most 2 slots.
Proposal 2	OOK-based LP-WUS in connected mode should only be used for triggering PDCCH monitoring for a limited set of PDCCH CCE aggregation levels. For example,
	PDCCH aggregation levels 1,2,4 for PDCCH 1Rx reception
	PDCCH aggregation levels 1,2 for PDCCH 2Rx reception
	PDCCH aggregation level 1 for PDCCH 4Rx reception
Proposal 3	UE PDCCH monitoring of at least certain configured PDCCH search space set(s) with higher ALs (e.g., used for scheduling RRC reconfiguration) should be independent of LP-WUS detection.
Proposal 4	Support {V1=3, V2=10, V3=33}ms for the candidate values of reported minimum time gap.
Proposal 5	Different candidate values can be selected for different WUR types. However, only one set of min gap values should be reported for both single carrier and multi-carrier scenarios.
Proposal 6	For LP-WUS MO configuration for option 1-1 by RRC parameters:
	For periodicity and offset1, a subset values used for Rel16 DCP (i.e. from the parameter monitoringSlotPeriodicityAndOffset corresponding to DCI 2_6) can be used.
	For number of MOs Z monitored by the UE per DRX cycle, the value range can be {1,2,3,4}
	For offset2, the value range can be agreed after agreements are made for values of possible MO durations, minimum time gap and periodicity of the MOs.
Proposal 7	For LP-WUS MO configuration for option 1-2 by RRC parameters
	For periodicity and offset3, a subset of values used for Rel16 DCP (i.e. from the parameter monitoringSlotPeriodicityAndOffset corresponding to DCI 2_6) can be used
	For number of MOs per periodicity monitored by the UE, the value range can be {1,2,3,4}
	For offset4, the value range can be agreed after agreements are made for values of possible MO durations and minimum time gap
Proposal 8	Do not support UE autonomous switching between LP-WUS monitoring and no LP-WUS monitoring without gNB knowledge.
Proposal 9	For RRC connected mode, UE assumes all non-UL slots are available for LP-WUS MOs and if any RE of any available symbol of a MO overlaps with SSB REs, UE may skip LP-WUS monitoring for that MO (i.e., drop the MO).
Proposal 10	Introduce following RRC parameters for LP-WUS in connected mode for both Option 1-1 and Option 1-2.
	LP-WUS MO duration for RRC Connected
i.	Value range: {1sym; 2sym; 3sym, 4sym; 6sym; 7sym; 1slot; 2slots} (‘sym’ refers to number of OFDM symbols)
	Sym-Bitmap (symbol-level, spanning MO duration) to indicate available OFDM symbols in a MO
i.	If this parameter is not configured, UE assumes all non-UL symbols in MO are available
ii.	Bitmap length: equal to number of OFDM symbols in LP-WUS MO duration
Proposal 11	Support Alt1 for provision of the TCI state for LP-WUS:

4	

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

Source:	ETRI
Title:		Discussion on LP-WUS operation in CONNECTED modes
Agenda item:	9.6.3
Document for:	Discussion/Decision

Summary
In this contribution, we made the following proposals for LP-WUS operation in RRC CONNECTED modes.
Proposal 1: For both Option 1-1 and Option 1-2 in RRC CONNECTED mode, it is proposed that:
If all the LP-WUS MO(s) associated with a slot where PDCCH monitoring would start, are not monitored due to the MR activity, the UE shall start the corresponding timer (drx-onDurationTimer for Option 1-1 or the new timer for Option 1-2) at that slot.
Proposal 2: For the UE capability report on the minimum time gap is between the end of the last symbol of LP-WUS and the time where MR starts PDCCH monitoring regardless of SCS, support X=3 candidate values corresponding to {6, 13, 33}ms.
Not support different values for OOK-based WUR and OFDM-based WUR and support candidate values only for OOK-based WUR
Not support special consideration for the case of CA
Proposal 3: For indication of TCI state of LP-WUS in RRC CONNECTED mode,
For the case where a UE does NOT support Rel-17 unified TCI framework but supports LP-WUS is supported in Rel-19:
Alt2: RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them
For the case where a UE supports Rel-17 unified TCI framework and supports LP-WUS is supported in Rel-19:
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,
Alt2: RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them
Proposal 4: It is proposed to support fallback mechanisms that allow the MR to switch to legacy C-DRX operation when the channel condition of LP-WUS is not sufficient, such as when it falls below a pre-configured threshold.
Details on pre-configured threshold are up to RAN4
Proposal 5: It is proposed to define an indication mechanism for the UE to notify the gNB when fallback from LP-WUS monitoring to PDCCH monitoring is triggered due to poor channel conditions.
The indication mechanism can be based on (implicit) measurement reporting or a (explicit) MAC CE indication
Proposal 6: It is proposed not to require explicit indication from the UE to inform the gNB of successful LP-WUS monitoring, except for the fallback case.
Proposal 7: It is proposed NOT to support LP-WUS operations under Option 1-1 and Option 1-2 when the UE is configured with CA with dual DRX groups in RRC CONNECTED mode.

3GPP TSG RAN WG1 #121		                                           R1-2504189
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	9.6.3
Source: 	OPPO
Title:	Further consideration on LP-WUS operation in connected mode
Document for:	Discussion & Decision

Conclusion
In this contribution, we had further discussed and analyzed lower power WUS in RRC CONNECTED mode. As summery, we have following proposals:
Proposal 1: 
A UE can report supported number of detecting codepoints for monitoring wake-up indication in CONNECTED mode, from 2 candidates {4, 8}.
A UE can be indicated by LP-WUS codepoints, in which each codepoint can be corresponding to one or more UEs in CONNECTED mode.
UE in CONNECTED mode is UE-specifically configured with the LP-WUS resources and codepoints. 
Proposal 3: Support the case when UE is configured with CA with dual DRX groups in RRC CONNECTED mode:
LP-WUS can be configured only on PCell.
LP-WUS indication is applicable to all serving cells of all DRX groups.
No additional UE capability is introduced.
Proposal 2: For RRC CONNECTED mode and Option 1-2, UE can detect all LP-WUS monitoring occasions the before minimum time gap given based on UE capability from the starting of the new timer.
Proposal 4: For the LP-WUS activation and deactivation by pre-configured condition(s), timer-based monitoring of LP-WUS is the baseline.
Proposal 5: For the LP-WUS operation, the LR/MR simultaneous activation can be allowed. RAN1 do not conclude the assumption if LR and MR cannot work in same time. 
Proposal 6: When Rel-17 unified TCI framework is configured and UE is capable, LP-WUS follows the activated/indicated TCI-state by MAC-CE/DCI, same as other DL channels/signals.
Otherwise,
RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS.
Proposal 7: In RRC CONNECTED mode, support UE capability report one value among 3 candidate values for minimum time gap between LP-WUS reception and MR to start PDCCH monitoring.
3 ms, 13ms and 33 ms are the candidature values.
UE could additionally report as UAI with another smaller gap than its capability report and among the candidature values.

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

Agenda Item:	9.6.3
Source: 	LG Electronics
Title: 	Discussion on LP-WUS operation in CONNECTED modes
Document for:	Discussion and decision

Conclusion
In this contribution, we shared our views on the LP-WUS operation in CONNECTED modes. Followings are proposed for LP-WUS operation in CONNECTED modes:
Proposal #1: For LP-WUS MOs in connected mode for Option 1-1,
a number of consecutive slots that MO lasts per periodicity can be introduced to define Z.
Proposal #2: Multiple MOs per periodicity should be considered for both Option 1-1 and Option 1-2, and the unified design should be adopted.
The number of MOs per periodicity is defined considering FAR.
Proposal #3: After the time offset4 from the following points in time, the UE starts PDCCH monitoring via new timer,
prior to the beginning of a symbol of the first LP-WUS MO per periodicity.
from the last symbol of the first LP-WUS MO per periodicity.
Proposal #4: Consider that the UE can report different set of values for OOK-based WUR and OFDM-based WUR.
Proposal #5: When Rel-17 unified TCI-state framework is not supported or configured, support separate indication/configuration for QCL source of LP-WUS
Re-use existing TCI-state framework to indicate TCI state of LP-WUS (i.e., Alt2)
If TCI-state is configured but not indicated, a UE assumes that LP-WUS is QCLed with SSB that the UE recently received for random access or initial access. 
Proposal #6: When LP-WUS is configured with Cell DTX, discuss whether the UE is expected to monitor LP-WUS triggering DRX Active Time overlapped with Cell DTX inactive period.
For example, during Cell DTX active period the UE may not monitor LP-WUS that can trigger DRX Active Time overlapped with Cell DTX inactive period.
Proposal #7: Support UE fallback to PDCCH monitoring, 
when the UE does not receive LP-WUS for a certain time duration.

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

Source:	MediaTek Inc.
Title:	LP-WUS operation in CONNECTED modes
Agenda item:	9.6.3
Document for:	Discussion and decision

Summary
In this contribution, the following proposals are provided:

Proposal 1: LP-WUS Fallback Mechanism for MR Activity
Applicable MR Activity: Define applicable MR activities to include: 
Ongoing PDSCH reception or PUSCH transmission (including scheduled and grant-free).
Monitoring for or receiving a PDCCH indicating a HARQ retransmission.
PRACH transmission or Msg3/MsgA PUSCH transmission.
SR transmission.
RRC Parameter for Enablement: Introduce a new boolean RRC parameter, e.g., lpWus-fallbackOnMRAcntivity, within the LP-WUS configuration to enable/disable this behavior. If not configured, the default behavior is disabled to maximize power saving unless explicitly needed.
Timer Initiation: The drx-onDurationTimer (for Option 1-1) or the "new timer" (for Option 1-2) shall start at the beginning of the slot where PDCCH monitoring would have started had an LP-WUS MO been monitored and indicated wake-up.

Proposal 2: UE Capability for Minimum LP-WUS to PDCCH Monitoring Time Gap
Values for V1/V2/V3: Support: V1 = 3ms, V2 = 13ms, V3 = 33ms, aiming for UE to report a single triplet of values.
Different Receiver Types: Do not support different sets of values for different receiver types in Rel-19 to minimize UE capability signaling complexity. The reported values should cover the UE's supported LP-WUS receiver type(s).
Carrier Aggregation (CA): The reported UE capability value applies to the PCell where LP-WUS is configured. The gap is defined from LP-WUS on PCell to the earliest possible start of PDCCH monitoring on any serving cell of the DRX group. No separate capability for CA.
UAI Candidate Values: Support UAI for the UE to indicate a preference from the set of values it reported in its capability (e.g., if it can temporarily meet a shorter gap). The UAI indicates one of the {V1, V2, V3} values that the UE currently prefers or can meet.

Proposal 3: RRC Parameters for LP-WUS Option 1-1
Reference Time for offset1: SFN=0, slot 0 of the PCell.
Candidate Values for periodicity (of LP-WUS MOs): {20, 40, 80, 160, 320} ms.
Candidate Values for time offset1: Integer values representing slots, from 0 up to (periodicity in slots - 1).
Candidate Values for time offset2: {0, 5, 10, 20, 40} ms.
Candidate Values for Z: {1, 2, 3, 4}.

Proposal 4: RRC Parameters for LP-WUS Option 1-2
Reference Time for offset3: SFN=0, slot 0 of the PCell (or PSCell if applicable for NR-DC).
Candidate Values for periodicity (of LP-WUS MO series): {40, 80, 160, 320, 640} ms.
Candidate Values for time offset3: Integer values representing slots, from 0 up to (periodicity in slots - 1).
Candidate Values for "a number of MOs for each periodicity" (N_MO_periodic): {1, 2, 3, 4}.
Details of MOs per periodicity: For Option 1-2, a set of N_MO_per_Group LP-WUS Monitoring Occasions (MOs) is defined. This group of MOs recurs with an RRC-configured GroupPeriodicity and starts at a configured time_offset3.
The individual MOs within this group (N_MO_per_Group being RRC-configured) are instances of a fundamental, RRC-configured BaseMO-Periodicity. The first MO in the group aligns with time_offset3, and subsequent MOs within the same group are separated by this BaseMO-Periodicity.
For simplicity in Rel-19, no additional RRC parameter is introduced for finer control over the intervals between MOs within the group beyond the BaseMO-Periodicity.
Candidate Values for time offset4: {5, 10, 20, 40, 80} ms. This offset is from the start of the first of the N_MO_periodic MOs in that cycle.

Proposal 5: TCI State Determination for LP-WUS
Select Alt2: RRC configures K TCI states for LP-WUS, and a new MAC-CE activates one of them. 
Reasoning: Provides more dedicated and potentially stable beam management for LP-WUS, which is critical for a low-power signal, rather than tying it to a CORESET beam that might change for other reasons.
K (number of TCI states): Support K = {1, 2, 4}.
New MAC-CE: Define a new MAC-CE to activate one of the K TCI states. If K=1, no MAC-CE activation is needed once RRC configured.
QCL Type: Finalize to QCL Type A (for Doppler, average delay, delay spread) and Type D (for spatial Rx parameters) with SSB or CSI-RS.

Proposal 6: Control Mechanisms for LP-WUS Monitoring
UE Assistance for Enablement: Do not support UE assistance for RRC enabling/disabling in Rel-19 to simplify initial deployment. gNB makes the decision based on UE capability and network strategy.
Implicit/Explicit UE Indication of Monitoring: LP-WUS monitoring by UE is known to gNB implicitly once RRC has configured and enabled it and the UE supports the feature. No explicit UE indication is necessary.
Activation/Deactivation Mechanism: Select Option 1 as the baseline: No additional indication/condition beyond RRC configuration is introduced for activation/deactivation of LP-WUS monitoring. If RRC enables it, UE monitors per RRC parameters. This provides simplicity. (Option 2 with MAC CE could be a future enhancement if proven necessary).

Proposal 7:  LP-WUS Configuration in CA/NR-DC and UE Capability for NR-DC
UE Capability for NR-DC: The UE shall report its capability to monitor LP-WUS independently for MCG and SCG. This means two separate capability bits/fields: 
lp-wus-MonitoringSupportMCG-r19
lp-wus-MonitoringSupportSCG-r19 The network can then configure LP-WUS on PCell (for MCG) and/or PSCell (for SCG) based on these capabilities, but not necessarily on both simultaneously.

Proposal 8: Periodic/Semi-Persistent SRS Transmission Behavior with LP-WUS
Apply Same Behavior to P/SP-SRS: Yes, apply the same behavior.
RRC Control for P/SP-SRS Skipping: Introduce a new RRC parameter within SRS-Config, e.g., srs-transmissionControlLPWUS-r19 (ENUMERATED {reportWhenActive, followWakeUp}). 
followWakeUp: P/SP-SRS is not transmitted if the UE is not indicated to wake up by LP-WUS during the relevant monitoring period (associated with Option 1-1 or Option 1-2). If woken up, SRS is transmitted during the subsequent active time.
reportWhenActive: P/SP-SRS is transmitted according to its configuration during any relevant active time (i.e., after LP-WUS wake-up or during legacy C-DRX active time), regardless of whether the specific LP-WUS instance indicated wake-up or not (this matches the "always report" logic for CSI). To be precise, for periods where LP-WUS is the only potential trigger for wake-up, if this is set to reportWhenActive, it means SRS is still skipped if no LP-WUS wake-up. This option should more accurately be "reportIfLPWUSactive" to align with CSI reporting. Let's refine: srs-transmissionLPWUS ENUMERATED {onWakeUp, setup}. 
onWakeUp: P/SP-SRS associated with an LP-WUS cycle is transmitted only if LP-WUS indicates wake-up.
setup: P/SP-SRS is transmitted as configured by legacy parameters, regardless of LP-WUS indication (network ensures consistency if it wants SRS). For simplicity, if this proposal is adopted, the behavior for P/SP-SRS for both Option 1-1 and Option 1-2 should be: 
If an RRC parameter (e.g., skipPeriodicSRSWithoutLPWUSWakeUp) is configured TRUE (or if not configured, this is default): UE does not transmit P/SP-SRS if not indicated to wake-up by LP-WUS.
If the parameter is configured FALSE: UE transmits P/SP-SRS as per existing configuration during periods it would be active due to LP-WUS wake-up or legacy DRX.

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

Agenda item: 	9.6.3
Source: 	Apple
Title:	LP-WUS operation in CONNECTED modes
Document for:	Discussion/Decision
 

Conclusion
In this contribution, the consideration on the procedures that are needed for CONNECTED UEs to enable LP-WUS operation are provided and the following proposals are made: 
Proposal 1: For a UE that does not support Rel-17 unified TCI framework but supports LP-WUS, or for a UE that supports Rel-17 unified TCI framework but unified TCI framework is not configured, support Alt 1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS. 

Proposal 2: RAN1 to discuss the CSI/L1-RSRP reporting behaviour during the drx-onDurationTimer that is outside DRX Active Time but with an overlapped Active Time started before (as shown in Duration A in Fig.2) and 
Confirm the understanding that if the parameter ‘lpwus-TransmitPeriodicL1-RSRP’ or ‘lpwus-TransmitOtherPeriodicCSI’ is configured, UE still reports P-CSI/L1-RSRP during Duration A
Adopt TP#1 in section 3 for TS 38.214.

Proposal 3: For the three values for the UE capability on minimum time gap, support the following three values: V1=6, V2=13, and V3=33. 

Observations 1: UE would report a larger value in the UE capability report for a better power saving gain, assuming UE is in a deeper sleep state, while indicating to the network a smaller value in UAI, assuming that if there are time-sensitive traffic needs, UE could sacrifice the power saving for a shorter latency.
Proposal 4: No restriction on the UAI values and values reported in UE capability is needed. 
Proposal 5: If UAI is reported, the time gap from the last LP-WUS MO per periodicity and the start of new timer is not smaller than the minimum value of the minimum time gap report by UE capability and UAI.   
Proposal 6: If UAI is reported, NW could additionally configure a time offset or a number of MOs to monitor for the UE, UE only monitors the MOs that are before the time offset or according to configured number.

Proposal 7: For LP-WUS configured in cell DTX inactive period, UE does not start the corresponding drx-onDurationTimer. 

Proposal 8: Support UE autonomous fall back to PDCCH monitoring:
For Option 1-1, UE falls back to legacy C-DRX behaviors
For Option 1-2, UE falls back to PDCCH monitoring in the duration defined by the WUS_PDCCHMonitoringTimer

Proposal 9: Adopt TP#1 for TS38.214 to cover the case where the UE is configured with DRX but not configured with DCI format 2_6 or LP-WUS.
 

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

Source:	Qualcomm Incorporated
Title:	LP-WUS operation in connected mode
Agenda Item:	9.6.3
Document for: 	Discussion and Decision

Conclusion
In this contribution, we share our views on LP-WUS in connected mode and provided following proposals and observations.

Proposal 1:
For Option 1-1, 
If a UE is configured with Z > 1:
The Z LP-WUS MOs shall be associated with the same C-DRX cycle and provide consistent indication for the same C-DRX cycle of the UE. A UE does not expect to detect more than one LP-WUS with different indications for the given C-DRX cycle in the associated Z LP-WUS MOs
The time unit of periodicity is a slot
Support symbol-level starting offset for a given periodicity of LP-WUS MOs

Proposal 2:
For Option 1-2, 
If a UE is configured with more than one MOs for the periodicity:
The LP-WUS MOs shall be associated with the same slot where the new timer would start and provide consistent indication for the new timer. A UE does not expect to detect more than one LP-WUS with different indications for the new timer for the slot in the associated LP-WUS MOs.
The time unit of periodicity is a slot
Support symbol-level starting offset for a given periodicity of LP-WUS MOs

Proposal 3:
For RRC connected mode, LP-WUS duration is configured (e.g. in unit of OFDM symbols, or M and L values)
A LP-WUS spans a number of consecutive OFDM symbols according to the configured LP-WUS duration
If there is at least one OFDM symbol unavailable for the LP-WUS MO within the OFDM symbols where the LP-WUS would span, the UE does not monitor the LP-WUS in the MO
For RRC connected mode, a symbol is considered unavailable for LP-WUS monitoring if:
The symbol is in C-DRX Active Time
MR is active on the symbol outside C-DRX Active Time, e.g.:
the UE transmits SR, PRACH or CG-PUSCH on the symbol outside C-DRX Active Time, or;
the UE monitors PDCCH on the symbol outside C-DRX Active time (e.g., for monitoring CSS sets including RAR PDCCH), or;
the symbol is in measurement gap, or;
the symbol is in interruption period by BWP switching

Proposal 4:
RAN1 confirms a UE does not monitor LR and MR simultaneously in connected mode
UE does not monitor LP-WUS in C-DRX Active Time (already agreed)
UE is not required to monitor LP-WUS when MR is active outside C-DRX Active Time, e.g.:
the UE transmits SR, PRACH or CG-PUSCH outside C-DRX Active Time, or;
the UE monitors PDCCH outside C-DRX Active time (e.g., for monitoring CSS sets including RAR PDCCH), or;
the UE is in measurement gap, or;
the UE is in interruption caused by BWP switching
RAN1 confirms RAN2’s working assumption is reasonable for the case of potential collision
“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.”
RAN1 considers the working assumption can be extended to Option 1-2
In Option 1-2, when the UE is not able to monitor the LP-WUS occasion(s) the UE should start the new MAC timer for Opt.1-2 PDCCH monitoring (as if LP-WUS was detected).

Proposal 5:
V1 = 5, V2 = 10, V3 = 42
Allow a UE to report a value from {V1, V2, V3} for each of OOK-based WUR and OFDM-based WUR
Allow a UE to report different values from {V1, V2, V3} for each of frequency band and CA band combination

Proposal 6:
If Alt.1 is adopted, RRC provides a CORESET ID of the DL BWP of the PCell
If Alt.2 is adopted, RRC provides a set of K TCI state IDs of TCI states in PDSCH-Config of the DL BWP of the PCell
How to define the RRC parameter depends on whether the RRC IE LP-WUS configuration is provided under ServingCellConfig or under BWP-DownlinkDedicated

Proposal 7:
In the UAI, UE should be able to provide:
Preferred value from {3, 5, 6, 10, 13, 20, 33, 42} ms, for the serving cell (in case non-CA) or the PCell (in case CA), together with:
preferred LP-WUS type(s) (if both OOK and OFDM are supported)

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

Source:	Sharp
Title:	Discussion on LP-WUS operation in CONNECTED modes
Agenda Item:	9.6.3
Document for:	Discussion and decision

Conclusion
In this contribution, we have the following observations and proposals:
Proposal 1: Support Alternative 2 for TCI configuration, allowing LP-WUS to use a dedicated TCI state.
Proposal 2: Confirm the working assumption on using codepoint-based LP-WUS information for connected UE.
Proposal 3: The basic UE capability is to detect at least 2 codepoints per MO.
Proposal 4: Clarify the definition of the time gap from the end of the LP-WUS MO:
-   The time gap from the end of last LP-WUS MO per periodicity and the start of new timer is not smaller than the minimum time gap given based on UE capability.
Proposal 5: Support timer-based LP-WUS monitoring activation and deactivation for UEs in connected mode. 

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

Source:	NTT DOCOMO, INC.
Title:	Discussion on LP-WUS operation in CONNECTED mode
Agenda Item:	9.6.3
Document for: 	Discussion and decision

Conclusion
In this contribution, LP-WUS operation in CONNECTED mode was discussed. Based on the discussion, the following proposals were made:
Proposal 1:
As the initial reply to RAN2 LS in R1-2503616, RAN1 confirms that at least the collision with Active Time, measurement gap, interruption caused by BWP switching, and RAR window monitoring for BFR can be considered for the cases/scenarios on when the UE is not able to monitor LP-WUS, assuming that LR and MR cannot operate simultaneously.
Proposal 2:
As the reply to RAN2 LS in R1-2503616, RAN1 confirms that the candidate values V1/V2/V3 for the minimum time gap as UE capability are reused for the UAI of preferred time offset.
The indicated UAI is not smaller than the reported minimum time gap for a UE
Proposal 3:
For RRC CONNECTED mode, the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring
does not have different capability for CA
does not support different set of values for different receiver types
Proposal 4: 
For LP-WUS MO configuration in connected mode for Option 1-1
LP-WUS periodicity:  the candidate values need to consider the possibility that an LP-WUS MO can span multiple slots
LP-WUS time offset1: can be defined by reusing that for common search space, i.e., relative to the frame boundary
LP-WUS time offset2: the candidate values need to consider longer minimum time gap than DCP
Z for MO window: the candidate values include {1, 2, FFS others}
Proposal 5: 
For LP-WUS MO configuration in connected mode for Option 1-2
LP-WUS periodicity:  the candidate values need to consider the possibility that an LP-WUS MO can span multiple slots and the periodicity is no larger than long C-DRX cycle
LP-WUS time offset3: can be defined by reusing that for common search space, i.e., relative to the frame boundary
LP-WUS time offset4: the candidate values need to consider longer minimum time gap than DCP, and can be same as Option 1-1
A number of MOs for the periodicity: an RRC parameter provides the number of consecutive MOs per periodicity. The candidate values include {1, 2, FFS others}
Proposal 6:
For the cases 1) where a UE does NOT supports Rel-17 unified TCI framework and 2) where a UE supports Rel-17 unified TCI framework but Rel-17 unified TCI framework is NOT configured, support Alt2: RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them
Proposal 7: 
When LP-WUS monitoring Option 1-1 is enabled for RRC CONNECTED mode, UE can fallback to legacy C-DRX behavior
It is up to UE in which conditions it can fallback to legacy C-DRX behavior
UE needs to send feedback to indicate gNB its fallback via SR
Proposal 8:
LPWUS_MO_CONNECTED_Option1-1
LP-WUS periodicity:  the candidate values need to consider the possibility that an LP-WUS MO can span multiple slots
LP-WUS time offset1: can be defined by reusing that for common search space, i.e., relative to the frame boundary
LP-WUS time offset2: the candidate values need to consider longer minimum time gap than DCP
Z for MO window (NumOfMO_Monitoring_Option 1-1): the candidate values include {1, 2, FFS others}
LPWUS_MO_CONNECTED_Option1-2
LP-WUS periodicity:  the candidate values need to consider the possibility that an LP-WUS MO can span multiple slots and the periodicity is no larger than long C-DRX cycle
LP-WUS time offset3: can be defined by reusing that for common search space, i.e., relative to the frame boundary
LP-WUS time offset4: the candidate values need to consider longer minimum time gap than DCP, and can be same as Option 1-1
A number of MOs for the periodicity: an RRC parameter provides the number of consecutive MOs per periodicity. The candidate values include {1, 2, FFS others}

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

Agenda Item:	9.6.3
Source:	TCL  
Title:	Discussion on LP-WUS procedures in Connected mode
Document for:	Discussion and Decision 

Conclusion
In this contribution, we further discuss the LP-WUS procedures in Connected mode. We have the following proposals.
Proposal 1: V1=3ms will be appropriate in case MR is in micro sleep, which can be applied for different receiver types.
Proposal 2: The same value can be used for CA and non-CA.
Proposal 3: The preference offset indicated by UAI is not smaller than the value reported by UE capability signaling. 
Proposal 4: Based on the preference offset indicated by UAI, gNB configures time offset between the end of LP-WUS reception and the start of PDCCH monitoring.
Proposal 5: Deactivation of LP-WUS monitoring can be based on:
Timer, e.g., if the UE doesn’t detect a LP-WUS before the expiration of the timer
UL signaling including SR, PRACH, CG PUSCH.
Proposal 6: For the case where a UE does not support Rel-17 unified TCI framework or the case where a UE supports Rel-17 unified TCI framework but Rel-17 unified TCI framework is NOT configured, Alt2 is applied, i.e., RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them.

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

Agenda Item:	9.6.3

Title:	FL summary #1 on LP-WUS operation in CONNECTED mode

Source:	Moderator (NTT DOCOMO)

Document for:	Discussion, Decision

1	

Conclusions
Following agreements were made in this meeting:
To be updated

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

Agenda Item:	9.6.3

Title:	FL summary #2 on LP-WUS operation in CONNECTED mode

Source:	Moderator (NTT DOCOMO)

Document for:	Discussion, Decision

1	

Conclusions
Following agreements were made in this meeting:

Agreement:
For LP-WUS MOs in connected mode for Option 1-1/1-2, the time offset1/3 in previous agreement are configured relative to the start of SFN0

Agreement:
As the initial reply to RAN2 LS in R1-2503616, RAN1 confirms that at least the collision with Active Time, measurement gap, and RAR window monitoring for BFR can be considered for the cases/scenarios on when the UE is not able to monitor LP-WUS.

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

Agenda Item:	9.6.3

Title:	FL summary #3 on LP-WUS operation in CONNECTED mode

Source:	Moderator (NTT DOCOMO)

Document for:	Discussion, Decision

1	

Conclusions
Following agreements were made in this meeting:

Agreement:
For LP-WUS MOs in connected mode for Option 1-1/1-2, the time offset1/3 in previous agreement are configured relative to the start of SFN0

Agreement:
As the initial reply to RAN2 LS in R1-2503616, RAN1 confirms that at least the collision with Active Time, measurement gap, and RAR window monitoring for BFR can be considered for the cases/scenarios on when the UE is not able to monitor LP-WUS.

Agreement:
For the UE capability report on the minimum time gap between the end of the last symbol of LP-WUS and the time where MR starts PDCCH monitoring regardless of SCS, the same candidate values {V1, V2, V3} are supported for different receiver types
V1=5ms
V2=13ms
V3=37ms

Agreement:
For LP-WUS monitoring in RRC CONNECTED mode, when Rel-17 unified TCI framework is NOT configured or UE does NOT support Rel-17 unified TCI framework
Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS

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

Agenda Item:	9.6.3

Title:	FL summary #4 on LP-WUS operation in CONNECTED mode

Source:	Moderator (NTT DOCOMO)

Document for:	Discussion, Decision

1	

Conclusions
Following agreements were made in this meeting:

Agreement:
For LP-WUS MOs in connected mode for Option 1-1/1-2, the time offset1/3 in previous agreement are configured relative to the start of SFN0

Agreement:
As the initial reply to RAN2 LS in R1-2503616, RAN1 confirms that at least the collision with Active Time, measurement gap, and RAR window monitoring for BFR can be considered for the cases/scenarios on when the UE is not able to monitor LP-WUS.

Agreement:
For the UE capability report on the minimum time gap between the end of the last symbol of LP-WUS and the time where MR starts PDCCH monitoring regardless of SCS, the same candidate values {V1, V2, V3} are supported for different receiver types
V1=5ms
V2=13ms
V3=37ms

Agreement:
For LP-WUS monitoring in RRC CONNECTED mode, when Rel-17 unified TCI framework is NOT configured or UE does NOT support Rel-17 unified TCI framework
Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS

Conclusion
There is no consensus in RAN1 whether to specify UE autonomous fallback to PDCCH monitoring when UE monitors LP-WUS in RRC CONNECTED mode

Agreement:
As the reply to RAN2 LS in R1-2503616, RAN1 assumes that UE is not able to operate LR and MR simultaneously in Rel-19. RAN1 understanding is that the terminology of LR and MR operations are for discussion purpose and will not be specified
LR operation is the UE operation for LP-WUS monitoring
MR operation is the UE operation for all other NR signals/channels transmissions/receptions in connected mode

Conclusion
From RAN1 perspective, for the case of potential collision (if any) in Option 1-2, when the UE is not able to monitor all the LP-WUS MO(s) in a LP-WUS periodicity,
It is up to RAN2 to further discuss and finalize the specification support, if any.

Agreement:
For the UAI of preferred time offset for LP-WUS monitoring in RRC connected mode,
The candidate values are same as those for the UE capability of minimum time gap, i.e., {V1=5, V2=13, V3=37}ms
The reported UAI value is equal to or longer than the minimum time gap reported by UE capability for a UE
Note: There is no change to the RAN1 agreed definition for UAI

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

Agenda Item:	9.6.3

Title:	Final summary on LP-WUS operation in CONNECTED mode

Source:	Moderator (NTT DOCOMO)

Document for:	Discussion, Decision

1	

Conclusions
Following agreements were made in this meeting:

Agreement:
For LP-WUS MOs in connected mode for Option 1-1/1-2, the time offset1/3 in previous agreement are configured relative to the start of SFN0 where the offset is a symbol-level offset

Agreement:
As the initial reply to RAN2 LS in R1-2503616, RAN1 confirms that at least the collision with Active Time, measurement gap, and RAR window monitoring for BFR can be considered for the cases/scenarios on when the UE is not able to monitor LP-WUS.

Agreement:
For the UE capability report on the minimum time gap between the end of the last symbol of LP-WUS and the time where MR starts PDCCH monitoring regardless of SCS, the same candidate values {V1, V2, V3} are supported for different receiver types
V1=5ms
V2=13ms
V3=37ms

Agreement:
For LP-WUS monitoring in RRC CONNECTED mode, when Rel-17 unified TCI framework is NOT configured or UE does NOT support Rel-17 unified TCI framework
Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS

Conclusion
There is no consensus in RAN1 whether to specify UE autonomous fallback to PDCCH monitoring when UE monitors LP-WUS in RRC CONNECTED mode

Agreement:
As the reply to RAN2 LS in R1-2503616, RAN1 assumes that UE is not able to operate LR and MR simultaneously in Rel-19. RAN1 understanding is that the terminology of LR and MR operations are for discussion purpose and will not be specified
LR operation is the UE operation for LP-WUS monitoring
MR operation is the UE operation for all other NR signals/channels transmissions/receptions in connected mode

Conclusion
From RAN1 perspective, for the case of potential collision (if any) in Option 1-2, when the UE is not able to monitor all the LP-WUS MO(s) in a LP-WUS periodicity,
It is up to RAN2 to further discuss and finalize the specification support, if any.

Agreement:
For the UAI of preferred time offset for LP-WUS monitoring in RRC connected mode,
The candidate values are same as those for the UE capability of minimum time gap, i.e., {V1=5, V2=13, V3=37}ms
The reported UAI value is equal to or longer than the minimum time gap reported by UE capability for a UE
Note: There is no change to the RAN1 agreed definition for UAI

Final reply LS on LP-WUS in RRC_CONNECTED is endorsed in R1-2504888

Agreement:
Nominal MO duration (X1, in unit of OFDM symbols) and actual LP-WUS duration (X2, in unit of OFDM symbols) are configured for LP-WUS in connected mode. (Alt C)
A LP-WUS MO spans the nominal MO duration (i.e., the LP-WUS MO duration is the same as the nominal MO duration.)
If the number of available OFDM symbols within the nominal MO duration is no less than the actual LP-WUS duration, UE monitors LP-WUS on the first X2 available symbols within the LP-WUS MO.
Otherwise, UE does not monitor LP-WUS in this MO (i.e., the MO is dropped).
Note: Any symbols that are not defined as unavailable are available symbols for LP-WUS.
Further discuss possible introduction of UE capability to restrict configuration of LP-WUS MO and LP-WUS duration. For example, 
A LP-WUS spans a number of consecutive OFDM symbols according to the configured LP-WUS duration
If there is at least one OFDM symbol unavailable for the LP-WUS MO within the OFDM symbols where the LP-WUS would span, the UE does not monitor the LP-WUS in the MO

Agreement:
For UE to determine whether a symbol is available for LP-WUS in connected mode, at least the following is supported:
A unit level bitmap with a periodicity 10, 20, or 40 units and a 14-bit or 28-bit symbol-level bitmap that covers 1 or 2 slots can be configured, where each unit is 1 or 2 slots for 14-bit or 28-bit symbol-level bitmap, respectively, with a maximum periodicity of 40ms.
‘1’ in unit-level bitmap means the symbol level bitmap is applied to determine which symbols are unavailable in the unit for LP-WUS (‘0’ means unavailable).
‘0’ in unit-level bitmap means: all the symbols in the unit are unavailable for LP-WUS
If the slot-level bitmap is not configured, UE assumes all 1’s for the bitmap.
If the symbol-level bitmap is not configured, UE assumes all 1’s for the bitmap.

Agreement:
For the handling of at least PCell/PSCell SSB for connected mode, the SSB symbols are considered as unavailable for LP-WUS 

Agreement:
The UL symbols/slots configured in tdd-UL-DL-configurationCommon or tdd-UL-DL-ConfigurationDedicated are considered as unavailable for LP-WUS in connected mode