RAN3#117bis-e

3: Approval of the Agenda

TDoc	Title	Source
R3-225300	RAN3#117bis-e Meeting Agenda	RAN3 Chair

4: Approval of the minutes from previous meetings

TDoc	Title	Source
R3-225301	RAN3#117-e Meeting report	ETSI-MCC

5: Documents for immediate consideration

TDoc	Title	Source
R3-225343	Guidelines for RAN3 Electronic Meetings	RAN3 Chair, RAN3 Vice-Chairs

7: General, protocol principles and issues

TDoc	Title	Source
R3-225302	TR 30.531 v1.44.0 Work Plan and Working Procedures - RAN WG3	ETSI-MCC

8.1: New Incoming LSs

TDoc	Title	Source
R3-225304	Reply LS on the maximum PTW length of IDLE eDRX	CT1
R3-225309	LS on the progress of NCR identification and authorization	RAN2
R3-225310	Reply LS on RAN feedback for low latency	RAN2
R3-225311	Reply LS on transferring SDT configuration and SRS positioning Inactive configuration from DU to CU	RAN2
R3-225313	Reply LS on CCA configurations of neighbour cells	RAN2
R3-225314	Reply LS on FS_REDCAP_Ph2 option feasibility	RAN2
R3-225320	LS Out on RAN dependency of FS_eNS_Ph3	SA2
R3-225323	LS on Inter-system handover to Home eNB	SA2
R3-225324	LS Out on LS on slice list and priority information for cell reselection and Random Access	SA2
R3-225325	Reply to LS on UE capability signalling for IoT-NTN	SA2
R3-225326	Reply LS on UE’s LTE UPIP capability for EN-DC	SA3
R3-225327	Reply LS to SA5 on TS 28.404/TS 28.405 Clarification	SA4
R3-225400	Draft Reply LS on RAN dependency of FS_eNS_Ph3	Qualcomm India Pvt Ltd
R3-225401	RRC_Inactive with eDRX Notification for RedCap Ph2	Qualcomm India Pvt Ltd
R3-225505	Analysis of Slice List And Priority Information for Random Access	Nokia, Nokia Shanghai Bell
R3-225506	Reply LS Out on RAN dependency of FS_eNS_Ph3	Ericsson
R3-225507	Analysis of RAN dependency of FS_eNS_Ph3	Ericsson
R3-225517	Correction of slice-based RACH resources at handover	Nokia, Nokia Shanghai Bell
R3-225518	Correction of slice-based RACH resources at handover	Nokia, Nokia Shanghai Bell
R3-225519	Reply LS on Slice List And Priority Information for cell re-selection and random access	Nokia, Nokia Shanghai Bell
R3-225520	Feedback to SA2 on RAN Dependency of FS_eNS_Ph3	Nokia, Nokia Shanghai Bell
R3-225521	Reply LS on RAN Dependency of FS_eNS_Ph3	Nokia, Nokia Shanghai Bell
R3-225562	Inter-system handover to Home eNB	Nokia, Nokia Shanghai Bell, AT&T, NEC, Verizon Wireless
R3-225563	Correction of inter-system handover to HeNB	Nokia, Nokia Shanghai Bell, AT&T, NEC, Verizon Wireless
R3-225564	Correction of inter-system handover to HeNB (alternative solution)	Nokia, Nokia Shanghai Bell, AT&T, Verizon Wireless
R3-225575	Inter-System Handover to HeNBs	Ericsson LM
R3-225576	[DRAFT] Reply LS on Inter-system handover to Home eNB	Ericsson LM
R3-225671	Discussion on RAN dependency of FS_eNS_Ph3	Huawei
R3-225672	[Draft] Reply LS on RAN dependency of FS_eNS_Ph3	Huawei
R3-225673	NSAG for cell reselection and random access	Huawei
R3-225674	NSAG for cell reselection and random access	Huawei
R3-225675	[Draft] Reply LS on slice list and priority information for cell reselection and Random Access	Huawei
R3-225676	Inter-system handover to Home eNB	Huawei
R3-225677	[Draft] Reply LS on Inter-system handover to Home eNB	Huawei
R3-225739	CCA configurations of neighbour cells	Huawei
R3-225740	[Draft] Reply LS on CCA configurations of neighbour cells	Huawei
R3-225741	CCA configurations of neighbour cells	Huawei
R3-225742	CCA configurations of neighbour cells	Huawei
R3-225859	Consideration on RAN dependency of FS_eNS_Ph3	ZTE
R3-225860	[Draft] Reply LS on RAN dependency of FS_eNS_Ph3	ZTE
R3-225861	Correction on NSAG_TS 38.300_CR	ZTE
R3-225889	Reply LS on the maximum PTW length of IDLE eDRX	Ericsson
R3-225893	Correction of RRC container reference name	Ericsson
R3-225894	CB: # 1_FS_eNS_RANImpact - Summary of email discussion	ZTE - moderator
R3-225895	CB: # 2_InterSystemHO_HeNB - Summary of email discussion	Ericsson - moderator
R3-225896	CB: # 3_SliceList_Priority - Summary of email discussion	Huawei - moderator
R3-225941	Response paper to R3-225739 CCA configurations of neighbour cells	Ericsson
R3-225942	Response to R3-225575 inter-system HO to HeNB	Nokia, Nokia Shanghai Bell
R3-225943	Response to R3-225507	Nokia, Nokia Shanghai Bell
R3-225949	CB: # 47_CCA - Summary of email discussion	Huawei - moderator
R3-225974	Correction on NSAG_TS 38.300_CR	ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Qualcomm Incorporated, Ericsson, LG Electronics, Huawei
R3-225975	NSAG for cell reselection and random access	Huawei, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Qualcomm Incorporated, LG Electronics
R3-226000	Reply LS on CCA configurations of neighbour cells	Huawei
R3-226032	Reply LS on RAN dependency of FS_eNS_Ph3	ZTE
R3-226035	Reply LS on Inter-system handover to Home eNB	Huawei
R3-226071	Reply LS on RAN dependency of FS_eNS_Ph3	ZTE
R3-226083	Reply LS on RAN dependency of FS_eNS_Ph3	ZTE

9.1: LTE

TDoc	Title	Source
R3-225504	Reply LS on Report Amount for M4, M5, M6 and M7 measurements	SA5
R3-225615	Correction to IoT NTN about constructing the Mapped Cell ID	CATT, Ericsson, ZTE, Nokia, Huawei
R3-225628	Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN	Huawei, Deutsche Telekom, Orange
R3-225629	Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN	Huawei, Deutsche Telekom, Orange
R3-225630	Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN	Huawei, Deutsche Telekom, Orange
R3-225631	[draft] Reply LS on Report Amount for M4, M5, M6 and M7 measurements	Huawei
R3-225857	Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN	Huawei, Deutsche Telekom, Orange
R3-225946	Response to R3-225628	Ericsson
R3-225950	Correction to IoT NTN about constructing the Mapped Cell ID	CATT, Ericsson, ZTE, Nokia, Huawei

9.2.1: RVQoE

TDoc	Title	Source
R3-225328	Reply LS on questions on RAN visible QoE	SA4
R3-225336	[Draft] LS Reply to Questions on RAN Visible QoE	Ericsson
R3-225429	Discussion on RAN visible QoE	Samsung
R3-225687	Further discussion on RAN visible QoE	Huawei
R3-225688	[DRAFT] Relpy LS on questions on RAN visible QoE	Huawei
R3-225771	Discussion of RAN2 LS on questions on RAN visible QoE	CATT
R3-225817	Discussion on RAN visible QoE open issues	ZTE
R3-225818	draft CR to 38.300 on RAN visible QoE	ZTE
R3-225897	CB: # 4_RVQoE - Summary of email discussion	Huawei - moderator
R3-226017	[DRAFT] Relpy LS on questions on RAN visible QoE	Huawei
R3-226018	draft CR to 38.300 on RAN visible QoE	ZTE
R3-226061	Relpy LS on questions on RAN visible QoE	Huawei
R3-226077	CB: # 4_RVQoE - Summary of email discussion	Huawei - moderator

9.2.2: SONMDT

