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

Agenda item:	8.8.2
Source:	vivo
Title:	Further Discussion on DL Coverage in NTN
Document for:	Discussion and Decision

Conclusion
In this contribution, we have further discussed the DL coverage aspect. And we make the following observations and proposals:
Observation 1: If the coarse UE location is needed, the legacy mechanism, i.e., UE measurement report or the UE information request/response procedure, can be used to acquire the location. 
Observation 2: NW can decide the SMTC configuration for a specific UE based on the reported UE coarse location and knowledge of the beam hopping pattern. 
Proposal 1: If a new SMTC periodicity is not adopted and the number of SMTC configurations is not extended, UE apply legacy behaviour to select the SMTCs.
Proposal 2: If a new SMTC periodicity is adopted or the number of SMTC configurations is extended, RAN2 continue to discuss what assistance information can be provided.  
Proposal 3: For UE in CONNECTED state, NW configures the corresponding SMTCs based on the reported coarse location and no further enhancement is needed. 

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

Agenda Item:	8.8.2
Source: 	CATT
Title: 	Discussion on downlink coverage enhancements
Document for: 	Discussion and Decision

Conclusion
In this contribution, DL coverage enhancement is further discussed with the corresponding observations and proposals listed below:
Observation 1: Current TS 38.331 supports the MIB broadcasted with the same periodicity as SSB when the periodicity of SSB is larger than 80 ms.
Observation 2: It is up to RAN1 whether any change is needed for the resource configuration used for SIB1 scheduling.
Observation 3: By network implementation, the SI scheduling in the current Spec can adapt to the SSB periodicity of 160 ms.
Observation 4: The PCCH-Config in the current Spec can adapt to the extended SSB periodicity of 160 ms.
Observation 5: It is up to RAN1 to check whether any enhancement is needed for PRACH configuration.
Observation 6: The current common search space configuration provided via RRC signalling can adapt to the extended SSB periodicity of 160 ms.
Observation 7: Based on progress of RAN1, legacy UEs might successfully decode SIB1 when M=2. However, whether the legacy UE can decode SIB1 remains pending for M=1 and M=1/2.
Observation 8: RAN1 still needs to down select the options for informing UE about the Msg4 repetition and whether UE capability reporting is required.

Proposal 1: RAN2 considers support of per SSB configured SMTC list in SIB2 and SIB4.
Proposal 2: RAN2 confirms that the current RAN2 Spec can support the extended SSB periodicity of 160 ms. No enhancement on SI-scheduling, PCCH-Config, RACH configuration and Common SearchSpace is foreseen (unless required by RAN1).
Proposal 3: Postpone the discussion on link level enhancement, including access barring and early identification for Msg4 repetition, until RAN1 has clear progress.

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

Agenda Item:	8.8.2
Source: 	CATT
Title: 	Discussion on the need of cell (re)selection enhancements for DL CE
Document for: 	Discussion and Decision

Conclusion
In this contribution, need of cell (re)selection enhancements for DL CE is further discussed with the following proposal:
Proposal 1: At least from SSB periodicity extension point of view, RAN2 confirms to not further consider methods to allow UEs not supporting DL CE to down-prioritize or prevent re-selection to cells operating with DL CE.

TDoc file reading error

TDoc file reading error

TDoc file reading error

3GPP TSG-RAN WG2 #129bis	R2-2503884
St. Julians, Malta, May 19th – 23rd, 2025	

Source:                    	DENSO CORPORATION
Title:  	Discussion on NR NTN downlink coverage enhancements
Document for:        	Discussion and decision
Agenda Item:         	8.8.2		Downlink coverage enhancements

Summary and proposal
This paper discussed about consideration on cell barring for downlink coverage enhancement and proposed the following:
Proposal 1: RAN2 to introduce a new SMTC field to support multiple SMTC periodicities
Proposal 2: The maximum number of SMTCs per frequency could be 6
Proposal 3: SSB-index could be associated with each SMTC for both idle/inactive and connected state

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

