3GPP TSG RAN WG1 #120bis			R1-2501769
Wuhan, China, April 7th – 11th, 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.
Observation 2: OFDM WUR has smaller minimum time gap than OOK WUR
OFDM WUR has less processing time than OOK WUR
OFDM WUR has less ramp-up time than OOK WUR 

Proposals:
Proposal 1: RRC activation/deactivation is the baseline
DCI deactivation and fallback mechanism based on 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: A time window defined as number of MOs is needed for both option 1-1 and option 1-2
Time offset 4 could be defined between the window start and new timer start
Proposal 3: Outside new or legacy active time, reusing legacy mechanism as DCP for Searchspace monitoring.
Proposal 4: The LP-WUS is used to indicate wake-up for PDCCH monitoring
Target all the configured searchspaces in the active DL BWP
Proposal 5: Use RRC configuration to indicate the TCI state for LP-WUS.
Proposal 6: LP-WUS can be transmitted in PCell or PScell.
Proposal 7: It is considered to support option 3 or not support dual DRX group for LP-WUS similar as DCP
Proposal 8: The candidate value is defined based on LP-WUS processing time and ramp-up time from LR to MR
The candidate value should differ from different WUR type
There is no need to differentiate the CA case
Proposal 9: During Cell-DTX off period, UE does not need to monitor LP-WUS.

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

Source:	vivo
Title:	Discussion 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 and conclusion are summarized as follows.
Proposal 1: For LP-WUS operation Option 1-2, LP-WUS periodicity is no larger smaller than long C-DRX cycle.
No other restrictions for LP-WUS monitoring configuration in relation with C-DRX configuration are needed. 

Proposal 2: For the case when UE is configured with CA with dual DRX groups in RRC CONNECTED mode, for both LP-WUS procedure Option 1-1 and Option 1-2, a UE monitors LP-WUS only on one serving cell per DRX group. 
The serving cell where to monitor LP-WUS is configured by the network. 
LP-WUS indication is applicable to all serving cells in the DRX group where the LP-WUS is monitored
Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation

Proposal 3 For LP-WUS operation option 1-1 and option 1-2 in RRC CONNECTED mode, the serving cell on which the LP-WUS can be RRC configured cell other than Pcell/PSCell.

Proposal 4: For the candidate values for the UE capability report on the minimum time gap for each SCS, it is unnecessary to restrict the candidates to the same set for different SCSs. 
Proposal 5: Allow a UE to report different values of the minimum time gap for OOK-based WUR and OFDM-based WUR, and for non-CA and CA scenarios. Up to 20ms can be considered as the maximum value for the minimum time gap reported by the UE. 
Proposal 6: 
A single time offset is configured for a UE at a given time.
The UAI value(s) should be equal to or longer than the minimum time gap reported by UE capability.
More UAI details should be decided in RAN2.
Proposal 7:
For Option 1-1 of LP-WUS CONNECTED mode operation, the minimum time gap is defined as the time between the end of the slot of the LP-WUS MO where LP-WUS is detected and the beginning of the slot where the UE would start the drx_onDurationTimer. 
For Option 1-2 of LP-WUS CONNECTED mode operation, the minimum time gap is defined as the time between the end of the slot of the LP-WUS MO where LP-WUS is detected and the beginning of the first slot where the UE would start PDCCH monitoring. 

Conclusion: From RAN1 perspective, when LP-WUS monitoring is enabled for RRC CONNECTED mode for Option 1-2, it is supported that SR, PRACH and CG-PUSCH triggers MR PDCCH monitoring according to the legacy UE behavior.

Proposal 8: When LP-WUS monitoring is enabled for RRC CONNECTED mode, support UE fallback to PDCCH monitoring when UE monitors LP-WUS.
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 is according to the C-DRX configuration
For LP-WUS operation option 1-2, the fallback behavior for PDCCH monitoring is always-on PDCCH monitoring. 
Proposal 9: At least for LP-WUS connected mode operation Option 1-2, support enhanced PDCCH skipping indication that is used to indicate UE to terminate the DRX active time (e.g., stop PDCCH monitoring on one or multiple serving cells) and starts LP-WUS monitoring. 
Proposal 10: For LP-WUS connected mode operation Option 1-1 configured with Cell DTX, UE is expected to monitor LP-WUS during the Cell DTX inactive time.   
Proposal 11: For LP-WUS connected mode operation Option 1-2 configured with Cell DTX, a UE does not expect to monitor the LP-WUS during the non-active periods of cell DTX of a serving cell. 
Proposal 12: For LP-WUS MOs in connected mode for both Option 1-1 and Option 1-2, support a maximum number of M=4 MOs per periodicity.
The M value is configured by RRC with the value range of INTEGER (1..4)

Proposal 13: For LP-WUS MOs in connected mode for both Option 1-1 and Option 1-2, support more than one LP-WUS configurations where the QCL configuration/indication is on a per LP-WUS configuration.
Proposal 14: For LP-WUS MOs in connected mode for Option 1-1, support Approach 1:
LP-WUS MOs, including periodicity and time offset1, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
The periodicity and time offset1 provide the periodicity and offset of the LP-WUS MO(s), 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}

The number of MOs per periodicity “M” is configured by RRC, the candidate values for M is INTEGER {1..4}

Time offset2 i.e., Time_offset_CONNECTED_Option1-1 configured by a new RRC parameter, 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 Time_offset_CONNECTED_Option1-1 is in multiples of 0.125ms (milliseconds), INTEGER (3..640), where 3 corresponds to 0.375ms, 4 corresponds to 0.5ms and so on. 
Z configured by a new RRC parameter provides a number of consecutive LP-WUS period(s) for LP-WUS monitoring for a C-DRX cycle. 
The candidate values on the Z can be: INTEGER {1.. [2]} 
The UE monitors LP-WUS at the WUS MOs in the first LP-WUS monitoring period(s) indicated by Z.
The LP-WUS MOs associated with the same C-DRX cycle provides consistent indication for the same C-DRX cycle of the UE, i.e., UE does not expect to detect more than one LP-WUSs with different indications for the UE in the LP-WUS MOs associated with the same C-DRX cycle.
UE is not required to monitor LP-WUS during the X slots prior to the beginning of a slot where the UE would start the drx-onDurationTimer, where X corresponds to the UE capability signaling report of the minimum time gap between the end of the slot of the LP-WUS MO where LP-WUS is detected and the beginning of the slot where the UE would start the drx_onDurationTimer.