TDoc	Title	Source
R3-225329	Reply LS on User Consent Updating	SA5
R3-225381	UE History Information for CHO	Samsung, Verizon, ZTE, Qualcomm, Ericsson
R3-225382	Correction of UE History Information for CHO	Samsung, Verizon, ZTE, Qualcomm, Ericsson
R3-225383	The inclusion of the CCO Issue Detection over Xn signalling	Samsung, Verizon, Ericsson, ZTE
R3-225387	Further correction to Report Caracteristics	Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CMCC, CATT, China Unicom, China Telecom, Deutsche Telekom
R3-225388	Further correction to Report Caracteristics	Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CMCC, CATT, China Unicom, China Telecom, Deutsche Telekom
R3-225389	Alternatives for solving the SCG UHI problem (incl. draft CRs)	Nokia, Nokia Shanghai Bell
R3-225390	Failure handling for SCG MRO	Nokia, Nokia Shanghai Bell
R3-225535	SHR correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone, BT
R3-225536	SHR correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone, BT
R3-225537	SHR correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone, BT
R3-225538	SHR correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone, BT
R3-225539	MR-DC UHI correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone
R3-225540	MR-DC UHI correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone
R3-225541	MR-DC UHI correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone
R3-225542	MR-DC UHI correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone
R3-225571	New load metrics per NR-U channel	Ericsson
R3-225596	Correction of 'set of NR cells' in UHI	Nokia, Nokia Shanghai Bell
R3-225619	Further discussion on Excess Packet Delay	CATT
R3-225695	Discussion on SON for NR-U to support DL MLB	Samsung, Qualcomm Incorporate
R3-225696	Correction of NR-U information exchange for DL MLB	Samsung, Qualcomm Incorporate
R3-225697	Correction of NR-U information exchange for DL MLB	Samsung, Qualcomm Incorporate
R3-225732	Correction of UE History Information for CHO	Samsung
R3-225733	Correction of UE History Information for CHO	Samsung
R3-225788	Discussion on UE History Information	CATT
R3-225828	Discussion on corrections for UE History Information in MR-DC	ZTE, Samsung, China Telecom
R3-225829	Correction for XnAP on UHI in MR-DC	ZTE, Samsung, Lenovo, China Telecom
R3-225830	Correction for X2AP on UHI in MR-DC	ZTE, Samsung, Lenovo, China Telecom
R3-225831	Correction for NGAP on UHI in MR-DC	ZTE, Samsung, Lenovo, China Telecom
R3-225832	Correction for S1AP on UHI in MR-DC	ZTE, Samsung, Lenovo, China Telecom
R3-225833	Correction for TS 37.340 on UHI MR-DC	ZTE, Samsung, Lenovo, China Telecom
R3-225834	Correction for TS 38.300 on UHI for CHO	ZTE, Samsung, China Telecom
R3-225862	R16 Correction on RACH report to TS38.423	ZTE, CATT, Samsung,CMCC
R3-225863	R17 Correction on RACH report to TS38.423	ZTE, CATT, Samsung,CMCC
R3-225864	R17 Correction on SHR report to TS38.423	ZTE, CATT, Samsung,CMCC
R3-225865	Stage 2 of successful HO	ZTE
R3-225883	R16 Correction on RACH report to TS38.423	ZTE, CATT, Samsung,CMCC
R3-225884	R17 Correction on RACH report to TS38.423	ZTE, CATT, Samsung,CMCC
R3-225886	Resource Status Reporting correction	Ericsson
R3-225890	UE History Information correlation	Ericsson
R3-225898	CB: # 5_UHI - Summary of email discussion	ZTE - moderator
R3-225899	CB: # 6_R17SONMDT - Summary of email discussion	Samsung - moderator
R3-225984	The inclusion of the CCO Issue Detection over Xn signalling	Samsung, Verizon, Ericsson, ZTE
R3-225988	SHR correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone, BT
R3-226012	Correction of UE History Information for CHO	Samsung
R3-226013	Correction of UE History Information for CHO	Samsung
R3-226030	Correction for TS 37.340 on UHI MR-DC	ZTE, Samsung, Lenovo, China Telecom
R3-226036	Failure handling for SCG MRO	Nokia, Nokia Shanghai Bell, CATT
R3-226037	NGAP Corrections related to Excess Packet Delay	CATT
R3-226038	XnAP Corrections related to Excess Packet Delay	CATT
R3-226039	Resource Status Reporting correction	Ericsson
R3-226059	CB: # 5_UHI - Summary of email discussion	ZTE - moderator
R3-226067	Correction of UE History Information for CHO	Samsung, ZTE, Ericsson
R3-226069	CB: # 6_R17SONMDT - Summary of email discussion	Samsung - moderator
R3-226070	The inclusion of the CCO Issue Detection over Xn signalling	Samsung, Verizon, Ericsson, ZTE
R3-226072	Resource Status Reporting correction	Ericsson
R3-226076	Correction for TS 37.340 on UHI MR-DC	ZTE, Samsung, Lenovo, China Telecom, Ericsson
R3-226082	SHR correction	Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone, BT

9.2.3: IAB

TDoc	Title	Source
R3-225306	Reply LS on RB set configuration for IAB	RAN1
R3-225349	(CR TS 38.473) Correction to NR Carrier List	Ericsson
R3-225356	(CR to TS 38.300) Correction for definition of IAB-topology	Qualcomm Inc.
R3-225433	Correction to procedure of topology redundancy	Fujitsu
R3-225443	Correction to TS 38.473 on RB Set Configuration	ZTE
R3-225650	Correction to TS 38.423 on RRC transfer	ZTE
R3-225678	Correction on Resource configuration for IAB	Huawei, Lenovo, Ericsson, Nokia, Nokia Shanghai Bell
R3-225679	Correction on Resource configuration for IAB	Huawei, Lenovo, Nokia, Nokia Shanghai Bell
R3-225825	Discussion on the RB Set Configuration for IAB	ZTE
R3-225900	CB: # 7_R17IAB - Summary of email discussion	Qualcomm - moderator
R3-226034	Correction to TS 38.423 on RRC transfer	ZTE
R3-226060	CB: # 7_R17IAB - Summary of email discussion	Qualcomm - moderator
R3-226068	Correction to TS 38.473 on RB Set Configuration	ZTE

9.2.4: Positioning

TDoc	Title	Source
R3-225316	Reply LS on the UE/TRP TEG framework	RAN4
R3-225560	Correction of timing error margin for UE/TRP TEGs	Nokia, Nokia Shanghai Bell, Ericsson, CATT
R3-225561	Correction of timing error margin for UE/TRP TEGs	Nokia, Nokia Shanghai Bell, Ericsson, CATT
R3-225566	Correction of Timing Error Margin	Ericsson, CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-225567	Correction of Positioning Information Transfer function	Ericsson, Nokia, Nokia Shanghai Bell, ZTE
R3-225568	Correction to the PRS Measurement configuration procedures	Ericsson
R3-225620	Correction of Timing Error Margin for F1AP	CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE
R3-225621	Corrections on NRPPa functions and procedures	CATT
R3-225632	Correction on timing error margin of RxTx TEG	Huawei, China Unicom, China Telecom
R3-225633	Correction on timing error margin of RxTx TEG	Huawei, China Unicom, China Telecom
R3-225634	CR to 38.455 on SRS periodicity	Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom
R3-225635	CR to 38.455 on SRS periodicity	Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom
R3-225636	CR to 38.473 on SRS periodicity	Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom
R3-225637	CR to 38.473 on SRS periodicity	Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom
R3-225638	Correction of ASN.1 for UL RTOA Measurement	Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell
R3-225639	Discussion on positioning SI delivery over F1AP	Huawei, China Unicom, CMCC
R3-225640	Correction on positioning SI delivery over F1AP	Huawei, China Unicom, CMCC
R3-225641	Correction on positioning SI delivery over F1AP	Huawei, China Unicom, CMCC
R3-225901	CB: # 8_R17Positioning - Summary of email discussion	Huawei - moderator
R3-226007	Correction of timing error margin for UE/TRP TEGs	Nokia, Nokia Shanghai Bell, Ericsson, CATT
R3-226008	Correction of timing error margin for UE/TRP TEGs	Nokia, Nokia Shanghai Bell, Ericsson, CATT
R3-226010	Corrections on NRPPa functions and procedures	CATT
R3-226019	Correction on positioning SI delivery over F1AP	Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT
R3-226020	Correction on positioning SI delivery over F1AP	Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT
R3-226022	Correction to 38.470 on Positioning System Information	Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CATT
R3-226023	Correction to 38.470 on Positioning System Information	Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CATT
R3-226043	Correction to the PRS Measurement configuration procedures	Ericsson
R3-226052	CB: # 8_R17Positioning - Summary of email discussion	Huawei - moderator
R3-226063	Correction on positioning SI delivery over F1AP	Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT
R3-226064	Correction on positioning SI delivery over F1AP	Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT

9.2.5: MBS

