3GPP TSG-RAN WG1 Meeting #120-bis	R1-2501731
Wuhan, People’s Republic of China, April 7th – 11th, 2025

Agenda Item:	5
Source:	Ericsson
Title:	Discussion on RAN2 LS on soft satellite switch with re-sync
Work Item:	NR_NTN_enh-Core
Document for:	Discussion

Conclusion
In the previous section we made the following observations: 
Observation 1	If ssb-TimeOffset is given a value that is not a multiple of a half-frame (5 ms), an SSB might end up in a sub-frame that is not allowed or does not match the SSB index, as specified in clause 4.1 of TS 38.213.
Observation 2	If ssb-TimeOffset is given a value that is not a multiple of a half-frame (5 ms), the MIB content might change within an SSB burst set, which is not allowed according to TS 38.331.
 
Based on the discussion we propose the following:
Proposal 1	Answer to RAN4 question 1: Configuring ssb-TimeOffset with values other than multiple of a half-frame (5 ms) may place the SSB in temporal positions not supported in the current specification (TS 38.213). Functional changes to RAN1 specifications should be avoided considering that Rel-18 is in maintenance phase since 1.5 years.
Proposal 2	Answer to RAN4 question 2: If ssb-TimeOffset has a value that is a multiple of a half-frame (5 ms), the half-frame indication and SFN indication bits can be configured according to the current specification (TS 38.213). Otherwise, it is currently unspecified how the half-frame indication and SFN indication bits would be configured.
Proposal 3	RAN1 to conclude that functional changes in Rel-18 RAN1 specifications to support soft satellite switch with resync should be avoided.
Proposal 4	RAN1 should study the use of time-shifted (CD-)SSB with a ssb-TimeShift granularity of 5 ms to confirm that it can be used for soft satellite switch with resync without RAN1 specification impact.

TDoc file unavailable

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

Source: 	ZTE Corporation, Sanechips
Title:	Discussion on LP-WUS UE RF
Agenda item: 	5
Document for:	Discussion and decision

Conclusions 
In this contribution, we have discussed issues on RAN4 LS and make the following proposals:
Proposal 1: Discuss and decide whether to reconsider the LP-WUS SNR target based on RAN4 MR NF assumption

Proposal 2: Capture the following information into the LS to RAN4
Chip rate could be 1, 2,4 if it refers to number of OOK symbols in an OFDM symbol 
RM coding and Manchester coding is supported, FFS code rate and details
Information bits for LP-WUS in idle mode is 5bits, and in connected mode is at least 8 bits
CRC bits is not needed

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

Source:	ZTE Corporation, Sanechips
Title:	Discussion on collision handling of SSB and RA occasion for LTM
Agenda Item:	5
Document for:	Discussion and Decision

Conclusion
In this contribution, we share our views on measurement related enhancements for Rel-19 LTM, and then proposals are provided as below:
Proposal 1: RAN1 should capture the following method recommended by RAN4 into Clause 8.1 of TS 38.213-i60 to clarify UE behavior when the collision between a SSB and a valid RO associated with different cells happens.
If the collision is outside MG, RACH shall be prioritized over SSB.
If collision happens within MG, it is up to UE implementation.
The corresponding draft CR can be found in Appendix. 

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

Source:	vivo
Title:	Discussion on L1 CLI measurement
Agenda Item:	5
Document for:	Discussion and Decision

Conclusion
In this contribution, we discussed the LS on L1 CLI measurement. The following proposals were made.
Proposal 1: Configuration of timeRestrictionForChannelMeasurements for legacy L1-RSRP or a similar configuration can be applied for L1-SRS-RSRP and L1-CLI-RSSI measurements.
Proposal 2: Similar to legacy L3 CLI measurement, an optional UE capability for FDM-ed DL reception and L1-SRS-RSRP measurement can be introduced.

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

Source:	CATT
Title:	Discussion on RAN4 LS on L1 CLI measurement
Agenda Item:	5
Document for:	Discussion and Decision

