3GPP TSG RAN WG1 Meeting #121	R1-2503228
St. Julian’s, Malta, May 19 – 23, 2025
Agenda Item:	9.6.1
Source:	Futurewei
Title:	Remaining Issues on LP-WUS and LP-SS Design
Document for:	Discussion/Decision 

Conclusion
This contribution discusses the remaining issues on LP-WUS and LP-SS designs. The following summarizes our observations and proposals.
Observation 1: The LP-WUS waveform at M=4 and 30 kHz SCS can tolerate timing errors up to 2μs, i.e., <1 dB error, with RM coded bits length>12bits. A RM coded bits length=12bits may not tolerate timing error of 1μs.
Proposal 1: Confirm the working assumption that a LP-WUR-enabled UE supports OOK-4 based LP-WUS design with M=4 for 30kHz SCS.
Proposal 2: Confirm the RAN1#118b working assumption that for OOK-1 and OOK-4 M=1, the overlaid sequence(s) are the sequence(s) of an OOK on symbol before DFT/LS processing, with the removal of “DFT size is 2^n” based on RAN1#120b agreement.
Observation 2: A coded bits length of 10 bits may be needed to satisfy the 1% FAR target with 2 monitored codepoints and ≤4 LP-WUS monitoring occasions. Further, a coded bits length>12bits may be needed to tolerate timing error of 1μs at M=4 and 30kHz SCS.
Proposal 3: For > 2 information bits with RM coding, support a minimum coded bits length after rate matching of 12 bits considering up to 4 candidate LP-WUS monitoring occasions per beam and LP-WUS timing error tolerance at M=4 and 30kHz SCS.
Observation 3: For -3dB target SNR, a coded bits length of 64 and 128 bits may be needed for M=2 and M=4, respectively, at 30kHz SCS.
Observation 4: Only coded bits length of 32 bits is needed for maximum Hamming distance between codewords. Codeword repetition for envelope detection receiver provides approximately the same 2 dB performance improvement as doubling the coded bits length.
Observation 5: Although incrementally increasing coded bits length ∈[12:32] provides very fine granularity for performance improvement, a limited subset of coded bits lengths can simplify LP-WUR while providing sufficient performance improvement granularity.
Proposal 4: Support 32 bits as the upper bound on coded bits length with repetition after rate matching, and the coded bits length being any of {12, 16, 20, 24, 28, 32}.
Proposal 5: Support Alt 1 for code block length determination in a MO which can be derived as N_rep×L_base for L_base as maximum value ∈{12,16,20,24,28,32} which is≤floor[M×N_ofdm/(2N_rep)], N_ofdm as a determined number of available OFDM symbols per the MO, and N_rep as a configured number of repetitions.
Proposal 6: Confirm RAN1#120 working assumption that the maximum number of codepoints checked per MO by a UE is up to 8 in RRC connected mode.
Proposal 7: For RRC idle/inactive mode only, the number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip. RRC connected mode has no such restriction.
Proposal 8: Do not support the candidate set of overlaid sequences changing across OOK ON chips to limit the complexity of the OFDM LR.
Observation 6: The support of 2 roots for the overlaid OFDM sequences can allow sliding window detection for the OFDM LR using 2 or 4 samples at the minimum sampling frequency of 1.98MHz and 3.96MHz for 15kHz and 30kHz SCS, respectively.
Proposal 9: Confirm RAN1#120b working assumption that supports a maximum of 2 roots to be used for overlaid OFDM sequences for M=1/2/4 at least for FR1.
Proposal 10: Support indexing of overlaid OFDM sequences in increasing order of cyclic shift index l and root value index n_root as (n_root×N_CS +l) where N_CS=N_seq/N_root is number of cyclic shifts based on configured number of candidate sequences N_seq and roots N_root.
Proposal 11: Support an M value for LP-SS larger than the M value for LP-WUS even if M=1 is configured for LP-WUS for the better time sync performance and/or resource overhead.
Proposal 12: Support the UE assuming modulus ones sequence is used for the generation of the OOK ON symbol only for LP-SS with M=1.
Proposal 13: Support derivation of root values for LP-SS overlaid OFDM sequences as floor(q_wus × M_WUS/M_LPSS) with M value for LP-SS (M_LPSS)≥ M value for LP-WUS (M_WUS) and LP-WUS overlaid OFDM sequences root values q_wus≤121 when M_WUS=1.

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

Agenda Item:	9.6.1
Source:	Huawei, HiSilicon
Title:	Signal Design of LP-WUS and LP-SS
Document for:	Discussion and Decision 

Conclusions
In this contribution, the design of LP-WUS and LP-SS are discussed. The following observations and proposals are made:

Retuning is not an issue for any type of UE if LP-WUS/LP-SS and SSB are confined within the same carrier.
Measurement misalignment is not an issue if LP-WUS/LP-SS and SSB are confined within the same carrier.
Based on the property of ZC sequence
If timing error is smaller than half of the minimum cyclic shift, ZC sequences with the same root but different cyclic shift is the best choice because of smaller cross-correlation.
If timing error is larger than half of the minimum cyclic shift, ZC sequences with the different roots may be the best choice
To meet the requirements of MDR and FAR:
20 OFDM symbols are needed when M=1
10 OFDM symbols are needed when M=2
8 OFDM symbols are needed when M=4
Repetition after rate matching is not needed.
To follow the agreed code scheme, and to avoid the case where minimum Hamming distance between code blocks is 0, the minimum value of code block length should at least be:
1,  for 1 information bit case
2,  for 2 information bit case
3,  for 3 information bit case
5,  for 4 information bit case
6,  for 5 information bit case
To avoid too much complexity, a common minimum value of code block length is preferred.
For LP-SS, using different roots of ZC sequences on different OOK "on" symbols can improve receiving performance.
If the periodicity of LP-SS is larger than 1280ms, the latency of obtaining RRM measurement results may be too large, which may restrict the UE max moving speed.
To support the functionality of falling back to MR and avoid too large latency of paging, the periodicity of LP-SS cannot be larger than 320ms.
The requirement of periodicity is usually dominated by the time error, where the residual frequency error contributes most of the time error.
To support the functionality of synchronization by periodic LP-SS only, the configured periodicity of LP-SS equal to 160ms is enough for OOK4 M=4.
Introducing preamble in addition to periodic LP-SS will increase the resource overhead.


For OOK-4, confirm the working assumption of M=4 for 30kHz SCS.
No need to define additional restriction on the maximum frequency gap between LP-WUS/LP-SS and SSB.
In order to reduce resource overhead, transmission duration of a LP-WUS targeting to wake up OFDM-based receiver can be shorter than the transmission duration required for ED based receiver.
For WUS information carried by the overlaid OFDM sequence(s), raw information bits are mapped to sequence(s), in case N/log2L is not an integer, Bit 0 as LSB is used for padding.
Confirm the WA with following changes.
At least for FR1, support maximum 2 roots to be used for overlaid OFDM sequences for M=1/2/4 in each cell (max 2 for each M value). 
Different roots can be picked for different M values.
The same set of candidate overlaid sequence across OOK ON chips is used for one cell (IDLE/INACTIVE mode) or one UE (CONNECTED mode).
For the DFT operation used to generate the LP - WUS signal, the DC component needs to be mapped to the center position.
Code block (coded bits) length is 6~32, and repetition after rate matching is not needed.
The code block length is determined based on the configured resources (e.g., OFDM symbols) for LP - WUS/MO, to avoid a LP-WUS occupying non-integer number of OFDM symbols.
For transmit LP-SS in the case of OOK-1, revisit the previous agreement and down-selection form the following:
Alt1: Whether to transmit LP-SS by using a specified overlaid OFDM sequence is not configurable.
Alt2: Do not support the case of OOK-1 for LP-SS.
Separate power offset can be configured for LP-WUS and LP-SS, where different power offset value can only be configured for the case that one of LP-WUS/LP-SS uses M=1 and the other one uses M>1.
The M values for LP-SS can be configured as 2 or 4 if M value for LP-WUS is 1. All UEs shall support any M value combination for LP-WUS and LP-SS.
For LP-SS periodicity, to support the functionality of RRM measurement by LP-WUR and the functionality of fallback operation, values larger than 320ms are NOT supported.
For LP-SS periodicity and preamble, additionally support 160ms and does not support preamble in the case of OOK-4 M=4.
The following parameters are specified to configure the overlaid OFDM sequence(s), and they are configured independently in IDLE/INACTIVE mode and CONNECTED mode
Number of candidate sequence(s), L1
The value(s) of root(s)

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

Source: 	ZTE Corporation, Sanechips
Title:	Discussion on LP-WUS design
Agenda item: 	9.6.1
Document for:	Discussion and decision

Conclusions 
In this contribution, we have discussed issues on waveform design and signal structure for LP-WUS. We make the following observations and proposals:
Observation 1: Without additional sync signal, only for the case of LP-SS periodicity with 80ms and residual frequency error=5ppm, the total TO before LP-WUS detection can meet the TO requirement of LP-WUS with M=4.
Observation 2: In low paging rate scenarios which is more practical for LP-WUS deployment, additional sync signal can provide obvious less overhead than smaller LP-SS periodicity.
Observation 3: Additional sync signal has more flexibility for gNB and provide better sync performance for LP-WUS reception.
Observation 4: Additional sync signal actually is kind of on-demand LP-SS which can help NW save more overhead.
Observation 5: For OFDM sequence based LR, output sequence length after LP-WUS information bits rate matching should be large enough to ensure its detection performance.
Observation 6: From OOK based LR point of view, the overlaid sequence and specified OFDM sequence carried by OOK-ON symbols have the same benefit on improving LP-WUS detection performance. 
Observation 7: If UE knows the characteristics of OOK waveform transmitted by the gNB in advance, it can help the UE to properly configure related parameters of the envelope detector to improve the envelope detection performance. 
Observation 8: OOK waveform generation with constant modulus feature is helpful for OOK based envelope detection performance.

Proposal 1: For OOK-4 with M >1, support M=4 with 30KHz SCS for LP-WUS.
Proposal 2: Support additional sync signal by reusing the LP-SS binary sequence, i.e., M value and sequence are the same as LP-SS
The additional sync signal is located on one nearest DL slot before the LO
Proposal 3: For > 2 information bits with RM coding, candidate code block (coded bits) length after rate matching is within the range of [6~64], and the code block length is selected as following:
Proposal 4: For OFDM sequence based LP-WUS information transmission, the overlaid sequences should be transmitted on all OOK-ON symbols which are used for OOK based LP-WUS transmission.
Proposal 5:For the generation of overlaid ZC sequence for LP-WUS, , 
Wherein, ,  Ncs is generated by the following formula:

Wherein,  is the configured ZC sequence number,  is the configured ZC sequence root number.
Proposal 6: For the case of no LP-WUS information carried by overlaid ZC sequence, a separate ZC sequence configuration including only root index is indicated by high layer signalling and used for OOK based LP-WUS transmission.
Proposal 7: LP-SS reuses the overlaid OFDM sequence(s) specified for LP-WUS only when the value of M are the same for both of them and a specific ZC sequence index from the configured overlaid OFDM sequence set should be indicated by high layer signalling. Otherwise, a separate ZC sequences configuration including only root index should be configured for LP-SS.
Proposal 8: For LP-SS with M=1, in case of the overlaid OFDM sequence is not configured, at least constant modulus feature should be satisfied for the generation of OOK waveform.

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