TDoc	Title	Source
R3-225305	LS on Multicast MBS session Deactivation and Reactivation	CT4
R3-225308	Reply LS on the MBS broadcast service continuity and MBS session identification	RAN2
R3-225319	Response LS on further outstanding issues in TS 23.247	SA2
R3-225341	Discussion on Multicast MBS Session Context Establishment	Google Inc.
R3-225342	Clarification to Multicast MBS Session Context Establishment	Google Inc.
R3-225444	Corrections to the example message flow for multicast MBS Context establishment	Ericsson, AT&T
R3-225446	MC Bearer Context Setup without MRB configuration available	Ericsson, AT&T, Orange, Nokia, Nokia Shanghai Bell, Qualcomm
R3-225447	F1-U references to UE Context in gNB-CU enabling retrieval of data forwarding progress information	Ericsson, AT&T, Nokia, Nokia Shanghai Bell, Qualcomm. Lenovo
R3-225448	Introduction of multicast MBS session status in Multicast Context Management messages	Ericsson, AT&T
R3-225449	Stage 3 description for admission control at multicast MBS Session Activation	Ericsson, AT&T, CATT, ZTE
R3-225468	Correction on F1-U tunnels for multicast MRB	Lenovo, Huawei
R3-225469	Discussion on initial value of RX_DELIV	Lenovo
R3-225470	Correction on initial value of RX_DEILV	Lenovo
R3-225471	Correction on User Inactivity for Multicast Session	Lenovo
R3-225522	Correction of MBS Broadcast Session Restart	Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated
R3-225523	Correction of MBS Broadcast Session Restart	Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated
R3-225524	Correction of MBS data forwarding	Nokia, Nokia Shanghai Bell, Huawei, Orange, Qualcomm Incorporated
R3-225525	Correction of MBS data forwarding	Nokia, Nokia Shanghai Bell, Huawei, Orange, Qualcomm Incorporated
R3-225526	Correction of MBS multicast HFN SN Initialisation	Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated
R3-225527	Correction of MBS multicast HFN SN Initialisation	Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated
R3-225528	LS on Multicast HFN/SN Initialization for Inactive Multicast Sessions	Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated
R3-225529	Correction of MBS shared CU UP	Nokia, Nokia Shanghai Bell, Ericsson, Orange
R3-225530	Correction of MBS shared CU UP	Nokia, Nokia Shanghai Bell, Ericsson, Orange
R3-225532	Correction of MBS Session Activation	Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R3-225652	Correction on Multicast Session Establishment	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo
R3-225653	Inclusion of MBS Parameters in PDU Session Management procedures	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo
R3-225654	Correction on Multicast Mobility procedure	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo
R3-225655	Minimization of data loss and duplication avoidance during mobility from MBS non upporting gNB to supporting gNB	Huawei, CBN, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Lenovo
R3-225656	Clarification on initialRXDELIV over E1AP	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R3-225657	Clarification on NID handling within the MBS Session ID	Huawei, CBN, China Unicom, Lenovo
R3-225658	Consideration on the delay of configuration of MRB	Huawei, CBN, China Unicom
R3-225659	Correction for the delay of configuration of MRB	Huawei, CBN, China Unicom
R3-225685	Clarification on NID handling within the MBS Session ID	Huawei, CBN, China Unicom, Lenovo
R3-225686	[DRAFT] LS on Inclusion of NID within MBS Session ID	Huawei
R3-225718	Introduction of ongoing broadcast service in XnAP	CATT, Nokia, Nokia Shanghai Bell, Huawei
R3-225719	Correction on non-MBS-supporting to MBS-supporting handover on TS 37.483	CATT,Nokia, Nokia Shanghai Bell
R3-225720	Correction on definition of Multicast F1-U Context	CATT
R3-225721	Discussion on MRB PDCP count “wrap around” problem	CATT
R3-225722	Correction on MRB PDCP count “wrap around” problem	CATT
R3-225827	[DRAFT] LS on delay issue on configuring MRB	Huawei
R3-225850	Multicast session state and its impacts to network interfaces	ZTE
R3-225851	Correction to 38.401 on admission control of multicast session for NR MBS	ZTE, Lenovo, CMCC
R3-225852	Correction to NGAP on distribution modification for NR MBS	ZTE, Lenovo, CMCC
R3-225902	CB: # 9_R17MBS1_GeneralNGXn - Summary of email discussion	Nokia - moderator
R3-225903	CB: # 10_R17MBS2_F1E1 - Summary of email discussion	Ericsson - moderator
R3-225944	Response to R3-225444	Nokia, Nokia Shanghai Bell
R3-225963	Corrections to the example message flow for multicast MBS Context establishment	Ericsson, AT&T
R3-225964	MC Bearer Context Setup without MRB configuration available	Ericsson, AT&T, Orange, Nokia, Nokia Shanghai Bell, Qualcomm
R3-225965	Provision of MBS Multicast F1-U references to UE Context in gNB-CU enabling retrieval of data forwarding progress information	Ericsson, AT&T, Nokia, Nokia Shanghai Bell, Qualcomm, Lenovo
R3-225966	Introduction of multicast MBS session status in Multicast Context Management messages	Ericsson, AT&T
R3-225967	Stage 3 description for admission control at multicast MBS Session Activation	Ericsson, AT&T, CATT, ZTE
R3-225968	Correction of MBS Session Activation	Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R3-225970	LS on availability of intialRX-DELIV at MRB setup	Ericsson
R3-225973	Clarification on initialRXDELIV over E1AP	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, CATT
R3-225978	Correction on User Inactivity for Multicast Session	Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Ericsson
R3-225979	CB: # 9_R17MBS1_GeneralNGXn - Summary of email discussion	Nokia - moderator
R3-225985	Correction on Multicast Mobility procedure	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, Samsung
R3-225996	Correction on Multicast Session Establishment	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo
R3-225997	Minimization of data loss and duplication avoidance during mobility from MBS non upporting gNB to supporting gNB	Huawei, CBN, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Lenovo
R3-225998	Correction on F1-U tunnels for multicast MRB	Lenovo, Huawei
R3-226011	Correction on non-MBS-supporting to MBS-supporting handover on TS 37.483	CATT, Nokia, Nokia Shanghai Bell
R3-226029	Introduction of further multicast session flow on MRB type reconfiguration	Ericsson, AT&T, Nokia , Nokia Shanghai Bell
R3-226049	Correction on Multicast Session Establishment	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, Ericsson, Google
R3-226073	Correction to 38.401 on NR MBS on admission control of multicast session	ZTE, Lenovo, CMCC
R3-226074	Correction to NGAP on distribution modification for NR MBS	ZTE, Lenovo, CMCC
R3-226078	Clarification on initialRXDELIV over E1AP	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, CATT
R3-226079	Correction on User Inactivity for Multicast Session	Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Ericsson
R3-226080	Correction on F1-U tunnels for multicast MRB	Lenovo, Huawei, Nokia, Nokia Shanghai Bell

9.2.6: PDCP Count Reset

TDoc	Title	Source
R3-225368	Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover	NEC, ZTE, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc
R3-225369	Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover	NEC, ZTE, Huawei, CATT, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc
R3-225370	Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover	NEC, ZTE, Huawei, CATT, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc
R3-225371	PDCP COUNT reset in CU-UP for inter-gNB-DU Handover	NEC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc, Samsung
R3-225372	PDCP COUNT reset in CU-UP for inter-gNB-DU Handover	NEC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc, Samsung
R3-225876	PDCP Count Reset over E1AP	Ericsson
R3-225904	CB: # 11_PDCPCount - Summary of email discussion	NEC - moderator
R3-226041	PDCP COUNT reset in CU-UP for inter-gNB-DU Handover	NEC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc, Samsung, Huawei
R3-226042	PDCP COUNT reset in CU-UP for inter-gNB-DU Handover	NEC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc, Samsung, Huawei

9.2.7: Gap Configuration

TDoc	Title	Source
R3-225598	Further discussion on generation of gap type over F1	ZTE, China Telecom, Lenovo, China Unicom
R3-225599	Correction on generation of gap type over F1 in Rel-15 (Option 1)	ZTE, China Telecom, Lenovo, China Unicom
R3-225600	Correction on generation of gap type over F1 in Rel-16 (Option 1)	ZTE, China Telecom, Lenovo, China Unicom
R3-225601	Correction on generation of gap type over F1 in Rel-17 (Option 1)	ZTE, China Telecom, Lenovo, China Unicom
R3-225602	Correction on generation of gap type over F1 in Rel-15 (Option 2)	ZTE, China Telecom, Lenovo, China Unicom
R3-225603	Correction on generation of gap type over F1 in Rel-16 (Option 2)	ZTE, China Telecom, Lenovo, China Unicom
R3-225604	Correction on generation of gap type over F1 in Rel-17 (Option 2)	ZTE, China Telecom, Lenovo, China Unicom
R3-225605	Draft LS on generation of gap type over F1	ZTE
R3-225606	Discussion on concurrent gap configuration over F1	ZTE, China Telecom, Lenovo, China Unicom
R3-225607	Correction on concurrent gap configuration over F1	ZTE, China Telecom, Lenovo, China Unicom
R3-225736	Gap Association Information for concurrent gap configuration [NR_RF_FR2_req_enh2-Core]	Huawei, Deutsche Telekom
R3-225905	CB: # 12_GapConfig - Summary of email discussion	ZTE - moderator
R3-225947	Correction on concurrent measurement gap configuration over F1 [NR_MG_enh-Core]	ZTE, China Telecom, Lenovo, China Unicom
R3-225971	Correction on generation of gap type over F1 in Rel-16	ZTE, China Telecom, Lenovo, China Unicom, Ericsson
R3-225972	Correction on generation of gap type over F1 in Rel-17	ZTE, China Telecom, Lenovo, China Unicom, Ericsson

9.2.8: DAPS over F1

TDoc	Title	Source
R3-225363	Disscussion on DAPS over F1	ZTE, Ericsson, CATT, Google, Samsung, Intel Corporation, Lenovo, NEC
R3-225364	R16CR for DAPS over F1 to TS38.473	ZTE, Ericsson, CATT, Google, Samsung, Intel Corporation, Lenovo, NEC
R3-225365	R17CR for DAPS over F1 to TS38.473	ZTE, Ericsson, CATT, Google, Samsung, Intel Corporation, Lenovo, NEC
R3-225402	Power Co-ordination for DAPS HO over F1 for R17	Qualcomm India Pvt Ltd
R3-225403	Power Co-ordination for DAPS HO over F1 for R16	Qualcomm India Pvt Ltd
R3-225737	Configuration Restriction Info for DAPS handover	Huawei, Qualcomm Incorporate
R3-225738	Configuration Restriction Info for DAPS handover	Huawei, Qualcomm Incorporate
R3-225906	CB: # 13_DAPS - Summary of email discussion	ZTE - moderator
R3-225993	R16CR for DAPS over F1 to TS38.473	ZTE, Ericsson, CATT, Google, Samsung, Intel Corporation, Lenovo, NEC
R3-225994	R17CR for DAPS over F1 to TS38.473	ZTE, Ericsson, CATT, Google, Samsung, Intel Corporation, Lenovo, NEC

9.2.9: Others