Agenda item:		8.8.2
Source:		Lenovo
Title:		On DL-CE aspects for NR NTN
Document for:		Discussion

Conclusion
In this contribution we discuss issues and potential solutions in cell barring, cell reselection and timing of satellite beam activation/deactivation for DL-CE in NTN. The following observations are given:
Observation 1: To implement location/distance-based SMTC selection, UE needs to obtain at least one neighbour cell reference location and timely perform at least one distance calculation to determine which SMTC is to be selected.
And we propose:
Proposal 1: The assistance information to help idle/inactive mode UE in SMTC selection from gNB is serving cell SSB index. It is up to UE implementation whether to use the assistance information for SSB-based SMTC selection.
Proposal 2: If there is a need of UE request/capability indication for Msg4 PDSCH repetition (i.e. from RAN1), UE can include such request/capability indication in Msg3. FFS a RSRP threshold to trigger such indication.
Proposal 3: If a neighbor NTN cell is operating in DL-CE, an NTN-capable UE not supporting DL-CE may deprioritize the frequency of that cell for cell reselection.
Proposal 4: If a beam activation/deactivation pattern is configured by gNB, UE shall consider the propagation delay (e.g. half of UE-gNB RTT) when determine the timing of satellite beam activation/deactivation.

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

Agenda item:	8.8.2
Source:	Nokia, Nokia Shanghai Bell
Title:	Open issues for DL coverage enhancements
WID/SID:	NR_NTN_Ph3-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion
This document has made the following observations and proposals:
Observation 1: RRM requirements are not applicable in case more than 2 SMTCs are configured.
Proposal 1: SMTC4 is the fallback in case SMTC5 is not supported by the UE similarly as SMTC1 is fallback in case the UE does not support SMTC4.
Proposal 2: RAN2 to discuss how to restrics the UE freedom when legacy SSB and SMTC is configured in order to prepare for RAN4 reply that such prioritisation is needed for the solution to be acceptable.
Observation 2: The relevant information for configuring the UE to measure neighbor cells that are active in a scattered manner in the same or different satellites are: periodicity and time offset. 
Proposal 3: gNB may provide the neighbor cells SSB periodicities and time offsets in relation to the serving cell SSB in addition or as a replacement to the location.
Proposal 4: In case both location based and the coordinated procedure is adopted, RAN2 to discuss whether the assistance information type indicated is used to determine the network configuration.
Proposal 5: Location assistance information should consist of a center and a radius of a number of circles, each referring to one of the SMTCs in the new list.
Proposal 6: Only 6 additional SMTCs are needed.

3GPP TSG-RAN WG2 Meeting #130	R2-2503943
St. Julian’s, Malta, 19 - 23 May, 2025
Source: 	Huawei, HiSilicon, Turkcell
Title: 	Discussion on DL coverage enhancements
Agenda Item:	8.8.2
Document for:	Discussion and decision

Conclusion
This contribution discussed the DL coverage enhancements in Rel-19 NR NTN. Proposals are summarized as follows:
Proposal 1: For UEs in RRC_IDLE/RRC_INACTIVE, the SMTCs are associated with serving cell SSB indexes. It is up to UE to select the corresponding SMTC based on measured SSB.
Observation 1: UE coarse location report cannot be relied on to solve SMTC issue, as it depends on user consent while user consent is up to location regulations and proprietary mechanisms rather than standardized by SA3.
Observation 2: Event D1/D2 requires a serving cell reference location condition to be configured, and multiple events to be configured (each corresponds to one neighbour cell).
Proposal 2: UEs in RRC_CONNECTED reports assistance information (e.g. closest reference location) to assist SMTC/gap configuration.
Proposal 3: For SSB and CORESET multiplexing pattern 1, SIB1 repetition transmission period is 160ms if SSB periodicity is 160ms.

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

Agenda item:	8.8.2 
Source: 	ITRI
Title: 	Discussions on the assistance information for supporting location-based SMTC selection
Document for:	Discussion 
1	