Proposal 15: For LP-WUS MOs in connected mode for Option 1-2, support Approach 1:
LP-WUS MOs, including periodicity and time offset3, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s). 
The periodicity and time offset3 provide the periodicity and offset of the LP-WUS MO(s). 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 number of MOs per periodicity “M” is configured by RRC, the candidate values for M is INTEGER {1..4}
UE monitors LP-WUS in the LP-WUS MOs and, if triggered to wake up, starts a new timer for PDCCH monitoring triggered by LP-WUS, after a time offset4, i.e., Time_offset_CONNECTED_Option1-2. 
The Time_offset_CONNECTED_Option1-2 configured by the network indicating a time between the end of the slot of the LP-WUS MO where LP-WUS is detected and the beginning of the first slot where the UE starts PDCCH monitoring via starting the new timer. 
The values for Time_offset_CONNECTED_Option1-2 is in multiples of 0.125ms (milliseconds), INTEGER (2..160), where 2 corresponds to 0.25ms, 3 corresponds to 0.375ms and so on. 
UE is not expected to be configured with a time offset4 that is smaller than the minimum value of the minimum time gap(s) reported by UE capability signaling.
Proposal 16: 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 C and Type D, when applicable

Proposal 17: For LP-WUS monitoring in RRC CONNECTED mode, support separate indication/configuration for QCL source of LP-WUS MO(s).
Separate RRC configuration and separate MAC CE are introduced to configure/indicate TCI state of LP-WUS monitoring.

3GPP TSG RAN WG1 #120bis                                                     R1-2501877
Wuhan, China, April 07th – 11th, 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: For the determination of the value of Z and X, the same mechanism as DCP can be reused.
Proposal 2: Activation/deactivation of LP-WUS monitoring by gNB L1 signaling (e.g., DCI) can be considered.
Proposal 3: For the case when UE is configured with CA without dual DRX groups, the serving cell on which the LP-WUS is configured can be RRC configured cell other than PCell.
Proposal 4: For the case when UE is configured with NR-DC with CA without dual DRX groups or without CA, the serving cell on which the LP-WUS is configured can be RRC configured cell other than Pcell/PSCell.
Proposal 5: During Cell DTX inactive time, the UE is expected to monitor LP-WUS.
Proposal 6: Separate indication/configuration for QCL source of LP-WUS should be supported.

3GPP TSG RAN WG1 #120bis		                                                     R1- 2502001
Wuhan, China, April 7th – 11th, 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 needs to 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 2 candidate value for the UE capability report on the minimum time gap with considering at least {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.
Proposal 4: For Option 1-1, 1, Z can be larger than 1 and configured by RRC.
Proposal 5: X is the value of UE capability report with ‘ms’ unit.  
Proposal 6: In Option1-2, support multiple LP-WUS MOs per periodicity and the definition of time offset4 is related with the LP-WUS MO window.
Proposal 7: 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.
Proposal 8: For the case when UE is configured with NR-DC and/or CA without dual group in RRC CONNECTED mode, LP-WUS can be configured in the PCell or on the SpCell per cell-group.
Proposal 9: For Rel-19 LP-WUS, the dual DRX group and LP-WUS cannot be configured simultaneously.
Proposal 10: A fallback mechanism to the legacy behavior of PDCCH monitoring can be specified to battle the MDR impact to the PDCCH decoding for UEs in CONNECTED mode.

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

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

1. 

PROPOSALS

Proposal 1:	For options 1-1, X corresponds to the configured minimum time gap.

Proposal 2:	For option 1-1, if more than one MO is configured for triggering PDCCH monitoring of the same onDuration, those MOs are restricted to the period/window between time offset 2 and the time set by X.
	FFS:   Which MOs within this time window the UE monitors, e.g. all or the first few defined by a rule/parameter.

Proposal 3:	For option 1-1, the maximum number of MOs the UE is expected to monitor for a given onDuration is [4].

Proposal 4:	For option 1-1, the UE is expected to blindly monitor all the MOs within the window.
	Note:    The network can select which MO(s) are used.
	
Proposal 5:	For option 1-2, new parameters time_offset6 and option1-2_periodicity define where LP-WUS triggered onDurations can start.

Proposal 6:	For option 1-2, the UE starts monitoring for LP-WUS at a time-offset5 prior to the slot to when the onDurationTimer can start.

Proposal 7:	For option 1-2, the UE is not required to monitor LP-WUS for time-offset4 prior to the slot when the onDurationTimer can start.
	FFS:  If this is the same as the minimum time gap

Proposal 8:	For option 1-2, the time between time-offset5 and time-offset4, corresponds to a time window where the UE is expected to monitor all MOs.
	
Proposal 9:	For option 1-2, the maximum number of MOs the UE is expected to monitor for a given onDuration is [4].

Proposal 10:	For option 1-2, the UE is expected to blindly monitor all the MOs within the window.
	Note:    The network can select which MO(s) is uses.

Proposal 11:  	The number, X, of candidate minimum time gap values, in a UE capability report, is limited to 2.	

Proposal 12:  	The candidate values for the minimum time gap, are not varied for different SCS.

Proposal 13:  	The candidate values for the minimum time gap, are not varied for different WUR types.

Proposal 14:	RAN1 determine if the singe cell candidate set of minimum time gap values is sufficient for CA scenarios.

Proposal 15:	The UE can use the UAI procedure to signal any value from the full candidate set.

Proposal 16:	For NR-DC and/or CA scenarios without dual-drx, LP-WUS can be configured on any serving cell within a cell group with an active DL BWP.
Proposal 17:	For NR-DC configuration with or without dual-drx, a new UE capability/capability component, is supported to indicate to the network the UEs ability to monitor 2 LP-WUS signals on separate component carriers.
Proposal 18:	The network identifies a specific PDCCH coreset in the active BWP that the LP-WUS is using, for the UE to determine the QCL source to apply for the LP-WUS (option 2).
Proposal 19:	LP-WUS can be monitored outside the cell DTX Active time. 

Proposal 21: 	For CONNECTED mode, there is no change to how existing MR based measurements (RRM/RLM/BFD/CSI) are determined when LP-WUS is enabled.

Proposal 22:     	Option 1-3 is deprioritised.





4.   

3GPP TSG RAN WG1 #120-bis			R1-2502060
Wuhan, CN, April 7th – 11th, 2025
Agenda Item:	9.6.3
Source:	Panasonic
Title:	Discussion on LP-WUS operation in CONNECTED mode
Document for:	Discussion/Decision

Conclusion
From RAN1 perspective, when LP-WUS monitoring is enabled for RRC CONNECTED mode, it is supported that SR, PRACH and CG-PUSCH triggers MR PDCCH monitoring according to the legacy UE behaviour
Above applies at least for Option 1-1

Agreement
For LP-WUS monitoring in RRC CONNECTED mode, select one of the options on how to define/configure/indicate QCL source of LP-WUS
Opt1: Separate indication/configuration for QCL source of LP-WUS
Opt2: Association of QCL source between LP-WUS and PDCCH/CORESET

Agreement
For LP-WUS MOs in connected mode for Option 1-1, support Approach 1:
LP-WUS MOs, including periodicity and time offset1, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
Time offset2 indicates a time prior to a slot where the drx-onDurationTimer would start
UE monitors the first Z LP-WUS MO(s) at or after Time offset2. 
FFS: How to determine the value of Z
Time offset2 is RRC configured
UE is not required to monitor LP-WUS during the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. FFS: How X is determined.

Agreement
For LP-WUS MOs in connected mode for Option 1-2, support Approach 1:
LP-WUS MOs, including periodicity and time offset3, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s). 
FFS one or multiple MOs per periodicity
UE monitors LP-WUS in the LP-WUS MOs and, if triggered to wake up, starts a new timer for PDCCH monitoring triggered by LP-WUS, after a time offset4. 
The time offset4 configured by the network indicating a time, after which the UE starts PDCCH monitoring via starting the new timer. 
FFS: Definition of time offset4 