TDoc	Title	Source
R3-225597	Remote Interference Management - issue on RIM-RS boundary alignment	Nokia, Nokia Shanghai Bell
R3-225750	Correction on coarse UE location reporting for TS 38.300	Xiaomi, Apple, CAICT, CMCC
R3-225757	Including data forwarding addresses for multiple T-SNs in the SN Change Confirm message in the SN-initiated inter-SN CPC procedure	Samsung

10.1: General

TDoc	Title	Source
R3-225805	Update of work Plan for Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI	CMCC
R3-225806	BLCR to 38.300:enhancement of SON	CMCC
R3-225999	BLCR to 38.300:enhancement of SON	CMCC
R3-226086	(BLCR to 38.423) Addition of SON features enhancement	Samsung

10.2.1: SHR and SPCR

TDoc	Title	Source
R3-225384	SON enhancement for Successful Handover Report and Successful PSCell Change Report	Samsung
R3-225393	[TP to 38.423, SON] Configuration coordination for the successful PSCell change report	Nokia, Nokia Shanghai Bell
R3-225405	Successful PSCell Change Report and inter-RAT Successful Handover Report	Qualcomm Incorporated
R3-225424	Discussion on support of SHR and SPCR	China Telecommunication
R3-225472	SON enhancements for successful PSCell change report	Lenovo
R3-225473	Successful Handover Report for inter-RAT HO	Lenovo
R3-225543	SHR and SPCR	Huawei
R3-225550	Inter-RAT SHR and SPR discussion	Ericsson
R3-225772	SHR for NR to LTE HO	Intel Corporation
R3-225789	Discussion on SON enhancement for SHR and SPCR	CATT
R3-225866	Discussion on inter-RAT SHR and SPCR	ZTE
R3-225907	CB: # SONMDT1_SHRandSPCR - Summary of email discussion	Qualcomm - moderator
R3-226003	LS on inter-RAT SHR and SPCR	Qualcomm

10.2.2: MRO

TDoc	Title	Source
R3-225385	SON enhancements for CPAC and MCG failure recovery	Samsung
R3-225386	Discussion on MR-DC SCG failure and CPAC	Samsung
R3-225394	Timer information to support MRO for fast MCG recovery	Nokia, Nokia Shanghai Bell
R3-225406	MRO enhancements for CPAC, voice fall back and MR-DC SCG failures	Qualcomm Incorporated
R3-225474	SON enhancements for CPAC	Lenovo
R3-225475	(TP for SON BLCR for 36.300) MRO for fast MCG link recovery and SCG failure	Lenovo
R3-225476	(TP for SON BLCR for 38.300) MRO for inter-system handover for voice fallback and way forward on use cases	Lenovo
R3-225544	MRO related objectives	Huawei
R3-225545	MRO: voice fallback	Huawei
R3-225551	SON enhancements for Mobility Robustness	Ericsson
R3-225608	Further discussion on MRO enhancements in Rel-18	ZTE
R3-225609	TP for BL CR 36.300 and 36.423 on MRO for SCG failure in EN-DC	ZTE
R3-225773	MRO for fast MCG recovery	Intel Corporation
R3-225774	MRO for voice fallback	Intel Corporation
R3-225790	Discussion on MRO enhancement	CATT
R3-225808	SON MDT enhancement for MR-DC CPAC	CMCC
R3-225835	MRO for inter-system handover voice fallback and fast MCG recovery	China Mobile Com. Corporation
R3-225908	CB: # SONMDT2_MRO - Summary of email discussion	Lenovo - moderator
R3-226004	WF on the MRO scenarious	Lenovo

10.2.3: RACH Enhancements

TDoc	Title	Source
R3-225312	LS on SN RACH report status in R17	RAN2
R3-225407	RACH optimization enhancements	Qualcomm Incorporated
R3-225508	Reply LS on SN RACH report status in R17	Ericsson
R3-225552	RACH Optimization enhancement	Ericsson
R3-225592	On RACH Report retrieval	Nokia, Nokia Shanghai Bell
R3-225642	(TPs to TS 38.473 and TS 38.423 BL CRs): Discussion on RACH optimisation	Huawei
R3-225698	Discussion on SON for RACH	Samsung
R3-225775	RACH report optimization	Intel Corporation
R3-225791	Discussion on RACH enhancement	CATT
R3-225807	SONMDT enhancement for RACH report	CMCC
R3-225809	draft reply LS on SN RACH report status in Rel-17	CMCC
R3-225867	Discussion on RACH report	ZTE
R3-225909	CB: # SONMDT3_RACH - Summary of email discussion	CMCC - moderator
R3-226005	Reply LS on SN RACH report status in R17	CMCC
R3-226053	Reply LS on SN RACH report status in R17	CMCC

10.2.4: SON/MDT Enhancements for Non-Public Networks

TDoc	Title	Source
R3-225408	SON MDT enhancements for Non-Public networks	Qualcomm Incorporated
R3-225553	SON enhancements for Non-public networks	Ericsson
R3-225593	On specification impact for MDT enhancements for SNPN and PNI-NPN	Nokia, Nokia Shanghai Bell
R3-225594	Support of MDT enhancements	Nokia, Nokia Shanghai Bell
R3-225643	(TP for TS 38.413 BLCR): SON/MDT for NPN	Huawei
R3-225699	Discussion on SON for NPN	Samsung
R3-225792	Discussion on SON enhancement for NPN	CATT
R3-225868	Discussion on MDT support in NPN and TPs	ZTE
R3-225910	CB: # SONMDT4_NPN - Summary of email discussion	ZTE - moderator
R3-225983	LS on user consent of Non-public Network	ZTE
R3-226006	LS on user consent of Non-public Network	ZTE

10.2.5: SON for NR-U

TDoc	Title	Source
R3-225395	MLB and MRO enhancement for NR-U	Nokia, Nokia Shanghai Bell
R3-225409	SON enhancements for NR-U	Qualcomm Incorporated
R3-225477	Discussion on MRO for NR-U	Lenovo
R3-225554	NR-U enhancements for UL MLB and MRO	Ericsson
R3-225610	Further discussion on NR-U optimization in Rel-18	ZTE
R3-225644	(TP for TS 38.423 BLCR): SON for NR-U	Huawei
R3-225700	Discussion on SON for NR-U	Samsung
R3-225793	Discussion on SON enhancement for NR-U	CATT
R3-225911	CB: # SONMDT5_NRU - Summary of email discussion	Ericsson - moderator
R3-225976	XnAP NR-U load metrics UL for MLB	Ericsson
R3-225977	F1AP NR-U load metrics UL for MLB	Ericsson
R3-225986	CB: # SONMDT5_NRU - Summary of email discussion	Ericsson - moderator
R3-225991	(TP for 38.423 SON) XnAP NR-U load metrics UL for MLB	Ericsson
R3-226040	(TP for 38.423 SON) XnAP NR-U load metrics UL for MLB	Ericsson
R3-226047	CB: # SONMDT5_NRU - Summary of email discussion	Ericsson - moderator
R3-226054	(TP for 38.423 SON) XnAP NR-U load metrics UL for MLB	Ericsson

10.2.6: MDT Enhancements

TDoc	Title	Source
R3-225555	Signalling based immediate MDT in NR-DC	Ericsson
R3-225616	Discussion on the scenario of Signalling based logged MDT override protection	CATT
R3-225912	CB: # SONMDT6_MDT - Summary of email discussion	CATT - moderator
R3-225992	[draft] LS for the signaling based logged MDT override protection	CATT
R3-226026	CB: # SONMDT6_MDT - Summary of email discussion	CATT - moderator
R3-226055	CB: # SONMDT6_MDT - Summary of email discussion	CATT - moderator

11.1: General

TDoc	Title	Source
R3-225836	Update Workplan for Rel-18 NR QoE Enhancement	China Unicom
R3-226087	(BLCR to 38.401) Enhancement on NR QoE	Samsung
R3-226088	(BLCR to 38.473) Enhancement on NR QoE	ZTE

11.2: Support for New Service Type and RRC_INACTIVE/RRC_IDLE states

TDoc	Title	Source
R3-225331	QMC Support for High-Speed Mobility Scenarios	Ericsson
R3-225332	Paper	Ericsson
R3-225410	QMC in RRC_INACTIVE and RRC_IDLE for MBS	Qualcomm Incorporated
R3-225411	QoE enhancements for high mobility scenarios	Qualcomm Incorporated
R3-225430	NR QoE Discussion on support for new service type and RRC inactive-idle state	Samsung
R3-225478	QoE for RRC_INACTIVE/RRC_IDLE states	Lenovo
R3-225479	(TP to 38.423 & 38.420) Support of QoE measurement in RRC_INACTIVE	Lenovo
R3-225557	QoE and RVQoE Measurement Support for MBS	Ericsson
R3-225589	Enhancements to legacy framework for support of QMC for MBS	Nokia, Nokia Shanghai Bell
R3-225746	Discussion on QoE configuration in RRC_INACTIVE RRC_IDLE states	Xiaomi
R3-225763	Discussion on NR QoE for new service type	CATT
R3-225764	Discussion on NR QoE in RRC_INACTIVE/RRC_IDLE states	CATT
R3-225838	Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states	China Unicom
R3-225841	Further discussions on the support of QoE measurement in RRC_INACTIVE and RRC_IDLE states for MBS service	Huawei
R3-225842	CR on the support of QoE measurement enhancements to 38.413	Huawei
R3-225871	discussion on QoE high speed scenario	ZTE, China Telecom
R3-225872	discussion on MBS broadcast QoE config and reporting	ZTE, China Telecom
R3-225913	CB: # QoE1_Inactive_Idle - Summary of email discussion	China Unicom - moderator
R3-225960	CB: # QoE1_Inactive_Idle - Summary of email discussion	China Unicom - moderator