Conclusions 
In this contribution, we provide our views on CLI handling schemes with the following proposals.
Proposal 1: Support to apply parameter timeRestrictionForChannelMeasurement to enable time- domain restriction for L1-SRS-RSRP and/or L1-CLI-RSSI measurement.
Proposal 2: Define optional UE capability for FDM-ed DL reception and CLI-RSSI/SRS-RSRP measurement for L1-CLI measurement.

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

Source:	CATT
Title:	Discussion on LS on differentiation of mTRP and sTRP
Agenda Item:	5
Document for:	Discussion and Decision

Conclusions
In this contribution, we have discussed the remaining questions asked by RAN2 regarding differentiation of mTRP and sTRP. Based on the discussion, we have the following proposal and a draft reply LS is provided in [3]:
Proposal 1: On RAN2’s question regarding Question 2a, RAN1 responses to RAN2 that the answer is no. Whether RRC parameter applyIndicatedTCI-State is configured in ControlResourceSet can be used to indicate whether a serving cell is in sDCI mTRP operation or sTRP operation.

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

Source:	CATT
Title:	Discussion on LS on two TA enhancement for asymmetric DL sTRP/ UL mTRP
Agenda Item:	5
Document for:	Discussion and Decision

Conclusions
In this contribution, we have discussed the question asked by RAN4 regarding on two TA enhancement for asymmetric DL sTRP UL mTRP. Based on the discussion, we have the following proposals:
Proposal 1: RAN1 reply to RAN4 that “One downlink reference timing is supported and applied to both TAGs” is not applied for the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s).
Proposal 2: For the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s), two downlink reference timings for DL TRP and UL TRP can be considered.

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

Source:	CATT
Title:	Discussions on LS on number of beam measurements in the measurement report MAC-CE
Agenda Item:	5
Document for:	Discussion and Decision

Conclusions
In this contribution, we provided our view on the maximum number of beam measurement results that can be reported in MAC CE in an event-triggered measurement report. We have the following proposal:
Proposal: For NR Rel-19 event-triggered LTM beam reporting, for each report instance carried by MAC
CE, subject to UE capability, the maximum number of configured/activated should be L = 4
and the maximum number of beams M for each of the L cells should be M = 4. Consequently, the
maximum number of beam level measurement results that can be included in the MAC CE should be 16. 

3GPP TSG RAN WG1 #120bis		R1-2502018
Wuhan, China, April 7th – 11th, 2025
Agenda Item:	5
Source:	China Telecom
Title:	Discussion on RAN4 LS of DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP 
Document for:	Discussion and Decision

Conclusions 
In this contribution, we discussion the necessity for supporting two DL referencing timings for two TAGs in the asymmetric DL sTRP/UL mTRP scenario for Rel-17 ICBM, and the provided the following proposal.
Proposal 1:
From RAN1’s prospective, support two downlink reference timings are supported and applied to two TAGs for the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s) in Rel-19 asymmetric DL sTRP/UL mTRP scenario.

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

Source:	ZTE Corporation, Sanechips
Title:		Discussion on RAN4 LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP
Agenda Item:	5
Document for:	Discussion and Decision

Conclusion
In this contribution, we discussed in details of the required DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP according to the LS from RAN4. Upon that, we have the following observation and proposals.
Observation 1: For the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s), it is corresponding to Rel-17 ICBM configured in asymmetric DL sTRP/UL mTRP deployment scenarios.
Proposal 1: Support that two downlink reference timings can be applied to two TAGs for the scenario that UE is not configured with PL offset in joint/UL TCI state(s) in asymmetric DL sTRP/UL mTRP deployment scenarios.
Each DL reference timing is associated with one TAG, i.e., the first DL reference timing is associated with the first TAG, and the second DL reference timing is associated with the second TAG.
Baseline assumption is that Rx timing difference between two DL reference timings is no larger than one CP length, while it is subject to UE optional to support the case of larger than one CP length.
Proposal 2: When two downlink reference timings are applied to two TAGs for the scenario that UE is not configured with PL offset in joint/UL TCI state(s) in asymmetric DL sTRP/UL mTRP deployment scenarios, support to reuse the 1-bit “PRACH association indicator” field in DCI format 1_0 to indicate that:
If the 1-bit “PRACH association indicator” field in DCI format 1_0 is 0, the first DL reference timing is applied for PRACH transmission towards to serving cell PCI. 
If the 1-bit “PRACH association indicator” field in DCI format 1_0 is 1, the second DL reference timing is applied for PRACH transmission towards to activated additional cell PCI.
Note: Sent an LS to RAN4 to capture the above in RAN4 specifications.

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