Agreement
For the X = [2, 3] candidate values for the UE capability report on the minimum time gap for each SCS, consider {0.25, 0.5, 1, 2, 3, 6, 10, 20, 30, 40}ms
Note: Other values are not precluded
Only for reported value of [20ms,] 30ms and 40ms (if supported), the reported values assume SSB periodicity of 20ms and ensures SSB(s) before PDCCH reception and during time gap
FFS: translation of minimum time gap for different SSB periodicities including different candidates for different SSB periodicities
FFS whether the same set of candidates are used for different SCSs
FFS whether different values are selected for OOK-based WUR and OFDM-based WUR
FFS whether/how to consider the case of CA
FFS: candidate values that can be indicated by UAI

3GPP TSG RAN WG1 #120bis		R1-2502077
Wuhan, China, April 7th – 11th, 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 #120-bis			R1-2502169
Athens, Greece, February 17th–February 21th, 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:
If X=2 is supported, the candidate values of minimum time gap are {3, 10}ms.
If X=3 is supported, the candidate values of minimum time gap are {0/1, 3, 10}ms.
Above candidate values are applicable for different SCSs, and there is no need to introduce separate values for OOK-based WUR and OFDM-based WUR.

Proposal 2. Regarding QCL information for LP-WUS, support:
Opt 1: Separate indication/configuration for QCL source of LP-WUS in previous agreement.
SSB and/or CSI-RS can be the QCL source of LP-WUS QCL type(s) is Type C, and Type D when applicable.

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

Proposal 4. Regarding LP-WUS monitoring in CA/DC, support:
LP-WUS is configured only in PCell/PSCell.
For CA/DC with dual DRX groups, LP-WUS can be separately configured for each DRX cell group. 

Observation 1. LP-SS occasion/LP-WUS MO may go across multiple slots and contiguous in time. Moreover, a LO/LP-SS burst may also contiguous in time.

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

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502239
Wuhan, China, April 7th-11th, 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:
DCI format 2_6 is monitored outside active time of cell DTX, which leaves gNB the flexibility to wake up UE earlier.
Monitoring LP-WUS also outside active time of cell DTX has marginal impact on power saving gain, since the power consumption for LP-WUS monitoring is expected to be low.

For the purpose of future discussion, RAN1 assumes at least the following as baseline.
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.
FFS how to let gNB and UE have the common understanding on where the UE performs measurement.
FFS: additional consideration of simultaneous operation between LP-WUR and MR.
FFS: UE capability.
The minimum time gap reported by the UE capability is defined between the end of the detected LP-WUS/the monitored last LP-WUS MO and the start of the PDCCH monitoring in the new timer or on duration timer respectively for Option 1-1 and Option 1-2.
For the X = 3 candidate values for the UE capability report on the minimum time gap for each SCS, consider {2, 30, 42} ms
For reported value of 30ms and 42ms, the reported values assume SSB periodicity of 20ms and ensures SSB(s) before PDCCH reception and during time gap
For larger SSB burst periodicity than 20ms, the translation of delay wake-up is used; For 5ms and 10ms SSB periodicity, the minimum value of 42ms/30ms assuming 20ms SSB periodicity should be kept;
The same set of candidates are used for different SCSs
Same values are used for OOK-based WUR and OFDM-based WUR
The case of CA should be considered and the minimum time gap is the same between CA case and non-CA case
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 X candidate values, which already considers the time duration required by synchronization:
The value indicated by UAI must be larger than the duration reported from the X candidate values, which already considers the time duration required for synchronization;
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, maximum number of LP-WUS information bits is up to 16 bits.
In CONNECTED mode, if LP-WUS monitoring is enabled, at least the following options are further supported.
Deactivation of LP-WUS monitoring based on timer.
Note: Activation of LP-WUS monitoring based on timer has been supported by the agreement for UE behavior Option 1-2 in RAN1#118 and the agreement in RAN2 #127bis. Activation of LP-WUS monitoring by gNB L2 signaling has been supported by the agreements in RAN1#119 and RAN2#128. And Activation/deactivation of LP-WUS monitoring based on implicit indication/condition, e.g. UL transmission has been supported in RAN1#120.
Note: PDCCH monitoring of a UE is suspended if LP-WUS monitoring of the UE is activated, and vice versa. PDCCH monitoring of a UE is resumed if LP-WUS monitoring of the UE is deactivated. 
The impact due to miss-detection/falsely-detection of LP-WUS activation/deactivation signaling should be minimized/avoided for CONNECTED mode UEs by e.g. explicit feedback signaling from UE to gNB, and the explicit feedback signaling can reuse SR.
For the LP-WUS monitoring occasion configuration
For Option 1-1,
UE monitors all the MOs between the time point determined by Time offset2 and the time point determined by X.
Time offset2 is configured to be no smaller than the minimum wake-up delay reported by UE capability and UAI (optional).
X is reported by UE capability.
For Option 1-2,
Time offset4 is configured to be no smaller than the minimum wake-up delay reported by UE capability and UAI (optional).
The basic capability for the maximum number of codepoints checked per MO by a UE is 2.
If DCP is configured, after LP-WUS monitoring is activated, the UE should not monitor DCP in MR.
After LP-WUS monitoring is activated, the UE should stop/suspend the Rel-17 PDCCH adaption mechanism, if configured.
LP-WUS monitoring outside legacy cell DTX active time according to the LP-WUS monitoring configuration can trigger the PDCCH monitoring.
When UE is configured with CA, LP-WUS monitoring is configured on one cell, where the cell can be either PCell or SCell.
If LP-WUS is configured to be monitored on a SCell for a UE, the UE expects that the SCell is not deactivated.
For the case when UE is configured with CA with dual DRX groups in RRC CONNECTED mode, 
LP-WUS can be configured on a serving cell in default DRX group.
LP-WUS indication is applicable to all serving cells
UE does not monitor LP-WUS during C-DRX active time, where the C-DRX active time is defined as
For option1-1, the C-DRX active time is defined as the union set of the legacy C-DRX active time from both DRX groups
For option1-2, the C-DRX active time is defined as the union set of the legacy C-DRX active time from both DRX groups, as well as the running time of a single new timer for both DRX groups.
Support association of QCL source between LP-WUS and PDCCH/CORESET(Opt2).
If LP-WUS monitoring is activated by PDCCH, UE can assume the same QCL source as the CORESET to receive the PDCCH activating LP-WUS monitoring.
If LP-WUS monitoring is activated by timer, the QCL source can be the same as the CORESET to receive the last PDCCH before the timer expires.
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 #120bis		                                           R1-2502259
Wuhan, China, April 7th – 11th, 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. We basically consider unified signal for different RRC modes and the procedures should be based on that unified design. 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 2: For RRC CONNECTED mode and Option 1-1/1-2, the LP-WUS monitoring occasions use one set of parameters for periodicity and offset.
For option 1-1, configured Z as a number of detecting MO started from configured offset2 slots before the start of drx-onDurationTimer. 
For option 1-2, after configured offset4 slots from positive detection of wake-up the new timer would start.
Proposal 3: When Cell DTX is configured with LP-WUS, LP-WUS is assumed to be disabled during the Cell DTX inactive time.
Proposal 4: When the LP-WUS is configured with CA in CONNECTED mode, only PCell/PSCell can be configured with LP-WUS. 
Proposal 5: For the LP-WUS activation and deactivation by pre-configured condition(s), timer-based monitoring of LP-WUS is the baseline.
Proposal 6: RAN1 can assume that MR measurements are one of the UE assistant information for the LP-WUS activation and deactivation. 
RAN1 discuss the introduction LP-SS measurement in CONNECTED mode as another UE assistant information. 
Proposal 7: For the LP-WUS the LR/MR activation assumption may be needed. We are fine for concluding the design assumption with clear definition of LR and MR behavior. The specification impact is to be further discussed.
Proposal 8: LP-WUS Monitoring Occasions can be associated with CORESETs for the TCI states determination. The activated TCI state of the CORESET is applied for the associated LP-WUS Monitoring Occasion.
SSB and/or CSI-RS is the QCL source of LP-WUS and the QCL type(s) is Type A, and Type D when applicable
Proposal 9: 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.
20 ms, 6 ms and 2 ms are the candidature values.
UE could additional report another smaller gap than its capability report as UAI.
Proposal 10: RAN1 may specify that the monitoring occasion of LP-WUS and associated monitoring occasion of PDCCH should meet the reported minimum gap.

