RAN3#120

3: Approval of the Agenda

TDoc	Title	Source
R3-232501	RAN3#120 Meeting Agenda	RAN3 Chair

4: Approval of the minutes from previous meetings

TDoc	Title	Source
R3-232502	RAN3#119bis-e Meeting Report	ETSI-MCC

5: Documents for immediate consideration

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

7: General, protocol principles and issues

TDoc	Title	Source
R3-232918	TR 30.531 v1.46.0 Work Plan and Working Procedures - RAN WG3	ETSI-MCC
R3-233306	TR 30.531 v1.46.0 Work Plan and Working Procedures - RAN WG3	ETSI-MCC

8.1: New Incoming LSs

TDoc	Title	Source
R3-232508	Reply LS on Network Triggered Service Request for a UE in Suspend State	SA2(Ericsson)
R3-232511	Reply LS on 3GPP work on Energy Efficiency	CT3(Huawei)
R3-232572	LS on flightpath information forwarding for UAV	RAN2(Intel)
R3-232574	Reply LS on 1-symbol PRS	RAN2(ZTE)
R3-232578	LS on TSCAI for XR	RAN2(Nokia)
R3-232579	LS on progress of 3GPP SA5 R18 work on intent driven management	SA5(Huawei)
R3-232580	Reply LS on secured and trusted access to the serving PLMN OAM server by a MBSR	SA5(Huawei)
R3-232581	Reply LS on Performance measurement for AI/ML	SA5(Intel, NEC)
R3-232727	Flightpath information forwarding for Rel-18 UAV	NEC
R3-232728	(TP to baseline CR for 38.423) UAV Flightpath information forwarding	NEC
R3-232729	(TP to baseline CR for 38.413) UAV Flightpath information forwarding	NEC
R3-232961	Discussion on flightpath information forwarding for UAV	Huawei
R3-232962	(TP to 38.413) Support flightpath information forwarding for UAV-option1	Huawei
R3-232963	(TP to 38.423) Support flightpath information forwarding for UAV-option1	Huawei
R3-232964	(TP to 38.413) Support flightpath information forwarding for UAV-option2	Huawei
R3-232965	(TP to 38.423) Support flightpath information forwarding for UAV-option2	Huawei
R3-232966	[draft] Reply LS on flightpath information forwarding for UAV	Huawei
R3-233056	Discussion on TSCAI for XR	Ericsson
R3-233057	TP to NGAP BL CR: Support of XR TSCAI	Ericsson
R3-233238	Discussion on Flight Path in UAV	Ericsson
R3-233239	Text Proposal on 38.300 BL draftCR: target Node obtains flight path	Ericsson
R3-233240	Text Proposal on NGAP BL CR: Flight Path in UAV	Ericsson
R3-233241	Text Proposal on XnAP BL CR: Flight Path in UAV	Ericsson
R3-233242	Text Proposal on 38.300 BL draftCR: Flight Path in UAV in HO	Ericsson
R3-233243	[Draft] Reply LS on flightpath information forwarding for UAV	Ericsson
R3-233257	Discussion on NR UAV supporting and A2X supporting based on received LS and draft reply LS	ZTE
R3-233258	TP to BLCR TS 38.413 for A2X communication supporting	ZTE
R3-233259	TP to BLCR TS 38.413 for Aerial UE flightpath information	ZTE
R3-233260	TP to BLCR TS 38.423 for A2X communication supporting	ZTE
R3-233261	TP to BLCR TS 38.423 for Aerial UE flightpath information	ZTE
R3-233307	CB#1_UAVRAN2LS	ZTE
R3-233428	(TP to 38.413) Support flightpath information forwarding for UAV-option1	Huawei
R3-233431	Reply LS to RAN2 on flightpath information forwarding for UAV	ZTE
R3-233467	Text Proposal on XnAP BL CR: Flight Path in UAV	Ericsson, Nokia, Nokia Shanghai Bell, ZTE, NEC, Huawei
R3-233492	(TP to 38.413) Support flightpath information forwarding for UAV-option1	Huawei
R3-233493	Reply LS to RAN2 on flightpath information forwarding for UAV	RAN3(ZTE)
R3-233571	(BLCR to 38.413) for UAV	Huawei
R3-233572	Introduction of Aerial authorization information	Ericsson, AT&T, NTT DOCOMO INC, Qualcomm Incorporated, Intel Corporation, Samsung, NEC, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT
R3-233573	NR support for UAV over Xn	Huawei, China Unicom, China Telecom, CATT, Intel Corporation, ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung

8.2: LSin received during the meeting

TDoc	Title	Source
R3-233471	Reply LS on the maximum length of Routing ID	CT4(Huawei)
R3-233472	Reply LS on Network Triggered Service Request for a UE in Suspend State	CT4(Ericsson)

8.3: Left over LSs / pending actions

TDoc	Title	Source
R3-232591	Discussion on LS on RAN UE Id optionality	Nokia, Nokia Shanghai Bell
R3-232592	[Draft] Reply LS on RAN UE Id optionality	Nokia, Nokia Shanghai Bell
R3-232748	Use of PEI during an Emergency PDU Session	Nokia, Nokia Shanghai Bell
R3-232749	Reply LS on the use of PEI during an Emergency PDU Session	Nokia, Nokia Shanghai Bell
R3-232750	Correction of Paging with PEI	Nokia, Nokia Shanghai Bell
R3-232934	Discussion on the use of PEI during an emergency PDU session	Huawei, China Unicom, China Telecom
R3-232935	[Draft] Reply LS on the use of PEI during an emergency PDU session	Huawei
R3-232936	Disabling PEI during an emergency PDU session	Huawei, China Unicom, China Telecom
R3-232937	Disabling PEI during an emergency PDU session	Huawei, China Unicom, China Telecom
R3-233067	Discussion on the use of PEI during an emergency PDU session	Ericsson, Deutsche Telekom, AT&T, Verizon Wireless
R3-233068	Disabling UE-ID based PEI during emergency PDU session	Ericsson, Deutsche Telekom, AT&T, Verizon Wireless
R3-233069	Disabling UE-ID based PEI during emergency PDU session	Ericsson, Deutsche Telekom, AT&T, Verizon Wireless
R3-233070	Reply LS on the use of PEI during an emergency PDU session	Ericsson
R3-233135	UE identifiers for management-based trace data	Ericsson
R3-233136	[DRAFT] Reply LS on RAN UE Id optionality	Ericsson
R3-233177	Further discussion on RAN UE ID usage in trace procedure	Huawei
R3-233178	[DRAFT] Reply LS on RAN UE Id optionality	Huawei
R3-233186	Discussion on RAN UE ID for management-based TRACE and MDT	ZTE
R3-233187	[Draft]Reply Discussion on RAN UE ID for management-based TRACE and MDT	ZTE
R3-233301	Response to R3-232748, R3-232934 and R3-233067	ZTE
R3-233308	[DRAFT] Reply LS on RAN UE Id optionality	Ericsson
R3-233313	Reply LS on the use of PEI during an Emergency PDU Session	RAN3(Nokia)
R3-233476	Reply LS on RAN UE Id optionality	RAN3(Ericsson)

9.1: LTE

TDoc	Title	Source
R3-233054	Correction of NB-IoT CP optimization during AMF change	Ericsson, Nokia, Nokia Shanghai Bell
R3-233055	Correction of NB-IoT CP optimization during AMF change	Ericsson, Nokia, Nokia Shanghai Bell
R3-233129	Correction on the presence of Area Scope of QMC over NGAP	Qualcomm Incorporated
R3-233208	Correction on the QoE Area Scope IE in UE Application layer measurement configuration	China Telecom, ZTE, CMCC
R3-233262	Correction on the QoE Area Scope IE in UE Application layer measurement configuration	ZTE, China Telecom, CMCC
R3-233263	Correction on the QoE Area Scope IE in UE Application layer measurement configuration	ZTE, China Telecom, CMCC
R3-233264	Correction on the QoE Area Scope IE in UE Application layer measurement configuration	ZTE, China Telecom, CMCC
R3-233265	Correction on the QoE Area Scope IE in UE Application layer measurement configuration	ZTE, China Telecom, CMCC
R3-233266	Correction on the QoE Area Scope IE in UE Application layer measurement configuration	ZTE, China Telecom, CMCC
R3-233267	Discussion on QoE area scope IE in NR and LTE	ZTE, China Telecom, CMCC
R3-233268	Correction on the QoE Area Scope IE in QMC Configuration Information	ZTE, China Telecom, CMCC
R3-233293	Correction on the QoE Area Scope IE in QMC Configuration Information	ZTE, China Telecom, CMCC
R3-233314	Correction of NB-IoT CP optimization during AMF change	Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Inc.
R3-233315	Summary of Offline Discussion on CB: # 4_QoEAreaScope	ZTE
R3-233430	Correction on the QoE Area Scope IE in QMC Configuration Information	ZTE, China Telecom, CMCC, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei,CATT, Samsung, China Unicom, Xiaomi, Lenovo

9.2.1: Redcap

TDoc	Title	Source
R3-232836	Correction of RedCap-specific initial DL BWP without CD-SSB for SDT	Huawei, ZTE, CATT, Ericsson
R3-233058	Support of preconfigured Measurement GAPs for RedCap UE	Ericsson, Qualcomm Incorporated, CATT
R3-233085	Correction on SI delivery to RedCap UE during handover	ZTE, China Telecom, CMCC
R3-233320	CB:#8_RedcapLSout	Ericsson
R3-233346	LS on applicability of pre-configured measurement gaps for RedCap UE with NCD-SSB	RAN3(Qualcomm Inc.)
R3-233478	LS on applicability of pre-configured measurement gaps for RedCap UE with NCD-SSB	RAN3(Qualcomm)

9.2.2: MBS

TDoc	Title	Source
R3-232697	Correction of MBS multicast HFN SN Initialisation	Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated
R3-232698	Correction of MBS multicast HFN SN Initialisation	Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated
R3-232699	LS on Multicast HFN/SN Initialization for Inactive Multicast Sessions	Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated
R3-232700	Correction of Multicast Supporting Node	Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, CATT
R3-232701	Correction of Multicast Supporting Node	Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, CATT
R3-232702	Correction of MRB Setup over F1	Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, Orange, ZTE
R3-232703	Correction of MRB Setup Configuration over E1	Nokia, Nokia Shanghai Bell, Huawei, Orange
R3-232704	Correction of MRB Setup Configuration over E1	Nokia, Nokia Shanghai Bell, Huawei, Orange
R3-232862	Delay issue on initialization of initialRX-DELIV	Huawei, CBN, China Unicom, Samsung, Lenovo, CMCC
R3-232863	Correction on the delay issue on initialization of initialRX-DELIV	Huawei, CBN, China Unicom, Samsung, Lenovo, CMCC
R3-232864	[DRAFT] LS on the delay issue on initialization of initialRX-DELIV	Huawei
R3-232880	Discussion on providing of MBS-NeighbourCellList and mtch-neighbourCell	Huawei, CBN, China Unicom, Qualcomm Incorporated
R3-232884	Thoughts and Approaches for proper initialization of multicast MRB PDCP COUNT including [draft CRs for several TSs]	Ericsson
R3-232972	Correction on location dependent MBS delivery in intra-gNB mobility	ZTE
R3-233081	Correction of MRBs in context	Nokia, Nokia Shanghai Bell
R3-233321	CB:#9_InitialRX-DELIV	Ericsson
R3-233322	Correction of MRB Setup	Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, Orange, ZTE
R3-233323	CB:#10_MBSSetup	Nokia
R3-233382	Correction of MRB Setup Configuration over E1	Nokia, Nokia Shanghai Bell, Huawei, Orange

9.2.3: SCG and CPAC

TDoc	Title	Source
R3-232684	Modify the figures for MN/SN initiated CPC and CHO with SCG	ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Ercisson, Huawei
R3-233312	Modify the figures for MN/SN initiated CPC and CHO with SCG	ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Ericsson, Huawei

9.2.4: Others