Agenda Item:	5
Source:	Lenovo
Title:	Discussion on LS on differentiation of sTRP and sDCI mTRP
Document for:	Discussion

Conclusion
Proposal: Whether RRC parameter applyIndicatedTCI-State is configured in ControlResourceSet can be used to indicate whether a serving cell is in sDCI mTRP operation or sTRP operation.

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

Source: 	CMCC
Title:	Discussion on RAN4 LS on L1 CLI measurement
Agenda item:	5
Document for:	Discussion & Decision

Conclusion
In this contribution, we discuss the LS on L1 CLI measurement from RAN4, and the following proposals are made.
Proposal 1. Regarding Issue #1, reply to RAN4 that, the NW configuration of timeRestrictionForChannelMeasurement or a similar configuration will apply for L1-SRS-RSRP and/or L1-CLI-RSSI measurement.
Proposal 2. Regarding Issue #2, reply to RAN4 that, RAN1 will define optional UE capability for FDM-ed DL reception and SRS measurement.

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

Source: 	CMCC
Title:	Discussion on Reply LS on soft satellite switch with re-sync
Agenda item:	5
Document for:	Discussion & Decision

Conclusions
In this contribution, we provide our views on issues mentioned in the LS from RAN4. The proposal is provided below.

Proposal 1:
Without any further input from RAN2, there is no need to further discuss this issue or reply the questions from RAN4.

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

Agenda item:	5
Title:	Discussion on LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP
Source:	CMCC
Document for:	Discussion and Decision

1. 

Conclusion
In this contribution, we provide our views on the RAN4 LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP, and the following observation and proposal are made:
Observation 1: Two DL reference timings where each DL reference timing is associated with one TAG are needed for scenario#2 that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s).
Proposal 1: For the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE is provided with SSB-MTC-AddtionalPCI,
Two downlink reference timings are supported where each DL reference timing is associated with one TAG
The first DL reference timing is applied when PRACH is triggered towards serving cell PCI, and the second DL reference timing is applied when PRACH is triggered towards cell with additional PCI.
Baseline assumption is that the Rx timing difference between the two DL reference timings is no larger than CP length 
As an optional UE capability, Rx timing difference between the two DL reference timings can be assumed to be larger than CP length

4. 

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

Agenda item:	5
Title:	Discussion on LS on number of beam measurements in the measurement report MAC CE
Source:	CMCC
Document for:	Discussion and Decision

1. 

Conclusion
In this contribution, we provide our views on the RAN2 LS on number of beam measurements in the measurement report, and the following proposals are made:
Proposal 1: For Rel-19 event-triggered measurement report, the number of reported cells can be {1,2,3,4} configured by RRC parameter, and the number of reported beams per cell can be {1,2,3,4} configured by RRC parameter.
Proposal 2: If SSB/CSI-RS from serving cell are configured in the LTM resources for channel measurement, whether the reported cell includes serving cell depends on UE implementation.
Proposal 3: The measurement result of current beam for event evaluation is included in the measurement report, the reported current beam is not counted in the maximum N reported cells and M reported beams per cell, the maximum number of reported beams is (N*M+1).
Proposal 4: UE does not need to report the corresponding SSBRI/CRI in the beam report.

4. 

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

Source:	OPPO
Title:	Discussion on LS on differentiation of sDCI mTRP, mDCI mTRP and sTRP
Agenda Item:	5
Document for:	Discussion and Decision

