RAN3#114bis-e

3: Approval of the Agenda

TDoc	Title	Source
R3-220001	RAN3#114bis-e Meeting Agenda	RAN3 Chair

4: Approval of the minutes from previous meetings

TDoc	Title	Source
R3-220002	RAN3#114-e Meeting report	ETSI-MCC

5: Documents for immediate consideration

TDoc	Title	Source
R3-220665	Guidelines for RAN3 Electronic Meetings	RAN3 Chair, RAN3 Vice-Chairs
R3-221015	Response to R3-220665	Huawei
R3-221096	Introduction of Tdoc Quotas	RAN3 Chairman, RAN3 Vice-Chairs
R3-221097	Guidelines for RAN3 Electronic Meetings	RAN3 Chair, RAN3 Vice-Chairs

7: General, protocol principles and issues

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

8.1: New Incoming LSs

TDoc	Title	Source
R3-220086	Reply LS on Insufficient UE Capabilities Cause Value	CT4
R3-220094	LS on updated Rel-17 LTE and NR higher-layers parameter list	RAN1
R3-220105	Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance	RAN2
R3-220106	Reply LS on downlink unmapped QoS flows	RAN2
R3-220107	Reply LS on UP security policy update	RAN2
R3-220110	Reply LS on inter-MN RRC resume without SN change	RAN2
R3-220116	Reply LS on Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance	SA2
R3-220117	Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance	SA2
R3-220124	Reply LS on support of Pre-shared key derivation for IAB-donor-CU-UP	SA3
R3-220129	LS Reply on security protection of RRCResumeRequest message	SA3
R3-220130	Reply LS on Inclusive language for ANR	SA5
R3-220135	LS on Energy Efficiency as guiding principle for new solutions	SA
R3-220263	Inter MN RRC Resume without SN Change	Qualcomm Incorporated, Huawei, Ericsson, China Telecom, T-Mobile USA
R3-220264	Inter MN RRC Resume without SN Change (CR to 38.423)	Qualcomm Incorporated, Huawei, Ericsson, China Telecom, T-Mobile USA
R3-220385	Discussion on LS Reply on security protection of RRCResumeRequest message	Huawei
R3-220386	[Draft] Reply LS on security protection of RRCResumeRequest message	Huawei
R3-220447	Clarifications on security protection of RRCResumeRequest message	Ericsson
R3-220448	[DRAFT] LS Reply on security protection of RRCResumeRequest message	Ericsson
R3-220470	Discussion on Unmapped DL QoS Flows	Nokia, Nokia Shanghai Bell
R3-220542	Discussion on unmapped QoS flow handling	CATT
R3-220543	Correction on unmapped QoS flow handling in RAN	CATT
R3-220621	Inter-MN RRC Resume without SN change [InterMNResume]	Ericsson, Qualcomm Incorporated, Huawei
R3-220622	[DRAFT] Reply LS on inter-MN RRC resume without SN change	Ericsson
R3-220637	UP security policy update over E1AP	Ericsson
R3-220638	UP security policy update over E1AP	Ericsson
R3-220639	UP security policy update over E1AP	Ericsson
R3-220640	Unmapped QoS flows at Bearer Context Setup	Ericsson
R3-220666	Downlink unmapped QoS flows for E1	Huawei
R3-220667	Downlink unmapped QoS flows for E1 (alternative 1)	Huawei
R3-220668	Downlink unmapped QoS flows for E1 (alternative 1)	Huawei
R3-220669	Downlink unmapped QoS flows for E1 (alternative 2)	Huawei
R3-220670	Downlink unmapped QoS flows for E1 (alternative 2)	Huawei
R3-220745	Consideration on security protection on RRCResumeRequest message	ZTE
R3-220746	Security protection on RRCResumeRequest message-Xn	ZTE
R3-220747	[DRAFT] Reply on security protection of RRCResumeRequest message	ZTE
R3-220748	UP security policy updated in the modification procedure over E1 interface	ZTE
R3-220749	UP security policy updated in the modification procedure over E1 interface_R15	ZTE
R3-220750	UP security policy updated in the modification procedure over E1 interface_R16	ZTE
R3-220797	Further discussion on Security handling for CP-UP separation of IAB-donor	Huawei
R3-220798	CR to 38.463 on support of Pre-shared key derivation for IAB-donor-CU-UP	Huawei, Lenovo, Motorola Mobility, Samsung
R3-220799	CR to 38.460 on support of Pre-shared key derivation for IAB-donor-CU-UP	Huawei, Lenovo, Motorola Mobility, Samsung
R3-220808	E1 impacts of UP security policy updated	China Telecom, Huawei, CATT
R3-220809	Security indication in the modification procedure over E1 interface	China Telecom,Huawei,CATT
R3-220810	Security indication in the modification procedure over E1 interface	China Telecom, Huawei, CATT
R3-220837	Discussion on Inter-MN resume without SN change	Intel Corporation
R3-220838	CR for 38.423 on supporting Rel-17 inter-MN resume without SN change	Intel Corporation
R3-220905	Discussion on UP security policy update	Huawei
R3-220906	CR to 38.423 on UP security policy update	Huawei, China Telecom
R3-220907	CR to 38.423 on UP security policy update	Huawei, China Telecom
R3-220988	CB: # 1_UnmappedDLQoS - Summary of email discussion	Nokia - moderator
R3-220989	CB: # 2_UPSecUpdate - Summary of email discussion	China Telecom - moderator
R3-220990	CB: # 3_IABKeyDerivation - Summary of email discussion	Huawei - moderator
R3-220991	CB: # 4_SecProtec_RRCResume - Summary of email discussion	ZTE - moderator
R3-221004	CB: # 12_InterMN_RRCResume - Summary of email discussion	Qualcomm - moderator
R3-221044	Response to R3-220637, R3-220748, R3-220808, R3-220905	Nokia, Nokia Shanghai Bell
R3-221045	Response to R3-220638, R3-220749, R3-220809, R3-220906	Nokia, Nokia Shanghai Bell
R3-221106	Inter MN resume without SN change [InterMNResume]	Qualcomm Incorporated, Huawei, Ericsson, China Telecom, T-Mobile USA, ZTE
R3-221107	CR for 38.423 on supporting Rel-17 inter-MN resume without SN change [InterMNResume]	Intel Corporation
R3-221183	Reply on security protection of RRCResumeRequest message	ZTE
R3-221223	CR to 38.463 on support of Pre-shared key derivation for IAB-donor-CU-UP	Huawei, Lenovo, Motorola Mobility, Samsung, Nokia, Nokia Shanghai Bell
R3-221224	CR to 38.460 on support of Pre-shared key derivation for IAB-donor-CU-UP	Huawei, Lenovo, Motorola Mobility, Samsung, Nokia, Nokia Shanghai Bell
R3-221253	Downlink unmapped QoS flows for E1	Huawei
R3-221276	CR to 38.423 on UP security policy update	Huawei, China Telecom, Nokia, Nokia Shanghai Bell
R3-221279	Security indication in the modification procedure over E1 interface	China Telecom, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT
R3-221285	Security indication in the modification procedure over E1 interface	Nokia, Nokia Shanghai Bell, China Telecom, Huawei, ZTE, CATT
R3-221288	Inter MN resume without SN change [InterMNResume]	Qualcomm Incorporated, Huawei, Ericsson, China Telecom, T-Mobile USA, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, Samsung
R3-221289	Inter-MN RRC Resume without SN change [InterMNResume]	Ericsson, Qualcomm Incorporated, Huawei, Intel Corporation, China Telecom, T-Mobile USA, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, Samsung
R3-221290	Reply LS on inter-MN RRC resume without SN change	Ericsson
R3-221322	Addition of the Retrieve UE Context Confirm procedure [InterMNResume]	Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, Ericsson, China Telecom, T-Mobile USA, ZTE, Intel Corporation, Samsung
R3-221336	CR to 38.423 on UP security policy update	Huawei, China Telecom, Nokia, Nokia Shanghai Bell
R3-221426	Inter-MN RRC Resume without SN change [InterMNResume]	Ericsson, Qualcomm Incorporated, Huawei, Intel Corporation, China Telecom, T-Mobile USA, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, Samsung
R3-221442	Inter-MN RRC Resume without SN change [InterMNResume]	Ericsson, Qualcomm Incorporated, Huawei, Intel Corporation, China Telecom, T-Mobile USA, ZTE, Nokia, Nokia Shanghai Bell, Samsung, RadiSys, Reliance JIO, Google Inc.

8.3.1: E-RABs Cannot Be Handed Over

TDoc	Title	Source
R3-220186	Handling E-RABs which cannot be handed over to 3g	Nokia, Nokia Shanghai Bell
R3-220187	Correction of Inter-RAT handover to 3g involving NR	Nokia, Nokia Shanghai Bell
R3-220522	Indicating E-RABs that cannot be handed over to 5G	Ericsson, BT, Vodafone, ZTE, China Telecom
R3-220523	Indicating E-RABs that cannot be handed over to 5G	Ericsson, BT, Vodafone, ZTE, China Telecom
R3-220526	Indicating E-RABs that cannot be handed over to 5G	Ericsson, BT, Vodafone, ZTE, China Telecom
R3-220527	E-RABs Cannot Be Handed Over for X2AP	ZTE,Ericsson,China Telecom
R3-220528	E-RABs Cannot Be Handed Over for X2AP	ZTE,Ericsson,China Telecom
R3-220671	On E-RABs that cannot be handed over for inter-system interworking	Huawei
R3-220672	On E-RABs that cannot be handed over for inter-system interworking	Huawei
R3-220992	CB: # 5_ERABsCannotHO - Summary of email discussion	Ericsson - moderator

8.3.2: Handling of UE Security Capabilities

TDoc	Title	Source
R3-220277	Handling of UE Security Capabilities	Qualcomm Incorporated, Huawei, Ericsson
R3-220278	Support for mapping complete security capabilities from NAS [UE_Sec_Caps]	Qualcomm Incorporated, Huawei, Ericsson
R3-220279	[DRAFT] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC	Qualcomm Incorporated
R3-220607	(TP for TS 36.423) X2AP Handling of UE Security Capabilities	Nokia, Nokia Shanghai Bell
R3-220608	(TP for TS 38.423) XnAP Handling of UE Security Capabilities	Nokia, Nokia Shanghai Bell
R3-220751	Remaining issues on lossless handling of UE security capabilities	ZTE
R3-220752	CR for TS 36.413 on UE Security Capabilities	ZTE
R3-220753	[Draft] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC	ZTE
R3-220993	CB: # 6_UESecurity_Capability - Summary of email discussion	Qualcomm - moderator
R3-221278	Support for mapping complete security capabilities from NAS [UE_Sec_Caps]	Qualcomm Incorporated, Huawei, Ericsson, Nokia and Nokia Shanghai Bell
R3-221325	Reply LS on User Plane Integrity Protection for eUTRA connected to EPC	Qualcomm Incorporated

9.2.1: Others

TDoc	Title	Source
R3-220623	Correction on UE X2AP ID in the ERROR INDICATION message	Ericsson
R3-220624	Correction on UE X2AP ID in the ERROR INDICATION message	Ericsson
R3-221098	Correction on UE X2AP ID in the ERROR INDICATION message	Ericsson
R3-221099	CB: # 89_UEX2APID - Summary of email discussion	Ericsson - moderator
R3-221364	Correction on UE X2AP ID in the ERROR INDICATION message	Ericsson
R3-221441	Correction on UE X2AP ID in the ERROR INDICATION message	Ericsson

9.3.1.1: E1 Aspects

TDoc	Title	Source
R3-220188	Support of 4g-5g direct data forwarding over E1 with non-shared gNB	Nokia, Nokia Shanghai Bell, CATT, China Telecom
R3-220189	Support of 4g-5g direct data forwarding over E1 with non-shared gNB	Nokia, Nokia Shanghai Bell, CATT, China Telecom
R3-220636	E1 aspects of inter-system direct data forwarding	Ericsson
R3-220673	Direct data forwarding for 4G to 5G handover	Huawei, Samsung, China Telecom
R3-220999	CB: # 7_DirectDataFwd_E1aspects - Summary of email discussion	Nokia - moderator
R3-221196	Direct data forwarding for 4G to 5G handover	Huawei, Samsung, China Telecom, Nokia, Nokia Shanghai Bell

9.3.1.2: With Mobility Between DC and SA

TDoc	Title	Source
R3-220260	SN direct data forwarding in inter-system handover	Qualcomm Incorporated
R3-220539	Discussion on direct data forwarding for mobility between DC and SA	CATT,Qualcomm,CMCC
R3-220540	Support of direct data forwarding for mobility from MR-DC to SA	CATT, Qualcomm, CMCC
R3-220548	Direct data forwarding in EN-DC to NR SA handover (CR to 36.413)	Qualcomm Incorporated, CATT, CMCC
R3-220601	Direct data forwarding in EN-DC to NR SA handover (CR to 36.423)	Qualcomm Incorporated, CATT, CMCC
R3-220674	Direct data forwarding for mobility between DC and SA	Huawei, Samsung, China Telecom, ZTE
R3-220774	Direct data forwarding for mobility between DC and SA	Samsung, Huawei, ZTE
R3-220775	Direct data forwarding for mobility between DC and SA	Samsung, Huawei, ZTE
R3-220776	Direct Data forwarding address allocation for handover to EN-DC	Samsung, Verizon Wireless, ZTE
R3-220777	Data forwarding address allocation for handover to EN-DC	Samsung, Verizon Wireless, ZTE
R3-220778	Data forwarding address allocation for handover to EN-DC	Samsung, Verizon Wireless, ZTE
R3-220879	CR on data forwarding from MR-DC to SA_NGAP	CMCC. CATT, Qualcomm
R3-220880	CR on data forwarding between EN-DC MR-DC and SA handover	CMCC. CATT, Qualcomm
R3-220957	Discussion on direct data forwarding for mobility between DC and SA	Samsung, Huawei, ZTE
R3-221000	CB: # 8_DirectDataFwd_DC - Summary of email discussion	Samsung - moderator
R3-221090	Discussion on direct data forwarding for mobility between DC and SA	Samsung, Verizon, ZTE
R3-221389	Direct data forwarding for mobility between DC and SA	Samsung, Huawei, ZTE
R3-221390	Direct data forwarding for mobility between DC and SA	Samsung, Huawei, ZTE
R3-221397	Direct data forwarding in EN-DC to NR SA handover (CR to 36.413)	Qualcomm Incorporated, CATT, CMCC
R3-221398	Direct data forwarding in EN-DC to NR SA handover (CR to 36.423)	Qualcomm Incorporated, CATT, CMCC
R3-221401	Direct data forwarding for mobility between DC and SA	Huawei, Samsung, China Telecom, ZTE
R3-221410	Support of direct data forwarding for mobility from MR-DC to SA	CATT, Qualcomm, CMCC
R3-221451	CB: # 8_DirectDataFwd_DC - Summary of email discussion	Samsung - moderator
R3-221454	CR on data forwarding between EN-DC MR-DC and SA handover	CMCC. CATT, Qualcomm

9.3.2: Dynamic ACL

TDoc	Title	Source
R3-220087	Reply LS on ACL support for Indirect Data Forwarding	CT4
R3-220088	Reply LS On Source IP address clarifications	CT4
R3-220176	Support of dynamic ACL during handover and dual connectivity	Huawei, Deutsche Telekom, China Telecom, Ericsson
R3-220177	Support of dynamic ACL during handover and dual connectivity	Huawei, Deutsche Telekom, China Telecom, Ericsson
R3-220178	Support of dynamic ACL during handover and dual connectivity	Huawei, Deutsche Telekom, China Telecom, Ericsson
R3-220179	Support of dynamic ACL during handover and dual connectivity	Huawei, Deutsche Telekom, Ericsson
R3-220301	Dynamic ACL over E1 CR 38.463	Ericsson, Deutsche Telekom, China Telecom, Huawei
R3-220302	Dynamic ACL over S1 CR 36.413	Ericsson, Deutsche Telekom, China Telecom, Huawei
R3-220303	Dynamic ACL over X2 CR 36.423	Ericsson, Deutsche Telekom, China Telecom, Huawei
R3-220304	Dynamic ACL over Xn CR 38.423	Ericsson, Deutsche Telekom, China Telecom, Huawei
R3-220437	Reply LS On Source IP address clarifications	Ericsson
R3-220536	Discussion on ACL for MR-DC scenario	CATT
R3-220627	Support of dynamic ACL for per DRB data forwarding + LS status	Nokia, Nokia Shanghai Bell
R3-220728	Discussion on ACL issue for indirect data forwarding in SN change	ZTE Corporation
R3-221001	CB: # 9_DynamicACL - Summary of email discussion	Huawei - moderator
R3-221371	Reply LS On Source IP address clarifications	Ericsson
R3-221444	Support of dynamic ACL during handover and dual connectivity	Huawei, Deutsche Telekom, Ericsson
R3-221474	Reply LS On Source IP address clarifications	Ericsson

9.3.3: Misalignment value range for report interval IE of MDT

TDoc	Title	Source
R3-220109	Reply LS on MDT Stage 2 and Stage 3 Alignment (reply LS to R3-207222)	RAN2
R3-220305	Synching the Collection Period values to those specified in TS32.422	Ericsson
R3-220306	Synching the Collection Period values to those specified in TS32.422	Ericsson
R3-220313	(draft) Reply LS to RAN2 stage 2 to stage 3 alignment	Ericsson
R3-220737	Discussion on synching the collection period values to SA5 specifications	CATT
R3-220738	36.413 CR for synching the collection period values to SA5 specifications	CATT
R3-220901	Discussion on value range misalignment for M1, M8 and M9 configuration	ZTE, CATT, China Telecom, China Unicom, Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Samsung
R3-220902	Value range misalignment for M1, M8 and M9 measurement configuration	ZTE, CATT, China Telecom, China Unicom, Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Samsung
R3-220903	Value range misalignment for M1, M8 and M9 measurement configuration	ZTE, CATT, China Telecom, China Unicom, Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Samsung
R3-221002	CB: # 10_ReportIntervalMDT - Summary of email discussion	ZTE - moderator
R3-221091	Value range misalignment for MDT M1, M8 and M9 configuration	ZTE, CATT, China Telecom, China Unicom, Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Samsung, CMCC, Ericsson
R3-221092	Value range misalignment for MDT M1, M8 and M9 configuration	ZTE, CATT, China Telecom, China Unicom, Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Samsung, CMCC, Ericsson
R3-221260	Draft LS to SA5 on updates on the configuration of MDT M1, M8 and M9 in RAN3 specifications	ZTE
R3-221445	LS on configuration updates of MDT M1, M8 and M9 in RAN3 specifications	ZTE

9.3.4: NAS PDU delivery during PDU Session Modify

TDoc	Title	Source
R3-220369	Correction of NAS PDU delivery	Nokia, Nokia Shanghai Bell, Orange, Verizon Wireless
R3-220372	Correction of NAS PDU delivery	Nokia, Nokia Shanghai Bell, Orange, Verizon Wireless
R3-220537	Discussion on NAS PDU delivery during PDU session modification procedure	CATT
R3-220538	Correction on NAS PDU delivery during PDU session modification procedure	CATT
R3-220613	Discussion on PDU session related NAS-PDU delivery	Ericsson
R3-220614	Discussion on PDU session related NAS-PDU delivery	Ericsson
R3-220615	Discussion on PDU session related NAS-PDU delivery	Ericsson
R3-220681	Correction of PDU session resource modify	Huawei, China Unicom, Orange
R3-220682	Correction of PDU session resource modify	Huawei, China Unicom, Orange
R3-220871	Discussion on PDU session resource modify	CMCC
R3-220958	Correction of NSA PDU Delivery for PDU SESSION RESOURCE MODIFY Procedure	ZTE
R3-221003	CB: # 11_NAS_PDUDelivery - Summary of email discussion	CATT - moderator
R3-221303	[Draft] LS on NAS PDU delivery during PDU Session Modification procedure	CATT
R3-221409	LS on NAS PDU delivery during PDU Session Modification procedure	CATT
R3-221475	LS on NAS PDU delivery during PDU Session Modification procedure	CATT

