3GPP TSG RAN WG2 Meeting #130            	                      R2-2503418
St Julian’s, Malta, 19-23 May 2025
Agenda Item:	8.10.3
Source:	Xiaomi
Title:	Discussion on other aspects of Rel-19 SON/MDT
Document for:	Discussion and Decision

Conclusion
In this contribution, we propose:
Proposal 1: RAN2 to introduce measured distance from UE to moving reference location of serving cell, and measured distance from UE to moving reference location of candidate cell in RLF report when RLF/HOF happens, based on which the network computes the distance.
Proposal 2: RAN2 to define a new CGI-Info-Logging-r19 IE to log trackingAreaList information for the support of MRO for NTN.
Proposal 3: When the UE is in IDLE/INACTIVE and the UE cannot obtain its location, the UE stops MDT logging for NTN.

3GPP TSG RAN WG2 #130                                                                                 R2-2503586
St. Julian’s, Malta, May 19th – 23rd, 2025
		
Source:	CATT
Title:	MHI Enhancement for SCG Activation and Deactivation
Agenda Item:	8.10.3
Document for:	Discussion and Decision

Conclusion
According to the discussion in section 2, the proposal is summarized as follows:
Proposal 1: UE logs the accumulated time for SCG activation for a PSCell in MHI if SCG activation/deactivation are performed multiple times for the PSCell.

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

Agenda item:	8.10.3
Source:	Nokia
Title:	SON/MDT enhancements for network slicing, MHI and NTN
WID/SID:	NR_ENDC_SON_MDT_Ph4-Core – Rel-19
Document for:	Discussion and Decision
1	

Conclusion
This document has made the following observations and proposal for SON/MDT enhancements for slicing:
Observation 1.1: New enhancements in logged MDT are needed on how the UE used the sliced based cell reselection parameters.
Observation 1.2: A flag that the highest rank NSAG ID was not used for cell reselection does not help the NG-RAN to optimize the slice-based cell reselection parameters, as NG-RAN cannot know the NSAG IDs and their priorities in the UE.
Proposal 1: Enhance the logged MDT report with all the NSAG IDs that did not lead to successful cell reselection and the NSAG ID (or the lack of any NSAG ID) that was used to select a new cell. 

This document has made the following observation and proposal on MHI Enhancement for SCG Deactivation/Activation:
Observation 2: The information of SCG activation and/or deactivation, e.g., the relative time in SCG activated state together with additional assistance information related to the condition(s) for SCG activation/deactivation, could help the network understand the actual utilization of Dual Connectivity and further optimize the configuration of Dual Connectivity.
Proposal 2: It is proposed to include additional assistance information related to the condition(s) for SCG activation/deactivation, in MHI such as DL and/or UL volume per second which was transmitted or received by UE during the SCG activation time for the given PSCell.

This document has made the following observations and proposals on SON/MDT for NTN:
Observation 3.1: Dynamic Grant based RACH-less access for NTN mobility involves optimization in multiple areas. It requires a lot of information to be transferred to the UE prior to or along with the HO Command which are processed by the UE to realize RACH-less access of the target Cell.
Observation 3.2: The DG based RACH-less access defined for NTN mobility could lead to sub-optimal scenarios (near failure scenarios) which would require constant measurement, monitoring and performance optimization.
Observation 3.3: The DG based RACH-less access defined for NTN mobility can lead to many failure scenarios related to NTN specific parameters that would require some MRO enhancements.
Proposal 3.1: RAN2 to consider enhancing RLF Report and SHR for DG based RACH-less access for NTN with the following additional parameters:
PDCCH Monitoring Time Until Success
No of PUSCH Attempts Until Success
Full TA, Doppler estimation and PC control parameters used during PUSCH transmissions
Target NTN-config in SIB19
Target NTN-config in RRC Reconfiguration message
New Cause value specific to NTN RACH-less access failure for RLF Report
New Cause value specific to NTN RACH-less HO (for SHR)

Proposal 3.2: Define a new SHR trigger (based on PDCCH monitoring time and/or number of PUSCH attempts) for the UE to log the enhancements measurements specific to NTN RACH-less access.

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