Conclusion
With above being said, we suggest the following response to RAN2. 
Proposal 1: Please kindly consider our answers into the response LS to RAN2. 
Answer 1b: Not Applicable.
Answer 2a: Yes, there is. The parameter, i.e. applyIndicatedTCI-State for ControlResourcesSet seems not sufficient to separate sTRP and sDCI mTRP. 
Answer 2b: Network ensures that either all applyIndicatedTCI-State are configured for all PDCCH/PDSCH/PUCCH/PUSCH in all BWPs of all serving cells or there is not any applyIndicatedTCI-State configured for any PDCCH/PDSCH/PUCCH/PUSCH of any BWP of any serving cell.

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

Source:	OPPO
Title:	Discussion on LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP
Agenda Item:	5
Document for:	Discussion and Decision

Conclusion
With above being said, we suggest the following response to RAN2. 
Proposal 1: No, the agreement of one DL reference timing for both TAGs is not applied for the scenario mentioned in R4-2502667. 

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

Source:	OPPO
Title:	Discussion on RAN4 LS for L1 CLI measurement
Agenda Item:	5
Document for:	Discussion and Decision

Conclusion
This contribution concludes with following proposals:
Proposal 1: From RAN1 perspective, the RRC IE timeRestrictionForChannelMeasurement or a similar configuration does not apply for L1-SRS-RSRP and/or L1-CLI-RSSI measurement defined in Rel-19 duplex WI. 
Respond to RAN4 accordingly.

Proposal 2: RAN1 agrees in UE feature session to have an optional UE feature group for simultaneous reception of DL signals/channels and L1-SRS-RSRP measurement resource, and responds to RAN4 accordingly.
RAN1 discusses in duplex session the prioritization between the DL reception and Rel-19 L1-SRS-RSRP measurement if the simultaneous reception and measurement is not supported by the UE. 

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

Source:	OPPO
Title:	Discussion on LS on number of beam measurements in the measurement report MAC CE
Agenda Item:	5
Document for:	Discussion and Decision

Conclusion
In this contribution, we presented our views to the Questions in [1] and made the following proposals:
Proposal 1: Regarding the beam-level measurement reported in MAC CE for LTM Event:
For all the Events, the UE shall report the beam measurement of serving cell.
For event LTM 3 and 5, the UE can report up to K = 4 beam measurement of each candidate cell that satisfies the trigger condition and report up to N = 4 candidate cells that satisfy the trigger condition.
Thus, the maximum number of beam-level measurement of serving cell and candidate cells reported in MAC CE is up to 17.

3GPP TSG RAN WG1 #120bis    		                           R1-2502346
Wuhan, China, April 7th – 11th, 2025
Agenda item:		5
Source:			Samsung
Title:		Discussion on RAN4 reply LS on soft satellite switch with re-sync 
Document for:		Discussion and decision

TDoc file conclusion not found

3GPP TSG RAN WG1 #120bis    		                           R1-2502348
Wuhan, Hubei, China, April 7th – 11th, 2025 
Agenda item:		5
Source:			Samsung
Title:			Discussion on RAN4 reply LS on signal configuration LP-WUS and LP-SS
Document for:		Discussion and decision

TDoc file conclusion not found

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

Agenda Item:	5
Source:	Samsung
Title:	Discussion on LS reply to RAN4 on L1 CLI measurement
Document for:	Discussion
1. 

Conclusions
In this contribution, we make the following proposals:

Proposal 1: Support timeRestrictionForChannelMeasurements for L1-SRS-RSRP and L1-CLI-RSSI.
Proposal 2: Introduce 2 new FGs (optional with capability signaling) for Rel-19 SBFD
FG60-x1: Simultaneous reception of DL signals/channels and CLI-RSSI measurement resource
FG60-x2: Simultaneous reception of DL signals/channels and SRS-RSRP measurement resource

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

Agenda item:		9.3.3
Source:	Nokia, Nokia Shanghai Bell
Title:	Discussion on RAN4 LS on CLI measurements
Document for:		Discussion and Decision

Conclusions
Proposals: 
Proposal 1:	RAN1 to reply to RAN4 that the higher layer parameter timeRestrictionForChannelMeasurements applies to L1-SRS-RSRP and L1-CLI-RSSI measurements.
Proposal 2:	RAN1 to reply to RAN4 that RAN1 will define optional UE capabilities to support the simultaneous FDM-ed DL reception and L1-SRS-RSRP and L1-CLI-RSSI, respectively.

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