TDoc	Title	Source
R3-232593	Clarification of Application Layer Measurement Collection	Nokia, Nokia Shanghai Bell
R3-232678	Clarification on usage of E-RAB Information List	NTT DOCOMO, INC., Ericsson, NEC
R3-232679	Clarification on usage of E-RAB Information List	NTT DOCOMO, INC., Ericsson, NEC
R3-232680	Clarification on usage of E-RAB Information List	NTT DOCOMO, INC., Ericsson, NEC
R3-232695	Discussion on UDC Parameters in E1AP	China Telecom
R3-232696	Correction to UDC Parameters in E1AP	China Telecom,
R3-232705	Correction of Xn Handover	Nokia, Nokia Shanghai Bell
R3-232706	Correction of Xn Handover	Nokia, Nokia Shanghai Bell
R3-232707	Correction of Xn Handover	Nokia, Nokia Shanghai Bell
R3-232708	Correction of Xn Handover	Nokia, Nokia Shanghai Bell
R3-232746	Correction on E-UTRA - NR Cell Resource Coordination	Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell, ZTE
R3-232747	Correction on E-UTRA - NR Cell Resource Coordination	Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell, ZTE
R3-232827	Mapping of SRB1 for the remote UE	Huawei, Samsung, China Telecom, LG Electronics
R3-232828	Mapping of SRB1 for the remote UE	Huawei, Samsung, China Telecom, LG Electronics
R3-232837	Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters	Huawei, Deutsche Telekom, Orange, BT
R3-232838	Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters	Huawei, Deutsche Telekom, Orange, BT
R3-232839	Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters	Huawei, Deutsche Telekom, Orange, BT
R3-232877	Correction of data forwarding for split PDU session	Huawei, Nokia, Noia Shanghai Bell, Qualcomm Incorporated, CMCC
R3-232878	Correction of data forwarding for split PDU session	Huawei, Nokia, Noia Shanghai Bell, Qualcomm Incorporated, CMCC
R3-232879	Correction of data forwarding for split PDU session	Huawei, Nokia, Noia Shanghai Bell, Qualcomm Incorporated, CMCC
R3-232907	Correction on QoS mapping information	Huawei, Lenovo, Samsung, Nokia, Nokia Shanghai Bell
R3-232908	Correction on QoS mapping information	Huawei, Lenovo, Samsung, Nokia, Nokia Shanghai Bell
R3-232909	Correction on IAB bar configuration	Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Xiaomi
R3-232910	Correction on IAB bar configuration	Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Xiaomi
R3-232920	Clarify the usage of IAB Supported IE	Nokia, Nokia Shanghai Bell, Huawei, China Telecom, Xiaomi
R3-232921	Clarify the usage of IAB Supported IE	Nokia, Nokia Shanghai Bell, Huawei, China Telecom, Xiaomi
R3-232922	Clarify the usage of IAB Supported IE	Nokia, Nokia Shanghai Bell, Huawei, China Telecom, Xiaomi
R3-232923	Clarify the usage of IAB Supported IE	Nokia, Nokia Shanghai Bell, Huawei, China Telecom, Xiaomi
R3-232933	Discussion on the multiple traces	BEIJING SAMSUNG TELECOM R&D
R3-232987	SRS Resource correction on Comb 8, Number of Symbols and Repetition Factor	Huawei, CMCC, China Telecom
R3-232988	SRS Resource correction on Comb 8, Number of Symbols and Repetition Factor	Huawei, CMCC, China Telecom
R3-232989	Subcarrier Spacing FR2 correction	Huawei, Ericsson, CMCC, China Telecom
R3-232990	Subcarrier Spacing correction	Huawei, Ericsson, CMCC, China Telecom
R3-232991	Subcarrier Spacing correction	Huawei, Ericsson, CMCC, China Telecom
R3-232992	Subcarrier Spacing correction	Huawei, Ericsson, CMCC, China Telecom
R3-232993	Subcarrier Spacing correction	Huawei, Ericsson, CMCC, China Telecom
R3-233052	Correction on F1AP for L2 U2N Relay	Philips International B.V., ZTE
R3-233053	Correction of SDT with UE context relocation	Ericsson, ZTE, China Telecom
R3-233071	Correction on F1AP for L2 U2N Relay	Philips International B.V., ZTE
R3-233072	Correction on F1AP for L2 U2N Relay	Philips International B.V., ZTE
R3-233084	Correction on L2 U2N Relay Remote UE RRC procedures	Philips International B.V., ZTE
R3-233104	Multiple traces in RAN	Ericsson
R3-233105	Correcting missing extension containers in CHOICE type definitions	Ericsson, InterDigital, Orange, CATT, Deutsche Telekom, Nokia, Nokia Shanghai Bell, AT&T, ZTE
R3-233106	Correcting missing extension containers in CHOICE type definitions	Ericsson, InterDigital, Orange, CATT, Deutsche Telekom, Nokia, Nokia Shanghai Bell, AT&T, ZTE
R3-233123	Correction to System Information Delivery procedure	Ericsson, Google
R3-233124	Correction to System Information Delivery procedure	Ericsson, Google
R3-233132	Clarification of the RAN UE ID usage in stage-2	Ericsson, Orange, Deutsche Telekom
R3-233133	Clarification of the RAN UE ID usage in stage-2	Ericsson, Orange, Deutsche Telekom
R3-233134	Clarification of the RAN UE ID usage in stage-2	Ericsson, Orange, Deutsche Telekom
R3-233137	Restriction of NIA0 algorithm in gNB-CU-UP	Ericsson
R3-233138	Restriction of NIA0 algorithm in gNB-CU-UP	Ericsson
R3-233139	Restriction of NIA0 algorithm in gNB-CU-UP	Ericsson
R3-233155	Correction of SIType List	Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung
R3-233156	Correction of SIType List	Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung
R3-233157	Correction of SIType List	Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung
R3-233158	Correction of SIType List	Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung
R3-233159	Correction of SIType List	Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung
R3-233169	Discussion on multiple Trace Session activation	CATT,ZTE,CMCC
R3-233170	[Draft]LS on multiple Trace Session activations	CATT,ZTE,CMCC
R3-233201	Discussion on inter-node message for CU-DU split scenario	Samsung
R3-233202	Correction to TS 38.473 on inter-node message for CU-DU split scenario_(Rel-16)	Samsung
R3-233203	Correction to TS 38.473 on inter-node message for CU-DU split scenario_(Rel-17)	Samsung
R3-233206	Clarification on mobility restriction list for MR-DC with 5GC	Huawei
R3-233207	Clarification on mobility restriction list for MR-DC with 5GC	Huawei
R3-233223	Discussion on exchanging AMF Set information over Xn	CMCC
R3-233224	Correction on AMF Set Information over Xn	CMCC, Huawei
R3-233247	Correction for UP security mechanism for Xn handover	ZTE, Nokia, Nokia Shanghai Bell, CMCC, China Telecom, China Unicom
R3-233248	Correction for UP security mechanism for Xn handover	ZTE, Nokia, Nokia Shanghai Bell, CMCC, China Telecom, China Unicom
R3-233249	Correction for UP security mechanism for Xn handover	ZTE, Nokia, Nokia Shanghai Bell, CMCC, China Telecom, China Unicom
R3-233269	Correction on the QoE Area Scope IE in QMC Configuration Information	ZTE, China Telecom, CMCC
R3-233270	Discussion on partial list indicator in XnAP procedures	ZTE, China Unicom
R3-233271	Correction to TS 38.423 on Partial List Indicator and Maximum Cell List Size	ZTE, China Unicom
R3-233272	Correction to TS 38.423 on Partial List Indicator and Maximum Cell List Size	ZTE, China Unicom
R3-233274	Discussion on Security Issues in SDT	China Telecom
R3-233277	Correction to Security Issues for MO-SDT	China Telecom,ZTE, CATT,Lenovo, Nokia, Nokia Shanghai Bell
R3-233279	Dicussion on SI request in F1AP	ZTE, China Telecom, CMCC, China Unicom
R3-233280	Correction on system information request over F1	ZTE, China Telecom, CMCC, China Unicom
R3-233281	Correction on system information request over F1	ZTE, China Telecom, CMCC, China Unicom
R3-233289	Correction to TS 38.473 on inter-node message for CU-DU split scenario_(Rel-16)	Samsung
R3-233290	Correction to TS 38.473 on inter-node message for CU-DU split scenario_(Rel-17)	Samsung
R3-233298	Clarification of the RAN UE ID usage in stage-2	Ericsson, Orange, Deutsche Telekom
R3-233299	Clarification of the RAN UE ID usage in stage-2	Ericsson, Orange, Deutsche Telekom
R3-233300	Clarification of the RAN UE ID usage in stage-2	Ericsson, Orange, Deutsche Telekom
R3-233302	Response to R3-232837	Nokia, Nokia Shanghai Bell
R3-233319	Correction for UP security mechanism for Xn handover	ZTE, Nokia, Nokia Shanghai Bell, CMCC, China Telecom, China Unicom
R3-233324	CB:#11_SIType	ZTE
R3-233325	Correction on QoS mapping information	Huawei, Lenovo, Samsung, Nokia, Nokia Shanghai Bell
R3-233326	Correction on QoS mapping information	Huawei, Lenovo, Samsung, Nokia, Nokia Shanghai Bell
R3-233327	CB:#13_MultipleTrace	CATT
R3-233332	Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters	Huawei, Deutsche Telekom, Orange, BT, Nokia, Nokia Shanghai Bell, Ericsson
R3-233333	Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters	Huawei, Deutsche Telekom, Orange, BT, Nokia, Nokia Shanghai Bell, Ericsson
R3-233334	Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters	Huawei, Deutsche Telekom, Orange, BT, Nokia, Nokia Shanghai Bell, Ericsson
R3-233355	SRS Resource correction on Comb 8, Number of Symbols and Repetition Factor	Huawei, CMCC, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell
R3-233356	SRS Resource correction on Comb 8, Number of Symbols and Repetition Factor	Huawei, CMCC, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell
R3-233383	Subcarrier Spacing correction	Huawei, Ericsson, CMCC, China Telecom, Nokia, Nokia Shanghai Bell
R3-233384	Subcarrier Spacing correction	Huawei, Ericsson, CMCC, China Telecom, Nokia, Nokia Shanghai Bell
R3-233385	Subcarrier Spacing correction	Huawei, Ericsson, CMCC, China Telecom, Nokia, Nokia Shanghai Bell
R3-233386	Subcarrier Spacing correction	Huawei, Ericsson, CMCC, China Telecom, Nokia, Nokia Shanghai Bell
R3-233388	Correction on F1AP for L2 U2N Relay	Philips International B.V., ZTE, Ericsson
R3-233389	Correction on L2 U2N Relay Remote UE RRC procedures	Philips International B.V., ZTE
R3-233391	Correction to UDC Parameters in E1AP	China Telecom
R3-233409	Correction of SIType List	ZTE, China Telecom, CMCC, China Unicom, Huawei
R3-233410	Correction of SIType List	Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Ericsson, Google
R3-233411	Correction of SIType List	Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, Google
R3-233412	Correction of SIType List	Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, Google
R3-233426	Correction on IAB bar configuration	Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Xiaomi, CATT, Ericsson, Qualcomm, Samsung
R3-233427	Correction on IAB bar configuration	Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Xiaomi, CATT, Ericsson, Qualcomm, Samsung
R3-233440	[Draft]LS on multiple Trace Session activations	CATT,ZTE,CMCC
R3-233441	Support of multiple Trace activations	CATT, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung
R3-233446	Correction to UDC Parameters in E1AP	China Telecom, CATT
R3-233473	Correction to Security Issues for MO-SDT	China Telecom,ZTE, CATT,Lenovo, Nokia, Nokia Shanghai Bell
R3-233481	LS on Multiple Trace/MDT configurations	RAN3(CATT)
R3-233487	Summary_of_offline_disc_CB # 11_SIType	ZTE
R3-233488	Correction of SIType List in Rel-16	ZTE, China Telecom, CMCC, China Unicom, Huawei, Ericsson, Google, Nokia, Nokia Shanghai Bell, CATT
R3-233490	Correction to Security Issues for MO-SDT	China Telecom, ZTE, CATT, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson, Huawei
R3-233501	Correction to UDC Parameters in E1AP	China Telecom,Huawei, CATT,Ericsson
R3-233521	Correction of SIType List	ZTE, China Telecom, CMCC, China Unicom, Huawei, Ericsson, Google, Nokia, Nokia Shanghai Bell, CATT
R3-233528	Correction to UDC Parameters in E1AP	China Telecom,Huawei, CATT,Ericsson, Nokia, Nokia Shanghai Bell, ZTE

9.4: Endorsed CRs from RAN3#119bis-e