3GPP TSG RAN WG1 #120bis			R1-2502304
Wuhan, China, April 07th – 11th, 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: Supporting dual DRX groups with RRC CONNECTED mode LP-WUS monitoring can reduce achievable power saving gains through LP-WUS monitoring and impact LP-WUS coverage.  
Observation 5: Compact LP-WUS payload size is important to support coverage comparable with PUSCH for Msg3. 
Observation 6: LP-WUS payload can be reduced by implicitly indicating some of information of LP-WUS. 
Observation 7: Time/frequency synchronization of MR is not impacted by RRC CONNTECTED mode LP-WUS monitoring. 
Observation 8: 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 a LP-WUS monitoring enabled UE, support activating/deactivating LP-WUS monitoring based on following preconfigured conditions.
For activating LP-WUS monitoring: level of UE activity (e.g., timer and/or counter associated with UE activity), channel/signal quality, mobility. 
For deactivating LP-WUS monitoring: level of UE activity (e.g., timer and/or counter associated with UE activity), channel/signal quality, mobility, LP-WUS reception quality. 
Proposal 3:  For OFDM based LP-WUR, both NR-SS (existing SSB) and LP-SS can be used to determine activation/deactivation of LP-WUS monitoring.
Proposal 4: Introduce a mechanism to report UE decision of LP-WUS monitoring deactivation potentially with reason for the decision.
Proposal 5: A UE is not configured with dual DRX groups and LP-WUS monitoring simultaneously. 
Proposal 6: For RRC CONNTECTE mode LP-WUS monitoring, when UE is configured with CA, LP-WUS is only configured on the PCell. 
Proposal 7: For RRC CONNTECTE mode LP-WUS monitoring, when UE is configured with NR-DC, LP-WUS is only configured on the PCell/PSCell.  
Proposal 8: A subset of LP-WUS information can be informed to UE implicitly using LP-WUS monitoring resource (e.g., LO and MO) association and structure of LP-WUS.
Proposal 9: For RRC CONNECTED mode LP-WUS monitoring, translation of reported minimum time gap for different SSB periodicities is not supported. 
Proposal 10: In RRC CONNECTED mode LP-WUS monitoring, for minimum time gap between LP-WUS reception and MR to start PDCCH monitoring, different sets of candidates are not supported for different SCSs. 
Proposal 11: 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 12: In RRC CONNECTED mode LP-WUS monitoring, for minimum time gap between LP-WUS reception to starting PDCCH monitoring, different set of candidates or reported values are not defined based on supporting/not supporting CA. 
Proposal 13: 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 14: LP-SS or LP-WUS is QCLed with one SSB and/or CSI-RS in QCL Type C and QCL Type D (when applicable).
Proposal 15: LP-SS is supported for RRC CONNECTED mode LP-WUS monitoring. 
Proposal 16: LP-WUS is QCLed with LP-SS in QCL Type A and QCL Type D (when applicable).
Proposal 17: For LP-WUS monitoring in RRC CONNECTED mode, Option 1 is supported for defining/configuring/indicating QCL source of LP-WUS. 
Option 1: Separate indication/configuration for QCL source of LP-WUS.
Proposal 18: UE is not expected to monitor for LP-WUS during Cell DTX inactive time. 

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

Agenda Item	: 	9.6.3
Source 	:	Sony 
Title 	:	LP-WUS operation in CONNECTED mode
Document for 	:	Discussion and decision

Conclusion
This document has considered the LP-WUS operation in RRC CONNECTED mode. We made the following proposals:
Proposal 1: The first Z LP-WUS MO(s) is determined based on the number of MO(s) at or after Time offset2 (and before the switching time-gap).
Proposal 2: the time-gap duration: X [slots/symbols] is determined based on the UE capability and also may depend on the numerology.
Proposal 3: Support LP-WUS option 1-2 with the configuration with multiple MOs per LP-WUS periodicity.
Proposal 4: The time offset 4 is the time offset from the LP-WUS MO reception to the starting of On-duration Time offset4 should be greater than the time-gap with X [slot/symbol].

3GPP TSG RAN WG1 #120bis		R1-2502377
Wuhan, Hubei, China, April 7th – 11th, 2025
Agenda item:	9.6.3
Source:	Samsung
Title:	Discussion on LP-WUS operation in CONNECTED modes
Document for:	Discussion and Decision

Conclusion
The proposals made in this contribution are summarized below: 

Proposal 1: For Option 1-1:
Support a configurable value of Z by RRC;
A UE assumes the same indication by LP-WUS in the Z MOs.

Proposal 2: For Option 1-2:
Support one or multiple (denoted by Z) MOs per periodicity;
Support a configurable value of Z by RRC;
Support a configurable time interval between two consecutive MOs by RRC;
A UE assumes the same indication by LP-WUS in the Z MOs;
The UE expects the time offset4 is no less than the minimum wake-up delay;
The UE may not need to monitor MOs within the time offset4 after the reception of LP-WUS indicating wake-up.

Proposal 3: For the time gap between LP-WUS reception and MR to start PDCCH monitoring:
Support two set of minimum gaps (i.e., X=2) per SCS and per LP-WUR type;
Candidate values for the indicated preferred gap value by UAI shall be same as the candidate values for the UE capability reporting.