Agenda Item:	5 
Source:	Ericsson
Title:	Discussion on RAN4 LS on L1 CLI measurement
Document for:	Discussion, Decision

1	

Conclusion
Based on the discussion in the previous sections we propose the following:
Proposal 1	RAN1 to reply to Question #1 as follows:
Yes, the NW configuration timeRestrictionForChannelMeasurement will apply for L1-SRS-RSRP and L1-CLI-RSSI measurement.
Proposal 2	RAN1 to reply to Question #2 as follows:
Yes, RAN1 will define an optional UE capability for FDM’d DL reception and measurement of L1-SRS-RSRP.

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

Agenda item:	5
Source:	Xiaomi
Title:	Discussion on RAN4 LS on L1 CLI measurement
Document for:	Decision

Conclusions
In this contribution, we provide our views on LS on L1 CLI measurement from RAN4, and the following proposals are made:
Proposal 1: Inform RAN4 that NW configuration of timeRestrictionForChannelMeasurement or a similar configuration will apply for L1-SRS-RSRP measurement.
Proposal 2: Inform RAN4 that NW configuration of timeRestrictionForChannelMeasurement or a similar configuration will not apply for L1-CLI-RSSI.
Proposal 3: Inform RAN4 that RAN 1 will define optional UE capabilities for FDM-ed DL reception and L1-SRS-RSRP measurement, and FDM-ed DL reception and L1-CLI-RSSI measurement respectively.

TDoc file reading error

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

Agenda item:		5
Source:	Nokia
Title:	Discussion of LS response related to soft satellite switch with re-sync
WI code:	NR_NTN_enh-Core
Release:	Rel-18
Document for:		Discussion and Decision

Conclusion
In this contribution we have discussed the LS from RAN1 on soft satellite swith with re-sync and we have reached the following observations and proposals:
Observation 1: From UE point of view, a frame will always be having a duration of 10 ms, and there is no possibility from RAN1 to change this.
Observation 2: The parameter “ssb-TimeOffset” cannot offset the location of the SSB in the frame, according to TS38.213. 
Observation 3: The terms ssb-TimeOffset, t-ServiceStart and t-Service are neither defined nor mentioned in current RAN1 Rel-18 specifications.
Proposal 1: Provide a response for question 1 to RAN4 and RAN2 that since the parameter ssb-TimeOffset is not defined in RAN1 specifications, there are no procedures to shift or adjust the timing of the SSBs.
Proposal 2: Provide a response for question 2 to RAN4 and RAN2 that since the parameter ssb-TimeOffset, t-ServiceStart and t-Service are not defined in RAN1 specifications there is no special handling of the SFN indication bits during this time period.

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

Agenda Item:	5
Source:	Ericsson
Title:	Discussion on RAN2 LS on number of beam measurements in the measurement report MAC CE 
Document for:	Discussion, Decision
1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	By including measurement results for multiple beams from the same LTM Candidate Cell, the network can learn if there are multiple beams with high RSRP in the cell or not.
Observation 2	By including measurement results from additional LTM candidate cells, the network can learn if there is another LTM candidate cell that has several beams with high RSRP.

Based on the discussion in the previous sections we propose the following:
Proposal 1	For event triggered LTM measurement reports, support UE to include measurement results for up to 4 beams per cell, for up to 4 cells. 
 

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

Agenda Item:	5

Source:	Apple Inc.
Title:	Discussion on the RAN4 LS on LP-WUS UE RF
Document for:	Discussion/Decision

Conclusion
Proposal: Update the RAN1#117 agreement as follows and send an LS to RAN4:
Agreement
For evaluation of LP-WUS and LP-SS design to achieve coverage of PUSCH for message3 from RAN1 perspective, at least the following SNR values should be considered: 
SNR=-4dB for IM+NF of LR=18dB
SNR=0dB for IM+NF of LR=13.5dB
SNR=-3dB for NF of LR = NF of MR+ 8dB
SNR= -0.5dB for NF of LR = NF of MR+ 5dB
SNR=2dB for NF of LR = NF of MR+ 2dB
Note 1: The NF of MR is assumed as 7dB