Conclusion
This contribution discussion the assistance information to help RRC_IDLE/RRC_INACTIVE UE for SMTC selection. The following observations and proposals are provided:
For the assistance information for the association between SMTC and location:
Observation 1: UE in RRC_IDLE/RRC_INACTIVE state needs to measure neighbour cells in vicinity for cell reselection.
Observation 2: Use serving cell SSB ID as assistance information is not sufficient to help RRC_IDLE/RRC_INACTIVE UE perform SMTC selection.
Observation 3: Use reference location as the assistance information could help RRC_IDLE/RRC_INACTIVE UE to select SMTC associated with the neighbour cells in vicinity for cell reselection measurements.
Proposal 1: RAN2 to adopt reference location as the assistance information to help RRC_IDLE/RRC_INACTIVE UE to perform SMTC selection.
For the association of assistance information and SMTC:
Observation 4:  Providing reference location per SMTC is not sufficient to help RRC_IDLE/RRC_INACTIVE UE to perform SMTC selection.
Observation 5: Reference locations associated with cells could enable UE to select the surrounding cells neighbouring to the UE for the cell reselection measurements.
Proposal 2: Location information is provided per PCI as the assistance information to help RRC_IDLE/RRC_INACTIVE UE to perform SMTC selection. 
4	

TDoc file reading error

3GPP TSG-RAN WG2 Meeting #130	R2-2504010
St.Julians, Malta,  May 19th – 23rd , 2025	
Agenda item:		8.8.2 Downlink coverage enhancements
Title:		Remaining issues on DL CE in NR NTN
Source:		ETRI
Document for:		Discussion
1. 

Conclusions
Proposal 1: RAN2 to agreed that the maximum number of SMTCs that can be configured for UEs in RRC_IDLE and RRC_INACTIVE modes should be increased to six.
Observation 1: RSRP is not a reliable metric for SMTC selection in NR-NTN.
Proposal 2: RAN2 to introduce a location information-based SMTC selection mechanism to assist or complement RSRP-based selection for UEs in idle/inactive mode.
Observation 2: SSB index-based SMTC selection lacks robustness in NTN due to limited granularity, ambiguous beam overlaps, and minimal signal variation.
Proposal 3: RAN2 to introduce a reference location-based SMTC selection as the preferred mechanism for idle/inactive mode SMTC selection. 
Observation 3: SMTC window adjustment, as introduced in legacy NR-NTN, may not be necessary for neighbouring beams from a single satellite. 
Observation 4: Without location-based SMTC window adjustment, the UE may fail to receive SSBs from neighbouring beam-hopping cells originating from other satellites. 
Proposal 4: RAN2 to consider omitting SMTC window adjustment for neighbouring beam-hopping cells from the serving satellite, while applying SMTC window adjustment—similar to legacy NR-NTN—for neighbouring beam-hopping cells from different satellites.

3GPP TSG-RAN WG2#129bis											   R2-2504035
Malta, MT, May. 19th – 23rd, 2025
Agenda Item:	8.8.2
Source: 	NEC
Title:	        Details on SMTC enhancement
Document for:	 Discussion

Conclusion
In summary, we would like to share our view on downlink coverage enhancement with following proposals:
RAN2 adopt one of following two options:
Option1: introduce reference locations to be associated to the configured SMTCs. 
Option1a: a list of reference locations (0, 1 or multiple) is associated to a SMTC. 
Option 1b: 0 or 1 reference location is associated to each PCI in the PCI list linked to a SMTC.
UE shall always select the SMTCs without reference location. 
Option2: introduce per SSB SMTC configuration, maximum 4 SMTC per SSB. 

RAN2 confirm that we need the implementation option as follows for UE not supporting SMTC selection, legacy smtc4list-r17 should be kept for this purpose, and independent smtc6withRefLocationlist-r19 or SSBsmtc4list-rel19 should be introduced. 
•	“Configure Maximum 4 SMTC with small periodicity to cover all beam-hopping neighboring cells, in each period (SMTC occasion) up to UE implementation to measure a subset PCIs)”