9.3.5.1: Other Corrections

TDoc	Title	Source
R3-220144	Restoring SCG configuration after SCG release	Nokia, Nokia Shanghai Bell
R3-220145	Restoring SCG configuration after SCG release	Nokia, Nokia Shanghai Bell
R3-220146	Restoring SCG configuration after SCG release	Nokia, Nokia Shanghai Bell
R3-220147	Restoring SCG configuration after SCG release	Nokia, Nokia Shanghai Bell
R3-220180	Discussion on Secondary RAT Data Usage Report Co-ordination for ENDC and MRDC	RadiSys, Reliance JIO, ZTE
R3-220181	CR on Secondary RAT Data Usage Co-ordination for 36.423 for R16	RadiSys, Reliance JIO, ZTE
R3-220182	CR on Secondary RAT Data Usage Co-ordination for 38.423 for R16	RadiSys, Reliance JIO, ZTE
R3-220183	F1 Cause value for R15	RadiSys, Reliance JIO, ZTE
R3-220184	F1 Cause value for R16	RadiSys, Reliance JIO, ZTE
R3-220190	Correction of intra-system data forwarding	Nokia, Nokia Shanghai Bell, CATT, Orange, Verizon Wireless, Deutsche Telekom
R3-220191	Correction of intra-system data forwarding	Nokia, Nokia Shanghai Bell, CATT, Orange, Verizon Wireless, Deutsche Telekom
R3-220212	Correction on packet delay budget for IAB access link in TS 38.473	ZTE, Qualcomm, CATT
R3-220213	CR to 38.473: Correction on IAB TNL Address Allocation procedure	ZTE, CATT, Qualcomm, Samsung, Nokia, Nokia Shanghai Bell
R3-220289	IPv6 Flow Label handling for Rel-16 IAB using IPsec tunnel mode	Qualcomm Incorporated
R3-220290	CR to 38.401 on IPv6 Flow Label handling for IAB using IPv6 tunnel mode	Qualcomm Incorporated
R3-220378	CR to TS38.473: Correction on PC5 QoS parameters for NR V2X	ZTE
R3-220405	Correction of intra-system data forwarding	Nokia, Nokia Shanghai Bell, CATT, Orange, Verizon Wireless
R3-220406	Correction of intra-system data forwarding	Nokia, Nokia Shanghai Bell, CATT, Orange, Verizon Wireless, Deutsche Telekom
R3-220434	Correction on the usage of selected PLMN	Huawei, Deutsche Telekom, Orange
R3-220435	Correction on the usage of selected PLMN	Huawei, Deutsche Telekom, Orange
R3-220443	F1-U delay measurement	Ericsson, ZTE, CATT, Nokia, Nokia Shanghai Bell
R3-220458	Discussion on removing the restriction of cause value of �procedure cancelled�	CATT
R3-220459	Remove the restriction on cause value �procedure cancelled� for 38.423 (R15)	CATT
R3-220471	Discussion on Unmapped UL Flows	Nokia, Nokia Shanghai Bell
R3-220472	Unmapped UL QoS Flows in NR-DC	Nokia, Nokia Shanghai Bell
R3-220473	Clarification on AS rekeying feedback during Xn handover	NTT DOCOMO INC.
R3-220474	Clarification on AS rekeying feedback during Xn handover	NTT DOCOMO INC.
R3-220504	Clarification on AS rekeying feedback during Xn handover	NTT DOCOMO INC.
R3-220505	Correction on positioning information configuration	Huawei
R3-220506	Correction on Measurement Periodicity	Huawei
R3-220507	Correction on Measurement Periodicity	Huawei
R3-220508	Correction on PRS Beam information	Huawei
R3-220509	Correction on PRS Beam information	Huawei
R3-220541	Correction on PDU Session Resource Setup procedure	CATT, Ericsson, ZTE, Nokia, Nokia Shanghai Bell
R3-220544	Correction on the ASN.1 for neighbour cell information	CATT,Ericsson,Huawei
R3-220555	Discussion on measurement gap configuration for position	Samsung, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CATT, Verizon Wireless, ZTE
R3-220556	CR for the correction on measurement gap configuration for position	Samsung, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CATT, Verizon Wireless, ZTE
R3-220557	IP packet mapping for EN-DC case	Samsung, ZTE, Huawei, Verizon Wireless
R3-220558	Correction of Qos Mapping Information IE in X2AP message for IAB (CR to TS36.423, R16)	Samsung, ZTE, Huawei, Verizon Wireless
R3-220591	Restoring SCG configuration after SCG release	Nokia, Nokia Shanghai Bell
R3-220592	Restoring SCG configuration after SCG release	Nokia, Nokia Shanghai Bell
R3-220625	Correction on UE XnAP ID in the ERROR INDICATION message	Ericsson
R3-220626	Correction on UE XnAP ID in the ERROR INDICATION message	Ericsson
R3-220641	Accurate retainability measurements for CP/UP separation	Ericsson
R3-220642	Accurate retainability measurements for CP/UP separation - Solution A	Ericsson
R3-220643	Accurate retainability measurements for CP/UP separation - Solution B	Ericsson
R3-220683	Retrieve UE context for NPN only cell	Huawei, Deutsche Telekom, Orange
R3-220684	Retrieve UE context for NPN only cell	Huawei, Deutsche Telekom, Orange
R3-220685	Correction of frequency information for DL only or UL only cell	Huawei, China Telecom, Deutsche Telekom
R3-220686	Correction of frequency information for DL only or UL only cell	Huawei, China Telecom, Deutsche Telekom
R3-220687	Correction of frequency information for DL only or UL only cell	Huawei, China Telecom, Deutsche Telekom
R3-220688	Correction of frequency information for DL only or UL only cell	Huawei, China Telecom, Deutsche Telekom
R3-220689	Correction of frequency information for DL only or UL only cell	Huawei, China Telecom, Deutsche Telekom
R3-220690	Correction of indirect data forwarding for MR-DC	Huawei, China Telecom, China Unicom, Deutsche Telekom
R3-220691	Correction of indirect data forwarding for MR-DC	Huawei, China Telecom, China Unicom, Deutsche Telekom
R3-220754	Clarification for handling of end marker packets_R15	ZTE
R3-220755	Clarification for handling of end marker packets_R16	ZTE
R3-220756	VoNR supportive for UE capability Check procedure in NGAP	ZTE, China Telecom
R3-220757	CR for VoNR supportive for UE capability Check procedure	ZTE, China Telecom
R3-220769	Discussion on F1-U Delay Measurement for QoS Monitoring	Samsung, Verizon Wireless, Intel Corporation, Huawei, CMCC, KDDI
R3-220770	Correction of F1-U delay measurement for QoS monitoring	Samsung, Verizon Wireless, Intel Corporation, Huawei, CMCC, KDDI
R3-220836	CR for 38.463 on fixing DAPS HO handling inconsistency during Bearer Context Modification procedure	Intel Corporation
R3-220848	Correction on NG interface management messages	Huawei, Deutsche Telekom
R3-220849	Correction on NG interface management messages	Huawei, Deutsche Telekom
R3-220850	Correcion of QoS monitoring disabled	Huawei, ZTE, CMCC
R3-220851	Correcion of QoS monitoring disabled	Huawei, ZTE, CMCC
R3-220994	[DRAFT] Reply LS on the user consent for trace reporting	Apple [to become RAN3]
R3-220995	On user consent for RLF/CEF	Apple
R3-220996	User consent for location information in RLF/CEF	Apple
R3-220997	User consent for location information in RLF/CEF	Apple
R3-221005	CB: # 13_F1-UDelay - Summary of email discussion	Ericsson - moderator
R3-221006	CB: # 14_IABCorrec - Summary of email discussion	ZTE - moderator
R3-221007	CB: # 15_PositionCorrec - Summary of email discussion	Huawei - moderator
R3-221087	Correction on the ASN.1 for neighbour cell information	CATT, Ericsson, Huawei
R3-221094	CR on Secondary RAT Data Usage Co-ordination for 36.423 for R16	RadiSys, Reliance JIO, ZTE
R3-221095	CR on Secondary RAT Data Usage Co-ordination for 38.423 for R16	RadiSys, Reliance JIO, ZTE
R3-221100	CB: # 90_IntraSystemDF - Summary of email discussion	Nokia
R3-221101	CB:# 91_DLUPOnlyCell - Summary of email discussion	Huawei - moderator
R3-221102	CB: # 92_IndirectDF - Summary of email discussion	Huawei - moderator
R3-221103	Correction on the ASN.1 for neighbour cell information	CATT, Ericsson, Huawei
R3-221104	CB: # 94_SecondaryRATDataReport - Summary of email discussion	RadiSys - moderator
R3-221105	CB: # 95_UEContextNPN - Summary of email discussion	Huawei - moderator
R3-221110	CB: # 96_PC5QoS - Summary of offline discussion	ZTE -moderator
R3-221111	CB: # 97_SCGReleaseRestore - Summary of email discussion	Nokia - moderator
R3-221186	Correction on positioning information configuration	Huawei, Nokia, Nokia Shanghai Bell
R3-221187	Correction on Measurement Periodicity	Huawei, Nokia, Nokia Shanghai Bell
R3-221188	Correction on Measurement Periodicity	Huawei, Nokia, Nokia Shanghai Bell
R3-221189	Correction on PRS Beam information	Huawei, Nokia, Nokia Shanghai Bell
R3-221190	Correction on PRS Beam information	Huawei, Nokia, Nokia Shanghai Bell
R3-221191	Correction of indirect data forwarding for MR-DC	Huawei, China Telecom, China Unicom, Deutsche Telekom
R3-221213	Correction of frequency information for DL only or UL only cell	Huawei, China Telecom, Deutsche Telekom, Orange, Nokia, Nokia Shanghai Bell
R3-221214	Correction of frequency information for DL only cell	Huawei, China Telecom, Deutsche Telekom, Orange, Nokia, Nokia Shanghai Bell
R3-221232	Correction on packet delay budget for IAB access link in TS 38.473	ZTE, Qualcomm, CATT
R3-221240	CR to 38.401 on IPv6 Flow Label handling for IAB using IPv6 tunnel mode	Qualcomm Incorporated
R3-221267	Correction of Qos Mapping Information IE in X2AP message for IAB (CR to TS36.423, R16)	Samsung, ZTE, Huawei, Verizon Wireless
R3-221277	Retrieve UE context for NPN only cell	Huawei, Deutsche Telekom, Orange, Nokia, Nokia Shanghai Bell
R3-221287	Correction of indirect data forwarding for MR-DC	Huawei, China Telecom, China Unicom, Deutsche Telekom
R3-221307	CR to TS38.473: Correction on PC5 QoS parameters for NR V2X	ZTE
R3-221365	Correction on UE XnAP ID in the ERROR INDICATION message	Ericsson
R3-221366	Correction on UE XnAP ID in the ERROR INDICATION message	Ericsson
R3-221420	CR to 38.401 on IPv6 Flow Label handling for IAB using IPv6 tunnel mode	Qualcomm Incorporated
R3-221457	CR to TS38.473: Correction on PC5 QoS parameters for NR V2X	ZTE

10.1: General

TDoc	Title	Source
R3-220006	BLCR to 36.423:Support of MDT enhancement	CATT
R3-220007	BLCR to 36.300_Addition of SON features enhancement	Lenovo, Motorola Mobility
R3-220013	MRO for PScell Change Failure	Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE
R3-220014	BLCR to 38.401: Support of MDT enhancement	CMCC
R3-220024	BLCR to 38.300_Addition of SON features enhancement	CMCC
R3-220025	BLCR to 38.401_Addition of SON features enhancement	ZTE
R3-220056	BLCR to 36.423_Addition of SON features enhancement	CATT
R3-220057	BLCR to 38.413_Addition of SON features enhancement	Ericsson
R3-220058	BLCR to 38.423_Addition of SON features enhancement	Samsung
R3-220059	BLCR to 38.473_Addition of SON features enhancement	Huawei
R3-220060	BLCR to 37.320: Support of MDT enhancement	Nokia, Nokia Shanghai Bell
R3-220061	MDT in MR-DC	Huawei
R3-220062	BLCR to 38.463: Support of MDT enhancement	Nokia, Nokia Shanghai Bell
R3-220081	BLCR to 38.473: Support of MDT enhancement	Samsung
R3-220082	BLCR to 36.413_Addition of SON features enhancement	Qualcomm
R3-220083	BLCR to 38.413: Support of MDT enhancement	Ericsson
R3-220875	updated work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI	CMCC, Ericsson
R3-221016	CB: # SONMDT1_Workplan_BLCRs - Summary of email discussion	CMCC - moderator
R3-221198	BLCR to 38.413: Support of MDT enhancement	Ericsson

10.2.1.3: Successful Handover Report

TDoc	Title	Source
R3-220315	Successful Handover Report	Huawei

10.2.1.4: UE History Information in EN-DC

TDoc	Title	Source
R3-220159	[TP to SON BL CR to 38.413, NR_ENDC_SON_MDT_enh] Completion of the work on the SCG UHI	Nokia, Nokia Shanghai Bell
R3-220160	[TP to SON BL CR to 38.423, NR_ENDC_SON_MDT_enh] Completion of the work on the SCG UHI	Nokia, Nokia Shanghai Bell
R3-220270	UE History Information in MR-DC	Qualcomm Incorporated
R3-220316	(TP for SON BLCR for 38.423, 38.413, 36.413 and 36.423, 37.340, 38.300) UE History Information in MR-DC	Huawei
R3-220389	Consideration on UE history information	China Telecommunication
R3-220517	(TP for 38.300)Enhancement of UE history information in MR-DC scenario	CATT, CMCC
R3-220518	(TP on UE history information for 36.413) Addition of UE history information for SN	CATT, CMCC
R3-220519	(TP on UE history information for 36.423) Addition of UE history information for SN	CATT, CMCC
R3-220575	(TP for SON BL CR for TS 38.423, TS 38.413, TS 36.413) UE History Information for Secondary Node	Ericsson
R3-220786	TP for SON BLCR for 38.423: UE History Information in MR-DC	Samsung
R3-220787	TP for SON BLCR for 36.423: UE History Information in EN-DC	Samsung
R3-220876	(TP to SON BLCR TS 38.413)UE history information in MR-DC	CMCC, CATT
R3-220877	(TP to SON BLCR TS 38.423)UE history information in MR-DC	CMCC, CATT
R3-220972	UE History Information in MR-DC	ZTE, Lenovo, Motorola Mobility, China Unicom
R3-220973	(TP for SON BL CR for TS 37.340) Introduce UHI in MR-DC	ZTE, Lenovo, Motorola Mobility, China Unicom
R3-220974	(TP for SON BL CR for TS 38.423) Introduce UHI in MR-DC	ZTE, Lenovo, Motorola Mobility, China Unicom
R3-220975	(TP for SON BL CR for TS 36.423) Introduce UHI in MR-DC	ZTE, Lenovo, Motorola Mobility, China Unicom
R3-220976	(TP for SON BL CR for TS 38.413) Introduce UHI in MR-DC	ZTE, Lenovo, Motorola Mobility, China Unicom
R3-220977	(TP for SON BL CR for TS 36.413) Introduce UHI in MR-DC	ZTE, Lenovo, Motorola Mobility, China Unicom
R3-221017	CB: # SONMDT2_UEHistoryInfor - Summary of email discussion	ZTE - moderator
R3-221182	(TP for SON BLCR for 38.300) UE History Information in MR-DC	Huawei
R3-221211	CB: # SONMDT2_UEHistoryInfor - Summary of email discussion	ZTE - moderator
R3-221262	TP for SON BLCR for 38.423: UE History Information in MR-DC	Samsung
R3-221282	(TP for SON BL CR for TS 37.340) Introduce UHI in MR-DC	ZTE, Lenovo, Motorola Mobility, China Unicom
R3-221283	(TP for SON BL CR for TS 36.423) Introduce UHI in MR-DC	ZTE, Lenovo, Motorola Mobility, China Unicom
R3-221321	[TP to SON BL CR to 38.413, NR_ENDC_SON_MDT_enh] Completion of the work on the SCG UHI	Nokia, Nokia Shanghai Bell
R3-221356	(TP for SON BL CR for TS 36.413): UE History Information for Secondary Node	Ericsson

10.2.1.5: Load Balancing Enhancements

TDoc	Title	Source
R3-220155	Per-beam load balancing and load information from aggregated cells	Nokia, Nokia Shanghai Bell
R3-220156	[SON, TP to BL CR to TS 38.473] The information on the per-beam HO triggering point	Nokia, Nokia Shanghai Bell
R3-220242	Discussion on PSCell MLB	CATT
R3-220252	Discussion on per-SSB and per-slice Mobility Settings Change	NEC
R3-220317	(TP for SON BLCR for 38.423) Load Balancing Enhancements	Huawei
R3-220422	Discussion on PSCell MLB	CATT
R3-220576	(TP for SON BL CR for TS 38.423) MLB enhancements	Ericsson
R3-220577	(TP for SON BL CR for TS 36.423) MLB enhancements	Ericsson
R3-220711	(TP for 36.423) Support of PSCell MLB	CATT
R3-220870	(TP for SON BLCR to 38.423) Remaining issues on MLB	CMCC
R3-220885	Further Discussion on Load Balancing Enhancements in NR	ZTE, China Telecom
R3-221018	CB: # SONMDT3_LoadBalance - Summary of email discussion	Nokia - moderator
R3-221212	CB: # SONMDT3_LoadBalance - Summary of email discussion	Nokia - moderator
R3-221359	(TP for 36.423) Support of PSCell MLB	CATT
R3-221368	(TP for SON BL CR for TS 38.423) MLB enhancements	Ericsson

10.2.1.6: MRO for SN Change Failure

TDoc	Title	Source
R3-220157	[TP to SON BL CRs to 38.423 and 36.423, NR_ENDC_SON_MDT_enh] MRO for PSCell change failure	Nokia, Nokia Shanghai Bell
R3-220271	MRO for SN change failure	Qualcomm Incorporated
R3-220318	(TP for SON BLCR for 38.423, 38.300) MRO for SN Change Failure	Huawei
R3-220390	MRO for SN Change Failure	China Telecommunication
R3-220516	(TP for 38.423)Consideration on support of SN change failure in case of MR-DC	CATT
R3-220578	(TP for SON BL CR for TS 38.300, TS 38.423) MRO for SN change failure	Ericsson
R3-220784	MRO for SN Change Failure	Samsung
R3-220785	TP for SON BLCR for TS38.423: Support of SON for SN change failure	Samsung
R3-220967	Further consideration on MRO SN change failure	ZTE
R3-220968	(TP for SON BL CR of TS 38.423) MRO SN change failure	ZTE
R3-221019	CB: # SONMDT4_SNChangeFailure - Summary of email discussion	Samsung - moderator
R3-221291	TP for SON BLCR for TS38.423: Support of SON for SN change failure	Samsung
R3-221334	CB: # SONMDT4_SNChangeFailure - Summary of email discussion	Samsung - moderator
R3-221436	CB: # SONMDT4_SNChangeFailure - Summary of email discussion	Samsung - moderator