A draft reply LS is provided in our companion contribution R1-2502591.

Appendix: Link Budget Analysis

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

Agenda Item:	5
Source:	Apple
Title:	Discussion on RAN4 LS on RRM aspects for LB CA via switching
Document for:	Discussion/Decision

Conclusion
In this contribution, we made the following observations/proposals on low-band carrier aggregation via switching:
Observation 1: Considering that SSB patterns are known to network and configured on serving cell basis, therefore, it would be feasible for network to ensure alignment between switching pattern configuration and at least the SSB configuration in PCell in order to protect SSB by avoiding the conflict

Proposal 1: Network is expected to at least avoid conflict between the SSB configuration on PCell and the switching pattern configuration to the UE
UE is not expected to handle such conflict

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

Agenda item: 		5
Source:	Nokia
Title:	Discussion on Reply LS on collision between SSB and RA occasion for LTM
Document for:		Discussion and Decision

Conclusion
In this contribution, we provide our views on the potential RAN1 actions based on the RAN4 reply on collision between SSB and RA occasion for LTM. The following proposal have been made:
Proposal 1: For RAN1, it should be sufficient to specify that RACH shall be prioritized over SSB if the collision occurs outside of the MG in TS 38.213.
Proposal 2: RAN1 should inform RAN2 about this reply from RAN4 for any potential RAN2 specification impacts. 

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

Agenda item: 		5
Source:	Nokia
Title:	Discussion on LS on number of beam measurements in the measurement report MAC CE
Document for:		Discussion and Decision

Conclusion
In this contribution, we provide our views on the RAN2 question on the number of beam measurements in the measurement report MAC CE. The following proposal have been made:
Proposal 1: In the reply to RAN2, it should be mentioned that, from a RAN1 perspective, the maximum number of measurement results that can be included in the MAC CE should align with the maximum used for gNB-scheduled L1 measurement reporting, i.e., 16.

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

Source:	NTT DOCOMO, INC.
Title:	Discussion on LS on L1 CLI measurement
Agenda Item:	5
Document for: 	Discussion and Decision

Conclusion
In this contribution, we discussed potential enhancements on CLI handling for SBFD. Based on the discussion we made the following observation and proposals.
Proposal 1: The configuration of timeRestrictionForChannelMeasurement is also applied to L1-CLI-RSSI/L1-SRS-RSRP measurement.
If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the UE shall compute L1-CLI-RSSI/L1-SRS-RSRP value reported in uplink slot n based on only the L1-CLI-RSSI/L1-SRS-RSRP measurement resource, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.
If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall compute L1-CLI-RSSI/L1-SRS-RSRP value reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of L1-CLI-RSSI/L1-SRS-RSRP measurement resource associated with the CSI resource setting.

Proposal 2: Introduce a new capability for FDM-ed DL reception and L1-SRS-RSRP measurement.

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

Agenda Item:	5
Source:	Ericsson
Title:	Discussion on RAN4 LS on LP-WUS UE RF
Document for:	Discussion
1	