Agenda item:	8.10.3
Source:	China Telecom
Title:	MRO for intra-NTN mobility
Document for:	Discussion

Conclusions
Based on the discussion above, we have the following proposal.
Proposal 1: Regarding MRO for CHO with a location-based trigger condition, include measured distance from UE to moving reference location of serving cell, and measured distance from UE to moving reference location of candidate cell when RLF occurred in the RLF report (i.e. option 2).

3GPP TSG-RAN WG2 Meeting#130	R2-2503915
Malta, MT, May 19 – 23, 2025

Agenda item:	 8.10.3
Source:		Lenovo
Title:		Discussion on MRO for intra-NTN mobility
Document for:		Discussion and Decision
1	

Conclusion
In this paper, MRO enhancements for intra-NTN mobility are discussed. We have the following proposal:
Observation: RAN3 agreed no further discussion on time-based CHO, e.g. the UE does not need to report the absolute UTC time when RLF/HOF happens in RLF report for time-based CHO in NTN.
Proposal 1: For location-based CHO in NTN, RLF report can be enhanced to include measured distance from UE to moving reference location of serving cell, and measured distance from UE to moving reference location of candidate cell when RLF/HOF occurred.

3GPP TSG-RAN WG2 Meeting #130	R2-2504237
St Julian's, Malta, 19 – 23 May, 2025

Title: 	Discussion on SONMDT for others
Source: 	Huawei, HiSilicon
Agenda item:	8.10.3
Document for:	Discussion and Decision

Conclusion
Based on the discussions above, we have the following observations and proposals:
Observation 1: The UE always has a valid GNSS position in RRC connected, and is totally capable of calculating the distance with any candidate cell for SON purpose regardless of whether location-based CHO is triggered/executed or not.
Observation 2: The UE may not camp on a cell supporting any or all of the intended NSAGs, and the network parameters may need to be adjusted.
Observation 3: To address the issue mentioned in observation 1, the UE can make the network aware of the issue so that the UE to find the correct cell during the slice-based cell (re)selection procedure.

Proposal 1: It is proposed RAN2 to agree on introducing the distance from UE to serving cell and candidate cell.
Proposal 2: It is proposed RAN2 to agree on introducing the following report type in logged MDT configuration:
highest ranked cell or best cell does not support any or all of the intended NSAGs
Proposal 3: It is proposed RAN2 to agree on including the NSAG information received from NAS in logged MDT report.
Proposal 4: It is proposed RAN2 to discuss whether to address the case where the UE fall backs to legacy cell reselection procedure from slice-based cell reselection.
Proposal 5: It is proposed RAN2 to discuss possible solutions, including:
addition of a new report type related to P3 in logged MDT configuration
addition of a fallback indicator in logged MDT report
Proposal 6: It is proposed RAN2 to adopt the percentage ratio or accumulated time for UE in SCG deactivated state in MHI.

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

Agenda item:	8.10.3
Source:	Samsung
Title:	Discussion on NTN, slicing and other open issues 
Document for:	Discussion and Decision

Conclusion
Based on the discussion, we have the following observation and proposals.
MRO for NTN
Proposal 1: UE reports following additional information in RLF report for NTN related failures
Timing Advance reported in the Timing Advance Report MAC CE, if it was triggered during the random access procedure during a handover.
A flag indicating whether T430 had expired when RLF or HOF occurred.
Information related to satellite position.