RAN2 confirm SMTC selection out of maximum 6 SMTCs is only for idle and inactive mode UEs, and no need of capability bit.
For RRC connected mode, introduce an Additional SMTC periodicity, and associate to a subset of all configured SMTCs (form smtc4list-r17), other SMTCs is then associated to the legacy periodicity.
Introduce one capability bit to indicate support of additional SMTC periodicity.
For RRC idle and inactive mode, RAN2 discuss not to support additional SMTC periodicity.

3GPP TSG-RAN WG2 Meeting #130  	                            R2-2504057
St.Julians, Malta, May 19th – 23rd, 2025							                (Revision of R2-2502493)          

Agenda Item:	8.8.2
Source: 	Sony
Title:	SMTC impacts due to NTN downlink coverage enhancements
Document for:	Discussion 

Conclusion
We propose RAN2 to discuss following proposals:
Proposal 1: Neighbour cell’s location information is one of the assistance information for UE to perform SMTC configuration selection. 
Proposal 2: If UE agrees to share its finer location information, the UE’s location information can be shared with network and network can configure the appropriate SMTC configuration for the UE in RRC_CONNECTED.  



  

TDoc file reading error

TDoc file reading error

3GPP RAN WG2 Meeting #130	R2-2504178
St Julian’s, Malta, May 19th – 23rd 2025                                       
Agenda Item:	8.8.2
Source:	InterDigital
Title:	Downlink coverage enhancement for NTN
Document for:	Discussion, Decision

Conclusion
In this contribution the following observations and proposals are made regarding DL coverage enhancements:
Proposal 1: For UE specific PDSCH with Msg4 repetition activation, a special LCID value is defined to request the Msg4 PDSCH repetition by Msg3.
Proposal 2: For UE specific PDSCH with Msg4 repetition activation, an RSRP threshold is defined in SIB1 and a UE can request the Msg4 PDSCH repetition only when the measured RSRP is less than the RSRP threshold.

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


Agenda item:	8.8.2
Source:	Samsung
Title:	Open issues on Downlink Coverage Enhancement 
WID/SID:	NR_NTN_Ph3-Core
Document for:	Discussion and Decision

Conclusion
In this contribution we have the following proposals.
Observation 1: For SMTC selection in idle/inactive mode, an area bitmap w.r.t a common reference location can achieve a good trade-off between overhead and reliability/efficacy. 
Proposal 1: For SMTC selection in idle/inactive mode, discuss and select one approach for the assistance information per SMTC:
Option 1: a reference location, 
Option 2: an SSB bitmap,
Option 3: an area bitmap w.r.t a common serving cell reference location.
Proposal 2: For RRC_CONNECTED, the number of SMTCs configured per frequency layer in measurement object is at most 4 as legacy. 
Observation 2: For RRC_CONNECTED, NW can configure UE dedicated SMTC(s) for close neighbor cells based on UE location obtained/estimated from measurement report (e.g., event D1/D2, coarseLocationRequest), UE assistance information (e.g., coarseLocationRequest), TA report, NW-verified UE location, etc. No need of additional report of UE location information.
Proposal 3: For RRC_CONNECTED, no need of UE autonomous SMTC selection and no need of additional report of UE location information.
Proposal 4: No need to introduce new frequency priority to prevent/deprioritize DL CE cells in cell reselection for legacy UE.
Observation 3: For legacy UE, there is no backward compatible issue in terms of link level enhancement (PDCCH/PDSCH repetition).
Proposal 5: For DL CE PDCCH/PDSCH repetition, no need to introduce new barring bit(s).

3GPP TSG-RAN WG2 Meeting #130                                    	R2-2504312
St. Julians, Malta, 19 - 23 May 2025                                                                                  	              
	 
Agenda item:	8.8.2
Source:	Qualcomm Incorporated
Title:	Discussion on beam hopping with multiple SMTC offsets
Document for:	Discussion and Decision