Proposal 4: For QCL source of LP-WUS:
If a dynamic adaptation of the QCL source for LP-WUS is not needed, the QCL source for LP-WUS can be provided to the UE as part of the configuration for LP-WUS;
If a dynamic adaptation of the QCL source for LP-WUS is needed, the QCL source for LP-WUS can follow the latest indication by DCI format using the existing TCI framework.

Proposal 5: For CA with two DRX groups:
LP-WUS can be configured on a serving cell for both Option 1-1 and Option 1-2;
For Option 1-1, LP-WUS carries separate indications for each DRX group(s) to trigger PDCCH monitoring of all serving cells;
For Option 1-2, LP-WUS carries a single indication to trigger PDCCH monitoring of all serving cells.

TDoc file reading error

3GPP TSG RAN WG1 #120bis			                  R1-2502483
Wuhan, China, April 7th – 11th, 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,
time offset2 is the same as ps-offset or can be configured as a separate value.
a number of consecutive slots that MO lasts per periodicity can be introduced to define Z.
Proposal #2: For LP-WUS MOs in connected mode for Option 1-2,
multiple MOs per periodicity should be considered for scheduling flexibility.
time offset4 is defined as the time gap between the reference MO and the starting of new timer.
Proposal #3: 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 #4: Support that the UE reports two values on the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring.
Different values are selected for OOK-based WUR and OFDM-based WUR.
Proposal #5: For LP-WUS monitoring in RRC CONNECTED mode, support separate indication/configuration for QCL source of LP-WUS
Re-use existing TCI-state framework to indicate TCI state of LP-WUS.
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: For the case when UE is configured with NR-DC and/or CA with dual DRX groups in RRC CONNECTED mode, 
LP-WUS is configured on a serving cell per cell-group (not per DRX group).
LP-WUS indication is applicable to all activated serving cells in the cell-group.
Proposal #7: When LP-WUS is configured with Cell DTX, discuss whether the UE is expected to monitor LP-WUS during Cell DTX inactive period by considering whether the time while the new timer is running is included in cell DTX active period or not.
Proposal #8: Support UE fallback to PDCCH monitoring, 
when the channel quality for a certain time duration and/or a certain number of times is below the threshold.
when the UE does not receive LP-WUS for a certain time duration.
Proposal #9: Do not support UE fallback by implementation without any condition and additional implicit/explicit indication from UE when it falls back.

3GPP TSG RAN WG1 Meeting #120bis			    			             R1-2502517
Wuhan, China, April 7th – 11th, 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: It is proposed to support only duty-cycled monitoring mode for LP-WUS in Rel-19.
Proposal 2: For the purpose of future discussions, RAN1 assumes at least the following
For RRC connected mode,
LP-WUR and MR cannot support simultaneous operation at a given time instance.
FFS: additional considerations for simultaneous operation between LP-WUR and MR
Proposal 3: For UE capability report on the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring
For the X = 2 candidate values for the UE capability report on the minimum time gap for each SCS, consider {0.25, 0.5, 1, 2, 3, 6, 10, 20, 30, 40}ms
Support different candidate values per SCS
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 4: It is proposed to configure the QCL source in advance as in Opt1, as part of the LP-WUS configuration.
Opt1: Separate indication/configuration for QCL source of LP-WUS
Proposal 5: It is proposed to support the use of PDCCH skipping and monitoring adaptation mechanisms as a means to trigger LP-WUS monitoring for the UE. The following two options can be considered:
Option 1: Utilize the reserved ‘11’ value of the 2-bit PDCCH monitoring adaptation field in the DCI as an explicit indication for the UE to terminate the DRX active time and transition to the sleep state for LP-WUS monitoring.
Option 2: Support an approach where the existing PDCCH skipping mechanism is utilized to indicate the UE to start LP-WUS monitoring without terminating the DRX active time. In this case, the UE may perform LP-WUS monitoring during the skipping duration and return to PDCCH monitoring upon LP-WUS detection.
Proposal 6: It is proposed to apply the conclusion that uplink transmissions such as SR, PRACH, and CG-PUSCH trigger MR PDCCH monitoring by deactivating LP-WUS monitoring to both Option 1-1 and Option 1-2.
Proposal 7: 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.
Proposal 8: 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.
FFS for detail mechanism
Proposal 9: 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 10: It is proposed to adopt Option 3 for the CA with dual DRX groups case.
Opt.3
LP-WUS can be configured on a serving cell 
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

3GPP TSG RAN WG1 #120bis				                                                                       R1-2502576
Wuhan, China, April 7th – 11th, 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 observation.
Observation 1: For the minimum time gap needed for different sleep states, it can be indicated by UAI.
Observation 2: The current agreement implies that LP-WUS monitoring can be deactivated based on C-DRX timers.
It is proposed that
Proposal 1: Two candidate values, i.e., X=2, can be the baseline. 
Proposal 2: The preference offset indicated by UAI is not smaller than the value reported by UE capability signaling. 
Proposal 3: 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 4: the value of X should be satisfied with the minimum time gap reported by UE capability signaling and the time offset between the end of LP-WUS reception and the start of PDCCH monitoring indicated by gNB (if the preference offset is indicated by UAI).
Proposal 5: For option 1-1, the value of Z can be one or multiple.
Proposal 6: For option 1-2, one or multiple LP-WUS MO(s) can be configured within a periodicity of LP-WUS.
Proposal 7: For option 1-2, the value of time offset4 should be satisfied with the minimum time gap reported by UE capability signaling and the time offset between the end of LP-WUS reception and the start of PDCCH monitoring indicated by gNB (if the preference offset is indicated by UAI).
Proposal 8: For option 1-2, the existing timer (e.g., drx-onDurationTimer or drx-InactivityTimer) duration can be used for the length of the new timer.
Proposal 9: For Option 1-2, support that SR, PRACH and CG-PUSCH triggers MR PDCCH monitoring according to the legacy UE behavior.
Proposal 10: 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 11: When Cell DTX is configured and activated, UE monitors LP-WUS during the active time of cell DTX (i.e., celldtxdrx-onDurationTimer) and does not monitor LP-WUS during the non-active time of Cell DTX.

3GPP TSG RAN WG1 #120bis							   R1-2502617
Wuhan, China, April 7th – 11th, 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: 
LP-WUS monitoring occasions
Observation 1: Z is important to determine the FAR probability and should be jointly considered with the number of codepoint a UE monitors as well as the UE grouping.
Proposal 1: Z is configured in the LP-WUS MO configuration, if not configured, UE monitors all the LP-WUS MO at or after Time offset2 until the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. 
Proposal 2: For Option 1-2, support configuring multiple LP-WUS MOs in one periodicity, which can be consecutive in time domain.
Proposal 3: Offset 3 is the starting slot of the first MO in a periodicity, offset 4 indicates the time gap of the last MO and the start of the new timer triggered by LP-WUS. 

QCL source of LP-WUS 
Proposal 4: Support Option 1: Separate indication/configuration for QCL source of LP-WUS. 