Proposal 2: UE may log tracking area list in CGI-Info-Logging in various SON/MDT reports.
Slice-based cell reselection and logged MDT
Observation 1: It is possible to determine the following using the existing logged MDT framework
Whether legacy cell reselection is used or NSAG based cell reselection is used 
The NSAG(s) used for the NSAG based cell reselection
Whether the UE has reselected to an optimal cell supporting the NSAG(s) triggering the NSAG based cell reselection.
Proposal 3:RAN2 to inform RAN3 that it is possible to address the scenario of UE supporting slice-based cell reselection not finding any suitable cell in the frequencies corresponding to the highest ranked NSAG, without any enhancement of logged MDT.
Open Issues in TS 36.331
Proposal 4: For Open issue LTERRC-1: the following condition is not required.
3>	if the last RRCReconfiguration message including the reconfigurationWithSync for the SCG was received to enter the PSCell in which the SCG failure was declared:
Observation 2: With a single container, optional presence and order of each of perRAInfoListNR, perRAInfoList-v1660-NR, perRAInfoList-v1840-NR, can’t be communicated to the network.
Proposal 5: For Open issue LTERRC-3: PerRAInfoList-r16, PerRAInfoList-v1660 and PerRAInfoList-v1800 are carried in separate containers.

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

Agenda Item:	8.10.3 
Source:	Ericsson
Title:	Discussion on SON-MDT enhancements for Slicing and NTN
Document for:	Discussion/Decision

Conclusion
In the previous sections we made the following observations: 
Observation 1	Legacy logged MDT measurements are sufficient for identifying coverage gaps in a given frequency.
Observation 2	Legacy logged MDT measurements contains serving cell information of a given UE and network can identify if any slice specific cell reselection is configured in the cell. Hence, network can estimate which cell UE should re-select to continue to have acces to a specific slice and whether the target cell provides sufficient coverage or not.
Observation 3	Inclusion of slice ID without additional information such as UE location and measurement results is not beneficial to the network.
Observation 4	Both options can solve the problem, however option 1 increases the RLF report message size and option 2 requires additional UE implementation effort.
Based on the discussion in the previous sections we propose the following:
Proposal 1	The scenario described in the LS may occur only if there is a coverage hole in the frequencies corresponding to the highest ranked NSAG.
Proposal 2	The scenario identified in RAN3 can be supported using legacy logged MDT procedure, no further enhancements are needed.
Proposal 3	RAN2 to agree that, due to the need for additional analysis to include slice information in SON report and time constraints in Rel-19, postpone such discussion to Rel-20.
Proposal 4	RAN2 to agree on the attached LS reply to RAN3.
Proposal 5	Introduce a UE capability of supporting geographic area scope checking with signaling.
Proposal 6	Introduce a single UE capability for location-based measurement initiation and MDT geographic area scope checking.
Proposal 7	Introduce separate UE capabilities to support geographic area scope checking for NTN quasi-Earth-fixed and Earth-moving cell.
Proposal 8	If the UE cannot obtain its location, it performs legacy area checking for logged MDT.
Proposal 9	Include an indication in each logged MDT measurement sample, i.e. in the LogMeasReport IE, if the UE has not obtained its location even though it supports geographic area scope checking.
Proposal 10	If the UE is configured with a geographical area scope and it can obtain location information, the UE performs geographical area checking for logged MDT, irrespective if a legacy area scope is configured or not. Geographical area has higher priority than legacy area scope.
Proposal 11	Introduce the relative time between the time when locationInfo was measured and the time when the RLF/HOF happens, based on which the network computes the distance.
 

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

Agenda Item:	8.10.3
Source:	CMCC
Title:	Discussion on SON/MDT for Slicing and NTN
Document for:	Discussion
1 

Conclusion
In this paper, we discuss on the potential SON/MDT enhancements for network slicing and MRO enhancement for location-based CHO in NTN for earth moving scenario, we have the following observations and proposals:
SON/MDT for network slicing
Observation 1: The scenario identified by RAN3 may occur especially when the UE resides at the boundary of different TA, since different NSAG(s) can be supported in different TA. 
Observation 2: Due to sub-optimal configuration of sliceAllowedCellListNR or sliceExcludedCellListNR in SIB16, the UE may find the best cell or highest ranked cell does not support the highest NSAG after the UE camps on, which may lead to unnecessary handover.
Observation 3: If the UE can log the NSAG(s) supported by the highest ranked cell or best cell, the NSAG(s) and priority information supported by the UE (received from NAS), the network can optimize the configuration of sliceAllowedCellListNR or sliceExcludedCellListNR, e.g. include the highest ranked cell or best cell in sliceExcludedCellListNR, then the UE will camp on the other suitable cell which supports the highest priority NSAG.
Proposal 1: It is proposed to log the NSAG(s) supported by the highest ranked cell or best cell, the NSAG(s) and priority information supported by the UE (received from NAS), which is helpful for NW to optimize the configuration of sliceAllowedCellListNR and/or sliceExcludedCellListNR in SIB16.