Conclusion
Following proposals are made.
Proposal 1	Existing signaling ssb-PeriodicityServingCell in serving cell common configuration is sufficient to indicate the default SSB periodicity of a cell.
Proposal 2	Introduce location-based SMTC selection procedure.
Proposal 3	Each SMTC can be associated with a reference location of the intended neighbor beams that need to be measured by the UE.
Proposal 4	The UE chooses 4 SMTCs based on the shortest distances from UE’s location to reference locations and perform RRM measurements using existing procedure as if smtc4list-r17 is configured.
Proposal 5	The legacy UEs use smtc4list-r17 and new capable UEs ignore smtc4list-r17. For new capable UEs (i.e., UEs supporting location-based SMTC), new list is introduced to include PCI list, offset and associated reference location for each SMTC.

3GPP TSG-RAN-WG2 Meeting #130	R2- 2504357
St Julian’s, Malta, May. 19th – 23rd , 2025
Agenda item	:		8.8.2
Source	: 	Sharp
Title	: 	Discussion on DL coverage enhancement
Document for	:	Discussion and Decision

Conclusion
In this paper, we made following proposals;

Proposal.1: New SMTC configuration (i.e. SMTC5) is introduced for NTN DL CE.
Proposal.2: Maximum number of SMTC configuration is 6.
Proposal.3: The location-based SMTC selection is introduced to help UE to perform SMTC selection.

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

Agenda item:	8.8.2
Title:	Analysis on DL coverage enhancements due to extended SSB periodicity	 
Source:	CMCC
Document for:	Discussion
 