LP-WUS operation with CA/DC
Proposal 5: LP-WUS can be configured in only one cell group when DC is configured. Configuring LP-WUS on both cell groups is subject to another UE capability. 
Proposal 6: For LP-WUS Option 1-2 when UE is configured with dual DRX group, consider the following three alternatives: 
Alt 1: Similar to legacy C-DRX with dual DRX group, the same periodicity and starting offset is configured for the LP-WUS triggered new timer, while the duration can be different. 
Alt 2: The same LP-WUS triggered timer is applied on both DRX groups.
Alt 3: LP-WUS Option 1-2 is not supported with CA with dual DRX group. 
Proposal 7: Support monitoring LP-WUS in only one serving cell when dual DRX group is configured.
Proposal 8: Support UE monitoring LP-WUS in SpCells.
Proposal 9: Support Option 1 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
LP-WUS can be configured on a serving cell per cell-group
LP-WUS carries separate indications for each DRX group(s) to trigger PDCCH monitoring of all serving cells
A UE monitors 2 codepoints for triggering dual DRX group, details FFS
Alt 1: One codepoint indicates triggering of a UE’s 1st DRX group, the other indicates triggering of the 2nd DRX group
Alt 2: One codepoint indicates triggering of the UE’s 1st DRX group/DRX group with PCell/DRX group with LP-WUS, the other codepoint indicates triggering of both DRX groups. 

Minimum time gap
Proposal 10: Consider X = 3 candidate values for the UE capability report on the minimum time gap for each SCS, consider the following options: 
Option 1: {6, 13, 33}ms;
Option 2: {6, 20, 40}ms.
Proposal 11: For the preferred configured time offset between LP-WUS and PDCCH reception using UAI mechanism, it is up to UE to report a larger or a smaller value than that reported by UE capability.  

Coexistence with cell DTX
Proposal 11: During Cell DTX non-active period, UE is not expected to monitor LP-WUS. 
Proposal 12: UE does not expect the case when all LP-WUS MOs are configured within cell DTX non-active period.

UE fallback behavior
Proposal 13: Support UE fall back to PDCCH monitoring:
For Option 1-1, UE falls back to legacy C-DRX behaviors
For Option 1-2, the following alternatives can be considered: 
Alt 1: UE falls back to C-DRX behavior, and indicates the fallback state to NW
Alt 2: UE falls back to PDCCH monitoring in the duration defined by the LP-WUS triggered new timer

 

3GPP TSG RAN WG1 #120bis			                                     R1-2502677
Wuhan, China, April 7th – 11th, 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: Confirm the working assumption on using codepoint-based LP-WUS information for connected UE.
Proposal 2: The basic UE capability is to detect at least 2 codepoints per MO.
Proposal 3: Support LP-WUS resource configured in PCell when UE is configured with CA.
Proposal 4: Support Option 1, which provides separate indications for one or more serving cells within an LP-WUS.
Proposal 5: Support timer-based LP-WUS monitoring activation and deactivation for UEs in connected mode. 

3GPP TSG RAN WG1 Meeting #120-bis	R1-2502713
Wuhan, China, April 7th – 11th, 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 observations and proposals are provided:
Observation 1: The UE’s active state takes priority, effectively bypassing LP-WUS whenever primary communications or measurements are ongoing, thus preventing conflicts or interference.

Proposal 1: The specification should clearly mandate that LP-WUS monitoring is skipped whenever the main receiver is active, ensuring the low-power receiver never disrupts primary operations while preserving maximum power-saving benefits.

Observation 2: The fallback requirement is most critical for Option 1-2, especially 1-2-2, where the UE otherwise relies solely on LP-WUS. Clear UE/network signaling of wake-up timing constraints helps ensure reliability.

Proposal 2: RAN1 further discuss and decide the following:
A periodic PDCCH check if the UE relies solely on WUS (e.g., Option 1-2-2), configured via RRC. 
Explicit UE capability/advisory signals about fallback needs and acceptable timings.
A parallel DRX onDuration as safety net for scenarios demanding higher reliability.


Observation 3: Dual/multiple-group scenarios necessitate flexible LP-WUS configurations (e.g., one WUS per DRX group), yet simplicity in signaling and consideration of UE capability (single vs. multiple WUS monitoring) remain key factors.

Proposal 3: RAN1 to further discuss and decide the following:
Use one LP-WUS per DRX domain, typically on the PCell for single-group scenarios.
In dual-group setup, configure separate WUS per group to reduce unnecessary wake-ups.
Define a UE capability bit for multiple simultaneous WUS monitoring, ensuring that UEs lacking this feature only receive a single WUS configuration.

Observation 4: Overlaps with UL or DL transmissions can block WUS reception, but existing awake states or exclusion windows help mitigate these conflicts.

Proposal 4: Establish clear scheduling restrictions, guard intervals, and priority rules to ensure LP-WUS does not interfere with essential UL or DL operations. If overlaps occur, prioritize normal NR procedures; skip or postpone WUS and rely on fallback as necessary, thereby preserving network reliability and power-saving benefits.

