R2-2503581 Views on R19 SONMDT UE capabilities.docx
3GPP TSG-RAN WG2 Meeting #130                                                                    R2-2503581
St. Julians, Malta, May 19th – 23rd, 2025

		
Source:	CATT 
Title:	Views on R19 SONMDT UE capabilities
Agenda Item:	8.10.1
Document for:	Discussion and Decision

Conclusion
According to the analysis in section 2, we have the observations and proposals as below:
LTM
Observation 1: some enhancements on RLF report and SHR for MCG LTM have been agreed.
Proposal 1: an optional UE capability with signalling is defined for RLF report for MCG LTM.
Proposal 2: an optional UE capability without signalling is defined for SHR for MCG LTM.

CHO with candidate SCGs 
Observation 2: some enhancements on RLF report, SHR and SCGFailureInformation for CHO with candidate SCG have been agreed
Proposal 3: an optional UE capability with signalling is defined for RLF report for CHO with candidate SCG.
Proposal 4: an optional UE capability without signalling is defined for SHR/SPR/SCGFailureInformation for CHO with candidate SCG.

SON/MDT for NTN
Proposal 5: an optional UE capability without signalling is defined for RLF report for time/location based CHO.
Proposal 6: an optional UE capability with signalling is defined for geographic area scope checking for logged MDT.

RACH optimization for SDT
Proposal 7: an optional UE capability without signalling is defined for RA-report for SDT.

MHI Enhancement for SCG Deactivation/Activation
Proposal 8: an optional UE capability without signalling is defined for MHI Enhancement for SCG Deactivation/Activation.

MRO for MR-DC SCG failure
Proposal 9: an optional UE capability without signalling is defined for MRO for EN-DC SCG failure in LTE specification.

R2-2504235 Open issue list for running 36.331 CR for R19 SONMDT.docx
3GPP TSG-RAN WG2 Meeting #130		R2-2504235
St Julian's, Malta, 19 - 23 May, 2025
Source:	Huawei, HiSilicon
Title:	Open issue list for running 36.331 CR for R19 SONMDT 
Agenda Item:	8.10.1
Document for:	Discussion and Decision
Conclusion
Based on the discussion in section 2 and in running 36.331 CR, the following open issues are identified and discussed. It is proposed:
Proposal 1: It is proposed RAN2 to discuss the open issue LTERRC-1, i.e. whether to keep the following condition or not (it has been captured in section 5.6.13a.3 in running 36.331 CR):
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:
Proposal 2: It is proposed RAN2 to discuss the open issue LTERRC-2, i.e. when the LTM based recovery fails and the UE selects E-UTRA cell and receives RRCConnectionSetup, timeUntilReconnection need to refer to the first failure and this should be captured in running 36.331 CR.
Proposal 3: It is proposed RAN2 to discuss the open issue LTERRC-3, i.e. whether to have a single container to carry all the fields (PerRAInfoList-r16, PerRAInfoList-v1660 and PerRAInfoList-v1800) or not.

R2-2504296 - Open issues for NR RRC SONMDT features.docx
3GPP TSG-RAN WG2 #130	R2-2504296
St Julian’s, Malta, 19-23 May 2025

Agenda Item:	8.10.1
Source:	Ericsson
Title:	Remaining RRC Open issues for SONMDT features
Document for:	Discussion, Decision
Conclusions
[Proposals for discussion]
Proposal 1. Companies are invited to discuss the Open issue RRC-1 (i.e., the correlation of SHR and SPR and avoiding duplication of the information) in their contribution for the meeting RAN2#130.


09-May-2025 21:19:09

© 2025 Majid Ghanbarinejad. All rights reserved.