Conclusion
Observation 1: Each SSB-MTC4 element of the smtc4list in the same MeasObjectNR uses the same duration and periodicity parameter (derived from parameter periodicityAndOffset) from the smtc1 configuration, not supporting two  periodicities. 
Observation 2:  The IE smtc1 and smtc4list-r17 in the same MeasObjectNR can configure at most 4 SMTC occasions.
Proposal 1: RAN2 introduce new SMTC information element (smtc5list-r19) in MeasObjectNR for R19 DL CE capable UE.
Proposal 2: RAN2 assume maximum number of SMTCs that need to be supported is 6, wherein the maximum sequence size of smtc5list-r19 is 5 for supporting 6 SMTCs per frequency for idle/inactive UEs. 
Observation 3:  UE needs to know the association between STMC and SSB beam  in order to improve measurement accuracy and efficiency. UE can utilize serving cell timing to derive the index of SS block transmitted by neighbour cell when field deriveSSB-IndexFromCell is set to true. Nevertheless, UE without the capability need to be informed the SSB index corresponding to each SMTC configuration.
Proposal 3: For informing UE the association between STMC and SSB beam, SSB index of neighbour cells needs be included in assitantInfo of the new SMTC information element (smtc5list-r19). 
Observation 4: Network can provide assistance information (for Rel-19 UEs, not necessarily supporting DL CE) on the association between SMTC and location to help UE to perform SMTC selection for idle/inactive mode.
Proposal 4: The NW assistance information about the SSB beam location can be the SSB index of neighbour cells, or the neighbour cells’ reference location (rough location or for the one SSB beam fully coverage cell), or the preset azimuth/tilt Angle corresponding to the antenna array that emits the SSB beam, etc. 
Proposal 5: NW assistance information needs to be included in  assitantInfo of the new SMTC information element (smtc5list-r19) of MeasObjectNR corresponding to other SMTC parameter.  
Observation 5: It will be facilitate the accurate SMTC configuration by network for a given UE, based on the  assistance information reported from the UE. And UE can report the UE assistance information through existing signaling process. 
Proposal 6: Network dynamically configures SMTC for a given UE based on its assistance information.
Observation 6: There are two cases in cell re-selection scenario:
Case 1: Neighboring cells supporting DL CE and normal cells are deployed in different carriers
Case 2: Neighboring cells supporting DL CE and normal cells are deployed in co-channel manner
Proposal 7: For case 1, the UEs not supporting DL CE can realize de-prioritizing re-selection to cells operating with DL CE via legacy frequency priority.
Proposal 8: For case 2, to avoid the complexity and inter-cell interference of the introducing the cell-specific priority, keeping the frequency-specific priority is preferred. Conversely, the existing IntraFreqExcludedCellList IE can be utilized to enable the UEs not supporting DL CE to avoid the performance of the detection for PSS/SSS of cell with DL CE to reduce the amount of unnecessary coherent detection and UE power. 
Observation 7: For above repetition scenarios, repetition trigger condition (e.g. threshold for signal quality) and  Specific thresholds may be discussed by RAN1 since the values of the threshold need to be  simulated and evaluated by RAN1.
Proposal 9: RAN2 assume Msg3 can be used to indicate the capability/request for Msg4 PDSCH repetition.
Observation 8: These reserved codepoints 8 to 63 can be used to indicate UE capability/request for Msg4 PDSCH repetition.
Proposal 10:  RAN2 discuss two options for supporting Msg4 PDSCH repetition:
Option1: Adding the following codepoints in Msg3 to indicate UE capability/request for Msg4 PDSCH repetition:
- CCCH of size 48 bits for Msg4 PDSCH repetition of a RedCap UE;
- CCCH of size 64 bits for Msg4 PDSCH repetition of a RedCap UE;
- CCCH of size 48 bits for Msg4 PDSCH repetition for an eRedCap UE;
- CCCH of size 64 bits for Msg4 PDSCH repetition for an eRedCap UE;
- CCCH of size 48 bits for Msg4 PDSCH repetition, except for an (e)RedCap UE
- CCCH of size 64 bits for Msg4 PDSCH repetition, except for an (e)RedCap UE
- CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition, except for an (e)RedCap UE
- CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition, except for an (e)RedCap UE
- CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition of a RedCap UE
- CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition of a RedCap UE
- CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition of an eRedCap UE
- CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition of an eRedCap UE
Option 2: Adding the  following codepoints in Msg3 to indicate UE capability/request for Msg4 PDSCH repetition and sending two MAC CE simultaneously when Msg4 HARQ-ACK & Msg4 PDSCH repetition are supported:
- CCCH of size 48 bits for Msg4 PDSCH repetition of a RedCap UE;
- CCCH of size 64 bits for Msg4 PDSCH repetition of a RedCap UE;
- CCCH of size 48 bits for Msg4 PDSCH repetition for an eRedCap UE;
- CCCH of size 64 bits for Msg4 PDSCH repetition for an eRedCap UE;
- CCCH of size 48 bits for Msg4 PDSCH repetition, except for an (e)RedCap UE
- CCCH of size 64 bits for Msg4 PDSCH repetition, except for an (e)RedCap UE

	
3GPP TSG-RAN WG2 Meeting #130	R2-2504506
St. Julians, Malta, May 19th – 23rd, 2025
		 
Agenda item:	8.8.2
Source:	NERCDTV
Title:			  Further consideration on downlink coverage enhancements 
WI Code:       NR_NTN_Ph3-Core
Document for:	Discussion and Decision

Conclusion
Based on the above discussion, we give the following observation and proposals:
Observation 1: UE only needs to consider some of the SMTCs according to its location. 
Proposal 1: When gNB provides the association between location and SMTCs, the active/inactive states of the neighbor cells associated should also be considered.
Proposal 2: Legacy UEs should not be barred from accessing the DL CE cells if RAN1 concludes there is no impact on legacy UEs considering the link level enhancements.

3GPP TSG-RAN WG2 Meeting #130	R2-2504571
St. Julians, Malta, May 19th-23rd, 2025
	
Agenda Item:	8.8.2
Source: 	CSCN, Huawei, HiSilicon, ZTE corporation, Sanechips, CATT
Title: 	Discussion on Downlink Coverage Enhancements
Document for: 	Discussion and Decision