3GPP TSG RAN WG1 #120bis			R1-2502775
Wuhan, China, April 7th – 11th, 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:
For LP-WUS in RRC CONNECTED mode in Rel-19, following is not supported
Option 1-3: LP-WUS monitoring inside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.
Proposal 2:
For LP-WUS in RRC CONNECTED mode in Rel-19, enhancement of PDCCH skipping is not supported to terminate the DRX active time and start LP-WUS monitoring
Proposal 3:
For RRC CONNECTED mode, the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring
does not include the duration for time/frequency synchronization of MR
does not have different capability for CA
has X=3 candidate values corresponding to {Y+0, Y+6, Y+20} ms, which are defined in the unit of “slots” and scaled with SCS
FFS: common value of Y
Proposal 4: 
For LP-WUS MOs in connected mode for Option 1-1
UE monitors the first Z LP-WUS MO(s) at or after Time offset2. 
Z is one or multiple MOs configured by RRC
UE is not required to monitor LP-WUS during the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. X is given by the minimum time gap reported as UE capability.
Proposal 5: 
For LP-WUS MOs in connected mode for Option 1-2
LP-WUS MOs, including periodicity and time offset3, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s). 
Introduce RRC parameter “Duration” to configure one or multiple MOs per periodicity
UE monitors LP-WUS in the LP-WUS MOs and, if triggered to wake up, starts a new timer for PDCCH monitoring triggered by LP-WUS, after a time offset4. 
The time offset4 configured by the network indicating a time, after which the UE starts PDCCH monitoring via starting the new timer. 
Time offset4 is configured so that the gap between the end of last MO in the duration and the start of new timer is not smaller than the minimum time gap
Proposal 6:
Support TCI framework for CORESET as baseline for LP-WUS:
Rel-15 TCI framework: RRC configured K TCI states and MAC-CE activates one of them
Rel-17 unified TCI framework: The indicated TCI state (to legacy NR DL/UL channels/signals) is also applied to LP-WUS
Proposal 7: 
For the case when UE is configured with CA without dual DRX groups, LP-WUS can be configured on PCell or an activated SCell
For the case when UE is configured with NR-DC with CA without dual DRX groups, LP-WUS can be configured on PCell/PScell or an activated SCell
For the case when UE is configured with NR-DC without CA, LP-WUS can be configured on PCell/PScell
Proposal 8: 
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
LP-WUS can be configured on PCell or an activated SCell per DRX group
LP-WUS indication is applicable to all serving cells in the DRX group 
Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation
For LP-WUS procedure Option 1-2, send LS to RAN2 to ask whether the new timer can be configured per DRX group
Proposal 9: 
Support UE autonomous fallback to PDCCH monitoring when UE monitors LP-WUS
FFS the condition for the fallback
For LP-WUS operation Option 1-1, UE monitors PDCCH during drx-onDurationTimer
For LP-WUS operation Option 1-2, UE monitors PDCCH during drx-onDurationTimer and indicates it to gNB
Proposal 10:
From RAN1 perspective, when LP-WUS monitoring is enabled for RRC CONNECTED mode, it is supported that SR, PRACH and CG-PUSCH triggers MR PDCCH monitoring according to the legacy UE behaviour
Above applies both for Option 1-1 and Option 1-2
Send LS to RAN2 to ask for potential RAN2 spec impact.
Proposal 11:
For RRC CONNECTED mode, when LP-WUS is configured with Cell DTX, irrespective of inside/outside Cell DTX inactive time, the UE is expected to monitor LP-WUS
Proposal 12:
Consider the overlapping handling of PDCCH as baseline for the overlapping handling between LP-WUS reception and existing NR transmission/reception
Proposal 13:
LPWUS_offset_CONNECTED is split into two parameters for Option 1-1 and Option 1-2
Option 1-1: Time_offset_CONNECTED_Option1-1
For LP-WUS operation Option 1-1, the time offset determines the start of LP-WUS monitoring relative to the start of  drx-onDurationTimer.
This parameter shall be configured for LP-WUS operation Option 1-1 in RRC CONNECTED
Option 1-2: Time_offset_CONNECTED_Option1-2
For LP-WUS operation Option 1-2, the time offset determines the start of UE PDCCH monitoring via starting the LPWUS_PDCCHMonitoringTimer after LP-WUS is detected.
This parameter shall be configured for LP-WUS operation Option 1-2 in RRC CONNECTED
Proposal 14:
LPWUS_MO_CONNECTED is split into two parameters for Option 1-1 and Option 1-2
Option 1-1: Time_MO_CONNECTED_Option1-1
Configuration for LP-WUS MOs for Option 1-1, including at least the following: 
Periodicity and time offset1
Number of first MOs where UE monitors LP-WUS at or after Time_offset_CONNECTED_Option1-1.  
This parameter shall be configured for LP-WUS operation Option 1-1 in RRC CONNECTED
Option 1-2: Time_MO_CONNECTED_Option1-2
Configuration for LP-WUS MOs for Option 1-2, including at least the following: 
Periodicity and time offset3. The configured periodicity is no larger than long C-DRX cycle
Duration to configure one or multiple MOs per periodicity
This parameter must be configured for LP-WUS operation option 1-2 in RRC CONNECTED

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502807
Wuhan, China, April 7th – April 11th, 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
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	The number of candidate values for minimum time gap reporting X is 2. 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 5	For Option 1-2, multiple MOs should be configured per periodicity (MO window) for scheduling flexibility.
Proposal 6	Offset4 is an offset indicating a time where the UE starts PDCCH monitoring after the last slot of the MO window in which the UE detects LP-WUS.
Proposal 7	Do not support UE autonomous switching between LP-WUS monitoring and no LP-WUS monitoring without gNB knowledge.
Proposal 8	LP-WUS is configured only on PCell for CA without dual DRX groups and PCell/PSCell for NR-DC with CA without dual DRX groups or without CA in RRC CONNECTED mode.
Proposal 9	Support Option2: Association of QCL source between LP-WUS and PDCCH/CORESET.
Proposal 10	UE is not expected to monitor LP-WUS during Cell DTX active time.

4	

3GPP TSG RAN WG1 Meeting #120bis    	            R1-2502848
Wuhan, China, April 7th – 11th, 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, the Z is an RRC parameter provided by RRC signalling
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 ‘X’ is the minimum time gap reported in the UE capability.

Proposal 2:
For Option 1-2, support RRC parameter providing the value of Z
Z LP-WUS MOs are for triggering the new timer for PDCCH monitoring starting at the same slot
If a UE is configured with Z > 1:
The Z 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 Z LP-WUS MOs.
The time gap from the last LP-WUS MO of the Z LP-WUS MOs associated with a slot where the new timer would start and the slot is not smaller than the minimum time gap ‘X’.

Proposal 3:
Allow a UE to autonomously fallback from LP-WUS monitoring to C-DRX operation in both Option 1-1 and Option 1-2
For Option 1-1, no matter whether the UE monitors the DCP before C-DRX active time or the UE fallbacks to the legacy C-DRX operation, the scheduling DCI within the C-DRX active time is receivable by the UE.
For Option 1-2, network can configure LP-WUS parameters such that the slots where the new MAC timer for PDCCH monitoring would start are in a superset of the slots where the drx-onDurationTimer would start. With this, at least some PDCCH monitoring windows are guaranteed, no matter whether the UE monitors LP-WUS or the UE fallbacks to the legacy C-DRX operation.

Proposal 4:
UE does not 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 CSS sets), or;
the UE is in measurement gap, or etc
For both Option 1-1 and Option 1-2, 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 starts drx-ondurationTimer or the new timer at the slot for PDCCH monitoring

Proposal 5:
Support at least “10ms” as one of the X candidate values that a UE can report in the UE capability for all the SCSs.

Proposal 6:
Allow a UE to report different values of the minimum time gap for OOK-based WUR and OFDM-based WUR
Allow a UE to report different values of the minimum time gap for non-CA and CA

Proposal 7:
Support TCI-state configuration by RRC for LP-WUS
The TCI-state in the LP-WUS configuration indicates one or two DL RSs with the corresponding QCL types.
Support unified TCI framework for LP-WUS
If a UE is configured with dl-OrJointTCI-StateList, the UE obtains the QCL assumptions from a TCI state within the dl-OrJointTCI-StateList
The TCI state from which the UE obtains the QCL assumptions for LP-WUS is the one activated by MAC-CE activation command and is indicated by the codepoint of the DCI field “Transmission Configuration Indication” 

Proposal 8:
For a UE configured with NR-CA without secondary DRX group, LP-WUS can be configured on the PCell to trigger PDCCH monitoring on all the active serving cells.
For a UE configured with NR-CA with secondary DRX group, support following:
LP-WUS can be configured on the PCell to trigger PDCCH monitoring on all the active serving cells in the primary DRX group, and LP-WUS can be configured on an SCell in the secondary DRX group to trigger PDCCH monitoring on all the active serving cells in the secondary DRX-group.
RRC configuration for LP-WUS monitoring shall be provided to a secondary cell in the secondary DRX-group to enable this
FFS: LP-WUS can be configured on the PCell to trigger PDCCH monitoring on all the active serving cells in either or both of the DRX groups. 