11.3: Support QoE for NR-DC

TDoc	Title	Source
R3-225333	Paper	Ericsson
R3-225412	Support for QoE in NR-DC	Qualcomm Incorporated
R3-225413	MDT-QoE alignment and QoE measurement continuity in mobility scenarios in NR-DC	Qualcomm Incorporated
R3-225431	NR QoE Discussion on support for NR-DC	Samsung
R3-225480	QoE measurement in NR-DC	Lenovo
R3-225481	(TP to TS 38.420) Support of QoE measurement in NR-DC	Lenovo
R3-225558	The Support for QoE and RVQoE Measurement and Reporting in NR-DC Scenarios	Ericsson
R3-225590	Handling of QMC configuration for NR-DC	Nokia, Nokia Shanghai Bell
R3-225747	Discussion on QoE in NR-DC	Xiaomi
R3-225765	Discussion on Support for legacy QoE in NR-DC	CATT
R3-225766	Discussion on Support for RV-QoE in NR-DC	CATT
R3-225819	Discussion on QoE configuration and reporting in NR-DC	ZTE, China Telecom
R3-225820	Diccussion on RVQoE configuration and reporting in NR-DC	ZTE, China Telecom
R3-225821	stage-2 TP to BL CR of 37.340 on QoE in NR-DC	ZTE, China Telecom
R3-225837	Discussion on QoE measurement in NR-DC	China Unicom
R3-225843	Further discussions on the support for QoE in NR-DC	Huawei
R3-225914	CB: # QoE2_NRDC - Summary of email discussion	Ericsson - moderator
R3-225961	CB: # QoE2_NRDC - Summary of email discussion	Ericsson - moderator

11.4: Left-over from R17

TDoc	Title	Source
R3-225334	Enhancements of Rel-17 QMC	Ericsson
R3-225335	Paper	Ericsson
R3-225414	Enhancements to RAN visible QoE	Qualcomm Incorporated
R3-225432	Discussion on QoE enhancement of R17 left-over features	Samsung
R3-225559	Enhancements of RAN Visible QoE Measurements and Reporting	Ericsson
R3-225591	QMC enhancements for RAN overload	Nokia, Nokia Shanghai Bell
R3-225689	Further discussion on the support of R17 left-over features	Huawei
R3-225690	[DRAFT] LS on RAN visible QoE value	Huawei
R3-225748	Discussion on RVQoE value	Xiaomi
R3-225749	Discussion onRVQoE Reporting	Xiaomi
R3-225767	Discussion on Left-over issues	CATT
R3-225822	Discussion on R17 QoE left issues	ZTE, China Telecom, China Unicom
R3-225823	TP to BL CR of 38.473 on RAN visible QoE	ZTE, China Telecom, China Unicom
R3-225824	TP to BL CR of 38.401 on RAN visible QoE	ZTE, China Telecom, China Unicom
R3-225840	Further discussion on R17 leftover issues	China Unicom
R3-225915	CB: # QoE3_Others - Summary of email discussion	ZTE - moderator
R3-225962	CB: # QoE3_Others - Summary of email discussion	ZTE - moderator
R3-226014	LS on RAN visible QoE value	Huawei
R3-226015	LS on including QoS flow information in the RAN visible QoE report over Uu	Huawei
R3-226027	TP to BL CR of 38.473 on RAN visible QoE	ZTE, China Telecom, China Unicom, Samsung
R3-226028	TP to BL CR of 38.401 on RAN visible QoE	ZTE, China Telecom, China Unicom, Samsung
R3-226051	TP to BL CR of 38.473 on RAN visible QoE	ZTE, China Telecom, China Unicom, Samsung, Ericsson
R3-226062	LS on including QoS flow information in the RAN visible QoE report over Uu	Huawei

12.1: General

TDoc	Title	Source
R3-225303	Draft CR to 38.300 on AI/ML for NG-RAN	CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation
R3-226085	Draft CR to 38.300 on AI/ML for NG-RAN	CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation

12.2.1: Stage2 Related

TDoc	Title	Source
R3-225510	(TP for AI/ML BLCT to TS38.300) Stage 2 Signalling Chart for AI/ML	Ericsson
R3-225583	Discussion on AI/ML Model Capability Exchange	Nokia, Nokia Shanghai Bell
R3-225701	Discussion on Stage 2 impact of AI/ML for NG-RAN	Samsung
R3-225776	Discussion on Stage 2 of AI/ML based Use Cases	Intel Corporation
R3-225810	Discussion on AI/ML Capability Exchange	CMCC
R3-225845	(TP for AI&ML BLCR for TS38.300) Further stage 2 updates on the introduction of RAN AI/ML	Huawei
R3-225877	Discussion on stage2 impacts for AIRAN feature	ZTE Corporation
R3-225878	CR to 38.401 for addition of AIML-RAN feature in the case of split architecture	ZTE Corporation
R3-225916	CB: # AIRAN1_General_Stage2 - Summary of email discussion	Ericsson - moderator
R3-226021	(TP for AI&ML BLCR for TS38.300) Further stage 2 updates on the introduction of RAN AI/ML	Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, CATT, Lenovo
R3-226045	CR to 38.401 for addition of AIML-RAN feature in the case of split architecture	ZTE Corporation
R3-226056	(TP for AI&ML BLCR for TS38.300) Further stage 2 updates on the introduction of RAN AI/ML	Huawei, China Mobile, CATT, Ericsson, Lenovo, Intel, Nokia, Nokia Shanghai Bell, Samsung, ZTE
R3-226057	CR to 38.401 for addition of AIML-RAN feature in the case of split architecture	ZTE Corporation, Samsung, Intel Corporation, CMCC

12.2.2.1: Xn interface

TDoc	Title	Source
R3-225375	AI/ML Load Balancing	NEC
R3-225376	AI/ML Energy Saving	NEC
R3-225377	Predicated resource status information in AI/ML energy saving	NEC
R3-225399	XN enhancements for NG-RAN AI/ML	Qualcomm India Pvt Ltd
R3-225425	Discussion on exchange of AI/ML capability over Xn interface	China Telecommunication
R3-225482	Discussion on AIML capability exchange	Lenovo
R3-225483	Discussion on procedure used for prediction information exchange	Lenovo
R3-225484	Discussion on procedure for measurement information exchange	Lenovo
R3-225485	Discussion on prediction and feedback transfer during handover	Lenovo
R3-225501	AI/ML parameter Open Issue List Discussion	InterDigital
R3-225502	AI/ML Radio Measurement Discussion	InterDigital
R3-225503	Discussion on Mobility Optimization Model Outputs	InterDigital
R3-225509	(TP for AI/ML BLCT to TS38.423) Procedures for exchanging AI/ML-related information	Ericsson, Inter Digital
R3-225511	Cell Trajectory Prediction exchange	Ericsson, Inter Digital, Version Wireless, Qualcomm
R3-225512	(TP for AI/ML BLCT to TS38.423) Cell trajectory prediction over Xn	Ericsson, Inter Digital, Verizon Wireless
R3-225513	Open points on capability exchange and validity time	Ericsson
R3-225514	AI/ML Network Energy Saving	Ericsson
R3-225516	AIML Load Balancing and Mobility Optimisation use cases	Ericsson
R3-225584	AI/ML Energy Saving: Energy Efficiency Metric and Procedures	Nokia, Nokia Shanghai Bell
R3-225585	AI/ML Mobility Optimization and Load Balancing Use Cases	Nokia, Nokia Shanghai Bell
R3-225586	Feedback Configuration after an AI/ML Action	Nokia, Nokia Shanghai Bell
R3-225587	Predictions Exchange between NG-RAN Nodes	Nokia, Nokia Shanghai Bell
R3-225588	(TP for TS 38.423) AI/ML Related Information and Procedures in Xn	Nokia, Nokia Shanghai Bell
R3-225702	Discussion on Xn impact of AI/ML for NG-RAN	Samsung
R3-225704	Correction of energy efficiency exchange for AI/ML for NG-RAN	Samsung
R3-225705	Correction of predicted resource status exchange for AI/ML for NG-RAN	Samsung
R3-225706	Correction of predicted UE trajectory exchange for AI/ML for NG-RAN	Samsung
R3-225726	Discussion on XnAP impacts of non-UE-associated metrics	CATT
R3-225727	Discussion on XnAP impacts of AI/ML for UE associated metrics	CATT
R3-225728	TP on TS 38.420 for AI/ML	CATT
R3-225729	TP on TS 38.423 for AI/ML	CATT
R3-225734	Open issues related to Xn interface for mobility optimization	LG Electronics Inc.
R3-225758	Signaling support for AI/ML information over Xn	AT&T
R3-225760	Further discussion on stage3 related issues for NG-RAN AI/ML	NTT DOCOMO, INC.
R3-225777	Discussion on AI/ML based network energy saving (including TP for TS 38.423)	Intel Corporation
R3-225778	Discussion on AI/ML based mobility optimization (including TP for TS 38.423)	Intel Corporation
R3-225779	Discussion on new procedures for AI/ML information exchange (including TP for TS 38.423)	Intel Corporation
R3-225780	Discussion on UE Performance and System KPI (including TP for TS 38.423)	Intel Corporation
R3-225781	Discussion on Validity Time of Predicted Information	Intel Corporation
R3-225811	Discussion on the procedure of AI/ML for NG-RAN	CMCC
R3-225812	Discussion on Open Issues for AI/ML for NG-RAN	CMCC
R3-225813	Open Issues on AI/ML for NG-RAN Energy Saving	CMCC
R3-225814	Open Issues on AI/ML for NG-RAN Mobility Optimization	CMCC
R3-225846	Further discussions on the support of mobility enhancements using AI/ML	Huawei
R3-225847	Further discussions on the support of load balancing using AI/ML	Huawei
R3-225848	Further discussions on the support of energy saving using AI&ML	Huawei
R3-225858	UE QoS Feedback	InterDigital
R3-225870	Consideration on AI/ML based mobility optimization	China Telecommunication
R3-225879	Discussion on the stage3 standard impacts of AIRAN	ZTE Corporation
R3-225880	TP to 38.423 and 38.420 for unified AI-ML procedures	ZTE Corporation
R3-225888	AI/ML Information via Xn Interface	China Telecom
R3-225891	On Energy Efficiency Metric over Xn Interface	China Telecom
R3-225917	CB: # AIRAN2_XnImpact - Summary of email discussion	Nokia - moderator