Conclusions
Based on above analyses, observations and proposals are summarized as follows.
Observation 1: There is no need for SMTC enhancement in the case of one single beam per cell. SSB-based SMTC configuration can only applied in the case of multiple beams per cell. 
Observation 2: Even the UE may at the edge of SSB or the overlapping area of SSBs, the UE can perform beam selection in a legacy way. Once a beam is selected, the associated SMTC of the serving cell SSB can be determined.
Observation 3: For SSB-based SMTC configuration, a SSB list with multiple SSBs configured for each SMTC is more reasonable. 
Observation 4: For intra-frequency and inter-frequency, configuring 4 SMTCs by NW is sufficient for UE measurement in RRC_CONNECTED. 
Observation 5: For inter-frequency, the inaccurate configuration of SMTC and gap becomes increasingly challenging in RRC_CONNECTED. 
Observation 6: Legacy events D1/D2 are no longer applicable for inter-frequency overlapping coverage scenario.
Observation 7: The clarification of condEvent/eventD1/D2 in the specification of R19 has no impact on legacy UEs. 
Observation 8: New event D3/D4 is more straightforward and clear and the design also aligns with legacy Event A specifications: Event D1/D2 aligns with Event A5 and Event D3/D4 aligns with Event A4.

Proposal 1: RAN2 to introduce SSB-based solution for SMTC enhancement in RRC_Idle/Inactive. 
Proposal 2: RAN2 to consider the following options for enhanced SMTCs and measurement gaps configurations for UEs in RRC_CONNECTED:
Option 1: Measurement report based solution (D1/D2 enhancement, new event D)
Option 2: UAI with multiple areas or locations. 

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

Agenda Item		:	8.8.2 
Source		:	LG Electronics Inc.
Title		:	Discussion on downlink coverage enhancement
Document for		:	Discussion and Decision
1. 

Conclusion
In this contribution, following statements are proposed:
Proposal 1	Provide the new SMTC periodicity as an extension of the SMTC4 list. 
Proposal 2	Do not provide serving cell’s SSB beam index as assistance location information, since the smtc selection based on this association is not applicable in single SSB beam scenario and has low accuracy.
Proposal 3	Provide assistance location information in the form of a neighboring cell reference location to UEs in RRC_IDLE/ INACTIVE mode to support the selection or prioritization of SMTCs for neighboring cell measurements.
Proposal 4	Location information is associated with each PCI in the SMTC4 list.
Proposal 5	The maximum number of SMTC configurations to be supported is six.
4. 

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

Agenda Item:	8.8.2
Source:	Ericsson
Title:	DL coverage enhancements
Document for:	Discussion/Decision

Conclusion
In the previous sections we made the following observations: 
Observation 1	In a typical NTN deployment due to the relatively large cell size, a UE does not need to be configured to measure all potential surrounding neighbour cells.
Observation 2	Without location information, the network may need to guess which is the most appropriate measurement configuration (e.g., SMTC) for a UE.
Observation 3	The UE Information procedure and reporting with multiple D1 events are suboptimal solutions to configure measurements (e.g., SMTCs) relevant to the UE’s current location.
Observation 4	RAN2 did not identify a need for access barring of legacy UEs in cells operating with DL CE and has agreed that the discussion is pending further progress in RAN1.
Observation 5	The “excluded cell lists” are not a suitable tool for preventing a UE to perform measurements on cells.

Based on the discussion in the previous sections we propose the following: 
Proposal 1	If RAN2 supports multiple SMTC periodicities and offsets, introduce a common solution for measurement configuration/selection in all RRC states.
Proposal 2	Adopt the same principle of SMTC selection for RRC_CONNECTED as for RRC_IDLE/INACTIVE.
Proposal 3	The UE is provided with multiple measurement configurations (e.g., SMTCs) to be selected from based on location criteria. After the decision, the UE reports its selection to the network.
Proposal 4	No enhancements to prevent legacy UEs from performing cell reselection to DL CE cells are pursued in Rel-19 (e.g., “excluded cell lists”).