TDoc	Title	Source
R3-232595	Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX	CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom
R3-232596	Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX	CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom
R3-232597	Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX	CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom
R3-232598	Introduction of the UE hashed ID to 38.423	ZTE, Nokia, Nokia Shanghai Bell, China Telecom, CATT, Huawei, Ericsson, Qualcomm
R3-232599	Correction of RAT type in Data Usage Report List for Rel-17	Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell
R3-232600	Correction of RRC Resume Cause in PATH SWITCH REQUEST message	Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated
R3-232601	Correction of RRC Resume Cause in PATH SWITCH REQUEST message	Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated
R3-232602	Correction of RAT type in Data Usage Report List	Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell
R3-232603	Correction of RAT type in Data Usage Report List	Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell
R3-232604	Correction on Event-based Reporting for Inter-system Resource Status Request	ZTE, Nokia, Nokia Shanghai Bell, China Telecom, CMCC, Lenovo
R3-232605	XnAP Rel-17 correction for NR-U metrics	Ericsson, Qualcomm Incorporated, Samsung, Nokia, Nokia Shanghai Bell
R3-232606	F1AP Rel-17 correction for NR-U metrics	Ericsson, Qualcomm Incorporated, Samsung, Nokia, Nokia Shanghai Bell
R3-232607	Correction to TS 38.423 on RB Set Configuration	ZTE, Lenovo, Qualcomm, Nokia, Nokia Shanghai Bell, CATT
R3-232608	Correction to TS 38.473 on RB Set Configuration	ZTE, Lenovo, Qualcomm, Nokia, Nokia Shanghai Bell, CATT
R3-232609	Correction of Burst Arrival Time semantics description	Ericsson, Huawei, Nokia, Nokia Shanghai Bell
R3-232610	Correction of Burst Arrival Time semantics description	Nokia, Nokia Shanghai Bell, Ericsson, Huawei
R3-232611	Correction of Burst Arrival Time semantics description	Ericsson, Huawei, Nokia, Nokia Shanghai Bell
R3-232612	Correction of Burst Arrival Time semantics description	Huawei, Ericsson, Nokia, Nokia Shanghai Bell
R3-232613	Correction on NG-U tunnel aspect for MBS session	Huawei, CBN, Lenovo, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R3-232614	Correction on Multicast session establishment	Huawei, CBN, Lenovo, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson
R3-232615	Correction on Broadcast Partial Success	Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson
R3-232616	Transfer of MBSInterestIndication from CU to DU	Google Inc.
R3-232617	Correction of Priority Level	Huawei, Deutsche Telekom, Orange, BT, Nokia, Nokia Shanghai Bell
R3-232618	Correction on behaviour procedure text for UP security procedure	ZTE, China Telecom, CATT, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson
R3-232619	Correction on E-UTRA - NR Cell Resource Coordination	Huawei, Ericsson, Orange, ZTE, Deutsche Telekom
R3-232620	Correction on E-UTRA - NR Cell Resource Coordination	Huawei, Ericsson, Orange, ZTE, Deutsche Telekom
R3-232621	Correction on E-UTRA - NR Cell Resource Coordination	Huawei, Ericsson, Orange, ZTE, Deutsche Telekom
R3-232622	Corrections on TNL association (X2)	Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei
R3-232623	Corrections on TNL association (X2)	Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei
R3-232624	Corrections on TNL association addition and removal (X2AP)	Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei
R3-232625	Missing Use Cases for Dynamic ACL	Ericsson, Deutsche Telekom, Huawei, China Telecom
R3-232626	Corrections on TNL association addition and removal (X2AP)	Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei
R3-232627	Missing Use Cases for Dynamic ACL	Ericsson, Deutsche Telekom, Huawei, China Telecom
R3-232628	Corrections on TNL association addition, update and removal (E1)	Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung
R3-232629	Corrections on TNL association addition, update and removal (E1)	Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung
R3-232630	Corrections on TNL association addition, update and removal	Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung
R3-232631	Corrections on TNL association addition, update and removal	Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung
R3-232632	Corrections on TNL association addition, update and removal	Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung
R3-232633	Corrections on TNL association addition, update and removal	Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung
R3-232634	Clarifications on TNLA Addition/Removal/Modification procedures	Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE
R3-232635	Clarifications on TNLA Addition/Removal/Modification procedures (XnAP)	Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE
R3-232636	Clarifications on TNLA Addition/Removal/Modification procedures (XnAP)	Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE
R3-232637	Clarifications on TNLA Addition/Removal/Modification procedures	Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE
R3-232638	Corrections on TNL association addition, update and removal (E1)	Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung
R3-232639	Corrections on TNL association addition, update and removal (E1)	Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung
R3-232640	Corrections on TNL association addition, update and removal (F1)	ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung
R3-232641	Corrections on TNL association addition, update and removal (F1)	ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung
R3-232642	Corrections on TNL association addition, update and removal (F1AP)	ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung
R3-232643	Corrections on TNL association addition, update and removal (F1AP)	ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung
R3-232644	Correction for UP security policy update in modification procedure	ZTE, China Telecom, CATT, China Unicom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung
R3-232645	Correction on Extended Packet Delay Budget	Nokia, Nokia Shanghai Bell, ZTE, CATT, China Telecom, Ericsson, Huawei
R3-232646	Correction on Extended Packet Delay Budget	Ericsson, ZTE, CATT, China Telecom, Nokia, Nokia Shanghai Bell, Huawei
R3-232647	Clarification on maximum length of Routing ID	NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson
R3-232648	Clarification on maximum length of Routing ID	NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson
R3-232649	Correction of QoE stage-2 description	ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, Qualcomm, Huawei, CATT, Samsung
R3-232650	Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX (stage 2)	CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom
R3-232651	Introduction of the UE hashed ID to 38.473	ZTE, Nokia, Nokia Shanghai Bell, China Telecom, CATT, Huawei, Ericsson, Qualcomm
R3-232652	Alignment of the tabular and ASN.1 definitions for the Resource Status Update	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung
R3-232653	Correction on RESOURCE STATUS FAILURE message over E1 in Rel-17	ZTE, China Telecom, CMCC, Lenovo, China Unicom
R3-232654	Correction on Mobility Change procedure	Huawei, Nokia, Nokia Shanghai Bell, Deutche Telekom, Qualcomm, ZTE, Orange, Vodafone
R3-232655	Correction on Trace Activation IE	Huawei, Deutsche Telekom, Orange, CMCC, Ericsson, Nokia, Nokia Shanghai Bell
R3-232656	Correction on the Area Scope IE in MDT Configuration	Huawei, CMCC, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Samsung
R3-232657	Correction on Mobility Change procedure	Huawei, Nokia, Nokia Shanghai Bell, Deutche Telekom, Qualcomm, ZTE, Orange, Vodafone
R3-232658	Correction on Trace Activation IE	Huawei, Deutsche Telekom, Orange, CMCC, Ericsson, Nokia, Nokia Shanghai Bell
R3-232659	Correction on the Area Scope IE in MDT Configuration	Huawei, CMCC, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Samsung
R3-232660	Alignment of the tabular and ASN.1 definitions for the Resource Status Update	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung
R3-232661	Correction on RESOURCE STATUS FAILURE message over E1 in Rel-16	ZTE, China Telecom, CMCC, Lenovo, China Unicom
R3-232662	ASN.1 Correction of PRACH Configuration	China Telecom,ZTE,CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell
R3-232663	ASN.1 Correction of PRACH Configuration	China Telecom,ZTE,CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell
R3-232664	Correction for SubcarrierSpacingSSB [NR_ext_to_71GHz-Core]	Nokia, Nokia Shanghai Bell, Qualcomm, Huawei, China Telecom, ZTE
R3-232665	Missing transmission bandwidth configurations in X2AP [NR_FR1_35MHz_45MHz_BW]	Ericsson, AT&T, Qualcomm, China Telecom, China Unicom, Samsung, CATT, CMCC, Nokia, Nokia Shanghai Bell, ZTE, Huawei
R3-232666	Correction of Extended Packet Delay Budget	ZTE, CATT,China Telecom, Nokia , Nokia Shanghai Bell, Ericsson, Huawei
R3-232667	Missing transmission bandwidth configurations in XnAP [NR_FR1_35MHz_45MHz_BW]	Ericsson, AT&T, Qualcomm, China Telecom, China Unicom, Samsung, CATT, CMCC, Nokia, Nokia Shanghai Bell, ZTE, Huawei
R3-232668	Correction of Extended Packet Delay Budget	ZTE, CATT,China Telecom, Nokia , Nokia Shanghai Bell, Ericsson, Huawei
R3-232669	Support 1-symbol PRS [1symbol_PRS]	ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Huawei
R3-232670	Support 1-symbol PRS [1symbol_PRS]	ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Huawei
R3-232785	Corrections on TNL association (X2)	Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei
R3-232786	Corrections on TNL association (X2)	Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei

10: Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI (RAN3-led)

TDoc	Title	Source
R3-233536	(BLCR for SON to 36.300) MRO and Naming	Lenovo (Beijing) Ltd

10.1: General

TDoc	Title	Source
R3-232524	(BLCR to 38.300) enhancement of SON	CMCC
R3-232525	(BLCR to 38.401) Addition of SON features enhancement	ZTE
R3-232526	(BLCR to 38.413) for SON	Ericsson
R3-232527	(BLCR to 38.423) Addition of SON features enhancement	Samsung
R3-232528	(BLCR to 38.473) Addition of SON features enhancement	Huawei
R3-232554	(BLCR to 36.423) Addition of SON features enhancement	CATT
R3-232555	(BLCR to 37.340) Addition of SON Rel.18 features	Nokia, Nokia Shanghai Bell
R3-232556	(BLCR to 38.423) for MDT	Huawei
R3-232568	(BLCR to 38.413) for MDT	Ericsson
R3-233209	Update of work Plan for Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI	CMCC
R3-233537	(BLCR to 36.423) Addition of SON features enhancement	CATT
R3-233538	(BLCR to 37.340) Addition of SON Rel.18 features	Nokia Poland
R3-233539	(BLCR to 38.300) enhancement of SON	CMCC
R3-233540	(BLCR to 38.413) for MDT	Ericsson
R3-233541	(BLCR to 38.423) for MDT	Huawei
R3-233542	(BLCR to 38.423) Addition of SON features enhancement	Samsung
R3-233543	(BLCR to 38.470) Addition of SON features enhancement	CMCC

10.2.1: SHR and SPR

TDoc	Title	Source
R3-232690	[TP to 38.423, SON] SHR and Configuration coordination for the successful PSCell change report	Nokia Austria
R3-232736	Discussion on remaining issue of inter-RAT SHR	NEC
R3-232752	(TPs for SON BLCRs for TS 38.300) SHR	Huawei
R3-232753	(TPs for SON BLCRs for TS 38.300, 38.423, 38.413) SPR	Huawei
R3-232817	(TP for SON BLCR for 38.423, 38.300 and 37.340) SON enhancement for SHR and SPR	Samsung
R3-232844	Successful Handover Report and Successful PSCell Change Report	Qualcomm Incorporated
R3-232891	Discussion on SON enhancement for SHR and SPR	CATT
R3-232946	[TP to 38.423, SON] SHR and Configuration coordination for the successful PSCell change report	Nokia, Nokia Shanghai Bell
R3-233022	SON enhancements for SHR	Lenovo
R3-233023	SON enhancements for SPR	Lenovo
R3-233091	(TP for SON BL CR for TS 38.423) Inter-RAT SHR and SPR discussion	Ericsson
R3-233188	(TPs for SON BLCRs for TS 38.300 TS 38.413 TS 38.473 and TS 38.423)Inter-RAT SHR and SPR	ZTE
R3-233210	Discussion on SON enhancement for Inter-RAT SHR	CMCC
R3-233211	Discussion on SON enhancement for SPR	CMCC
R3-233335	CB:#17_SHRSPR	Samsung
R3-233379	(TP for SON BLCR for 37.340) SON enhancement for SPR	Samsung
R3-233380	LS on SHR and SPR	RAN3(Samsung)
R3-233399	(TPs for SON BLCRs for TS 38.300) Forwarding mechanism for Inter-RAT SHR and SPR	ZTE, Samsung
R3-233408	(TPs for SON BLCRs for TS 38.300) SPR	Huawei

10.2.2: MRO

TDoc	Title	Source
R3-232693	Further discussion on the MRO for the fast MCG recovery and for CPAC	Nokia, Nokia Shanghai Bell
R3-232737	Discussion on MRO for fast MCG recovery	NEC
R3-232754	(TPs to TS 38.413 and 36.300 BL CRs) MRO	Huawei
R3-232818	(TP for SON BLCR for 38.423 and 37.340) SON enhancements for CPAC and MCG failure recovery	Samsung
R3-232819	(TP for SON BLCR for 38.413, 38.300 and 36.300) MRO for inter-system handover for voice fallback	Samsung
R3-232845	MRO enhancements for CPAC, voice fallback and fast MCG recovery	Qualcomm Incorporated
R3-232892	Discussion on MRO for CPAC	CATT
R3-232893	Discussion on MRO for fast MCG recovery and voice fallback	CATT
R3-233024	(TP for SON BLCR to TS36.300) MRO for inter-system handover for voice fallback	Lenovo
R3-233025	SON enhancements for CPAC	Lenovo
R3-233026	Update of the MRO scenarios	Lenovo, Qualcomm, Huawei
R3-233086	(TPs for SON BL CR 36.300, 38.300 and 38.413) MRO enhancemetns in Rel-18	ZTE
R3-233092	(TP for SON BL CR for TS 36.300, TS 37.340) SON enhancements for MRO	Ericsson
R3-233222	Further considerations on fast MCG recovery	CMCC, CATT
R3-233336	CB:#18_MRO	ZTE
R3-233396	(TP for SON BL CR for TS36.300) MRO for inter-system handover for voice fallback	ZTE
R3-233397	(TP for SON BL CR for TS38.300) MRO for inter-system handover for voice fallback	Samsung

10.2.3: RACH Enhancements

TDoc	Title	Source
R3-232587	(TP for SON BL CR to TS 38.473) Further discussion on RACH optimisation	Nokia, Nokia Shanghai Bell
R3-232805	Discussion on SON for RACH	Samsung
R3-232820	(TPs for SON BLCR for TS 38.470, TS 38.420, TS 36.423 and TS 36.000) Remaining issues for RACH optimisation	Huawei
R3-232846	RACH optimization enhancements	Qualcomm Incorporated
R3-232894	Discussion on RACH enhancement	CATT
R3-233093	RACH Optimization enhancement	Ericsson
R3-233189	(TPs for SON BLCRs for TS 38.423 TS 38.473 TS 37.340)RACH enhancements	ZTE
R3-233337	CB:#19_SONMDT3_RACH	Qualcomm
R3-233448	(TPs for SON BLCR for TS 38.470): Introduction of RACH Indication	Huawei
R3-233449	(TPs for SON BLCR for TS 38.420): Introduction of RACH Indication	Huawei
R3-233450	(TPs for SON BLCR for TS 36.300): Naming update for RA report	Huawei
R3-233451	(TPs for SON BLCR for TS 36.423): Introduction of RACH Indication	Huawei
R3-233456	(TP for SON BLCRs for 37.340)RACH enhancements	ZTE, Qualcomm
R3-233483	(TP for SON BLCR to TS36.423) Addition of PSCell List	Ericsson
R3-233484	(TP for SON BLCR to TS38.423) Addition of PSCell List	Ericsson
R3-233497	CB:#19_SONMDT3_RACH	Qualcomm
R3-233498	(TPs for SON BLCR for TS 38.470): Introduction of RACH Indication	Huawei, Ericsson, Nokia, ZTE
R3-233499	(TPs for SON BLCR for TS 36.423): Introduction of RACH Indication	Huawei, Ericsson, Nokia
R3-233500	(TP for SON BLCR to TS38.423) Addition of PSCell List	Ericsson

10.2.4: SON/MDT Enhancements for Non-Public Networks

TDoc	Title	Source
R3-232588	(TP for MDT BL CR to TS 38.413) Support of NPN in MDT area scope	Nokia, Nokia Shanghai Bell
R3-232674	Discussion on SONMDT enhancement for NPN	CATT
R3-232821	(TP for MDT BL CRs for TS 38.413 and TS 38.423): Remaining issues for MDT in NPN	Huawei
R3-232822	(TP for MDT BLCR for TS 37.320): MDT support in NPN	Huawei, Orange, China Telecom, CMCC
R3-232847	SON MDT enhancements for Non-Public networks	Qualcomm Incorporated
R3-232917	(TPs for MDT BLCRs for TS 38.413 and TS 38.423) SON/MDT for NPN	BEIJING SAMSUNG TELECOM R&D
R3-233094	(TP for SON BL CR for TS 38.413) SON enhancements for Non-public networks	Ericsson
R3-233095	Reply LS on user consent of Non-public Network	Ericsson
R3-233190	MDT support in NPN	ZTE
R3-233338	CB:#20_SONMDT4_SNPN	Nokia
R3-233452	(TP for MDT BL CR to TS 38.423) Support of SNPN in MDT area scope	Huawei
R3-233470	(TP for MDT BL CR to TS 38.413) Support of NPN in MDT area scope	Nokia, Nokia Shanghai Bell

10.2.5: SON for NR-U

TDoc	Title	Source
R3-232694	LBT waiting time for correct classification of MRO events	Nokia, Nokia Shanghai Bell
R3-232806	Discussion on SON for NR-U	Samsung
R3-232823	(TPs for SON BLCR for TS 38.423 and TS 38.473): SON for NR-U	Huawei
R3-232848	SON enhancements for NR-U	Qualcomm Incorporated
R3-232895	Discussion on SON enhancement for NR-U	CATT
R3-233027	Discussion on MRO for NR-U	Lenovo
R3-233087	Further discussion on NR-U optimizations	ZTE
R3-233096	NR-U enhancements for MRO and MLB	Ericsson
R3-233097	CAC per NR-U Channel	Ericsson, Deutsche Telekom, Qualcomm Incorporated
R3-233098	(TP for SON BL CR for TS 38.423) CAC per NR-U Channel	Ericsson, Deutsche Telekom, Qualcomm Incorporated
R3-233099	Radio Resource Status per NR-U Channel	Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm Incorporated
R3-233100	(TP for SON BL CR for TS 38.423) Radio Resource Status per NR-U Channel	Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm Incorporated
R3-233101	(TP for SON BL CR for TS 38.473) Radio Resource Status per NR-U Channel	Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm Incorporated
R3-233339	CB:#21_SONMDT5_NRU	Ericsson
R3-233491	(TP for SON BL CR for TS 38.423) EDT in UL	Ericsson

