TDoc list

Tdoc List

2024-10-16 16:00

TDoc	Title	Source	Type	For	Agenda	Avail	Treated	Decision	Wdrn	Replaced-by	Replaces
R3‑245001	RAN3#125-bis Meeting Agenda	RAN3 Chair	agenda	Approval	3Approval of the Agenda	Yes	Yes	approved	No
R3‑245002	RAN3#125 Meeting Report	ETSI-MCC	report	Approval	4Approval of the minutes from previous meetings	Yes	Yes	approved	No
R3‑245003	Guidelines for RAN3 Meetings	RAN3 Chair, RAN3 Vice-Chairs	discussion	Endorsement	5Documents for immediate consideration	Yes	Yes	endorsed	No
R3‑245004	TR 30.531 v1.54.0 Work Plan and Working Procedures - RAN WG3	ETSI-MCC	other	Endorsement	7General, protocol principles and issues	Yes	Yes	endorsed	No
R3‑245005	Reply LS on Clarification of requirements for Ambient IoT	RAN1(Ericsson)	LS in	Discussion	16.1General	Yes	Yes	noted	No
R3‑245006	LS to RAN3 on PHY/L1 aspects of information exchange among gNBs for CLI mitigation	RAN1(Ericsson)	LS in	Discussion	19.2Support CLI Handling	Yes	No	available	No
R3‑245007	LS on security key update of inter-CU SCG LTM	RAN2(CATT)	LS in	Discussion	13.2Support for inter-CU LTM	Yes	Yes	noted	No
R3‑245008	L3 measurement based LTM support over F1	RAN2(Vodafone)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245009	LS on MHI enhancement solution for SCG deactivation/activation	RAN2(China mobile)	LS in	Discussion	10.4R18 leftovers	Yes	No	available	No
R3‑245010	Reply LS on FS_XRM Ph2	RAN2(VIVO)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245011	Reply to RAN3 LS on UL PSI based PDU discarding in NR-DC	RAN2(Qualcomm)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245012	Reply LS on SDT signalling optimization for partial context transfer	RAN2(ZTE)	LS in	Discussion	8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245013	Reply LS on Rel-18 higher-layers parameter list	RAN2(Ericsson)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245014	LS on AIML data collection	RAN(Interdigital)	LS in	Discussion	20.1General	Yes	Yes	noted	No
R3‑245015	Reply LS on Clarification of requirements for Ambient IoT	SA1(Ericsson)	LS in	Discussion	16.1General	Yes	Yes	noted	No
R3‑245016	LS Reply on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies"	SA2(Huawei)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245017	LS reply on multi-modality awareness at RAN	SA2(Huawei)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245018	LS on Clarification regarding definition of 5G NR femto ownership	SA3(Nokia)	LS in	Discussion	12.35G Femto	Yes	No	available	No
R3‑245019	LS Reply on FS_XRM_Ph2	SA4(Nokia)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245020	LS on Application-Layer FEC Awareness at RAN	SA4(Qualcomm)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245021	Reply LS on improved KPIs involving end-to-end data volume transfer time analytics	SA5(Ericsson)	LS in	Discussion	8.3Left over LSs / pending actions	Yes	YesMove to 8.3	noted	No
R3‑245022	Reply LS on MDT configuration control in NR-DC	SA5(Ericsson)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245023	LS on terminology definitions for AI-ML in NG-RAN	SA5(NEC)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245024	LS reply to IETF Traffic Engineering Architecture and Signaling Working Group on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies"	SA5(Huawei)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245025	LS on Number of UEs in RRC_INACTIVE state with data transmission	SA5(China Telecom)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245026	LS reply on AI/ML for NG-RAN Energy Saving Energy Cost index	SA5(Huawei)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245027	LS on initiation of two new Recommendations ITU-T Y.NGNe-cp_mobility: “Mobility management and control framework in NGN evolution control plane” and ITU-T Y.NGNe-cp_na: “Network attachment control framework in NGN evolution control plane”	ITU-T SG13(China Telecom)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245028	(BL CR to 36.300 for SON) Addition of SON enhancements	Lenovo	draftCR	Endorsement	10.1General	Yes	No	available	No		R3‑244851
R3‑245029	(BL CR to 36.423 for SON) Addition of SON enhancements	CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia	CR	Endorsement	10.1General	Yes	No	available	No		R3‑244852
R3‑245030	(BL CR to 38.300 for SON) Addition of SON enhancements	China Unicom, ZTE, Samsung, Nokia, Lenovo	draftCR	Endorsement	10.1General	Yes	No	available	No		R3‑244853
R3‑245031	(BL CR to 38.413 for MDT) Addition of MDT enhancements	Nokia	CR	Endorsement	10.1General	Yes	No	available	No		R3‑244854
R3‑245032	(BL CR to 38.300) Support for Inter-CU LTM	Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung	draftCR	Endorsement	13.1General	Yes	Yes	endorsed	No		R3‑244855
R3‑245033	(BL CR to 38.300) Support for Regenerative Payload in NR NTN	Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo	draftCR	Endorsement	14.1General	Yes	No	available	No		R3‑244856
R3‑245034	(BL CR to 37.340) Support of XR enhancements	ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC	draftCR	Endorsement	21.1General	Yes	Yes	endorsed	No		R3‑244857
R3‑245035	(BL CR to 38.423) Support of XR enhancements	CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC	CR	Endorsement	21.1General	Yes	Yes	revised	No	R3‑245714	R3‑244858
R3‑245036	(BL CR to 38.425) XR enhancements for NR-NR DC	Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai Bell,China Telecom, CMCC, ZTE, CATT	CR	Endorsement	21.1General	Yes	Yes- Update the BL CR title to align with other BL CRs: (BL CR to 38.425) Support of XR enhancements	revised	No	R3‑245741	R3‑244859
R3‑245037	(BL CR to 38.300) Support of XR enhancements	Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung, Huawei	draftCR	Endorsement	21.1General	Yes	Yes	endorsed	No		R3‑244845
R3‑245038	Support for DL PSI based discard	Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom	CR	Endorsement	21.1General	Yes	Yes- Update the BL CR title to align with other BL CRs: (BL CR to 38.473) Support of XR enhancements	revised	No	R3‑245742	R3‑244767
R3‑245039	LS on AIML data collection	RAN(Interdigital)	LS in	Discussion	8.1New Incoming LSs	Yes	Yes	withdrawn	Yes
R3‑245040	Discussion on Rel-19 Inter-CU LTM	Nokia	discussion	Discussion	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245041	Discussion on Inter-CU LTM Dual Connectivity	Nokia	discussion		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245042	Correction on configuration update for an inactive Multicast session	ZTE Corporation, Huawei, CATT, Nokia, Lenovo	CR	Approval	9.2NR	Yes	No	available	No
R3‑245043	Draft correction to group paging conflicts for multicast reception in RRC_INACTIVE	ZTE Corporation	draftCR	Endorsement	9.2NR	Yes	No	available	No
R3‑245044	Discussion on L3 based L1/2 Triggered Mobility	Nokia, LG Electronics, NTT Docomo	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245045	TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures	Nokia	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245046	Discussion on SDT signalling optimization for partial context transfer	ZTE Corporation	discussion		8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245047	Correction on Transmission Bandwidth less than 5MHz in TS38.423	ZTE Corporation, China Telecom, CATT, China Unicom, Qualcom, Huawei, Nokia	CR		9.2NR	Yes	Yes	noted	No
R3‑245048	Correction on Transmission Bandwidth less than 5MHz	ZTE Corporaton, China Telecom, CATT, China Unicom, Qualcom, Huawei, Nokia	CR		9.2NR	Yes	Yes	noted	No
R3‑245049	Correction on Transmission Bandwidth less than 5MHz	ZTE Corporation, China Telecom, CATT, China Unicom	CR		9.2NR	Yes	Yes	noted	No
R3‑245050	Discussion on inter-CU LTM	ZTE Corporation	discussion		13.2Support for inter-CU LTM	Yes	Yes	noted	No
R3‑245051	Discussion on Unified logical system architecture for topology 1 and 2	ZTE Corporation	discussion		16.2RAN Architecture	Yes	No	available	No
R3‑245052	(TP for TR38.769) Unified logical system architecture for Topology 1 and Topology 2	ZTE Corporation	other		16.2RAN Architecture	Yes	No	available	No
R3‑245053	(TP for TR38.769) Text description for AIoT Signalling and Procedures	ZTE Corporation, Huawei, NEC, Nokia, CATT, China Telecom	other		16.3RAN-CN Interface Impact	Yes	Yes	withdrawn	Yes
R3‑245054	(TP for TR38.769) content for Ambient-IoT Inventory procedure	ZTE Corporation	other		16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245055	(TP for TR38.769) Locating an AIoT device	ZTE Corporation	other		16.4Others	Yes	No	available	No
R3‑245056	(TP to BL CR for TS 38.413) Support of MBS broadcast service for NR NTN	CATT	other	Decision	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245057	(TP to BL CRs) Support of regenerative payload	CATT	other	Decision	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245058	(TP to TR 38.769) A-IoT architecture aspects	CATT	other	Decision	16.2RAN Architecture	Yes	No	available	No
R3‑245059	(TP to TR 38 769) Procedures for AIoT Command	CATT	other	Decision	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245060	(TP to TR 38 769) Information exchange between AIoT CN and AIoT RAN	CATT	other	Decision	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245061	(TP to TR 38.879) Locating of A-IoT device	CATT	other	Decision	16.4Others	Yes	No	available	No
R3‑245062	Correction to area-specific SRS activation	CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated	draftCR	Approval	9.2NR	Yes	YesXiaomi: This scenario has not been specified in RAN2. RAN2 CR will be discussed in next meeting. HW: The CR is not correct. Noted Check RAN2 progress.	noted	No
R3‑245063	Correction to area-specific SRS activation	CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated	CR	Approval	9.2NR	Yes	Yes	noted	No
R3‑245064	Support of UE specific SRS Reservation	CATT, Huawei, ZTE, Samsung	draftCR	Approval	9.2NR	Yes	YesNok: Has been discussed before, no solution is needed HW: It was discussed a lot. E///: No	noted	No		R3‑244188
R3‑245065	Consideration on SDT signalling optimization for partial context transfer	CATT	discussion	Decision	8.3Left over LSs / pending actions	Yes	YesResp in R3-245677	noted	No
R3‑245066	Discussion on AIML assisted positioning	CATT	discussion	Decision	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245067	Discussion on Direct AIML positioning	CATT	discussion	Decision	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245068	Signaling design to enable NR SBFD operation	Qualcomm Incorporated	discussion	Agreement	19.2Support CLI Handling	Yes	No	available	No
R3‑245069	(BL pCR to TR 38.769) Study on solutions for Ambient IoT in NR	Huawei, CMCC	pCR	Agreement	16.1General	Yes	Yes	endorsed	No
R3‑245070	(TP to TR 38.769) A-IoT RAN Architecture aspects	Huawei	other	Agreement	16.2RAN Architecture	Yes	No	available	No
R3‑245071	(TP to TR 38.769) Protocol Stacks of Topology 2 solutions	Huawei, CMCC, ZTE, CATT, NEC, Xiaomi	other	Agreement	16.2RAN Architecture	Yes	Yes	noted	No
R3‑245072	(TP to TR 38.769) A-IoT Signalling and Procedures for Topology 1	Huawei	other	Agreement	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245073	(TP to TR 38.769) A-IoT Signalling and Procedures for Topology 2	Huawei	other	Agreement	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245074	(TP to TR 38.769) A-IoT Device Locating	Huawei	other	Agreement	16.4Others	Yes	No	available	No
R3‑245075	Correction on MBS Service Area	Huawei, CMCC, Ericsson, CBN	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245076	Correction on Retrieve UE Context Confirm [InterMNResume]	Huawei, Nokia, Qualcomm Incorporated	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245077	Correction on Retrieve UE Context Confirm [InterMNResume]	Huawei, Nokia, Qualcomm Incorporated	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245078	Correction on CIoT optimization with 5GC	Huawei, Ericsson, Qualcomm Incorporated, ZTE	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245079	Correction on CIoT optimization with 5GC	Huawei, Ericsson, Qualcomm Incorporated, ZTE	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245080	Correction on CIoT optimization with 5GC	Huawei, Ericsson, Qualcomm Incorporated, ZTE	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245081	(TP to BL CR for TR 38.769) AIoT RAN architecture	Xiaomi	other	Approval	16.2RAN Architecture	Yes	No	available	No
R3‑245082	(TP to BL CR for TR 38.769)) AIoT interface impacts between RAN and CN	Xiaomi	other	Approval	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245083	(TP to BL CR for TR 38.769)) Locating AIoT device	Xiaomi	other	Approval	16.4Others	Yes	No	available	No
R3‑245084	(TP to BL CR for TS 38.413) Support of Broadcast service	Xiaomi	other	Approval	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245085	Support of regenerative payload	Xiaomi	discussion	Agreement	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245086	Discussion on AI-based positioning	Xiaomi	discussion	Agreement	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245087	(TP to BL CR for TS 38.455) Support of gNB-side model training	Xiaomi	other	Approval	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245088	(TP to 38.423) Discussion on Mobility Optimization for NR-DC	ZTE Corporation	other	Approval	11.4R18 leftovers	Yes	Yes	noted	No
R3‑245089	Discussion on AI/ML assisted Network Slicing	ZTE Corporation	discussion		11.2AI/ML enabled Slicing	Yes	Yes	noted	No
R3‑245090	[TP to BLCR 38.423] Support of AI/ML assisted Network Slicing	ZTE Corporation, Qualcomm, China Unicom	other	Approval	11.2AI/ML enabled Slicing	Yes	Yes	noted	No
R3‑245091	Discussion on AI/ML assisted Coverage and Capacity Optimization	ZTE Corporation	discussion	Approval	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	Yes	noted	No
R3‑245092	[TP to 38.423 and 38.473] Support of AI/ML assisted Coverage and Capacity Optimization	ZTE Corporation, China Unicom	other	Approval	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245093	(TP to 38.473, 37.483) Discussion on split architecture	ZTE Corporation	other	Approval	11.4R18 leftovers	Yes	No	available	No
R3‑245094	Discussion on continuous MDT collection	ZTE Corporation	discussion	Approval	11.4R18 leftovers	Yes	No	available	No
R3‑245095	Discussion on AIML terminology	ZTE Corporation	discussion	Approval	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245096	[Draft] Reply LS on terminology definitions for AI-ML in NG-RAN	ZTE Corporation, Qualcomm, CMCC	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245097	Discussion on AIML assisted Positioning (Case 3a)	ZTE Corporation	discussion	Approval	20.2Support Positioning Accuracy Enhancements	Yes	Yes	noted	No
R3‑245098	Discussion on Direct Positioning (Case 3b)	ZTE Corporation	other	Approval	20.2Support Positioning Accuracy Enhancements	Yes	Yes	noted	No
R3‑245099	Correction of Positioning SI for connected UE	ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi	CR	Approval	9.2NR	Yes	Yes	endorsed	No
R3‑245100	Correction of Positioning SI for connected UE	ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi	CR	Approval	9.2NR	Yes	Yes	endorsed	No
R3‑245101	Correction of Positioning SI for connected UE	ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi	CR	Approval	9.2NR	Yes	Yes	endorsed	No
R3‑245102	Missing definition in RESOURCE STATUS REQUEST	ZTE Corporation, Samsung, CATT, China Telecom, CMCC, China Unicom	CR	Approval	9.2NR	Yes	YesTo be corrected by spec rapporteur in R19 as editorial correction.	noted	No
R3‑245103	Missing definition in RESOURCE STATUS REQUEST	ZTE Corporation, Samsung, CATT, China Telecom, CMCC, China Unicom	CR	Approval	9.2NR	Yes	YesTo be corrected by spec rapporteur in R19 as editorial correction.	noted	No
R3‑245104	Missing definition in RESOURCE STATUS REQUEST	ZTE Corporation, Samsung, CATT, China Telecom, CMCC, China Unicom	CR	Approval	9.2NR	Yes	YesTo be corrected by spec rapporteur in R19 as editorial correction.	noted	No
R3‑245105	Support of UE specific SRS reservation	ZTE Corporation, CATT, Huawei, Samsung	CR	Approval	9.2NR	Yes	YesTo be resubmitted with the change on the Requested SRS Preconfiguration Characteristics List IE in next meeting with updated coversheet	noted	No		R3‑244206
R3‑245106	(TP for TS 38.473) Discussion on On-Demand SSB SCell Operation	CMCC	other	Discussion	17.2Support on-demand SSB SCell operation	Yes	Yes	noted	No
R3‑245107	Support On-Demand SIB1 for UEs	CMCC	discussion	Discussion	17.3Support on-demand SIB1 for UEs	Yes	Yes	noted	No
R3‑245108	Support AIML Assisted Positioning	CMCC	discussion	Discussion	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245109	Support Direct AIML Positioning	CMCC	discussion	Discussion	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245110	Discussion on UL PSI based PDU discarding in NR-DC	CMCC	discussion	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245111	Discussion on on multi-modality awareness at RAN	CMCC	discussion	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245112	Discussion on MRO for LTM	Samsung	discussion	Approval	10.2MRO Enhancements	Yes	No	available	No
R3‑245113	Discussion on AI/ML enabled slicing	Samsung	discussion	Approval	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245114	Discussion on AI/ML enabled CCO	Samsung	discussion	Approval	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	Yes	noted	No
R3‑245115	Discussion on AI/ML for mobility in NR-DC	Samsung	discussion	Approval	11.4R18 leftovers	Yes	No	available	No
R3‑245116	Discussion on AI/ML for NG-RAN in split architecture	Samsung	discussion	Approval	11.4R18 leftovers	Yes	No	available	No
R3‑245117	(CR to 37.483) AI/ML for NG-RAN on split architecture	Samsung	CR	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245118	Discussion on continuous MDT collection targeting the same UE across RRC states	Samsung	discussion	Approval	11.4R18 leftovers	Yes	No	available	No
R3‑245119	Discussion on on-demand SSB SCell operation in low-carbon green network	Samsung	discussion	Approval	17.2Support on-demand SSB SCell operation	Yes	No	available	No
R3‑245120	Discussion on on-demand SIB1 in low-carbon green network	Samsung	discussion	Approval	17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245121	Discussion on AI/ML for positioning	Samsung	discussion	Approval	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245122	Support of UE specific SRS reservation	Samsung, CATT, Huawei, ZTE	CR	Agreement	9.2NR	Yes	YesTo be resubmitted in next meeting with updated coversheet	noted	No		R3‑244216
R3‑245123	Discussion on QMC support in NR-DC for RRC segmentation	Samsung, ZTE, CATT, China Unicom, Lenovo	discussion	Agreement	9.2NR	Yes	NoResp in R3-245679	available	No
R3‑245124	Corrections to QMC support in NR-DC for RRC Segmentation	Samsung, ZTE, CATT, Lenovo, China Unicom	CR	Agreement	9.2NR	Yes	NoResp in R3-245679	available	No
R3‑245125	Further discussion on support MBS broadcast service for NR NTN	Samsung	discussion	Agreement	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245126	Further discussion on support of regenerative payload for NR NTN	Samsung	discussion	Agreement	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245127	Further discussion on RAN architecture for Ambient IoT	Samsung	discussion	Agreement	16.2RAN Architecture	Yes	No	available	No
R3‑245128	Further discussion on RAN-CN interface impact for Ambient IoT	Samsung	discussion	Agreement	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245129	Correction of SON for fast MCG recovery in stage 2	Samsung, Lenovo, CATT, Nokia	draftCR	Endorsement	9.2NR	Yes	Yes	noted	No
R3‑245130	Failure scenarios on MRO for CHO with candidate SCGs	Samsung, Cybercore, Lenovo	discussion	Approval	10.2MRO Enhancements	Yes	No	available	No
R3‑245131	Discussion on MRO for CHO with candidate SCGs and S-CPAC	Samsung	discussion	Approval	10.2MRO Enhancements	Yes	No	available	No
R3‑245132	(TP for SON BLCR for 38.423, 36.423) Rel-18 SON and MDT leftovers	Samsung	discussion	Approval	10.4R18 leftovers	Yes	No	available	No
R3‑245133	Discussion on information exchange among gNBs for CLI handling	Samsung	discussion	Agreement	19.2Support CLI Handling	Yes	No	available	No
R3‑245134	TPs to BLCRs of TS38.473 and TS38.423 on CLI handling	Samsung	discussion	Agreement	19.2Support CLI Handling	Yes	No	available	No
R3‑245135	Discussion on AI/ML based Coverage and Capacity Optimization	China Telecom	discussion	Decision	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245136	(TP to TS38.470) Support of AI/ML for NG-RAN	China Telecom	other	Approval	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245137	(TP to TS38.423) Support of AI/ML based Coverage and Capacity Optimization	China Telecom	other	Approval	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245138	Discussion on Continuous MDT measurement	China Telecom	discussion	Decision	11.4R18 leftovers	Yes	No	available	No
R3‑245139	Support of MBS broadcast service	China Telecom	discussion	Decision	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245140	Support of regenerative payload in NR NTN	China Telecom	discussion	Decision	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245141	(TP to TR 38.769) RAN architecture for Ambient-IoT	China Telecom	other	Approval	16.2RAN Architecture	Yes	No	available	No
R3‑245142	Discussion on signaling enhancement for inter-CU LTM	China Telecom	discussion	Decision	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245143	Discussion on support of inter-CU LTM in NR-DC scenario	China Telecom	discussion	Decision	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245144	(TP for TS38.300) On support of inter-CU LTM	China Telecom	other	Approval	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245145	Discussion on MRO enhancements for LTM	China Telecom	discussion	Decision	10.2MRO Enhancements	Yes	No	available	No
R3‑245146	Discussion on SON enhancements for network slicing	China Telecom	discussion	Decision	10.3.2Network Slicing	Yes	No	available	No
R3‑245147	Discussion on AI/ML based Mobility Optimization for NR-DC	China Telecom	discussion	Discussion	11.4R18 leftovers	Yes	No	available	No
R3‑245148	(TP to TS38.423) Support of AIML based Mobility Optimization for NR-DC	China Telecom	other	Approval	11.4R18 leftovers	Yes	No	available	No
R3‑245149	Discussion on support of direct AI/ML positioning (Case 3b)	China Telecom	discussion	Discussion	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245150	Discussion on support of AI/ML assisted positioning (Case 3a)	China Telecom	discussion	Discussion	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245151	On NR Femto Architecture and functional split	China Telecom	discussion	Decision	12.35G Femto	Yes	No	available	No
R3‑245152	On access control for NR Femtos	China Telecom	discussion	Decision	12.35G Femto	Yes	No	available	No
R3‑245153	On support on-demand SSB SCell operation	China Telecom	discussion	Decision	17.2Support on-demand SSB SCell operation	Yes	No	available	No
R3‑245154	TPs to BLCRs of TS38.473 and TS38.423 on CLI handling	Samsung	discussion	Agreement	19.2Support CLI Handling	No	Yes	withdrawn	Yes
R3‑245155	Discussion on WAB mobility	Samsung	discussion	Agreement	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245156	Discussion on other aspects for the support of WAB	Samsung	discussion	Agreement	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245157	Discussion on NR Femto architecture	Samsung	discussion	Agreement	12.35G Femto	Yes	No	available	No
R3‑245158	Discussion on access control for NR Femto	Samsung	discussion	Agreement	12.35G Femto	Yes	No	available	No
R3‑245159	Correction on UAI for support XR in DC	Samsung, Ericsson, Cybercore	CR	Agreement	31.1Corrections	Yes	YesZTE: Do not see the necessity, the current mechanism is sufficient. UAI is not introduced for XR QC: It’s beneficial, support this SS: Try to shorten the delay Nok: Similar comment as ZTE	noted	No
R3‑245160	Introduction to coordination for QoE RRC segmentation in NR-DC	ZTE Corporation, Samsung, Lenovo, China Unicom	draftCR	Agreement	9.2NR	Yes	NoResp in R3-245679	available	No
R3‑245161	Discussion on remaining issues on R18 LTM	Samsung	discussion	Approval	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245162	Discussion on inter-gNB-CU LTM	Samsung	discussion	Approval	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245163	Additional discussion on Inter-gNB-CU LTM	Samsung	discussion	Approval	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245164	(TP to BLCR for TS 38.401) Procedure on Inter-gNB-CU LTM	Samsung	other	Approval	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245165	Discussion on LS from SA2 on multi-modality	vivo	discussion	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245166	Discussion on signaling design for LP-WUS subgrouping	vivo, NTT DOCOMO INC.	discussion	Discussion	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245167	BLCR for TS 38.300 on support of LP-WUS	vivo, NTT DOCOMO INC.	draftCR	Discussion	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245168	Support User Location Information reporting for NB-IoT NTN	Nokia, Nokia Shanghai Bell, Qualcomm	CR		9.1LTE	Yes	Yes	noted	No		R3‑244345
R3‑245169	Discussion on the LS related to XR	Nokia, Nokia Shanghai Bell	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245170	[Draft] Reply LS on multi-modality awareness at RAN	Nokia	LS out	Agreement	8.1New Incoming LSs	Yes	Yes- Remove the last sentence. - Remove “during the QoS Flow establishment/modification procedure	revised	No	R3‑245682
R3‑245171	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR		9.2NR	Yes	Yes- Update the consequence: The ambiguity of the semantics description for gNB-DU Cell Resource Configuration-FDD-DL IE, and the semantics description for gNB-DU Cell Resource Configuration-TDD IE exist.	revised	No	R3‑245704
R3‑245172	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR		9.2NR	Yes	Yes- Update the consequence: The ambiguity of the semantics description for gNB-DU Cell Resource Configuration-FDD-DL IE, and the semantics description for gNB-DU Cell Resource Configuration-TDD IE exist.	revised	No	R3‑245705
R3‑245173	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR		9.2NR	Yes	Yes- Update the consequence: The ambiguity of the semantics description for DL Carrier List IE exist.	revised	No	R3‑245706
R3‑245174	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR		9.2NR	Yes	Yes- Update the consequence: The ambiguity of the semantics description for DL Carrier List IE exist.	revised	No	R3‑245707
R3‑245175	(TP for TS 38.401) Discussion on high level aspects for WAB	Nokia, Nokia Shanghai Bell	other		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245176	(TP for TS 38.423) Discussion on WAB mobility	Nokia, Nokia Shanghai Bell	other		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245177	(TP for TS 38.300) Discussion on the support of MBS Broadcast Service	Nokia, Nokia Shanghai Bell	other		14.2Support MBS broadcast service	Yes	No	available	No
R3‑245178	(TP for TS 38.300) Discussion on the support of Regenerative payload	Nokia, Nokia Shanghai Bell	other		14.3Support of Regenerative payload	Yes	No	available	No
R3‑245179	(TP for TS 38.413) Introduce NG Removal procedure	Nokia, Nokia Shanghai Bell, Huawei, CATT, CMCC, Ericsson, Qualcomm, Xiaomi	other		14.3Support of Regenerative payload	Yes	No	available	No
R3‑245180	Correction on conditional PSCell addition or change failure	CATT, CMCC, ZTE, Nokia, Nokia Shanghai Bell	draftCR	Agreement	9.2NR	Yes	YesE/// comments that it’s a new use case on Too late CPC execution.	endorsed	No
R3‑245181	Option1: Correction on DU collecting and reporting of DL LBT failure information	CATT, Ericsson, Nokia	CR	Agreement	9.2NR	Yes	Yes	noted	No
R3‑245182	Indicating configuration of PSI-based discard in SN-triggered modification procedure	CATT	CR	Agreement	31.1Corrections	Yes	Yes- Update Working Group	revised	No	R3‑245711
R3‑245183	(TP for 38.300 and 37.340) MRO for R18 mobility mechanisms	CATT	other	Decision	10.2MRO Enhancements	Yes	No	available	No
R3‑245184	(TP for 38.300) Intra-NTN mobility for SONMDT	CATT	other	Decision	10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245185	(TP for 38.413 and 38.423) Network slicing for SONMDT	CATT	other	Decision	10.3.2Network Slicing	Yes	No	available	No
R3‑245186	(TP for 37.340 and 38.413) SON enhancement for R18 leftover	CATT	other	Decision	10.4R18 leftovers	Yes	No	available	No
R3‑245187	Discussion on Evolution of Duplex Operation	CATT	discussion	Decision	19.2Support CLI Handling	Yes	No	available	No
R3‑245188	(TP for 38.423 and 38.473) Support SBFD Operation	CATT	other	Decision	19.2Support CLI Handling	Yes	No	available	No
R3‑245189	Discussion on XR LS R3-245011 and R3-245017	CATT	discussion	Decision	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245190	[TP to BLCR 38.300] Support of AI/ML assisted Network Slicing	ZTE Corporation, Lenovo, Samsung	other	Approval	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245191	Discussion on AIML based Mobility Optimization for NR-DC	CMCC	discussion	Discussion	11.4R18 leftovers	Yes	No	available	No
R3‑245192	(TP to 38.300) Discussion on SONMDT enhancement for NTN	CMCC	other	Discussion	10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245193	Discussion on AI-based network slice	CMCC	discussion	Discussion	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245194	TP to 38.423 AI/ML based Slice	CMCC	other	Approval	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245195	Discussion on AI/ML-based CCO	CMCC	discussion	Discussion	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245196	Discussion on AIML for split architecure use cases	CMCC	discussion	Discussion	11.4R18 leftovers	Yes	No	available	No
R3‑245197	Discussion on continuous MDT	CMCC	discussion	Discussion	11.4R18 leftovers	Yes	No	available	No
R3‑245198	Discussion on supporting CLI handling in SBFD	CMCC	discussion	Discussion	19.2Support CLI Handling	Yes	No	available	No
R3‑245199	Discussion on SONMDT for network slicing	CMCC	discussion	Discussion	10.3.2Network Slicing	Yes	No	available	No
R3‑245200	Discussion on Low-power wake-up signal and receiver for NR	CMCC	discussion	Discussion	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245201	Discussion on the PDCP anchor based solution	Huawei, Ericsson, CATT, China Telecom, CMCC,Samsung	discussion		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245202	Discussion on Inter-CU LTM procedure	Huawei	discussion		13.2Support for inter-CU LTM	Yes	Yes	noted	No
R3‑245203	(TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure	Huawei	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245204	(TP for LTM BLCR for TS 38.473): F1 impact for Inter-CU LTM	Huawei	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245205	Correction of the Signalling based MDT PLMN List IE	Huawei, China Unicom, China Telecom	CR		9.2NR	Yes	Yes	noted	No
R3‑245206	Correction of the Signalling based MDT PLMN List IE	Huawei, China Unicom, China Telecom	CR		9.2NR	Yes	Yes	noted	No
R3‑245207	Correction of the Signalling based MDT PLMN List IE	Huawei, China Unicom, China Telecom	CR		9.2NR	Yes	Yes	noted	No
R3‑245208	(TP for TS 38.413 and TS 38.300) Discussion on NTN broadcast service supporting	ZTE Corporation	other	Approval	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245209	Correction to enhancing QoS Monitoring with Per-Packet Granularity	ZTE Corporation	CR	Agreement	31.2Enhancements	Yes	Yes	noted	No
R3‑245210	Enhancing QoS Monitoring with Per-Packet Granularity	ZTE Corporation	discussion	Approval	31.2Enhancements	Yes	NoCMCC: Per packet delay has not been discussed in SA2 ZTE: The per packet delay monitoring has been defined in SA1 E///: SA2 has discussed, focus on UE side what to report, D1 delay measurement report needs to be checked by RAN2, fine to send LS to RAN2 and start from there CATT: This requirement needs to be supported, can further discuss the LS to RAN2 SS: Worry about the impact on UE side, check with RAN2 first HW: Check with SA2 on the requirement CB: # 11_QoSMonitoring - Send the LS to RAN2, cc SA2 on the feasibility of the solution for per packet delay monitoring (moderator - ZTE)	available	No
R3‑245211	Discussion on RAN2 and SA2 LS	ZTE Corporation	discussion	Approval	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245212	(draft reply LS) Reply to RAN2 LS on UL PSI based PDU discarding in NR-DC	ZTE Corporation	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245213	(draft reply LS)Reply LS to SA2 on multi-modality awareness at RAN	ZTE Corporation	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245214	Further miscellaneous corrections to QMC procedure	Huawei, China Unicom, Lenovo	draftCR	Endorsement	9.2NR	Yes	No	available	No
R3‑245215	Workplan for Rel-19 WI on Evolution of NR duplex operation: Sub-band full duplex (SBFD)	Huawei	Work Plan	Decision	19.1General	Yes	No	available	No
R3‑245216	General discussion on RAN3 impacts by the RAN1 agreements	Huawei	discussion	Discussion	19.2Support CLI Handling	Yes	No	available	No
R3‑245217	BL CR on the introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD)	Huawei	CR	Approval	19.2Support CLI Handling	Yes	No	available	No
R3‑245218	(TP for TS 38.473) Discussion on on-demand SSB SCell operation	Huawei	other		17.2Support on-demand SSB SCell operation	Yes	No	available	No
R3‑245219	(TP for TS 38.473) Discussion on on-demand SIB1 for UEs in idle or inactive mode	Huawei	other		17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245220	(TP for TS 38.413 and TS 38.423) Discussion on Low-power wake-up signal and receiver for NR	Huawei	other		18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245221	Introduction of low-power wake-up signal and receiver for NR	Huawei	CR		18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No		R3‑244077
R3‑245222	DRAFT Reply LS on L3 measurement based LTM support over F1	Vodafone GmbH	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	revised	No	R3‑245699
R3‑245223	[TP to 38.300] Support of AI/ML assisted CCO	ZTE Corporation, Lenovo, China Unicom	other	Approval	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245224	[TP to 38.401] Support of AI/ML assisted CCO	ZTE Corporation, Lenovo, China Unicom	other	Approval	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245225	Correction of mobility change procedure	Huawei, Nokia, Deutsche Telekom	CR		9.2NR	Yes	Yes	noted	No
R3‑245226	Correction of mobility change procedure	Huawei, Nokia, Deutsche Telekom	CR		9.2NR	Yes	Yes	noted	No
R3‑245227	Correction of mobility change procedure	Huawei, Nokia, Deutsche Telekom	CR		9.2NR	Yes	Yes- Only for R18, with Cat.F as BC CR	revised	No	R3‑245701
R3‑245228	Correcting IE reference in Cell Replacing Info	Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC	CR		9.2NR	Yes	Yes	endorsed	No
R3‑245229	Correcting IE reference in Cell Replacing Info	Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC	CR		9.2NR	Yes	Yes	endorsed	No
R3‑245230	(TP for BLCR for SON for 38.300, 38.401,38.473, 37.340, 38.423) MRO enhancement for R18 mobility mechanisms	Huawei	other		10.2MRO Enhancements	Yes	No	available	No
R3‑245231	(TP for BLCR for MDT for 38.413) SON and MDT for Network Slicing	Huawei	other		10.3.2Network Slicing	Yes	No	available	No
R3‑245232	(TP for BLCR for SON for 38.413, 36.423) Rel-18 SON and MDT leftovers	Huawei	other		10.4R18 leftovers	Yes	No	available	No
R3‑245233	[DRAFT] Reply LS on MHI enhancement solution for SCG deactivation/activation	Huawei, CMCC, Ericsson, ZTE [will be RAN3]	LS out	Agreement	10.4R18 leftovers	Yes	No	available	No
R3‑245234	Support of LP-WUS	Nokia	draftCR		18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245235	Support of LP-WUS	Nokia	CR		18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245236	Correction of MBS PDCP packets discard	Nokia	discussion		31.1Corrections	Yes	YesZTE: Same comment as last meeting, the data loss issue is not solved E///: What’s the behavior from UE point of view? CATT: Same concern as ZTE and E///	noted	No
R3‑245237	Exchange of MBS multicast services in RRC inactive	Nokia, Huawei, CATT, Qualcomm Incorporated	CR		31.1Corrections	Yes	YesZTE: Do not like this solution, the conclusion in R18 is that the change is not often E///: SIB24? Class1 procedure	noted	No
R3‑245238	Discussion for support L3 based LTM	CATT	discussion	Approval	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245239	Support L3 mesauement based LTM(stage3)	CATT	CR	Approval	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245240	Support L3 mesauement based LTM(stage2)	CATT	CR	Approval	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245241	Discussion on UE Location Information for NB-IoT NTN with draft LS	CATT	discussion	Decision	9.1LTE	Yes	Yes	noted	No
R3‑245242	Alignment for misalignment of early sync procedure	CATT, China Telecom, CMCC	CR	Approval	9.2NR	Yes	YesE///: The name alignment is fine, but the color in the figure is not correct	noted	No
R3‑245243	Scenario clarification for continuous MDT	CATT	discussion	Decision	11.4R18 leftovers	Yes	No	available	No
R3‑245244	Discussion for Inter-CU LTM	CATT	discussion	Decision	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245245	Discussion for Inter-CU LTM in DC	CATT	discussion	Decision	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245246	TP for LTM BLCR for TS38.300	CATT	other	Agreement	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245247	(draft Reply LS to SA2) Discussion on SA2 questions on multi-hop WAB and UE ULI	Qualcomm Inc.	other	Discussion	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245248	Discussion on assumptions and architecture for WAB	Qualcomm Inc.	other	Discussion	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245249	Aspects of on-demand SIB1 for NES enhancements	Qualcomm Inc.	discussion	Discussion	17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245250	Support LP-WUS subgrouping in RRC_IDLE/RRC_INACTIVE	Qualcomm Inc.	discussion	Discussion	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245251	QoE measurement handling in idle mode	CATT, Ericsson, ZTE, Xiaomi	draftCR	Approval	9.2NR	Yes	No	available	No		R3‑244230
R3‑245252	Discussion on stage-2 aspects for WAB	CATT	discussion	Decision	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245253	Other issues for WAB	CATT	discussion	Decision	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245254	Discussion on 5G Femto in stage 2	CATT	discussion	Decision	12.35G Femto	Yes	No	available	No
R3‑245255	Impact to NG interface for 5G Femto	CATT	discussion	Decision	12.35G Femto	Yes	No	available	No
R3‑245256	On support on-demand SSB SCell operation	CATT	discussion	Decision	17.2Support on-demand SSB SCell operation	Yes	No	available	No
R3‑245257	On support on-demand SIB1 for idle UE	CATT	discussion	Decision	17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245258	Correction on IAB TMM	CATT, Nokia, Nokia Shanghai Bell	CR	Approval	9.2NR	Yes	YesQC, SS, ZTE: The changes are not necessary E///: Open to discuss further HW: The first change is clear enough in stage2, can further discuss the options Nok: backhaul resources releasing is missing in stage3	noted	No
R3‑245259	Correction on IAB TMM	CATT, Nokia, Nokia Shanghai Bell	CR	Approval	9.2NR	Yes	Yes	noted	No
R3‑245260	Support cell DTXDRX for NES	CATT, ZTE, NEC	discussion	Decision	31.2Enhancements	Yes	No	available	No
R3‑245261	Support Cell DTX/DRX for NES	CATT, ZTE, NEC	CR	Approval	31.2Enhancements	Yes	No	available	No		R3‑241533
R3‑245262	Support cell DTXDRX for NES	CATT, ZTE, NEC	CR	Approval	31.2Enhancements	No	Yes	withdrawn	Yes
R3‑245263	Discussion on LTM MRO	Google	discussion	Decision	10.2MRO Enhancements	Yes	No	available	No
R3‑245264	Discussion on Early Sync and CFRA resource configurations in inter-CU LTM	Google	discussion	Decision	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245265	Correction on CPAC failure states and detection mechanism in stage 2	Nokia, CATT, Lenovo, CMCC, Qualcomm Incorporated, Huawei	draftCR	Approval	9.2NR	Yes	YesE///: Same comment as previous meeting, the current text is correct ZTE: The new text seems more clear than the original one	noted	No
R3‑245266	Discussion on ENB Configuration Update procedure	CATT, Huawei, CMCC, NEC	discussion	Decision	9.1LTE	Yes	YesLate contribution Add description in Deactivation Indication IE that If this IE is not included, indicates that the concerned cell is activated? E///: Whenever this IE presents, it means the current status of the cell rather than the state change. Check the procedure text and semantic description together. SS: Fine with CATT’s CR The receiving node keep the information unchanged in case the optional IE in Served Cell Information IE and Neighbour Information IE is absent? The behavior of the receiving node when NR Neighbor Information IE is not available, as well as whether the sending node should always include the complete list of NR Neighbor Cell Information? Same question on E-UTRAN Neighbor Information IE. E///: The current spec is very clear. CATT: The neighbor cell list procedure text is missing. HW: Including full list is a safe way. ZTE: Two scenarios Nok: The current mechanism is enough. SS: Clarification is needed for Serving cell and neighbor cell. The sending node should always include the complete list of NR Serving Cell information and Neighbor Cell Information in case of modification? Check current spec description.	noted	No
R3‑245267	Clarification on indication of dormant cell re-activation	CATT,Nokia,Huawei,CMCC,ZTE,NEC,Samsung	CR	Agreement	9.1LTE	Yes	YesLate contribution - Check whether any updates needed for procedure text together?	revised	No	R3‑245687
R3‑245268	Discussion on definition of UE performance metrics	CATT,Deutsche Telekom,China Unicom	discussion	Decision	9.2NR	Yes	NoLate contribution	available	No
R3‑245269	[DRAFT] LS on UE level measurements	CATT,Deutsche Telekom,China Unicom[To be RAN3]]	LS out	Agreement	9.2NR	Yes	NoLate contribution	available	No
R3‑245270	(TP on 38.423)Support of AI/ML enabled Slicing	CATT	other	Decision	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245271	(TP on 38.423/38.473)Discussion on AI/ML based CCO	CATT	other	Decision	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245272	Discussion on left over issues on DC and split architecture	CATT	discussion	Decision	11.4R18 leftovers	Yes	No	available	No
R3‑245273	(TP on TS37.480)Introducing data collection function into E1	CATT	other	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245274	(TP on TS38.470) Introducing data collection function into F1	CATT	other	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245275	Potential RAN3 impacts of LP-WUS	CATT	discussion	Discussion	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245276	TP on TS 38.300 for LP-WUS	CATT	other	Decision	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245277	(TP for SON BL CR for TS 38.300) MRO Enhancements for LTM and CHO with Candidate SCG(s)	Nokia	other	Agreement	10.2MRO Enhancements	Yes	No	available	No
R3‑245278	Discussion on Draft Reply LS on multi-modality awareness at RAN (Response to S2-2409444)	NEC	discussion	Decision	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245279	(Draft) Reply LS on multi-modality awareness at RAN	NEC	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245280	inter-CU LTM issues	NEC	discussion	Decision	13.2Support for inter-CU LTM	Yes	Yes	noted	No
R3‑245281	(TP to 38.423 on inter-CU LTM) inter-CU LTM related information	NEC	other	Agreement	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245282	Discussion on AIML based Positioning Accuracy Enhancements	NEC	discussion	Decision	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245283	Discussion on CLI handling support	NEC	discussion	Decision	19.2Support CLI Handling	Yes	No	available	No
R3‑245284	(TP for SON BLCR of 38.473) Discussion on MRO for LTM	NEC	other	Decision	10.2MRO Enhancements	Yes	No	available	No
R3‑245285	(TP to 38.413, 38.423, 38.473 on LP-WUS) Discussion on the support of LP-WUS indicating paging monitoring	NEC	other	Decision	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245286	(TP to BL CR of 38.423 on WAB) Discussion on the reliability and mobility for WAB	NEC	other	Decision	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245287	(TP for TS 38.300 and TS 38.413) Discussion on NR NTN supporting MBS broadcast service	NEC	other	Agreement	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245288	(TP for TS 38.300) Discussion on regenerative payload enhancement for NR NTN	NEC	other	Agreement	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245289	(TP for TR 38.769) Discussion on Architecture of Ambient IoT	NEC	discussion	Discussion	16.2RAN Architecture	Yes	No	available	No
R3‑245290	Discussion on RAN-CN interface impact on Ambient IoT	NEC	discussion	Discussion	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245291	Corrections for QoE intra-5GC inter-RATs mobility	NEC	draftCR	Agreement	9.2NR	Yes	No	available	No
R3‑245292	Corrections for QoE intra-5GC inter-RATs mobility on XnAP	NEC	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245293	(TP to TS38.423) General considerations on Enhancements for AI/ML for NG-RAN	NEC	other	Agreement	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245294	Draft CR to TS38.300 on enhancements for AI/ML for NG-RAN	NEC	draftCR	Agreement	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245295	Draft CR to TS38.401 on enhancements for AI/ML for NG-RAN	NEC	draftCR	Agreement	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245296	(TP to TS38.423) Split architecture and NR-DC mobility optimization	NEC	other	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245297	Continuous MDT collection for AI/ML	NEC	discussion	Decision	11.4R18 leftovers	Yes	No	available	No
R3‑245298	(TP to TS38.300) NR Femto	NEC	other	Agreement	12.35G Femto	Yes	No	available	No
R3‑245299	Support on-demand SSB operation	NEC	discussion	Decision	17.2Support on-demand SSB SCell operation	Yes	No	available	No
R3‑245300	Support on-demand SIB1	NEC	discussion	Decision	17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245301	Corrections on MP relay based PDCP duplication	ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell	CR	Approval	9.2NR	Yes	Yes	endorsed	No
R3‑245302	(TP to TS 38.413, 38.473, 38.423) Discussion on RAN3 impacts for LP-WUS	ZTE Corporation	other	Agreement	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245303	[draft LS] to SA2/CT1 on support of LP-WUS subgrouping	ZTE Corporation	other	Approval	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245304	Discussion on AI-ML based positioning accuracy enhancement	Baicells	discussion	Decision	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245305	Discussion on NR Femto Architecture and Functionality	Baicells	discussion	Decision	12.35G Femto	Yes	No	available	No
R3‑245306	TP to 38.300 for NR Femto	Baicells	discussion	Decision	12.35G Femto	Yes	No	available	No
R3‑245307	(TP for TR38.769) Text description for AIoT Signalling and Procedures	ZTE Corporation, Huawei, NEC, Nokia, CATT, China Telecom, CMCC	other	Agreement	16.3RAN-CN Interface Impact	Yes	YesXiaomi: How to perform reader selection needs further discussion. Remove the note: NOTE 1: Before initiating inventory procedure, the AIoT CN may select suitable AIoT-enabled UE(s). Lenovo: NOTE 1: Before initiating inventory procedure, the AIoT CN may select candidate AIoT-enabled UE(s).	noted	No
R3‑245308	Clarification of the usage of the UE History Information	Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone	CR	Agreement	9.2NR	Yes	Yes	endorsed	No
R3‑245309	---	Nokia	CR	Agreement	9.2NR	No	Yes	withdrawn	Yes
R3‑245310	[TP to BL CR to 37.340, SON] Failure handling and optimal use of Subsequent CPAC	Nokia	other	Agreement	10.2MRO Enhancements	Yes	No	available	No		R3‑244065
R3‑245311	[TP to BL CR to 38.423, SON] Solution to avoid restarting MRO in NTN deployments	Nokia	other	Agreement	10.3.1Intra-NTN Mobility	Yes	No	available	No		R3‑244066
R3‑245312	[TP to BL CR to 38.300, MDT] MDT solution for slice support and slice-related mobility enhancements	Nokia	other	Agreement	10.3.2Network Slicing	Yes	No	available	No		R3‑244067
R3‑245313	Signalling enhancements for inter-CU LTM HO	Qualcomm Incorporated, Vodafone, Bharti Airtel (India)	discussion	Decision	13.2Support for inter-CU LTM	Yes	Yesneed to add JIO as a co-source company.	revised	No	R3‑245744
R3‑245314	Enabling subsequent inter-gNB LTM by decoupling of cell and anchor changes	Qualcomm Incorporated, Vodafone, NTT DOCOMO, Sony, Bharti Airtel (India)	discussion	Decision	13.2Support for inter-CU LTM	Yes	Yesneed to add JIO as a co-source company.	revised	No	R3‑245745
R3‑245315	Impact analysis of coupling LTM cell switch and CU anchor changes on subsequent inter-gNB LTM	Qualcomm Incorporated, Vodafone, NTT DOCOMO, Sony, Bharti Airtel (India)	discussion	Decision	13.2Support for inter-CU LTM	Yes	Yesneed to add JIO as a co-source company.	revised	No	R3‑245746
R3‑245316	Further discussion on XnAP signaling for inter-CU LTM	Ericsson	discussion		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245317	(TP for TS 38.423) Xn support for inter-CU LTM	Ericsson	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245318	(TP for TS 38.300) Stage-2 signalings for inter-CU LTM	Ericsson	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245319	Switch to RRC Connected after SDT Partial Context Transfer	Nokia, Ericsson	discussion		8.3Left over LSs / pending actions	Yes	YesResp in R3-245677	noted	No
R3‑245320	Correction of switch to RRC connected after SDT Partial Context Transfer	Nokia, Ericsson	draftCR		8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245321	Correction of switch to RRC connected after SDT Partial Context Transfer	Nokia, Ericsson	CR		8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245322	Response LS on SDT signalling optimization for partial context transfer	Nokia	LS out	Agreement	8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245323	Completion of Protocol and Functional aspects of NR Femto Architecture	Nokia	discussion		12.35G Femto	Yes	No	available	No
R3‑245324	Introduction of NR Femto Architecture and Protocol Aspects	Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter	draftCR		12.35G Femto	Yes	No	available	No
R3‑245325	Introduction of Functional aspects of NR Femto architecture	Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter	draftCR		12.35G Femto	Yes	No	available	No
R3‑245326	Introduction of NR Femto architecture with optional NR Femto Gateway	Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter	CR		12.35G Femto	Yes	No	available	No
R3‑245327	LS on Security Verifications related to NR Femtos	Nokia	LS out	Agreement	12.35G Femto	Yes	No	available	No
R3‑245328	Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE]	Ericsson, CATT, Xiaomi, ZTE	CR	Agreement	9.2NR	Yes	Yes- Add HW as co-source	revised	No	R3‑245697	R3‑244406
R3‑245329	Correction of TRP Geographical coordinates [PosLocalCoords]	Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia	CR	Agreement	9.2NR	Yes	Yes- Put the optional IE below the mandatory IE, and the same change in ASN.1	revised	No	R3‑245689	R3‑244407
R3‑245330	Correction of TRP Geographical coordinates [PosLocalCoords]	Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia	CR	Agreement	9.2NR	Yes	Yes- Put the optional IE below the mandatory IE, and the same change in ASN.1	revised	No	R3‑245690	R3‑244408
R3‑245331	Architecture, interfaces and transport for Ambient IoT	Qualcomm Incorporated	discussion	Discussion	16.2RAN Architecture	Yes	No	available	No
R3‑245332	Inventory and Command related procedures for Ambient IoT	Qualcomm Incorporated	discussion	Discussion	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245333	Methods for locating Ambient IoT devices	Qualcomm Incorporated	discussion	Discussion	16.4Others	Yes	No	available	No
R3‑245334	MRO enhancements for R18 mobility mechanisms	Qualcomm Incorporated	discussion	Discussion	10.2MRO Enhancements	Yes	No	available	No
R3‑245335	SON MDT for NTN	Qualcomm Incorporated	discussion	Discussion	10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245336	SON MDT for network slicing	Qualcomm Incorporated	discussion	Discussion	10.3.2Network Slicing	Yes	No	available	No
R3‑245337	UHI enhancements for SCG (de)activation	Qualcomm Incorporated	discussion	Discussion	10.4R18 leftovers	Yes	No	available	No
R3‑245338	Introduction of LP-WUS paging monitoring	Ericsson	CR	Endorsement	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No		R3‑244410
R3‑245339	Correction of mapped cell support list	Nokia, Nokia Shanghai Bell, Ericsson, Huawei	draftCR		9.1LTE	Yes	Yes	noted	No
R3‑245340	Discussion on support of regenerative payload for NR NTN	CSCN	discussion	Discussion	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245341	L2 reset for intra-DU LTM	Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, Ericsson, CATT	CR		9.2NR	Yes	Yes	noted	No
R3‑245342	[Draft]Response reply LS on MDT configuration control in NR-DC	ZTE Corporation	other		8.1New Incoming LSs	Yes	YesResp in R3-245678	noted	No
R3‑245343	Correction on definition of MDT measurements collection in MR-DC	ZTE Corporation	other		8.1New Incoming LSs	Yes	YesResp in R3-245678	noted	No
R3‑245344	(TP for TS 37.340 TS38.401)Discussion on MRO	ZTE Corporation	discussion		10.2MRO Enhancements	Yes	No	available	No
R3‑245345	Further consideration on SON/MDT for Slicing	ZTE Corporation	discussion		10.3.2Network Slicing	Yes	No	available	No
R3‑245346	Correction on Xn Setup message	ZTE Corporation	CR		9.2NR	Yes	No	available	No
R3‑245347	Correction on Xn Setup message	ZTE Corporation	CR		9.2NR	Yes	No	available	No
R3‑245348	Correction on Xn Setup message	ZTE Corporation	CR		9.2NR	Yes	No	available	No
R3‑245349	Correction on Xn Setup message	ZTE Corporation	CR		9.2NR	Yes	No	available	No
R3‑245350	Clarification on SpCell ID replacement	Google	CR	Agreement	9.2NR	Yes	Yes	revised	No	R3‑245749	R3‑244179
R3‑245351	Support Cell DTX/DRX for NES	CATT, ZTE, NEC	CR	Approval	31.2Enhancements	Yes	No	available	No		R3‑241533
R3‑245352	Corrections for L3 measurement triggered LTM cell switch	Google	CR	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245353	Discussion on SON enhancements for NTN	Samsung Electronics Nordic AB	discussion		10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245354	Discussion on AI/ML based CCO	Rakuten Mobile, Inc	discussion		11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245355	Editorial correction on TNL Configuration Info	NTTDOCOMO, INC.	CR		9.2NR	Yes	No	available	No
R3‑245356	Editorial correction on TNL Configuration Info	NTTDOCOMO, INC.	CR		9.2NR	Yes	No	available	No
R3‑245357	Correction of mapped cell support list	Huawei, Ericsson, Nokia, Nokia Shanghai Bell	draftCR	Endorsement	9.2NR	Yes	No	available	No
R3‑245358	Correction of mapped cell support list	Huawei, Nokia, Ericsson, Nokia Shanghai Bell	draftCR	Endorsement	9.2NR	Yes	No	available	No
R3‑245359	Discussion on UE Location Information for NB-IoT NTN	Huawei	discussion	Agreement	9.1LTE	Yes	Yes	noted	No
R3‑245360	(TP for TS 38.413 and TS 38.300) Support MBS broadcast service	Huawei	other	Agreement	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245361	(TP for BLCR for TS 38.300) Support of regenerative payload (including LS responses to SA2)	Huawei	other	Agreement	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245362	(TP for TS 38.410) Introduce NG Removal procedure	Huawei, Nokia, Nokia Shanghai Bell, CATT, CMCC, Ericsson, Qualcomm, Xiaomi	other	Agreement	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245363	Support of UE specific SRS reservation	Huawei, CATT,Samsung, ZTE	CR	Agreement	9.2NR	No	Yes	withdrawn	Yes
R3‑245364	Clarification on TRP ID for SRS Bandwidth Aggregation	Huawei, Nokia, CMCC, CUC, ZTE	discussion	Decision	9.2NR	Yes	YesTRP ID is associated with no more than one PCI value, ARFCN value, and NR CGI value within one NG-RAN node.	noted	No
R3‑245365	Correction on Measurement Time Window	Huawei,CMCC, CUC, Ericsson	discussion	Agreement	9.2NR	Yes	No	available	No
R3‑245366	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	Yes	YesE///: It’s not critical. There has additional text in R17. Only R18 CR is needed. ZTE: Support CRs CATT: No harm to have this - Change meeting information - Add ZTE, SS as co-source	revised	No	R3‑245691
R3‑245367	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	Yes	Yes- Change meeting information - Add ZTE, SS as co-source	revised	No	R3‑245692
R3‑245368	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	Yes	Yes- Change meeting information - Add ZTE, SS as co-source - Additional place to be updated?	revised	No	R3‑245693
R3‑245369	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	Yes	Yes- Change meeting information - Add ZTE, SS as co-source	revised	No	R3‑245694
R3‑245370	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	Yes	Yes- Change meeting information - Add ZTE, SS as co-source	revised	No	R3‑245695
R3‑245371	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	Yes	Yes- Change meeting information - Add ZTE, SS as co-source - Additional place to be updated?	revised	No	R3‑245696
R3‑245372	Work plan for Additional topological enhancements for NR	NTT DOCOMO INC., AT&T	Work Plan		12.1General	Yes	No	available	No
R3‑245373	Discussion on Support of NTN Regenerative Architecture	TCL	discussion	Discussion	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245374	Discussion on Support of MBS Broadcast Service	TCL	discussion	Discussion	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245375	Inactivity Timer for Fixed Wireless Access	Nokia	CR		31.2Enhancements	Yes	NoResp in R3-245681	available	No
R3‑245376	Correction of N3IWF user location information	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR		9.2NR	Yes	No	available	No
R3‑245377	Correction of N3IWF user location information	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR		9.2NR	Yes	No	available	No
R3‑245378	Correction of N3IWF user location information	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR		9.2NR	Yes	No	available	No
R3‑245379	Introduction of AUN3 device access	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR		9.2NR	Yes	No	available	No
R3‑245380	Introduction of AUN3 device access	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR		9.2NR	Yes	No	available	No
R3‑245381	Discussion on Wireless Access Backhaul	NTTDOCOMO, INC.	discussion		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245382	Corrections on SL relay procedure	LG Electronics, Samsung, Nokia, Nokia Shanghai Bell	CR	Agreement	9.2NR	Yes	Yes- In case of the PDCP duplication, the gNB-CU-UP should not request the discard of the duplicated DL data to the gNB-DU for the direct path based on the Downlink Data Delivery Status frame received from the gNB-DU for the indirect path, and only act as specified in TS 38.323 [xx]. - Add E///, HW, CATT as co-source	revised	No	R3‑245708
R3‑245383	Discussion on enhancements for WAB	CANON Research Centre France	discussion	Discussion	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245384	Discussion on the PDCP SN gap report handling during UE’s handover	Huawei, CATT, Xiaomi, China Telecom, LG Electronics	discussion		9.2NR	Yes	YesNEC: Fine to Opt2, the behavior in the source node needs to be described LGE, E///: Should not go for Opt2 E///: Opt3 may not need RAN2 impact QC: It has to be sent from source to target, Opt1 works Xiaomi: Prefer Opt1 Lenovo: The scenario is not critical, if we have to solve the issue, Opt1 for both UL and DL Nok: The scenario is not critical and prefer Opt3 CATT: The scenario is not critical, prefer Opt2 SS, CMCC: Prefer Opt1 CB: # 22_PDCPSN - Send LS to RAN2 to check whether Opt3 is feasible or not? (moderator - HW)	noted	No
R3‑245385	Introduction of 2Rx XR devices support [2Rx_XR_Device]	Huawei, Qualcomm, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, China Telecom	CR		9.2NR	Yes	Yes	endorsed	No
R3‑245386	Discussion on SA2’s LS (S2-2409444) on multi-modality awareness	Huawei	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245387	[Draft] Reply LS on multi-modality awareness at RAN	Huawei	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245388	Correction on BAP mapping configuration for IAB	Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT	CR		9.2NR	Yes	Yes	noted	No
R3‑245389	Correction on BAP mapping configuration for IAB	Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT	CR		9.2NR	Yes	Yes	noted	No
R3‑245390	Correction on BAP mapping configuration for IAB	Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT	CR		9.2NR	Yes	Yes	noted	No
R3‑245391	(TPs for TS 38.300/38.413) Architecture and Access control for WAB	Huawei	other		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245392	(TP for TS 38.300) Discussion on WAB related procedures	Huawei	other		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245393	(TP for TS 38.300) Discussion on the architecture for NR Femto	Huawei	other		12.35G Femto	Yes	No	available	No
R3‑245394	(TP for TS 38.300) Access control for NR Femto	Huawei	other		12.35G Femto	Yes	No	available	No
R3‑245395	(TP for BLCR for SON for TS 38.300) MRO enhancements for LTM and CHO with candidate SCGs	Ericsson	other	Agreement	10.2MRO Enhancements	Yes	No	available	No
R3‑245396	Discussion on SON enhancements for network slicing	Ericsson, AT&T, Jio	discussion	Agreement	10.3.2Network Slicing	Yes	No	available	No
R3‑245397	On MDT enhancements for Network Slicing	Ericsson, AT&T, Jio	discussion	Agreement	10.3.2Network Slicing	Yes	No	available	No
R3‑245398	Further discussion on RACH optimization for SDT	Ericsson	discussion		10.4R18 leftovers	Yes	No	available	No
R3‑245399	(TP for BLCR for SON for TS 38.413) UHI for SCG activation-deactivation	Ericsson	other	Agreement	10.4R18 leftovers	Yes	No	available	No
R3‑245400	Clarification of the usage of the UE History Information	Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone	CR	Agreement	9.2NR	Yes	Yes	endorsed	No
R3‑245401	LTM interwork with L3 measurements	Nokia, NTT Docomo	CR	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No		R3‑244090
R3‑245402	Functional Aspects of WAB-Nodes	Ericsson	discussion	Agreement	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245403	Reply to SA2 Regarding WAB-MT Access Control and Additional ULI for WAB-Nodes	Ericsson	discussion	Agreement	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245404	Discussion on interfaces mobility aspects for regenerative payload	THALES	discussion	Discussion	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245405	Correction of Unavailable GUAMI in AMF Status Indication message	Huawei	CR		9.2NR	Yes	No	available	No
R3‑245406	Correction of Unavailable GUAMI in AMF Status Indication message	Huawei	CR		9.2NR	Yes	No	available	No
R3‑245407	Correction of Unavailable GUAMI in AMF Status Indication message	Huawei	CR		9.2NR	Yes	No	available	No
R3‑245408	Correction of message level criticality of E1AP procedures	Huawei	CR	Agreement	31.1Corrections	Yes	Yes- Use CPUP split WI code - Update the coversheet, remove proposal in reason for change - Remove Impact Analysis	revised	No	R3‑245712
R3‑245409	Correction of IE criticality in Bearer Context Setup Response and Modification Response message	Huawei	CR	Agreement	31.1Corrections	Yes	YesE///, Nok: Align to ASN.1 seems better	noted	No
R3‑245410	Discussion on UE-Sat-UE communications	THALES	discussion	Information	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245411	Discussion on the LS reply on AI/ML for NG-RAN Energy Saving Energy Cost index	Huawei	discussion	Decision	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245412	[Draft] LS on Rel-19 Enhancements of AI/ML for NG-RAN in split architecture	Huawei	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	withdrawn	Yes
R3‑245413	Discussion on the LS on terminology definitions for AI-ML in NG-RAN	Huawei	discussion	Decision	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245414	Discussion on the Reply LS on improved KPIs involving end-to-end data volume transfer time analytics	Huawei	discussion	Decision	8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245415	[Draft] LS on per-UE UE performance metrics	Huawei	LS out	Agreement	8.3Left over LSs / pending actions	Yes	Yes	withdrawn	Yes
R3‑245416	Stage 3 corrections for UAV	Huawei, CATT, Nokia, ZTE	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245417	(TP for AI/ML BLCR to TS 38.423) Discussion on the AI/ML-based Network Slicing	Huawei	other	Agreement	11.2AI/ML enabled Slicing	Yes	Yes	noted	No
R3‑245418	AI/ML-based Coverage and Capacity Optimization	Huawei	discussion	Decision	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245419	TPs for AI/ML BLCR to TS 38.743 and AI/ML BLCR to TS 38.423 for AI/ML-based Coverage and Capacity Optimization	Huawei	other	Agreement	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245420	AI/ML-based Mobility Optimization in NR-DC	Huawei	discussion	Decision	11.4R18 leftovers	Yes	Yes	noted	No
R3‑245421	(TPs for AI/ML BLCR to TS 38.473 and AI/ML BLCR to TS 37.483) Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases	Huawei	other	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245422	On Continuous MDT for AI/ML	Huawei	discussion	Decision	11.4R18 leftovers	Yes	No	available	No
R3‑245423	Discussion on RAN3 impacts for Direct AI/ML positioning	Huawei	discussion	Decision	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245424	Discussion on RAN3 impacts for AI/ML assisted positioning	Huawei	discussion	Decision	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245425	Discussions on enhancements for AIML support for CCO	Jio	discussion	Decision	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245426	Further discussions on enhancements for AIML support for CCO	Jio, Deutsche Telekom	discussion	Discussion	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245427	Discussion on AIML based Network Slicing	Jio	discussion	Discussion	11.2AI/ML enabled Slicing	Yes	Yes	withdrawn	Yes
R3‑245428	Enhancements for AI ML NG-RAN mobility	Jio	discussion	Discussion	11.4R18 leftovers	No	Yes	withdrawn	Yes
R3‑245429	(TP for TS 36.300) Discussion on UE Location for NTN NB-IoT UE	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell	other	Agreement	9.1LTE	Yes	Yes	noted	No
R3‑245430	Discussion on NG-RAN AI/ML for Network Slicing	Qualcomm Incorporated	discussion	Agreement	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245431	Discussion on AI/ML enabled CCO	Qualcomm Incorporated	discussion	Agreement	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	Yes	noted	No
R3‑245432	Discussion on Continuous MDT	Qualcomm Incorporated	discussion	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245433	(TP for TS38.300) Discussion on Support for NR NTN MBS Broadcast Service	Qualcomm Incorporated	other	Agreement	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245434	(TP for TS 38.300) Discussion on RAN Signaling impacts for NR NTN Regenerative Payload	Qualcomm Incorporated	other	Agreement	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245435	Discussion on incoming LSs on XR	Lenovo	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245436	(TP for SON BLCR for 38.300) Discussion on MRO for LTM	Lenovo	other		10.2MRO Enhancements	Yes	No	available	No
R3‑245437	(TP for SON BLCR for 37.340) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s)	Lenovo	other		10.2MRO Enhancements	Yes	No	available	No
R3‑245438	Discussion on MRO for intra-NTN mobility	Lenovo	discussion		10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245439	Discussion on MRO for R18 leftovers	Lenovo	discussion		10.4R18 leftovers	Yes	No	available	No
R3‑245440	(TP to BLCR 38.423) Discussion on AIML based network slicing	Lenovo	other		11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245441	(TP to BLCR 38.473) Discussion on AIML based CCO	Lenovo	other		11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245442	(TP to BLCR 38.423) Discussion on UE performance feedback in AIML for NR-DC	Lenovo	other		11.4R18 leftovers	Yes	No	available	No
R3‑245443	(TP to BLCR 38.473 and 37.483) Discussion on split architecture related issues for Rel18 use cases	Lenovo	other		11.4R18 leftovers	Yes	Yes	noted	No
R3‑245444	(TP to BLCR 37.340) AIML for NR-DC	Lenovo, CATT, ZTE Corporation, Samsung	other		11.4R18 leftovers	Yes	No	available	No
R3‑245445	(TP to BLCR 38.401) AIML for RAN in split architecture	Lenovo, CATT, ZTE Corporation	other		11.4R18 leftovers	Yes	No	available	No
R3‑245446	Architecture and configuration for WAB-node	Lenovo	discussion		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245447	Integration and migration for WAB node	Lenovo	discussion		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245448	Architecture and access control for NR Femto	Lenovo	discussion		12.35G Femto	Yes	No	available	No
R3‑245449	(TP to 38.300) On NR Femto	Lenovo	other		12.35G Femto	Yes	No	available	No
R3‑245450	Broadcast service area indication and service continuity in NTN	Lenovo	discussion		14.2Support MBS broadcast service	Yes	No	available	No
R3‑245451	Interface management for regenerative payload in NTN	Lenovo	discussion		14.3Support of Regenerative payload	Yes	No	available	No
R3‑245452	On RAN architecture of ambient IoT	Lenovo	discussion		16.2RAN Architecture	Yes	No	available	No
R3‑245453	On basic procedures of ambient IoT	Lenovo	discussion		16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245454	Context Management and Data Transport of Ambient IOT	Lenovo	discussion		16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245455	Discussion on On-demand SSB for SCell	Lenovo	discussion		17.2Support on-demand SSB SCell operation	Yes	No	available	No
R3‑245456	Discussion on On-demand SIB1 for Idle/Inactive UE	Lenovo	discussion		17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245457	AIML for gNB assisted positioning	Lenovo	discussion		20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245458	[TP to BLCR for TS 38.300] Inter-CU LTM	Lenovo	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245459	[TP for TS 38.423] Inter-CU LTM	Lenovo	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245460	General aspects of inter-CU SCG LTM	Lenovo	discussion		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245461	AI/ML based positioning accuracy enhancements	Qualcomm Incorporated	discussion		20.2Support Positioning Accuracy Enhancements	Yes	Yes	noted	No
R3‑245462	Correction to Requested DL PRS Transmission Characteristics	Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia	CR		9.2NR	Yes	YesSS: Fine with first two changes, comment on the third change Further check on the third change? Mention BC or NBC in the coversheet.	revised	No	R3‑245738	R3‑244393
R3‑245463	Correction to Requested DL PRS Transmission Characteristics	Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia	CR		9.2NR	Yes	Yes	revised	No	R3‑245739
R3‑245464	Support of UE specific SRS reservation	Huawei, CATT,Samsung, ZTE	CR	Agreement	9.2NR	No	Yes	withdrawn	Yes
R3‑245465	Support of UE specific SRS reservation	Huawei, CATT,Samsung, ZTE	CR	Agreement	9.2NR	Yes	Yes	noted	No		R3‑244227
R3‑245466	Discussion on SA2 LS regarding Multimodality application and protocol impacts	Ericsson	discussion	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245467	Addition of MMSID	Ericsson	CR	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245468	Addition of MMSID	Ericsson	CR	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245469	Addition of MMSID	Ericsson	CR	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245470	LS reply on multi-modality awareness at RAN	Ericsson	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245471	Correction of UE Rx-Tx Time difference measurements	Ericsson, Polaris, CATT, Huawei	CR	Agreement	9.2NR	Yes	YesNok: Not convinced on the usage of those new Ies	noted	No
R3‑245472	Work Plan for Rel-19 on AI/ML for PHY (Positioning)	Ericsson (Rapporteur)	Work Plan	Approval	20.1General	Yes	Yes	noted	No
R3‑245473	Discussion on RAN3 impacts to support AI/ML Positioning accuracy enhancements	Ericsson	discussion	Discussion	20.2Support Positioning Accuracy Enhancements	Yes	Yes	noted	No
R3‑245474	Support of AI/ML Positioning	Ericsson	CR	Endorsement	20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245475	Discussion of LPWUS impacts on NG-RAN architecture	Ericsson	discussion	Discussion	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245476	[DRAFT] Reply LS on UE Location Information for NB-IoT NTN	Ericsson, Huawei, Apple, Thales	LS out	Agreement	9.1LTE	Yes	Yes	noted	No		R3‑244367
R3‑245477	Clarification of the description of the UE History Information	Nokia, ZTE, CMCC	draftCR	Endorsement	9.2NR	Yes	YesE///, HW: Only change the title Check with TS38.300 rapporteurs whether changing the title of 15.5.4 as UE History Information in order to reflect the content properly and corrected by the rapporteur.	noted	No
R3‑245478	Correction of a wrong description of the S-NG-RAN node Counter Check procedure	Nokia	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245479	Correction of a wrong description of the S-NG-RAN node Counter Check procedure	Nokia	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245480	Correction of a wrong description of the S-NG-RAN node Counter Check procedure	Nokia	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245481	Correction of a wrong description of the S-NG-RAN node Counter Check procedure	Nokia	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245482	E-SMLC OAM Configuration for IoT NTN	Ericsson, Thales, Huawei	draftCR	Endorsement	9.1LTE	Yes	Yes	noted	No		R3‑244368
R3‑245483	WI Work plan for R19 Network Energy Savings	Ericsson	Work Plan		17.1General	Yes	YesAdditional BL CR assignment: TS38.401 QC (if needed)	noted	No		R3‑244347
R3‑245484	Coarse UE Location Information Reporting - S1AP Impacts	Ericsson	discussion	Discussion	9.1LTE	Yes	Yes	noted	No
R3‑245485	Correction of mapped cell support list	Ericsson, Huawei, Nokia, Nokia Shanghai Bell	draftCR	Endorsement	9.1LTE	Yes	Yes	noted	No
R3‑245486	NR Femto - Stage 2 Aspects	Ericsson	discussion	Discussion	12.35G Femto	Yes	No	available	No
R3‑245487	NR Femto - Stage 2 TP	Ericsson	other	Agreement	12.35G Femto	Yes	No	available	No
R3‑245488	Stage 2 correction for AI/ML for NG-RAN	Qualcomm Incorporated, ZTE, Reliance JIO	draftCR	Approval	9.2NR	Yes	Yes	noted	No
R3‑245489	Discussion on Time Reference Distribution Subscription for UEs in LTE	Qualcomm Incorporated, Vodofone Group Plc, Vodofone Telekomünikasyon A.S.	discussion	Agreement	31.1Corrections	Yes	NoHW: OK to align with SA2, consider DL NAS TRANSPORT message as well? CB: # 9_TimeReference - Comments on CR coversheet: core network box, the wording in the reason for change - Which messages to include this indication? - ASN.1 is missing (moderator - QC)	available	No
R3‑245490	Broadcast Service Area for NR NTN	Ericsson, SES, ESA	discussion	Discussion	14.2Support MBS broadcast service	Yes	No	available	No		R3‑244373
R3‑245491	Broadcast Service Area for NR NTN - NGAP Impacts	Ericsson, SES, ESA	other	Agreement	14.2Support MBS broadcast service	Yes	No	available	No		R3‑244374
R3‑245492	uRLLC	Qualcomm Incorporated	CR	Approval	31.1Corrections	No	Yes	withdrawn	Yes
R3‑245493	NG Removal – Stage 2 Description	Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Xiaomi, CATT, Qualcomm Incorporated	other	Agreement	14.3Support of Regenerative payload	Yes	No	available	No		R3‑244639
R3‑245494	Further Discussion on NTN Regenerative Payload Issues in Rel-19	Ericsson, Thales, SES, ESA, Sateliot	discussion	Discussion	14.3Support of Regenerative payload	Yes	No	available	No		R3‑244375
R3‑245495	[DRAFT] Reply LS on Support of Regenerative Payload Issues in Rel-19	Ericsson	LS out	Agreement	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245496	Discussion on RAN3 impacts to support enhancements for CLI handling for SBFD	Ericsson	discussion	Agreement	19.2Support CLI Handling	Yes	No	available	No
R3‑245497	Enhancements for CLI handling in SBFD	Ericsson	CR	Approval	19.2Support CLI Handling	Yes	No	available	No
R3‑245498	Xn impact of On-demand SIB1 for UEs in idle/inactive mode	Ericsson	other		17.3Support on-demand SIB1 for UEs	Yes	Yes	noted	No		R3‑244349
R3‑245499	Support for AI/ML based Network Slicing	Ericsson, InterDigital	discussion	Agreement	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245500	(TP for BLCR for AIML for 38.423) Support for AI/ML based Network Slicing	Ericsson, InterDigital	other	Agreement	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245501	AI/ML support for CCO	Ericsson, Deutsche Telekom, InterDigital	discussion	Agreement	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	Yes	noted	No
R3‑245502	Signalling aspects of AI/ML support for CCO	Ericsson, Deutsche Telekom, InterDigital	discussion	Agreement	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245503	(TP to 38.423) - AI/ML support for CCO	Ericsson, Deutsche Telekom, InterDigital	other	Agreement	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245504	(TP to 38.473) - AI/ML support for CCO	Ericsson, Deutsche Telekom, InterDigital	other	Agreement	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245505	Split architecture support for Release 18 use cases	Ericsson, Jio, InterDigital	discussion	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245506	(TP to 38.473) - Split architecture support for Release 18 use cases	Ericsson, Jio, InterDigital	other	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245507	(TP to 37.483) - Split architecture support for Release 18 use cases	Ericsson, Jio, InterDigital	other	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245508	AI/ML support for NR-DC	Ericsson, Jio	discussion	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245509	(TP to 38.423) - AI/ML support for NR-DC	Ericsson, Jio	other	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245510	Discussion on Continuous MDT and improved KPIs involving end-to-end data volume transfer time analytics	Ericsson	discussion	Agreement	11.4R18 leftovers	Yes	Yes	noted	No
R3‑245511	Reply LS on improved KPIs involving end-to-end data volume transfer time analytics	Ericsson	LS out	Agreement	8.3Left over LSs / pending actions	Yes	YesMove to 8.3 Resp in R3-245680 Nok, CATT: No need to send LS to SA5, correlation ID can be discussed in R19 AI RAN WI Noted The correlation UE ID can be continued to be discussed in R19 AI/ML for NG-RAN WI and contact with SA5 if needed. The correlation UE ID can be continued to be discussed in R19 AI/ML for NG-RAN and contact with SA5 if needed.	noted	No
R3‑245512	Regarding the LS on number of UEs in SDT	Ericsson	discussion	Agreement	8.1New Incoming LSs	Yes	YesNok, CATT: RAN3 can reply to SA5 and share same view as E/// CATT: CN knows how many UE in active mode and how many UEs in data transmission, no other information needed from RAN HW, ZTE: RAN2 will discuss this incoming LS in this meeting, wait for RAN2 progress	noted	No
R3‑245513	Discussion about Stage 2 corrections in AI/ML for NG-RAN	Ericsson, InterDigital, Nokia	discussion	Agreement	9.2NR	Yes	Yes	noted	No
R3‑245514	Stage 2 correction for AI/ML for NG-RAN	Ericsson, Huawei, Nokia, InterDigital	draftCR	Endorsement	9.2NR	Yes	Yes	noted	No		R3‑243465
R3‑245515	(TP for AI/ML BLCR to TS38.423) Continuous MDT collection targeting the same UE across RRC states	Ericsson	other	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245516	Stage-2 support for LTM L2 reset	Ericsson, Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, CATT	CR		9.2NR	Yes	YesHW: The same change needed for inter-DU L2 reset configuration QC: Not convinced on inter-DU case	revised	No	R3‑245724
R3‑245517	F1 impact of On-demand SIB1 for UEs in idle/inactive mode	Ericsson	discussion		17.3Support on-demand SIB1 for UEs	Yes	No	available	No		R3‑244348
R3‑245518	(TP to BL CR for TS 38.423) support of LP-WUS	CMCC	other	Approval	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245519	Discussion on Support of regenerative payload for NR NTN	CMCC	discussion	Discussion	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245520	Discussion on Supporting MBS broadcast service for NR NTN	CMCC	discussion	Discussion	14.2Support MBS broadcast service	Yes	No	available	No
R3‑245521	Discussion on inter-CU LTM	CMCC	discussion	Discussion	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245522	(TP to BL CR for TS 38.300) Inter-CU LTM procedure	CMCC	other	Approval	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245523	Correction for the reference specification on UE History Information for Rel-16	CMCC, Huawei, CATT, ZTE	CR	Approval	9.2NR	Yes	Yes	noted	No
R3‑245524	Correction for the reference specification on UE History Information for Rel-17	CMCC, Huawei, CATT, ZTE	CR	Approval	9.2NR	Yes	Yes	noted	No
R3‑245525	Correction for the reference specification on UE History Information for Rel-18	CMCC, Huawei, CATT, ZTE, Nokia	CR	Approval	9.2NR	Yes	Yes- Change Cat. A to Cat. F	revised	No	R3‑245743
R3‑245526	Discussion on MRO enhancements for LTM	CMCC	discussion	Discussion	10.2MRO Enhancements	Yes	No	available	No
R3‑245527	Discussion on mechanism for UAV regulation	CMCC, ZTE, CATT, China Telecom, NTT DOCOMO	discussion	Discussion	31.2Enhancements	Yes	NoQC: Send LS to SA2 to ask for more details ZTE: Support the requirement E///: UAV was supported since R17 in CN. Non-UAV Aerial UE conception does not exist which needs to be checked by SA2. SA1 should look at this first. HW: Positive on the intention and requirement. Check with SA2 whether the current spec can support such requirement. Nok: the requirement needs to be checked by SA2 CATT: It’s commercial requirement, it’s fair to send LS to SA2 to check the solution involved SS: Support to send LS to SA2, especially on p2. CB: # 10_UAVRegulation - Send LS to SA2 on the requirement and feasibility of the solution, cc SA, RAN (moderator - CMCC)	available	No
R3‑245528	Correction on mechanism for UAV regulation	CMCC	CR	Approval	31.2Enhancements	Yes	Yes	noted	No
R3‑245529	Work Plan for Ambient IoT SI	CMCC, Huawei, T-Mobile USA	Work Plan	Information	16.1General	Yes	Yes	noted	No
R3‑245530	Discussion on RAN Architecture for Ambient IoT	CMCC	discussion	Discussion	16.2RAN Architecture	Yes	No	available	No
R3‑245531	Discussion on signalling procedure for topology1	CMCC	discussion	Discussion	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245532	Discussion on signalling procedure for topology2	CMCC	discussion	Discussion	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245533	Discussion on locating Ambient IoT device	CMCC	discussion	Discussion	16.4Others	Yes	Yes	noted	No
R3‑245534	MHI and UHI Enhancement for SCG Deactivation Activation	CMCC, Huawei, CATT, Ericsson, Lenovo, ZTE	discussion	Discussion	10.4R18 leftovers	Yes	No	available	No
R3‑245535	Discussion on architecture and access control for NR Femto	ZTE corporation	discussion	Decision	12.35G Femto	Yes	No	available	No
R3‑245536	(TP for BLCR 38.300&38.410)NR Femto	ZTE corporation	discussion	Decision	12.35G Femto	Yes	No	available	No
R3‑245537	Discussion on Information exchange for SBFD	ZTE corporation	discussion	Decision	19.2Support CLI Handling	Yes	No	available	No
R3‑245538	(TP for BLCR 38.300&420&423&473-36.423-37.340) SBFD	ZTE corporation	discussion	Decision	19.2Support CLI Handling	Yes	No	available	No
R3‑245539	Discussion on Timing Aspects for AIML support in CCO	Jio, NOKIA	discussion	Decision	11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245540	Data Collection Aspects for AIML support in CCO	Jio	discussion		11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245541	X2 correction for EN-DC Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.1LTE	Yes	YesHW, ZTE, CATT: Not convinced this is needed. It’s clear enough. CATT: The description in IE semantic description is clear enough.	noted	No
R3‑245542	X2 correction for EN-DC Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.1LTE	Yes	Yes	noted	No
R3‑245543	X2 correction for EN-DC Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.1LTE	Yes	Yes	noted	No
R3‑245544	X2 correction for Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.1LTE	Yes	Yes	noted	No
R3‑245545	X2 correction for Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.1LTE	Yes	Yes	noted	No
R3‑245546	X2 correction for Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.1LTE	Yes	Yes	noted	No
R3‑245547	X2 correction for Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.1LTE	Yes	Yes	noted	No
R3‑245548	Xn correction for Data Collection Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.2NR	Yes	YesHW, ZTE: Similar issue as we discussed this morning	noted	No
R3‑245549	Xn correction for Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.2NR	Yes	Yes	noted	No
R3‑245550	Xn correction for Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.2NR	Yes	Yes	noted	No
R3‑245551	Xn correction for Resource Status Reporting Initiation	Ericsson, Jio, InterDigital	CR	Agreement	9.2NR	Yes	Yes	noted	No
R3‑245552	Stage 2 correction for network slice support during XN handover	Ericsson, Jio	draftCR	Endorsement	9.2NR	Yes	No	available	No
R3‑245553	Stage 2 correction for network slice support during XN handover	Ericsson, Jio	draftCR	Endorsement	9.2NR	Yes	No	available	No
R3‑245554	Stage 2 correction for network slice support during XN handover	Ericsson, Jio	draftCR	Endorsement	9.2NR	Yes	No	available	No
R3‑245555	Stage 2 correction for network slice support during XN handover	Ericsson, Jio	draftCR	Endorsement	9.2NR	Yes	No	available	No
R3‑245556	Discussion on AIML based Network Slicing	Jio	discussion	Decision	11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245557	Scenarios and open points for AI/ML-based Coverage and Capacity Optimization (CCO)	Nokia, Jio, Telecom Italia	discussion		11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245558	Initial discussion on stage 3 impact for AI/ML-based Coverage and Capacity Optimization (CCO)	Nokia, Jio, Deutsche Telekom	discussion		11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245559	Introduction of AIML-based CCO	Nokia	CR		11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245560	On-Demand SSB SCell operation for UEs in connected mode	Nokia	discussion		17.2Support on-demand SSB SCell operation	Yes	No	available	No
R3‑245561	Further thoughts on open Issues in support of On-Demand SIB1	Nokia	discussion		17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245562	Initial discussion on RAN3 work on Evolution of NR duplex operation: Sub-band full duplex (SBFD)	Nokia	discussion		19.2Support CLI Handling	Yes	No	available	No
R3‑245563	Triggering LTM without L1 measurements UE capability	Ericsson, Vodafone	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245564	F1 support for L3 measurements-based LTM	Ericsson, Vodafone	CR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245565	Stage-2 updates for L3 measurements-based LTM	Ericsson, Vodafone	CR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245566	Rel-18 correction on LTM with gNB-CU-UP change	LG Electronics Inc.	CR	Approval	9.2NR	Yes	No	available	No		R3‑244474
R3‑245567	Rel-18 correction on Intra-CU LTM procedure	LG Electronics Inc.	CR	Approval	9.2NR	Yes	No	available	No
R3‑245568	Continuing discussions on Inter-CU LTM signaling design	LG Electronics Inc.	discussion	Decision	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245569	Baseline CR for introducing Rel-19 Mobility enhancement in E1AP	LG Electronics Inc.	CR	Approval	13.2Support for inter-CU LTM	Yes	No	available	No		R3‑244477
R3‑245570	(TP for NR_Mob_Ph4 TS 38.423)	LG Electronics Inc.	other	Approval	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245571	Discussions on NG management and Inactive support	LG Electronics Inc.	discussion	Decision	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245572	(TP for NR_NTN_Ph3 TS 38.300)	LG Electronics Inc.	other	Approval	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245573	[TP for TR 38.769] Protocol Stack Option for Topology 2	Nokia	other		16.2RAN Architecture	Yes	Yes	noted	No
R3‑245574	Inventory Signalling reusing Paging procedures for AIoT Topology 2	Nokia	discussion		16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245575	[TP for TR 38.769] Inventory Signalling reusing Paging procedures for AIoT Topology 2	Nokia	other		16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245576	[TP for TR 38.769] Data Transport and Context Management for AIoT	Nokia	other		16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245577	Support of AUN3 devices	Ericsson, BT, China Unicom	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245578	Support of AUN3 devices	Ericsson, BT, China Unicom	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245579	Further discussionis on AIoT RAN architecture	Ericsson	discussion	Agreement	16.2RAN Architecture	Yes	No	available	No
R3‑245580	[TP for TR 38.769] on AIoT Architecture aspects	Ericsson	other	Agreement	16.2RAN Architecture	Yes	Yes	noted	No
R3‑245581	[TP for TR 38.769] Elements for AIoT RAN – AIoT CN communication and overall signalling	Ericsson	other	Agreement	16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245582	[TP for TR 38.769] On locating AIoT devices	Ericsson	other	Agreement	16.4Others	Yes	No	available	No
R3‑245583	RAN3 issues related to SBFD	Charter Communications, Inc	discussion	Agreement	19.2Support CLI Handling	Yes	No	available	No
R3‑245584	Discussion on AIML for split architecture	NTT DOCOMO INC..	discussion	Discussion	11.4R18 leftovers	Yes	No	available	No
R3‑245585	Discussion on inter-CU LTM non-DC case	NTT DOCOMO INC..	discussion	Discussion	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245586	Discussion on Xn impact for NR NTN regenerative payload	NTT DOCOMO INC..	discussion	Discussion	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245587	Addition of RRC segmentation information for NR-DC QMC	Nokia	CR		9.2NR	Yes	NoResp in R3-245679	available	No
R3‑245588	Discussion on NG interface management through ISL	ETRI	discussion	Discussion	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245589	Correction on broadcast reception for eRedCap UE [RedcapMBS]	Huawei, Qualcomm Incorporated, ZTE, CBN	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245590	Correction on broadcast reception for eRedCap UE [RedcapMBS]	Huawei, Qualcomm Incorporated, ZTE, CBN	CR	Agreement	9.2NR	Yes	No	available	No
R3‑245591	Consideration on SDT signalling optimization for partial context transfer [SDTnetworkSolution]	Huawei	discussion	Agreement	8.3Left over LSs / pending actions	Yes	YesResp in R3-245677	noted	No
R3‑245592	Introduction of SDT network-based solution [SDTnetworkSolution]	Huawei	draftCR	Agreement	8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245593	Introduction of SDT network-based solution [SDTnetworkSolution]	Huawei	CR	Agreement	8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245594	Introduction of SDT Network-based solution [SDTnetworkSolution]	Huawei	CR	Agreement	8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245595	[DRAFT] Reply LS on SDT signalling optimization for partial context transfer	Huawei	LS out	Agreement	8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245596	Discussion on the reply LS on Terminology Definitions for AI-ML in NG-RAN	Nokia	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245597	[Draft] Reply LS on terminology definitions for AI-ML in NG-RAN	Nokia	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245598	Correction on AI/ML Terminology	Nokia	draftCR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245599	Correction on AI/ML Terminology	Nokia	CR	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245600	Discussion on the LS reply from SA5 on AI/ML for NG-RAN Energy Saving Energy Cost Index	Nokia	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245601	[Draft] Reply LS to LS reply on AI/ML for NG-RAN Energy Saving Energy Cost index	Nokia	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245602	OAM Requirements on Energy Cost index	Nokia, Jio, Telecom Italia	draftCR	Endorsement	9.2NR	Yes	YesNEC: Need more time to check the wording	noted	No
R3‑245603	Extension of Data Collection Procedures for AI/ML Slicing	Nokia, Jio	discussion		11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245604	AI/ML Slicing Support in Data Collection Reporting procedures	Nokia, Jio	CR		11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245605	Discussion on Energy Cost Reporting in Split Architecture	Nokia, Deutsche Telekom, Jio, Telecom Italia	discussion		11.4R18 leftovers	Yes	No	available	No
R3‑245606	Procedures over F1 for the exchange of Energy Cost index	Nokia, Deutsche Telekom, Jio, Telecom Italia	CR		11.4R18 leftovers	Yes	No	available	No
R3‑245607	[Draft] LS on New Energy Consumption Measurement for gNB-DU	Nokia, Deutsche Telekom, Jio, Telecom Italia	LS out	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245608	Procedures for AI/ML Mobility Optimization in NR-DC	Nokia, Jio	discussion		11.4R18 leftovers	Yes	No	available	No
R3‑245609	Discussion on the Rel-18 UE Performance measurements	Nokia	discussion		11.4R18 leftovers	Yes	No	available	No
R3‑245610	[Draft] LS on the Feasibility of new measurement that Averages UE Throughput in the UL	Nokia	LS out	Agreement	11.4R18 leftovers	Yes	No	available	No
R3‑245611	Continuous Management-based MDT	Nokia, Qualcomm, Jio, Telecom Italia, Deutsche Telekom	discussion		11.4R18 leftovers	Yes	No	available	No
R3‑245612	Support for AI/ML Positioning	Nokia	discussion		20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245613	AI/ML Assisted positioning case 3a	Nokia	draftCR		20.2Support Positioning Accuracy Enhancements	Yes	No	available	No
R3‑245614	Discussion on Transmission Bandwidth less than 5MHz	China Telecom, ZTE	discussion	Discussion	9.2NR	Yes	YesZTE: Related to RAN4 and RAN2 E///: nrb12 and nrb20 are not included in TS38.104. There is one to one mapping relation with NRFCN. The change is not correct. Noted To be further checked…	noted	No
R3‑245615	Correction on SCSs of 480kHz for FR2-2 in TS 36.423	China Telecom,ZTE, CATT,China Unicom	CR	Approval	9.2NR	Yes	YesE///: Could not find the clue that scs480 is not applied in EN-DC. Whether it is only used for NR? CT: See WI summary CB: # 23_SCSValues - Check the details (moderator - CT)	noted	No
R3‑245616	Workplan for Rel-19 SON_MDT Enhancement	China Unicom, CMCC	Work Plan		10.1General	Yes	No	available	No
R3‑245617	Discussion on MRO Enhancements	China Unicom	discussion		10.2MRO Enhancements	Yes	No	available	No
R3‑245618	Discussion on SONMDT enhancements for NTN mobility	China Unicom	discussion		10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245619	Discussion on SONMDT enhancements for network slicing	China Unicom	discussion		10.3.2Network Slicing	Yes	No	available	No
R3‑245620	Correction on SCSs of 480kHz for FR2-2 in TS 36.423	China Telecom, ZTE, CATT, China Unicom	CR	Approval	9.2NR	Yes	Yes	noted	No
R3‑245621	(TP for MDT BLCRs for TS38.413, TS38.423, TS37.320) SON for Intra-NTN mobility	Huawei	discussion		10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245622	Discusson on the reply LS on MDT configuration control in NR-DC	Huawei	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245623	[draft] Reply LS on MDT configuration control in NR-DC	Huawei	LS out	Agreement	8.1New Incoming LSs	Yes	YesE///: CT4 should be in “to” list Nok: Slightly prefer not to send reply LS - Move CT4 in “to” list - Add: According to 3GPP TR 21.801 v.18.0.0 Annex K, Table K.1 (first row), “master” is considered non-inclusive “when used in ‘master / slave’ context”. This is not the case in Dual Connectivity, where the SN is the Secondary Node. - RAN3 would like SA5 and CT4 to retain the previous definition of the term “MN” meaning “Master node” to avoid misalignment and misleading between groups. - To SA5 and CT4 - ACTION: RAN3 kindly asks SA5 and CT4 to retain the previous definition of the term “MN” as “Master node” and update their specifications accordin	revised	No	R3‑245684
R3‑245624	Correction on MDT configuration control in NR-DC	Huawei	CR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245625	Correction on MDT configuration control in NR-DC	Huawei	CR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245626	Discussion on L3 measurement based LTM support over F1	Huawei	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245627	Support of L3 measurement based LTM over F1	Huawei	CR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245628	Support of L3 measurement based LTM over F1	Huawei	CR		8.1New Incoming LSs	No	Yes	withdrawn	Yes
R3‑245629	Support of L3 measurement based LTM over F1	Huawei	draftCR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245630	[draft] Repy LS on L3 measurement based LTM support over F1	Huawei	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245631	Support of L3 measurement based LTM over F1	Huawei	CR	Agreement	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245632	Option 2: Correction on DU collecting and reporting of DL LBT failure information	CATT, Ericsson, Nokia	CR	Agreement	9.2NR	Yes	YesZTE, Lenovo: Prefer Opt2 - Add HW, SS, ZTE as co-sourc	revised	No	R3‑245700
R3‑245633	Discussion on LP-WUS subgrouping	Samsung	other	Discussion	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245634	Work plan for enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN	ZTE Corporation, NEC	Work Plan	Endorsement	11.1General	Yes	YesThe assignment of the BLCR: 38.300 NEC 38.401 CMCC 38.420 China Telecom 38.423 ZTE 38.470 Nokia 38.473 Ericsson 37.340 Huawei 37.480 CATT 37.483 Samsung 38.413 (if any) Lenovo 37.320 (if any) Qualcomm	noted	No
R3‑245635	(TP to BLCR for TS 38.413, 38.423, 38.473) LP-WUS Assistance Information to support subgrouping	Samsung	other	Approval	18.2Support LP-WUS Indicating Paging Monitoring	Yes	No	available	No
R3‑245636	(TP for TS 38.300) Support of 5G Femto	LG Electronics	other		12.35G Femto	Yes	No	available	No
R3‑245637	Access control and location information in WAB	LG Electronics	discussion		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245638	Discussion on RAN impact for Ambient IoT	LG Electronics	discussion		16.2RAN Architecture	Yes	No	available	No
R3‑245639	Discussion on 5G femto	NTTDOCOMO, INC.	discussion		12.35G Femto	Yes	No	available	No
R3‑245640	Discussion on RAN2 impact of WAB	China Telecom	discussion		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245641	On Xn and NG interface management	China Telecom	discussion		12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245642	Time Reference Distribution Information in S1AP	Qualcomm, Vodafone Group Plc, Vodafone Telekomünikasyon A.S.	CR	Approval	31.1Corrections	Yes	Yes	noted	No
R3‑245643	Data forwarding and transmission in Inter-CU LTM	Rakuten Mobile, Inc	discussion	Agreement	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245644	Discussion on RAN-CN interface for Ambient IoT	China Telecom	discussion		16.3RAN-CN Interface Impact	Yes	No	available	No
R3‑245645	Initial considerations on Inter-CU LTM	Rakuten Mobile, Inc	discussion	Decision	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245646	Open issues on MRO for LTM and CHO with candidate SCGs	LG Electronics Inc.	discussion		10.2MRO Enhancements	Yes	No	available	No
R3‑245647	Discussion on OD-SIB1	Rakuten Mobile, Inc	discussion		17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245648	Mobility Optimization with AI/ML based Network Slicing	Rakuten Mobile, Inc	discussion		11.2AI/ML enabled Slicing	Yes	No	available	No
R3‑245649	Discusson on support of L3 measurement based LTM support over F1	ZTE Corporation	discussion		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245650	Support L3 measurement based LTM support over F1 - TS38.473	ZTE Corporation	CR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245651	Support L3 measurement based LTM support over F1 - TS38.401	ZTE Corporation	CR		8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245652	TP to 38.423 for inter-CU LTM	ZTE Corporation	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245653	TP to 38.300 for inter-CU LTM	ZTE Corporation	other		13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245654	SON/MDT enhancements for NTN	Ericsson	discussion		10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245655	(TP to 38.300) Discussion on supporting WAB and the reply LS to SA2	ZTE Corporation	other	Approval	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245656	(TP to 38.305 38.455) Support of location service involving WAB	ZTE Corporation	other	Approval	12.2Wireless Access Backhaul (WAB)	Yes	No	available	No
R3‑245657	Correction of IAB F1-C transfer in NR-DC	ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung	draftCR	Approval	9.2NR	Yes	Yes- Change the M-NG-RAN node and S-NG-RAN node to MN and SN - Remove the comments - Change the title of the figures?	revised	No	R3‑245702
R3‑245658	Correction of IAB F1-C transfer in NR-DC	ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung	draftCR	Approval	9.2NR	Yes	Yes- Change the M-NG-RAN node and S-NG-RAN node to MN and SN - Remove the comments - Change the title of the figures?	revised	No	R3‑245703
R3‑245659	Further Discussion on UE Location Information for NB-IoT NTN	ZTE Corporation	other	Approval	9.1LTE	Yes	Yes	noted	No
R3‑245660	Correction on UE History Information	ZTE Corporation, CMCC, CATT	CR	Approval	9.2NR	Yes	Yes	noted	No
R3‑245661	Discussion on Location Reporting Control procedure for UPF Relocation	ZTE Corporation, CMCC, China Telecom	other	Approval	9.2NR	Yes	No	available	No
R3‑245662	Correction on Location Reporting Control procedure for NR NTN	ZTE Corporation, CMCC, China Telecom	CR	Approval	9.2NR	Yes	No	available	No
R3‑245663	Correction on Location Reporting Control procedure for NR NTN	ZTE Corporation, CMCC, China Telecom	CR	Approval	9.2NR	Yes	No	available	No
R3‑245664	(TP to BL CR for 38.300) Further discussion on SONMDT enhancement for NTN	ZTE Corporation	other	Agreement	10.3.1Intra-NTN Mobility	Yes	No	available	No
R3‑245665	(TP to BL CR for 38.413, 38.300, 38.423) Further discussion on Rel-18 leftovers	ZTE Corporation	other	Agreement	10.4R18 leftovers	Yes	No	available	No
R3‑245666	Further discussion on support of regenerative payload	ZTE Corporation	other	Agreement	14.3Support of Regenerative payload	Yes	No	available	No
R3‑245667	(TP to BL CR for TS38.473) Further discussion on on-demand SSB Scell operation	ZTE Corporation	other	Agreement	17.2Support on-demand SSB SCell operation	Yes	No	available	No
R3‑245668	Further discussion on on-demand SIB1	ZTE Corporation	discussion	Discussion	17.3Support on-demand SIB1 for UEs	Yes	No	available	No
R3‑245669	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	Yes	YesHW: It’s useless E///: 3 MHz is missing, may not help much CATT: Support this change, the request should be aware by the gNB Nok: No strong view on the CRs but the values supported in different releases are different	revised	No	R3‑245726
R3‑245670	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	Yes	Yes	revised	No	R3‑245727
R3‑245671	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	Yes	Yes	revised	No	R3‑245728
R3‑245672	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	Yes	Yes	revised	No	R3‑245729
R3‑245673	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	Yes	Yes	revised	No	R3‑245730
R3‑245674	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	Yes	Yes	revised	No	R3‑245731
R3‑245675	Discussion on standard impacts on Xn interface for AI/ML-based CCO	LG Electronics Inc.	discussion		11.3AI/ML enabled Coverage and Capacity Optimization	Yes	No	available	No
R3‑245676	Response to R3-245201	Qualcomm Incorporated	response	Decision	13.2Support for inter-CU LTM	Yes	No	available	No
R3‑245677	Response to R3-245065, R3-245319 and R3-245591	ZTE Corporation	response		8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245678	Response to R3-245342 and R3-245343	Ericsson	response	Discussion	8.1New Incoming LSs	Yes	Yes	noted	No
R3‑245679	Response to R3-245123, R3-245124, R3-245160 and R3-245587	Ericsson India Private Limited	response	Decision	9.2NR	Yes	No	available	No
R3‑245680	Response to R3-245511	ZTE Corporation	response	Discussion	8.3Left over LSs / pending actions	Yes	Yes	noted	No
R3‑245681	Response to R3-245375	Ericsson	response		31.2Enhancements	Yes	No	available	No
R3‑245682	[Draft] Reply LS on multi-modality awareness at RAN	Nokia	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	agreed	No		R3‑245170
R3‑245683	CB:#1_AI/ML-Training	ZTE	discussion	discussion	8.1New Incoming LSs	No	No- Whether to send LS to SA5 on the meaning of AI/ML training? Any spec updates needed?	reserved	No
R3‑245684	[draft] Reply LS on MDT configuration control in NR-DC	RAN3(Huawei)	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	agreed	No		R3‑245623
R3‑245685	CB:3_SDTNetworkBasedSolution	ZTE	discussion	discussion	8.3Left over LSs / pending actions	No	No- Check the issues raised online towards network based solution	reserved	No
R3‑245686	CB:#4_NBIoTNTN	QC	discussion	discussion	9.1LTE	No	No- Discuss the open issues above - Other critical corrections if agreeabl	reserved	No
R3‑245687	Clarification on indication of dormant cell re-activation	CATT,Nokia,Huawei,CMCC,ZTE,NEC,Samsung	CR	Agreement	9.1LTE	No	No	reserved	No		R3‑245267
R3‑245688	CB:#5_DeactivationIndication	CATT	discussion	discussion	9.1LTE	No	No- Check details of CR - Check the open issue above	reserved	No
R3‑245689	Correction of TRP Geographical coordinates [PosLocalCoords]	Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245329
R3‑245690	Correction of TRP Geographical coordinates [PosLocalCoords]	Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245330
R3‑245691	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia, ZTE, Samsung	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245366
R3‑245692	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia, ZTE, Samsung	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245367
R3‑245693	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia, ZTE, Samsung	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245368
R3‑245694	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245369
R3‑245695	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245370
R3‑245696	Positioning measurement correction related to "shall, if supported"	Huawei, CMCC, CUC, Nokia	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245371
R3‑245697	Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE]	Ericsson, CATT, Xiaomi, ZTE	CR	Agreement	9.2NR	Yes	Yes	endorsed	No		R3‑245328
R3‑245698	summary of offline for CB#2	Ericsson	discussion	discussion	8.1New Incoming LSs	Yes	Yes- Check companies’ view on whether to support L3 measurement triggered LTM in R18 and whether send LS to RAN2 for further clarification based on the agreed scope (e.g., early syn, cell switch)?	noted	No
R3‑245699	DRAFT Reply LS on L3 measurement based LTM support over F1	Vodafone GmbH	LS out	Agreement	8.1New Incoming LSs	Yes	Yes- Correct editorials	revised	No	R3‑245710	R3‑245222
R3‑245700	Option 2: Correction on DU collecting and reporting of DL LBT failure information	CATT, Ericsson, Nokia, Huawei, Samsung, ZTE	CR	Agreement	9.2NR	Yes	Yes	endorsed	No		R3‑245632
R3‑245701	Correction of mobility change procedure	Huawei, Nokia, Deutsche Telekom	CR	-	9.2NR	No	YesRAN3 agreed to only change in R18.	endorsed	No		R3‑245227
R3‑245702	Correction of IAB F1-C transfer in NR-DC	ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung	draftCR	Approval	9.2NR	No	No	reserved	No		R3‑245657
R3‑245703	Correction of IAB F1-C transfer in NR-DC	ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung	draftCR	Approval	9.2NR	No	No	reserved	No		R3‑245658
R3‑245704	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR	-	9.2NR	Yes	Yes	endorsed	No		R3‑245171
R3‑245705	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR	-	9.2NR	Yes	Yes	endorsed	No		R3‑245172
R3‑245706	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR	-	9.2NR	Yes	Yes	endorsed	No		R3‑245173
R3‑245707	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR	-	9.2NR	Yes	Yes	endorsed	No		R3‑245174
R3‑245708	Corrections on SL relay procedure	LG Electronics, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT	CR	Agreement	9.2NR	Yes	Yes	endorsed	No		R3‑245382
R3‑245709	CB:#8_AIMLforNG-RAN	Ericsson	discussion	discussion	9.2NR	No	No- Further check the options for stage2 model performance - Check wording in R3-245602	reserved	No
R3‑245710	Reply LS on L3 measurement based LTM support over F1	Vodafone GmbH	LS out	Agreement	8.1New Incoming LSs	Yes	Yes	agreed	No		R3‑245699
R3‑245711	Indicating configuration of PSI-based discard in SN-triggered modification procedure	CATT	CR	Agreement	31.1Corrections	Yes	Yestechnically Endorsed Merged to BL CR in R19 XR WI after RAN3#125bis, and the BL CR to be resubmitted when R19 XR WI reopen in RAN3.	endorsed	No		R3‑245182
R3‑245712	Correction of message level criticality of E1AP procedures	Huawei	CR	Agreement	31.1Corrections	Yes	YesTechnically Endorsed	endorsed	No		R3‑245408
R3‑245713	CB:#AIRAN_Slicing	ZTE	discussion	discussion	11.2AI/ML enabled Slicing	No	No- Draft the TP for TS38.423 based on the agreements - Discuss the open issues above and capture agreements if any	reserved	No
R3‑245714	(BL CR to 38.423) Support of XR enhancements	CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC	CR	Endorsement	21.1General	Yes	Yes	endorsed	No		R3‑245035
R3‑245715	CB: # 9_MobilityEnh	Google	discussion	discussion	9.2NR	No	No- Check the critical corrections if any	reserved	No
R3‑245716	CB:#AIRAN2_CCO	Samsung	discussion	discussion	11.3AI/ML enabled Coverage and Capacity Optimization	No	No- Draft the TP for TS38.423 based on the agreements - Discuss the open issues above and capture agreements if any	reserved	No
R3‑245717	CB:#AIRAN3_NR-DC	Huawei	discussion	discussion	11.4R18 leftovers	No	No- Start with the SN addition and SN change as NR-DC scenarios and open issue above - Capture agreements and provide TP if agreeable	reserved	No
R3‑245718	CB:#AIRAN4_SplitArchitecture	Lenovo	discussion	discussion	11.4R18 leftovers	No	No- Check the open issues above and capture agreements if any	reserved	No
R3‑245719	CB:#AIRAN5_ContinousMDT	Ericsson	discussion	discussion	11.4R18 leftovers	No	No- Check the principle above - LS to SA5?	reserved	No
R3‑245720	TP for BL CR on Introduction of NR Femto Architecture and Protocol Aspects	Nokia	other	Agreement	12.35G Femto	Yes	Yes	revised	No	R3‑245754
R3‑245721	CB:#AIoT1_ProtocolStack	Huawei	discussion	discussion	16.2RAN Architecture	No	No- Capture the functions needed in AIoT RAN for each options - Capture protocol stack options at least including Opt1, 2 and 3 - Whether to capture the unified architecture including both Topology1 and Topology2 (whether one AIoT gNB should support Topology1 and Topology2 together)? - FFS cleanup if agreeable	reserved	No
R3‑245722	(TP to BL CR TS 38.423) AI/ML enabled CCO	Samsung	other	Agreement	11.3AI/ML enabled Coverage and Capacity Optimization	No	No	reserved	No
R3‑245723	CB:#AIoT2_RANCNinterface	Ericsson	discussion	discussion	16.3RAN-CN Interface Impact	No	No- Check the details in R3-245307, taking R3-245581 into account - Continue the discussion on reader selection for Topology1 and Topology2 based on progress in RAN2	reserved	No
R3‑245724	Stage-2 support for LTM L2 reset	Ericsson, Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, CATT	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245516
R3‑245725	CB:#AIoT3_Location	Nokia	discussion	discussion	16.4Others	No	No- Discuss the open issues above - Cleanup the FFS for AIoT location if agreeable - Capture agreements if any	reserved	No
R3‑245726	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	No	No	reserved	No		R3‑245669
R3‑245727	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	No	No	reserved	No		R3‑245670
R3‑245728	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	No	No	reserved	No		R3‑245671
R3‑245729	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	No	No	reserved	No		R3‑245672
R3‑245730	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	No	No	reserved	No		R3‑245673
R3‑245731	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom	CR	Approval	9.2NR	No	No	reserved	No		R3‑245674
R3‑245732	introduction of bandwidths 35MHz and 45MHz in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE	CR	Agreement	9.2NR	No	No	reserved	No
R3‑245733	introduction of bandwidths 35MHz and 45MHz in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE	CR	Agreement	9.2NR	No	No	reserved	No
R3‑245734	introduction of bandwidths 35MHz and 45MHz in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE	CR	Agreement	9.2NR	No	No	reserved	No
R3‑245735	introduction of bandwidths 35MHz and 45MHz in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE	CR	Agreement	9.2NR	No	No	reserved	No
R3‑245736	CB:#AIPHY	Ericsson	discussion	discussion	20.2Support Positioning Accuracy Enhancements	No	No- Discuss the open issues above - Capture agreements and open issues	reserved	No
R3‑245737	CB:#R19ES	Ericsson	discussion	discussion	17.3Support on-demand SIB1 for UEs	No	No- Discuss the open issues above	reserved	No
R3‑245738	Correction to Requested DL PRS Transmission Characteristics	Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia	CR	-	9.2NR	No	No	reserved	No		R3‑245462
R3‑245739	Correction to Requested DL PRS Transmission Characteristics	Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia	CR	-	9.2NR	No	No	reserved	No		R3‑245463
R3‑245740	Summary of Offline Discussion on additional topological enhancement	NTTDOCOMO, INC.	discussion	discussion	12.2Wireless Access Backhaul (WAB)	Yes	Yes	noted	No
R3‑245741	(BL CR to 38.425) Support of XR enhancements	Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai Bell,China Telecom, CMCC, ZTE, CATT	CR	Endorsement	21.1General	No	Yes	endorsed	No		R3‑245036
R3‑245742	(BL CR to 38.473) Support of XR enhancements	Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom	CR	Endorsement	21.1General	No	Yes	endorsed	No		R3‑245038
R3‑245743	Correction for the reference specification on UE History Information for Rel-18	CMCC, Huawei, CATT, ZTE, Nokia	CR	Approval	9.2NR	No	Yes	endorsed	No		R3‑245525
R3‑245744	Signalling enhancements for inter-CU LTM HO	Qualcomm Incorporated, Vodafone, Bharti Airtel (India)	discussion	Decision	13.2Support for inter-CU LTM	No	No	reserved	No		R3‑245313
R3‑245745	Enabling subsequent inter-gNB LTM by decoupling of cell and anchor changes	Qualcomm Incorporated, Vodafone, NTT DOCOMO, Sony, Bharti Airtel (India)	discussion	Decision	13.2Support for inter-CU LTM	No	No	reserved	No		R3‑245314
R3‑245746	Impact analysis of coupling LTM cell switch and CU anchor changes on subsequent inter-gNB LTM	Qualcomm Incorporated, Vodafone, NTT DOCOMO, Sony, Bharti Airtel (India)	discussion	Decision	13.2Support for inter-CU LTM	No	No	reserved	No		R3‑245315
R3‑245747	CB:#MobilityEnh_LTM	China Telecom, Lenovo	discussion	discussion	13.2Support for inter-CU LTM	No	No	reserved	No
R3‑245748	2nd SoD of CB:#MobilityEnh_LTM: Discuss on the PDCP anchor solution and capture the view	Lenovo	discussion	discussion	13.2Support for inter-CU LTM	No	No	reserved	No
R3‑245749	Clarification on SpCell ID replacement	Google	CR	Agreement	9.2NR	No	No	reserved	No		R3‑245350
R3‑245750	Clarification on SpCell ID replacement	Google	CR	Agreement	9.2NR	No	No	reserved	No
R3‑245751	Clarification on SpCell ID replacement	Google	CR	Agreement	9.2NR	No	No	reserved	No
R3‑245752	Draft reply LS to SA2 based on the agreement above	Qualcomm	LS out	discussion	12.2Wireless Access Backhaul (WAB)	No	No	reserved	No
R3‑245753	CB:#WAB	NTT DOCOMO	discussion	discussion	12.2Wireless Access Backhaul (WAB)	No	No	reserved	No
R3‑245754	TP for BL CR on Introduction of NR Femto Architecture and Protocol Aspects	Nokia	other	Agreement	12.35G Femto	No	No	reserved	No		R3‑245720