10.2.1.7: RACH Optimization Enhancements

TDoc	Title	Source
R3-220379	(TP for SON BL CR for TS 38.473, TS 36.423): Left overs on RACH Optimization Enhancements	Huawei
R3-220529	Discussion on Rel-16 leftover issues for PRACH coordination	CATT,CMCC,China Telecom
R3-220530	(TP on SON for 38.473) TP on PRACH coordination for F1AP	CATT, CMCC, China Telecom
R3-220531	(TP on SON for 36.423) TP on PRACH coordination for X2AP	CATT, CMCC, China Telecom
R3-220579	(TP for SON BL CR for TS 38.473 and for TS38.423) RACH conflict resolution and reporting procedures	Ericsson
R3-220630	(TP for TS 38.473) Discussion on Leftover Issues of RACH Optimization	Nokia, Nokia Shanghai Bell
R3-221020	CB: # SONMDT5_RACHOpt - Summary of email discussion	CATT - moderator
R3-221252	(TP for SON BL CR for TS 36.423): Left overs on RACH Optimization Enhancements	Huawei
R3-221300	(TP on SON for 38.473) TP on PRACH coordination for F1AP	CATT, CMCC, China Telecom
R3-221333	CB: # SONMDT5_RACHOpt - Summary of email discussion	CATT - moderator
R3-221414	(TP on SON for 38.473) TP on PRACH coordination for F1AP	CATT, CMCC, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson
R3-221458	(TP on SON for 38.473) TP on PRACH coordination for F1AP	CATT, CMCC, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson

10.2.2: Coverage and Capacity Optimization

TDoc	Title	Source
R3-220253	CCO over F1: functional split and signaling between gNB-CU and gNB-DU	NEC
R3-220254	(TP for SON BLCR 38.300) Coverage and Capacity Optimization	NEC
R3-220255	(TP for SON BLCR for 38.473) Coverage and Capacity Optimization	NEC
R3-220319	(TP for SON BLCR for 38.473, 38.401,38.300, 38.470) Coverage and Capacity Optimization	Huawei
R3-220333	(TP for SON BL CR for TS 38.300, 38.401) Further discussion on CCO	Nokia, Nokia Shanghai Bell
R3-220580	(TP for SON BL CR for TS 38.300, TS 38.401) NR CCO solution	Ericsson
R3-220581	(TP for SON BL CR for TS 38.423, TS 38.473) Measurements for CCO issue detection	Ericsson
R3-220783	TP for SON BLCR for TS38.300: Support of SON for CCO	Samsung
R3-220886	Further Discussion on Coverage and Capacity Optimization in NR	ZTE, China Telecom, China Unicom
R3-220887	TP for BL CR 38.300 on Coverage and Capacity Optimization	ZTE, China Telecom, China Unicom
R3-220888	TP for BL CR 38.423 on Coverage and Capacity Optimization	ZTE, China Telecom, China Unicom
R3-220889	TP for BL CR 38.473 on Coverage and Capacity Optimization	ZTE, China Telecom, China Unicom
R3-221021	CB: # SONMDT6_CCO - Summary of email discussion	Ericsson - moderator
R3-221197	(TP for SON BL CR for TS 38.473) Measurements for CCO issue detection	Ericsson
R3-221249	TP for BL CR 38.423 on Coverage and Capacity Optimization	ZTE, China Telecom, China Unicom
R3-221323	CB: # SONMDT6_CCO - Summary of email discussion	Ericsson - moderator
R3-221416	(TP for SON BL CR for TS 38.473) Measurements for CCO issue detection	Ericsson
R3-221417	TP for BL CR 38.423 on Coverage and Capacity Optimization	ZTE, China Telecom, China Unicom

10.2.4: Inter-System Load Balancing

TDoc	Title	Source
R3-220256	Discussion on PRB usage load status metric for inter-system load balancing	NEC
R3-220320	(TP for SON BLCR for 38.413) Inter-System Load Balancing	Huawei
R3-220582	(TP for SON for TS 38.413, TS 38.300, TS 36.300) Inter-System Load Balancing	Ericsson
R3-220868	Introduction of PRB usage for inter-system load balancing	CMCC, Deutsche Telekom, Bell Mobility, Verizon, NTT DOCOMO, Orange, China Unicom, ZTE
R3-220869	(TP for SON BLCR to 38.413, 38.300, 36.300) Remaining issues on load metrics of inter-system load balancing	CMCC
R3-220978	Further Discussion on Inter-system Load Balancing in NR	ZTE, China Telecom
R3-220979	TP for BL CR 36.300 on Inter-system Load Balancing	ZTE, China Telecom
R3-220980	TP for BL CR 38.300 on Inter-system Load Balancing	ZTE, China Telecom
R3-220981	TP for BL CR 38.413 on Inter-system Load Balancing	ZTE, China Telecom
R3-221022	CB: # SONMDT7_InterSystemLB - Summary of email discussion	CMCC - moderator
R3-221251	CB: # SONMDT7_InterSystemLB - Summary of email discussion	CMCC - moderator

10.2.6: Mobility Enhancement Optimization

TDoc	Title	Source
R3-220158	Further consideration on using the Mobility Information in case of CHO	Nokia, Nokia Shanghai Bell
R3-220321	(TP for SON BLCR for 38.423) Mobility enhancements	Huawei
R3-220475	SON Enhancements for CHO	Lenovo, Motorola Mobility, ZTE
R3-220514	(TP on MRO for mobility Enhancement for 38.300)Discussion on MRO for mobility Enhancement	CATT
R3-220515	(TP on MRO for 38.423) Failure Indication message enhancement for CHO	CATT
R3-220758	Leftover issue on Mobility enhancement	ZTE
R3-220780	TP for TS 38.300: SON enhancements for CHO	Samsung
R3-220781	TP for SON BLCR for 38.423: Support of CHO for MRO	Samsung
R3-220782	LS on SON for CHO	Samsung
R3-221023	CB: # SONMDT8_CHOEnh - Summary of email discussion	Lenovo - moderator
R3-221089	TP for TS 38.300: SON enhancements for CHO	Samsung
R3-221292	TP for TS 38.300: SON enhancements for CHO	Samsung
R3-221294	CB: # SONMDT8_CHOEnh - Summary of email discussion	Lenovo - moderator
R3-221308	(TP on MRO for mobility Enhancement for 38.300)Discussion on MRO for mobility Enhancement	CATT

10.3.2.1: MDT Enhancements

TDoc	Title	Source
R3-220095	Reply LS on Area scope configuration and Frequency band info in MDT configuration	RAN2
R3-220104	Reply LS on Beam measurement reports for the MDT measurements	RAN2
R3-220134	Reply LS on the Beam measurement reports for the MDT measurements	SA5
R3-220380	Propagation of user consent related information during Xn inter-PLMN Handover	Huawei
R3-220381	Propagation of user consent related information during Xn inter-PLMN handover	Huawei, Samsung
R3-220382	Discussion on Reply LS on Area scope configuration and Frequency band info in MDT configuration	Huawei
R3-220583	(TP for MDT BL CR for TS 38.413, TS38.423) Remaining MDT updates	Ericsson
R3-220584	(TP for MDT BL CR for TS 38.413, TS38.423) Introduction of the on Beam level measurement report configuration	Ericsson
R3-220585	[DRAFT] Reply LS to RAN2 on beam measurement reports	Ericsson
R3-220586	[DRAFT] Reply LS to SA5 on beam measurement reports	Ericsson
R3-220605	On open points for MDT enhancements	Nokia, Nokia Shanghai Bell
R3-220735	Discussion on the propagation of MDT configuration in Xn inter-RAT HO and NG HO in case of s-based MDT	CATT
R3-220736	Discussion about the received LS on MDT enhancement	CATT
R3-220743	[Draft] Reply LS on Area scope configuration and Frequency band info in MDT configuration	Huawei
R3-220759	Leftover issue on MDT	ZTE
R3-220760	Misalignment between RAN2 and RAN3 specs on the area scope configuration	ZTE
R3-220761	TPs for the introduction of the on Beam level measurement report configuration in TS38.413 and TS38.423	ZTE
R3-221024	CB: # SONMDT9_MDTEnh - Summary of email discussion	ZTE - moderator
R3-221177	Propagation of user consent related information during Xn inter-PLMN handover	Huawei, Samsung
R3-221178	Reply LS on Area scope configuration and Frequency band info in MDT configuration	Huawei
R3-221180	(TP for MDT BL CR for TS38.423) TPs for the introduction of the on Beam level measurement report configuration	ZTE
R3-221195	Correction to Area Scope Configuration and Frequency Band Info in MDT Configuration	Huawei
R3-221210	LS on User consent Updating	Ericsson
R3-221235	(TP for MDT BL CR for TS 38.413) Introduction of the on Beam level measurement report configuration	Ericsson
R3-221247	CB: # SONMDT9_MDTEnh - Summary of email discussion	ZTE - moderator
R3-221383	Reply LS to SA5 on beam measurement reports	Ericsson

10.3.2.2: MDT for MR-DC

TDoc	Title	Source
R3-220334	Further discussion on inter-node coordination for MDT in case of MR-DC	Nokia, Nokia Shanghai Bell
R3-220587	(TP for MDT BL CR for TS 38.413, TS 38.423) Signalling based immediate MDT in NR-DC	Ericsson
R3-221025	CB: # SONMDT10_MRDC - Summary of email discussion	Nokia - moderator
R3-221228	CB: # SONMDT10_MRDC - Summary of email discussion	Nokia - moderator

10.4: Support for L2 Measurements

TDoc	Title	Source
R3-220096	Reply LS on MDT M6 calculation for split bearers in MR-DC	RAN2
R3-220335	M5, M6 and M7 MDT measurements for split bearer	Nokia, Nokia Shanghai Bell
R3-220383	Discussion on Reply LS on MDT M6 calculation for split bearers in MR-DC	Huawei
R3-220588	On L2 (M6) Measurements	Ericsson
R3-220744	[DRAFT] Reply LS on MDT M6 calculation for split bearers in MR-DC	Huawei
R3-220762	L2 measurement relate to MDT M6 calculation for split bearers in MR-DC	ZTE
R3-221026	CB: # SONMDT11_L2Measurements - Summary of email discussion	Huawei - moderator

10.5: SON/MDT Optimizations for NR-U

TDoc	Title	Source
R3-220154	Further discussion on MRO and a new problem of PCI allocation in NR-U	Nokia, Nokia Shanghai Bell
R3-220384	MLB and MRO for NR-U	Huawei
R3-220476	SON Enhancements for NR-U	Lenovo, Motorola Mobility
R3-220589	(TP for SON BL CR for TS 38.423): Progress on MLB for NR-U	Ericsson
R3-220779	TP for SON BLCR for TS 38.423: Support of SON for NR-U	Samsung
R3-220890	Further Discussion on Load Balancing Optimization for NR-U	ZTE
R3-221027	CB: # SONMDT12_NRU - Summary of email discussion	Ericsson - moderator
R3-221273	TP to 38.423 to support MLB for NR-U	Ericsson
R3-221274	TP to 38.473 to support MLB for NR-U	Ericsson

11.1: General

TDoc	Title	Source
R3-220034	CR to TS38.473 for RedCap support	Samsung
R3-220035	Support for Redcap Ues	Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Samsung, Qualcomm Incorporated, CATT
R3-220036	Support for Redcap Ues	Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE
R3-220037	Draft BL CR to TS 38.300 on RedCap UEs impacts to NG-RAN	Ericsson, Nokia, Nokia Shangahi Bell, Samsung, CATT, Qualcomm Incorporated, ZTE
R3-220038	BL CR to 38.401 Support for Redcap Ues	CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Radisys
R3-220039	BL CR to 38.470 Support for Redcap Ues	ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, CATT, Qualcomm Incorporated
R3-221028	CB: # RedCap1_BLCRs - Summary of email discussion	Samsung - moderator
R3-221122	CR to TS38.473 for RedCap support	Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, CATT

11.2: Support for RedCap Capability Exchange

TDoc	Title	Source
R3-220101	LS reply on the coordination between gNBs supporting RedCap UEs	RAN2
R3-220185	(TP for XnAP and NGAP BL CR on RedCap) Redcap Support for Xn and NG mobility	RadiSys, Reliance JIO
R3-220192	Coordination of Redcap Capability across gNBs	Nokia, Nokia Shanghai Bell
R3-220232	Discussion on RedCap capability exchange	CATT
R3-220243	RedCap Mobility Handling and Capability Exchange	NEC
R3-220280	(TP for XnAP BL CR on RedCap) Xn mobility handling for RedCap UEs	Qualcomm Incorporated, Ericsson, T-Mobile USA, Samsung, Radisys, Reliance JIO, ZTE, Huawei, CMCC
R3-220299	[DRAFT] LS reply on the coordination between gNBs supporting RedCap UEs	Ericsson LM
R3-220300	(TP for F1AP BL CR on RedCap) F1 mobility handling for RedCap UEs	ZTE, Qualcomm Incorporated, Ericsson, T-Mobile USA, Samsung, Radisys, Reliance JIO, CMCC, Huawei
R3-220412	Discussion on RedCap capability exchange	CATT
R3-220460	Supporting RedCap UEs over E1 interface	Huawei
R3-220891	(TP to BL CR of 38.470) RedCap capability exchange	ZTE, Radisys, Reliance JIO, CMCC
R3-220892	(TP to BL CR of 38.413) RedCap indication	ZTE
R3-221029	CB: # RedCap2_UECapability - Summary of email discussion	Qualcomm - moderator
R3-221142	CB: # RedCap2_UECapability - Summary of email discussion	Qualcomm - moderator
R3-221375	(TP for XnAP BL CR on RedCap) Xn mobility handling for RedCap UEs	Qualcomm Incorporated, Ericsson, T-Mobile USA, Samsung, Radisys, Reliance JIO, ZTE, Huawei, CMCC, Verizon Wireless, NTTDOCOMO, Vodafone
R3-221376	(TP for F1AP BL CR on RedCap) F1 mobility handling for RedCap UEs	ZTE, Qualcomm Incorporated, Ericsson, T-Mobile USA, Samsung, Radisys, Reliance JIO, CMCC, Huawei, Vodafone
R3-221377	(TP to BL CR of 38.470) RedCap capability exchange	ZTE, Radisys, Reliance JIO, CMCC
R3-221382	[DRAFT] LS reply on the coordination between gNBs supporting RedCap UEs	Ericsson LM
R3-221396	LS reply on the coordination between gNBs supporting RedCap Ues	Ericsson LM

11.3: Support for the Extended DRX enhancements for RedCap UEs

TDoc	Title	Source
R3-220193	(TP for TS 38.413) Support of eDRX for Redcap UEs	Nokia, Nokia Shanghai Bell
R3-220194	(TP for TS 38.473) Support of eDRX for Redcap UEs	Nokia, Nokia Shanghai Bell
R3-220233	Discussion on extended DRX enhancements for RedCap UEs	CATT
R3-220234	TP for TS 38.473 Support for the eDRX enhancement for RedCap UEs	CATT
R3-220281	(TP for Support for RedCap TS 38.413) RAT specific eDRX parameters	Qualcomm Incorporated, Ericsson, Huawei
R3-220282	(TP for Support for RedCap TS 38.423) RAT specific eDRX parameters	Qualcomm Incorporated, Ericsson, Huawei
R3-220413	Discussion on extended DRX enhancements for RedCap UEs	CATT
R3-220414	TP for RedCap BL CR for TS 38.473 Support for the eDRX enhancement for RedCap UEs	CATT
R3-220449	TP to NG-AP BL CR: Addition of RedCap Indication and other clarifications	Ericsson, Qualcomm Inc., Radisys, Reliance JIO
R3-220450	TP to Xn-AP BL CR: Clarification on usage of CN PTW	Ericsson, Qualcomm Inc., ZTE
R3-220451	TP to F1-AP BL CR: Addition of RedCap eDRX Information	Ericsson
R3-220461	Supporting Redcap UEs over Xn interface	Huawei
R3-220463	Supporting Redcap UEs over F1 interface	Huawei
R3-220566	(TP to BL CR of TS38.473) Discussion on the remaining issues of Rel-17 RedCap	Samsung
R3-220724	TP for TS 38.473 Support for the eDRX enhancement for RedCap UEs	CATT
R3-220861	Discussion on Extended DRX enhancements for RedCap UEs	CMCC
R3-220893	(TP to BL CR of 38.423) RedCap paging	ZTE
R3-220894	(TP to BL CR of 38.473) RedCap paging	ZTE
R3-221030	CB: # RedCap3_eDRX - Summary of email discussion	Ericsson - moderator
R3-221125	Supporting Redcap UEs over Xn interface	Huawei, ZTE
R3-221143	CB: # RedCap3_eDRX - Summary of email discussion	Ericsson - moderator

12.2: Support for Carrier Selection and Carrier Specific Configuration

TDoc	Title	Source
R3-220195	Support of Carrier Selection based on coverage level	Nokia, Nokia Shanghai Bell
R3-220196	Support of Carrier Selection based on coverage level	Nokia, Nokia Shanghai Bell
R3-220225	(TP to TS36.413) Support CEL based paging carrier selection	ZTE
R3-220226	BLCR to TS38.413 for introduction of CEL based paging carrier selection	ZTE
R3-220423	(TPs to TS 36.413, 38.413) CE based Carrier Selection for NB-IoT	Huawei
R3-220446	Discussion on Rel-17 NB-IoT Carrier selection	Ericsson
R3-221047	CB: # NBIoTMTC1_CarrierSelect - Summary of email discussion	Nokia - moderator
R3-221150	LS on Coverage-Based Carrier Selection	Nokia, Nokia Shanghai Bell
R3-221162	LS on Coverage-Based Carrier Selection	Nokia, Nokia Shanghai Bell

13.1: General

TDoc	Title	Source
R3-220012	CR on CP-UP separation for Rel-17 IAB	Nokia, Nokia Shanghai Bell, Samsung, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics
R3-220015	CP-based Congestion Mitigation for IAB Network	ZTE
R3-220063	BL CR to TS 38.401 on support of eIAB	Huawei
R3-220064	BL CR to XnAP on Rel-17 eIAB	Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics
R3-220084	CP-based Congestion Indication for IAB Networks	Ericsson
R3-220291	Updated Workplan for Rel-17 IAB	Qualcomm Incorporated (WI Rapporteur)
R3-220292	draft CR for 38.300 on Rel-17 IAB enhancements	Qualcomm Incorporated
R3-221048	CB: # 1301_IAB_BL_CRs - Summary of email discussion	Qualcomm - moderator
R3-221230	draft CR for 38.300 on Rel-17 IAB enhancements	Qualcomm Incorporated
R3-221286	BL CR to TS 38.401 on support of eIAB	Huawei

13.2.1.1: Procedure Details