10.2.6: MDT Enhancements

TDoc	Title	Source
R3-232677	Signalling based logged MDT override protection	Nokia, Nokia Shanghai Bell
R3-233191	(TPs for MDT BLCRs for TS 38.413)MDT Enhancements	ZTE
R3-233340	CB:#22_SONMDT6_MDT	Nokia

11.1: General

TDoc	Title	Source
R3-232542	Support of Enhancement of NR QoE	China Unicom
R3-232543	(BLCR) Enhancement on NR QoE	Samsung
R3-232544	Enhancement on NR QoE	ZTE
R3-232582	(BLCR to 38.413) Introduction of R18 QoE measurement	Huawei, China Telecom, China Unicom
R3-233275	Update Workplan for Rel-18 NR QoE Enhancement	China Unicom
R3-233564	(BLCR to 38.300) Support of Enhancement of NR QoE	China Unicom
R3-233565	(BL CR to 38.423) QoE in NR-DC	Ericsson LM

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

TDoc	Title	Source
R3-232583	MBS idle/inactive	Nokia, Nokia Shanghai Bell, Orange
R3-232774	Discussion on NR QoE in RRC_INACTIVE/RRC_IDLE states	CATT
R3-232849	QMC for applications carried over MBS broadcast and multicast	Qualcomm Incorporated
R3-232850	QoE enhancements for high mobility scenarios	Qualcomm Incorporated
R3-232911	QoE and RVQoE Measurement Collection for Sessions Carried via MBS	Ericsson
R3-232912	QMC in HSDN Cells and High Mobility Scenarios	Ericsson
R3-232949	Further discussion on the support of MBS QoE	Huawei
R3-232954	[draft] Reply LS to Reply LS on QoE measurements in RRC IDLE/INACTIVE states	Huawei
R3-232975	QoE configuration and reporting in RRC_INACTIVE RRC_IDLE states	Xiaomi
R3-233028	Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states	Lenovo
R3-233029	(TP to 38.423 & 38.420) Support of QoE measurement in RRC_INACTIVE	Lenovo
R3-233182	Further discussion on QMC for MBS and RRC state	Samsung
R3-233255	Discussion on IDLE INACTIVE MBS QoE	ZTE
R3-233256	Discussion on high speed scenario	ZTE
R3-233291	Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states	CITC
R3-233292	Discussion on QoE measurement for high mobility scenarios	CITC
R3-233398	CB:#QoE1_MBS	Qualcomm
R3-233457	LS on QoE measurement collection for application sessions delivered via MBS broadcast or multicast	RAN3(Qualcomm)

11.3: Support QoE for NR-DC