Source:	vivo
Title:	Remaining issues on LP-WUS and LP-SS design 
Agenda Item:	9.6.1
Document for:	Discussion and Decision

Conclusion
In this contribution, we provide our views on LP-WUS and LP-SS design aspects. The observations and proposals are summarized as follows.  
Observation 1: The number of overlaid sequences applicable for a UE per OOK ON chip is determined by the number of codepoints to be monitored by a UE, thus no need of separate discussion.  
Observation 2: There is no clear benefit of candidate set of overlaid sequences changing across OOK ON chips, while it increases gNB/UE complexity as well as standard effort. 
Observation 3: For both RRC connected and RRC idle/inactive state, supporting LP-WUS transmission only targeting OFDM receiver can be beneficial to reduce resource overhead. 
Observation 4: There is no need of specified DFT shift operation for LP-WUS/LP-SS signal generation.
Observation 5:With up to 5ppm frequency error,synchronization accuracy is almost indentical for single root and two roots case. 
Observation 6:  There is no need to support additional sync for LP-WUS with M=4 case. 
Proposal 1: For LP-WUS/LP-SS frequency resource configuration, PRB offset with reference to carrier boundary determined by offsetToCarrier corresponding to SCS of the active BWP or DL initial BWP is configured by gNB, with range of 0~ 263.
Proposal 2: For candidate M values,  
For FR1: Confirm the working assumption for M=4 with 30kHz SCS as optional feature. 
For FR2: Support only M=1 for LP-WUS and LP-SS. 
 Proposal 3:.   For LP-WUS information carried by OOK, 