TDoc	Title	Source
R3-220114	Reply LS on Inter-donor migration for IAB enhancement	RAN4
R3-220138	Discussion on IAB inter-donor topology adaptation procedures	ZTE
R3-220161	(TP for IAB BL CR for TS 38.401): IAB Inter-Donor Topology Adaptation	Ericsson
R3-220230	Discussion on inter-CU migration for IAB	CATT
R3-220293	Inter-donor topology adaptation	Qualcomm Incorporated
R3-220402	Procedure of inter-donor topology migration	Fujitsu
R3-220410	Discussion on inter-CU migration for IAB	CATT
R3-220477	Discussion on IAB inter-donor migration	Lenovo, Motorola Mobility
R3-220559	(TP to BL CR of TS38.401) Discussion on inter-donor IAB node partial migration	Samsung
R3-220802	(TP for NR_IAB_enh BL CR for TS 38.401) Inter-CU topology update	Huawei
R3-220821	discussion on Inter-Donor IAB Node Migration	Nokia, Nokia Shanghai Bell
R3-221049	CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion	Qualcomm - moderator
R3-221231	(TP for IAB BL CR for TS 38.401) IAB Inter-CU topology adaptation procedure	Qualcomm Inc (Moderator)
R3-221326	(TP to BL CR for TS 38.300) Definition of IAB topology	Qualcomm Inc (Moderator)
R3-221327	CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion	Qualcomm - moderator

13.2.2: Reduction of Service Interruption

TDoc	Title	Source
R3-220139	Further considerations on service interruption reduction	ZTE
R3-220162	Reduction of Service Interruption in IAB Migration	Ericsson
R3-220294	Reduction of service interruption during IAB migration	Qualcomm Incorporated
R3-220403	Avoidance of descendant node reconfiguration	Fujitsu
R3-220560	(TP to BL CR of TS 38.473) Discussion on service interruption reduction for Rel-17 IAB	Samsung
R3-220709	intra-donor CU service interruption reduction	Intel Corporation
R3-220801	Further discussions on service reduction	Huawei
R3-220822	(TP for BL CR for TS 38.401) Discussion on Reduction of Service Interruption	Nokia, Nokia Shanghai Bell
R3-221050	CB: # 1303_IAB_Red_Serv_Inter - Summary of email discussion	Huawei - moderator
R3-221255	(TP for BL CR for TS 38.401) Discussion on Reduction of Service Interruption	Nokia, Nokia Shanghai Bell
R3-221360	(TP to BL CR of TS 38.473) Discussion on service interruption reduction for Rel-17 IAB	Samsung
R3-221429	(TP for BL CR for TS 38.401) Discussion on Reduction of Service Interruption	Nokia, Nokia Shanghai Bell
R3-221450	(TP to BL CR of TS 38.473) Discussion on service interruption reduction for Rel-17 IAB	Samsung

13.2.3: Topology Redundancy

TDoc	Title	Source
R3-220140	Discussion on the XnAP signalling for Inter-topology transport	ZTE
R3-220163	IAB Inter-Donor Topology Redundancy	Ericsson
R3-220211	(TP for NR_IAB BL CR for TS 38.473): F1-C transfer path configuration	ZTE, CATT, Qualcomm, Samsung
R3-220231	Discussion on inter-donor topology redundancy	CATT
R3-220295	Inter-donor topology transport	Qualcomm Incorporated
R3-220411	Discussion on inter-donor topology redundancy	CATT
R3-220478	Discussion on IAB inter-donor topology redundancy	Lenovo, Motorola Mobility
R3-220561	(TP to BL CR of TS38.423) Discussion on inter-donor topology redundancy	Samsung
R3-220800	(TP for NR_IAB_enh BL CR for TS 38.423_38.401) Inter-CU topology redundancy	Huawei
R3-220823	discussion on Inter-Donor IAB Topology Redundancy	Nokia, Nokia Shanghai Bell
R3-221051	CB: # 1304_IAB_Top_Red - Summary of email discussion	Ericsson - moderator
R3-221233	TP for IAB BL CR for TS 38.423	Samsung, Ericsson
R3-221237	TP for IAB BL CR for TS 38.401	Huawei, Ericsson
R3-221244	(TP for NR_IAB BL CR for TS 38.473): F1-C transfer path configuration	ZTE, CATT, Qualcomm, Samsung
R3-221317	CB: # 1304_IAB_Top_Red - Summary of email discussion	Ericsson - moderator
R3-221460	TP for IAB BL CR for TS 38.401	Huawei, Ericsson

13.3.1: Congestion Mitigation

TDoc	Title	Source
R3-220143	(TP for NR_IAB_enh BL CR for TS 38.473): Congestion indication in CP-based congestion mitigation	ZTE
R3-220164	(TP for IAB BL CR for TS 38.473): Congestion Mitigation in IAB Networks	Ericsson
R3-220479	(TP for IAB BL CR for TS 38.473) Remaining issues on congestion mitigation for IAB	Lenovo, Motorola Mobility
R3-220562	Discussion on congestion mitigation in Rel-17 eIAB	Samsung
R3-220803	Further discussions on congestion mitigation	Huawei
R3-221052	CB: # 1305_IAB_Con_Mit - Summary of email discussion	Lenovo - moderator

13.3.2: Multi-Hop Performance: QoS, Latency, Fairness

TDoc	Title	Source
R3-220141	Discussion on inter-Donor-DU re-routing in IAB	ZTE
R3-220165	Uplink Inter-Donor Rerouting in IAB Networks	Ericsson
R3-220296	Inter-donor-DU local rerouting for IAB	Qualcomm Incorporated
R3-220404	Discussion on inter-donor-DU re-routing	Fujitsu
R3-220480	Discussion on UL packet transmission for inter-donor-DU re-routing	Lenovo, Motorola Mobility
R3-220563	(TP to BL CR of TS38.473) Discussion on the inter-donor-DU rerouting	Samsung
R3-220804	(TP for NR_IAB_enh BL CR for TS 38.423_38.473)Inter-donor re-routing for IAB during topology update	Huawei
R3-220824	(TP for BL CR for TS 38.401) Inter donor-DU re-routing	Nokia, Nokia Shanghai Bell
R3-221053	CB: # 1306_IAB_Multi-hop - Summary of email discussion	ZTE - moderator
R3-221256	(TP for BL CR for TS 38.401) Inter donor-DU re-routing	Nokia, Nokia Shanghai Bell

13.4.1: Resource Multiplexing of Child and Parent Links and CLI Management

TDoc	Title	Source
R3-220142	Discussion on resource multiplexing in IAB	ZTE
R3-220166	(TP for IAB BL CR for TS 38.423 and TS 38.473) Inter-Donor Resource Coordination in IAB Networks	Ericsson
R3-220297	IAB multiplexing enhancements	Qualcomm Incorporated
R3-220805	(TP for NR_IAB_enh BL CR for TS 38.423) IAB resource multiplexing	Huawei
R3-220825	(TP for BL CR for TS 38.473) Resource multiplexing	Nokia, Nokia Shanghai Bell
R3-221054	CB: # 1307_IAB_Res_Multiplex - Summary of email discussion	Nokia - moderator

13.4.2: Others

TDoc	Title	Source
R3-220590	PHY layer configurations for Rel-17 IAB	Qualcomm Incorporated

14.1: General

TDoc	Title	Source
R3-220020	CPAC BL CR to TS38.401	ZTE
R3-220021	CPAC BL CR to TS38.463	Qualcomm
R3-220022	BLCR to TS 38.473 for Conditional PScell Change/Addition	CATT
R3-220041	CPAC BL CR to TS 38.420	Lenovo, Motorola Mobility
R3-220045	SCG BL CR to TS 36.423	Nokia, Nokia Shanghai Bell
R3-220046	SCG BL CR to TS 37.340	ZTE
R3-220047	SCG BL CR to TS 38.401	Huawei
R3-220048	SCG BL CR to TS 38.423	Ericsson
R3-220049	SCG BL CR to TS 38.473	Samsung
R3-220050	CPAC BL CR to TS 36.420	China Telecommunications
R3-220051	CPAC BL CR to TS 36.423	Nokia, Nokia Shanghai Bell
R3-220052	CPAC BL CR to TS 37.340	Huawei
R3-220053	CPAC BL CR to TS 38.423	Ericsson
R3-220153	(TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) CPAC BL CR rapporteur�s corrections	Nokia, Nokia Shanghai Bell
R3-221032	CB: # MRDC1_BLCRs - Summary of email discussion	Huawei - moderator
R3-221123	SCG BL CR to TS 38.473	Samsung
R3-221126	(TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) CPAC BL CR rapporteur�s corrections	Nokia, Nokia Shanghai Bell
R3-221134	SCG BL CR to TS 36.423	Nokia, Nokia Shanghai Bell
R3-221135	SCG BL CR to TS 38.401	Huawei
R3-221136	CPAC BL CR to TS 38.423	Ericsson

14.2: Signaling Support for Efficient Activation/Deactivation for One SCG and SCells

TDoc	Title	Source
R3-220148	(TPs to SCG BL CRs to 38.423 and 36.423, LTE_NR_DC_enh2-Core) Closing of remaining open points in the MN-SN signalling	Nokia, Nokia Shanghai Bell
R3-220149	(TP to SCG BL CR to 38.463, LTE_NR_DC_enh2-Core) Enabling information on SCG use	Nokia, Nokia Shanghai Bell
R3-220244	SCG Activation / Deactivation open issues discussion	NEC
R3-220245	(TP for SCG BL CR to TS36.423) SCG Activation / Deactivation	NEC
R3-220342	(TP for SCG BL CR to 38.423) Remaining issues for SCG (de)activation	Ericsson
R3-220343	(TP for SCG BL CR to TS 38.473) F1 impacts of SCG (de)activation	Ericsson
R3-220428	(TPs to SCG TS 38.401, 38.463 BL CRs) UP awareness of SCG activation deactivation	Huawei
R3-220429	(TPs to SCG TS 38.423, 36.423 BL CRs) Leftover issues on SCG activation deactivation	Huawei
R3-220481	Support of SCG Activation and Deactivation	Lenovo, Motorola Mobility
R3-220482	Left issues on SCG activation and deactivation	Lenovo, Motorola Mobility
R3-220571	(TP to SCG BL CR of TS38.473) Discussion on open issues for SCG (de)activation	Samsung
R3-220572	(TP to SCG BL CR of TS38.401) Discussion on open issues for SCG (de)activation	Samsung
R3-220931	Discussion on efficient Activation/Deactivation for SCG	CATT
R3-220932	(TP for SCG BLCR for TS 38423)efficient Activation/Deactivation for SCG	CATT
R3-220969	TP for SCG BL CR to TS 37.340	ZTE
R3-220970	TP for SCG BL CR to TS 38.423 36.423 38.463	ZTE
R3-220971	(TP for SCG BL CR to TS 38.473) Assisting information from F1 for SCG (de)activation	ZTE, Samsung, China Telecom
R3-221033	CB: # MRDC2_SCGActivation_Deactivation - Summary of email discussion	ZTE - moderator
R3-221139	CB: # MRDC2_SCGActivation_Deactivation - Summary of email discussion	ZTE - moderator
R3-221242	(TP for SCG BL CR to TS 38.473) F1 impacts of SCG (de)activation	Ericsson
R3-221281	TP for SCG BL CR to TS 37.340	ZTE, CATT
R3-221284	TP for SCG BL CR TS38.463	Lenovo, Motorola Mobility
R3-221335	(TP to SCG BL CR of TS38.401) Discussion on open issues for SCG (de)activation	Samsung
R3-221337	(TP to SCG TS 38.423) Leftover issues on SCG activation deactivation	Huawei
R3-221358	(TPs to SCG BL CR to 36.423, LTE_NR_DC_enh2-Core) Closing of remaining open points in the MN-SN signalling	Nokia, Nokia Shanghai Bell

14.3: Signaling Support for Conditional PSCell Change/Addition

TDoc	Title	Source
R3-220098	LS on SN initiated inter-SN CPC	RAN2
R3-220150	(TP to CPAC BL CR to 38.423, LTE_NR_DC_enh2-Core) Further development of the CPAC	Nokia, Nokia Shanghai Bell
R3-220151	(TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) Further development of the CPAC	Nokia, Nokia Shanghai Bell
R3-220152	(TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) Introducing the Release to the MN-initiated CPC	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Lenovo, Motorola Mobility, Ericsson
R3-220221	(TP for CPAC BLCR to TS36.423) CPAC replace and cancel	ZTE
R3-220222	(TP for CPAC BLCR to TS38.423) CPAC replace and cancel	ZTE
R3-220246	RAN3 signalling aspect for the SN Initiated Inter-SN CPC	NEC
R3-220261	Remaining aspects of CPAC replace and cancel procedures	Qualcomm Incorporated
R3-220262	Discussion of some outstanding CPAC issues	Qualcomm Incorporated
R3-220298	(TP to CPAC TS 37.340 BL CR) Update of MN initiated inter-SN CPC	Huawei, ZTE, Lenovo, Motorola Mobility, Ericsson, Nokia, Nokia Shanghai Bell
R3-220336	(TP to CPAC BL CR to 38.423) Introducing the Release to the MN-initiated CPC	Ericsson, Huawei, ZTE, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell
R3-220344	(TP for CPAC BL CR to 37.340) Signaling flows for SN-initiated inter-SN CPC	Ericsson
R3-220345	(TP for CPAC BL CR to TS 38.423) SN-initiated CPC and inter-node message design	Ericsson
R3-220346	[DRAFT] Reply LS on SN initiated inter-SN CPC	Ericsson
R3-220391	(TP for CPAC BLCR to TS36.423) Resolve the overload issues in CPAC procedure	China Telecommunication
R3-220392	(TP for CPAC BLCR to TS38.423) Resolve the overload issues in CPAC procedure	China Telecommunication
R3-220430	(TP to CPAC TS 37.340 BL CR) Support of SN initiated inter-SN CPC	Huawei
R3-220431	(TPs to 38.423 36.423 38.473 38.425 CPAC BL CRs) PDCP PDU forwarding and discard	Huawei
R3-220483	On support of SN initiated CPC	Lenovo, Motorola Mobility
R3-220484	[Draft] Reply LS on SN initiated inter-SN CPC	Lenovo, Motorola Mobility
R3-220521	Remaining issues on SN initiated conditional PSCell change	NTT DOCOMO INC.
R3-220554	(TP to CPAC BLCR to 37.340) Coordination Information and configuration parameters application in CPAC	Google Inc.
R3-220573	(TPs to CPAC BLCR for TS36.423 and TS38.423) Timer handling in MN initiated SN modification procedure	Google Inc.
R3-220812	(TP for CPAC BL CR to TS 38.423) Impacts considering RAN2 progress	Samsung
R3-220813	(TP for CPAC BL CR to TS 36.423) Impacts considering RAN2 progress	Samsung
R3-221034	CB: # MRDC3_CPAC - Summary of email discussion	Nokia - moderator
R3-221137	(TP to CPAC BL CR to 38.423) Introducing the Release to the MN-initiated CPC	Ericsson, Huawei, ZTE, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell
R3-221140	CB: # MRDC3_CPAC - Summary of email discussion	Nokia - moderator
R3-221338	(TP to CPAC TS 37.340 BL CR) Support of SN initiated inter-SN CPC	Huawei
R3-221363	(TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) Further development of the CPAC	Nokia, Nokia Shanghai Bell
R3-221369	(TP for CPAC BL CR to TS 38.423) SN-initiated CPC and inter-node message design	Ericsson
R3-221391	(TP for CPAC BLCR to TS36.423) CPAC replace and cancel	ZTE
R3-221393	(TP for CPAC BL CR to TS 38.423) Impacts considering RAN2 progress	Samsung

15.1: General

TDoc	Title	Source
R3-220040	(BL CR for TS38.473) Support of QoE information transfer	Samsung
R3-220042	CR TS 38.423 Mobility Support for NR QoE Measurement Collection	Ericsson
R3-220074	BLCR to 38.300	China Unicom, Ericsson, ZTE
R3-220075	BLCR to 38.410: Support of QoE Measurement Collection for NR	Nokia, Nokia Shanghai Bell
R3-220080	CR to 38.413 on Introduction of QoE measurement	Huawei, China Mobile, China Unicom, Ericsson, Samsung
R3-220113	LS on SA4 requirements for QoE	RAN2
R3-220727	Updated Workplan for Rel-17 NR QoE	China Unicom
R3-220733	(TP to TS38.300) NR QoE to merge RAN2 agreements	China Unicom
R3-221035	CB: # QoE1_Workplan_BLCRs - Summary of email discussion	China Unicom - moderator
R3-221208	(BL CR for TS38.473) Support of QoE information transfer	Samsung

15.2.1.1: Configuration, Activation and Deactivation Procedures

TDoc	Title	Source
R3-220132	LS on QoE configuration and reporting related issues	SA5
R3-220167	(TP for QoE BL CR for TS 38.300) Stage-2 Aspects of NR QoE Management	Ericsson
R3-220174	[Draft] Reply on LS QoE Configuration and Reporting Related Issues	Ericsson
R3-220328	(TP for BL CR to TS 38.300) Further discussion on configuration and activation aspects + overload handling	Nokia, Nokia Shanghai Bell
R3-220910	Stage 2 TPs to 38.300 on QoE measurement	Huawei
R3-220933	Discussion on NR QoE configuration procedures	CATT
R3-220934	TP for BLCR for 38.413 on NR QoE configuration	CATT
R3-220959	TP to BL CR of TS 38.300 for NR QoE	ZTE, China Telecom
R3-220987	(TP for BL CR to TS 38.410) Introduction of QMC mobility aspect	Nokia, Nokia Shanghai Bell
R3-221036	CB: # QoE2_Stage2 - Summary of email discussion	ZTE - moderator
R3-221258	Stage 2 TP to BL CR of TS 38.300 for NR QoE	ZTE, Ericsson, Huawei, Nokia
R3-221259	LS on QMC configuration and reporting	ZTE
R3-221269	(TP for BL CR to TS 38.410) Introduction of QMC mobility aspect	Nokia, Nokia Shanghai Bell
R3-221309	CB: # QoE2_Stage2 - Summary of email discussion	ZTE - moderator
R3-221437	LS on QMC related RAN3 progress	ZTE
R3-221438	Stage 2 TP to BL CR of TS 38.300 for NR QoE	ZTE, Ericsson, Huawei, Nokia, CATT, Qualcomm, China Unicom, China Telecom

15.2.1.2: Configuration Details

TDoc	Title	Source
R3-220131	LS on the mapping between service types and slice at application	SA5
R3-220168	(TP for QoE BL CR for TS 38.413) QoE Configuration and Reporting	Ericsson
R3-220175	[Draft] Reply LS on Mapping Between Service Types and Slice at Application	Ericsson
R3-220272	QoE configuration details	Qualcomm Incorporated
R3-220329	Clarifications on configuration aspects	Nokia, Nokia Shanghai Bell
R3-220874	Remaining issues on per-slice QoE measurement	CMCC
R3-220908	Further discussions on configuration details	Huawei
R3-220909	TP to 38.413 on further configuration details	Huawei
R3-220921	Further discussion on per-slice QoE	Samsung
R3-220935	Discussion on NR QoE configuration details	CATT
R3-220960	Discussion on NR QoE Configuration details	ZTE, China Telecom, China Unicom
R3-220961	(TP to BL CR of TS 38.413) NR QoE Configuration	ZTE, China Telecom
R3-221037	CB: # QoE3_Configuration_Report - Summary of email discussion	Huawei - moderator
R3-221271	TP to 38.413 on further configuration details	Huawei
R3-221310	CB: # QoE3_Configuration_Report - Summary of email discussion	Huawei - moderator
R3-221461	TP to 38.413 on further configuration details	Huawei

15.2.2: Measurement Collection and Continuity in Intra-System Intra-RAT Mobility