Proposal 9:
For NR-CA, specify the minimum time gap as the time gap to wake up multiple active serving cells.
For NR-CA without secondary DRX group, the UE reports the minimum time gap to wake up all the active serving cells.
For NR-CA with secondary DRX group, the UE reports the minimum time gap to wake up all the active serving cells in the DRX group.

Proposal 10:
Introduce MAC-CE for LP-WUS activation/deactivation
A UE can be configured with one or multiple LP-WUS configurations
The MAC-CE activates one (or none) of the LP-WUS configurations dynamically

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502997
Wuhan, China, April 7th – 11th, 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 #120bis	R1-2503055
Wuhan, China, April 7th – 11th, 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 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

3GPP TSG-RAN WG1 Meeting #120bis	R1-2503088
Wuhan, China, April 7th – 11th, 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 and conclusions were made in this meeting:

Agreement
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

Conclusion
From RAN1 perspective, when LP-WUS monitoring Option 1-2 is enabled for RRC CONNECTED mode, it is supported that SR, PRACH and CG-PUSCH triggers PDCCH monitoring according to the legacy UE behaviour


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}

Agreement
Update previous agreement in red:
Agreement
For LP-WUS MOs in connected mode for Option 1-1, support Approach 1:
LP-WUS MOs, including periodicity and time offset1, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
Time offset2 indicates a time prior to a slot where the drx-onDurationTimer would start
UE monitors the first Z LP-WUS MO(s) at or after Time offset2. 
FFS: How to determine the value of Z is RRC configured
Time offset2 is RRC configured
UE is not required to monitor LP-WUS during the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. FFS: How X is determined given based on the minimum time gap reported by UE capability.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2503102
Wuhan, China, April 7th – 11th, 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 and conclusions were made in this meeting:

Agreement
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

Conclusion
From RAN1 perspective, when LP-WUS monitoring Option 1-2 is enabled for RRC CONNECTED mode, it is supported that SR, PRACH and CG-PUSCH triggers PDCCH monitoring according to the legacy UE behaviour


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}

Agreement
Update previous agreement in red:
Agreement
For LP-WUS MOs in connected mode for Option 1-1, support Approach 1:
LP-WUS MOs, including periodicity and time offset1, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
Time offset2 indicates a time prior to a slot where the drx-onDurationTimer would start
UE monitors the first Z LP-WUS MO(s) at or after Time offset2. 
FFS: How to determine the value of Z is RRC configured
Time offset2 is RRC configured
UE is not required to monitor LP-WUS during the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. FFS: How X is determined given based on the minimum time gap reported by UE capability.

Agreement
Update previous agreement in red:
Agreement
For LP-WUS MOs in connected mode for Option 1-2, support Approach 1:
LP-WUS MOs, including a periodicity and a time offset3, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s). 
FFS one or multiple MOs per periodicity
UE is configured with a number of MOs for the periodicity by RRC
UE monitors LP-WUS in the LP-WUS MOs and, if triggered to wake up, starts a new timer for PDCCH monitoring triggered by LP-WUS 
FFS: Definition of time offset4
Alt1:
TheA time offset4 configured by the network indicating a time from the first LP-WUS MO per periodicity, after which the UE starts PDCCH monitoring via starting the new timer.
The time gap from the 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

Agreement
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 {V1=[3,5,6], V2=[10,13,20], V3=[33,42]}ms where V1

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

Agenda Item:	9.6.3

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

Source:	Moderator (NTT DOCOMO)

Document for:	Discussion, Decision

1	

Conclusions
Following agreements and conclusions were made in this meeting:

Agreement
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

Conclusion
From RAN1 perspective, when LP-WUS monitoring Option 1-2 is enabled for RRC CONNECTED mode, it is supported that SR, PRACH and CG-PUSCH triggers PDCCH monitoring according to the legacy UE behaviour


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}

Agreement
Update previous agreement in red:
Agreement
For LP-WUS MOs in connected mode for Option 1-1, support Approach 1:
LP-WUS MOs, including periodicity and time offset1, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
Time offset2 indicates a time prior to a slot where the drx-onDurationTimer would start
UE monitors the first Z LP-WUS MO(s) at or after Time offset2. 
FFS: How to determine the value of Z is RRC configured
Time offset2 is RRC configured
UE is not required to monitor LP-WUS during the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. FFS: How X is determined given based on the minimum time gap reported by UE capability.

Agreement
Update previous agreement in red:
Agreement
For LP-WUS MOs in connected mode for Option 1-2, support Approach 1:
LP-WUS MOs, including a periodicity and a time offset3, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s). 
FFS one or multiple MOs per periodicity
UE is configured with a number of MOs for the periodicity by RRC
UE monitors LP-WUS in the LP-WUS MOs and, if triggered to wake up, starts a new timer for PDCCH monitoring triggered by LP-WUS 
FFS: Definition of time offset4
Alt1:
TheA time offset4 configured by the network indicating a time from the first LP-WUS MO per periodicity, after which the UE starts PDCCH monitoring via starting the new timer.
The time gap from the 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

Agreement
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 {V1=[3,5,6], V2=[10,13,20], V3=[33,42]}ms where V1

3GPP TSG-RAN WG1 Meeting #120bis	R1-2503121
Wuhan, China, April 7th – 11th, 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 and conclusions were made in this meeting:

Agreement
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

Conclusion
From RAN1 perspective, when LP-WUS monitoring Option 1-2 is enabled for RRC CONNECTED mode, it is supported that SR, PRACH and CG-PUSCH triggers PDCCH monitoring according to the legacy UE behaviour


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}

Agreement
Update previous agreement in red:
Agreement
For LP-WUS MOs in connected mode for Option 1-1, support Approach 1:
LP-WUS MOs, including periodicity and time offset1, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
Time offset2 indicates a time prior to a slot where the drx-onDurationTimer would start
UE monitors the first Z LP-WUS MO(s) at or after Time offset2. 
FFS: How to determine the value of Z is RRC configured
Time offset2 is RRC configured
UE is not required to monitor LP-WUS during the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. FFS: How X is determined given based on the minimum time gap reported by UE capability.

Agreement
Update previous agreement in red:
Agreement
For LP-WUS MOs in connected mode for Option 1-2, support Approach 1:
LP-WUS MOs, including a periodicity and a time offset3, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s). 
FFS one or multiple MOs per periodicity
UE is configured with a number of MOs for the periodicity by RRC
UE monitors LP-WUS in the LP-WUS MOs and, if triggered to wake up, starts a new timer for PDCCH monitoring triggered by LP-WUS 
FFS: Definition of time offset4
Alt1:
TheA time offset4 configured by the network indicating a time from the first LP-WUS MO per periodicity, after which the UE starts PDCCH monitoring via starting the new timer.
The time gap from the 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

Agreement
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 {V1=[3,5,6], V2=[10,13,20], V3=[33,42]}ms where V1