12.2.2.2: Other interfaces

TDoc	Title	Source
R3-225486	(TP for TS37.483 TS37.480) Support UE traffic prediction over E1 interface	Lenovo
R3-225703	Discussion on E1 impact of AI/ML for NG-RAN	Samsung
R3-225730	Discussion on E1AP and F1AP impacts of non-UE-associated metrics	CATT
R3-225731	Discussion on E1AP and F1AP impacts of UE-associated metrics	CATT
R3-225849	Introduction of RAN AI/ML to 38.473	Huawei
R3-225892	On the Stage 3 Impact over F1 and E1 interface	China Telecom
R3-225918	CB: # AIRAN3_F1E1Impact - Summary of email discussion	Samsung - moderator

12.3: Others

TDoc	Title	Source
R3-225398	MDT Enhancements for NG-RAN AI/ML	Qualcomm India Pvt Ltd
R3-225487	Discussion on transferring logged UE trajectory to old NG-RAN node	Lenovo
R3-225515	(TP for AI/ML BLCT to TS38.423 and TS38.413) MDT Enhancements for AI/ML	Ericsson
R3-225844	Further general considerations on NG-RAN AI/ML	Huawei
R3-225881	Discussion on MDT enhancement for continuous AI-ML related information	ZTE Corporation
R3-225882	[DRAFT] LS on the MDT enhancement to support continuous AI-ML related information reporting from UE	ZTE Corporation
R3-225919	CB: # AIRAN4_MDT - Summary of email discussion	ZTE - moderator

13.1: General

TDoc	Title	Source
R3-225317	LS on FS_VMR solutions review	SA2
R3-225344	Discussion of SA2 FS_VMR Solutions	Ericsson
R3-225357	Workplan for Rel-18 mobile IAB	Qualcomm Inc. (Rapporteur)
R3-225358	[Draft] Reply LS on FS_VMR solutions review	Qualcomm Inc.
R3-225438	Discussion on LS on VMR solutions from SA2	ZTE
R3-225452	Discussion on the questions from SA2 LS on VMR	Nokia, Nokia Shanghai Bell
R3-225453	[draft] Reply LS on FS_VMR solutions review	Nokia, Nokia Shanghai Bell
R3-225531	[Draft] Reply to LS on FS_VMR Solutions Review	Ericsson
R3-225751	Discussion on LS of FS_VMR solutions review	Xiaomi
R3-225936	CB: # IAB1_General - Summary of email discussion	Qualcomm - moderator
R3-226009	[Draft] Reply LS on FS_VMR solutions review	Qualcomm Inc.
R3-226048	Reply LS on FS_VMR solutions review	Qualcomm Inc.

13.2: Support IAB-node mobility

TDoc	Title	Source
R3-225345	The Migration Procedure for Mobile IAB-Nodes	Ericsson
R3-225359	Topology adaptation for mobile IAB	Qualcomm Inc.
R3-225434	Discussion on IAB-node mobility	Fujitsu
R3-225435	Discussion on IAB full migration	Fujitsu
R3-225439	Discussion on inter-donor migration in mobile IAB scenario	ZTE
R3-225454	IAB-DU migration based on dual-DU	Nokia, Nokia Shanghai Bell
R3-225488	Discussion on mobile IAB-node inter-donor topology adaptation	Lenovo
R3-225489	Inter-donor full migration procedure of mobile IAB-node	Lenovo
R3-225680	Disscussion on partial migration for mobile IAB	Huawei
R3-225681	Disscussion on full migration for mobile IAB	Huawei
R3-225714	Discussion on IAB-node mobility	Samsung
R3-225715	Discussion on full migration procedure	Samsung
R3-225752	Discussion on IAB-node mobility	Xiaomi
R3-225937	CB: # IAB2_Mobility - Summary of email discussion	Ericsson - moderator

13.3: Mobility Enhancements

TDoc	Title	Source
R3-225346	Enhancements for IAB-Node Mobility	Ericsson
R3-225347	paper	Ericsson
R3-225360	Enhancements for mobility of IAB-node and its served UEs	Qualcomm Inc.
R3-225436	Discussion on IAB-node mobility together with served UEs	Fujitsu
R3-225440	Discussion on enhancements to UE migration in mobile IAB scenario	ZTE
R3-225441	Discussion on mobility enhancement for mobile IAB	ZTE
R3-225455	Discussion on mobility enhancements	Nokia, Nokia Shanghai Bell
R3-225490	Mobility enhancements for mobile IAB-node and its served UE	Lenovo
R3-225491	(TP to TS 38.401) Support for group mobility of mobile IAB-node	Lenovo
R3-225682	Group mobility for mobile IAB	Huawei
R3-225683	Preconfiguration and information sharing for mobile IAB	Huawei
R3-225716	Discussion on mobility enhancements	Samsung
R3-225753	Discussion on mobility enhancement	Xiaomi
R3-225938	CB: # IAB3_MobEnh - Summary of email discussion	Huawei - moderator
R3-225980	CB: # IAB3_MobEnh - Summary of email discussion	Huawei - moderator
R3-226016	(TP for NR_mobile_IAB BL CR for TS 38.423): mobile IAB indication in HO preparation	Huawei

13.4: Mitigation of interference

TDoc	Title	Source
R3-225348	PCI Collision Avoidance for Mobile IAB-Nodes	Ericsson
R3-225361	PCI collision avoidance for mobile IAB	Qualcomm Inc.
R3-225437	Avoidance of resource collisions due to IAB-node mobility	Fujitsu
R3-225442	Discussion on enhancement for PCI collision avoidance for mobile IAB	ZTE
R3-225456	Mobile IAB interference mitigation	Nokia, Nokia Shanghai Bell
R3-225492	Interference mitigation of mobile IAB-node mobility	Lenovo
R3-225549	PCI Collision Avoidance with Mobile IAB	CANON Research Centre France
R3-225684	Discussion on the PCI collision and TAC/RANAC issue for mobile IAB	Huawei
R3-225717	Discussion on mitigation of interference	Samsung
R3-225754	Discussion on mitigation of interference	Xiaomi
R3-225939	CB: # IAB4_IntMit - Summary of email discussion	Lenovo - moderator
R3-225981	CB: # IAB4_IntMit - Summary of email discussion	Lenovo - moderator

14.1: General

TDoc	Title	Source
R3-225782	Rel-18 Further mobility enhancement BLCR for CHO with NR-DC for XnAP	Intel Corporation
R3-225885	RAN3 Work Plan for Rel-18 Further NR Mobility Enhancements WI	MediaTek Inc., Apple, Huawei

14.2: Signaling Support for L1/L2 based Inter-Cell Mobility