TDoc	Title	Source
R3-220169	Mobility Support for NR QoE Management	Ericsson
R3-220170	(TP for QoE BL CR for TS 38.423) Mobility Support for NR QoE Measurement Collection	Ericsson
R3-220273	QoE measurement collection and reporting continuity in mobility scenarios	Qualcomm Incorporated
R3-220330	Globally unique reference for m-based QMC session for mobility	Nokia, Nokia Shanghai Bell
R3-220911	Further discussions on mobility support of QoE measurement	Huawei
R3-220922	(TP for BL CR TS 38.423) Mobility support of NR QoE	Samsung
R3-220936	Discussion on Measurement Collection and Continuity in Intra-System Intra-RAT Mobility	CATT
R3-220953	Discussion on Mobility Support for Signalling Based QOE	China Telecom Corporation Ltd.
R3-220962	(TP to TS 38.423) NR QoE Configuration	ZTE, China Telecom
R3-220963	Discussion on Measurement Collection in Intra-System Intra-RAT Mobility	ZTE
R3-221038	CB: # QoE4_Mobility - Summary of email discussion	Ericsson - moderator
R3-221234	(TP for QoE BL CR for TS 38.423) Mobility Support for NR QoE Measurement Collection	Ericsson
R3-221270	LS on RAN3 agreement for management based QoE mobility	ZTE
R3-221305	(TP for QoE BL CR for TS 38.423) Mobility Support for NR QoE Measurement Collection	Ericsson
R3-221311	CB: # QoE4_Mobility - Summary of email discussion	Ericsson - moderator
R3-221427	LS on RAN3 agreement for management based QoE mobility	ZTE
R3-221462	(TP for QoE BL CR for TS 38.423) Mobility Support for NR QoE Measurement Collection	Ericsson

15.3: Support for RAN-Visible QoE

TDoc	Title	Source
R3-220111	LS on RAN visible QoE	RAN2
R3-220171	The Remaining Issues for RAN Visible QoE	Ericsson
R3-220172	Reporting Periodicity of RAN Visible QoE	Ericsson, CMCC, China Unicom
R3-220274	RAN visible QoE	Qualcomm Incorporated
R3-220331	Use of RAN visible QoE in the NG-RAN node	Nokia, Nokia Shanghai Bell
R3-220734	Configuration and Reporting of RAN Visible QoE	China Unicom
R3-220912	Further discussions on RAN visible QoE metrics	Huawei
R3-220923	Further discussion on RAN visible QoE	Samsung
R3-220937	Discussion on RAN visible QoE configuration and reporting	CATT
R3-220964	Further consideration on RVQoE configuration and reporting	ZTE, China Telecom
R3-220965	[draft] LS on the support for RAN visible QoE	ZTE
R3-221039	CB: # QoE5_RANVisible - Summary of email discussion	China Unicom - moderator
R3-221312	CB: # QoE5_RANVisible - Summary of email discussion	China Unicom - moderator
R3-221318	Support for RAN Visible QoE Measurements	Ericsson
R3-221319	Support for RAN Visible QoE Measurements	Ericsson
R3-221320	Support for Configuration and Reporting of RAN Visible QoE	Ericsson
R3-221463	Support for RAN Visible QoE Measurements	Ericsson
R3-221464	Support for RAN Visible QoE Measurements	Ericsson
R3-221465	Support for Configuration and Reporting of RAN Visible QoE	Ericsson

15.4: Alignment of Radio-Related Measurement and QoE Measurements

TDoc	Title	Source
R3-220173	(TP for QoE BL CR for TS 38.300) The Alignment of Radio-related Measurements and QoE Measurements	Ericsson
R3-220275	Alignment of Radio related measurements and QoE measurements	Qualcomm Incorporated
R3-220332	Alignment of MDT and QMC in Rel-17	Nokia, Nokia Shanghai Bell
R3-220742	Further discussion on alignment of MDT and QoE Measurements	China Unicom
R3-220913	Further discussions on alignment between QoE measurement and MDT measurement	Huawei
R3-220924	Alignment of MDT and QoE	Samsung
R3-220938	Discussion on Alignment of MDT and QoE Measurements	CATT
R3-220966	Further discussion on alignment of MDT and QoE Measurements	ZTE
R3-221040	CB: # QoE6_MDTAlignment - Summary of email discussion	Qualcomm - moderator
R3-221243	LS on Session Start and Session End Indication from the UE	Ericsson
R3-221295	(TP for BL CR of TS38.473) Alignment of MDT and QoE Measurements	ZTE
R3-221296	(TP for BL CR of TS38.463) Alignment of MDT and QoE Measurements	ZTE
R3-221297	(TP for BL CR of TS38.401) Alignment of MDT and QoE Measurements	ZTE
R3-221313	CB: # QoE6_MDTAlignment - Summary of email discussion	Qualcomm - moderator

16.1: General

TDoc	Title	Source
R3-220023	Introduction of support for eNPN	Qualcomm Incorporated
R3-220054	Support for Enhanced Non Public Networks	Nokia, Nokia Shanghai Bell, China Telecom
R3-220055	Supporting enhanced private network	Huawei
R3-220115	Reply to LS on support of PWS over SNPN	SA1
R3-220387	Work Plan for Enhancement for Private Network Support for NG-RAN WI	China Telecommunication
R3-221055	CB: # NPN1_Workplan_BLCRS - Summary of email discussion	China Telecom - moderator

16.2.1: Cell Access Control

TDoc	Title	Source
R3-220197	(TP for TS 38.300) Conclusions on onboarding open points	Nokia, Nokia Shanghai Bell
R3-220198	(TP for TS 38.413) Conclusion on onboarding open points	Nokia, Nokia Shanghai Bell
R3-220388	(TP for TS 38.473) Support for eNPN	China Telecommunication
R3-220655	(TP for NG_RAN_PRN_enh BLCR for TS 38.300) Supporting enhanced private network	Huawei
R3-220656	Supporting enhanced private network	Huawei
R3-220853	Left issues on ehanced NPN	ZTE Corporation
R3-220854	TP to TS38.300 on enhanced NPN	ZTE Corporation
R3-221056	CB: # NPN2_CellAccessControl - Summary of email discussion	Nokia - moderator
R3-221155	(TP for NG_RAN_PRN_enh BLCR for TS 38.300) Supporting enhanced private network	Huawei

17.1: General

TDoc	Title	Source
R3-220031	Support of Enhanced RAN Slicing	Nokia, Nokia Shanghai Bell
R3-220032	Supporting network slicing enhancement	Huawei
R3-220872	Revised work plan for RAN slicing	CMCC, ZTE
R3-221041	CB: # RANSlicing1_Workplan_BLCRs - Summary of email discussion	CMCC - moderator

17.2: Support Service Continuity

TDoc	Title	Source
R3-220097	Reply LS on Slice list and priority information for cell reselection	RAN2
R3-220199	(TP for TS38.300 and TS38.413) Handling of Slicing resource shortage	Nokia, Nokia Shanghai Bell
R3-220662	(TP for NR_Slice BLCR for TS 38.300) Supporting Service Continuity	Huawei
R3-220763	Discussion on Support Service Continuity	ZTE,China Telecom, China Unicom
R3-220873	Further discussion on the suport of service continuity	CMCC
R3-220925	(TP for BL CR TS 38.300) Support of Service Continuity	Samsung
R3-221042	CB: # RANSlicing2_Service_Continuity - Summary of email discussion	Nokia - moderator
R3-221115	(TP for TS38.300 and TS38.413) Handling of Slicing resource shortage	Nokia, Nokia Shanghai Bell
R3-221124	(TP for NR_Slice BLCR for TS 38.300) Supporting Service Continuity	Huawei
R3-221138	(TP for TS38.300 and TS38.413) Handling of Slicing resource shortage	Nokia, Nokia Shanghai Bell

17.3: Support the Enforcement of Slice MBR

TDoc	Title	Source
R3-220200	(TP for TS 38.413) Support for Slice Maximum Bit Rate	Nokia, Nokia Shanghai Bell
R3-220201	(TP for TS 38.473 and TS 38.463) Support of Slice Maximum Bit Rate	Nokia, Nokia Shanghai Bell
R3-220247	Support of Enhancement of RAN slicing - UE Slice MBR and Target NSSAI	NEC
R3-220438	Introduction of Target NSSAI and SMBR	Ericsson
R3-220439	LS on S-MBR and Target NSSAI	Ericsson
R3-220440	Way forward on S-MBR and Target NSSAI	Ericsson
R3-220663	(TP for NR_Slice for TS 38.413, TS 38.423, TS 38.463 and TS 38.473) Supporting network slicing enhancement	Huawei
R3-220664	(TP for NR_Slice BLCR for TS 38.300) Supporting network slicing enhancement	Huawei
R3-220725	(TP for SON BL CR for TS 38.463) SA2 impact on RAN	China Unicom
R3-220726	(TP for SON BL CR for TS 38.473) SA2 impact on RAN slicing	China Unicom
R3-220764	Impact on RAN slicing of UE slice MBR and Target NSSA	ZTE
R3-220765	(TP for SON BL CR for TS 38.413) SA2 impact on RAN slicing	ZTE
R3-220766	(TP for SON BL CR for TS 38.423) SA2 impact on RAN slicing	ZTE
R3-220811	(TP for SON BL CR for TS 37.340) SA2 impact on RAN slicing	China Telecom,ZTE
R3-220920	Consideration on Target NSSAI in Dual Connectivity	LG Electronics
R3-220926	(TP for BL CR TS 38.413) Support of Target NSSAI	Samsung
R3-220927	(CR for TS38.423) RAN slicing enhancement	Samsung
R3-220943	BLCR to 37.340 for Enhancement of RAN Slicing	CATT
R3-220944	Discussion on Supporting for UE-Slice-MBR	CATT
R3-220945	TP to 38.413 for UE-Slice-MBR	CATT
R3-220946	TP to 38.423 for UE-Slice-MBR	CATT
R3-221043	CB: # RANSlicing3_UESliceMBR - Summary of email discussion	ZTE - moderator
R3-221141	CB: # RANSlicing3_UESliceMBR - Summary of email discussion	ZTE - moderator
R3-221165	(TP for NR_Slice for TS 38.413) Supporting network slicing enhancement	Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT, Ericsson
R3-221209	(CR for TS38.423) RAN slicing enhancement	Samsung
R3-221248	(TP for SON BL CR for TS 38.473) RAN slicing enhancement	ZTE, Nokia, Nokia Shanghai Bell, Huawei, CATT,Ericsson
R3-221367	(TP for NR_Slice BLCR for TS 37.340) Supporting network slicing enhancement	CATT
R3-221388	BLCR to 38.463: Support of slicing enhancement	Ericsson, ZTE, Samsung, Nokia, Nokia Shanghai Bell, Huawei, CATT
R3-221405	(TP for TS 38.300) support of Slice MBR	Nokia, Nokia Shanghai Bel, Huaweil
R3-221418	(TP for NR_Slice for TS 38.413) Supporting network slicing enhancement	Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT, Ericsson
R3-221419	(TP for NR_Slice BLCR for TS 38.473) Supporting network slicing enhancement	ZTE, Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson
R3-221421	(BLCR to TS 38.473) Supporting network slicing enhancement	ZTE, Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson, Samsung
R3-221422	BLCR to 38.463: Support of slicing enhancement	Ericsson, ZTE, Samsung, Nokia, Nokia Shanghai Bell, Huawei, CATT
R3-221423	(TP for TS 38.300) support of Slice MBR	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, Ericsson, CATT
R3-221424	(BL CR to TS38.423) RAN slicing enhancement	Samsung, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT, Ericsson
R3-221425	(BLCR to 37.340) Enhancement of RAN Slicing	CATT, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Samsung, Ericsson

18.1: General

TDoc	Title	Source
R3-220133	LS Reply on model deployment and update from OAM to NG-RAN	SA5
R3-220407	TR37.817	China Mobile Com. Corporation
R3-220833	Consideration on AIML RAN in R17 SI	ZTE Corporation, Lenovo, Motorola Mobility, China Unicom
R3-220881	Work plan for Study on enhancement for data collection for NR and EN-DC	CMCC
R3-221014	TR37.817 v1.1.0	CMCC
R3-221057	CB: # AIRAN1_General - Summary of email discussion	CMCC - moderator

18.2: High-Level Principles and Definitions

TDoc	Title	Source
R3-220209	RAN Intelligence Framework � Further Discussion on remaining issues	Futurewei
R3-220257	Proposed resolutions to open issues on functional framework	NEC
R3-220311	(TP for BL CR for TR 37.817) Framework for RAN intelligence	Ericsson
R3-220401	Discussion on Model Performance Feedback within AI/ML-based functional framework for RAN intelligence	Deutsche Telekom AG
R3-220408	Discussion on definition of online training	PML
R3-220485	On model performance feedback from Model Inference	Lenovo, Motorola Mobility, NEC, Qualcomm, Intel Corporation, Futurewei
R3-220631	(TP for TR 37.817) Open points on AI/ML Framework and Feedback Collection Discussions	Nokia, Nokia Shanghai Bell
R3-220661	(TP for TR 37.817)Discussion on the model performance feedback arrow	CATT
R3-220771	Discussion on Functional Framework and High-Level Principles	Samsung
R3-220816	Discussion on Model Performance Feedback	China Telecom Corporation Ltd.
R3-220834	Further discussion on AI Functional Framework for RAN Intelligence	ZTE Corporation, China Unicom
R3-220878	Remaining open issues of AI framework	CMCC
R3-220914	Further discussions on framework	Huawei
R3-221058	CB: # AIRAN2_Framework - Summary of email discussion	NEC - moderator
R3-221199	TP for TR 37.817 on High-Level Principles and Definitions	NEC
R3-221221	TP for TR 37.817 on High-Level Principles and Definitions	NEC

18.4.1: Network Energy Saving

TDoc	Title	Source
R3-220265	TP for network Energy saving	Qualcomm Incorporated
R3-220312	Network Energy Saving	Ericsson
R3-220501	AI/ML based�network energy saving	Intel Corporation
R3-220520	(TP for 37.817) Discussion on Standards Impact on energy saving and load balancing	CATT
R3-220603	Network Energy Saving � Further Discussions on Solutions and Standard Impacts	Futurewei
R3-220609	Alignment of the description of the Energy Savings and the other AI/ML use cases	InterDigital
R3-220632	(TP for TR 37.817) Discussion on AI/ML Energy Saving, Load Balancing and Mobility Optimization Use Cases	Nokia, Nokia Shanghai Bell
R3-220772	Discussion on Standard Impact for AI/ML based Network Energy Saving and Load Balancing	Samsung
R3-220819	Discussion on solutions of AI-based energy saving in case of split architecture	China Telecom Corporation Ltd.
R3-220835	Further discussion on solution to AI based Network Energy Saving	ZTE Corporation, Lenovo, Motorola Mobility, China Unicom
R3-220882	Further discussion on AI based Energy Saving	CMCC
R3-220915	Furhter discussions on energy saving	Huawei
R3-221059	CB: # AIRAN3_ES - Summary of email discussion	Intel - moderator
R3-221152	TP to 37.817 on AI/ML based network energy saving	Intel Corporation
R3-221328	CB: # AIRAN3_ES - Summary of email discussion	Intel - moderator
R3-221329	TP to 37.817 on AI/ML based network energy saving	Intel Corporation
R3-221439	CB: # AIRAN3_ES - Summary of email discussion	Intel - moderator
R3-221440	TP to 37.817 on AI/ML based network energy saving	Intel Corporation

18.4.2: Load Balancing

TDoc	Title	Source
R3-220210	AI/ML-based Load Balancing: Further Discussion on remaining issues	Futurewei
R3-220258	Proposed updates to Load Balancing Solutions and Standard Impact	NEC
R3-220266	TP for load balancing	Qualcomm Incorporated
R3-220310	AI/ML Load Balancing and Mobility Optimisation use cases	Ericsson
R3-220486	Discussion on traffic load prediction	Lenovo, Motorola Mobility
R3-220502	AI/ML based load balancing	Intel Corporation
R3-220610	Alignment of the description of the load balancing and the other AI/ML use cases	InterDigital
R3-220817	Discussion on solutions of AI-based load balancing in case of split architecture	China Telecom Corporation Ltd.
R3-220845	Further discussion on solution to AI based Load Balancing	ZTE Corporation, China Unicom
R3-220916	Furhter discussions on load balancing	Huawei, China Moblie, China Unicom
R3-221060	CB: # AIRAN3_LB - Summary of email discussion	ZTE - moderator
R3-221192	TP to 37.817 on AI/ML based load balancing	ZTE
R3-221361	TP to 37.817 on AI/ML based load balancing	ZTE
R3-221435	CB: # AIRAN3_LB - Summary of email discussion	ZTE - moderator
R3-221446	TP to 37.817 on AI/ML based load balancing	ZTE

18.4.3: Mobility Optimization

TDoc	Title	Source
R3-220259	Proposed updates to Mobility Optimization Solutions and Standard Impact	NEC
R3-220267	Reduction of UE power consumption in RRM measurement	Qualcomm Incorporated
R3-220487	Collecting UE trajectory measurement from the new serving RAN node	Lenovo, Motorola Mobility
R3-220503	AI/ML based�mobility optimization	Intel Corporation
R3-220574	Discussion on definition of online training	PML
R3-220604	Mobility Optimization � Further Discussions on Solutions and Standard Impacts	Futurewei
R3-220611	Alignment of the description of the Mobility Optimization and the other AI/ML use cases	InterDigital
R3-220633	(TP for TR 37.817) Further Discussion on AI/ML Mobility Optimization Solution	Nokia, Nokia Shanghai Bell
R3-220773	Discussion on Standard Impact for AI/ML based Mobility Optimization	Samsung
R3-220789	(TP for 37.817)Discussion on Standards Impact on Mobility	CATT
R3-220847	Further discussion on solution to AI based Mobility Optimization	ZTE Corporation, China Unicom
R3-220883	Further discussion on AI based Mobility	CMCC
R3-220904	Discussion on solutions of mobility optimization	VIVO TECH GmbH
R3-220917	Furhter discussions on mobility enhancement	Huawei
R3-221061	CB: # AIRAN5_Mobility - Summary of email discussion	Samsung - moderator
R3-221179	Discussion on Standard Impact for AI/ML based Mobility Optimization	Samsung
R3-221181	TP for AI/ML based Mobility Optimization	Samsung
R3-221341	CB: # AIRAN5_Mobility - Summary of email discussion	Samsung - moderator
R3-221342	TP for AI/ML based Mobility Optimization	Samsung
R3-221394	CB: # AIRAN5_Mobility - Summary of email discussion	Samsung - moderator
R3-221395	TP for AI/ML based Mobility Optimization	Samsung
R3-221467	TP for AI/ML based Mobility Optimization	Samsung

19.1: General

TDoc	Title	Source
R3-220072	Introduction of NR Positioning enhancements to NRPPa	Ericsson
R3-220073	Introduction of NR Positioning enhancements	Huawei

19.2.1: Positioning Accuracy Improvements