Conclusions
In this document we discuss the RAN4 LS on UE RF [1] and propose the following
RAN1 should discuss if/how to consider SNR of -6dB (or -5.7dB without rounding) in evaluations for LP-WUS/LP-SS design.
For the RAN4 question on signal configuration details of LP-WUS and LP-SS for both idle/inactive and connected modes, provide the relevant RAN1 agreements (including any additional relevant agreements made in RAN1#120bis) in LS reply to [1]. 
4	

​3GPP TSG RAN WG1 #120-bis			R1-2502826
Wuhan, China, April 7th – 11th, 2025
	
Agenda item:	5
Source: 	Qualcomm Incorporated
Title: 	Discussion on response to RAN4 LS on LP-WUS UE RF
Document for:	Discussion and Decision

Conclusions
In this contribution, we have provided the following observations and proposals:
Observation 1: The entry/exit condition for LP-WUS monitoring in idle/inactive mode and UE specific signal allow network to control the actual coverage of LP-WUS irrespective of the targeted coverage.
Proposal 1: RAN1 does not need to consider new SNR for LP-WUS and LP-SS design.
Proposal 2: RAN1 responds to RAN4 questions based on the following assumptions
Set 1 value for OOK based LP-WUR
Set 2 value for OFDM based LP-WUR
Proposal 3: Answers to RAN4 questions:
Chip rate of OOK sequences
Answer: For SCS 30kHz, the OOK chip rate is 28k, 56k and 112k OOK chips/sec for M=1, 2, and 4 respectively. For the other SCS values, the OOK chip rate can be scaled accordingly.
Length of information bits of OOK sequences
Answer: For the OOK LP-WUS for Set 1 assumption, evaluations in TDL-C channels shows that to achieve 1% FAR and 1% MDR at SNR = -3dB
For SCS 30kHz, 16 OFDM symbols are needed if the network transmits a OOK sequence to indicate the UE to wake up the main radio (MR) for PDCCH monitoring and transmits nothing if the network does not indicate the UE to wake up the MR for PDCCH monitoring. This corresponds to 8, 16 and 32 bits for M=1, 2 and 4, respectively.
For SCS 30kHz and a single codepoint is associated with the LP-WUS MO, 2 OFDM symbols are needed if the network transmits a first OOK sequence to indicate the UE to wake up the MR for PDCCH monitoring and transmits a second sequence which is orthogonal to the first sequence to indicate the UE to not wake up the MR for PDCCH monitoring. This corresponds to 1, 2 and 4 bits for M=1, 2 and 4, respectively.
Coding
Answer: LP-WUS information carried by OOK is based on, for more than 2 information bits: RM coding as in section 5.3.3.3 of 38.212, for 2 information bits: coding as in section 5.3.3.2 of 38.212, and for 1 information bit: repetition as in section 5.3.3.1 of 38.212. For LP-WUS information carried by OOK, coding is not supported.
Whether CRC will be configured
Answer: CRC is not supported for LP-WUS.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502827
Wuhan, China, April 7th – 11th, 2025
Agenda item:	5
Source: 	Qualcomm Incorporated
Title: 	Discussion on LS reply on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP 
Document for:	Discussion/Decision
1 

Conclusion 
In this contribution, we discuss the RAN4 LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP, and have the following proposal:
Proposal 1: Reply to RAN4 with the following answer: 
No, two downlink reference timings are supported for the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s) where each downlink reference timing is applied to a TAG.
4 

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

Agenda Item:	5
Source:	Google
Title:	Discussion on RAN4 LS on collision between SSB and RA occasion for LTM
Document for: 	Discussion

Conclusion
According to the above discussion(s), we have the following observation(s) and/or proposal(s). 
Observation 1: Collision handling of SSB and RA occasion associated with different cells should only consider whether the collision is inside measurement gap or outside measurement gap. 
Observation 2: Collision handling of SSB and RA occasion associated with different cells can apply for both intra-band and inter-band cases. 
Observation 3: Collision handling of SSB and RA occasion associated with different cells can be performed upon a SSB and a RO is overlapped in time domain. 
Proposal 1: Endorse the Text Proposal 1 in TS 38.213, according to the reply LS from RAN4 (R1-2501697).  

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

Agenda Item:	5 
Source:	Ericsson
Title:	Discussion on RAN4 LS on switching periods for low-low band switching
Document for:	Discussion, Decision

1	

Conclusion
Based on the discussion in the previous sections we propose the following:
Proposal 1	RAN1 to define a switching gap for switching from FDD to SDL bands in the last N1 symbols of a slot and for switching from SDL to FDD bands in the last N2 symbols of a slot.
FFS: Value(s) of N1 and N2 depending on RAN4 agreements, and whether N1 and N2 are the same or can be different, and whether N1 and/or N2 are the same for both UL and DL, or can be different.
Proposal 2	Support RRC configuration of N1 and N2
Proposal 3	The UE shall omit UL transmission and DL reception during the switching gap of N1 or N2 symbols.
Proposal 4	Send an LS to RAN4 with the above agreements

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