SON/MDT for NTN
Observation 4: For location-based trigger condition, the distance information between UE and the moving reference location in serving cell and in candidate cell respectively when the failure occurs is beneficial to analysis whether the distance thresholds configured in location-based trigger condition have the potential problem.
Observation 5: For Option 1 (the absolute UTC time), the following issues need to be considered:
The absolute UTC time which may be represented by 39 bits are only provided from Network to UE by now.
Reporting the absolute UTC time when RLF occurred in the RLF report would cause UE complexity. 
Option 1 is only used to get the time of when RLF/HOF happens. The additional calculation is still needed for Network to derive the distance between UE and the reference location in serving cell and in candidate cell when RLF occurred based on UE location information.
Since the IE locationInfo in RLF report is optional, UE location information may be not available when RLF occurred and network could not derive the distance between UE and the referenceLocation in serving cell and in candidate cell.
Observation 6: Option 2 is a more reasonable solution to get the distance information for location-based CHO with the following reasons:
Option 2 is a straightforward solution to get the distance information for location-based CHO. There is no need for Network to perform any additional calculation for distance information.
There is no additional complexity for UE to measure the distance between UE and the moving reference location in serving cell and in candidate cell when RLF occurred. Anyway, UE needs to measure the distance between UE and the moving reference location in serving cell and in candidate cell respectively to evaluate whether location-based CHO execution condition is satisfied.
The  IE size of measured distance from UE to moving reference location of serving cell and candidate cell would be much less than the IE size of the absolute UTC time.
Proposal 2: RAN2 to select Option 2 in RAN3 LS to optimize the distance threshold for location-based CHO in NTN for earth moving scenario, i.e., to introduce measured distance from UE to moving reference location of serving cell, and measured distance from UE to moving reference location of candidate cell when RLF/HOF happens in RLF report.
Proposal 3: To inform RAN3 with RAN2 decision in the reply LS.

TDoc file reading error

3GPP TSG-RAN WG2 Meeting #130	R2-2504559
St.Julians, Malta,  May 19th – 23rd , 2025
Source:                Qualcomm Incorporated 
Title:	SON and MDT for LTM
Agenda Item:	8.10.3
Document for:	Discussion and Decision
Introduction & 

Conclusion
Introduce UE capability for SON/MDT for LTM.
Introduce UE capability for SON/MDT for CHO with candidate SCGs.
Introduce UE capability for RLF report for time/location-based CHO in NTN.
Introduce UE capability on RA-report for SDT.
Introduce UE capability on MHI enhancement for SCG deactivation/activation
Introduce UE capability on MRO for EN-DC SCG failure
FFS whether radio access signalling is needed for above UE capabilities.
UE reports the capability of  supporting geographic area scope checking to the gNB.

3GPP TSG-RAN WG2 Meeting #130		R2-2504569
Malta, May 19 – 23, 2025	Revision of R2-2502808

Agenda Item:	8.10.3
Source: 	LG Electronics
Title:  	NTN Logging for Unchanged PCI Mobility

Document for:	Discussion

Conclusion
It is proposed to discuss and decide on the following proposals:
Proposal 1: For unchanged PCI satellite mobility, the UE uses the RLF report, including a new cause to indicate a failure of the unchanged PCI satellite mobility if RLF is declared due to this mobility.
Proposal 2: For unchanged PCI satellite mobility, the UE reports the near failure information that out-of-sync indication(s) has been detected during the mobility if the UE detects the out-of-sync indications during the unchanged PCI satellite mobility but successfully complete this mobility.
Proposal 3: To determine a proper near failure of the unchanged PCI satellite mobility, a new logging condition is considered based on reception of a significant number of out-of-sync indications during the mobility.

TDoc file reading error