TDoc	Title	Source
R3-232584	(TP for TS 38.300) Discussion on stage 2 description for QMC for NR-DC	Nokia, Nokia Shanghai Bell, China Unicom, Orange
R3-232585	QMC enhancements for NR-DC	Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange
R3-232775	Discussion on Support for legacy QoE in NR-DC	CATT
R3-232776	Discussion on Support for RV-QoE in NR-DC	CATT
R3-232851	Support for QoE in NR-DC	Qualcomm Incorporated
R3-232913	(TP for QoE BL CR for TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios	Ericsson
R3-232950	(TP for 38.423) on QoE measurement enhancements	Huawei, China Telecom, China Unicom
R3-232951	Further discussion on the support for QoE in NR-DC	Huawei
R3-232976	Discussion on QoE configuration and reporting in NR-DC	Xiaomi
R3-233030	Discussion on QoE measurement in NR-DC	Lenovo
R3-233183	Further discussion on support of NR-DC	Samsung
R3-233276	Discussion on QoE measurement in NR-DC	China Unicom
R3-233282	(TP to BL CR of 38.423) QoE in NR-DC	ZTE
R3-233353	SoD - QoE NR-DC	Ericsson
R3-233395	(TP for QoE BL CR for TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios	Ericsson
R3-233402	CB:#QoE2_NRDC	Ericsson
R3-233466	QMC enhancements for NR-DC	Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange, Ericsson
R3-233504	(TP to BL CR of 38.423) QoE in NR-DC	ZTE
R3-233508	(TP for QoE BL CR for TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios	Ericsson
R3-233514	(TP to BL CR of 38.423) QoE in NR-DC	ZTE, Ericsson, Lenovo, Xiaomi, Nokia, Nokia Shanghai Bell

11.4: Others

TDoc	Title	Source
R3-232570	Reply LS on Approval of eQoE CRs for NR	RAN2(Lenovo)
R3-232586	Further discussion on QoE leftovers	Nokia, Nokia Shanghai Bell
R3-232777	Discussion on Left-over issues	CATT
R3-232852	Other open topics related to QoE	Qualcomm Incorporated
R3-232914	(TP for QoE BL CR for TS 38.473) Enhancements of Rel-17 QoE and RVQoE Features	Ericsson
R3-232952	Further discussion on the support of R17 left-over features	Huawei
R3-232953	Further discussion on the support of QoE continuity during intra-5GC inter-RAT handover	Huawei
R3-232977	Discussion on RVQoE leftovers	Xiaomi
R3-233031	Discussion on QoE measurement during intra-5GC inter-RAT handover	Lenovo
R3-233278	NR QoE continuity during intra-5GC inter-RAT handover	China Unicom
R3-233283	(TP to BLCR of 38.473) other issues in NR QoE	ZTE

12.1: General

TDoc	Title	Source
R3-232521	(BLCR to 38.300) 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-232522	CR to TS 38.401 for addition of AI/ML-RAN feature in the case of split architecture	ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Intel Corporation, CMCC
R3-232523	(BLCR to 38.423) for AI/ML for NG-RAN	Ericsson
R3-233534	(BLCR to 38.300) 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-233535	(BLCR to 38.423) for AI/ML for NG-RAN	Ericsson, Nokia, Nokia Shanghai Bell

12.2.1: Stage2 Related

TDoc	Title	Source
R3-232807	Discussion on time information in AI/ML information reporting	Samsung
R3-232998	Further discussions on common issues and Stage 2 updates on the introduction of RAN AI/ML	Huawei
R3-232999	(TP for AI/ML BL CR for TS 38.300) Stage 2 updates on the introduction of RAN AI/ML	Huawei
R3-233001	(TP for TS38.300) Further discussion on AIML RAN function and timing information	ZTE
R3-233032	(TP for TS38.423 BLCR) On the naming of the new procedures	Lenovo
R3-233033	Discussion on prediction accuracy and time information	Lenovo
R3-233034	Left issues related to UE performance feedback collection	Lenovo
R3-233109	Characteristics of the procedures for exchanging AI/ML-related information	Ericsson, InterDigital, Deutsche Telekom
R3-233110	(TP for AI/ML BLCR to TS38.300) Characteristics of the procedures for exchanging AI/ML-related information	Ericsson, InterDigital, Deutsche Telekom
R3-233121	Open points on prediction accuracy	Ericsson
R3-233122	Open points on requested prediction time	Ericsson
R3-233127	Discussion on AI/ML Procedures Names	Ericsson
R3-233128	(TP for AI/ML BLCR to TS38.423) Procedure Name	Ericsson
R3-233145	Prediction Time, Validity Time and Accuracy Discussion	Nokia, Nokia Shanghai Bell
R3-233164	Discussion on various concepts about time for prediction	CATT
R3-233221	(TP for AI&ML BLCR to TS38.300) Stage 2 updates on the new procedures of AIML for RAN	CMCC, CATT, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Intel, Samsung
R3-233341	CB:#23_AIRAN1_stage2	ZTE
R3-233342	(TP for AI&ML BLCR to TS38.300) Stage 2 updates on the new procedures of AIML for RAN	CMCC, CATT, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Intel, Samsung, ZTE, Ericsson
R3-233418	(TP for AI/ML BL CR for TS 38.300) Stage 2 updates on the introduction of RAN AI/ML	Huawei, Nokia, Nokia Shanghai Bell, ZTE
R3-233434	(TP to 38.423) Addition of requested prediction time	ZTE, Nokia, Nokia Shanghai Bell,CATT, Ericsson
R3-233509	(TP to 38.423) Addition of requested prediction time	ZTE, Nokia, Nokia Shanghai Bell,CATT, Ericsson, Samsung

12.2.2.1: LB and Xn procedures

TDoc	Title	Source
R3-232742	AIML Load balancing	NEC
R3-232792	Discussion on Xn Enhancements for NG-RAN AI/ML	Qualcomm Incorporated
R3-232808	Discussion on Xn impact of LB	Samsung
R3-232811	TP to 38.423 for partial reporting of AI/ML information	Samsung
R3-232840	(TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Load Balancing use case	Huawei
R3-233002	Further discussion on remaining issues on procedures for AI	ZTE
R3-233003	(TP to 38.423 and 38.420) AIRAN impact on Xn Interface	ZTE
R3-233107	Xn Procedures for Load Balancing	Ericsson, InterDigital, Deutsche Telekom
R3-233108	(TP for AI/ML BLCR to TS 38.423) Xn Procedure for AIML Events and Load Balancing	Ericsson, InterDigital, Deutsche Telekom
R3-233119	Partial success for the AI-ML Assistance Data Reporting procedure	Ericsson, InterDigital, Deutsche Telekom
R3-233120	(TP for AI/ML BLCR to TS38.423) Partial success for the AI-ML Assistance Data Reporting procedure	Ericsson, InterDigital, Deutsche Telekom
R3-233125	Discussion on Event Based Reporting for NG-RAN AI/ML	Qualcomm Incorporated
R3-233146	(TP for TS 38.423) Open aspects on AI/ML Load Balancing and AI/ML Information Exchange	Nokia, Nokia Shanghai Bell
R3-233165	Discussion on partial success, post-handover measurement	CATT
R3-233167	(TP for 38.423) Updates to support AI/ML	CATT
R3-233216	Discussion on AI/ML remaining issues	CMCC
R3-233217	(TP for 38.423)Procedure for AIML related Information	CMCC
R3-233343	CB:#AIRAN2_LB	Ericsson
R3-233443	(TP to 38.423) AIRAN impact on Xn Interface	ZTE
R3-233462	(TP for AI/ML BLCR to TS38.423) Partial success for the AI-ML Assistance Data Reporting procedure	Ericsson, InterDigital, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Lenovo, ZTE
R3-233512	(TP for AI/ML BLCR to TS38.423) Partial success for the AI-ML Assistance Data Reporting procedure	Ericsson, InterDigital, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, CMCC
R3-233513	(TP to 38.423) AIRAN impact on Xn Interface	ZTE, Lenovo, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Ericsson

12.2.2.2: ME and Xn procedures

TDoc	Title	Source
R3-232740	AIML Mobility Enhancement	NEC
R3-232793	Discussion on Mobility Enhancement for NG-RAN AI/ML	Qualcomm Incorporated, Ericsson, Deutsche Telekom, InterDigital
R3-232809	Discussion on Xn impact of ME	Samsung
R3-232841	(TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Mobility Enhancements use case	Huawei
R3-233004	Discussion on left issues of AI based mobility optimization	ZTE
R3-233013	Discussion on Cell based UE trajectory prediction	China Telecommunication
R3-233014	(TP for AI/ML BLCR for TS 38.423) Cell based UE trajectory	China Telecommunication
R3-233035	Discussion on future UE trajectory collection after handover	Lenovo, Intel Corporation, ZTE, Nokia, Nokia Shanghai Bell
R3-233036	Discussion on transferring visited cell list to old NG-RAN node	Lenovo, ZTE, Samsung, Nokia, Nokia Shanghai Bell
R3-233037	(TP for TS38.423 BL CR) On future UE trajectory collection	Lenovo
R3-233073	Mobility Optimization Outputs and their use	InterDigital Communications
R3-233076	(TP for AIML BLCR for TS 38.423) Mobility Optimization Outputs	InterDigital Communications
R3-233111	Cell based UE trajectory prediction exchange	Ericsson, InterDigital, Qualcomm, Deutsche Telekom
R3-233112	(TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange	Ericsson, InterDigital, Qualcomm, Deutsche Telekom
R3-233147	(TP for TS 38.423) AI/ML Mobility Optimization	Nokia, Nokia Shanghai Bell
R3-233148	(TP for TS 38.423) Presence of Predicted Time UE Stays in a Cell	Nokia, Nokia Shanghai Bell
R3-233151	Discussion on UE trajectory information in mobility optimization use case	LG Electronics Inc.
R3-233152	(TP for NR_AIML_NGRAN-Core BL CR for TS 38.423) Discussion on UE trajectory information in mobility optimization use case	LG Electronics Inc.
R3-233168	(TP for 38.423) Support of AI/ML based mobility optimization	CATT
R3-233212	Discussion on Predicted UE Trajectory	CMCC
R3-233348	CB:# AIRAN3_ME	Lenovo

12.2.2.3: ES and Xn procedures

TDoc	Title	Source
R3-232741	AIML Energy Saving	NEC
R3-232794	Discussion on ES Enhancements for NG-RAN AI/ML	Qualcomm Incorporated
R3-232810	Discussion on Xn impact of ES	Samsung
R3-232812	TP to 38.423 for predicted energy saving strategy exchanging procedure for AI/ML for NG-RAN	Samsung, Lenovo
R3-232842	(TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Energy Saving use case	Huawei
R3-233005	Further discussion on AIML based energy saving	ZTE
R3-233038	Discussion on issues related to AI based network energy saving	Lenovo
R3-233113	AI-ML Network Energy Saving	Ericsson
R3-233114	(TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving	Ericsson
R3-233149	(TP for TS 38.423) Discussion on AI/ML Energy Saving Open Aspects	Nokia, Nokia Shanghai Bell
R3-233166	Discussion on the EC metric	CATT
R3-233219	Remaining Issues on AI/ML for NG-RAN Energy Saving	CMCC
R3-233220	TP for AIML Energy Saving to TR38.423	CMCC
R3-233232	Further discussion for NG-RAN AIML energy saving	NTT DOCOMO INC.
R3-233349	CB:# AIRAN4_ES	CMCC
R3-233422	LS on AI/ML for NG-RAN Energy Saving Energy Cost index	CMCC
R3-233515	LS on AI/ML for NG-RAN Energy Saving Energy Cost index	RAN3(CMCC)

12.2.2.4: Other interfaces

TDoc	Title	Source
R3-233039	(TP for TS37.480 TS38.470 BL CR) Discussion on E1 F1 interface impact	Lenovo
R3-233296	On the Support of AI/ML over F1 and E1 interface	China Telecom

12.3: Others

TDoc	Title	Source
R3-232676	Discussion on the MDT enhancement for AI	CATT
R3-232795	Discussion on MDT enhancement for NG-RAN AI/ML	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R3-232843	Further discussions on MDT enhancements	Huawei
R3-233006	Discussion on MDT enhancement for continuous AI-ML related information	ZTE, Lenovo, Samsung
R3-233007	(TP to TS38.413) MDT Enhancements for continuous data collection	ZTE, Lenovo, Samsung
R3-233008	[DRAFT] LS on the MDT enhancement to support continuous AI-ML related information reporting from UE	ZTE
R3-233115	Continuous MDT tracing	Ericsson, Deutsche Telekom, InterDigital, AT&T
R3-233116	(TP for AI/ML BLCR to TS38.423) Continuous MDT tracing	Ericsson, Deutsche Telekom, InterDigital, AT&T
R3-233117	(TP for AI/ML BLCR to TS38.413) Continuous MDT tracing	Ericsson, Deutsche Telekom, InterDigital, AT&T
R3-233118	LS on Continuous MDT	Ericsson, Deutsche Telekom, InterDigital, AT&T
R3-233150	MDT Further Enhancements in the Context of Rel.18 NG-RAN AI/ML Use Cases	Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R3-233218	Discussion on MDT enhancement for continuous MDT collection	CMCC
R3-233350	CB: # AIRAN5_MDT	CATT

13.1: General

TDoc	Title	Source
R3-232560	(BLCR to 38.413) Support for mobile IAB	Nokia, Nokia Shanghai Bell
R3-232764	Workplan for Rel-18 mobile IAB	Qualcomm Inc. (Rapporteur)
R3-233345	Offline discussion on Mobile IAB	Qualcomm Inc.
R3-233369	LS on cell ID (re)configuration for mobile IAB cell	Qualcomm
R3-233516	LS on cell ID (re)configuration for mobile IAB cell	RAN3(ZTE)
R3-233551	(BLCR to 38.413) Support for mobile IAB	Nokia, Nokia Shanghai Bell

13.2: Support IAB-node mobility

TDoc	Title	Source
R3-232724	Discussion on IAB-node DU migration	Fujitsu
R3-232725	Discussion on IAB-node consecutive partial migrations	Fujitsu
R3-232766	Topology adaptation for mobile IAB	Qualcomm Inc.
R3-232830	Migration Procedure for Mobile IAB-Nodes	Ericsson
R3-232904	(TP for NR_mobile_IAB BL CRs for TS 38.401/ 38.473) Support of mobility for mobile IAB	Huawei
R3-232924	(TP for Mobile IAB BL CR TS38.413) Discussion on Support IAB-node mobility	Nokia, Nokia Shanghai Bell
R3-232980	Discussion on IAB-node mobility	Xiaomi
R3-233000	Discussion on MT and DU Migrations of Mobile IAB-node	CANON Research Centre France
R3-233040	Discussion on mobile IAB-node inter-donor topology adaptation	Lenovo
R3-233171	(TP for NR_mobile_IAB BL CR for TS 38.401/38.423/38.473): Inter-donor migration in mobile IAB scenario	ZTE
R3-233197	Discussion on DU migration	Samsung
R3-233198	Discussion on multiple partial migration	Samsung
R3-233244	Consideration on support IAB-node mobility	CATT

13.3: Mobility Enhancements

TDoc	Title	Source
R3-232767	Enhancements for mobility of mobile IAB-node and its served UEs	Qualcomm Inc.
R3-232797	Discussion on mobility enhancements for mobile-IAB	KT Corp.
R3-232831	IAB-Node Mobility Enhancements	Ericsson
R3-232905	(TP for NR_mobile_IAB BL CR for TS 38.423): Mobility enhancement for mobile IAB	Huawei
R3-232925	Discussion on IAB configuration	Nokia, Nokia Shanghai Bell
R3-232981	Discussion on mobility enhancement	Xiaomi
R3-233041	Mobility enhancements for mobile IAB-node and its served UE	Lenovo
R3-233172	Discussion on enhancements to IAB node migration in mobile IAB scenario	ZTE
R3-233199	Discussion on mobility enhancements	Samsung
R3-233245	Enhancements for mobility IAB	CATT

13.4: Mitigation of interference

TDoc	Title	Source
R3-232768	Interference mitigation for mIAB	Qualcomm Inc.
R3-232832	PCI Collision Avoidance for Mobile IAB-Nodes	Ericsson
R3-232906	PCI collision for mobile IAB	Huawei
R3-232926	Mobile IAB interference mitigation	Nokia, Nokia Shanghai Bell
R3-232982	Discussion on PCI collision detection	Xiaomi
R3-233042	PCI collision mitigation of mobile IAB-node mobility	Lenovo
R3-233173	Discussion on PCI collision avoidance for mobile IAB	ZTE
R3-233200	Discussion on mitigation of interference	Samsung

13.5: Others

TDoc	Title	Source
R3-232765	Discusssion on issues related to SA2 VMR	Qualcomm Inc.
R3-232833	Discussion of SA2 FS_VMR Solutions	Ericsson
R3-232834	(draftCR TS 38.305) Introduction of Mobile TRP	Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-232835	Support for mobile TRP Location Information	Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-232903	(TP for NR_mobile_IAB BL CRs for TS 38.455/ 38.413/38.473) Discussion on the UE positioning and additional ULI	Huawei
R3-232927	Discussion on positioning with mobile IAB	Nokia, Nokia Shanghai Bell
R3-232978	Discussion on SA2 related issues on mobile IAB	Xiaomi
R3-232979	(CR to TS 38.473) Support of mobile TRP Location Information	Xiaomi, Ericsson, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-233043	Discussion on location information for mobile IAB	Lenovo
R3-233174	Enhancements on positioning and additional ULI for mobile IAB	ZTE
R3-233425	(CR to TS 38.473) Support of mobile TRP Location Information	Xiaomi, Ericsson, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-233463	(draftCR TS 38.305) Introduction of Mobile TRP	Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-233464	Support for mobile TRP Location Information	Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-233469	Reply LS on FS_VMR solutions review	RAN3(ZTE)
R3-233479	(TP for NR_mobile_IAB BL CR for TS 38.413) additional ULI	Huawei
R3-233502	Support for mobile TRP Location Information	Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-233505	(CR to TS 38.473) Support of mobile TRP Location Information	Xiaomi, Ericsson, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei
R3-233506	Reply LS on FS_VMR solutions review	RAN3(ZTE)
R3-233507	(CR to TS 38.473) Support of mobile TRP Location Information	Xiaomi, Ericsson, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei
R3-233517	(draftCR TS 38.305) Introduction of Mobile TRP	Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-233518	Support for mobile TRP Location Information	Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-233519	(CR to TS 38.473) Support of mobile TRP Location Information	Xiaomi, Ericsson, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei
R3-233520	(TP for NR_mobile_IAB BL CR for TS 38.413) additional ULI	Huawei

14.1: General

TDoc	Title	Source
R3-232531	(BLCR to 38.401) for L1L2Mob	Huawei, Ericsson, Nokia, Nokia Shanghai Bell
R3-232532	(BLCR to 38.473) Additions for L1/L2 triggered mobility	Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation
R3-232558	(BLCR to 37.340) Introduction of CHO with SCG(s)	CATT
R3-232559	(SCG Selective Activation BL CR to TS 38.423) Introduction of SCG Selective Activation	Huawei
R3-233141	(BLCR to 38.473) Additions for L1/L2 triggered mobility	Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation
R3-233548	(BLCR to 38.401) for L1L2Mob	Huawei, Ericsson, Nokia, Nokia Shanghai Bell
R3-233549	(SCG Selective Activation BL CR to TS 38.423) Introduction of SCG Selective Activation	Huawei
R3-233550	(BLCR to 38.473) Additions for L1/L2 triggered mobility	Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation

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

TDoc	Title	Source
R3-232569	LS on beam indication of target cell(s) and time gap between a PDCCH order and the corresponding PRACH transmission for LTM	RAN1(CATT)
R3-232575	Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM	RAN2(Fujitsu, CATT)
R3-232671	TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures	Nokia, Nokia Shanghai Bell
R3-232673	Discussion on TA Acquisition for LTM	Nokia, Nokia Shanghai Bell
R3-232726	Signaling for LTM candidate configuration	Fujitsu
R3-232730	Rel-18 LTM discussion on solutions	NEC
R3-232731	(TP to TS 38.473 on LTM) co-existence between LTM and L3 mobility	NEC
R3-232744	gNB-DU initiated target cell re-configuration for LTM	Rakuten Symphony
R3-232751	(TP to Mob_enh2 BL CR TS38.401) Discussion on L1/L2 based Inter-cell Mobility	Samsung Electronics France SA
R3-232759	(TP for LTM BL CR to TS 38.401) Solutions for LTM	Ericsson
R3-232760	(TP for LTM BL CR to TS 38.473) F1AP impacts for LTM	Ericsson
R3-232772	Signalling Support for LTM	Qualcomm Incorporated
R3-232824	(TP for L1L2Mob BLCR for TS 38.401): F1 signalling impact on the incoming LSs for LTM	Huawei
R3-232825	(TP for L1L2Mob BLCR for TS 38.401 and TS 38.473): Continuation on LTM procedure design	Huawei
R3-232829	Intra gNB CU-UP relocation during LTM	Rakuten Symphony
R3-232859	Discussion on general issues for LTM	CATT
R3-232860	Discussion about RAN1 LS about Beam indication of target cell(s)	CATT, Fujitsu
R3-232861	[Draft] Reply LS on beam indication of target cell(s) for LTM	CATT, Fujitsu
R3-233046	Discussion on L1L2 based inter-cell mobility	Lenovo
R3-233047	(TP to TS 38.401 & TS 38.470 BL CR) Support of L1L2 based inter-cell mobility	Lenovo
R3-233153	Discussion on signaling for candidate cells configuration	LG Electronics Inc.
R3-233154	(TP for NR_Mob_enh2 BL CR for TS 38.401) Discussion on signaling for candidate cells configuration	LG Electronics Inc.
R3-233195	(TP for L1L2Mob BLCR for TS 38.401) Discussion on reference configuration in LTM	Google Inc.
R3-233196	(TP for L1L2Mob BLCR for TS 38.401) Discussion on LTM execution	Google Inc.
R3-233225	Discussion on L1L2 based Inter-Cell Mobility	CMCC
R3-233226	(TP to TS 38.401) L1L2 based Inter-Cell Mobility	CMCC
R3-233233	Further discussion on LTM	NTT DOCOMO INC.
R3-233250	(TP for LTM BL CR to TS 38.473) Discussion on L1L2 triggered mobility	ZTE
R3-233251	TP for LTM BL CR to TS 38.401	ZTE
R3-233357	CB:#MobilityEnh1_L1L2Mobility	Huawei
R3-233453	(TP for L1L2Mob BLCR for TS 38.401): Introduction of LTM procedure for inter-DU with CU-UP change	Huawei, ZTE, Nokia, Nokia Shanghai Bell, CMCC, Lenovo
R3-233461	(TP for LTM BL CR to TS 38.473) F1AP impacts for LTM	Ericsson
R3-233495	TP for LTM BL CR to TS 38.401	ZTE, NEC, Huawei, Nokia, Nokia Shanghai Bell, CMCC, Ericsson, Lenovo
R3-233522	(TP for L1L2Mob BLCR for TS 38.401): Introduction of LTM procedure for inter-DU with CU-UP change	Huawei, ZTE, Nokia, Nokia Shanghai Bell, CMCC, Lenovo, Ericsson, NEC
R3-233523	(TP for LTM BL CR to TS 38.473) F1AP impacts for LTM	Ericsson

14.3: Support CHO in NR-DC

TDoc	Title	Source
R3-232685	(TP for CHO with NR-DC to TS 38.423): Early data forwarding optimization for CHO with SCG procedure	ZTE
R3-232691	[TPs to TS38423 and TS37340, CHO with NRDC] Continuation of the discussions on enhancements for CHO with MR-DC	Nokia, Nokia Shanghai Bell
R3-232761	CHO with candidate SCG(s)	Ericsson
R3-232763	Avoid unnecessary signaling due to SCG reconfigurations	Ericsson, ZTE, Lenovo
R3-232771	CHO with multiple candidate SCGs	Qualcomm Incorporated
R3-232778	Discussion on CHO with SCG and multiple SCGs	CATT
R3-232869	(TPs to TS 37.340 and 38.423 BL CRs) avoid multiple data forwarding paths	Huawei, Samsung, Lenovo, Qualcomm Incorporated
R3-232870	(TPs to TS 37.340, 38.423 BL CRs) other CHO related aspects	Huawei
R3-233048	Discussion on CHO in NR-DC	Lenovo
R3-233235	Considerations on data forwarding optimization and avoiding unnecessary signalling for CHO in NR-DC	Samsung
R3-233236	Discussion on indirect data forwarding on CHO+CPAC	Samsung
R3-233358	Summary of Offline Discussion on selected aspect of the CHO with MR-DC \n(CB: # MoblityEnh2_CHO)	Nokia

14.4: Others

TDoc	Title	Source
R3-232692	[TP to TS 38.423 for Selective Activation] RAN signalling problems for Selective Activation	Nokia, Nokia Shanghai Bell
R3-232732	Discussion on Selective Activation of the cell of groups	NEC
R3-232733	(TP to TS38.423 BL CR) Selective Activation of the cell of groups	NEC
R3-232762	(TP to TS 38.423 BL CR) NR-DC with Selective Activation	Ericsson
R3-232773	SCG Selective Activation in NR-DC	Qualcomm Incorporated
R3-232779	Discussion on NR-DC with selective activation of the cell groups	CATT
R3-232871	(TPs to TS 38.423 38.473 BL CRs) Consideration on selective activation of SCGs	Huawei
R3-233011	Discussion on SCG selective activation	China Telecommunication
R3-233012	(TP to TS 38.423 BL CR) On support of selective activation	China Telecommunication
R3-233044	(TP for TS 38.473 BL CR) On SCG selective activation	Lenovo
R3-233234	(TP to BLCR TS38.401 on SCG selective activation) Discussions on selective activation of the cell groups	Samsung
R3-233237	Discussion on selective activation	NTT DOCOMO INC.
R3-233252	(TP to TS 38.423) Support of SCG selective activation	ZTE
R3-233359	Summary of Offline Discussion on MobilityEnh3_SelectiveActivation	ZTE
R3-233496	(TP to TS 38.423) Support of SCG selective activation	ZTE
R3-233524	(TP to TS 38.423) Support of SCG selective activation	ZTE

15.1: General

TDoc	Title	Source
R3-232529	(BLCR to 38.300) introduction of NR MBS enhancements	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo
R3-232530	(BLCR to 38.401) Introduction of NR MBS enhancements	Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo
R3-232557	(BLCR to 38.470) Multicast Reception for RRC_INACTIVE state Ues	Lenovo
R3-233075	(BLCR to 38.470) Multicast Reception for RRC_INACTIVE state UEs	Lenovo, Huawei, Nokia, Nokia Shanghai Bell
R3-233373	Summary of unofficial offline Discussion on Rel-18 MBS	CATT
R3-233423	CB:#43_R18MBS	CATT
R3-233544	(BLCR to 38.300) introduction of NR MBS enhancements	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo
R3-233545	Support of MBS enhancement	Ericsson, Nokia, Nokia Shanghai Bell
R3-233546	(BLCR to 38.413) RAN sharing optimisations for MBS	Datang Mobile Com. Equipment
R3-233547	(BLCR to 38.473) Introducing MBS RAN sharing information	Samsung Electronics GmbH

15.2: Support for MBS reception in RAN sharing scenarios

TDoc	Title	Source
R3-232681	Support of MBS in RAN sharing scenarios	Qualcomm Incorporated
R3-232709	(TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions	Nokia, Nokia Shanghai Bell
R3-232867	(TPs to BL CRs) MBS reception in RAN sharing scenario	Huawei, CBN, CMCC
R3-232885	Further discussions and proposals concerning Rel-18 work on resource efficiency for MBS reception in RAN sharing scenarios	Ericsson
R3-232915	(TP for TS38.473, TS38.413 BL CR) Discussion on MBS RAN sharing	BEIJING SAMSUNG TELECOM R&D
R3-232973	(TP to TS 38.413, 38.473) Discussion on network sharing of MBS	ZTE
R3-233051	Remaining issues of supporting MBS reception in RAN Sharing	Lenovo
R3-233163	(TP for 38.401/38.413/38.473/37.483)Discussion on efficient MBS reception in RAN sharing scenario	CATT,CBN
R3-233368	(TP for BLCR 38.473) Introducing MBS RAN sharing information	Samsung, Huawei, Nokia, Nokia Shanghai Bell, CATT, ZTE, Lenovo, China Mobile, NEC, Qualcomm, Ericsson
R3-233376	(TP for 37.483)Support of efficient MBS reception in RAN sharing scenario	CATT, CBN, Samsung, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Lenovo, China Mobile, NEC, Qualcomm, Google
R3-233381	(TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions	Nokia, Nokia Shanghai Bell
R3-233390	[TP for TS 38.413] on RAN sharing optimisations for MBS	Ericsson
R3-233401	(TP for BLCR 38.473) Introducing MBS RAN sharing information	Samsung, Huawei, Nokia, Nokia Shanghai Bell, CATT, ZTE, Lenovo, China Mobile, NEC, Qualcomm, Ericsson
R3-233403	(TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions	Nokia, Nokia Shanghai Bell
R3-233415	(TP for BLCR 38.473) Introducing MBS RAN sharing information	Samsung, Huawei, Nokia, Nokia Shanghai Bell, CATT, ZTE, Lenovo, China Mobile, NEC, Qualcomm, Ericsson
R3-233416	[TP for TS 38.413] on RAN sharing optimisations for MBS	Ericsson
R3-233417	(TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions	Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Samsung, Qualcomm

15.3: Support for RRC_INACTIVE state

TDoc	Title	Source
R3-232683	Enhancements to support Multicast reception by UEs in RRC_INACTIVE state	Qualcomm Incorporated
R3-232710	(TP for TS 38.300, TS 38.413, TS 38.423) MBS Reception in RRC Inactive State	Nokia, Nokia Shanghai Bell
R3-232868	(TPs to BL CRs) Multicast Reception for RRC_INACTIVE state UEs	Huawei, CBN
R3-232886	Further discussions and proposals concerning Rel-18 work on multicast reception in RRC_INACTIVE	Ericsson
R3-232916	(TP for TS38.473 and TS38.423 BL CR) Discussion on MBS reception by inactive state UE	BEIJING SAMSUNG TELECOM R&D
R3-232974	Multicast reception in RRC_INACTIVE	ZTE
R3-233050	Discussion on multicast reception in RRC_INACTIVE	Lenovo
R3-233162	(TP for 38.413/38.423/38.473)Discussion on multicast over RRC INACTIVE	CATT,CBN
R3-233204	Multicast reception in RRC_INACTIVE state	TD Tech, Chengdu TD Tech
R3-233227	Multicast Reception in RRC_INACTIVE state	CMCC
R3-233365	[TP for BL CR 38.300] Introducing stage-2 text for the MBS Assistance Information	Ericsson
R3-233366	[TP for BL CR 38.413] Introducing the MBS Assistance Information	Ericsson
R3-233367	[TP for BL CR 38.423] Introducing the MBS Assistance Information	Ericsson
R3-233377	[TP for BL CR 38.300] Introducing stage-2 text for the MBS Assistance Information	Nokia
R3-233378	[TP for BL CR 38.413] Introducing the MBS Assistance Information	Huawei, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Lenovo, China Mobile, NEC, Qualcomm, Ericsson, CATT
R3-233387	TP to TS 38.323 on MBS assistance information for RRC Inactive	ZTE
R3-233419	[TP for BL CR 38.413] Introducing the MBS Assistance Information	Huawei, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Lenovo, China Mobile, NEC, Qualcomm, Ericsson
R3-233420	[TP for BL CR 38.300] Introducing stage-2 text for the MBS Assistance Information	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, Lenovo, China Mobile, NEC, Qualcomm, Ericsson
R3-233421	TP to TS 38.423 on MBS assistance information for RRC Inactive	ZTE

16.1: General

TDoc	Title	Source
R3-232545	(BLCR to 38.401) Introduction of NR SL relay enhancements	LG Electronics
R3-232546	(BLCR to 38.413) Support for NR Sidelink Relay Enhancements	Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, CMCC, ZTE, Samsung, LG Electronics, Huawei
R3-232547	(BLCR to 38.423) Support NR Sidelink Relay Enhancements	Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Samsung, Huawei, CATT, LG Electronics, CMCC
R3-232548	(BLCR to 38.473) Support for NR Sidelink Relay Enhancements	Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE
R3-233567	(BLCR to 38.401) Introduction of NR SL relay enhancements	LG Electronics
R3-233568	(BLCR to 38.413) Support for NR Sidelink Relay Enhancements	Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, CMCC, ZTE, Samsung, LG Electronics, Huawei
R3-233569	(BLCR to 38.423) Support NR Sidelink Relay Enhancements	Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Samsung, Huawei, CATT, LG Electronics, CMCC
R3-233570	(BLCR to 38.473) Support for NR Sidelink Relay Enhancements	Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE

16.2: Support Relay and Remote UE Authorization

TDoc	Title	Source
R3-232573	LS to SA2 on authorization for multi-path Scenario 2	RAN2(VIVO)

16.3: Support Service Continuity Enhancements

TDoc	Title	Source
R3-232738	Discussion on the support of service continuity	NEC
R3-232755	(TP for BLCR 38.401, 38.413, 38.423) Inter-gNB mobility	Huawei
R3-232757	(TP for SL Relay BL CR to TS 38.423) Inter-gNB Service Continuity for L2 U2N Relay	Ericsson
R3-232769	Further discussion on service continuity for SL relay	ZTE
R3-232896	Discussion on Service Continuity Enhancements for SL relay	CATT
R3-232928	Discussion on Support Service Continuity Enhancements	Nokia, Nokia Shanghai Bell
R3-233009	(TPs to 38.413 and 38.423) Remaining open issues on inter-gNB mobility	China Telecommunication
R3-233077	Support of service continuity enhancement for U2N relay	LG Electronics
R3-233179	Further discussion on service continuity enhancement	Samsung
R3-233213	Discussion on service continuity on U2N relay	CMCC
R3-233215	(BLCR)Support of SL relay enhancement in TS38.300	CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE
R3-233360	(BLCR)Support of SL relay enhancement in TS38.300	CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE
R3-233361	Summary of CB: # SLRelay1_ServiceContinuity	ZTE
R3-233444	(TP for SL Relay BLCR to TS 38.413) Support of service continuity enhancement for U2N relay	LG Electronics
R3-233445	(TP for SL Relay BLCR to TS 38.423) Support of service continuity enhancement for U2N relay	LG Electronics
R3-233447	(TP for SL Relay BLCR to TS 38.401) Support of service continuity	CATT
R3-233510	(TP for SL Relay BLCR to TS 38.413) Support of service continuity enhancement for U2N relay	LG Electronics
R3-233511	(TP for SL Relay BLCR to TS 38.423) Support of service continuity enhancement for U2N relay	LG Electronics

16.4: Multi-path Support

TDoc	Title	Source
R3-232739	Discussion on the support of multi-path relay	NEC
R3-232756	(TP for BLCR 38.401, 38.473) Multi-path relay	Huawei
R3-232758	Multi-path for Sidelink Relay	Ericsson
R3-232770	Discussion on multi-path relay support	ZTE
R3-232897	Discussion on Multi-path Support for SL relay	CATT
R3-232929	discussion on the support for multi-path	Nokia, Nokia Shanghai Bell
R3-233020	(TP to TS 38.401) Path change for multi-path for sidelink relay	China Telecommunication
R3-233078	(TP to TS 38.401) Further consideration on multi-path support	LG Electronics
R3-233180	(TP to TS 38.473) More discussion on path addition and release for multipath	Samsung
R3-233214	(TP to TS 38.401)Considerations on multi-path for SL relay	CMCC
R3-233362	SoD of CB: # SLRelay2_MultiPath	LG Electronics
R3-233480	(TP to TS 38.473) More discussion on path addition for multipath	Samsung

17.1: General

TDoc	Title	Source
R3-232540	(BLCR to 38.300) Stage 2 BL CR for NR NTN	Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R3-232541	XnAP BLCR on NTN Functionality	Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC
R3-232826	(BLCR to 38.300) Stage 2 BL CR for NR NTN	Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R3-233021	R18 WI NR-NTN-enh work plan at RAN1, 2 and 3	THALES
R3-233559	(BLCR to 38.300) Stage 2 BL CR for NR NTN	Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R3-233560	NGAP BLCR on NTN Functionality	Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Nokia, Nokia Shanghai Bell, Samsung, Qualcomm Incorporated

17.2: Support Mobility and Service Continuity Enhancements

TDoc	Title	Source
R3-232743	Discussion on Mobility and Service Continuity Enhancements	NEC
R3-232787	Discussion on NR NTN Service Continuity Enhancements	Qualcomm Incorporated
R3-232788	Cell ID over Xn for NTN	Qualcomm Incorporated, CATT, Nokia, Nokia Shanghai Bell, NEC
R3-232798	(TP for BL CR to TS 38.413/38.423) On Mobility and Service Continuity Enhancements for NTN	CATT
R3-232930	(TP for NR NTN BL CR TS38.300) Discussion on the time-based trigger condition in NR NTN	Nokia, Nokia Shanghai Bell
R3-232931	(TP for NR NTN BL CR TS38.413) Support time-based trigger condition in NR NTN NG-HO	Nokia, Nokia Shanghai Bell
R3-232947	NGAP Support for Time-Based HO in NTN	Ericsson, Thales, Intelsat, Lockheed Martin, Hughes Network Systems, CATT, ESA, Nokia, Nokia Shanghai Bell
R3-232948	Time-Based HO for NTN - NGAP Impacts	Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA
R3-232957	Further discussion on cell ID usage and TAC	Huawei
R3-232958	Further discussion on NG HO	Huawei
R3-232967	Time Margin for CHO in NR NTN	Ericsson, Thales
R3-232971	Time Margin for CHO in NR NTN - XnAP Impact	Ericsson LM
R3-233010	Further discussion on network ID usage and time based handover in NTN	China Telecommunication
R3-233088	Further discussion on mobility issue for NR NTN	ZTE
R3-233089	(TP for NTN BL CR 38.423) No exchange of TAC for non-UE associated Xn procedures	ZTE
R3-233181	Further discussion on service continuity enhancement for NTN	Samsung
R3-233304	Time Margin for CHO in NR NTN	Ericsson, Thales, ESA
R3-233305	Time Margin for CHO in NR NTN - XnAP Impact	Ericsson LM, ESA
R3-233309	Time-Based HO for NTN - NGAP Impacts	Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA
R3-233435	(TP for TS 38.300) Uu Cell ID for Xn Setup and Config Update Procedures	Qualcomm Incorporated, CATT, Nokia, Nokia Shanghai Bell, NEC, ZTE
R3-233437	Summary of Offline Discussion on NR NTN Service Continuity	Ericsson
R3-233454	(TP for NR NTN BL CR TS38.300) Early Data Forwarding in Xn/NG-HO with time-based trigger condition	Nokia, Nokia Shanghai Bell
R3-233455	(TP for NR NTN BL CR TS38.413) Early Data Forwarding in NG-HO with time-based trigger condition	Nokia, Nokia Shanghai Bell
R3-233475	LS on time-based trigger condition in NG HO for NR NTN	RAN3(Ericsson)
R3-233482	Time-Based HO for NTN - NGAP Impacts	Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Nokia, Nokia Shanghai Bell
R3-233494	NGAP Support for Time-Based HO in NTN	Ericsson, Thales, Intelsat, Lockheed Martin, Hughes Network Systems, CATT, ESA, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Qualcomm Incorporated
R3-233503	(TP for NR NTN BL CR to 38.423) Correction to time based CHO	CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei
R3-233526	Time-Based HO for NTN - NGAP Impacts	Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Nokia, Nokia Shanghai Bell, Qualcomm, Samsung
R3-233527	LS on time-based trigger condition in NG HO for NR NTN	RAN3(Ericsson)

17.3: Network verified UE location

TDoc	Title	Source
R3-232789	Discussion on Network Verified UE Location for NTN	Qualcomm Incorporated
R3-232799	Consideration on OAM requirements for UE location verification	CATT,Ericsson, Huawei
R3-232944	OAM Requirements for UE Location Verification	Ericsson, CATT, Huawei
R3-232945	[DRAFT] Reply LS on Latency impact for NTN verified UE location	Ericsson, CATT, Huawei
R3-232959	Further discussion on network verified UE location	Huawei, Ericsson, CATT
R3-232960	(TP to 38.300) OAM Requirements for UE Location Verification	Huawei, Ericsson, CATT
R3-233205	Discussion on NTN Network Verified UE Location	TCL Communication Ltd.
R3-233311	OAM Requirements for UE Location Verification	Ericsson, CATT, Huawei

18.1: General

TDoc	Title	Source
R3-232516	(BLCR to 36.423) X2AP CR on IoT NTN Functionality	Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung
R3-232517	(BLCR to 36.300) IoT NTN enhancements	ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson
R3-232518	(BLCR) Support for IoT NTN enhancements	Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE
R3-232745	(BLCR) X2AP CR on IoT NTN Functionality	Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung
R3-232796	(BLCR to 36.300) IoT NTN enhancements	ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson
R3-233533	(BLCR to 36.300) IoT NTN enhancements	ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson

18.2: Support discontinuous coverage

TDoc	Title	Source
R3-232675	Discussion on time based CHO in X2	CATT
R3-232932	(TP for BL CR 36.300 and 36.413) on support X2-CHO and S1-HO with time-based trigger condition	Nokia, Nokia Shanghai Bell
R3-232941	Time Margin for CHO in IoT NTN - X2AP Impact	Ericsson, Inmarsat, ESA
R3-232942	Time-Based HO and IoT NTN - Stage 2 Impacts	Ericsson, CATT, ESA, Huawei
R3-232943	Time-Based HO for IoT NTN - S1AP Impacts	Ericsson, Huawei, CATT, ESA
R3-232997	Altitude correction for the NTN TRP	Huawei
R3-233090	Further discussion on remaining issues for IoT NTN	ZTE
R3-233439	(TP for IoT NTN BL CR 36.300) Uu Cell ID for X2 Setup and eNB Configuration Update procedures	ZTE, Qualcomm Incorporated

19.1: General

TDoc	Title	Source
R3-232549	(BLCR to 38.300) NR support for UAV	Nokia, Nokia Shanghai Bell, Huawei, Intel Corporation, ZTE, Ericsson, Samsung, CATT, Qualcomm, Deutsche Telekom, NEC
R3-232550	(BLCR to 38.413) Introduction of Aerial authorization information	Ericsson, AT&T, NTT DOCOMO INC, Qualcomm Incorporated, Intel Corporation, Samsung, NEC, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT

20.1: General

TDoc	Title	Source
R3-232533	(BLCR to 38.401) Introduction on MT-SDT	Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, China Telecom, Lenovo, LG Electronics
R3-232534	(BLCR to 38.423) Introduciton on MT-SDT	Ericsson, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, China Telecom, Huawei, Lenovo
R3-232535	(BLCR to 38.473) Introduction on MT-SDT	Intel Corporation, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei
R3-232536	(BLCR to 37.483) introduction of MT-SDT	Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei, Lenovo, LG Electronics
R3-232561	(BLCR to 38 300) Introduction on MT-SDT	ZTE, CATT, Ericsson, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Google, LG Electronics
R3-232562	(BLCR to 38.420) Introduction on MT-SDT	Lenovo
R3-233074	(BLCR to 38.420) Introduction on MT-SDT	Lenovo, CATT, ZTE
R3-233328	(BLCR to 38.473) Introduction on MT-SDT	China Telecom, Intel Corporation, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei
R3-233329	(BLCR to 37.483) introduction of MT-SDT	Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei, Lenovo, LG Electronics
R3-233552	(BLCR to TS 37.480) Introduction of MT-SDT	LG Electronics Polska
R3-233553	(BLCR to 37.483) introduction of MT-SDT	Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei, Lenovo, LG Electronics
R3-233554	(BLCR to 38 300) Introduction on MT-SDT	ZTE, CATT, Ericsson, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Google, LG Electronics
R3-233555	(BLCR to 38.401) Introduction on MT-SDT	Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, China Telecom, Lenovo, LG Electronics
R3-233556	(BLCR to 38.420) Introduction on MT-SDT	Lenovo, CATT, ZTE
R3-233557	(BLCR to 38.423) Introduction on MT-SDT	Ericsson, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, China Telecom, Huawei, Lenovo
R3-233558	(BLCR to 38.473) Introduction on MT-SDT	intel

20.2: Support for Paging-Triggered SDT

TDoc	Title	Source
R3-232682	Signaling enhancements to enable MT-SDT for RRC_INACTIVE UEs.	Qualcomm Incorporated
R3-232686	(TP to 38.423, 38.473, 37.483) Introduction on MT-SDT	ZTE
R3-232687	(TP to 38.401,37.480) Introduction on MT-SDT	ZTE
R3-232711	(TP for TS 37.483 and TS 38.300) Completion of MT-SDT Open Points	Nokia, Nokia Shanghai Bell, Orange
R3-232712	(TP for TS 38.423 and TS 38.473) Completion of MT-SDT Open Points	Nokia, Nokia Shanghai Bell, Orange
R3-232800	(TP for BL CR to TS 38.423/38.473/37.483) Support of MT-SDT	CATT,CERPI
R3-232801	(TP for BLCR to TS 38.413) Support of Redcap and MT-SDT	CATT,CERPI
R3-232865	(TPs to TS 38.401, 38.473 BL CRs) Consideration on MT-SDT	Huawei
R3-232866	(TPs to TS 38.423, 37.463 BL CRs) Consideration on MT-SDT	Huawei
R3-233049	(TP to TS 38.300/401/420 BL CRs) Support for Paging-Triggered SDT	Lenovo
R3-233059	Discussion on MT-SDT Open issues for E1, F1 and Xn with TPs	Ericsson
R3-233060	TPs to TS 38.401 BL CR and E1AP BL CR	Ericsson
R3-233079	(TP to TS 38.423, 38.473 and 37.483) Support of MT-SDT	LG Electronics
R3-233080	(TP to TS 38.401) MT-SDT Support	LG Electronics
R3-233294	Discussion on Support of MT-SDT in Split Architecture	China Telecom
R3-233295	Discussion on Remaining Issues for RAN Paging	China Telecom
R3-233330	CB:#15_SDT	ZTE
R3-233372	(TP for TS 37.483) Update of MT-SDT information over E1	Nokia
R3-233404	(TP to MT-SDT TS 38.401) consideration on MT-SDT	Huawei, Qualcomm Incorporated, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, Samsung, ZTE, LG Electronics, CATT
R3-233405	(TP to BL CR TS 38.423 on MT-SDT)	Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, Samsung, LG Electronics, CATT
R3-233406	Discussion on MT-SDT Open issues for E1, F1 and Xn with TPs	Ericsson
R3-233413	(TP for MT-SDT BL CR to TS 38.300) Handling of non-SDT during MT-SDT	CATT, China Telecom, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Google, LG Electronics, Huawei, Lenovo
R3-233436	(TP for MT-SDT BLCR to TS 37.480) Introduction of MT-SDT	LG Electronics, Nokia, Nokia Shanghai Bell, ZTE, CATT
R3-233438	(TP to 38.473) Introduction on MT-SDT	ZTE, LG Electronics, CATT, China Telecom
R3-233442	(TP to TS 38.420 BL CRs) Support for Paging-Triggered SDT	Lenovo
R3-233485	(TP to MT-SDT TS 38.401) consideration on MT-SDT	Huawei, Qualcomm Incorporated, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, Samsung, ZTE, LG Electronics, CATT
R3-233486	(TP to 38.473) Introduction on MT-SDT	ZTE, LG Electronics, CATT, China Telecom

21.1: General

TDoc	Title	Source
R3-232563	(BLCR to 38.300) introduction of NR Redcap Enhancement	Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE
R3-232564	(BLCR to 38.410) Introduction of NR Redcap Enhancement	CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-232565	(BLCR to 38.413) Introduction of NR Redcap Enhancement	Huawei, Nokia, Nokia Shanghai Bell, ZTE
R3-232566	(BLCR to 38.423) Introduction of RedCap enhancement	Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE
R3-232567	(BLCR to 38.473) Introduction on NR Redcap enhancement	ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei
R3-232858	(BLCR to 38.410) Introduction of NR Redcap Enhancement	CATT, Nokia, Nokia Shanghai Bell, ZTE
R3-233061	WI work plan for Rel-18 RedCap	Ericsson (Rapporteur)
R3-233566	(BLCR to 38.413) Introduction of NR Redcap Enhancement	Huawei, Nokia, Nokia Shanghai Bell, ZTE

21.2: Support Enhanced eDRX in RRC_INACTIVE

TDoc	Title	Source
R3-232505	Reply LS on Paging Policy Information for Network Triggered Connection Resume	SA2(Ericsson)
R3-232506	Reply LS on INACTIVE eDRX above 10.24sec and SDT	SA2(Intel)
R3-232688	(TP to 38.413, 38.423, 38.473, 38.300) Introduction on NR Redcap enhancement	ZTE
R3-232689	(TP to 38.413, 38.410) Introduction on NR Redcap enhancement with SDT	ZTE
R3-232713	(TP for TS 38.413) Support of Extended eDRX for RRC Inactive	Nokia, Nokia Shanghai Bell
R3-232714	(TP for TS 38.413 and TS 38.410) Support of NGAP DL DATA Notification	Nokia, Nokia Shanghai Bell
R3-232790	Discussion on RRC Inactive with long eDRX for RedCap	Qualcomm Incorporated
R3-232898	Discussion on long eDRX for RRC_INACTIVE	CATT
R3-232899	(TP for 38.413) Discussion on long eDRX for RRC_INACTIVE	CATT
R3-232955	Further discussion on long eDRX support for RRC_INACTIVE	Huawei
R3-232956	Discussion on R18 RedCap capability	Huawei
R3-232985	Discussion on INACTIVE eDRX above 10.24sec and SDT	Xiaomi
R3-233062	Open issues on MT communication handling procedure based on SA2 updates	Ericsson
R3-233063	(TP to NGAP BLCR on Rel-18 RedCap): Support of connection resume indication and introduction of paging policy parameters for RAN Paging	Ericsson
R3-233126	Draft Reply LS on INACTIVE eDRX above 10.24sec and SDT	Qualcomm Incorporated
R3-233331	CB:#16_R18Redcap	Ericsson
R3-233344	(TP for TS 38.413) Update of CN based Communication Handling	Nokia
R3-233347	Reply LS on INACTIVE eDRX above 10.24sec and SDT	RAN3(Ericsson)

22.1: General

TDoc	Title	Source
R3-232537	(BLCR to 38.300) BL CR for Network Controlled Repeater management	ZTE, China Telecom, Samsung,CATT, Ericsson, Nokia, Nokia Shanghai Bell
R3-232538	Support of Network-Controlled Repeater	Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson, Samsung, NEC, China Telecom, ZTE
R3-232539	(BLCR to 38.473) Support of Network-Controlled Repeater	Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Samsung, China Telecom, ZTE, NEC

23.1: General

TDoc	Title	Source
R3-232802	Work Plan for Rel-18 WI on Expanded and Improved NR Positioning	CATT, Intel Corporation, Ericsson

23.2: Support Enhancements on NR Positioning

TDoc	Title	Source
R3-232507	LS on Authorization and Provisioning for Ranging/SL positioning service	SA2(Xiaomi)
R3-232571	Response LS on PRU Procedures	RAN2(Qualcomm)
R3-232576	LS to RAN1 on RAT-dependent positioning integrity	RAN2(OPPO)
R3-232672	Support of NR Positioning Enhancements	ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson
R3-232803	Discussion on Expanded and Improved NR Positioning	CATT
R3-232804	(TP for BL CR to TS 38.305/38.423/38.455) Support of LPHAP	CATT
R3-232983	Discussion on positioning enhancement	Xiaomi
R3-232984	Draft Reply LS on Authorization for SL Pos to SA2	Xiaomi
R3-232986	Support of NR Positioning Enhancements	Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ercisson
R3-232994	(TP BL CR 38.455, 38.743) Discussion on LPHAP	Huawei
R3-232995	[Draft] Reply LS on SRS Configuration Request	Huawei
R3-232996	(TP BL CR 38.455, 38.743) Discussion on Sidelink & Others topics	Huawei
R3-233064	Discussion on RAN3 impacts to support Rel-18 positioning enhancements	Ericsson
R3-233065	Support of NR Positioning Enhancements	Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell
R3-233066	(TP to NRPPA BL CR): Support of Sidelink Positioning, Integrity and LPHAP	Ericsson
R3-233082	Enhancements for LPHAP	Qualcomm Incorporated
R3-233083	Integrity of NR Positioning Technologies	Qualcomm Incorporated
R3-233130	LMF-based Integrity	Nokia, Nokia Shanghai Bell
R3-233131	LPHAP: SRS positioning validity area	Nokia, Nokia Shanghai Bell
R3-233140	Support of NR Positioning Enhancements	Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson
R3-233184	Discussion on enhancements for positioning	Samsung
R3-233228	Discussion on NR SL Positioning	CMCC
R3-233230	(TP to 38.413, 38.423, 38.455, 38.473) Discussion on Sidelink positioning and Integrity of RAT-dependent positioning	ZTE
R3-233231	Discussion on LPHAP impacts	ZTE
R3-233297	Discussion on solution of LPHAP	vivo
R3-233374	Summary of Offline Discussion � CB_Positioning	Huawei
R3-233424	Reply LS on Authorization and Provisioning for Ranging/SL positioning service	RAN3(Xiaomi)
R3-233458	(TP for Positioning BL CR to TS 38.413) Addition of RSPP Transport QoS parameters	ZTE, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Inc., Xiaomi
R3-233459	(TP for Positioning BL CR to TS 38.423) Addition of RSPP Transport QoS parameters	CATT, Ericsson, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Inc., Xiaomi
R3-233460	[TP for BL CR 38.473] Addition of RSPP Transport QoS parameters	Ericsson, CATT, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Inc., Xiaomi
R3-233474	Reply LS on SRS Configuration Request	RAN3(Huawei)
R3-233561	Support of NR Positioning Enhancements	ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson
R3-233562	Support of NR Positioning Enhancements	Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson
R3-233563	Support of NR Positioning Enhancements	Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell

24.1: General

TDoc	Title	Source
R3-232519	(BLCR to 38.423) Network energy saving techniques	Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Intel
R3-232520	(BLCR to 38.473) Introduction of Network Energy Saving	Ericsson, Huawei, Samsung, ZTE, CATT, Intel
R3-232889	WI Work plan for R18 network energy savings	Huawei
R3-233273	(BLCR to 38.473) Introduction of Network Energy Saving	Ericsson, Huawei, Samsung, ZTE, CATT, Intel

24.2: Support Network Energy Savings

TDoc	Title	Source
R3-232577	LS on Cell DTX/DRX activation/deactivation	RAN2(Huawei)
R3-232589	(TP to TS 38.423) Support of network energy saving techniques	Nokia, Nokia Shanghai Bell
R3-232590	Introduction of Network Energy Saving	Nokia, Nokia Shanghai Bell
R3-232594	(TP to TS 38.473) Beam deactivation decision and signalling for energy saving	Nokia, Nokia Shanghai Bell
R3-232813	Discussion on network energy saving	Samsung
R3-232814	(CR to 38.413) Introduction of Network Energy Saving for Paging IDLE UE	Samsung
R3-232853	Paging enhancements, Inter-node beam activation and Cell DTX/DRX	Qualcomm Incorporated
R3-232890	(TP to Netw_Energy_NR BLCR for TS 38.423) Network energy saving techniques	Huawei
R3-232902	(TP to Netw_Energy_NR BLCR for TS 38.473, 38.470 and 38.300) Network energy saving techniques	Huawei
R3-232968	Introduction of Network Energy Saving	Ericsson
R3-232969	Text Proposal on F1AP: Introduction of Network Energy Saving	Ericsson
R3-233045	Discussion on NES related issues	Lenovo
R3-233246	Discussion on Paging Enhancement (TP for 38.423)	CATT
R3-233284	Discussion on network energy saving	ZTE
R3-233285	TPs to BL CRs for network energy saving	ZTE
R3-233375	Summary of offline discussions on CB: # 36_R18ES	Huawei
R3-233465	(TP to Netw_Energy_NR BLCR for TS 38.473) Network energy saving techniques	Huawei

26.1: eNPN WI

TDoc	Title	Source
R3-232512	(BLCR to 29.413) Support of the enhanced NPN phase 2	Huawei, China Telecom, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, ZTE, Samsung, Ericsson
R3-232513	(BLCR to 38.300) On introduction of R18 eNPN	China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson
R3-232514	(BLCR to 38.413) Support of the enhanced NPN phase 2	ZTE
R3-232515	Introduction of equivalent SNPNs	Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC
R3-232715	(TP for TS 38.413) Indicating selected SNPN over NG for Further NPN Enhancements	Nokia, Nokia Shanghai Bell
R3-232716	(TP for TS 38.423) Indicating selected SNPN over Xn for further NPN Enhancements	Nokia, Nokia Shanghai Bell
R3-232734	Further discussion on eNPN impact on RAN specifications	NEC
R3-232735	(TP to TS29.413 BL CR) & (TP to TS38.413 BL CR) eNPN	NEC
R3-232784	(BLCR to 38.413) Support of the enhanced NPN phase 2	ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung
R3-232854	Equivalent SNPNs and non-3GPP access for SNPN	Qualcomm Incorporated
R3-232882	(TP to eNPN_Ph2 BLCR for TS 29.413) Support of the enhanced NPN phase 2	Huawei
R3-232883	(TP to eNPN_Ph2 BLCR for TS 38.413, TS 38.423 and TS 38.300) Support of the enhanced NPN phase 2	Huawei
R3-232887	Remaining topics for Rel-18 eNPN work	Ericsson
R3-232888	[TP for BL CR 38.423] Further input for eNPN_Ph2	Ericsson
R3-232900	Discussion on RAN impact for NPN enhancement in Rel-18	CATT
R3-232901	[TP to 38.300 and 38.413] RAN impact for NPN enhancement in Rel-18	CATT
R3-232919	(TP for TS 38.413 BL CR) Discussion on Enhanced support of NPN	BEIJING SAMSUNG TELECOM R&D
R3-233015	Discussion on remaining issues to support eNPN	China Telecommunication
R3-233016	(TPs to BL CRs of 38.423/38.413/38.300) On support of eNPN	China Telecommunication
R3-233019	Work Plan for Further Enhancement for Private Network Support for NG-RAN WI	China Telecommunication
R3-233253	Left issues on RAN support for eNPN phase 2	ZTE
R3-233254	TPs to BL CRs for eNPN phase 2	ZTE
R3-233351	Summary of offline discussions on CB: # 28_R18	Ericsson
R3-233363	(TP to eNPN_Ph2 BLCR for TS 38.413) Support of the enhanced NPN phase 2	Huawei, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, NEC
R3-233364	[TP for BL CR 29.413] Remove Editor�s Note	Ericsson, Huawei, ZTE, NEC
R3-233400	[TP to eNPN_Ph2 BLCR for TS38.300] RAN impact for NPN enhancement in Rel-18	CATT, Huawei, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, NEC
R3-233529	(BLCR to 29.413) Support of the enhanced NPN phase 2	Huawei, China Telecom, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, ZTE, Samsung, Ericsson
R3-233530	(BLCR to 38.300) On introduction of R18 eNPN	China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson
R3-233531	(BLCR to 38.413) Support of the enhanced NPN phase 2	ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung

26.2: Timing Resiliency and URLLC WI

TDoc	Title	Source
R3-232504	Response to Reply LS on Proposed method for Time Synchronization status reporting to UE(s)	CT1(Nokia)
R3-232551	(BLCR to 38.413) Introduction of 5G Timing Resiliency and URLLC enhancements	Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT
R3-232552	(BLCR to 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements	Ericsson
R3-232553	(BLCR to 38.473) Introduction of 5G Timing Resiliency and URLLC enhancements	ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung
R3-232722	(TP for TS 38.413 BL CR) Further details on timing resiliency	Nokia, Nokia Shanghai Bell
R3-232723	(TP for TS 38.413 BL CR) Further details on RAN feedback for low latency communication	Nokia, Nokia Shanghai Bell
R3-232780	Discussion on Network timing synchronization status and reporting	CATT
R3-232781	TP for BLCR to TS38.413 Adapting downstream and upstream scheduling	CATT
R3-232791	Discussion on Time Synchronization Status and Reporting	Qualcomm Incorporated
R3-232938	Text Proposals on Support NR Timing Resiliency and URLLC enhancements	Ericsson
R3-232970	Discussion on NR Timing Resiliency and URLLC enhancements	Ericsson
R3-233142	Discussion on open issues for network timing synchronization status and reporting	Samsung
R3-233143	(TP for TRS_URLLC-NR for TS 38.473) Supporting network timing synchronization status and reporting over F1	Samsung
R3-233175	(TP to TRS_URLLC BLCR for TS 38.413, TS 38.423 and TS 38.473) Support of 5G Timing Resiliency enhancements	Huawei, China Unicom
R3-233176	(TP to TRS_URLLC BLCR for TS 38.413, TS 38.423 and TS 38.473) Support of RAN feedback enhancements	Huawei, China Unicom
R3-233286	Discussion and TPs for timing synchronization status and reporting	ZTE
R3-233287	(TP to BL CR of 38.413) RAN feedback for downlink scheduling	ZTE
R3-233288	(BLCR to 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements	Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, CATT
R3-233352	CB:#29_R18URLLC	Nokia
R3-233414	(TP to TRS_URLLC BLCR for TS 38.473) Support of 5G Timing Resiliency enhancements and URLLC	ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT, Samsung, Qualcomm Incorporated
R3-233468	(TP to TRS_URLLC BLCR for TS 38.423): Introduction of 5G Timing Resiliency and URLLC enhancements	Ericsson, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung
R3-233477	(TP to TRS_URLLC BLCR for TS 38.413) Support of 5G Timing Resiliency enhancements and URLLC	Huawei, China Unicom, Ericsson, CATT, Samsung, Qualcomm Incorporated, ZTE, Nokia, Nokia Shanghai Bell
R3-233489	(TP to TRS_URLLC BLCR for TS 38.423): Introduction of 5G Timing Resiliency and URLLC enhancements	Ericsson, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung
R3-233525	(TP to TRS_URLLC BLCR for TS 38.473) Support of 5G Timing Resiliency enhancements and URLLC	ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT, Samsung, Qualcomm Incorporated
R3-233574	(BLCR to 38.413) Introduction of 5G Timing Resiliency and URLLC enhancements	Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT
R3-233575	(BLCR to 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements	Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, CATT
R3-233576	(BLCR to 38.473) Introduction of 5G Timing Resiliency and URLLC enhancements	ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung

26.3: RAN Slicing WI

TDoc	Title	Source
R3-232509	Reply LS on Support of network slices which have area of service not matching deployed tracking areas	SA2(Ericsson)
R3-232510	Reply LS on partially allowed/rejected S-NSSAI	SA2(Nokia)
R3-232717	(TP for TS 38.413 and TS 38.423) Support of Network Slice Service Continuity	Nokia, Nokia Shanghai Bell, Orange
R3-232718	(TP for TS 38.413) Support of partially allowed S-NSSAI in RRC connected mode	Nokia, Nokia Shanghai Bell, Orange
R3-232719	Response LS on Partially Allowed/Rejected S-NSSAI	Nokia, Nokia Shanghai Bell, Orange
R3-232782	Discussion on supporting Partially Allowed NSSAI	CATT
R3-232783	Discussion on supporting Network Slice Service continuity	CATT
R3-232855	Supporting Partially Allowed NSSAI and Alternative NSSAI	Qualcomm Incorporated
R3-232856	(TP for TS 38.300) Partially Allowed NSSAI in a Registration Area	Huawei
R3-232857	Support of Network Slice Replacement	Huawei
R3-233017	Discussion on RAN Slicing enhancement	China Telecommunication
R3-233018	(TP to TS 38.300/38.423/38.413) Support of Partially Allowed S-NSSAI	China Telecommunication
R3-233102	Discussion Partially Allowed NSSAI	Ericsson
R3-233103	Discussion on Service Continuity	Ericsson
R3-233185	Discussion on the enhancement of RAN slicing	Samsung
R3-233192	RAN Slicing workplan	ZTE
R3-233193	(TPs for BLCRs for 38.413 38.423 38.473 38.300)RAN impact on supporting Network Slice Service continuity scenario	ZTE
R3-233194	(TPs for BLCRs for TS 38.413 TS38.423)RAN impact on support Partially Allowed NSSAI	ZTE
R3-233229	Initial consideration on RAN Slicing	CMCC
R3-233354	CB:#30_R18Slice	ZTE
R3-233370	(TP for TS 38.413) Support of Partially Allowed S-NSSAI in RRC connected mode	Nokia, Nokia Shanghai Bell, Orange
R3-233371	Response LS on Partially Allowed/Rejected S-NSSAI	Nokia, Nokia Shanghai Bell, Orange
R3-233407	Resposne to Reply LS on Support of network slices which have area of service not matching deployed tracking areas	RAN3(Ericsson)
R3-233429	(TP for TS 38.413) Support of Partially Allowed S-NSSAI in RRC connected mode	Nokia, Nokia Shanghai Bell, Orange
R3-233432	Resposne to Reply LS on Support of network slices which have area of service not matching deployed tracking areas	RAN3(Ericsson)
R3-233433	Response LS on Partially Allowed/Rejected S-NSSAI	RAN3(Nokia)
R3-233532	Introduction of Enhancement of RAN Slicing for NR	Nokia France

31.1: Corrections

TDoc	Title	Source
R3-232720	Resolution of MRB PDCP Wrap Around issue	Nokia, Nokia Shanghai Bell
R3-232815	Discussion on HARQ Related Assistance Information in NR User Plane	Samsung, China Telecom, CMCC
R3-232816	Correction for HARQ Related Assisstance Information in NR User Plane	Samsung, China Telecom, CMCC
R3-232872	Further Discussion on the Criticality Diagnostics in Response messages [Add_Crit_Diag]	Huawei, BT, Deutsche Telekom, Orange, NEC
R3-232873	Correction on Missing Criticality Diagnostics [Add_Crit_Diag]	Huawei, BT, Deutsche Telekom, Orange, NEC
R3-232874	Correction on Missing Criticality Diagnostics [Add_Crit_Diag]	Huawei, BT, Deutsche Telekom, Orange, NEC
R3-232875	Correction on Missing Criticality Diagnostics [Add_Crit_Diag]	Huawei, BT, Deutsche Telekom, Orange, NEC
R3-232876	Correction on Missing Criticality Diagnostics [Add_Crit_Diag]	Huawei, BT, Deutsche Telekom, Orange, NEC
R3-232881	Discussion on leftover aspects for NR MBS [MBS_Leftovers]	Huawei, CBN, China Unicom, Lenovo
R3-233144	Adding the NCR Authorized information in the Retrieve UE Context Response	Samsung
R3-233160	Discussion on MRB PDCP count �wrap around� problem	CATT,CBN
R3-233161	Correction on MRB PDCP count �wrap around� problem	CATT, CBN
R3-233303	Response to R3-232720, R3-233160, and R3-232884 on PDCP COUNT wrap around of multicast MRB	Huawei
R3-233316	Summary of Offline Discussion on CB # 5_NCRCellReselection	Samsung
R3-233317	Summary of Offline Discussion � CB: # 6_ Criticality Diagnostics	Huawei
R3-233392	Correction concerning procedural text for "Unsuccessful Operation" specified in �Successful Operation� sections	Ericsson
R3-233393	Correction concerning procedural text for "Unsuccessful Operation" specified in �Successful Operation� sections	Ericsson
R3-233394	Correction concerning procedural text for "Unsuccessful Operation" specified in �Successful Operation� sections	Ericsson

31.2: Enhancements

TDoc	Title	Source
R3-232721	Switching from SDT to RRC Connected mode	Nokia, Nokia Shanghai Bell
R3-232939	LMF Outage Detection and Reporting	Ericsson LM
R3-232940	LMF Outage Reporting	Ericsson
R3-233310	LMF Outage Reporting [LMF_outage]	Ericsson
R3-233318	CB:#7_SDTRRCstateSwitch	Nokia