TDoc	Title	Source
R3-220089	LS on ARP association with UL measurements for NR positioning	RAN1
R3-220091	LS on TRP beam/antenna information	RAN1
R3-220093	LS on the reporting of the Tx TEG association information	RAN1
R3-220351	(TP for NR_pos_enh BL CR for TS 38.455) Associating ARP location with UL measurements	Nokia, Nokia Shanghai Bell
R3-220400	[DRAFT] Reply LS on TRP Beam/Antenna Information	Ericsson LM
R3-220452	(TP for NRPPa BL CR on Positioning) Implementation of RAN1 Positioning accuracy improvement agreements and other aspects	Ericsson
R3-220453	Discussion on signalling UE TX TEG association	Ericsson
R3-220510	(TP for POS BL CR for TS 38.455 & TS 38.473 ) on Positioning enhancement	Huawei
R3-220718	(TP for Positioning BL CR) Consideration on Positioning Accuracy Improvement	CATT
R3-220788	TP to 38.455 and 38.473 on Positioning Accuracy Improvement	Huawei
R3-220950	Discussion on supporting UL positioning measurement with gNB ARP	ZTE Corporation
R3-220951	TP for TS38.455 on supporting UL positioning measurements with gNB ARP	ZTE Corporation
R3-220954	(TP for POS BL CR for TS 38.455 & TS 38.473) on Positioning enhancement - light	Huawei
R3-221062	CB: # 1901_Pos_Acc_Imp - Summary of email discussion	Ericsson - moderator
R3-221200	(TP for NRPPa BL CR on Positioning) Implementation of RAN1 Positioning accuracy improvement agreements and other aspects	Ericsson
R3-221201	Discussion on signalling UE TX TEG association	Ericsson
R3-221225	(TP for NR_pos_enh BL CR for TS 38.455) Associating ARP location with UL measurements	Nokia, Nokia Shanghai Bell
R3-221245	(TP for NR_pos_enh BL CR for TS 38.473) Associating ARP location with UL measurements	Nokia, Nokia Shanghai Bell
R3-221272	(TP for F1AP BL CR on Positioning) Implementation of RAN1 Positioning accuracy improvement agreements and other aspects	Ericsson
R3-221275	(TP for POS BL CR for TS 38.455 & TS 38.473) on Positioning enhancement - light	Huawei
R3-221352	CB: # 1901_Pos_Acc_Imp - Summary of email discussion	Ericsson - moderator
R3-221353	(TP for F1AP BL CR on Positioning) Implementation of RAN1 Positioning accuracy improvement agreements and other aspects	Ericsson
R3-221354	Discussion on signalling UE TX TEG association	Ericsson
R3-221384	(TP to NRPPa) Removal of Editor notes in Measurement Update message	Ericsson
R3-221399	Discussion on signalling UE TX TEG association	Ericsson, Huawei, CATT
R3-221400	(TP for POS BL CR for TS 38.473) on Positioning enhancement - light	Huawei, Ericsson, CATT

19.2.2: RRC_INACTIVE State Positioning

TDoc	Title	Source
R3-220373	Discussion on RRC_INACTIVE state Positioning	VIVO TECH GmbH
R3-220454	(TP for NRPPa BL CR on Positioning) Addition of LMF assistance information for RRC_Inactive positioning	Ericsson
R3-220511	(TP for POS BL CR for TS 38.455 & TS 38.473 & TS 38.423) on RRC inactive positioning	Huawei
R3-220715	(TP for Positioning BL CR 38.455) Provision of assistance information in NRPPa	CATT
R3-220716	Transfer of Positioning Context in XnAP	CATT
R3-220862	Discussion on RRC INACTIVE State Positioning	CMCC
R3-220928	Positioning in RRC inactive state	Samsung
R3-220929	(TP for BL CR TS38.423) Support of RRC Inactive positioning	Samsung
R3-220930	(TP for BL CR TS38.473) Support of RRC Inactive positioning	Samsung
R3-221063	CB: # 1902_Pos_RRC_INACTIVE - Summary of email discussion	Samsung - moderator
R3-221193	(TP for NRPPa BL CR on Positioning) Addition of LMF assistance information for RRC_Inactive positioning	Ericsson
R3-221280	(TP for POS BL CR for TS 38.423) on RRC inactive positioning	Huawei
R3-221343	CB: # 1902_Pos_RRC_INACTIVE - Summary of email discussion	Samsung - moderator
R3-221380	(TP for POS BL CR for TS 38.423) on RRC inactive positioning	Huawei, Samsung
R3-221402	Transfer of Positioning Context in XnAP	CATT
R3-221432	(BL CR to TS 38.423) Transfer of Positioning Context in XnAP	CATT

19.2.3: On-Demand PRS Transmission and Reception

TDoc	Title	Source
R3-220352	(TP for NR_pos_enh BL CR for TS 38.455) Further details of on-demand PRS	Nokia, Nokia Shanghai Bell
R3-220512	(TP for POS BL CR for TS 38.455 & TS 38.473) on on-demand PRS	Huawei
R3-220549	Introduction of release 17 positioning enhancements	Qualcomm Incorporated
R3-220719	(TP for Positioning BL CR 38.455) Further Consideration on on-demand PRS	CATT
R3-221064	CB: # 1903_Pos_OnDemandPRS - Summary of email discussion	Huawei - moderator
R3-221222	(TP for POS BL CR for TS 38.455 & TS 38.473) on on-demand PRS	Huawei
R3-221226	(TP for NR_pos_enh BL CR for TS 38.455) Further details of on-demand PRS	Nokia, Nokia Shanghai Bell
R3-221372	(TP for NR_pos_enh BL CR for TS 38.455) Further details of on-demand PRS	Nokia, Nokia Shanghai Bell, Huawei, CATT
R3-221381	(TP for POS BL CR for TS 38.473) on on-demand PRS	Huawei, Nokia, Nokia Shanghai Bell, CATT

19.2.5: Information Reporting for Multipath and NLOS Mitigation

TDoc	Title	Source
R3-220455	(TP for NRPPa BL CR on Positioning) Discussion on support of Multipath Reporting and NLOS detection	Ericsson
R3-220524	(TP for NR_pos_enh BL CR for TS 38.455) LoS/NLoS information	Nokia, Nokia Shanghai Bell
R3-220525	(TP for NR_pos_enh BL CR for TS 38.455) Multipath reporting enhancements	Nokia, Nokia Shanghai Bell
R3-220955	(TP for POS BL CR for TS 38.455 & TS 38.473) on NLOS Mitigation\nAnd the Multipath Reporting	Huawei
R3-221065	CB: # 1904_Pos_Multipath_NLOS - Summary of email discussion	Nokia - moderator
R3-221227	(TP for NR_pos_enh BL CR for TS 38.455) LoS/NLoS information	Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT
R3-221246	(TP for NR_pos_enh BL CR for TS 38.473) LoS/NLoS information	Nokia, Nokia Shanghai Bell
R3-221373	(TP for NR_pos_enh BL CR for TS 38.473) LoS/NLoS information	Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT

19.3: Support for Latency Improvement

TDoc	Title	Source
R3-220090	LS on latency improvement for PRS measurement with MG	RAN1
R3-220092	LS on PRS processing window	RAN1
R3-220354	(TP for NR_pos_enh BL CR for TS 38.455) Latency reduction related to measurement gap	Nokia, Nokia Shanghai Bell
R3-220456	(TP for NRPPa BL CR on Positioning) Support of latency improvement for PRS measurement with MG	Ericsson
R3-220513	(TP for POS BL CR for TS 38.455, TS 38.473) on Latency improvement in positioning	Huawei
R3-220717	(TP for Positioning BL CR) Latency Improvement for PRS Measurement	CATT
R3-220806	[Draft] Reply LS on latency improvement for PRS measurement with MG	Huawei
R3-220807	[DRAFT] Reply LS on PRS processing window	Huawei
R3-220952	Discussion on latency improvement with MG	ZTE Corporation
R3-221066	CB: # 1905_Pos_LatencyImprovement - Summary of email discussion	CATT - moderator
R3-221254	[DRAFT] Reply LS on latency improvement in NR positioning	CATT
R3-221345	(TP for NR_pos_enh BL CR for TS 38.455) Latency improvement in positioning	Huawei
R3-221355	(TP for NR_pos_enh BL CR for TS 38.473) Latency improvement in positioning	Ericsson
R3-221385	CB: # 1905_Pos_LatencyImprovement - Summary of email discussion	CATT - moderator
R3-221403	(TP for NR_pos_enh BL CR for TS 38.455) Latency improvement in positioning	Huawei, Ericsson
R3-221404	(TP for NR_pos_enh BL CR for TS 38.473) Latency improvement in positioning	Ericsson, Huawei

20.1: General

TDoc	Title	Source
R3-220010	Clarification of NAS Node Selection Function for NTN nodes providing access over multiple countries	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, Thales
R3-220011	Support of NTN RAT identification and NTN RAT restrictions	Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT
R3-220029	Support of NTN RAT identification and NTN RAT restrictions	Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT
R3-220071	Support Non-Terrestrial Networks	Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated
R3-220108	Reply LS on UE location aspects in NTN	RAN2
R3-220112	Reply LS on extended NAS supervision timers at satellite access	RAN2
R3-220125	Reply LS on NTN specific User Consent	SA3
R3-220126	Reply LS on UE location aspects in NTN	SA3
R3-220127	Reply LS on UE location aspects in NTN	SA3
R3-220465	Clean-up definition and abbreviation	Huawei
R3-220998	Updated NR-NTN-solutions work plan	THALES
R3-221067	CB: # 2001_NTN_General - Summary of email discussion	Thales - moderator
R3-221266	CB: # 2001_NTN_General - Summary of email discussion	Thales - moderator
R3-221477	Support Non-Terrestrial Networks	Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated

20.2.1: Network Identifier Handling

TDoc	Title	Source
R3-220121	LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access	SA2
R3-220283	(TP for TS38.413 BL CR on NTN) Handling TA reporting in ULI	Qualcomm Incorporated
R3-220284	[DRAFT] Reply LS on LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access (R3-220121/S2-2109337)	Qualcomm Incorporated
R3-220394	Multi TAC handling and reporting in NTN	China Telecommunication
R3-220466	Further discuss on multiple TAC issues	Huawei
R3-220629	TAC Reporting in ULI for NTN	Ericsson LM
R3-220713	(TP for NTN BL CR 38.413) TAI reporting in ULI	CATT
R3-220826	(TP for BL CR for TS 38.300) mapped cell ID determination after AS security and TAC reporting	Nokia, Nokia Shanghai Bell
R3-220827	(TP for BL CR for TS 38.413) TAC reporting for support multiple TAC broadcast over the air	Nokia, Nokia Shanghai Bell
R3-220895	(TP for BL CR 38.413) TAC Reporting in ULI for NTN	ZTE
R3-221068	CB: # 2002_NTN_NWID - Summary of email discussion	Qualcomm - moderator
R3-221257	(TP for BL CR for TS 38.300) mapped cell ID determination after AS security and TAC reporting	Nokia, Nokia Shanghai Bell
R3-221293	(TP for BL CR for TS 38.300) mapped cell ID determination after AS security and TAC reporting	Nokia, Nokia Shanghai Bell
R3-221357	LS on UE location during initial access in NTN	RAN2
R3-221362	TAC Reporting in ULI for NTN	Ericsson LM
R3-221370	Reply LS on LS on TAC reporting in ULI and support of Sas and Fas for NR Satellite Access (R3-220121/S2-2109337)	Qualcomm Incorporated

20.2.5: Aspects Related to Country-Specific Routing

TDoc	Title	Source
R3-220285	(TP for BL CR for 38.300) Final aspects of country border crossing	Qualcomm Incorporated
R3-220464	New paging cause for UE Context Release Request	Huawei
R3-220628	Country Routing and Cause Value for UE Context Release	Ericsson LM
R3-220714	(TP for NTN BL CR 38.413) On Cause Value for Cross-country Scenario	CATT
R3-220860	Discussion on Country-Specific Routing	CMCC
R3-220896	(TP for BL CR 38.413) Country-specific Routing for NTN	ZTE
R3-221069	CB: # 2003_NTN_Country_Routing - Summary of email discussion	CATT - moderator
R3-221263	(TP for NTN BL CR 38.413) On Cause Value for Cross-country Scenario	CATT, CMCC
R3-221264	Country Routing and Cause Value for UE Context Release	Ericsson LM
R3-221265	[DRAFT] LS on RAN Initiated Release due to out-of-PLMN area condition	Qualcomm Incorporated
R3-221298	Country Routing and Cause Value for UE Context Release	Ericsson LM
R3-221299	(TP for NTN BL CR 38.413) On Cause Value for Cross-country Scenario	CATT, CMCC, ZTE
R3-221324	[DRAFT] LS on RAN Initiated Release due to out-of-PLMN area condition	Qualcomm Incorporated
R3-221379	LS on RAN Initiated Release due to out-of-PLMN area condition	Qualcomm Incorporated

21.1: General

TDoc	Title	Source
R3-220065	Introduction of Enhanced IIoT support over NG	CATT, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Ericsson, ZTE
R3-220066	Introduction of Enhanced IIoT support over Xn	Ericsson, Samsung, Huawei, ZTE,CATT, Nokia, Nokia Shanghai Bell
R3-220067	Introduction of Enhanced IIoT support over E1	ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson
R3-220068	Introduction of Enhanced IIoT support over F1	Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Samsung
R3-220939	TP for BLCR for 38.413 ASN.1 added	CATT
R3-221070	CB: # NRIIOT1_BL CRs - Summary of email discussion	Huawei - moderator

21.2: Support for Propagation Delay Compensation Enhancements

TDoc	Title	Source
R3-220227	Remaining issues on Time Synchronization enhancements	ZTE
R3-220228	(TP for Introduction of Enhanced IIoT support over F1) Time Synchronization enhancements	ZTE
R3-220337	Discussion on Further enhanced NR-IIoT: Enhancements for support of time synchronization	Ericsson
R3-220338	Enhancements for support of time synchronization	Ericsson
R3-220367	(TP for NR_IIOT_URLLC_enh BL CR for TS 38.473) Time synchronization open issues	Nokia, Nokia Shanghai Bell
R3-220368	(TP for NR_IIOT_URLLC_enh BL CR for TS 38.423) Time synchronization and handover	Nokia, Nokia Shanghai Bell
R3-220616	Discussion on PDC TA based and E-CID measurement	Ericsson
R3-220646	(TP for NR_IIOT_URLLC_enh BL CR for TS 38.473) Discussion on supporting the network pre-compensated PDC	Samsung
R3-220647	(TP for NR_IIOT_URLLC_enh BL CR for TS 38.470) Supporting the network pre-compensated PDC	Samsung
R3-220648	(TP for NR_IIOT_URLLC_enh BL CR for TS 38.473) Discussion on the time synchronization error budget over F1AP	Samsung
R3-220652	(TP for eIIOT BLCR for TS 38.473) Supporting propagation delay compensation enhancements	Huawei
R3-220653	(TP for eIIOT BLCR for TS 38.423) Supporting propagation delay compensation enhancements	Huawei
R3-220940	Discussion on Propagation Delay Compensation Enhancements	CATT
R3-220941	TP for BLCR for 38.473 on Propagation Delay Compensation Enhancements	CATT
R3-221071	CB: # NRIIOT2_PDC - Summary of email discussion	Nokia - moderator
R3-221112	CB: # NRIIOT2_PDC - Summary of email discussion	Nokia - moderator
R3-221220	(TP for NR_IIOT_URLLC_enh BL CR for TS 38.413) Resolution of FFS in Path Switch Request Acknowledge	Nokia, Nokia Shanghai Bell
R3-221374	(TP for NR_IIOT_URLLC_enh BL CR for TS 38.413) Removal of FFS from Path Switch Request Ack	Nokia, Nokia Shanghai Bell

21.3: Enhancements Based on New QoS Related Parameters

TDoc	Title	Source
R3-220229	(TP for Introduction of Enhanced IIoT support over Xn and F1) Analysis of New QoS Related parameters	ZTE
R3-220370	(TP for NR_IIOT_URLLC_enh BL CR for TS 38.423) Survival Time and handover	Nokia, Nokia Shanghai Bell
R3-220654	(TP for eIIOT BLCR for TS 38.423 and 38.425) Survival time remaining issues	Huawei
R3-220942	Discussion on new QoS related parameters	CATT
R3-221072	CB: # NRIIOT2_NewQoS - Summary of email discussion	ZTE - moderator
R3-221113	CB: # NRIIOT2_NewQoS - Summary of email discussion	ZTE - moderator

22.1: General

TDoc	Title	Source
R3-220004	Introduction of MBS(BL CR for 38.463)	CATT
R3-220005	Introduction of NR MBS	Lenovo, Motorola mobility
R3-220008	Introduction of NR MBS	Samsung
R3-220009	Introduction of NR MBS	LG Electronics
R3-220026	Introduction of NR MBS	Huawei, CMCC
R3-220027	BL CR for NR MBS for 38.413	Qualcomm
R3-220028	Introduction of NR Multicast and Broadcast Services	Ericsson
R3-220030	BL CR to TS38.420	CMCC
R3-220069	Introduction of NR MBS	Nokia, Nokia Shanghai Bell
R3-220070	MBS BL CR for TS38.410	ZTE
R3-220118	Reply LS on maximum number of MBS sessions that can be associated to a PDU session	SA2
R3-220119	LS on MBS broadcast service continuity and MBS session identification	SA2
R3-220136	Further reply on MBS broadcast service continuity	RAN2
R3-220202	Rapporteur update of NR MBS	Nokia, Nokia Shanghai Bell
R3-221073	CB: # MBS1_General	LG Electronics - moderator
R3-221154	Rapporteur update of NR MBS	Nokia, Nokia Shanghai Bell
R3-221164	Rapporteur update of NR MBS	Nokia, Nokia Shanghai Bell

22.2.2: Session Management over NG

TDoc	Title	Source
R3-220353	(TP for 38.413) Stage 3 for Broadcast Session	Nokia, Nokia Shnaghai Bell, Huawei
R3-220355	(TP for 38.413) Stage 3 for MBS Context and UE MBS Context	Nokia, Nokia Shanghai Bell
R3-220356	(TP for 38.413) Stage 3 for User Plane Shared Delivery Tunnel	Nokia, Nokia Shanghai Bell
R3-220488	(TP to TS 38.460 BL CR) Support of Shared NG-U Distribution Setup and Release	Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated
R3-220489	(TP to TS 38.463 BL CR) Support of Shared NG-U Distribution Setup and Release	Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated
R3-220545	TP for 38.413 on session management for broadcast service	CATT
R3-220546	TP for 38.410 on session management for multicast service	CATT
R3-220547	TP for 38.413 on session management for multicast service	CATT
R3-220593	[TP for BL CR38.401] Last exit: �Point to multipoint� - or: �one for all� taken seriously	Ericsson
R3-220594	[TP for BL CR 38.413, 38.423] on Session Management for NR MBS	Ericsson
R3-220692	(TP to TS 38.413 BL CR) Shared NG-U tunnel establishment and release	Huawei, CBN, China Unicom, China Telecom, Lenovo, Motorola Mobility, Qualcomm Incorporated
R3-220693	(TPs to TS 38.410, 38.413 BL CRs) Multicast Session Activation Deactivation and Update	Huawei, CBN, China Unicom, China Telecom, Lenovo, Motorola Mobility
R3-220694	(TPs to TS 38.300, 38.410, 38. 413 BL CRs) Multicast Admission Control	Huawei, CBN
R3-220695	(TP to TS 38.413 BL CR) MBS information in PDU Session Management procedures	Huawei, CBN, China Unicom, China Telecom
R3-220696	(TPs to TS 38.410, 38.413 BL CRs) Reset of Broadcast Sessions over NG interface	Huawei
R3-220731	( TP for TS 38.300) Management of multicast session	ZTE Corporation
R3-220732	(TP for TS 38.413) Management of multicast session	ZTE Corporation
R3-220856	MBS Session management over NG for multicast	CMCC
R3-220884	(TP to TS 38.300) MBS session management over NG	CMCC, Huawei
R3-221074	CB: # MBS2_SessMgmt - Summary of email discussion	Huawei - moderator
R3-221166	(TP for 38.413) Stage 3 for Broadcast Session	Nokia, Nokia Shnaghai Bell, Huawei
R3-221167	(TP to TS 38.413 BL CR) Support of Multicast Session Management	Huawei, CBN, China Unicom, China Telecom, Lenovo, Motorola Mobility, Qualcomm Incorporated, Samsung
R3-221168	[TP for BL CR38.401] Last exit: �Point to multipoint� - or: �one for all� taken seriously	Ericsson
R3-221169	TP for 38.410 on session management for multicast service	CATT
R3-221170	(TP for TS 38.300) Management of multicast session	ZTE Corporation
R3-221171	LS on MBS Session Management aspects	Huawei
R3-221172	CB: # MBS2_SessMgmt - Summary of email discussion	Huawei - moderator
R3-221304	Draft LS on Associated PDU Sessions with deactivated UP connection	Ericsson
R3-221459	CB: # MBS2_SessMgmt - Summary of email discussion	Huawei - moderator
R3-221468	LS on MBS Session Management aspects	Huawei