Agenda Item:	5 
Source:	Ericsson
Title:	Discussion on RAN4 LS on RRM aspects for LB CA via switching
Document for:	Discussion, Decision

1	

Conclusion
Based on the discussion in the previous sections we propose the following:
Proposal 1	For lowband-lowband CA via switching, a UE is semi-statically configured with switching pattern defined by a bitmap of length L, where each bit corresponds to a slot at 15 kHz SCS. The first bit of the bitmap corresponds to the first slot of the first radio frame (SFN 0). The pattern is assumed to be periodic with periodicity of L slots.
Proposal 2	For lowband-lowband CA via switching, the length of the bitmap for configuring the switching pattern is at least L = 40 slots @15 kHz SCS (4 radio frames).

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

Agenda Item:	5
Source:	Huawei, HiSilicon
Title:	Discussion on RAN4 LS on L1 CLI measurement
Document for:	Discussion and Decision

Conclusions
In this contribution, the following are proposed:
Proposal 1: From RAN1 perspective, the higher layer parameter timeRestrictionForChannelMeasurement also applies for L1-SRS-RSRP and/or L1-CLI-RSSI measurement.
Proposal 2: RAN1 informs RAN4 that an optional UE capability will be defined for FDM-ed DL reception and SRS measurement.

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

Agenda Item:	5
Source:	Huawei, HiSilicon
Title:	Discussion on the RAN2 LS on number of beam measurements in the measurement report MAC CE
Document for:	Discussion and Decision

Conclusions
Based on the discussion above, we had following proposals.
Proposal 1: UE can report the maximum number of cells (L), maximum number of beams per cell (M) and maximum number of beams across cells (M × L) it can report in a MAC CE. 
Proposal 2: The value ranges of L={1,2,3,4}, M={1,2,3,4} and M×L={1,2,3,4,6,8,9,12,16} are same as the those defined in FG45-1 and 45-1a for NW-triggered SSB-based L1-RSRP measurement and reporting in Rel-18 LTM. 

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

Agenda Item:	5
Source:	Huawei, HiSilicon
Title:	Discussion on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP
Document for:	Discussion and Decision

Conclusion
In this contribution, we have provided our views on the RAN4 LS on UE RF issues for Rel-19 MIMO enhancement, and made the following proposal: 
Proposal 1: reply to Question 1:
“One downlink reference timing is supported and applied to both TAGs” are not applied for the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s).  

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

Agenda Item:	5
Source:	Huawei, HiSilicon
Title:	Discussion on differentiation of sDCI mTRP, mDCI mTRP and sTRP
Document for:	Discussion and Decision

Conclusion
The replies to the questions from the LS are summarized below: 
Reply to Question 2a: RAN1 understanding is that the highlighted sentence is incorrect as applyIndicateTCI-State maybe present for a sTRP-based transmission scheme. 
Reply to Question 2b: No spec change is needed to ensure that sDCI mTRP cell and sTRP cell are not configured in the same cell list since the cells in the same cell list always share the same indicated TCI-state(s) and, therefore, have the same number of indicated TCI-states, and, consequently, either all are sTRP cells or all are sDCI-based mTRP cells.

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

Agenda Item:	5
Source:	Huawei, HiSilicon
Title:	Discussion on the RAN4 LS on soft satellite switch with re-sync
Document for:	Discussion and Decision

Conclusion
According to the above discussions, we have the proposals to answer RAN4 questions: 

Proposal 1: ssb-TimeOffset should be configured with values that are multiples of 5ms to keep the legacy SSB pattern. 
Proposal 2: Without changing the legacy SSB pattern within a half radio frame, the timing of the temporarily shifted SSB during [t-ServiceStart, t-Service] is indicated based on the IE systemFrameNumber in MIB of shifted SSB, the LSB of SFN bits and half frame bit in the PBCH payload of shifted SSB. 
.

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


Source:	Moderator (CATT)
Title:	Summary on LS on differentiation of sDCI mTRP and sTRP
Agenda Item:	5
Document for:	Decision

TDoc file conclusion not found