TDoc	Title	Source
R3-225315	LS on L1/L2-based inter-cell mobility	RAN2
R3-225350	Solutions for L1/L2 based inter-cell mobility	Ericsson
R3-225351	Additions for L1/L2 based inter-cell mobility	Ericsson
R3-225404	Signalling Support for L1/L2 based Inter-Cell Mobility	Qualcomm Incorporated
R3-225420	Consideration on support of intra-DU L1/L2 based Inter-Cell Mobility	China Telecommunication
R3-225421	Consideration on support of Intra-CU inter-DU L1/L2 based Inter-Cell Mobility	China Telecommunication
R3-225493	Discussion on L1/L2 based inter-cell mobility	Lenovo
R3-225494	(TP to TS 38.401 & TS 38.470) Support of L1/L2 based inter-cell mobility	Lenovo
R3-225573	Discussion on Intra-gNB-DU L1/L2 Inter-Cell Mobility Procedure	Nokia, Nokia Shanghai Bell
R3-225574	Discussion on Additional Considerations for L1/L2 Inter-Cell Mobility	Nokia, Nokia Shanghai Bell
R3-225617	Further discussion on L1/L2 mobility	CATT
R3-225645	Introduction of L1/L2 handover	Huawei
R3-225646	(TP for L1L2Mob BLCR for TS 38.401): Discussion on L1/L2 Mobility procedure	Huawei
R3-225648	Discussion of L1/L2 based Inter-Cell Mobility	NTT DOCOMO INC.
R3-225735	Open issues for L1/L2 based inter-cell mobility	LG Electronics Inc.
R3-225743	Discussion on collision between L1/L2 based mobility and L3 mobility	vivo
R3-225744	Discussion on L1/L2 based mobility procedures	vivo
R3-225762	Discussion on L1/L2 based Inter-cell Mobility	Samsung
R3-225783	High-level principles for L1/L2 based inter-cell mobility	Intel Corporation
R3-225784	Considerations for L1/L2 based "intra-DU" mobility (including TPs for L1/L2 Mob for TS 38.401 and TS 38.473)	Intel Corporation
R3-225785	Considerations on L1/L2 based "intra-CU inter-DU" mobility (including TPs for L1/L2 Mob for TS 38.401 and TS 38.473)	Intel Corporation
R3-225796	Discussion on L1/L2 based Inter-Cell Mobility	CMCC
R3-225815	Discussion on L1/L2 based mobility	ZTE
R3-225816	TP for L1L2Mob BL CR to TS 38.473	ZTE
R3-225924	CB: # MobilityEnh1_L1L2Mo - Summary of email discussion	Huawei - moderator
R3-225957	CB: # MobilityEnh1_L1L2Mo - Summary of email discussion	Huawei - moderator
R3-226024	Introduction of L1/L2 handover	Huawei
R3-226025	(TP for L1L2Mob BLCR for TS 38.401): Inter-DU L1/L2 Mobility procedure	Huawei
R3-226044	CB: # MobilityEnh1_L1L2Mo - Summary of email discussion	Huawei - moderator
R3-226046	Introduction of L1/L2 handover	Huawei
R3-226050	Introduction of L1/L2 handover	Huawei

14.3: Support CHO in NR-DC

TDoc	Title	Source
R3-225352	RTT issue for CHO+MR-DC	Ericsson
R3-225353	Early data forwarding aspects for CHO+MR-DC	Ericsson
R3-225366	(TP for CHO with NR-DC BLCR to TS 37.340/38.423/37.483) Data forwarding optimization	ZTE
R3-225391	[TP to BL CR to TS 38.423, CHO w/ NR-DC] Data forwarding in case of CHO with DC	Nokia, Nokia Shanghai Bell
R3-225419	CHO including target MCG and candidate SCGs	Qualcomm Incorporated
R3-225422	Consideration on data forwarding optimizations for CHO in NR-DC	China Telecommunication
R3-225495	Discussion on CHO in NR-DC	Lenovo
R3-225664	(TP to TS 37.340 BL CR) Data forwarding in CHO Related aspects	Huawei
R3-225712	Considerations on CHO with multiple SCGs	Samsung
R3-225768	Discussion on CHO with SCG	CATT
R3-225769	Discussion on CHO with multiple candidate SCGs	CATT
R3-225786	Considerations on data forwarding optimization for CHO including target MCG and target SCG	Intel Corporation
R3-225925	CB: # MobilityEnh2_CHO - Summary of email discussion	Ericsson - moderator
R3-225958	CB: # MobilityEnh2_CHO - Summary of email discussion	Ericsson - moderator

14.4: Others

TDoc	Title	Source
R3-225367	Disscussion on NR-DC with selective activation	ZTE
R3-225373	Decision on selective activation of the cell groups	NEC
R3-225392	Data forwarding considerations for selective activation	Nokia, Nokia Shanghai Bell
R3-225418	Configuration and activation of multiple cell groups in NR-DC	Qualcomm Incorporated
R3-225423	Consideration on support of selective activation of cell groups	China Telecommunication
R3-225496	(TP for TS 38.473) On SCG selective activation	Lenovo
R3-225649	Discussion of selective activation	NTT DOCOMO INC.
R3-225665	(TPs to TS 37.340, TS 38.423 BL CRs) Consideration on selective activation of SCGs	Huawei
R3-225713	Considerations on selective activation of the cell groups	Samsung
R3-225745	Considerations on NR-DC with Selective Activation	vivo
R3-225770	Discussion on NR-DC with selective activation of the cell groups	CATT
R3-225926	CB: # MobilityEnh3_Others - Summary of email discussion	Nokia - moderator
R3-225959	CB: # MobilityEnh3_Others - Summary of email discussion	Nokia - moderator

15.1: General

TDoc	Title	Source
R3-225321	LS on FS_5MBS_Ph2 progress	SA2
R3-225445	On SA2 LS on FS_5MBS_Ph2 progress	Ericsson
R3-225533	Feedback to SA2 on FS_5MBS_Ph2 Progress	Nokia, Nokia Shanghai Bell
R3-225660	Consideration on SA2 LS on FS_5MBS_Ph2 progress	Huawei, CBN, China Unicom
R3-225661	[DRAFT] Reply LS on FS_5MBS_Ph2 progress	Huawei
R3-225761	Plan on Baseline CR assignment for Rel-18 MBS enhancement	CATT
R3-225920	CB: # MBS1_Workplan_SA2LS - Summary of email discussion	Huawei - moderator
R3-225987	Reply LS on FS_5MBS_Ph2 progress	Huawei
R3-225995	CB: # MBS1_Workplan_SA2LS - Summary of email discussion	Huawei - moderator

15.2: Support for MBS reception in RAN sharing scenarios

TDoc	Title	Source
R3-225330	Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario	RAN
R3-225338	Broadcast reception in a certain area	TD Tech, Chengdu TD Tech
R3-225340	Support of MBS in RAN sharing scenarios	Qualcomm Incorporated
R3-225378	MBS RAN sharing scenario	NEC
R3-225450	On Support for MBS reception in RAN sharing scenarios	Ericsson
R3-225464	Discussion on MBS RAN sharing	Samsung R&D Institute UK
R3-225662	(TPs to TS 38.300, TS 38.413 BL CRs) MBS reception in RAN sharing scenario	Huawei, CBN
R3-225724	Discussion on efficient MBS reception in RAN sharing scenario	CATT
R3-225797	Discussion on MBS reception in RAN sharing scenarios	CMCC
R3-225853	MBS reception in RAN sharing scenarios	ZTE
R3-225921	CB: # MBS2_NetworkSharing - Summary of email discussion	CATT - moderator
R3-225945	Response to R3-225450	Nokia, Nokia Shanghai Bell
R3-225982	CB: # MBS2_NetworkSharing - Summary of email discussion	CATT - moderator
R3-226031	[Draft] LS on resource efficiency for MBS reception in RAN sharing scenario	CATT
R3-226058	[Draft] LS on resource efficiency for MBS reception in RAN sharing scenario	CATT
R3-226081	CB: # MBS2_NetworkSharing - Summary of email discussion	CATT - moderator
R3-226084	LS on resource efficiency for MBS reception in RAN sharing scenario	CATT

15.3: Support for RRC_INACTIVE state

TDoc	Title	Source
R3-225337	Multicast reception in RRC_INACTIVE state	TD Tech, Chengdu TD Tech
R3-225339	Enhancements to support Multicast reception by UEs in RRC_INACTIVE state	Qualcomm Incorporated
R3-225379	MBS Inactive Reception	NEC
R3-225380	CR for RRC_INACTIVE MBS interested indication in 38.473	NEC
R3-225451	On support of multicast reception in RRC_INACTIVE state	Ericsson
R3-225465	Discussion on MC support for RRC Inactive	Samsung R&D Institute UK
R3-225497	PTM configuration for multicast reception in RRC_INACTIVE	Lenovo
R3-225498	Mobility and state transition for multicast reception in RRC_INACTIVE	Lenovo
R3-225534	Information needed at gNB to enable multicast RRC inactive delivery mode	Nokia, Nokia Shanghai Bell
R3-225663	(TP to TS 38.300 BL CR) Multicast Reception for RRC_INACTIVE state Ues	Huawei, CBN
R3-225725	Discussion on multicast over RRC INACTIVE	CATT
R3-225798	Multicast Reception in RRC_INACTIVE state	CMCC
R3-225854	Multicast reception in RRC_INACTIVE	ZTE
R3-225922	CB: # MBS3_RRCInactive - Summary of email discussion	ZTE - moderator
R3-225969	Support of Enhancement of NR Multicast and Broadcast Services	Nokia, Nokia Shanghai Bell
R3-226033	CB: # MBS3_RRCInactive - Summary of email discussion	ZTE - moderator

16.2: Support Relay and Remote UE Authorization

TDoc	Title	Source
R3-225322	LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN	SA2
R3-225354	Authorization for U2U relay	Ericsson
R3-225415	Authorization for multi-path and U2U relays	Qualcomm Incorporated
R3-225466	Discussion on RAN3 impacts on U2U relay	ZTE
R3-225927	CB: # SLRelay1_Authorization - Summary of email discussion	ZTE - moderator

16.3: Support Service Continuity Enhancements

TDoc	Title	Source
R3-225355	Inter-gNB aspects of Service Continuity for L2 U2N Relays	Ericsson
R3-225416	Service continuity enhancements for L2 relays	Qualcomm Incorporated
R3-225426	Inter-node path switching for U2N relays	China Telecommunication
R3-225457	Discussion on Support Service Continuity Enhancements	Nokia, Nokia Shanghai Bell
R3-225500	Selection of the target relay UE for service continuity	InterDigital
R3-225546	SL relay: Inter-gNB mobility	Huawei
R3-225708	(TP to TS 38.401) Further discussion on service continuity enhancement	Samsung
R3-225755	(TP to TS 38.401) Consideration on service continuity enhancement for L2 U2N relay	LG Electronics
R3-225794	Discussion on Service Continuity Enhancements for SL relay	CATT
R3-225802	Service continuity on U2N relay	CMCC
R3-225928	CB: # SLRelay2_ServiceContinuity - Summary of email discussion	Qualcomm - moderator
R3-225954	CB: # SLRelay2_ServiceContinuity - Summary of email discussion	Qualcomm - moderator