22.2.3: Dynamic Change Between PTP and PTM for UEs in RRC_CONNECTED State

TDoc	Title	Source
R3-220250	PTM to PTP switching	NEC

22.2.4: Bearer Management over F1/E1

TDoc	Title	Source
R3-220251	MBS Session Management at F1E1 interface	NEC
R3-220269	F1-U tunnel for MRB retransmission	Qualcomm Incorporated
R3-220357	(TP for 38.401) UE associated vs non-UE associated over F1	Nokia, Nokia Shanghai Bell
R3-220490	MCCH related encoding over F1 interface	Lenovo, Motorola Mobility
R3-220491	(TP to TS 38.425 BL CR) Remaining issues on Flow control and F1-U tunnel	Lenovo, Motorola Mobility
R3-220534	TP for 38.463 on MBS Bearer Management at E1 interface	CATT
R3-220595	On Bearer Management over E1/F1	Ericsson
R3-220596	[TP for E1AP and F1AP BL CR] On Bearer Management over E1/F1	Ericsson
R3-220697	(TPs to TS 38.401 38.470, 38.460 BL CRs) Bearer management over F1 and E1 for Broadcast	Huawei, Nokia, Nokia Shanghai Bell, CBN, China Unicom, China Telecom
R3-220698	(TP to TS 38.473 BL CR) F1AP Bearer Management for Broadcast	Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CBN
R3-220699	(TPs to TS 38.470, 38.473 BL CRs) Reset of Broadcast Context over F1 interface	Huawei
R3-220700	(TPs to TS 38.401, 470, 460 BL CRs) Bearer Management for Multicast	Huawei, Lenovo, Motorola Mobility
R3-220701	(TP to TS 38.425 BL CR) Flow Control for MBS	Huawei, CBN, China Unicom, China Telecom
R3-220790	(TP for TS 38.473 BL): Introduction of session management for broadcast	Samsung
R3-220791	(TP for TS 38.463 BL): Introduction of session management for broadcast	Samsung
R3-220792	(TP for TS38.425): Discussion on flow control for MBS	Samsung
R3-220857	Discussion on flow control for MBS	CMCC
R3-220947	(TP to BL CR for TS 38.425 BL CR) Bearer management for NR MBS	ZTE
R3-221075	CB: # MBS3_BearerMgmt - Summary of email discussion	Ericsson - moderator
R3-221194	CB: # MBS3_BearerMgmt - Summary of email discussion	Ericsson - moderator
R3-221306	Draft LS on NR RRC to support split NR-RAN architecture for NR MBS	Ericsson
R3-221339	(TP to TS 38.473 BL CR) F1AP Bearer Management for Broadcast	Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CBN
R3-221469	LS on NR RRC to support split NR-RAN architecture for NR MBS	Ericsson

22.2.5: Multicast Group Paging

TDoc	Title	Source
R3-220223	(TP for BL CR for 38.413) Multicast group paging	ZTE, Qualcomm Incorporated, Samsung, Huawei, Lenovo, Nokia, Nokia Shanghai Bell
R3-220224	[Draft]Reply LS on paging for multicast session activation notification	ZTE
R3-220358	(TP for 38.413) Further Stage 3 for MBS Group Paging	Nokia, Nokia Shanghai Bell
R3-220492	(TP to TS 38.423 BL CR) RAN Multicast Group Paging	Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated, Samsung, ZTE, Nokia, Nokia Shanghai Bell, LG Electronics
R3-220597	On Multicast Group Paging	Ericsson
R3-220708	Discussion on multicast group paging	LG Electronics
R3-220710	(TP for NR_MBS BL CR for TS 38.470) Discussion on multicast group paging	LG Electronics, Samsung, Qualcomm Incorporated, ZTE, Huawei, Lenovo, Nokia, Nokia Shanghai Bell
R3-220793	(TP for BL CR for 38.473) Multicast Group Paging procedure in F1	Samsung, Qualcomm Incorporated, ZTE, Huawei, Lenovo, Nokia, Nokia Shanghai Bell
R3-220794	Discussion on paging for multicast session activation notification	Samsung
R3-220795	[Draft] Reply LS on paging for multicast session activation notification	Samsung
R3-221076	CB: # MBS4_GroupPaging - Summary of email discussion	Samsung - moderator
R3-221175	(TP for BL CR for 38.473) Multicast Group Paging procedure in F1	Samsung, Qualcomm Incorporated, ZTE, Huawei, Lenovo, Nokia, Nokia Shanghai Bell
R3-221176	[Draft] Reply LS on paging for multicast session activation notification	Samsung
R3-221330	(TP to TS 38.423 BL CR) RAN Multicast Group Paging	Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated, Samsung, ZTE, Nokia, Nokia Shanghai Bell, LG Electronics
R3-221331	CB: # MBS4_GroupPaging - Summary of email discussion	Samsung - moderator
R3-221392	(TP for BL CR for 38.413) Multicast group paging	ZTE, Qualcomm Incorporated, Samsung, Huawei, Lenovo, Nokia, Nokia Shanghai Bell
R3-221430	Reply LS on paging for multicast session activation notification	Samsung
R3-221431	CB: # MBS4_GroupPaging - Summary of email discussion	Samsung - moderator
R3-221470	Reply LS on paging for multicast session activation notification	Samsung

22.2.6: Others

TDoc	Title	Source
R3-220493	Remaining Issues on MBS Service Area Management	Lenovo, Motorola Mobility
R3-220702	(TP to TS 38.300 BL CR) Support of Local MBS	Huawei, CBN, China Unicom
R3-221077	CB: # MBS5_Others - Summary of email discussion	Lenovo - moderator
R3-221348	CB: # MBS5_Others - Summary of email discussion	Lenovo - moderator

22.3.1: Mobility Between MBS Supporting Nodes

TDoc	Title	Source
R3-220268	Data forwarding in handover between suppporting nodes	Qualcomm Incorporated
R3-220359	(TP for 38.415 for TS 38.423 and for TS 38.300) Mobility between MBS Supporting Nodes	Nokia, Nokia Shanghai Bell
R3-220432	Consideration on MBS latest progress and outstanding issues in SA WG2	Huawei
R3-220433	[Draft] Reply LS on latest progress and outstanding issues in SA WG2	Huawei
R3-220494	On handover between MBS supporting nodes - Alt.1	Lenovo, Motorola Mobility
R3-220495	(TP to TS 38.415 BL CR) Support of MBS Sequence number in PDU Session User Plane Protocol	Lenovo, Motorola Mobility
R3-220532	Supporting lossless handover while retaining flexible MRB mapping	CATT
R3-220533	[Draft] Reply LS on latest progress and outstanding issues in SA WG2	CATT
R3-220598	More on mobility between gNBs supporting NR MBS	Ericsson
R3-220599	[TP for BL CR 38.401, 38.463, 38.413] to support mobility between gNBs supporting NR MBS	Ericsson
R3-220703	(TP to TS38.300 BL CR) Consideration on DL PDCP Synchronization in Alt1	Huawei, CBN, China Unicom, China Telecom
R3-220704	(Stage 2 TPs to TS 38.300, TS38.401 BL CRs) Mobility between MBS supporting nodes	Huawei, CBN, China Unicom, China Telecom
R3-220705	(TP to TS 38.415 BL CR) Support of NR MBS data transmission	Huawei, CBN, China Unicom, China Telecom
R3-220730	Discussion on Reply LS on SA2 latest progress and outstanding issues	ZTE Corporation
R3-220796	(TP to TS38.423 BL): Data forwarding for mobility between MBS supporting nodes	Samsung
R3-220818	(Stage 3 TP to TS 38.423 BL CR) Mobility between MBS supporting nodes	Huawei, CBN, China Unicom, China Telecom
R3-220858	Discussion on mobility with service continuity	CMCC
R3-220948	(TP to BL CR for TS 38.300, 38.463) Mobility between MBS Supporting Nodes	ZTE
R3-221078	CB: # MBS6_MobilitySupporting - Summary of email discussion	ZTE - moderator
R3-221185	CB: # MBS6_MobilitySupporting - Summary of email discussion	ZTE - moderator
R3-221408	[DRAFT] LS on support of mobility between gNBs supporting NR MBS	Ericsson
R3-221433	CB: # MBS6_MobilitySupporting - Summary of email discussion	ZTE - moderator

22.3.2: Mobility Between MBS Supporting and non-MBS Supporting Nodes

TDoc	Title	Source
R3-220123	Reply LS on Feedback on data forwarding solutions for MBS	SA2
R3-220360	(TP for 38.300) Minimizing Data Loss for mobility from non-MBS supporting NG-RAN nodes	Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R3-220361	Response LS on Feedback on data forwarding solutions for MBS	Nokia, Nokia Shanghai Bell
R3-220706	(TP to TS 38.300 BL CR) Mobility between MBS supporting and non-supporting nodes	Huawei, CBN, China Unicom, China Telecom, Lenovo, Motorola Mobility
R3-220729	( TP for BL CR for 38.300) Mobility between MBS Supporting and non-MBS Supporting Nodes	ZTE Corporation
R3-220859	Discussion on Mobility between non-MBS supporting node and MBS supporting node	CMCC
R3-221079	CB: # MBS7_MobilityNonSupporting - Summary of email discussion	Nokia - moderator
R3-221151	Response LS on Feedback on data forwarding solutions for MBS	Nokia, Nokia Shanghai Bell
R3-221157	Reply LS to SA2 on data forwarding solutions for MBS	ZTE
R3-221239	Response LS on Feedback on data forwarding solutions for MBS	Nokia, Nokia Shanghai Bell

22.4: Others

TDoc	Title	Source
R3-220362	(TP for 38.300) Stage 2 for Broadcast Service Continuity	Nokia, Nokia Shanghai Bell
R3-220535	Further Consideration on MBS broadcast service continuity	CATT
R3-220600	Robustness and interoperability considerations	Ericsson
R3-220707	(TP to TS 38.300 BL CR) Broadcast service continuity	Huawei, CBN, China Unicom, China Telecom
R3-220949	MBS IDs over XnAP	ZTE
R3-221080	CB: # MBS8_BroadcastService - Summary of email discussion	CATT - moderator
R3-221238	(TP for 38.300) Stage 2 for Broadcast Service Continuity	Nokia, Nokia Shanghai Bell
R3-221301	(TP for 38.473) Support of Broadcast Service Continuity	CATT, CBN
R3-221302	LS on MBS Service Area Identity and start procedure for broadcast service	CATT
R3-221332	CB: # MBS8_BroadcastService - Summary of email discussion	CATT - moderator
R3-221349	TP to 38.423 on MBS service area identity	ZTE
R3-221386	(TP for 38.473) Support of Broadcast Service Continuity	CATT, CBN
R3-221387	CB: # MBS8_BroadcastService - Summary of email discussion	CATT - moderator
R3-221476	TP to 38.423 on MBS service area identity	ZTE

23.1: General

TDoc	Title	Source
R3-220863	Updated Work planning for R17 Sidelink Relay WI	CMCC, OPPO

23.2: Specification of Relay and Remote UE authorization

TDoc	Title	Source
R3-220137	Reply LS on discovery and relay (re)selection	RAN2
R3-220238	Discussion on Authorisation for 5G ProSe Layer-3 Remote UE	CATT
R3-220239	Reply LS for authorisation information for 5G ProSe Layer-3 Remote UE	CATT
R3-220240	Support of NR ProSe Authorized for F1AP	CATT
R3-220241	Support of NR ProSe Authorized for XnAP	CATT
R3-220322	Introduction of ProSe authorization information	Huawei
R3-220323	(TP for SLrelay BLCR for 38.413, 38.423) Introduction of ProSe authorization information	Huawei
R3-220324	[draft] Reply LS on discovery and relay (re)selection	Huawei
R3-220340	Introduction of service authorization for SL Relay over NG	Ericsson
R3-220341	Introduction of service authorization for SL Relay over Xn	Ericsson
R3-220349	Authorization for Relay and Remote UE	Ericsson
R3-220374	Discussion on NR ProSe authorization	ZTE
R3-220395	Discussion on UE authorization for SL Relay	China Telecommunication
R3-220418	Discussion on Authorisation for 5G ProSe Layer-3 Remote UE	CATT
R3-220419	Reply LS for authorisation information for 5G ProSe Layer-3 Remote UE is needed by NG-RAN	CATT
R3-220420	Support of NR ProSe Authorized for F1AP	CATT
R3-220421	Support of NR ProSe Authorized for XnAP	CATT
R3-220457	Support of NR ProSe Authorized for NGAP	CATT
R3-220829	Discussion on Relay and Remote UE authorization	Nokia, Nokia Shanghai Bell
R3-220830	(NGAP CR) support for NR Sidelink Relay	Nokia, Nokia Shanghai Bell
R3-220831	(XnAP CR) support for NR Sidelink Relay	Nokia, Nokia Shanghai Bell
R3-220832	(F1AP CR) support for NR Sidelink Relay	Nokia, Nokia Shanghai Bell
R3-220864	Consideration on authorization for SL relay	CMCC
R3-220865	Support of 5G ProSe Authorization for NG-AP	CMCC
R3-220866	Support of 5G ProSe Authorization for Xn-AP	CMCC
R3-221081	CB: # SLRelay1_Authorization - Summary of email discussion	CMCC - moderator
R3-221088	Support of NR ProSe Authorized for XnAP	CATT
R3-221158	Introduction of ProSe authorization information	Huawei
R3-221160	CB: # SLRelay1_Authorization - Summary of email discussion	CMCC - moderator
R3-221184	Support of 5G ProSe Authorization for NG-AP	CMCC
R3-221202	Reply LS for authorisation information for 5G ProSe Layer-3 Remote UE	CATT
R3-221241	Introduction of Sidelink Relay over Xn	Ericsson

23.3: Specification of Control Plane procedures

TDoc	Title	Source
R3-220237	Discussion on the Open Issues of Control Plane Procedures	CATT
R3-220276	Control Plane procedures for U2N L2 relays	Qualcomm Incorporated
R3-220325	(TP for SLrelay BLCR for 38.473) Support of Uu adaptation layer for U2N relay	Huawei
R3-220350	Network signaling for NR SL Relay	Ericsson
R3-220375	Discussion on SL relay architecture and RRC connection management of remote UE	ZTE
R3-220376	Discussion on F1 signalling design for the PC5&Uu RLC channel and bearer mapping configuration	ZTE
R3-220377	(F1AP CR) Support of NR SL relay	ZTE
R3-220396	Discussion on control plane procedures for SL Relay	China Telecommunication
R3-220417	Discussion on the Open Issues of Control Plane Procedures	CATT
R3-220496	(TP for TS 38.401) Control plane issues on SL relay	Lenovo, Motorola Mobility
R3-220569	(TP to TS38.473 on sidelink relay) Discussion on open issues for sidelink relay	Samsung
R3-220570	CR to TS38.401 on Rel-17 Sidelink Relay	Samsung
R3-220867	Discussion on CP issue for SL relay	CMCC
R3-221082	CB: # SLRelay2_ControlPlane - Summary of email discussion	Samsung - moderator
R3-221159	CB: # SLRelay2_ControlPlane - Summary of email discussion	Samsung - moderator
R3-221161	(TP for SLrelay BLCR for 38.473) Support of Uu adaptation layer for U2N relay	Huawei
R3-221163	BL CR to TS38.401 on Rel-17 sidelink relay	Samsung
R3-221340	LS on mapping configuration of sidelink relay	Samsung
R3-221411	LS on mapping configuration of sidelink relay	Samsung
R3-221412	(TP for SL relay BLCR for 38.473) Support of Uu adaptation layer for U2N relay	Huawei

24.1: General

TDoc	Title	Source
R3-220033	CG-SDT BLCR to TS 38.473	Samsung
R3-220076	RA-SDT BLCR to TS 38.300	ZTE
R3-220077	RA-SDT BLCR to TS 38.401	Intel Corporation
R3-220078	RA-SDT BLCR to TS 38.423	Ericsson
R3-220079	Support of RACH based SDT	Nokia, Nokia Shanghai Bell
R3-221083	CB: # SDT2_RACHbased - Summary of email discussion	ZTE - moderator

24.2: Support of Context Fetch and Data Forwarding

TDoc	Title	Source
R3-220203	(TP for TS 38.423) Support of RACH-based SDT	Nokia, Nokia Shanghai Bell
R3-220204	(TP for TS 38.473) Support of RACH-based SDT	Nokia, Nokia Shanghai Bell
R3-220214	(TP for RA-SDT BLCR to TS 38.300) Overall procedure for RA-SDT without anchor relocation case	ZTE, Samsung, Ericsson, Lenovo, China Telecom, CATT, Qualcomm Incorporated
R3-220215	(TP for RA-SDT BLCR to TS 38.423) Support of RA-SDT	ZTE, China Telecom
R3-220218	(TP for RA-SDT BLCR to TS 38.463) Support of SDT	ZTE
R3-220248	RACH based SDT discussion	NEC
R3-220347	Further discussion on RACH-based SDT	Ericsson
R3-220348	(TP for RA-SDT BLCR to TS 38.423) Support of RACH-based SDT	Ericsson
R3-220424	(TPs to RA-SDT BL CRs of TS 38.300, 38.420) RACH based SDT without anchor relocation	Huawei
R3-220425	(TPs to RA-SDT BL CRs of TS 38.423, 38.425) RACH based SDT without anchor relocation	Huawei
R3-220497	On RACH based SDT	Lenovo, Motorola Mobility
R3-220550	Discussion on support of RA-SDT	LG Electronics
R3-220551	(TP for RA-SDT BL CR for TS 38.423) Support of RA-SDT	LG Electronics
R3-220568	(TP to RA-SDT BL CR of TS38.473) Discussion on SDT bearer awareness and SDT configurations	Samsung
R3-220612	Handling of first UL data in RA-SDT without anchor relocation	Qualcomm Incorporated
R3-220720	Discussion on open issues of RA-SDT without anchor relocation	CATT
R3-220721	Draft LS on define a RRC container for SDT related RLC bearer config	CATT
R3-220839	(TP for RA-SDT BL CR for TS 38.423) Discussion on RACH based SDT	Intel Corporation
R3-220840	(TP for RA-SDT BL CR for TS 38.423) Assistance Information from New gNB for RACH based SDT	Intel Corporation
R3-220841	(TP for RA-SDT BL CR for TS 38.300)	Intel Corporation
R3-220956	Discussion on SDT Assistance Information	Samsung
R3-221084	CB: # SDT3_CGbased - Summary of email discussion	ZTE - moderator
R3-221204	(TP for RA-SDT BLCR to TS 38.300) Overall procedure for RA-SDT without anchor relocation case	ZTE, Samsung, Ericsson, Lenovo, China Telecom, CATT, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R3-221205	(TP for RA-SDT BLCR to TS 38.423) Support of RACH-based SDT	Ericsson, Nokia, Nokia Shanghai Bell, Samsung
R3-221206	(TP to RA-SDT BL CR of TS38.473) Discussion on SDT bearer awareness and SDT configurations	Samsung, Nokia, Nokia Shanghai Bell
R3-221207	RA-SDT BLCR to TS 38.420	Qualcomm Incorporated
R3-221218	CB: # SDT3_CGbased - Summary of email discussion	ZTE - moderator
R3-221452	CB: # SDT3_CGbased - Summary of email discussion	ZTE - moderator