For 1 &2 information bits, confirm the working assumption for coding. 
For 1 ~ 5 information bits, support candidate code block (coded bits) length after rate matching in the range of 1~32 bit and 64 bit for all M values by the specification. gNB can configure any proper length within the range. 
There is no further repetitin after rate matching. 
Proposal 4: For the number of candidates overlaid sequences per OOK ON chip for one cell, the minimum number is 2. 
Proposal 5: For LP-WUS overlaid OFDM sequence configuration in a cell, 
gNB configures number of sequences N1 (2n, where n=1,2,… 4), number of roots N2 and root index(s) (range:1 ~ Bzc-1）. 
The number of CS is derived by N1/N2. CS value , v=0,1,.. N1/N2-1, is the largest prime number no larger than sequence length .
N1 sequences are enumerated in increasing order of first increasing cyclic shift of first root sequence, and then in increasing order of the root sequence index in case of N2>1.
Proposal 6: Support LP-WUS targeting OFDM receiver only. 
The LP-WUS transmission is determined by the information bits without channel coding, number of overlaid OFDM sequences per OOK ON chip and the repetition factor, without dependency of OOK ON-OFF pattern targeting OOK receiver. 
Proposal 7: For repetition of overlaid OFDM sequence(s), 
Support block-level repetition for overlaid OFDM sequences, where one block carry whole information bits. 
gNB configures repetition factor of overlaid OFDM sequence. 
Proposal 8: If M=1 is configured for either of LP-WUS or LP-SS, the M values for LP-WUS and LP-SS can be configured to be same or different. M value for LP-WUS cannot be larger than that of LP-SS.  
Proposal 9: For LP-SS with specified overlaid OFDM sequence, gNB configures root value for overlaid OFDM sequence assuming default cyclic shift value =0. 
Proposal 10: RAN1 to discuss how to specify OOK generation, when LP-SS is not configured with specified overlaid OFDM sequence. 

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

Agenda Item:	9.6.1
Source:	Spreadtrum, UNISOC
Title: 	Discussion on LP-WUS and LP-SS design
Document for:	Discussion and decision

Conclusion
We have the following proposals.
Proposal 1: Number of roots N2 and root index(s) can be configurable by the network.
Proposal 2: The number of CS and corresponding cyclic shift value is derived by the number of sequences and number of roots.
Proposal 3: There is no need to introduce additional sync signal for LP-WUS with M=4.
Proposal 4: If M=1 is configured for either of LP-WUS or LP-SS, M=1 is configured for both.
Proposal 5: for LP-WUS/LP-SS frequency resource configuration, PRB offset with reference to carrier boundary determined by offsetToCarrier corresponding to SCS of the active BWP or legacy DL initial BWP is configured by gNB.

3GPP TSG RAN WG1 #121		R1-2503573
St Julian's, Malta, May 19th – 23th, 2025
Agenda item:	9.6.1
Source:	Samsung
Title:	Discussion on LP-WUS and LP-SS design
Document for:	Discussion and Decision

Conclusion
The proposals and observation made in this contribution are summarized below:
Observation 1: If overlaid OFDM sequences over OOK symbol are specified, OOK-based LP-WUS can be detected either by envelope detection or correlation with OFDM sequence according to the type of LP-WUR.
Observation 2: If multiple candidates of OFDM sequences are specified to be overlaid by ON pulse of OOK symbol, it is beneficial for OFDM-based LP-WUR to reduce the power consumption of LP-WUS monitoring.
Proposal 1: For LP-WUS/LP-SS frequency resource configuration, PRB offset with reference to carrier boundary determined by offsetToCarrier corresponding to SCS of LP-WUS/LP-SS is configured by the gNB.
If LP-SS transmission is configured, frequency position for LP-WUS and LP-SS is configured by the same PRB offset parameter.
Proposal 2: For LP-WUS with M=1, support configuring M values for LP-SS to be same or different.
Proposal 3: Consider limiting M value for 60kHz/120kHz to have the same maximum OOK chip rate with 15kHz/30kHz SCSs case (i.e., M =1, 2 for 60kHz SCS, M = 1 for 120kHz SCS).
Proposal 4: Confirm the working assumption related to codepoint-based LP-WUS for RRC CONNECTED mode with the following modification:
Delete “Depending on UE capability, a UE may support less than 8.”
Add “Codepoint value set to be checked by a UE can be configured by the gNB.”
Proposal 5: Codepoint value is defined as the information bits/raw information bits to generate OOK-based and OFDM-based LP-WUS.
Proposal 6: The subset of code block lengths after rate matching should be supported considering the following:
The number of OFDM symbols for a LP-WUS transmission after rate matching and Manchester coding should be the integer value (i.e., the number of OOK symbols after Manchester coding mod M should be zero).
Proposal 7: To determine the code block length after rate matching for each M value, the following alternatives can be considered:
Alt. 1: The different subset for the code block length is explicitly specified for each M value.
Alt. 2: The same number of OFDM symbols are configured for a LP-WUS transmission regardless of M values. The code block length after rate matching can be implicitly derived from the number of OFDM symbols.
Proposal 8: Do not support the additional repetition after rate matching.
Repetition by rate matching is sufficient for intra-MO repetition.
Proposal 9: The number of information bits per OOK ON symbol (N1), the number of roots(N2), and root index(s) are configured by the gNB.
The number of cyclic shift ((2N1)/N2) and corresponding cyclic shift values can be derived implicitly.
The single candidate set for overlaid OFDM sequence is applied across OOK ON symbol for a LP-WUS.
If the number of information bits per OOK ON symbol is 0 (N1=0), the single overlaid OFDM sequence is configured for each OOK ON symbol (not carrying information case).
Proposal 10: Support repetition of overlaid OFDM sequence.
The repetition factor (R) is configured by the gNB.
The monitoring window for OFDM-based LP-WUS can be determined based on the configured repetition factor (R) and the number of segments (K).
Proposal 11: For the LP-SS binary sequence used in a cell, additional support of sequence determination by predefined rule is not needed.
Proposal 12: For LP-WUS M=4 case, support Option 1A with additional support for 160ms LP-SS periodicity (same option with M=1 and M=2 LP-WUS cases).

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

Agenda Item:	9.6.1
Source:	TCL  
Title:	LP-WUS and LP-SS Design
Document for:	Discussion and Decision 

Conclusion
In this contribution, we discussed the necessary information included in the LP-SS, LP-WUS for connected and idle/inactive UE, and made the following observations and proposals.
Observation 1: The UE uses the LP-SS for synchronization and needs to identify the cell which transmits the LP-SS by its cell ID.
Proposal 1: RAN1 to consider including the physical cell ID (PCI) into the LP-SS signal.
Proposal 2: Support the following working assumption: 

Proposal 3: For the LP-WUS information used to trigger PDCCH monitoring for RRC connected UEs, to support the checking of up to 8 codepoints in a MO, the association/mapping between the codepoints in an LP-WUS and the MOs is configured to the UEs.
Proposal 4: Consider a frequency gap between the LP-SS/LP-WUS and the SSB, defined in terms of RB-offset between the LP-SS/LP-WUS and the SSB. 
Proposal 5: For the maximum frequency gap between the LP-SS/LP-WUS and the SSB, consider a maximum RB-offset of 20 RBs. 

3GPP TSG RAN WG1 #121	R1- 2503694
Valetta, Malta, May 19th – May 23rd, 2025
Agenda item: 		9.6.1
Title:			LP-WUS and LP-SS design
Source: 			Nokia
Document for: 		Discussion and Decision

Conclusion
In this document, we presented our initial thoughts on the WI scope and the topics that are relevant to be considered and discussed during the WI phase.
List of Proposals
Proposal 1:	The edge-to-edge separation between LP-WUS/LP-SS and SSB in frequency shall be restricted within  to ensure similar channel conditions.
Proposal 2:	RAN1 shall consider DC centering after DFT processing before mapping the LP-WUS samples to frequency domain REs.
Proposal 3:	As unified signal design is preferred to minimize the specification impact, pulse shaping for  shall not be considered, since in RAN1#119 it was agreed that  does not.
Proposal 4:	RAN1 shall consider repeating the overlay sequence(s) based on the same information bits used to generate the underlying OOK sequence within a MO.
Proposal 5:	RAN1 shall consider at least 4 root sequences for overlaid OFDM sequences to ensure sufficient tolerance margin for LR impairments.
Proposal 6:	RAN1 shall consider LP-WUS codeword sizes of [7,11,15,19,20,23,25,27,29,31] bits that provides better Hamming distance while considering all information sizes.
Proposal 7:	RAN1 shall consider LP-SS M to be either the same or greater than the M value used for LP-WUS, i.e., also for M=1.
Proposal 8:	RAN1 shall deprioritize additional synchronization and instead reuse the LP-SS periodicity that supports 160ms also for M=4.

List of Observations
Observation 1:	As the overlay sequence based on ZC is robust against frequency offset, the frequency separation between LP-WUS/LP-SS and SSB need not be restrictive.
Observation 2:	As SSBs are used for synchronization, RRM, entry, and exit conditions for LP-WUS monitoring, ensuring SSBs and LP-WUS/LP-SS to experience the channel state is necessary for reliability.
Observation 3:	Repeating the same overlay sequence over an MO benefit the IQ receiver to perform combining over multiple OOK symbols depending on the coverage.
Observation 4:	As the overlay sequences derived from fewer roots using cyclic shifts, if the LR cannot decode using first  OFDM symbols, Option1 type detection can be performed.
Observation 5:	As LP-WUS uses transform precoding of ZC sequence before mapping to frequency domain, the cross correlation between different root sequences under frequency offset is not as worse as the one without transform precoding.
Observation 6:	Even with LP-WUS using M=4 can support up to 31 roots, restricting the roots to a maximum of 2 may be too restrictive and can cause false detections if there is any residual timing and/or frequency error in LR due to the gap between SSB and LP-WUS.
Observation 7:	The LP-WUS size depends on the choice of M used for OOK and the number of information bits. The length of LP-WUS shall be chosen such that the Hamming distance increase for a codeword size over the one less for all information bits.
Observation 8:	The LP-WUS codeword size depends on the choice of  and the number of subgroups used.
Observation 9:	LP-SS detection is performed as sequence correlation and not as symbol-by-symbol OOK detection for timing synchronization. Thus, it does not matter what  value used for LP-SS if LR uses a sequence stored as LUT and use it for correlation at a desired sampling rate.
Observation 10:	The detection accuracy can be improved by averaging the timing estimates over multiple LP-SS monitoring occasions, while ensuring the coherency of the channel fading.
Observation 11:	By adopting three timing hypotheses that are separated by half the maximum timing error, the OOK detection performance can be improved without significant degradation compared to ideal.
Observation 12:	The impact of timing error on the OOK detection performance is dB worse than the one without any timing error under the presence of channel coding.

Conclusion 
In this contribution, the following proposals and observations have been made:
Proposal 1: Consider if pulse-shaping is required after sequence design and potential preamble are agreed.
Proposal 2: The DFT-shift is compensated at the LR.
Proposal 3: Confirm working assumption on the support of 1 and 2 information bits for LP-WUS.
Observation 1: For , without repetition, the maximum code word length is 32.
Observation 2: Clarify how repetition of the LP-WUS relates to the potential repetitions of MOs within a beam.
Proposal 4: For , support repetition in the rate-matching procedure for LP-WUS.
Proposal 5: For , the minimum code block length is .
Proposal 6: For , the code block lengths apply to all values of 
Proposal 7: For , all of the code block lengths within the range are supported
Observation 3: with Manchester Coding has the worst coverage compared to .
Proposal 8: For , consider jointly encoding multiple bits into ON pulse position to increase SNR by 3dB.
Observation 4: PAPR increase of Pulse Position Coding for  compared to Manchester encoding depends on the ratio of channel BW to WUS BW and is minor (~0.1dB) for many system configurations.
Proposal 9: Allow configuration of Pulse Position Coding for .
Proposal 10: Confirm working assumption on the number of roots.

3GPP TSG RAN WG1 #121                                                                                            R1-2503800
St Julian’s, Malta, May 19th – 23rd, 2025
Source:            CATT
Title:                 Design of LP-WUS and LP-SS
Agenda Item:   9.6.1
Document for: Discussion and Decision

Conclusion 
In this contribution, we discuss the waveform design and sequence design of LP-WUS and LP-SS and give the following proposals: 
Proposal 1: OOK-4 with M=1 is the DFT-S-OFDM waveform with low PAPR and should be supported.
Proposal 2: The code block length can be configured from the range of 3 ~ 64 bits after rate matching.
Proposal 3: Same code block length range can be applied to all M values of OOK-4 modulation.
Proposal 4: 1 & 2 information bits for LP-WUS should be confirmed.
Proposal 5: Block-level repetition over RM coding before Manchester coding should not be supported.
Proposal 6: Block-level repetition after Manchester coding could be supported for coverage enhancement.
Proposal 7: It is should be clarified that the OFDM sequences are overlaid after Manchester coding at each ON chip.
Proposal 8: Same candidate set of overlaid sequences should be supported for all OOK ON chips of LP-WUS.
Proposal 9: It should be supported that CS(s) values is configured by gNB from 1 ~ (Bzc -1).
Proposal 10: It should be supported that the overlaid OFDM sequences can be repeated in the set of OOK ON chips, which carry the raw information bits in one segment.
Proposal 11: The maximum frequency gap between LP-WUS/LP-SS and SSB should be determined by RAN4.
Proposal 12: It should be supported the LP-WUS/LP-SS and other NR channel can be transmitted in FDM for interference cancellation.
Proposal 13: Both OOK-1 and OOK-4 with M=1/2/4 can be supported for LP-SS waveform.
Proposal 14: It should be supported that M=1 value is configured for both LP-WUS and LP-SS, if M=1 is configured for either of LP-WUS or LP-SS. 
Proposal 15: Capture the following RRC parameters into the LP-WUS RRC parameter list.

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

Source: 	CMCC
Title:	Discussion on LP-WUS and LP-SS design
Agenda item:	9.6.1
Document for:	Discussion & Decision

Conclusions
In this contribution, we discussed the LP-WUS and LP-SS design, and the following proposals were made.
Proposal 1: For RRC connected mode, for candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell, it’s unnecessary to change the candidate set of overlaid sequences across OOK ON chips.
Proposal 2: For LP-WUS information to trigger PDCCH monitoring of RRC connected UEs, both 1-to-1 and 1-to-all mapping from codepoint to UEs are supported.
Proposal 3: For LP-WUS with M=4, support additional sync signal to LP-SS with LP-SS periodicity =320/160 ms. LP-SS with M=4 can be reused as the additional sync signal.
Proposal 4: For the M value for LP-WUS and LP-SS, different M values for LP-SS can be used for LP-WUS with M=1.
Proposal 5: For RRC idle/inactive mode, don’t support to define the maximum frequency gap between LP-WUS/LP-SS and SSB.

TDoc file reading error

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


Agenda item:	9.6.1
Source:	NEC
Title:              	Discussion on LP-WUS and LP-SS design
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the LP-WUS and LP-SS design, and the following proposals are made:
Proposal 1: support flexibly configuring frequency locations of one or more LP-WUS bands within a carrier, UE can select an LP-WUS band based on its UE ID or a PF/PO it is intended to monitor.
Proposal 2: support message based LP-WUS structure with a preamble and a CRC.
Proposal 3: support repetition of LP-WUS to improve the coverage.
Observation 1: for UE with OFDM LR, it is beneficial if UE is allowed to receive only partial OOK symbols of LP-WUS and acquire the information bits based on the OOK on-off pattern and overlaid sequences of the partial OOK symbols.
Proposal 4: the order/pattern of information bits mapped to overlaid sequences should facilitate UE to acquire information bits based on partial OOK symbols, e.g., first half of the OOK symbols, of the LP-WUS.
Proposal 5: support FDM multiplexing of an LP-SS and its QCLed SSB.

3GPP TSG RAN WG1 #121			R1-2503964
St Julian’s, Malta, May 19th – 23rd, 2025
                                      
Agenda Item:	9.6.1
Source:	InterDigital, Inc.
Title:	Discussion on LP-WUS and LP-SS design
Document for:	Discussion and Decision

Conclusion
In this contribution, we discussed LP-WUS and LP-SS design frameworks. From the discussions, we made following observations and proposals:
Observation 1. Considering additional sync signal increases the synchronization overhead as well as receiver’s complexity.
Observation 2. In LP-SS based on OOK-4 with diverse values of M, the LP-WURs experience frequent need to change modulation order resulting in increased implementation complexity due to configured LP-SS having OOK-4 with different M values in serving and non-serving cells. 
Observation 3. Inaccuracy in RRM measurements based on LP-SS could cause inconsistency between RRM measurements based on LP-SS and NR-SS that could result in frequent false MR wake up.

Proposal 1. Support no additional sync signal for M = 4.
Additional LP-SS periodicity can be considered to support M=4, if needed. 
Proposal 2.  Confirm the working assumption on modulation orders for LP-SS to include both Option 1 with OOK-1 and Option 2 with OOK-4 and M = 2 or 4. 
Do not support additional M values.
Proposal 3. M=1 is not required to be configured for both LP-WUS and LP-SS if M=1 is configured for either of LP-WUS or LP-SS.
Proposal 4. Procedures for handling inconsistencies in RRM measurements based on LP-SS and RRM measurements based on NR-SS, e.g., due to RRM measurements inaccuracies based on LP-SS, should be supported.
Proposal 5. Whether to define the maximum frequency gap between LP-WUS/LP-SS and SSB is up to RAN4.
Proposal 6. The candidate set of overlaid sequences does not change across OOK ON chips.
Proposal 7. Confirm the working assumption on the support of maximum 2 roots for FR1.
Support the maximum 2 roots for FR2. 
Proposal 8. Confirm the working assumption on the support of 1 and 2 information bits.
Proposal 9: The OOK waveform without overlaid OFDM sequence is not specified in RAN1 and define RAN4 requirements to guarantee the OOK detection performance.

3GPP TSG-RAN WG1 Meeting #121	R1- 2504018
St. Julian’s, Malta, May 19th – May 23rd, 2025
Agenda Item:	9.6.1
Source:	Ericsson
Title:	LP-WUS and LP-SS design
Document for:	Discussion

Conclusion
In the previous sections we made the following observations: 
Observation 1	Case of LP-SS with M=1 has the benefit of simplicity. Case of LP-SS with M>1 improves the synchronization accuracy or alternatively reduces the overhead and NW energy consumption for a fixed synchronization accuracy.
Observation 2	Compared to OOK-4 [M>1], OOK-1 [M=1] has lower complexity for both the UE and gNB and it can provide slightly better coverage and is more robust against timing errors.
Observation 3	In the Idle/Inactive mode, OOK-4 [M>1] does not provide benefit over OOK1 while increasing both gNB and UE complexity and M=4 especially does not provide any benefit over M=2 while being more sensitive to timing error.
Observation 4	For the case that LP-WUS/LP-SS and SSB are located within the initial BWP where the UE receives paging, the UE should be able to rely on SSB-based measurements.
Observation 5	When LP-WUS/LP-SS is located outside the initial DL BWP (which contains SSB), then the RRM measurement can be based on the UE capability between SSB-based and LP-SS-based.
Observation 6	For OOK based LP-WUS,
	For OOK-1 (M=1), 18-28 OFDM symbols are required to achieve 1%MDR for -3dB SNR depending on FAR assumption (0.1% vs 1%), and number of sequences checked by the UE.
	For OOK-4 (M=2,4) slightly more OFDM symbols than OOK-1 are needed to achieve same performance when same total power is assumed for the duration of LP-WUS transmission.
Observation 7	For LP-WUS, it is beneficial to support a wide range of code-block length to allow efficient WUS transmission in different scenarios. For maximum block-code length, the UE detection complexity should also be considered.
Observation 8	For M>1, code-block length of 32 corresponds to 16 or 8 OFDM symbols duration which is not sufficient for -3dB SNR coverage without any repetitions.
Observation 9	For OFDM detection, WUS duration of around 4 OFDM symbols is sufficient to reach -3 dB SNR.
Observation 10	The maximum repetition factor is given by:  ,  where  is the number of OOK ON symbols over the entire LP-WUS duration,  is the number of raw information bits, and  is the number of candidate overlaid OFDM sequences for one OOK ON chip.
Observation 11	Sequences with different roots are more robust against timing error/uncertainty compared to different cyclic shifts. Hence, multiple roots need to be considered for OFDM sequences.
Observation 12	If the ZC sequences are generated with different roots and/or cyclic shifts (with sufficient separation), the cross correlations between them are low and do not increase the FAR.
Based on the discussion in the previous sections we propose the following:
Proposal 1	Following principles should be considered for LP-WUS and LP-SS design
a.	It should be possible to generate LP-WUS/LP-SS transmissions using existing gNB hardware and not trigger any new emissions or compliance requirements.
b.	It should be possible to multiplex the LP-WUS/LP-SS with other NR transmissions in time or frequency domain without causing interference.
c.	It should be possible to reuse any unused LP-WUS time and frequency resources for other transmissions.
Proposal 2	Paging misdetection performance of the UE should not be impacted when LP-WUS is used by the UE for power savings.
Proposal 3	For M=1 LP-WUS, LP-SS with both M=1 and M>1 should be supported.
Proposal 4	For LP-WUS, M=4 is not supported in idle/inactive mode.
Proposal 5	For case when LP-WUS/LP-SS and SSB are located within the initial BWP where the UE receives paging, UE supports SSB-based RRM.
Proposal 6	For case when LP-WUS/LP-SS and SSB are located outside the initial BWP where the UE receives paging (but within the carrier), UE may indicate support of either SSB-based RRM or LP-SS-based RRM.
Proposal 7	Maximum frequency gap between LP-WUS/LP-SS and SSB is not defined and no additional signaling is introduced to indicate such gap.
Proposal 8	Confirm the working assumption from RAN1#120bis regarding “No additional restriction on the supported number of subgroups/codepoints by LP-WUS and the support of 1 & 2 information bits for LP-WUS”.
Proposal 9	Regarding the code-block length, all values from 3 to 32 (listed in RAN1#120bis agreement) is supported and it is considered for all M values.
Proposal 10	Repetitions should be supported for LP-WUS to reach -3dB SNR coverage.
Proposal 11	If repetition is supported for OOK-based LP-WUS, the OOK symbols after Manchester coding are repeated N_rep times. The N_rep repetitions occur in same MO.
Proposal 12	Maximum N_rep=[5] repetitions can be supported in the specifications considering different deployment scenarios, gNB flexibility to reserve some symbols in each slot for other transmissions, UE implementation margins etc., resulting in maximum MO duratio for LP-WUS (i.e., after maximum repetitions) of [15] slots.
Proposal 13	Confirm the Working Assumption from RAN1#120 regarding codepoint scheme in connected mode.
Proposal 14	To carry OFDM information, sequences associated with the WUS information block (which can span over one or multiple OOK ON symbols) should be repeated over the entire LP-WUS duration.
Proposal 15	To carry OFDM information over entire LP-WUS duration, the rate matching should be done according to Clause 5.4.3 of TS 38.212.
Proposal 16	Confirm the working assumption from RAN1#120bis that “At least for FR1, support maximum 2 roots to be used for overlaid OFDM sequences for M=1/2/4 (max 2 for each M value). Different roots can be picked for different M values.”
Proposal 17	The cyclic shifts of the OFDM sequences CSs () are determined as follows:
,  is the sequence length.
Proposal 18	For LP-SS with M=1, when specified overlaid OFDM sequence is not configured, 
, for .

3GPP TSG RAN WG1 #121			                     R1-2504066 St Julian’s, Malta, May 19th – 23th 2025   
Agenda Item 	:	9.6.1
Source 	:	Sony 
Title 	:	LP-WUS and LP-SS design
Document for 	:	Discussion and decision

Conclusion
In this contribution, we have discussed our views on LP-WUS and LP-SS design and made the following observations and proposals.
Observation 1 – OOK-4 with M>1 has lower system overhead and can be detected with shorter delay using lower power LP-WUR, compared to OOK-1 or OOK-4 candidates with lower values of M. 
Observation 2 - The maximum number of bits per OFDM symbol, M, needs to be calculated based on LP-WUS bit rate, preventing ISI and the tolerable time/frequency errors by the LP-WUR. 
Observation 3 – Using the same SCS configuration as other NR has less complexity for gNB.

Observation 4 - To allow for fine synchronization and to prevent the NW from always-on transmission of LP-SS with short periodicity, it is beneficial that the LP-WUS also includes a preamble prior to its data information. 

Observation 5 – A use of a preamble before LP-WUS data part results in reduced power consumption at the UE while monitoring for LP-WUS. The LP-WUR first needs to only look for the preamble and it only continues to detect the data if the preamble is detected.

Proposal 1 – RAN1 to support setting M value to its maximum, i.e., M=4 for 30 kHz SCS and M=8 for 15 kHz to allow for low system overhead, lower latency and less power consumption at the LP-WUR.
Proposal 2 – RAN1 to support the same SCS configuration as other NR as it has less complexity for gNB.
Proposal 3 – Support LP-WUS structure with two fields, a preamble field for synchronization and cell identification purposes and a data field for indication of subsequent actions and/or wake-up group identity, depending on state of the operation.
Proposal 4 – When carrying information, the information carried in the overlaid sequence should be only for the purpose of reducing the total length of the LP-WUS received by OFDM based LP-WUR without degrading performance of the OOK-based LP-WUR. 

Proposal 5 – The OFDM overlaid sequence carrying cell information, should be only used for the purpose of assisting OFDM-based LP-WUR detection and not carrying any additional information that cannot be detected by the OOK-based LP-WUR.
Proposal 6 – Support inclusion of association of cell ID to the LP-SS sequences, e.g., by choosing LP-SS with max. value of M and L.
 
Proposal 7 – RAN1 to revise the agreed number of sequences and allow for larger number of sequences. 
Proposal 8 – Consider additional aperiodic synchronization signal where the signal/sequence is transmitted as part of LP-WUS. 
Proposal 9 – Support longer periodicity of LP-SS to allow reduced resource, power consumption and spectrum usage.

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

Agenda Item:	9.6.1
Source:	HONOR
Title:	Discussion on LP-WUS and LP-SS design
Document for:	Discussion and Decision

Conclusions
The following observations and proposals are given:
Observation 1: When there are frequency domain errors, the performance of using only cyclic shift to generate the ZC sequence degrades significantly.
Observation 2: For LP-SS occupying 6 and 8 symbols, the existing SSB symbol positions cannot be directly reused and require predefined rules.

Proposal 1: The M values for LP-WUS and LP-SS can be configured to be the same or different. For any M value, the M value for LP-WUS cannot be larger than that of LP-SS.
Proposal 2：Support M=4 for 30kHz SCS.
Proposal 3: The value of M is independent of SCS.
Proposal 4：Specify only the necessary steps for the design of OOK-1 and OOK-4.
Proposal 5: Specifies only the overlaid sequence for OOK-1.
Proposal 6: Specifies the two steps of sequence mapping and DFT for OOK-4.
Proposal 7: Further discuss how the UE obtains the OOK waveform generation scheme.
Proposal 8: The candidate overlaid sequence set of the cell is configurable.
Proposal 9: The overlaid sequence configuration reuses the configuration method of PRACH preamble sequences.
Proposal 10: Confirm the following work assumption:
At least for FR1, support maximum 2 roots to be used for overlaid OFDM sequences for M=1/2/4 (max 2 for each M value). 
Different roots can be picked for different M values.
Proposal 11: Confirm the following working assumption:
Support the following options for LP-SS
Option 1: OOK-1 
Option 2: OOK-4 with M=2,4
The SCS of a CP-OFDM symbol used for LP-SS generation is the same as that used for LP-WUS generation
Proposal 12: Assign the SSB symbols and the two blank symbols either before or after it to the LP-SS with 6 occupied symbols.
Proposal 13: The time domain symbol positions of LP-SS with 8 symbols use the time domain symbol positions of two 20ms SSBs.

3GPP TSG RAN WG1 #121		                                           R1-2504187
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	9.6.1
Source: 	OPPO
Title:	Signal design for LP-WUS and LP-SS
Document for:	Discussion & Decision

Conclusion
In this contribution, we discussed the signal design for LP-WUS and LP-SS.  Observations and proposals are summarized as following.
Confirm the working assumption. Support M=4 for 30KHz SCS. 
Confirm the Working Assumption with following update.
Proposal 3: RAN1 to clarify the numbers of candidates overlaid sequences supported other than the maximum value.
RAN1 can confirm the working assumption on the supported information bits.
Coded bits length after rate matching depends on the resource allocation, if we limit the coded bits length, it will limit the time domain resource allocation for LP-WUS.
Based on the agreement, no further mapping rule between POs and MOs in case of multiple POs associated with one LO.
No restriction on the coded bits length. Exactly code block length depends on the resource allocation
In case of multiple POs associated with one LO, it needs to determine how to wake up subgroups in different POs by LP-WUS.
In case of multiple POs associated with one LO, if one codepoint value is configured for the subgroups in different POs, it will decrease the power saving gain.
For the power saving gain, avoid the case that non-target subgroup(s) are woke-up by LP-WUS in case of multiple POs associated with one LO.
Support the PO indication in LP-WUS.
Introducing PO indication field won’t change the maximum number of LP-WUS information bits.
Introducing PO indication field could achieve the early termination for non-target PO’s UE.
If no PO indication field, it needs to increase the bit number for codepoint. The total bits for LP-WUS is same.
Support PO indication field in LP-WUS, i.e. LP-WUS consist of 2 fields, one is used to indicate the associated PO, the other one is used to indicate the codepoint.
A UE can report supported number of detecting codepoints for monitoring wake-up indication in CONNECTED mode, from 2 candidates {4, 8}.
LP-SS sequence is associated to the cell ID by pre-determined rules.
For LP-SS. 
Single overlaid sequence is on each OOK ‘ON’ symbol.
When LP-SS reuses the overlaid OFDM sequence(s) specified for LP-WUS.
It needs to determine how to reuse the overlaid OFDM sequence(s) specified for LP-WUS, e.g. the overlaid OFDM sequence for LP-SS is associated with the candidate overlaid OFDM sequence.
LP-WUS and LP-SS share the same frequency location, SSB location should determine LP-WUS/LP-SS location with an offset. 
Frequency gap between starting of LP-WUS/LP-SS and starting of SSB can be set to up to 100MHz for FR1.
No to consider the restriction on the M value configuration in case of M=1.

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

Agenda Item:	9.6.1
Source:	Panasonic
Title:	Discussion on the LP-WUS and LP-SS design
Document for:	Discussion/Decision

Conclusion 
For RRC idle/inactive, LP-WUS is not supported for the case where associated CD-SSB and initial DL BWP have different SCSs


Agreement
At least for M>1, for the overlaid OFDM sequence length, support
Alt2:
Note: X is the number of RBs of LP-WUS/LP-SS bandwidth (blanked guard RBs are not included)



Agreement
Proposal 4.3-1: Update the agreements in RAN1 #118bis as below
Agreement
Support overlaid OFDM sequence(s) for LP-SS:
LP-SS reuses the overlaid OFDM sequence(s) specified for LP-WUS. The design on overlaid OFDM sequence(s) specified for LP-WUS doesn’t target for sync and RRM measurement performance based on overlaid OFDM sequence for LP-SS.
Applicable to both OOK-1 and OOK-4
Whether to transmit LP-SS by using a specified overlaid OFDM sequence is configurable.
Applicable at least for OOK-1 only and FFS for OOK-4
From RAN1 perspective, it is not intended to introduce new RAN4 requirements specific to overlaid sequences


Agreement
For RRC connected, for LP-WUS SCS:
Alt 1: LP-WUS SCS is same as the active DL BWP 


Working Assumption 
Regarding the LP-WUS information to trigger PDCCH monitoring of RRC connected UEs:
Codepoint based
The maximum number of codepoints checked per MO by a UE is up to 8
Depending on UE capability, a UE may support less than 8



Agreement
For M=2, 4, is given by the largest prime number such that,is the overlaid OFDM sequence length.
The base overlaid sequenceis generated by extension of
,
With CS(s) applied to the base overlaid OFDM sequence if any:denotes the potential cyclic shift (s)
,
Note it doesn’t preclude any pulse shaping scheme if any.



Agreement
For RRC connected, LP-WUS frequency resource can be outside of active DL BWP but has to be within the same carrier as the active DL BWP 
Basic capability is LP-WUS, if present, frequency resource within active DL BWP. LP-WUS frequency resource outside of active DL BWP is subject to separate UE capability
No RAN1 optimization specific to the case where LP-WUS frequency resource is outside of active DL BWP



Agreement
For M=1, L=4 (if supported), the set of LP-SS binary sequences is:
[0 1 0 1]
[0 1 1 0]
[1 0 0 1]
[1 0 1 0]

Agreement
For M=1, L=6 (if supported), the set of LP-SS sequence is:
[1 0 1 0 1 0]
[0 1 0 1 0 1]
[1 0 0 1 0 1]
[1 0 1 0 0 1]

Agreement
For M=1, L=8 (if supported), the set of LP-SS sequence is:
[1 0 1 0 0 1 0 1]
[1 0 1 0 1 0 0 1]
[1 0 0 1 0 1 0 1]
[0 1 0 1 0 1 0 1]

Agreement
For M=2, L=8 (if supported), the set of LP-SS sequence is:
[0 1 0 1 1 0 0 1]
[0 1 1 0 0 1 0 1]
[0 1 1 0 1 0 0 1]
[1 0 0 1 0 1 1 0]

Agreement
For M=2, L=12 (if supported), the set of LP-SS sequence is:
[1 0 0 1 1 0 0 1 1 0 0 1]
[0 1 1 0 1 0 0 1 1 0 0 1]
[0 1 1 0 0 1 1 0 1 0 0 1]
[0 1 1 0 0 1 0 1 1 0 0 1]

Agreement
For M=2, L=16 (if supported), the set of LP-SS sequence is:
[1 0 0 1 0 1 0 1 1 0 0 1 1 0 0 1]
[1 0 0 1 1 0 0 1 0 1 1 0 0 1 0 1]
[1 0 0 1 1 0 1 0 0 1 0 1 1 0 0 1]
[1 0 1 0 0 1 1 0 0 1 1 0 0 1 0 1]

Agreement
For M=4, L=16 (if supported), the set of LP-SS sequence is down-selected between:
Set 1
[0 1 1 0 1 0 0 1 1 0 1 0 1 0 1 0]
[0 1 1 0 1 0 1 0 1 0 0 1 1 0 1 0]
[1 0 1 0 0 1 1 0 1 0 1 0 1 0 0 1]
[1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0]
Set 2
[1 0 0 0 1 0 0 0 0 0 0 1 0 0 1 0]
[1 0 0 0 0 1 0 0 1 0 0 0 0 0 1 0]
[1 0 0 0 0 1 0 0 0 1 0 0 1 0 0 0]
[1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 1]

Agreement
For M=4, L=32(if supported), the set of LP-SS sequence is down-selected between:
Set 1:
[0 1 0 1 1 0 1 0 1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0 0 1 1 0 0 1 0 1]
[0 1 1 0 0 1 0 1 0 1 1 0 0 1 0 1 1 0 0 1 1 0 1 0 1 0 1 0 0 1 0 1]
[0 1 0 1 0 1 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0]
[0 1 0 1 0 1 1 0 0 1 0 1 1 0 1 0 0 1 1 0 0 1 1 0 1 0 1 0 0 1 0 1]
Set 2
[0 0 0 1 1 0 0 0 0 0 0 1 0 0 0 1 1 0 0 0 0 0 0 1 0 0 0 1 0 1 0 0]
[0 0 0 1 0 1 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 0 1 0 1 0 0]
[0 0 1 0 0 0 1 0 1 0 0 0 0 1 0 0 1 0 0 0 0 0 0 1 0 0 1 0 0 0 1 0]
[0 0 1 0 0 1 0 0 0 0 0 1 1 0 0 0 0 0 1 0 1 0 0 0 0 1 0 0 0 0 1 0]

Agreement
For idle mode, regarding the maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell:
support maximum 16 candidates overlaid sequences for M=1
support maximum 8 candidates overlaid sequences for M=2
For candidate overlaid sequences across all OOK ON chips of LP-WUS, the number of roots (in specification) is up to [FFS: X], FFS whether the number of roots can be different for different M value. 
FFS: The number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip.



Agreement
For WUS information carried by the overlaid OFDM sequence(s), consider at least the following alternatives:
Alt 1: Raw information bits are mapped to sequence(s)
Alt 2: Raw information bits are mapped to sequence(s) after channel coding
Same channel coding scheme(s) as OOK is applied.
FFS same or different rate matching and/or repetition factor as OOK
Alt 3: Codepoint/Subgroup is mapped to sequence(s)


Agreements from RAN1#120bis meeting

Agreement
From specification design perspective, for both RRC idle/inactive and RRC connected mode, support up to 5 information bits and up to 32 codepoints for a LP-WUS.

Agreement
Support maximum length for a LP-WUS (actual OFDM symbols used) which is larger than one slot
Non-consecutive OFDM symbols at least across multiple slots can be used for a LP-WUS transmission

Agreement
For RRC connected mode, maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell, 
support maximum 16 candidates overlaid sequences for M=1
support maximum 8 candidates overlaid sequences for M=2
support maximum 4 candidates overlaid sequences for M=4 (agreed in RAN1#119)
For candidate overlaid sequences across all OOK ON chips of LP-WUS, the number of roots (in specification) is up to [FFS: X], FFS whether the number of roots can be different for different M value. 
FFS: The number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip.
FFS: Whether or not the candidate set of overlaid sequences change across OOK ON chips

Agreement
For M=1, the overlaid OFDM sequence length , X is the number of RBs of LP-WUS/LP-SS bandwidth (blanked guard RBs are not included)
The agreement overrides previous WA

Agreement
Regarding whether to support additional sync signal to LP-SS, support the following for LP-WUS with M=1, M=2:
Option 1A: No additional sync signal, LP-SS periodicity =320ms
Additionally support LP-SS periodicity of 160ms

Working Assumption
At least for FR1, support maximum 2 roots to be used for overlaid OFDM sequences for M=1/2/4 (max 2 for each M value). 
Different roots can be picked for different M values.

Agreement
For > 2 information bits with RM coding, support one of the following alternatives for rate matching after RM coding, when code block (coded bits) length after rate matching < 32
Alt 1: Rate matching after RM coding is applied, as section 5.4.3 in TS 38.212.

Agreement
For the length L of LP-SS binary sequence, supports
M=1, L= {6,8}
M=2, L= {12,16}
M=4, L= {16,32}
Note: For each value of M, UE supports both L values – no UE capability. 
Note: There is no consensus in RAN1 that SNR of -3dB can be fulfilled with the smaller value of L for each M. Definition of the proper requirements for different values of L is up to RAN4.

Agreement
For LP-SS with M=4, supports set1 (balanced).

Agreement
For the root(s) used for overlaid OFDM sequences, gNB can configure any value from 1 ~ (Bzc -1), where Bzc is given by the largest prime number such that , is the overlaid OFDM sequence length.

Agreement
For WUS information carried by the overlaid OFDM sequence(s), down-select between Alt 1 and Alt2:
Alt 1: Raw information bits are mapped to sequence(s)
N raw information bits are divided into K segments from MSB to LSB, where K= ceil (N/log2L), L is the number of candidate overlaid OFDM sequences for one OOK ON chip.
In one OOK ON chip, a segment of information bits is mapped to one sequence sequentially, e.g., for a segment of 2 information bits, 00 is mapped to sequence #1, 01 is mapped to seq #2. 
In case N/log2L is not an integer, Bit 0 as MSB is used for padding

Agreement
For > 2 information bits with RM coding, support candidate code block (coded bits) length after rate matching within the below range:
Alt 1a: code block (coded bits) length: [3,4]~[32,64]
FFS whether all or a subset of lengths is selected.
FFS whether same range applies to all M values
FFS: above lengths do not consider repetition (if supported) after rate matching

Agreement
For RRC idle/inactive, support Alt 1 for both Redcap and non-redcap UEs:
Alt 2: LP-WUS/LP-SS frequency resource can be out of initial DL BWP where UE receives paging but within the same carrier.
FFS whether to define the maximum frequency gap between LP-WUS/LP-SS and SSB 

Working Assumption
Support 1 & 2 information bits for LP-WUS. No additional restriction is introduced on the supported number of subgroups/codepoints by LP-WUS.
2 information bits: coding is done as described in the first row in the table in section 5.3.3.2 of 38.212 (scrambling is not applied)
1 information bit: repetition is done as described in the first row in the table in section 5.3.3.1 of 38.212 (scrambling is not applied)

Agreement
For the M value for LP-WUS and LP-SS, supports:
Alt2: The M values for LP-WUS and LP-SS can be configured to be same or different. M value for LP-WUS cannot be larger than that of LP-SS. 
At least for M values larger than 1 (applies to both LP-WUS and LP-SS)
FFS: If M=1 is configured for either of LP-WUS or LP-SS, M=1 is configured for both

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

Agenda Item:	9.6.1
Source: 	LG Electronics
Title: 	Discussion on LP-WUS and LP-SS design
Document for:	Discussion and decision

Conclusions
In this contribution, we have discussed on the various aspects for LP-WUS and LP-SS design, and the followings are proposed.
Proposal #1: Confirm to support OOK-4 with M=4 for 30 kHz SCS
Proposal #2: Not support M=4 for LP-WUS/LP-SS in FR2
Proposal #3: Code block length should be 3~32
Proposal #4: Confirm the working assumption on supporting 1 & 2 information bits for LP-WUS
Proposal #5: Additional repetition can be considered when the information bits carried by LP-WUS is 1 bit or 2 bits
For more than 2 bits, no need to consider the additional repetition on top of RM coding
Proposal #6: Consider different root for different cells to mitigate inter-cell interferences
For a given cell, different CS can be used to differentiate sequences 
Proposal #7: When two roots are needed for a cell, the pair of roots can be determined by one of following options for ensuring better cross-correlation property or lower correlation complexity
Option 1: When root q1 is configured based on Cell ID, root q2 is determined so that |q1-q2| is relatively prime to L
Option 2: When root q1 is configured based on Cell ID, root q2 is determined so that q2 = L-q1.
Proposal #8: For a given root value, the smallest CS value is selected as a smallest relatively prime to the sequence length, and the subsequence CS values are determined by adding constant to the previous CS value
Proposal #9: For the overlaid OFDM sequence on each OOK ON symbol within an OFDM symbol, two sequences with different CS values are alternatively used on each OOK ON symbol
Proposal #10: Discuss the applicable M value for LP-WUS bandwidth smaller than 5 MHz
Proposal #11: In case of overlaid OFDM sequence not carrying information, one sequence is selected from multiple candidates overlaid OFDM sequences which can be configured for the overlaid sequences carrying information bits
Proposal #12: For frequency resource configurations of LP-WUS/LP-SS, consider the followings
For Idle/Inactive mode, frequency resource is configured with a PRB offset from SSB
For Connected mode, frequency resource is configured with a PRB offset from CRB#0
Proposal #13: Support the same frequency resource for LP-WUS and LP-SS
Proposal #14: Confirm the working assumption for LP-SS waveform generation
Proposal #15: At least for FR2, the value of M could be determined based on the SCS of LP-WUS/LP-SS
Proposal #16: When the M value for LP-WUS is configured as 1, the M value for LP-SS should be configured as at least 2 or 4 to ensure adequate timing error tolerance and maintain gNB flexibility 
Observation #1: Applicable L for LP-SS can be configured depending on SCS for LP-WUS and SCS for LP-SS when multiple L values are configured to each M
Proposal #17: Discuss whether and how to configure the M value of LP-SS among multiple candidates with consideration of the followings:
SCS of LP-WUS/LP-SS
LP-SS periodicity
Sequence length of LP-SS (i.e., LP-SS duration)
Proposal #18: Specify the overlaid OFDM sequence in frequency domain for OOK-1
Proposal #19: Specific sequence index from overlaid OFDM sequence of LP-WUS can be used for overlaid OFDM sequence of LP-SS
Proposal #20: Additional sync signal needs to be supported for LP-WUS with M=4
Reuse the agreed binary sequence for additional synchronization signal

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

Source:	MediaTek Inc.
Title:	LP-WUS and LP-SS design
Agenda item:	9.6.1
Document for:	Discussion and decision 

Summary
In this contribution, the following proposals are provided:

Proposal 1:
Support Repetition for Overlaid OFDM Sequences: Repetition should be a supported feature for information carried by overlaid OFDM sequences to improve robustness.
Implicit Derivation of Repetition Parameters: To avoid additional signaling, the number of repetitions for overlaid OFDM sequences could be determined implicitly from RRC-configured parameters concerning the LP-WUS payload and characteristics of the overlaid sequences. Specifically, the number of repetition can be derived by (the number of on-chips for OOK WUS) / K, where K= ceil (N/log2L), where N is raw information bit number and L is the number of candidate overlaid OFDM sequences for one OOK on-chip.

Proposal 2:
LP-WUS M=4 Support with LP-SS M=4, L=32: The combination of LP-WUS with M=4 and LP-SS with M=4, L=32 is well-supported by existing agreements. This configuration benefits from the high timing accuracy of M=4 LP-SS.

Proposal 3:
Flexibility for LP-SS M Value with LP-WUS M=1: Based on the current primary agreement, it is supported to use an LP-SS with M > 1 (e.g., M=2 or M=4) even when the LP-WUS is configured with M=1. This allows the system to capitalize on the superior synchronization performance offered by higher M-value LP-SS configurations.
Resolution of FFS Point: The FFS item regarding a strict M=1 linkage for both LP-WUS and LP-SS should be addressed as well (no such restriction). The technical advantage of permitting a more robust (higher M) LP-SS for a better timing reference and potentially shorter LP-SS length should be allowed.

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

Agenda Item:	9.6.1

Source:	Apple Inc.
Title:	LP-WUS and LP-SS design
Document for:	Discussion/Decision

Conclusion 
For RRC idle/inactive, LP-WUS is not supported for the case where associated CD-SSB and initial DL BWP have different SCSs

Agreement
At least for M>1, for the overlaid OFDM sequence length, support
Alt2:
Note: X is the number of RBs of LP-WUS/LP-SS bandwidth (blanked guard RBs are not included)

Agreement
Proposal 4.3-1: Update the agreements in RAN1 #118bis as below
Agreement
Support overlaid OFDM sequence(s) for LP-SS:
LP-SS reuses the overlaid OFDM sequence(s) specified for LP-WUS. The design on overlaid OFDM sequence(s) specified for LP-WUS doesn’t target for sync and RRM measurement performance based on overlaid OFDM sequence for LP-SS.
Applicable to both OOK-1 and OOK-4
Whether to transmit LP-SS by using a specified overlaid OFDM sequence is configurable.
Applicable at least for OOK-1 only and FFS for OOK-4
From RAN1 perspective, it is not intended to introduce new RAN4 requirements specific to overlaid sequences

Agreement
For RRC connected, for LP-WUS SCS:
Alt 1: LP-WUS SCS is same as the active DL BWP 

Working Assumption 
Regarding the LP-WUS information to trigger PDCCH monitoring of RRC connected UEs:
Codepoint based
The maximum number of codepoints checked per MO by a UE is up to 8
Depending on UE capability, a UE may support less than 8

Agreement
For M=2, 4, is given by the largest prime number such that,is the overlaid OFDM sequence length.
The base overlaid sequenceis generated by extension of
,
With CS(s) applied to the base overlaid OFDM sequence if any:denotes the potential cyclic shift (s)
,
Note it doesn’t preclude any pulse shaping scheme if any.

Agreement
For RRC connected, LP-WUS frequency resource can be outside of active DL BWP but has to be within the same carrier as the active DL BWP 
Basic capability is LP-WUS, if present, frequency resource within active DL BWP. LP-WUS frequency resource outside of active DL BWP is subject to separate UE capability
No RAN1 optimization specific to the case where LP-WUS frequency resource is outside of active DL BWP

Agreement
For M=1, L=4 (if supported), the set of LP-SS binary sequences is:
[0 1 0 1]
[0 1 1 0]
[1 0 0 1]
[1 0 1 0]

Agreement
For M=1, L=6 (if supported), the set of LP-SS sequence is:
[1 0 1 0 1 0]
[0 1 0 1 0 1]
[1 0 0 1 0 1]
[1 0 1 0 0 1]

Agreement
For M=1, L=8 (if supported), the set of LP-SS sequence is:
[1 0 1 0 0 1 0 1]
[1 0 1 0 1 0 0 1]
[1 0 0 1 0 1 0 1]
[0 1 0 1 0 1 0 1]

Agreement
For M=2, L=8 (if supported), the set of LP-SS sequence is:
[0 1 0 1 1 0 0 1]
[0 1 1 0 0 1 0 1]
[0 1 1 0 1 0 0 1]
[1 0 0 1 0 1 1 0]

Agreement
For M=2, L=12 (if supported), the set of LP-SS sequence is:
[1 0 0 1 1 0 0 1 1 0 0 1]
[0 1 1 0 1 0 0 1 1 0 0 1]
[0 1 1 0 0 1 1 0 1 0 0 1]
[0 1 1 0 0 1 0 1 1 0 0 1]

Agreement
For M=2, L=16 (if supported), the set of LP-SS sequence is:
[1 0 0 1 0 1 0 1 1 0 0 1 1 0 0 1]
[1 0 0 1 1 0 0 1 0 1 1 0 0 1 0 1]
[1 0 0 1 1 0 1 0 0 1 0 1 1 0 0 1]
[1 0 1 0 0 1 1 0 0 1 1 0 0 1 0 1]

Agreement
For M=4, L=16 (if supported), the set of LP-SS sequence is down-selected between:
Set 1
[0 1 1 0 1 0 0 1 1 0 1 0 1 0 1 0]
[0 1 1 0 1 0 1 0 1 0 0 1 1 0 1 0]
[1 0 1 0 0 1 1 0 1 0 1 0 1 0 0 1]
[1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0]
Set 2
[1 0 0 0 1 0 0 0 0 0 0 1 0 0 1 0]
[1 0 0 0 0 1 0 0 1 0 0 0 0 0 1 0]
[1 0 0 0 0 1 0 0 0 1 0 0 1 0 0 0]
[1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 1]

Agreement
For M=4, L=32(if supported), the set of LP-SS sequence is down-selected between:
Set 1:
[0 1 0 1 1 0 1 0 1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0 0 1 1 0 0 1 0 1]
[0 1 1 0 0 1 0 1 0 1 1 0 0 1 0 1 1 0 0 1 1 0 1 0 1 0 1 0 0 1 0 1]
[0 1 0 1 0 1 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0]
[0 1 0 1 0 1 1 0 0 1 0 1 1 0 1 0 0 1 1 0 0 1 1 0 1 0 1 0 0 1 0 1]
Set 2
[0 0 0 1 1 0 0 0 0 0 0 1 0 0 0 1 1 0 0 0 0 0 0 1 0 0 0 1 0 1 0 0]
[0 0 0 1 0 1 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 0 1 0 1 0 0]
[0 0 1 0 0 0 1 0 1 0 0 0 0 1 0 0 1 0 0 0 0 0 0 1 0 0 1 0 0 0 1 0]
[0 0 1 0 0 1 0 0 0 0 0 1 1 0 0 0 0 0 1 0 1 0 0 0 0 1 0 0 0 0 1 0]

Agreement
For idle mode, regarding the maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell:
support maximum 16 candidates overlaid sequences for M=1
support maximum 8 candidates overlaid sequences for M=2
For candidate overlaid sequences across all OOK ON chips of LP-WUS, the number of roots (in specification) is up to [FFS: X], FFS whether the number of roots can be different for different M value. 
FFS: The number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip.

Agreement
For WUS information carried by the overlaid OFDM sequence(s), consider at least the following alternatives:
Alt 1: Raw information bits are mapped to sequence(s)
Alt 2: Raw information bits are mapped to sequence(s) after channel coding
Same channel coding scheme(s) as OOK is applied.
FFS same or different rate matching and/or repetition factor as OOK
Alt 3: Codepoint/Subgroup is mapped to sequence(s)

RAN1#120bis agreements
Agreement
From specification design perspective, for both RRC idle/inactive and RRC connected mode, support up to 5 information bits and up to 32 codepoints for a LP-WUS.

Agreement
Support maximum length for a LP-WUS (actual OFDM symbols used) which is larger than one slot
Non-consecutive OFDM symbols at least across multiple slots can be used for a LP-WUS transmission

Agreement
For RRC connected mode, maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell, 
support maximum 16 candidates overlaid sequences for M=1
support maximum 8 candidates overlaid sequences for M=2
support maximum 4 candidates overlaid sequences for M=4 (agreed in RAN1#119)
For candidate overlaid sequences across all OOK ON chips of LP-WUS, the number of roots (in specification) is up to [FFS: X], FFS whether the number of roots can be different for different M value. 
FFS: The number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip.
FFS: Whether or not the candidate set of overlaid sequences change across OOK ON chips

Agreement
For M=1, the overlaid OFDM sequence length , X is the number of RBs of LP-WUS/LP-SS bandwidth (blanked guard RBs are not included)
The agreement overrides previous WA

Agreement
Regarding whether to support additional sync signal to LP-SS, support the following for LP-WUS with M=1, M=2:
Option 1A: No additional sync signal, LP-SS periodicity =320ms
Additionally support LP-SS periodicity of 160ms

Working Assumption
At least for FR1, support maximum 2 roots to be used for overlaid OFDM sequences for M=1/2/4 (max 2 for each M value). 
Different roots can be picked for different M values.

Agreement
For > 2 information bits with RM coding, support one of the following alternatives for rate matching after RM coding, when code block (coded bits) length after rate matching < 32
Alt 1: Rate matching after RM coding is applied, as section 5.4.3 in TS 38.212.

Agreement
For the length L of LP-SS binary sequence, supports
M=1, L= {6,8}
M=2, L= {12,16}
M=4, L= {16,32}
Note: For each value of M, UE supports both L values – no UE capability. 
Note: There is no consensus in RAN1 that SNR of -3dB can be fulfilled with the smaller value of L for each M. Definition of the proper requirements for different values of L is up to RAN4.

Agreement
For LP-SS with M=4, supports set1 (balanced).

Agreement
For the root(s) used for overlaid OFDM sequences, gNB can configure any value from 1 ~ (Bzc -1), where Bzc is given by the largest prime number such that , is the overlaid OFDM sequence length.

Agreement
For WUS information carried by the overlaid OFDM sequence(s), down-select between Alt 1 and Alt2:
Alt 1: Raw information bits are mapped to sequence(s)
N raw information bits are divided into K segments from MSB to LSB, where K= ceil (N/log2L), L is the number of candidate overlaid OFDM sequences for one OOK ON chip.
In one OOK ON chip, a segment of information bits is mapped to one sequence sequentially, e.g., for a segment of 2 information bits, 00 is mapped to sequence #1, 01 is mapped to seq #2. 
In case N/log2L is not an integer, Bit 0 as MSB is used for padding

Agreement
For > 2 information bits with RM coding, support candidate code block (coded bits) length after rate matching within the below range:
Alt 1a: code block (coded bits) length: [3,4]~[32,64]
FFS whether all or a subset of lengths is selected.
FFS whether same range applies to all M values
FFS: above lengths do not consider repetition (if supported) after rate matching

Agreement
For RRC idle/inactive, support Alt 1 for both Redcap and non-redcap UEs:
Alt 2: LP-WUS/LP-SS frequency resource can be out of initial DL BWP where UE receives paging but within the same carrier.
FFS whether to define the maximum frequency gap between LP-WUS/LP-SS and SSB 

Working Assumption
Support 1 & 2 information bits for LP-WUS. No additional restriction is introduced on the supported number of subgroups/codepoints by LP-WUS.
2 information bits: coding is done as described in the first row in the table in section 5.3.3.2 of 38.212 (scrambling is not applied)
1 information bit: repetition is done as described in the first row in the table in section 5.3.3.1 of 38.212 (scrambling is not applied)

Agreement
For the M value for LP-WUS and LP-SS, supports:
Alt2: The M values for LP-WUS and LP-SS can be configured to be same or different. M value for LP-WUS cannot be larger than that of LP-SS. 
At least for M values larger than 1 (applies to both LP-WUS and LP-SS)
FFS: If M=1 is configured for either of LP-WUS or LP-SS, M=1 is configured for both

​3GPP TSG RAN WG1 #121			R1-2504401
St Julian’s, Malta, May 19th – 23th, 2025
	
Agenda item:	9.6.1
Source: 	Qualcomm Incorporated
Title: 	LP-WUS and LP-SS Design
Document for:	Discussion and Decision

Conclusions
In this contribution, we have provided the following observations and proposals:
Observation 1: From design and implementation simplicity perspective, it is preferrable to ensure that the LP-WUS fully occupies an integer number of OFDM symbols.
Proposal 1: Regarding whether all or a subset of lengths is selected, any code block length in the agreed range is supported if the corresponding LP-WUS fully occupies the used OFDM symbols
For M=4, only the subset of even lengths is selected.
Proposal 2: To achieve performance target (1% FAR from noise, 1% MDR) at SNR = -3dB in TDL-C channel, the maximum code block length for OOK LP-WUS is
For M=4, L=32 in 16 OFDM symbols
For M=2, L=16 in 16 OFDM symbols
For M=1
L=8 in 16 OFDM symbols with power pooling
L=32 in 64 OFDM symbols without power pooling
Proposal 3: The same maximum code block length is supported for FR1 and FR2.
Proposal 4: The same maximum code block length is supported for different number of information bits including 1, 2 and > 2.
Proposal 5: Confirm the RAN1 #120bis Working Assumption for the support of 1 and 2 information bits for LP-WUS.
Observation 2: It is preferrable to select the minimum code block length that corresponds to integer number of OFDM symbols for all M values.
Proposal 6: The minimum code block length is
For > 2 information bits, 
3 for M = 1 and 2
4 for M = 4
For 2 information bits
2 for M = 1, 2 and 4
For 1 information bit
1 for M = 1 and 2
2 for M = 4
Proposal 7: Confirm the RAN1 #1120bis Working Assumption for maximum 2 roots to be used for overlaid OFDM sequences for FR1. The same applies to FR2.
Proposal 8: Same set of candidate sequences is configured for LP-WUS across OOK On chips for idle/inactive and connected modes.
Proposal 9: Confirm the maximum number of overlaid sequences applicable for a UE is 2 per OOK On chip.
Proposal 10: When multiple MOs are configured in each LP-WUS transmission period, LP-WUS transmission always starts from the first MO and occupies consecutive MOs if more than one LP-WUS is transmitted in the period. UE stops detecting LP-WUS in the remaining MOs of the period if any of the following two conditions is met
UE has detected an LP-WUS for itself, or
UE does not detect any LP-WUS for any UE in the MO
Proposal 11: Support the mapping of multiple codepoint values into overlaid OFDM sequences in the same MO
Support only transmitting overlaid OFDM sequences for UEs that only support OFDM based LP-WUR.
Proposal 12: At least for connected mode UE, the starting OOK On chip in a MO where overlaid OFDM sequences are transmitted for the UE.
Proposal 13: Repetition for overlaid OFDM sequences is not applied by default. Repetition is explicitly enabled by network configuration.
When repetition is enabled, network configures the number of repetitions
Network configures the repetition pattern, i.e., the set of overlaid OFDM sequences for a codepoint is repeated or each overlaid OFDM sequence in the set is repeated first.
Proposal 14: For M=4 for LP-WUS, down select between the following two options 
Option 1: Support additional sync signal
Option 2: Support LP-SS periodicity of 80ms
Proposal 15: It is an optional UE feature for the UE to support the case that LP-WUS/LP-SS frequency resource can be out of initial DL BWP.
Proposal 16: RAN1 asks RAN4 for the RF tuning time if the LP-WUR needs to tune RF before and after SSB reception.
Proposal 17: Available symbols for LP-WUS exclude the RF tuning time for LP-WUR.
Observation 3: LP-WUR AGC design needs to consider additional 3dB dynamic range of time domain average signal power within OOK On chips if same EPRE is assumed for LP-WUS with M=1 and LP-SS with M>1.
Proposal 18: If M=1 is configured for either of LP-WUS and LP-SS, M=1 is configured for both.
Proposal 19: Adopt RRC parameters in Table 2 for early termination of LP-WUS detection.
Proposal 20: Adopt RRC parameters in Table 3 for repetitions of overlaid OFDM sequences.

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

Source:	Sharp
Title:	         Discussion on LP-WUS and LP-SS design
Agenda Item:	9.6.1
Document for:	Discussion and decision

Conclusion
In this contribution, we have the following observations and proposals:
Proposal 1: Ensure that two consecutive symbols within the same slot are always assigned for LP-WUS with M = 1 to support valid Manchester coding.
Proposal 2: Limit the duration of a single LP-WUS to a maximum of 2–3 consecutive slots.
Proposal 3: Confirm the working assumption to support 1-bit and 2-bit LP-WUS. 
Proposal 4: For 1-bit or 2-bit LP-WUS, apply small code block rate matching as defined in 3GPP TS 38.212.
Proposal 5: Do not support additional repetition after rate matching.
Proposal 6: Consider two methods for configuring LP-WUS resources:
   - BWP-specific mode, where LP-WUS resources are configured per BWP.
   - Cell-specific mode, where LP-WUS resources are configured at the cell level.

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

Agenda item:	9.6.1
Source: 	NTT DOCOMO, INC.
Title: 	Discussion on LP-WUS and LP-SS design
Document for:	Discussion and Decision

Conclusion 
In this contribution, we discussed L1 structures on LP-WUS/LP-SS. Based on the discussion, we made following observations and proposals.
Observation 1
There is no difference between allocating LP-SS/LP-WUS and allocating SSB or BWP on a frequency resource within a carrier
Observation 2
If the maximum frequency gap is too small, it may cause significant restriction for NW operation
Observation 3
Repetition in overlaid OFDM sequence over OOK ON chips is important in terms of coverage improvements
Observation 4
If the number of information bits is fixed, the total bit length is known to the UE, so even if overlaid OFDM is repetitive, it can also be used for early termination
If the number of information bits is variable, by defining the number of repetitions, the UE can recognize the length of information bits and the number of repetitions and perform early termination

Observation 5
Based on Y=1 LP-SS sample, 
LP-SS with OOK-4 M=4, L=16,32 does not achieve T=1us accuracy with P=90% at SNR=-3dB 
Observation 6
LP-SS with OOK-4 M=4, L=32 almost achieves T=1us accuracy with P=90% at SNR=-3dB in case of Y=4
Observation 7
For demodulation by the envelope detector, time error must be less than half the duration of one chip
If LP-SS periodicity is larger than 320ms, time error is larger than half of 1chip duration of OOK-4 M=4
Observation 8
For M=4, shorter LP-SS periodicity of 80ms or less is necessary for IDLE/INACTIVE modes, which would increase overhead.
Observation 9
For CONNECTED mode, LP-SS is not assumed
Observation 10
Different values of M were supported between LP-SS and LP-WUS at least for M values larger than 1
LP-SS M candidates and the length of L were agreed
Observation 11
In the case of overlaid OFDM sequence without carrying information, OOK-based LP-WUR can be used to reduce inter-cell interference and improve detection performance

Proposal 1
For LP-WUS/LP-SS frequency resource configuration, reuse the point A and offset scheme described in TS 38.211 section 4.4.4
Proposal 2
At least, all UEs need to support LP-SS/LP-WUS within initial DL BWP without any frequency gaps
Proposal 3
Repetition of overlaid OFDM sequence is supported 
Proposal 4
LP-WUS OOK-4 M=4 is not supported for IDLE/INACTIVE modes
Proposal 5
LP-WUS OOK-4 M=4 is supported for CONNECTED mode only without additional preambles or synchronizations  and only UEs that meet the performance requirements for LP-WUS OOK-4 M=4 support LP-WUS OOK-4 M=4 based on an optional capability
Proposal 6
Remove the bracket of [LP-SS_Mvalue]
Remove the bracket of [{1,2,4} for FR1, FFS FR2]
Proposal 7
Before discussing the details on [LP-WUS/LP-SS_startRB_IDLE/INACTIVE] and [LP-WUS_startRB_CONNECTED] in higher layer parameters list, whether the scheme of point A is used or not should be discussed

Proposal 8
Regarding LP-SS_Binary_Seq in higher layer parameters list,
This parameter should be configured for both OOK-based and OFDM-based LP-WUR
Proposal 9
Regarding LP-SS_periodicityoffset in higher layer parameters list,
Remove the bracket of [320 ms,160ms]
This parameter should be configured for both OOK-based and OFDM-based LP-WUR
Proposal 10
Regarding LP-WUS_overlaidSeq_IDLE/INACTIVE and CONNECTED in higher layer parameters list,
This parameter should be configured for both OFDM-based LP-WUR and OOK-based LP-WUR for LP-WUS operation in IDLE/INACTIVE
Proposal 11
Before discussing the details on LP-WUS_overlaidSeq_IDLE/INACTIVE,LP-WUS_overlaidSeq_CONNECTED in higher layer parameters list, followings should be firstly discussed
How to send information via overlaid OFDM for LP-WUS in IDLE/INACTIVE modes and CONNECTED mode
Proposal 12
Before discussing the details on LP-SS_overlaidSeq in higher layer parameters list, followings should be firstly discussed
How to decide which overlaid OFDM to send in LP-SS
What pattern of overlaid OFDM should be sent
Proposal 13
Regarding WUS_codepoint_CONNECTED in higher layer parameters list,
Confirm the necessity of this parameter
Proposal 14
Regarding Max_codepoints_CONNECTED in higher layer parameters list,
Value range should be [2-32]

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

Agenda item:		9.6.1
Source:	Nordic Semiconductor ASA
Title:					On LP-WUS and LP-SS design
Document for:		Discussion and Decision

Conclusions 

Proposal-1: No maximum frequency gap is defined in specification(s) between SSB and LP-WUS/LP-SS.
Proposal-2: Consider set of configurable  values as defined by Table 1. 
Proposal-3: Revert WA, do not support 1 and 2 information bits for LP-WUS.
Proposal-4: To simplify LP-WUS design, support only payloads of 3 4 and 5bits for LP-WUS
take 32bit codeblock length as baseline.
define maximum of 4 LP-WUS codeblock length per M. Candidates could be 8,16,32,64.

Proposal-5: Support repetition of K segments (agreed in Alt 1) across the duration of OOK code-block.
Proposal-6: Set of supported combinations for IDLE mode is {LP-WUS-M, LP-SS-M}={1,1}, {2,2}, {2,4}.

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

Source:	Moderator (vivo)
Title:	Summary #1 of discussion on LP-WUS and LP-SS design    
Agenda Item:	9.6.1
Document for:	Discussion and Decision

Proposal 14
Regarding Max_codepoints_CONNECTED in higher layer parameters list,
Value range should be [2-32]


R1-2504437 Sharp 
Proposal 1: Ensure that two consecutive symbols within the same slot are always assigned for LP-WUS with M = 1 to support valid Manchester coding.
Proposal 2: Limit the duration of a single LP-WUS to a maximum of 2–3 consecutive slots.
Proposal 3: Confirm the working assumption to support 1-bit and 2-bit LP-WUS. 
Proposal 4: For 1-bit or 2-bit LP-WUS, apply small code block rate matching as defined in 3GPP TS 38.212.
Proposal 5: Do not support additional repetition after rate matching.
Proposal 6: Consider two methods for configuring LP-WUS resources:
   - BWP-specific mode, where LP-WUS resources are configured per BWP.
   - Cell-specific mode, where LP-WUS resources are configured at the cell level.



R1-2504575 Nordic Semiconductor ASA

Proposal-1: No maximum frequency gap is defined in specification(s) between SSB and LP-WUS/LP-SS.
Proposal-2: Consider set of configurable  values as defined by Table 1. 
Proposal-3: Revert WA, do not support 1 and 2 information bits for LP-WUS.
Proposal-4: To simplify LP-WUS design, support only payloads of 3 4 and 5bits for LP-WUS
take 32bit codeblock length as baseline.
define maximum of 4 LP-WUS codeblock length per M. Candidates could be 8,16,32,64.

Proposal-5: Support repetition of K segments (agreed in Alt 1) across the duration of OOK code-block.
Proposal-6: Set of supported combinations for IDLE mode is {LP-WUS-M, LP-SS-M}={1,1}, {2,2}, {2,4}.

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

Source:	Moderator (vivo)
Title:	Summary #2 of discussion on LP-WUS and LP-SS design    
Agenda Item:	9.6.1
Document for:	Discussion and Decision

Proposal 14
Regarding Max_codepoints_CONNECTED in higher layer parameters list,
Value range should be [2-32]


R1-2504437 Sharp 
Proposal 1: Ensure that two consecutive symbols within the same slot are always assigned for LP-WUS with M = 1 to support valid Manchester coding.
Proposal 2: Limit the duration of a single LP-WUS to a maximum of 2–3 consecutive slots.
Proposal 3: Confirm the working assumption to support 1-bit and 2-bit LP-WUS. 
Proposal 4: For 1-bit or 2-bit LP-WUS, apply small code block rate matching as defined in 3GPP TS 38.212.
Proposal 5: Do not support additional repetition after rate matching.
Proposal 6: Consider two methods for configuring LP-WUS resources:
   - BWP-specific mode, where LP-WUS resources are configured per BWP.
   - Cell-specific mode, where LP-WUS resources are configured at the cell level.



R1-2504575 Nordic Semiconductor ASA

Proposal-1: No maximum frequency gap is defined in specification(s) between SSB and LP-WUS/LP-SS.
Proposal-2: Consider set of configurable  values as defined by Table 1. 
Proposal-3: Revert WA, do not support 1 and 2 information bits for LP-WUS.
Proposal-4: To simplify LP-WUS design, support only payloads of 3 4 and 5bits for LP-WUS
take 32bit codeblock length as baseline.
define maximum of 4 LP-WUS codeblock length per M. Candidates could be 8,16,32,64.

Proposal-5: Support repetition of K segments (agreed in Alt 1) across the duration of OOK code-block.
Proposal-6: Set of supported combinations for IDLE mode is {LP-WUS-M, LP-SS-M}={1,1}, {2,2}, {2,4}.

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

Source:	Moderator (vivo)
Title:	Summary #3 of discussion on LP-WUS and LP-SS design    
Agenda Item:	9.6.1
Document for:	Discussion and Decision

Proposal 14
Regarding Max_codepoints_CONNECTED in higher layer parameters list,
Value range should be [2-32]


R1-2504437 Sharp 
Proposal 1: Ensure that two consecutive symbols within the same slot are always assigned for LP-WUS with M = 1 to support valid Manchester coding.
Proposal 2: Limit the duration of a single LP-WUS to a maximum of 2–3 consecutive slots.
Proposal 3: Confirm the working assumption to support 1-bit and 2-bit LP-WUS. 
Proposal 4: For 1-bit or 2-bit LP-WUS, apply small code block rate matching as defined in 3GPP TS 38.212.
Proposal 5: Do not support additional repetition after rate matching.
Proposal 6: Consider two methods for configuring LP-WUS resources:
   - BWP-specific mode, where LP-WUS resources are configured per BWP.
   - Cell-specific mode, where LP-WUS resources are configured at the cell level.



R1-2504575 Nordic Semiconductor ASA

Proposal-1: No maximum frequency gap is defined in specification(s) between SSB and LP-WUS/LP-SS.
Proposal-2: Consider set of configurable  values as defined by Table 1. 
Proposal-3: Revert WA, do not support 1 and 2 information bits for LP-WUS.
Proposal-4: To simplify LP-WUS design, support only payloads of 3 4 and 5bits for LP-WUS
take 32bit codeblock length as baseline.
define maximum of 4 LP-WUS codeblock length per M. Candidates could be 8,16,32,64.

Proposal-5: Support repetition of K segments (agreed in Alt 1) across the duration of OOK code-block.
Proposal-6: Set of supported combinations for IDLE mode is {LP-WUS-M, LP-SS-M}={1,1}, {2,2}, {2,4}.

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

Source:	Moderator (vivo)
Title:	Summary #4 of discussion on LP-WUS and LP-SS design    
Agenda Item:	9.6.1
Document for:	Discussion and Decision

Proposal 14
Regarding Max_codepoints_CONNECTED in higher layer parameters list,
Value range should be [2-32]


R1-2504437 Sharp 
Proposal 1: Ensure that two consecutive symbols within the same slot are always assigned for LP-WUS with M = 1 to support valid Manchester coding.
Proposal 2: Limit the duration of a single LP-WUS to a maximum of 2–3 consecutive slots.
Proposal 3: Confirm the working assumption to support 1-bit and 2-bit LP-WUS. 
Proposal 4: For 1-bit or 2-bit LP-WUS, apply small code block rate matching as defined in 3GPP TS 38.212.
Proposal 5: Do not support additional repetition after rate matching.
Proposal 6: Consider two methods for configuring LP-WUS resources:
   - BWP-specific mode, where LP-WUS resources are configured per BWP.
   - Cell-specific mode, where LP-WUS resources are configured at the cell level.



R1-2504575 Nordic Semiconductor ASA

Proposal-1: No maximum frequency gap is defined in specification(s) between SSB and LP-WUS/LP-SS.
Proposal-2: Consider set of configurable  values as defined by Table 1. 
Proposal-3: Revert WA, do not support 1 and 2 information bits for LP-WUS.
Proposal-4: To simplify LP-WUS design, support only payloads of 3 4 and 5bits for LP-WUS
take 32bit codeblock length as baseline.
define maximum of 4 LP-WUS codeblock length per M. Candidates could be 8,16,32,64.

Proposal-5: Support repetition of K segments (agreed in Alt 1) across the duration of OOK code-block.
Proposal-6: Set of supported combinations for IDLE mode is {LP-WUS-M, LP-SS-M}={1,1}, {2,2}, {2,4}.

TDoc file unavailable

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

Source:	Moderator (vivo)
Title:	Final summary of discussion on LP-WUS and LP-SS design    
Agenda Item:	9.6.1
Document for:	Discussion and Decision

Proposal 14
Regarding Max_codepoints_CONNECTED in higher layer parameters list,
Value range should be [2-32]


R1-2504437 Sharp 
Proposal 1: Ensure that two consecutive symbols within the same slot are always assigned for LP-WUS with M = 1 to support valid Manchester coding.
Proposal 2: Limit the duration of a single LP-WUS to a maximum of 2–3 consecutive slots.
Proposal 3: Confirm the working assumption to support 1-bit and 2-bit LP-WUS. 
Proposal 4: For 1-bit or 2-bit LP-WUS, apply small code block rate matching as defined in 3GPP TS 38.212.
Proposal 5: Do not support additional repetition after rate matching.
Proposal 6: Consider two methods for configuring LP-WUS resources:
   - BWP-specific mode, where LP-WUS resources are configured per BWP.
   - Cell-specific mode, where LP-WUS resources are configured at the cell level.



R1-2504575 Nordic Semiconductor ASA

Proposal-1: No maximum frequency gap is defined in specification(s) between SSB and LP-WUS/LP-SS.
Proposal-2: Consider set of configurable  values as defined by Table 1. 
Proposal-3: Revert WA, do not support 1 and 2 information bits for LP-WUS.
Proposal-4: To simplify LP-WUS design, support only payloads of 3 4 and 5bits for LP-WUS
take 32bit codeblock length as baseline.
define maximum of 4 LP-WUS codeblock length per M. Candidates could be 8,16,32,64.

Proposal-5: Support repetition of K segments (agreed in Alt 1) across the duration of OOK code-block.
Proposal-6: Set of supported combinations for IDLE mode is {LP-WUS-M, LP-SS-M}={1,1}, {2,2}, {2,4}.