16.4: Multi-path Support

TDoc	Title	Source
R3-225428	On multi-path support for sidelink relay	China Telecommunication
R3-225458	discussion on the support for multi-path	Nokia, Nokia Shanghai Bell
R3-225467	Further study on multi-path relay and service continuity of L2 U2N relay	ZTE
R3-225547	SL relay: U2U relay and Multi-path relay	Huawei
R3-225709	(TP to TS 38.401) Further discussion on multipath for sidelink relay	Samsung
R3-225756	(TP to TS 38.401) Consideration on multi-path support	LG Electronics
R3-225795	Discussion on Multi-path Support for SL relay	CATT
R3-225803	Configurations on multi-path	CMCC
R3-225929	CB: # SLRelay3_Others - Summary of email discussion	LG Electronics - moderator
R3-225955	CB: # SLRelay3_Others - Summary of email discussion	LG Electronics - moderator

17.1: General

TDoc	Title	Source
R3-225923	R18 WI NR-NTN-enh work plan at RAN1, 2 and 3	THALES

17.2: Support Mobility and Service Continuity Enhancements

TDoc	Title	Source
R3-225396	Cell Identifier for NTN handover	Qualcomm India Pvt Ltd
R3-225397	NTN Mobility and Feeder Link Switch Over Enhancements	Qualcomm India Pvt Ltd
R3-225427	Discussion on NTN mobility enhancements	China Telecommunication
R3-225459	Discussion on the Mobility and Service Continuity Enhancements in NR NTN	Nokia, Nokia Shanghai Bell
R3-225499	Xn interface enhancements in NTN	InterDigital
R3-225579	CHO for NTN - NGAP impacts	Ericsson, Thales, ZTE, Omnispace, TTP, CATT
R3-225580	CHO for NTN - XnAP Impacts	Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT
R3-225611	Further discussion on mobility issue for NR NTN	ZTE
R3-225622	Discussion on Mobility enhancement for NR NTN	CATT
R3-225692	Further discussion on mobility of NTN	Huawei
R3-225711	Discussion on service continuity enhancement	Samsung
R3-225800	Discussion on mobility enhancement of NTN	CMCC
R3-225930	CB: # NTN1_ServiceContinuity - Summary of email discussion	Huawei - moderator
R3-225951	CB: # NTN1_ServiceContinuity - Summary of email discussion	Huawei - moderator
R3-225989	CHO for NTN - NGAP impacts	Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes, EchoStar
R3-225990	CHO for NTN - XnAP Impacts	Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, Huawei, CMCC
R3-226065	CHO for NTN - XnAP Impacts	Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, Huawei, CMCC
R3-226066	XnAP BLCR on NTN Functionality	Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC
R3-226075	CB: # NTN1_ServiceContinuity - Summary of email discussion	Huawei - moderator

17.3: Network verified UE location

TDoc	Title	Source
R3-225307	LS on LCS framework for Network verified UE location (NTN)	RAN2
R3-225460	Discussion on the network verified UE location	Nokia, Nokia Shanghai Bell
R3-225581	Capturing Initial Agreements on Network Verified UE Location	Ericsson, CATT, Thales
R3-225582	UE Location Verification by the Network	Ericsson, CATT, Thales, Huawei
R3-225612	Cause value on network verified UE location for NR NTN	ZTE
R3-225623	Discussion on UE location verification for NR NTN	CATT
R3-225693	Discussion on network verified UE location	Huawei
R3-225801	Consideration on UE Location Verification via Network	CMCC
R3-225931	CB: # NTN2_LocationVerification - Summary of email discussion	Ericsson - moderator
R3-225952	CB: # NTN2_LocationVerification - Summary of email discussion	Ericsson - moderator
R3-225956	UE Location Verification by the Network	Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell

18.2: Support discontinuous coverage

TDoc	Title	Source
R3-225461	Discussion on the support for discontinuous coverage	Nokia, Nokia Shanghai Bell
R3-225462	Support for IoT NTN enhancements	Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson
R3-225613	Further discussion on discontinuous coverage issue for IoT NTN	ZTE
R3-225614	Discussion on discontinuous coverage(draft LS included )	CATT
R3-225691	Further discussion on the support of discontinuous coverage	Huawei
R3-225932	CB: # IoTNTN_Coverage - Summary of email discussion	ZTE - moderator

19.1: General

TDoc	Title	Source
R3-225570	Uncrewed Aerial Vehicles in Rel-18 - workplan	Nokia, Nokia Shanghai Bell

19.2: Support Subscription-based Aerial-UE Identification

TDoc	Title	Source
R3-225374	UAV Support over NG-RAN interface	NEC
R3-225572	On subscription-based UAV UE identification	Nokia, Nokia Shanghai Bell
R3-225618	Subscription-based Aerial-UE Identification for NR	CATT
R3-225694	Initial discussion on NR support for UAV	Huawei
R3-225804	Subscription-based aerial-UE identification for NR UAV	CMCC
R3-225855	NR support for UAV WI	Ericsson
R3-225856	Introduction of Aerial authorization information	Ericsson, AT&T, NTT DOCOMO, INC, Qualcomm Incorporated, Intel Corporation
R3-225875	Discussion on NR support for UAV	ZTE
R3-225933	CB: # UAV_Identification - Summary of email discussion	Nokia - moderator
R3-225948	Introduction of Aerial authorization information	Ericsson, AT&T, NTT DOCOMO, INC, Qualcomm Incorporated, Intel Corporation

22.1: General

TDoc	Title	Source
R3-225869	Work plan for NR network-controlled repeaters	ZTE

22.2: Support Network-Controlled Repeater Management

TDoc	Title	Source
R3-225362	RAN3 Aspects of Network-Controlled Repeater	Qualcomm Inc.
R3-225463	Discussion on Identification and authorization of Network Controlled Repeater	Nokia, Nokia Shanghai Bell
R3-225577	Authorization for Network-Controlled Repeaters	Ericsson LM
R3-225578	Network-Controlled Repeaters Authorization - Solution 4	Ericsson LM
R3-225626	Discussion on NCR management	CATT
R3-225627	CR for TS 38.413 Support NCR authorization	CATT
R3-225651	Authorization for Network Controlled Repeater	Samsung
R3-225666	(TPs to TS 38.300, TS 38.413 BL CRs) Support of Network-Controlled Repeater	Huawei
R3-225667	(TPs to TS 38.401, TS 38.473 BL CRs) Support of Network-Controlled Repeater in disaggregated architecture	Huawei
R3-225759	Authorization for NR network-controlled repeaters	AT&T
R3-225787	A possible smart approach for NCR management solution	Intel Corporation
R3-225873	discussion on NCR management	ZTE
R3-225874	discussion on network architecture for NCR	ZTE
R3-225887	On Solution 3 and Solution 4 for Repeater management	China Telecom
R3-225934	CB: # NCR_Solution - Summary of email discussion	ZTE - moderator

23.1: General

TDoc	Title	Source
R3-225624	Work Plan for Study Item on Expanded and Improved NR Positioning	CATT

23.2: Support Enhancements on NR Positioning

TDoc	Title	Source
R3-225318	LS on Terminology Alignment for Ranging/Sidelink Positioning	SA2
R3-225548	Enhancements to Positioning in RRC_INACTIVE State for LPHAP	Qualcomm Incorporated
R3-225556	Remaining RAN3 aspects of Rel-18 NR Positioning study	Nokia, Nokia Shanghai Bell
R3-225569	Discussion on the SA2 LS on Terminology Alignment for Ranging/Sidelink Positioning	Ericsson
R3-225625	Consideration on SL Positioning Terms and Scenarios	CATT
R3-225647	Discussion on sidelink positioning	Huawei
R3-225710	Further discussion on sidelink positioning	Samsung
R3-225799	Consideration on Sidelink positioning	CMCC
R3-225826	Discussion on sidelink positioning configuration	ZTE Corporation
R3-225940	CB: # Positioning_PosEnh - Summary of email discussion	Nokia - moderator

24.1: General

TDoc	Title	Source
R3-225668	Work plan for NR network energy savings	Huawei
R3-225669	TR 38.864 v0.1.0 for information	Huawei

24.2: Support Network Energy Savings

TDoc	Title	Source
R3-225417	Information exchange over network interfaces for network energy savings	Qualcomm Incorporated
R3-225565	Discussion on Network Energy Saving SI	Ericsson
R3-225595	(TP for TR 38.864) Increased autonomy for cell switch-on/off in the gNB-DU	Nokia, Nokia Shanghai Bell
R3-225670	Network energy saving techniques	Huawei
R3-225707	Discussion on network energy saving	Samsung
R3-225723	TP for 38.864 on beam level activation/deactivation	CATT
R3-225839	Discussion on NW Energy Saving and TP to TR38.864	ZTE
R3-225935	CB: # NetworkES_Scenarios - Summary of email discussion	Huawei - moderator
R3-225953	CB: # NetworkES_Scenarios - Summary of email discussion	Huawei - moderator
R3-226001	Network energy saving techniques	Huawei
R3-226002	LS on Cell DTX/DRX for NR network energy savings	Huawei