24.3: Support of CG based SDT

TDoc	Title	Source
R3-220205	Support of CG-based SDT	Nokia, Nokia Shanghai Bell
R3-220206	(TP for TS 38.473) Support of CG-based SDT	Nokia, Nokia Shanghai Bell
R3-220216	(TP for CG-SDT BLCR to TS 38.401) Overall procedure for CG-SDT	ZTE, China Telecom
R3-220217	(TP for CG-SDT BLCR to TS 38.473) Support of CG-SDT	ZTE, China Telecom
R3-220426	(TP to TS 38.401 BL CR) Support of CG-SDT	Huawei
R3-220445	Discussion on F1 impacts for supporting CG-based SDT	Ericsson
R3-220498	On CG based SDT	Lenovo, Motorola Mobility
R3-220552	(TP for CG-SDT BL CR to TS 38.463) Support of CG-SDT	LG Electronics
R3-220553	(TP for CG-SDT BL CR to TS 38.473) Support of CG-SDT	LG Electronics
R3-220567	(TP to CG-SDT BL CR of TS38.473) Discussion on CG-based small data transmission	Samsung, ZTE
R3-220602	TP to TS 38.470 BL CR: Support of CG-SDT	Ericsson LM
R3-220814	E1 impact on SDT	China Telecom Corporation Ltd.
R3-220815	TP to TS38.463 on the support of SDT in E1 interface	China Telecom Corporation Ltd.
R3-220842	(TP for CG-SDT BL CR for TS 38.473, 38.463, 38.401) Discussion on CG based SDT	Intel Corporation
R3-221215	(TP for CG-SDT BLCR to TS 38.401) Overall procedure for CG-SDT	ZTE, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, Samsung
R3-221216	TP to TS 38.470 BL CR: Support of CG-SDT	Ericsson, Nokia, Nokia Shanghai Bell, Samsung
R3-221236	Discussion on F1 impacts for supporting CG-based SDT	Ericsson, Nokia, Nokia Shanghai Bell, Samsung, LG Electronics
R3-221250	(TP for RA-SDT BLCR to TS 38.463) Support of SDT in E1 interface	China telecom, ZTE, CATT, Nokia, Nokia Shanghai Bell, Intel Corporation, LG Electronics
R3-221455	Discussion on F1 impacts for supporting CG-based SDT	Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell, Samsung, LG Electronics

24.4: Others

TDoc	Title	Source
R3-220103	LS on the ROHC continuity for SDT	RAN2
R3-220427	(TP to RA-SDT BL CR of TS 38.300) CCCH solution for UL non-SDT arrival and ROHC continuity aspects	Huawei
R3-220499	(TP to 38.300 BL CR) DL non-SDT data and signalling arrival during SDT procedure	Lenovo, Motorola Mobility
R3-220500	[Draft] LS on DL non-SDT data or signalling arrival during SDT transmission	Lenovo, Motorola Mobility
R3-220722	(TP for SDT BL CR for TS 38.300) Handling of non-SDT during SDT transmission	CATT, China Telecommunication
R3-220723	Draft LS on handling of non-SDT during SDT	CATT
R3-221085	CB: # SDT4_Others - Summary of email discussion	CATT - moderator
R3-221086	CB: # SDT1_BLCRs - Summary of email discussion	Samsung - moderator
R3-221203	Reply LS on the ROHC continuity for SDT	Huawei
R3-221217	CB: # SDT4_Others - Summary of email discussion	CATT - moderator
R3-221219	CB: # SDT1_BLCRs - Summary of email discussion	Samsung - moderator
R3-221346	(TP to 38.300 BL CR) DL non-SDT data and signalling arrival during SDT procedure	Lenovo, Motorola Mobility, CATT
R3-221347	[DRAFT] LS on handling of DL non-SDT during SDT procedure	CATT
R3-221456	CB: # SDT4_Others - Summary of email discussion	CATT - moderator
R3-221471	Reply LS on the ROHC continuity for SDT	Huawei
R3-221472	LS on handling of DL non-SDT during SDT procedure	CATT

30.1: NB-IoT and eMTC support for NTN

TDoc	Title	Source
R3-220085	Reply LS on EPS support for IoT NTN in Rel-17	CT1
R3-220122	Reply LS on EPS support for IoT NTN in Rel-17	SA2
R3-220309	NNSF for IoT NTN providing access over multiple countries	Qualcomm Technologies Int
R3-220314	NNSF for IoT NTN providing access over multiple countries	Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell
R3-220397	Proposal for IoT NTN Baseline CRs	Ericsson, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell
R3-220398	[draft] LS on IoT NTN Open Issues	Ericsson LM
R3-220399	Support of NTN RAT identification and NTN RAT restrictions	Ericsson, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R3-220409	Introduction of IoT and MTC NTN in E-UTRAN Stage 2	Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Qualcomm Inc.
R3-220436	Work Plan on NB-IoT and eMTC Support for NTN	ZTE
R3-220462	Support of NTN RAT identification and NTN RAT restrictions	Huawei, Ericsson, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R3-220469	Discussion about location report and mapping in NTN-IoT	Huawei
R3-220739	Discussion on NB-IoT and eMTC Support for NTN	CATT
R3-220740	IoT NTN CR for 36.413	CATT
R3-220741	IoT NTN CR for 36.423	CATT
R3-220828	Discussion on the mapped cell ID determination and energy saving	Nokia, Nokia Shanghai Bell
R3-220982	Discussion on NB-IoT and eMTC Support for NTN	ZTE, Samsung, Eutelsat
R3-220983	NB-IoT/eMTC support for Non-Terrestrial Networks	ZTE, CATT, Samsung
R3-220984	NAS Node Selection Function for NB-IoT/eMTC NTN nodes providing access over multiple countries	ZTE, CATT, Samsung
R3-220985	NB-IoT/eMTC NTN support of identification and restriction of satellite access for S1	ZTE, Samsung
R3-220986	NB-IoT/eMTC NTN support of identification and restriction of satellite access for X2	ZTE, Samsung
R3-221008	CB: # 16_IoToverNTN - Summary of email discussion	ZTE - moderator
R3-221093	NB-IoT/eMTC support for Non-Terrestrial Networks	ZTE, CATT, Samsung,MediaTek
R3-221145	CB: # 16_IoToverNTN - Summary of email discussion	ZTE - moderator
R3-221314	[draft] LS on opens issues for NB-IoT and eMTC support for NTN	Nokia
R3-221351	Support of NTN RAT identification and NTN RAT restrictions	Ericsson, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R3-221378	NB-IoT/eMTC support for Non-Terrestrial Networks	ZTE, CATT, Samsung, MediaTek, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated
R3-221406	LS on opens issues for NB-IoT and eMTC support for NTN	Nokia
R3-221407	IoT NTN CR for 36.423	CATT
R3-221413	Support of NTN RAT identification and NTN RAT restrictions	Ericsson, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, CATT
R3-221415	NNSF for IoT NTN providing access over multiple countries	Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT

30.2: Multi-SIM

TDoc	Title	Source
R3-220099	Reply LS on RAN2 agreements for MUSIM	RAN2
R3-220100	LS on RAN2 agreements for paging with service indication	RAN2
R3-220120	LS on Paging Cause Indication for Voice Service Supported in RRC Inactive assistance information	SA2
R3-220219	Multi-USIM BLCR to TS 36.413	ZTE, vivo
R3-220220	(TP for BLCR 38.413/38.423/38.473) Support of Multi-SIM	ZTE
R3-220363	Support for Multi-USIM devices	Nokia, Nokia Shanghai Bell
R3-220364	Support for Multi-USIM devices	Nokia, Nokia Shanghai Bell
R3-220467	Discussion of paging cause for MUSIM	Huawei
R3-220617	Paging Cause Indication for Voice Service Supported� in RRC Inactive	Ericsson
R3-220618	Support of MUSIM in XnAP	Ericsson
R3-220649	(TP for LTE_NR_MUSIM CR for TS 38.413) Discussion on supporting the paging cause for MUSIM UE	Samsung
R3-220650	(TP for LTE_NR_MUSIM BL CR for TS 38.463) Supporting the paging cause for MUSIM UE	Samsung
R3-220677	(CR to 38.473) Support for Multi-SIM devices	Huawei, vivo, CMCC
R3-220678	(CR to 38.413) Support for Multi-SIM devices	Huawei
R3-220679	(CR to 36.413) Support for Multi-SIM devices	Huawei,vivo,CMCC
R3-220680	(CR to 38.423) Support for Multi-SIM devices	Huawei,vivo,CMCC
R3-220855	(TP for NGAP, F1AP and XnAP on MUSIM) MUSIM Paging Service Indication Support	RadiSys, Reliance JIO
R3-221009	CB: # 17_MultiSIM - Summary of email discussion	Ericsson - moderator
R3-221127	Introduction of MultiSIM support over S1	ZTE, vivo, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei
R3-221128	Introduction of MultiSIM support over NG	Nokia, Nokia Shanghai Bell, Ericsson, Samsung, ZTE, Huawei, vivo
R3-221129	Introduction of MultiSIM support over Xn	Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Huawei, vivo
R3-221130	Introduction of MultiSIM support over F1	Huawei, vivo, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE
R3-221132	Introduction of MultiSIM support over E1	Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, vivo
R3-221146	CB: # 17_MultiSIM - Summary of email discussion	Ericsson - moderator

30.3: UE Power Saving Enhancements

TDoc	Title	Source
R3-220102	LS on paging subgrouping and PEI	RAN2
R3-220235	Support of paging subgrouping for UE power saving (F1AP)	CATT
R3-220236	Support of paging subgrouping for UE power saving (NGAP)	CATT
R3-220286	Addition of PEIPS Assistance Information	Qualcomm Incorporated, Ericsson
R3-220287	Addition of PEIPS Assistance Information	Qualcomm Incorporated, Ericsson
R3-220307	Addition of UE Subgrouping for paging	Ericsson, Qualcomm Incorporated
R3-220308	Addition of PEIPS Assistance Information	Ericsson, Qualcomm Incorporated
R3-220365	Support of UE Power Saving Enhancements	Nokia, Nokia Shanghai Bell
R3-220366	Support of UE Power Saving Enhancements	Nokia, Nokia Shanghai Bell
R3-220415	Support of paging subgrouping for UE power saving (F1AP)	CATT
R3-220416	Support of paging subgrouping for UE power saving (NGAP)	CATT
R3-220564	Discussion on UE power saving	Samsung
R3-220565	CR to support UE power saving over F1	Samsung
R3-220675	(TP for TS 38.413 and TS 38.473) Supporting UE Power Saving Enhancements	Huawei
R3-220676	Supporting UE Power Saving Enhancements	Huawei
R3-220767	Work plan for UE power saving enhancements WI	ZTE,MediaTek Inc.
R3-220897	Discussion on UE paging subgroup	ZTE Corporation, MediaTek
R3-220898	CR to TS38.413 for UE paging subgroup	ZTE Corporation, MediaTek, China Unicom
R3-220899	CR to TS38.473 for UE paging subgroup	ZTE Corporation, MediaTek, China Unicom
R3-220900	CR to TS38.423 for UE paging subgroup	ZTE Corporation, MediaTek
R3-221010	CB: # 18_UEPowerSaving - Summary of email discussion	ZTE - moderator
R3-221133	Support of UE Power Saving Enhancements	Nokia, Nokia Shanghai Bell
R3-221147	CB: # 18_UEPowerSaving - Summary of email discussion	ZTE - moderator
R3-221153	Addition of PEIPS Assistance Information	Ericsson, Qualcomm Incorporated
R3-221156	CR to TS38.473 for UE paging subgroup	ZTE Corporation, MediaTek, China Unicom
R3-221261	Supporting UE Power Saving Enhancements	Huawei
R3-221268	(BL CR to TS 38.410) Support for ePowerSaving	CATT
R3-221315	(BL CR to TS 38.470) Support for UE Power Saving Enhancements	Qualcomm Incorporated
R3-221428	CB: # 18_UEPowerSaving - Summary of email discussion	ZTE - moderator

30.4: UPIP Support with EN-DC

TDoc	Title	Source
R3-220128	LS on LTE User Plane Integrity Protection	SA3
R3-220288	Introduction of User Plane Integrity Protection in EPS	Qualcomm Incorporated
R3-220327	Introduction of User Plane Integrity Protection in EPS	Qualcomm Incorporated
R3-220606	Support of EPS User Plane Integrity Protection	Nokia, Nokia Shanghai Bell
R3-220619	Support for User Plane Integrity Protection support for EPC connected architectures	Ericsson, ZTE
R3-220620	EPS User Plane Integrity Protection	VODAFONE Group Plc
R3-220651	Discussion on UPIP support for EPC connected architecture	Samsung
R3-220657	Supporting EPS User Plane Integrity Protection	Huawei, Orange, CATT, ZTE
R3-220658	Supporting EPS User Plane Integrity Protection	Huawei, Orange, CATT
R3-220659	Supporting EPS User Plane Integrity Protection	Huawei, Orange, CATT
R3-220660	Supporting EPS User Plane Integrity Protection	Huawei, Orange, CATT
R3-220768	Support for User Plane Integrity Protection support for EPC connected architectures with EN-DC capable UE_E1AP	ZTE, China Telecom, Ericsson, Vodafone, Qualcomm
R3-221011	CB: # 19_EPSUPIP - Summary of email discussion	Vodafone - moderator
R3-221114	Introduction of User Plane Integrity Protection in EPS	Qualcomm Incorporated
R3-221131	Supporting EPS User Plane Integrity Protection	Huawei, Orange, CATT
R3-221144	Support for User Plane Integrity Protection support for EPC connected architectures with EN-DC capable UE_E1AP	ZTE, China Telecom, Ericsson, Vodafone, Qualcomm
R3-221148	CB: # 19_EPSUPIP - Summary of email discussion	Vodafone - moderator
R3-221316	Draft Reply LS on LTE User Plane Integrity Protection	Vodafone
R3-221350	CB: # 19_EPSUPIP - Summary of email discussion	Vodafone - moderator
R3-221434	Support for User Plane Integrity Protection support for EPC connected architectures with EN-DC capable UE_E1AP	ZTE, China Telecom, Ericsson, Vodafone, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei
R3-221447	Supporting EPS User Plane Integrity Protection	Huawei, Orange, CATT, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R3-221448	Introduction of User Plane Integrity Protection in EPS	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Vodafone, Ericsson
R3-221453	Supporting EPS User Plane Integrity Protection	Huawei, Orange, CATT, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Vodafone, Ericsson
R3-221466	Draft Reply LS on LTE User Plane Integrity Protection	Vodafone
R3-221473	Reply LS on LTE User Plane Integrity Protection	Vodafone

30.5: Others

TDoc	Title	Source
R3-220016	CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution	Ericsson
R3-220017	CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution	Ericsson, Huawei, Nokia, Nokia Shanghai Bell
R3-220018	CR to 38.462 on the introduction of new interface	Huawei, Ericsson
R3-220019	CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB	Huawei, Ericsson
R3-220043	CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution	Ericsson, Huawei, Nokia, Nokia Shanghai Bell
R3-220044	Further discussions on logical entities and corresponding definitions	Huawei, Ericsson
R3-220249	(TP for CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB) Correction ASN.1.	NEC
R3-220468	Correction on enhanced eNB architecture evolution	Huawei
R3-220634	Draft TS 37.483 (E1AP)	Ericsson
R3-220635	E1AP specification transfer to TS 37.483	Ericsson
R3-220645	(TP for Enh-eNB Arch Evol BL CR for TS 38.463) LTE CP-UP split leftovers	Ericsson
R3-220843	Transfer of Rel-17 E1 interface specification from 38.46x series to 37.48x series	Intel Corporation
R3-220844	[Draft] TS 37.481	Intel Corporation
R3-220846	Draft TS 37.480	Nokia, Nokia Shanghai Bell
R3-220852	E1 TS 38.460 specification transfer to TS 37.480	Nokia, Nokia Shanghai Bell
R3-220918	Transfer of E1 interface specification from 38-series to 37-series	Huawei
R3-220919	Draft TS 37.482	Huawei
R3-221012	CB: # 20_eNBarchEvo - Summary of email discussion	Huawei - moderator
R3-221108	E1 TS 38.460 specification transfer to TS 37.480	Nokia, Nokia Shanghai Bell
R3-221109	Transfer of E1 interface specification from 38-series to 37-series	Huawei
R3-221116	Transfer of Rel-17 E1 interface specification from 38.46x series to 37.48x series	Intel Corporation
R3-221117	Draft TS 37.481	Intel Corporation
R3-221118	E1AP specification transfer to TS 37.483	Ericsson
R3-221119	Draft TS 37.480	Nokia, Nokia Shanghai Bell
R3-221120	Draft TS 37.482	Huawei
R3-221121	Draft TS 37.483 (E1AP)	Ericsson
R3-221149	CB: # 20_eNBarchEvo - Summary of email discussion	Huawei - moderator
R3-221173	CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution	Ericsson, Huawei, Nokia, Nokia Shanghai Bell
R3-221443	Draft TS 37.480	Nokia, Nokia Shanghai Bell
R3-221449	Draft TS 37.481	Intel Corporation

31.1.2: Rapporteur Review

TDoc	Title	Source
R3-220207	Rapporteur review 38.415	Nokia, Nokia Shanghai Bell
R3-220208	Rapporteur review 38.410	Nokia, Nokia Shanghai Bell
R3-220326	Rapporteurs proposed editorial update of F1AP	Huawei
R3-220339	X2AP Rapporteur Corrections	Ericsson
R3-220371	NGAP rapporteur corrections	Nokia, Nokia Shanghai Bell
R3-220444	NRPPa Rapporteur Corrections	Ericsson
R3-220644	E1AP Rapporteur Corrections	Ericsson
R3-220820	S1AP Rapporteur Corrections	Nokia, Nokia Shanghai Bell
R3-221013	CB: # 21_RapporteurUpdates - Summary of email discussion	Ericsson - moderator
R3-221174	XnAP Rapporteur Corrections	Ericsson
R3-221229	Rapporteur review 38.410	Nokia, Nokia Shanghai Bell
R3-221344	S1AP Rapporteur Corrections	Nokia, Nokia Shanghai Bell

31.2.5: CHO with SCG configuration

TDoc	Title	Source
R3-220393	Discussion on CHO with SCG configuration	China Telecommunication

31.2.6: Others

TDoc	Title	Source
R3-220712	Clarification of DU Early Identification capability for MPS	Peraton Labs, CISA ECD, AT&T

32: Any other business

TDoc	Title	Source
R3-220441	Discussion and way forward on Flexible gNB-ID solutions	Ericsson, Bell Mobility, Telus, Verizon Wireless, China Telecom
R3-220442	LS on Flexible gNB ID	Ericsson
R3-221031	Response to R3-220441	Huawei, Qualcomm Incorporated
R3-221046	Response to R3-220441	ZTE Corporation