TDoc list

Agenda	Topic	TDoc	Title	Source	Type	For	Avail	Treated	Decision	Wdrn	Replaced-by	Replaces
1	Opening of the meeting
2	Reminders
2.1	IPR Declaration
2.2	Statement of Antitrust Compliance
2.3	Responsible IT Behavior
2.4	Additional reminders
3	Approval of the Agenda	R3‑247001	RAN3#126 Meeting Agenda	RAN3 Chair	agenda	Approval	Yes	Yes	approved	No
4	Approval of the minutes from previous meetings	R3‑247002	RAN3#125-bis Meeting Report	ETSI-MCC	report	Approval	Yes	Yes	approved	No
5	Documents for immediate consideration	R3‑247003	Guidelines for RAN3 Meetings	RAN3 Chair, RAN3 Vice-Chairs	discussion	Endorsement	Yes	Yes	endorsed	No
6	Organizational topics
7	General, protocol principles and issues	R3‑247004	TR 30.531 v1.55.0 Work Plan and Working Procedures - RAN WG3	ETSI-MCC	other	Endorsement	Yes	Yes	endorsed	No
8	Incoming LSs
8.1	New Incoming LSs	R3‑247009	Reply to SA2 LS on multi-modality awareness	RAN2(Huawei)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247113	LS for PDU Set Information Marking Support without QoS parameters	SA2(Vivo)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247015	Reply on FS_XRM_Ph2	RAN2(Nokia)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247339	Discussion on the LS related to XR	Nokia, Nokia Shanghai Bell	discussion		Yes	Yes	noted	No
		R3‑247255	Discussion on LS on XR from SA2	vivo	discussion	Discussion	Yes	Yes	noted	No
		R3‑247659	Discussion on SA2 LS on PDU Set Information	ZTE Corporation	discussion	Decision	Yes	Yes	noted	No
		R3‑247359	Discussion on the usage of multi-modality information	Huawei	discussion		Yes	Yes	noted	No
		R3‑247246	Discussion on on RAN3 support of multi-modality awareness	CMCC	discussion	Discussion	Yes	Yes	noted	No
		R3‑247360	[draft] Reply LS on usage of multi-modality information	Huawei	LS out	Agreement	Yes	Yes	revised	No	R3‑247767
		R3‑247767	[draft] Reply LS on usage of multi-modality information	Huawei	LS out	Agreement	No	No	reserved	No		R3‑247360
		R3‑247718	Disccsion on LS for PDU Set Information Marking Support without QoS parameters	CATT	discussion	Decision	Yes	No	available	No
		R3‑247340	[Draft] Reply LS for PDU Set Information Marking Support without QoS parameters	Nokia, Nokia Shanghai Bell	LS out	Agreement	Yes	No	available	No
		R3‑247245	Discussion on PDU Set Information Marking Support without QoS parameters	CMCC	discussion	Discussion	Yes	No	available	No
		R3‑247361	Discussion on the PDU set information marking support without PDU set QoS parameters	Huawei	discussion		Yes	No	available	No
		R3‑247362	[draft] Reply LS on PDU set information marking support without PDU set QoS parameters	Huawei	LS out	Agreement	Yes	No	available	No
		R3‑247571	Discussion on SA2 LS regarding PDU Set Information Marking Support without QoS parameters	Ericsson	discussion	Discussion	Yes	No	available	No
		R3‑247572	LS reply on PDU Set Information Marking Support without QoS parameters	Ericsson	LS out	Agreement	Yes	No	available	No
		R3‑247660	[Draft]Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters	ZTE Corporation	other	Approval	Yes	No	available	No
		R3‑247114	LS to RAN3 on renewable energy based LBO	SA5(Huawei)	LS in	Discussion	Yes	YesReply to SA5 that support of renewable energy at the RAN is valuable. There is no proper WI in RAN3 concerning this topic in R19. Action: RAN3 kindly asks SA5 to take the above feedback into account.	noted	No
		R3‑247528	Reply LS on Renewable energy based LBO	Ericsson	LS out	Agreement	Yes	Yes	noted	No
		R3‑247700	Discussion on renewable energy based LBO	ZTE Corporation	discussion		Yes	Yes	noted	No
		R3‑247701	[Draft]Reply LS on renewable energy based LBO	ZTE Corporation	other		Yes	YesCB: # 2_RenewableEnergy - Provide the reply LS in R3-247768 (moderator - ZTE)	revised	No	R3‑247768
		R3‑247768	[Draft]Reply LS on renewable energy based LBO	ZTE Corporation	other	-	No	No	reserved	No		R3‑247701
		R3‑247568	Discussion on LS from SA5 on renewable energy based LBO	Nokia	discussion		Yes	Yes	noted	No
		R3‑247663	[Draft] Reply LS on renewable energy based LBO	Nokia	LS out	Agreement	Yes	Yes	noted	No
		R3‑247631	Discussion on renewable energy based LBO	Huawei	discussion		Yes	Yes	noted	No
		R3‑247632	[draft] Reply LS on renewable energy based LBO	Huawei	LS out	Agreement	Yes	Yes	noted	No
		R3‑247011	LS on UL RRC message segmentation for UECapabilityInformation	RAN2(Qualcomm)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247117	Discussion on UL RRC message segmentation for UECapabilityInformation	ZTE Corporation	discussion	Agreement	Yes	YesLS to SA2 whether CN needs to inform RAN about the maximum UE capability size that CN can accommodate and postpone the CR before it is confirmed by SA2.	noted	No
		R3‑247118	NGAP on UL RRC message segmentation for UECapabilityInformation	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑247119	NGAP on UL RRC message segmentation for UECapabilityInformation	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑247120	Draft LS to SA2 on UL RRC message segmentation for UECapabilityInformation	ZTE Corporation	LS out	Agreement	Yes	No	available	No
		R3‑247307	NR UE capability storing limitation discussion and draft reply LS	Qualcomm Incorporated	discussion	Agreement	Yes	YesOption 1 : OAM based approach Option 2 : NGAP signalling approach (either via NG interface management or UE context management signalling)	noted	No
		R3‑247335	Discussion on the UL RRC message segmentation for UECapabilityInformation	Nokia, Nokia Shanghai Bell	discussion		Yes	YesIntroduce a new IE in the NG SETUP RESPONSE message to allow the AMF provides the Maximum UE capability size to the gNB. LTE case?	noted	No
		R3‑247336	Introduction of the signalling of UE capability size of the AMF	Nokia, Nokia Shanghai Bell	CR		Yes	No	available	No
		R3‑247337	Introduction of the signalling of UE capability size of the AMF	Nokia, Nokia Shanghai Bell	CR		Yes	No	available	No
		R3‑247338	[DRAFT] Reply LS on UL RRC message segmentation for UECapabilityInformation	Nokia, Nokia Shanghai Bell	LS out	Agreement	Yes	No	available	No
		R3‑247408	UL RRC message segmentation for UECapabilityInformation	Huawei	discussion		Yes	YesOption 1: OAM configuration Option 2: Signaling based Option 2a: AMF node level message Option 2b: UE level message	noted	No
		R3‑247409	Introduction of Allowed UE Radio Capability Size for UECapabilityInformation [UL_Capa_Segmentation]	Huawei	CR		Yes	No	available	No
		R3‑247410	Introduction of Allowed UE Radio Capability Size for UECapabilityInformation [UL_Capa_Segmentation]	Huawei	CR		Yes	No	available	No
		R3‑247411	[draft] Reply LS on UL RRC message segmentation for UECapabilityInformation	Huawei	LS out	Agreement	Yes	No	available	No
		R3‑247589	On the RAN2 LS on "UL RRC message segmentation for UECapabilityInformation"	Ericsson	discussion	Agreement	Yes	Yesreply to RAN2 that RAN3 considered their case but did not agree to include the indication in NGAP.	noted	No
		R3‑247769	Reply LS to RAN2_(related to_CB:#3_RRCSegmentation)	Qualcomm	LS in	discussion	No	No	reserved	No
		R3‑247005	LS on Multicast MBS session restoration procedure for N3mb path failure	CT4(Nokia)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247121	Recovery of N3mb path failure for unicast transport of multicast session	ZTE Corporation	CR	Approval	Yes	Yes	noted	No
		R3‑247748	Recovery of N3mb path failure for unicast transport of multicast session	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑247240	Recovery of N3mb failure for Multicast Session	Nokia	discussion		Yes	Yes	noted	No
		R3‑247247	Recovery of N3mb path failure for unicast transport of multicast session	Nokia	CR	Agreement	Yes	No	available	No
		R3‑247248	Recovery of N3mb path failure for unicast transport of multicast session	Nokia	CR	Agreement	Yes	Yes	revised	No	R3‑247781
		R3‑247781	Recovery of N3mb path failure for unicast transport of multicast session	Nokia	CR	Agreement	No	No	reserved	No		R3‑247248
		R3‑247249	Recovery of N3mb path failure for unicast transport of multicast session	Nokia	draftCR	Endorsement	Yes	Yes	revised	No	R3‑247782
		R3‑247782	Recovery of N3mb path failure for unicast transport of multicast session	Nokia	draftCR	Endorsement	No	No	reserved	No		R3‑247249
		R3‑247250	Reply LS on Multicast MBS Session Restoration procedure for N3mb path failure	Nokia	LS out	Agreement	Yes	Yes	revised	No	R3‑247783
		R3‑247783	Reply LS on Multicast MBS Session Restoration procedure for N3mb path failure	Nokia	LS out	Agreement	No	No	reserved	No		R3‑247250
		R3‑247251	Consideration on Multicast MBS session restoration procedure for N3mb path failure	Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated	discussion	Agreement	Yes	Yes	noted	No
		R3‑247252	Support of Multicast MBS session restoration procedure for N3mb path failure	Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated	CR	Agreement	Yes	Yes	revised	No	R3‑247764
		R3‑247764	Support of Multicast MBS session restoration procedure for N3mb path failure	Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated	CR	Agreement	Yes	Yes	revised	No	R3‑247802	R3‑247252
		R3‑247802	Support of Multicast MBS session restoration procedure for N3mb path failure	Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated, Nokia	CR	Agreement	No	No	reserved	No		R3‑247764
		R3‑247253	Support of Multicast MBS session restoration procedure for N3mb path failure	Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated	CR	Agreement	Yes	No	available	No
		R3‑247254	[Draft] Reply LS on Multicast MBS session restoration procedure for N3mb path failure (Reply to C4-244467)	Huawei	LS out	Agreement	Yes	No	available	No
		R3‑247720	Restoration of N3mb Failure for MBS multicast	Ericsson	CR	Agreement	Yes	Yes	noted	No
		R3‑247721	Restoration of N3mb Failure for MBS multicast	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑247770	CB:#4_N3mb	Nokia	discussion	discussion	No	No- Check the details above - Provide the CRs and reply LS if agreeable	reserved	No
		R3‑247010	Reply to SA5 LS on Number of UEs in RRC_INACTIVE state with data transmission	RAN2(Huawei)	LS in	Discussion	Yes	YesHW: RAN3 can achieve this on our side CATT: The real benefits are not clear based on RAN2 LS, nothing needs to be done in RAN3 E///: Agree with Nok that the number of SDT UEs in RRC_INACTIVE state has no relationship to evaluate the load status of a specific cell	noted	No
		R3‑247597	Counting number of RRC_INACTIVE SDT UEs	Nokia	discussion		Yes	Yes	noted	No
		R3‑247752	Response to R3-247597 and R3-247599	ZTE Corporation	response		Yes	Yes	noted	No
		R3‑247599	Response LS on number of UEs in RRC_INACTIVE state with data transmission	Nokia	LS out	Agreement	Yes	Yes	noted	No
		R3‑247115	LS on AI/ML Model transfer/delivery to UE	SA5(NEC)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247759	LS on draft-ietf-raw-technologies, "Reliable and Available Wireless Technologies"	IETF	LS in	Discussion	Yes	Yes	noted	No
		R3‑247167	Discussion on the support of semi-persistent CSI-RS resource for LTM candidate cells	ZTE Corporation	discussion		Yes	Yes	withdrawn	Yes
		R3‑247168	[DRAFT] Reply LS on the support of semi-persistent CSI-RS resource for LTM candidate cells	ZTE Corporation	LS out		Yes	Yes	withdrawn	Yes
		R3‑247169	[DRAFT] Reply LS on Early TA acquisition for the inter-DU scenario	ZTE Corporation	LS out		Yes	Yes	withdrawn	Yes
		R3‑247170	Discussion on support of intra-SN SCPAC in MN format	ZTE Corporation	discussion		Yes	Yes	withdrawn	Yes
		R3‑247171	Support intra-SN SCPAC in MN format - TS37.340	ZTE Corporation	draftCR		Yes	Yes	withdrawn	Yes
		R3‑247172	Support intra-SN SCPAC in MN format over Xn - TS38.423	ZTE Corporation	CR		Yes	Yes	withdrawn	Yes
		R3‑247174	Discussion on L3 measurement based LTM support over F1	ZTE Corporation	discussion		Yes	Yes	withdrawn	Yes
		R3‑247175	Support L3 measurement based LTM support over F1 - TS38.401	ZTE Corporation	CR		Yes	Yes	withdrawn	Yes
		R3‑247176	Support L3 measurement based LTM support over F1 - TS38.473	ZTE	CR		Yes	Yes	withdrawn	Yes
		R3‑247177	Support L3 measurement based LTM support over F1 - TS38.470	ZTE Corporation	CR		Yes	Yes	withdrawn	Yes
		R3‑247178	[Draft]reply LS on L3 measurement based LTM support over F1	ZTE Corporation	LS out		Yes	Yes	withdrawn	Yes
8.2	LSin received during the meeting	R3‑247784	Reply LS to SA5 on AIML data collection	RAN2(Nokia)	LS in	discussion	Yes	No	available	No
		R3‑247798	Reply LS to SA2 on AIML data collection	RAN2(Interdigital)	LS in	discussion	Yes	No	available	No
8.3	Left over LSs / pending actions	R3‑247295	Issues for network based solution for SDT partial UE context transfer	Qualcomm Incorporated, ZTE	discussion	Agreement	Yes	Yes	noted	No
		R3‑247503	Introduction of SDT network-based solution	Nokia, Ericsson, Huawei, LG Electronics	discussion		Yes	Yes	noted	No
		R3‑247179	Discussion on SDT signalling optimization for partial context transfer	ZTE Corporation	discussion		Yes	Yes	noted	No
		R3‑247180	[DRAFT] LS on network-based solution for SDT signalling optimization	ZTE Corporation	LS out	Agreement	Yes	No	available	No
		R3‑247290	Further discussion on support of SDT network-based solution	CATT	discussion	Decision	Yes	No	available	No
		R3‑247291	Support of SDT network-based solution	CATT, Nokia	draftCR	Approval	Yes	No	available	No
		R3‑247292	Support of SDT network-based solution	CATT	CR	Approval	Yes	No	available	No
		R3‑247504	Introduction of SDT network-based solution	Nokia, Huawei, Ericsson, LG Electronics	CR		Yes	No	available	No
		R3‑247505	Response LS on SDT signalling optimization for partial context transfer	Nokia	LS out	Agreement	Yes	No	available	No
		R3‑247163	Introduction of SDT network-based solution	Huawei, Nokia, Ericsson, LG Electronics	draftCR	Agreement	Yes	No	available	No
		R3‑247164	Introduction of SDT network-based solution	Huawei, Nokia, Ericsson, LG Electronics	CR	Agreement	Yes	No	available	No
		R3‑247573	Introduction of SDT network-based solution	Ericsson, Nokia, Huawei, LG Electronics	CR	Agreement	Yes	No	available	No
		R3‑247613	Discussion on Improved KPIs involving end-to-end data volume transfer time analytics	Nokia	discussion		Yes	Yes	noted	No
		R3‑247754	Response to R3-247613, R3-247506	ZTE Corporation	response		Yes	Yes	noted	No
		R3‑247614	[Draft] Reply LS on Improved KPIs involving end-to-end data volume transfer time analytics	Nokia	LS out	Agreement	Yes	Yes	noted	No
		R3‑247506	Further discussion related to the Reply LS on improved KPIs	Ericsson	discussion	Approval	Yes	Yes	noted	No
		R3‑247507	Reply to Reply LS on improved KPIs involving end-to-end data volume transfer time analytics	Ericsson	LS out	Agreement	Yes	Yes	noted	No
		R3‑247508	Correction of existing reference to TS28.552 by updating it to TS28.558	Ericsson	draftCR	Agreement	Yes	Yes	noted	No
9	Corrections to Rel-18 or earlier releases
9.1	LTE	R3‑247341	Correction of mapped cell support list	Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Thales	draftCR	Endorsement	Yes	YesZTE: Not needed, the updates have the risk to extend the usage of mapped cell ID CATT: Brings confusion, e.g., X2 setup procedure NEC: Prefer the original text SS: Not needed, should discuss case by case. [MCC reports] Source companies' opinion: Without this change, each time a new feature is introduced in NTN that uses Cell Identity as mapped cell, TS 36.300/TS 38.300 will need to be modified. It also remains unclear if a feature not listed should use Mapped Cell ID or not.	noted	No		R3‑245339
		R3‑247449	Correction of mapped cell support list	Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Thales	draftCR	Endorsement	Yes	Yes[MCC reports] Source companies' opinion: Without this change, each time a new feature is introduced in NTN that uses Cell Identity as mapped cell, TS 36.300/TS 38.300 will need to be modified. It also remains unclear if a feature not listed should use Mapped Cell ID or not.	noted	No		R3‑245485
		R3‑247450	E-SMLC OAM Configuration for IoT NTN	Ericsson, Thales, Huawei	draftCR	Endorsement	Yes	Yes[MCC reports] Source companies' opinion: Without this change, it is not possible to support positioning for IoT NTN or LTE-M NTN.	noted	No		R3‑245482
		R3‑247451	E-SMLC OAM Configuration for IoT NTN - Motivation	Ericsson, Huawei, Thales	discussion	Discussion	Yes	YesCATT, ZTE: RAN3 had the conclusion in R18 IoT NTN in Chicago meeting last year CATT: RAN1 did evaluation work for NR NTN at that time but such work did not performed in RAN1 for IoT NTN	noted	No
		R3‑247475	Correction of MT-EDT	Nokia, Peraton Labs	CR	Agreement	Yes	YesHW: There has the stage2 text in TS23.401 E///: Support this CR NEC: Should come from SA2	noted	No
		R3‑247476	Correction of MT-EDT	Nokia, Peraton Labs	CR	Agreement	Yes	Yes	noted	No
		R3‑247477	Correction of MT-EDT	Nokia, Peraton Labs	CR		Yes	Yes	noted	No
		R3‑247734	Correction on criticality of Measurement Result	ZTE Corporation, China Unicom	CR	Agreement	Yes	Yes	noted	No
		R3‑247735	Correction on criticality of Measurement Result	ZTE Corporation, China Unicom	CR	Agreement	Yes	Yes	noted	No
		R3‑247736	Correction on criticality of Measurement Result	ZTE Corporation, China Unicom	CR	Agreement	Yes	Yes	noted	No
		R3‑247739	Discussion on criticality of measurement result	ZTE Corporation, CATT, China Telecom, China Unicom	discussion	Approval	Yes	YesThere are two solutions to address this misalignment: - Solution 1: Modify the assigned criticality of Node Measurement Initiation Result List IE and Cell Measurement Initiation Result List IE in the DATA COLLECTION RESPONSE to "ignore" to align with LTE. - Solution 2: Modify the assigned criticality of Measurement Initiation Result IE in the RESOURCE STATUS RESPONSE to "reject" to align with NR. Nok: From logical point of view, either way works Noted The criticality of Measurement Initiation Result in LTE resource status response message and NR data collection response message are different.	noted	No
		R3‑247740	Correction on criticality of Measurement Result for Data Collection	ZTE Corporation, Lenovo, CMCC, China Telecom, China Unicom	CR		Yes	Yes	noted	No
		R3‑247464	Discussion on Configuration Update procedure	CATT	discussion	Decision	Yes	YesE///: Conflict with the overwriting principle HW: Not sure whether companies stand on the same page on the Cat1/2 for IEs listed. Anything to be updated should use the modification procedure. ZTE: Fine with proposals CB: # 5_NeighbourCellupdates - Focus on proposal3 and check the corresponding CRs (moderator - CATT)	noted	No
9.2	NR	R3‑247014	Reply LS on Early TA acquisition for the inter-DU scenario	RAN2(Google)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247124	Corrections for Early TA acquisition for PDCCH order in LTM	Google, ZTE, Huawei, Ericsson, Nokia, CATT, China Telecom, LG Electronics	CR	Agreement	Yes	Yes- Add SS as co-source	revised	No	R3‑247772
		R3‑247772	Corrections for Early TA acquisition for PDCCH order in LTM	Google, ZTE, Huawei, Ericsson, Nokia, CATT, China Telecom, LG Electronics, Samsung	CR	Agreement	Yes	Yes	agreed	No		R3‑247124
		R3‑247012	Reply LS on intra-SN SCPAC in MN format	RAN2(ZTE)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247173	[DRAFT] Reply LS on intra-SN SCPAC in MN format	ZTE Corporation	LS out	Agreement	Yes	YesMove to 9.2	noted	No
		R3‑247729	Stage-2 updates for intra-SN S-CPAC with MN involvement	Ericsson, Nokia, CATT	draftCR	Endorsement	Yes	YesZTE: Only update 10.20 - Add reference in general signalling procedure - update the step1 in 10.20 Rev in R3-247773 CB: # 6_S-CPAC - Check the details in R3-247773 - Check whether any stage3 CR is needed? (moderator - E///)	revised	No	R3‑247773
		R3‑247773	Stage-2 updates for intra-SN S-CPAC with MN involvement	Ericsson, Nokia, CATT	draftCR	Endorsement	No	No	reserved	No		R3‑247729
		R3‑247742	Correction on “S-CPAC Request” IE description for Intra-SN S-CPAC in MN format	LG Electronics Inc.	CR	Agreement	Yes	Yes	agreed	No
		R3‑247013	L3 measurement based LTM support over F1	RAN2(Vodafone)	LS in	Discussion	Yes	Yes	noted	No
		R3‑247105	Discussion on L3 L1/2 Triggered Mobility	Nokia, LG Electronics, NTT Docomo	discussion	Discussion	Yes	Yes	noted	No
		R3‑247728	Triggering LTM without L1 measurements UE capability	Ericsson, Vodafone, CATT	discussion	Discussion	Yes	Yes	noted	No
		R3‑247237	Signaling enhancements for L3 measurement based R18 LTM	Qualcomm Incorporated, Reliance JIO, Bharti Airtel	discussion	Decision	Yes	YesMove to 9.2	noted	No
		R3‑247106	L3 based L1/2 Triggered Mobility	Nokia, NTT Docomo, LG Electronics	CR	Agreement	Yes	Yes	noted	No		R3‑245401
		R3‑247125	Corrections for L3 measurement triggered LTM cell switch	Google	CR	Agreement	Yes	Yes	noted	No		R3‑245352
		R3‑247265	Discussion on L3 measurement based LTM support over F1 (CRs included)	Huawei	discussion		Yes	Yes	noted	No
		R3‑247349	Discussion on L3 measurement based LTM	Samsung	discussion	Approval	Yes	Yes	noted	No
		R3‑247460	Stage 2 updates for support of L3 measurements based LTM	CATT, Ericsson, Vodafone	CR	Approval	Yes	Yes	noted	No		R3‑245240
		R3‑247725	F1 support for L3 measurements-based LTM	Ericsson, Vodafone, CATT	CR	Agreement	Yes	Yes	noted	No		R3‑245564
		R3‑247394	Correction on the presence issue of TCI states configuration List	CATT,Google, Huawei, Nokia, China Telecom, CMCC	CR	Agreement	Yes	Yes	noted	No
		R3‑247774	CB:#7_L3LTM	Vodafone	discussion	discussion	Yes	No- Check the technical issue on the solutions as described above - If there is no technical issue, the solution similar to early synchronization for cell switch could be adopted - RAN3 should make the final decision in this meeting for this late LTM feature in R18	available	No
		R3‑247465	Discussion on definition of UE performance metrics	CATT,Deutsche Telekom,China Unicom,ZTE,China Telecom,Jio	discussion	Decision	Yes	Yes	noted	No
		R3‑247466	[DRAFT] LS on UE level measurements	CATT,Deutsche Telekom,China Unicom,ZTE,China Telecom,Jio	LS out	Agreement	Yes	Yes	noted	No
		R3‑247412	On Rel-18 UE performance feedback for AI/ML for NG-RAN	Huawei, Lenovo, Deutsche Telekom, Telecom Italia, BT, InterDigital, Nokia	discussion	Decision	Yes	Yes	noted	No
		R3‑247413	[Draft] LS on per-UE UE performance metrics	Huawei, Lenovo, Deutsche Telekom, Telecom Italia, BT, InterDigital, Nokia	LS out	Agreement	Yes	Yes- Check with SA5, for Average UE Throughput DL/UL: these metrics could be calculated as specified in TS 28.558 clauses 6.3.1.4.1 and 6.3.1.4.2. Rev in R3-247775 CB: # 8_AIMILStoSA5 - Provide the LS in R3-247775 (moderator - HW)	revised	No	R3‑247775
		R3‑247775	[Draft] LS on per-UE UE performance metrics	Huawei, Lenovo, Deutsche Telekom, Telecom Italia, BT, InterDigital, Nokia	LS out	Agreement	No	No	reserved	No		R3‑247413
		R3‑247514	Correction for Data Collection Reporting procedure’s interaction with Handover Request procedure	Ericsson, Jio, AT&T, InterDigital, Lenovo	CR	Agreement	Yes	Yes	noted	No
		R3‑247288	Correction to area-specific SRS activation	CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated, Xiaomi, Huawei	draftCR	Endorsement	Yes	Yes	endorsed	No
		R3‑247289	Correction to area-specific SRS activation	CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated, Xiaomi, Huawei	CR	Agreement	Yes	Yes	agreed	No		R3‑245063
		R3‑247738	Support of UE specific SRS reservation	ZTE Corporation, CATT, Huawei, Samsung, Nokia, Ericsson, Xiaomi	CR	Agreement	Yes	Yes- Remove “TS 38.305 CR” in the link field	revised	No	R3‑247776	R3‑245105
		R3‑247776	Support of UE specific SRS reservation	ZTE Corporation, CATT, Huawei, Samsung, Nokia, Ericsson, Xiaomi	CR	Agreement	No	Yes	agreed	No		R3‑247738
		R3‑247605	Support of UE specific SRS reservation	Samsung, CATT, Huawei, ZTE, Ericsson, Nokia, Xiaomi	CR	Agreement	Yes	Yes	agreed	No		R3‑245122
		R3‑247333	Correction on Positioning SRS Resource in TS38.455	China Telecom, ZTE,CATT	CR	Agreement	Yes	NoNok: Comment on the semantic description and the presence of the IE in ASN.1 should be optional HW: Same comment as Nok E///: Another way is to extend the current IE CT: WI code is not correct CB: # 9_SRS - Check the details (moderator - CT)	available	No
		R3‑247334	Correction on Positioning SRS Resource in TS38.473	China Telecom, ZTE,CATT	CR	Agreement	Yes	Yes	noted	No
		R3‑247737	Correction on criticality of Time Window Information SRS	ZTE Corporation, CATT, Ericsson, Huawei, Nokia	CR	Agreement	Yes	Yes	agreed	No
		R3‑247397	Correction on Measurement Time Window	Huawei, CMCC, CUC, Ericsson, Nokia	CR	Agreement	Yes	YesNBC CR - The Slot Number is not correct?	revised	No	R3‑247777
		R3‑247777	Correction on Measurement Time Window	Huawei, CMCC, CUC, Ericsson, Nokia	CR	Agreement	No	No	reserved	No		R3‑247397
		R3‑247575	Correction on Measurement Time Window	Ericsson, Huawei, CMCC, CUC, Nokia	CR	Agreement	Yes	Yes- The Slot Number is not correct?	revised	No	R3‑247778
		R3‑247778	Correction on Measurement Time Window	Ericsson, Huawei, CMCC, CUC, Nokia	CR	Agreement	No	No	reserved	No		R3‑247575
		R3‑247570	Correction of UE Rx-Tx Time difference measurements	Ericsson, Polaris Wireless, CATT, Huawei	CR	Agreement	Yes	YesZTE: Fine with the motivation - CR revision history is missing - update the IE name in ASN.1 - Add ZTE, CT as co-source	revised	No	R3‑247779	R3‑245471
		R3‑247779	Correction of UE Rx-Tx Time difference measurements	Ericsson, Polaris Wireless, CATT, Huawei, ZTE, China Telecom	CR	Agreement	No	No	reserved	No		R3‑247570
		R3‑247530	Discussion on Periodic E-CID Measurement Procedure	Jio	discussion	Agreement	Yes	YesE///, ZTE: Do not understand the motivation. LMF can stop the measurement towards gNB when needed CATT: No need to consider the corner case HW: We do not define such kind of count number for the procedures	noted	No
		R3‑247532	Periodic E-CID measurement procedure	Jio	CR	Agreement	Yes	Yes	noted	No
		R3‑247562	NR-DC QMC Coordination for RRC Segmentation	Nokia, ZTE, Samsung	discussion		Yes	Yes	noted	No
		R3‑247656	Discussion on NR-DC QMC Coordination for RRC Segmentation	ZTE Corporation, Samsung, Nokia, China Unicom, China Telecom	discussion	Approval	Yes	Yes	noted	No
		R3‑247655	Introduction to coordination for QoE RRC segmentation in NR-DC	ZTE Corporation, Samsung, Nokia, China Unicom, China Telecom	draftCR	Agreement	Yes	Yes	noted	No
		R3‑247606	Corrections to QMC support in NR-DC for RRC Segmentation	Samsung, ZTE Corporation, Nokia, China Unicom, China Telecom	CR	Agreement	Yes	Yes	noted	No
		R3‑247267	QoE measurement handling in idle mode	CATT, Ericsson, ZTE, Xiaomi	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑245251
		R3‑247638	Further miscellaneous corrections to QMC procedure	Huawei, China Unicom, Lenovo	draftCR	Endorsement	Yes	Yes	noted	No
		R3‑247218	Corrections for QoE intra-5GC inter-RATs mobility	NEC	draftCR	Endorsement	Yes	YesZTE, Nok: The original text is clear E///: Not critical, but OK	noted	No
		R3‑247219	Corrections for QoE intra-5GC inter-RATs mobility on XnAP	NEC	CR	Agreement	Yes	YesZTE, Nok: Not needed	noted	No
		R3‑247704	Discussion on abnormal case of Xn setup procedure	ZTE Corporation	discussion		Yes	Yes	noted	No
		R3‑247705	Correction on Xn Setup message	ZTE Corporation	CR		Yes	No	available	No
		R3‑247706	Correction on Xn Setup message	ZTE Corporation	CR		No	No	available	No
		R3‑247707	Correction on Xn Setup message	ZTE Corporation	CR		Yes	No	available	No
		R3‑247708	Correction on Xn Setup message	ZTE Corporation	CR		No	No	available	No
		R3‑247515	Corrections on Xn Setup Duplication	Ericsson	CR	Agreement	Yes	Yes	noted	No
		R3‑247516	Corrections on Xn Setup Duplication	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑247517	Corrections on Xn Setup Duplication	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑247518	Corrections on Xn Setup Duplication	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑247780	CB:#12_MultipleXnSetup	ZTE	discussion	discussion	No	No- Check the common understanding: In case an additional Xn setup procedure is triggered for an already established Xn-C interface instance, it shall not impact the already established Xn-C interface instance regardless if the additional Xn setup procedure is successful or failed.	reserved	No
		R3‑247199	Correction on IAB RESOURCE COORDINATION	ZTE Corporation, Lenovo, Nokia, Nokia Shanghai Bell, Samsung	CR	Agreement	Yes	Yes	agreed	No
		R3‑247200	Correction on IAB RESOURCE COORDINATION	ZTE Corporation, Lenovo, Nokia, Nokia Shanghai Bell, Samsung	CR	Agreement	Yes	Yes	agreed	No
		R3‑247274	Correction for resource configuration	CATT	CR	Agreement	Yes	Yes	revised	No	R3‑247765
		R3‑247765	Correction for resource configuration	CATT	CR	Approval	Yes	Yes	noted	No		R3‑247274
		R3‑247275	Correction for resource configuration	CATT	CR	Approval	Yes	Yes	revised	No	R3‑247766
		R3‑247766	Correction for resource configuration	CATT	CR	Approval	Yes	Yes	noted	No		R3‑247275
		R3‑247478	Correction of MBS PDCP packets discard	Nokia, Huawei, Qualcomm, CMCC, CBN, China Broadnet	discussion		Yes	NoZTE:The intention is good, but reluctant to update at this stage It is expected that the gNB CU-UP may supports PDCP SN continuity after establishment of shared NG-U resources with 5GC2. HW: The CR does not change too much CATT: The CR will bring new issue CB: # 25_MBSPDCP - Check the issues raised online, if no consensus, then stop the optimization in R18 (moderator - Nok)	available	No
		R3‑247479	Correction on PDCP packets discard in case of MBS broadcast path update	Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, Chnia Broadnet	CR		Yes	Yes	revised	No	R3‑247807
		R3‑247807	Correction on PDCP packets discard in case of MBS broadcast path update	Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, Chnia Broadnet	CR	-	No	No	reserved	No		R3‑247479
		R3‑247481	Correction of MBS PDCP packets discard in case of MBS broadcast path update	Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, China Broadnet	CR		Yes	Yes	revised	No	R3‑247808
		R3‑247808	Correction of MBS PDCP packets discard in case of MBS broadcast path update	Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, China Broadnet	CR	-	No	No	reserved	No		R3‑247481
		R3‑247122	Draft CR with rethinking on Rel-18 group paging design	ZTE Corporation, China Telecom, CMCC, Lenovo	draftCR	Endorsement	Yes	YesHW: Not convinced about the scenario, do not see the need to limit the RNA area in a gNB Nok: RAN2 has solved the issue	noted	No
		R3‑247510	Stage 2 correction for network slice support during XN handover	Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia	draftCR	Endorsement	Yes	YesHW: Look at the discussion history, there is the intention not to such limitation ZTE: The mobility decision is based on radio quality rather than support slice. Xn case is the same as NG case. SS: It’s up to source gNB implementation	noted	No		R3‑245552
		R3‑247511	Stage 2 correction for network slice support during XN handover	Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia	draftCR	Endorsement	Yes	Yes	noted	No		R3‑245553
		R3‑247512	Stage 2 correction for network slice support during XN handover	Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia	draftCR	Endorsement	Yes	Yes	noted	No		R3‑245554
		R3‑247513	Stage 2 correction for network slice support during XN handover	Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia	draftCR	Endorsement	Yes	Yes	noted	No		R3‑245555
		R3‑247574	Corrections to Stage-2 for XR awareness	Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE, China Telecom, Xiaomi, CATT, CMCC, Lenovo	draftCR	Endorsement	Yes	Yes- update the coversheet	revised	No	R3‑247817
		R3‑247817	Corrections to Stage-2 for XR awareness	Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE, China Telecom, Xiaomi, CATT, CMCC, Lenovo	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑247574
		R3‑247358	Discussion on the PDCP SN gap report handling during UE’s handover	Huawei, CATT, Xiaomi, China Telecom, LG Electronics	discussion	Discussion	Yes	YesQC: Sol1 is simple, not prefer sol3 LGE: Prefer to solve it in RAN3, Sol1 is preferred CATT:Prefer Sol2 ZTE, E///: Send LS to RAN2 Nok: Prefer to treat it in R19 with all possible solutions SS: Prefer Sol1	noted	No
		R3‑247818	CB:#26_PDCPSN	Huawei	discussion	discussion	No	No	reserved	No
		R3‑247155	Correction on CIoT optimization with 5GC	Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia	CR	Agreement	Yes	No	available	No
		R3‑247156	Correction on CIoT optimization with 5GC	Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia	CR	Agreement	Yes	No	available	No
		R3‑247157	Correction on CIoT optimization with 5GC	Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia	CR	Agreement	Yes	No	available	No
		R3‑247690	Clarification on the name of AP ID over Xn interface for Rel-15	CMCC, CATT, Huawei, ZTE	CR	Approval	Yes	No	available	No
		R3‑247691	Clarification on the name of AP ID over Xn interface for Rel-16	CMCC, CATT, Huawei, ZTE	CR	Approval	Yes	No	available	No
		R3‑247692	Clarification on the name of AP ID over Xn interface for Rel-17	CMCC, CATT, Huawei, ZTE	CR	Approval	Yes	No	available	No
		R3‑247693	Clarification on the name of AP ID over Xn interface for Rel-18	CMCC, CATT, Huawei, ZTE	CR	Approval	Yes	No	available	No
		R3‑247406	Introduction of AUN3 device access	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR		Yes	No	available	No		R3‑245379
		R3‑247407	Introduction of AUN3 device access	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR		Yes	No	available	No		R3‑245380
		R3‑247583	Support of AUN3 devices	Ericsson, BT, China Unicom	CR	Agreement	Yes	No	available	No		R3‑245577
		R3‑247584	Support of AUN3 devices	Ericsson, BT, China Unicom	CR	Agreement	Yes	No	available	No		R3‑245578
		R3‑247633	Correction of Unavailable GUAMI in AMF Status Indication message	Huawei, China Telecom, China Unicom	CR		Yes	No	available	No		R3‑245405
		R3‑247634	Correction of Unavailable GUAMI in AMF Status Indication message	Huawei, China Telecom, China Unicom	CR		Yes	No	available	No		R3‑245406
		R3‑247635	Correction of Unavailable GUAMI in AMF Status Indication message	Huawei, China Telecom, China Unicom	CR		Yes	No	available	No		R3‑245407
		R3‑247644	Addition of procedural description of CPAC Configuration	ZTE Corporation, Samsung, China Telecom	CR	Approval	Yes	No	available	No
		R3‑247395	Correction of mapped cell support list	Huawei, Ericsson, Nokia, Thales	draftCR	Agreement	Yes	Yes[MCC reports] Source companies' opinion: Without this change, each time a new feature is introduced in NTN that uses Cell Identity as mapped cell, TS 36.300/TS 38.300 will need to be modified. It also remains unclear if a feature not listed should use Mapped Cell ID or not.	noted	No
		R3‑247396	Correction of mapped cell support list	Huawei, Ericsson, Nokia, Thales	draftCR	Agreement	Yes	Yes[MCC reports] Source companies' opinion: Without this change, each time a new feature is introduced in NTN that uses Cell Identity as mapped cell, TS 36.300/TS 38.300 will need to be modified. It also remains unclear if a feature not listed should use Mapped Cell ID or not.	noted	No
		R3‑247540	Clarification on NTN time-based handover over NG	ZTE Corporation. CMCC, China Telecom	CR	Approval	Yes	No	available	No
		R3‑247541	Clarification on NTN time-based handover over S1	ZTE Corporation, CMCC, China Telecom	CR	Approval	Yes	No	available	No
		R3‑247542	Discussion on Location Reporting Control procedure for UPF Relocation	ZTE Corporation, CMCC, China Telecom	other	Approval	Yes	No	available	No
		R3‑247543	Correction on Location Reporting Control procedure for NR NTN	ZTE Corporation, CMCC, China Telecom	CR	Approval	Yes	No	available	No
		R3‑247544	Correction on Location Reporting Control procedure for NR NTN	ZTE Corporation, CMCC, China Telecom	CR	Approval	Yes	No	available	No
		R3‑247553	Support MUSIM capability restriction over XnAP	Ericsson, Qualcomm Incorporated, Xiaomi	CR	Agreement	Yes	No	available	No		R3‑241650
		R3‑247554	Support MUSIM capability restriction	Ericsson, Qualcomm Incorporated, Xiaomi	discussion	Discussion	Yes	No	available	No		R3‑241653
		R3‑247555	Support MUSIM capability restriction over NGAP	Ericsson, Qualcomm Incorporated, Xiaomi	CR	Agreement	Yes	No	available	No		R3‑241654
		R3‑247133	Clarification of the chapter title to match the description of the UE History Information	Nokia, ZTE, CMCC	draftCR	Endorsement	Yes	No	available	No		R3‑245477
		R3‑247509	On the special case of Nrb 12 and Nrb 20 Transmission Bandwidth configurations	Ericsson, Strict, Qualcomm	discussion	Approval	Yes	No	available	No
		R3‑247165	Editorial correction on TNL Configuration Info	NTTDOCOMO, INC.	CR		Yes	No	available	No		R3‑245355
		R3‑247166	Editorial correction on TNL Configuration Info	NTTDOCOMO, INC.	CR		Yes	No	available	No		R3‑245356
		R3‑247259	Clarification on resumption of non-SDT bearer in SDT termination	Google	CR	Agreement	Yes	No	available	No
		R3‑247266	Correction on the Signalling based MDT PLMN List	Huawei	draftCR		Yes	No	available	No
		R3‑247134	Correction of a wrong description of the S-NG-RAN node Counter Check procedure	Nokia	CR	Agreement	Yes	No	available	No		R3‑245478
		R3‑247135	Correction of a wrong description of the S-NG-RAN node Counter Check procedure	Nokia	CR	Agreement	Yes	No	available	No		R3‑245479
		R3‑247136	Correction of a wrong description of the S-NG-RAN node Counter Check procedure	Nokia	CR	Agreement	Yes	No	available	No		R3‑245480
		R3‑247137	Correction of a wrong description of the S-NG-RAN node Counter Check procedure	Nokia	CR	Agreement	Yes	No	available	No		R3‑245481
		R3‑247711	Correction on DL LBT failure information	CATT	draftCR	Agreement	Yes	No	available	No
		R3‑247743	Correction on the UE Initial Access procedure	Ericsson	CR		Yes	No	available	No
		R3‑247744	Correction on the UE Initial Access procedure	Ericsson	CR		Yes	No	available	No
		R3‑247745	Correction on the UE Initial Access procedure	Ericsson	CR		Yes	No	available	No
		R3‑247746	Correction on the UE Initial Access procedure	Ericsson	CR		Yes	No	available	No
		R3‑247107	L3 based L1/2 Triggered Mobility	Nokia	CR		No	Yes	withdrawn	Yes
		R3‑247194	Periodic E-CID measurement procedure	Jio	CR	Agreement	Yes	Yes	withdrawn	Yes
		R3‑247792	update of broadcast MCCH information	RAN3(Nokia)	LS out	Agreement	No	No	reserved	No
9.3	Endorsed TEI CRs Review	R3‑247037	Correction on configuration update for an inactive Multicast session	ZTE Corporation, Huawei, CATT, Nokia, Lenovo	CR	Agreement	Yes	Yes	agreed	No		R3‑245042
		R3‑247038	Correction of Positioning SI for connected UE	ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi	CR	Agreement	Yes	Yes	agreed	No		R3‑245099
		R3‑247039	Correction of Positioning SI for connected UE	ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi	CR	Agreement	Yes	Yes	agreed	No		R3‑245100
		R3‑247040	Correction of Positioning SI for connected UE	ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi	CR	Agreement	Yes	Yes	agreed	No		R3‑245101
		R3‑247041	Correction on conditional PSCell addition or change failure	CATT, CMCC, ZTE, Nokia, Nokia Shanghai Bell	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑245180
		R3‑247042	Correcting IE reference in Cell Replacing Info	Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC	CR	Agreement	Yes	Yes	agreed	No		R3‑245228
		R3‑247043	Correcting IE reference in Cell Replacing Info	Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC	CR	Agreement	Yes	Yes	agreed	No		R3‑245229
		R3‑247044	Corrections on MP relay based PDCP duplication	ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑245301
		R3‑247045	Clarification of the usage of the UE History Information	Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone	CR	Agreement	Yes	Yes	agreed	No		R3‑245308
		R3‑247046	L2 reset for intra-DU LTM	Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, Ericsson, CATT	CR	Agreement	Yes	Yes- Update the “LTM L2 Reset Configuration Item IEs”-> “LTM L2 Reset Configuration Item”	revised	No	R3‑247811	R3‑245341
		R3‑247811	L2 reset for intra-DU LTM	Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, Ericsson, CATT	CR	Agreement	No	Yes	agreed	No		R3‑247046
		R3‑247047	Introduction of 2Rx XR devices support [2Rx_XR_Device]	Huawei, Qualcomm, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, China Telecom	CR	Agreement	Yes	Yes- Remove the comments and changes over changes	revised	No	R3‑247810	R3‑245385
		R3‑247810	Introduction of 2Rx XR devices support [2Rx_XR_Device]	Huawei, Qualcomm, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, China Telecom	CR	Agreement	Yes	Yes	agreed	No		R3‑247047
		R3‑247048	Clarification of the usage of the UE History Information	Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone	CR	Agreement	Yes	Yes	agreed	No		R3‑245400
		R3‑247049	Clarification on indication of dormant cell re-activation	CATT, Nokia, Huawei, CMCC, ZTE, NEC, Samsung	CR	Agreement	Yes	Yes- Check LTE proper WI code and TEI18	revised	No	R3‑247814	R3‑245687
		R3‑247814	Clarification on indication of dormant cell re-activation	CATT, Nokia, Huawei, CMCC, ZTE, NEC, Samsung	CR	Agreement	No	No	available	No		R3‑247049
		R3‑247050	Positioning measurement correction related to “shall, if supported”	Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245691
		R3‑247051	Positioning measurement correction related to “shall, if supported”	Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245692
		R3‑247052	Positioning measurement correction related to “shall, if supported”	Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245693
		R3‑247053	Positioning measurement correction related to “shall, if supported”	Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245694
		R3‑247054	Positioning measurement correction related to “shall, if supported”	Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245695
		R3‑247055	Positioning measurement correction related to “shall, if supported”	Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245696
		R3‑247056	Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE]	Ericsson, CATT, Xiaomi, ZTE, Huawei, Qualcomm Inc.	CR	Agreement	Yes	Yes	agreed	No		R3‑245697
		R3‑247057	Option 2: Correction on DU collecting and reporting of DL LBT failure information	CATT, Ericsson, Nokia, Huawei, Samsung, ZTE	CR	Agreement	Yes	Yes- correct co-source company name: Samsung	revised	No	R3‑247812	R3‑245700
		R3‑247812	Option 2: Correction on DU collecting and reporting of DL LBT failure information	CATT, Ericsson, Nokia, Huawei, Samsung, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑247057
		R3‑247058	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR	Agreement	Yes	Yes	agreed	No		R3‑245704
		R3‑247059	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR	Agreement	Yes	Yes	agreed	No		R3‑245705
		R3‑247060	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR	Agreement	Yes	Yes	agreed	No		R3‑245706
		R3‑247061	Correction for the semantics description	Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei	CR	Agreement	Yes	Yes	agreed	No		R3‑245707
		R3‑247062	Corrections on SL relay procedure	LG Electronics, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245708
		R3‑247063	Stage-2 support for LTM L2 reset	Ericsson, Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245724
		R3‑247064	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑245726
		R3‑247065	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑245727
		R3‑247066	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑245729
		R3‑247067	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes- update the clause number as 9.2.27	revised	No	R3‑247821	R3‑245730
		R3‑247821	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑247067
		R3‑247068	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom, Ericsson, Huawei,ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑245731
		R3‑247069	Correction to Requested DL PRS Transmission Characteristics	Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia	CR	Agreement	Yes	Yes	agreed	No		R3‑245738
		R3‑247070	Correction to Requested DL PRS Transmission Characteristics	Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia	CR	Agreement	Yes	Yes	agreed	No		R3‑245739
		R3‑247071	Correction for the reference specification on UE History Information for Rel-18	CMCC, Huawei, CATT, ZTE, Nokia	CR	Agreement	Yes	Yes- update the title:Correction for the reference specification on UE History Information	revised	No	R3‑247813	R3‑245743
		R3‑247813	Correction for the reference specification on UE History Information	CMCC, Huawei, CATT, ZTE, Nokia	CR	Agreement	No	Yes	agreed	No		R3‑247071
		R3‑247072	Clarification on SpCell ID replacement	Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑245749
		R3‑247073	Clarification on SpCell ID replacement	Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑245750
		R3‑247074	Clarification on SpCell ID replacement	Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑245751
		R3‑247075	Correction on AI/ML Terminology	Nokia	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑245772
		R3‑247076	OAM Requirements on Energy Cost index	Nokia, Jio, Telecom Italia	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑245773
		R3‑247077	Correction on broadcast reception for eRedCap UE [RedcapMBS]	Huawei, Qualcomm Incorporated, ZTE, CBN, Nokia, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245776
		R3‑247078	Correction on broadcast reception for eRedCap UE [RedcapMBS]	Huawei, Qualcomm Incorporated, ZTE, CBN, Nokia, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245777
		R3‑247079	Correction on MBS Service Area	Huawei, CMCC, Ericsson, CBN, Nokia	CR	Agreement	Yes	Yes	agreed	No		R3‑245778
		R3‑247080	Correction on Retrieve UE Context Confirm	Huawei, Nokia, Qualcomm Incorporated	CR	Agreement	Yes	Yes	agreed	No		R3‑245780
		R3‑247081	Correction on Retrieve UE Context Confirm	Huawei, Nokia, Qualcomm Incorporated	CR	Agreement	Yes	Yes	agreed	No		R3‑245781
		R3‑247082	Correction of N3IWF user location information	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245783
		R3‑247083	Alignment of procedural text for LTM early sync procedure	CATT, China Telecom, CMCC, Huawei, Google, Nokia, LG Electronics, Ericsson, Samsung	CR	Agreement	Yes	Yes	agreed	No		R3‑245786
		R3‑247084	Correction on LTM procedures for Inter-DU case and CU-UP change	LG Electronics, CATT, CMCC, China Telecom, Ericsson, Google, Huawei, Lenovo, NEC, Nokia, NTT Docomo, Samsung, Qualcomm, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑245790
		R3‑247085	Correction of TRP Geographical coordinates [PosLocalCoords]	Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑245791
		R3‑247086	Correction of TRP Geographical coordinates [PosLocalCoords]	Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑245792
		R3‑247087	Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑245803
		R3‑247092	Correction of IAB F1-C transfer in NR-DC	ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑245809
		R3‑247093	Correction of IAB F1-C transfer in NR-DC	ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑245810
		R3‑247094	Correction on BAP mapping configuration for IAB	Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245811
		R3‑247095	Correction on BAP mapping configuration for IAB	Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245812
		R3‑247096	Correction on BAP mapping configuration for IAB	Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245813
		R3‑247098	Correction of mobility change procedure	Huawei, Nokia, Deutsche Telekom	CR	Agreement	Yes	Yes	agreed	No		R3‑245816
		R3‑247099	Coarse UE Location Information Reporting from MME to eNB for NB-IoT Ues	Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT	draftCR	Endorsement	Yes	Yes	revised	No	R3‑247815	R3‑245817
		R3‑247815	Coarse UE Location Information Reporting from MME to eNB for NB-IoT Ues	Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT	draftCR	Endorsement	No	Yes	agreed	No		R3‑247099
		R3‑247100	Coarse UE Location Information Reporting from MME to eNB – S1AP Impacts	Ericsson, Huawei, Qualcomm Incorporated, CATT, ZTE	CR	Agreement	Yes	Yes- update WI code as: IoT_NTN_enh-Core	revised	No	R3‑247816	R3‑245818
		R3‑247816	Coarse UE Location Information Reporting from MME to eNB – S1AP Impacts	Ericsson, Huawei, Qualcomm Incorporated, CATT, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑247100
		R3‑247101	Correction of N3IWF user location information	Huawei, Nokia, Nokia Shanghai Bell, CATT	CR	Agreement	Yes	Yes	agreed	No		R3‑245825
		R3‑247127	introduction of Missing Bandwidths in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑247088
		R3‑247128	introduction of Missing bandwidths in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑247089
		R3‑247129	introduction of Missing bandwidths in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑247090
		R3‑247130	introduction of Missing bandwidths in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	agreed	No		R3‑247091
		R3‑247097	Stage 2 correction for AI/ML for NG-RAN	Ericsson, Huawei, Nokia, InterDigital	draftCR	Endorsement	Yes	Yeslate contribution	endorsed	No		R3‑245814
		R3‑247088	introduction of Missing Bandwidths in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	withdrawn	Yes	R3‑247127	R3‑245804
		R3‑247089	introduction of Missing Bandwidths in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	withdrawn	Yes	R3‑247128	R3‑245805
		R3‑247090	introduction of Missing Bandwidths in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	withdrawn	Yes	R3‑247129	R3‑245806
		R3‑247091	introduction of Missing Bandwidths in FR1 SRS Bandwidth	China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	withdrawn	Yes	R3‑247130	R3‑245807
		R3‑247123	Correction on configuration update for an inactive Multicast session	ZTE Corporation, Huawei, CATT	CR	Approval	No	Yes	withdrawn	Yes
10	Data Collection for SON_MDT in NR standalone and MR-DC WI (RAN3-led)
10.1	General	R3‑247019	(BL CR to 36.300 for SON) Addition of SON enhancements	Lenovo	draftCR	Endorsement	Yes	No	available	No		R3‑245028
		R3‑247020	(BL CR to 36.423) Addition of SON enhancements	CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia	CR	Endorsement	Yes	No	available	No		R3‑245851
		R3‑247021	(BL CR to 37.340 for SON) on MRO for S-CPAC	CMCC	draftCR	Endorsement	Yes	No	available	No		R3‑245852
		R3‑247022	(BL CR to 38.300 for SON) Addition of SON enhancements	China Unicom, Nokia, Huawei, Lenovo, CATT, Ericsson, Qualcomm Inc., Samsung, LG Electronics Inc, ZTE Corporation	draftCR	Endorsement	Yes	No	available	No		R3‑245853
		R3‑247023	(BL CR to 38.401 for SON) Addition of SON enhancements	ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung	CR	Endorsement	Yes	No	available	No		R3‑245854
		R3‑247024	(BL CR to 38.413 for MDT) Addition of MDT enhancements	Nokia	CR	Endorsement	Yes	No	available	No		R3‑245855
		R3‑247025	(BL CR to 38.423 for MDT) Addition of MDT enhancements	CATT	CR	Endorsement	Yes	No	available	No		R3‑245856
		R3‑247026	(BL CR to 38.423 for SON) Addition of SON enhancements	ZTE Corporation, Samsung, Nokia, Lenovo, Jio	CR	Endorsement	Yes	No	available	No		R3‑245857
		R3‑247027	(BL CR to 38.473 for SON) Addition of SON enhancements	Huawei, Nokia, Jio	CR	Endorsement	Yes	No	available	No		R3‑245858
		R3‑247681	Workplan for Rel-19 SON_MDT Enhancement	CMCC, China Unicon	Work Plan	Information	Yes	No	available	No
10.2	MRO Enhancements	R3‑247494	(TP for BL CR to 38.300 for SON) MRO enhancements for LTM	Ericsson	other	Agreement	Yes	No	available	No
		R3‑247151	MRO enhancements for R18 mobility mechanisms	Qualcomm Incorporated	discussion	Discussion	Yes	No	available	No
		R3‑247159	(TP for BLCR for SON for 38.300, 38.401,38.473, 38.413, 37.340, 38.423) MRO enhancement for R18 mobility mechanisms	Huawei	other	Agreement	Yes	No	available	No
		R3‑247223	(TP for SON BLCR of 38.473) MRO for LTM with RLF-report unavailible	NEC	other	Agreement	Yes	No	available	No
		R3‑247296	(TP to BL CR TS38.401) MRO for LTM	Samsung	other	Agreement	Yes	No	available	No
		R3‑247308	(TP for SON BL CR for TS 38.473)Discussion on LTM MRO	Google	other	Agreement	Yes	No	available	No
		R3‑247309	Failure scenarios on MRO for CHO with candidate SCGs	Samsung, Cybercore, Lenovo	discussion	Approval	Yes	No	available	No
		R3‑247310	(TP for SON BLCR TS38.300, TS37.340 and TS38.423) MRO for CHO with candidate SCGs and S-CPAC	Samsung	other	Approval	Yes	No	available	No
		R3‑247321	(TP for SON BL CR for TS 38.473 and for TS 37.340) MRO Enhancements for LTM, CHO with Candidate SCG(s) and S-CPAC	Nokia	other	Agreement	Yes	No	available	No
		R3‑247424	(TP for SON BLCR for 38.401) Discussion on MRO for LTM	Lenovo	other	Agreement	Yes	No	available	No
		R3‑247425	(TP for SON BLCR for 37.340) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s)	Lenovo	other	Agreement	Yes	No	available	No
		R3‑247601	Discussion on MRO enhancements for LTM	LG Electronics Inc.	discussion	Discussion	Yes	No	available	No
		R3‑247645	Discussion on MRO Enhancements	China Unicom	discussion	Discussion	Yes	No	available	No
		R3‑247702	(TP for TS 38.401 TS38.473) Discussion on MRO	ZTE Corporation	other	Agreement	Yes	No	available	No
		R3‑247712	(TP 37.340) MRO for R18 mobility mechanisms	CATT	other	Agreement	Yes	No	available	No
10.3	SON/MDT for NTN and Slicing
10.3.1	Intra-NTN Mobility	R3‑247545	(TP to BL CR for 38.300) Further discussion on SONMDT enhancement for NTN	ZTE Corporation	other	Agreement	Yes	No	available	No
		R3‑247495	SON-MDT enhancements for NTN	Ericsson	discussion		Yes	No	available	No
		R3‑247713	(TP for 38.300 and 38.413) Intra-NTN mobility for SONMDT	CATT	other	Decision	Yes	No	available	No
		R3‑247131	[TP to BL CR to 38.423, SON] Solution to avoid restarting MRO in NTN deployments	Nokia	other	Agreement	Yes	No	available	No		R3‑245311
		R3‑247152	SON MDT for NTN	Qualcomm Incorporated	discussion	Discussion	Yes	No	available	No
		R3‑247225	Discussion on SON/MDT enhancements for NTN	NEC	discussion	Decision	Yes	No	available	No
		R3‑247264	(TP for MDT BLCRs for TS38.413, TS38.423, TS37.320) SON for Intra-NTN mobility	Huawei	other		Yes	No	available	No
		R3‑247426	Discussion on MRO for intra-NTN mobility	Lenovo	discussion		Yes	No	available	No
		R3‑247612	Discussion on SON enhancements for NTN	Samsung Electronics Polska	discussion		Yes	No	available	No
		R3‑247646	Discussion on SONMDT enhancements for NTN mobility	China Unicom	discussion		Yes	No	available	No
		R3‑247666	(TP to 38.300) Discussion on SONMDT enhancement for NTN	CMCC	other	Agreement	Yes	No	available	No
10.3.2	Network Slicing	R3‑247132	[TP to BL CR to 38.300, MDT] MDT solution for slice support and slice-related mobility enhancements	Nokia	other	Agreement	Yes	No	available	No		R3‑245312
		R3‑247496	On MDT enhancements for Network Slicing	Ericsson, T-Mobile US, InterDigital, Jio, Telecom Italia, Deutsche Telekom	discussion	Agreement	Yes	No	available	No
		R3‑247703	Further consideration on SON/MDT for Slicing	ZTE Corporation	discussion		Yes	No	available	No
		R3‑247153	SON MDT for network slicing	Qualcomm Incorporated	discussion	Discussion	Yes	No	available	No
		R3‑247160	SON and MDT for Network Slicing	Huawei	other		Yes	No	available	No
		R3‑247497	On SON enhancements for Network Slicing	Ericsson, InterDigital, Jio	discussion	Agreement	Yes	No	available	No
		R3‑247498	(TP for BLCR for MDT for TS 38.413) Addition of MDT enhancements	Ericsson	other	Agreement	Yes	No	available	No
		R3‑247650	Discussion on SONMDT enhancements for network slicing	China Unicom	discussion		Yes	No	available	No
		R3‑247668	Discussion on SONMDT for network slicing	CMCC	discussion	Discussion	Yes	No	available	No
		R3‑247714	Network slicing for SONMDT	CATT	discussion	Decision	Yes	No	available	No
10.4	R18 leftovers	R3‑247682	MHI and UHI Enhancement for SCG Deactivation Activation	CMCC, Huawei, CATT, Lenovo, ZTE	discussion	Discussion	Yes	No	available	No
		R3‑247162	[DRAFT] Reply LS on MHI enhancement solution for SCG deactivation/activation	Huawei, CMCC, ZTE, CATT [will be RAN3]	LS out	Agreement	Yes	No	available	No
		R3‑247154	UHI enhancements for SCG (de)activation	Qualcomm Incorporated	discussion	Discussion	Yes	No	available	No
		R3‑247161	(TP for BLCR for SON for 38.413, 36.423) Rel-18 SON and MDT leftovers	Huawei	other	Agreement	Yes	No	available	No
		R3‑247311	(TP for SON BLCR TS38.423 and TS36.423) Rel-18 SON and MDT leftovers	Samsung	other	Agreement	Yes	No	available	No
		R3‑247322	MHI/UHI Enhancement for SCG Deactivation/Activation	Nokia	discussion		Yes	No	available	No
		R3‑247427	Discussion on MRO for R18 leftovers	Lenovo	discussion		Yes	No	available	No
		R3‑247499	Further discussion on RACH optimization for SDT	Ericsson, CATT, ZTE Corporation	discussion		Yes	No	available	No
		R3‑247500	(TP for BL CR to 38.413 for SON) UHI for SCG activation and deactivation	Ericsson	other	Agreement	Yes	No	available	No
		R3‑247546	(TPs to BL CR for 38.300, 38.413) Further discussion on Rel-18 leftovers	ZTE Corporation	other	Agreement	Yes	No	available	No
		R3‑247694	Discussion on RACH optimization for SDT	China Telecom	discussion	Discussion	Yes	No	available	No
		R3‑247715	(TP for 37.340, 38.423, 36.423 and 38.413) SON enhancement for R18 leftover	CATT	other	Agreement	Yes	No	available	No
11	AI/ML for NG-RAN WI (RAN3-led)
11.1	General	R3‑247028	(BLCR to 38.423) Support of enhancements on AI/ML for NG-RAN	ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio, Rakuten	CR	Endorsement	Yes	Yes	endorsed	No		R3‑245850
		R3‑247741	Work plan for Rel-19 Enhancements for AI/ML for NG-RAN	ZTE Corporation, NEC	Work Plan		Yes	Yes	noted	No
11.2	AI/ML enabled Slicing	R3‑247203	(TP to BLCR TS38.423) AI/ML-based Slicing	NEC	other	Agreement	Yes	Yes	noted	No
		R3‑247615	AI/ML Slicing Discussion	Nokia	discussion	Discussion	Yes	Yes	noted	No
		R3‑247138	Discussion on AI/ML assisted Network Slicing	ZTE Corporation	discussion	Discussion	Yes	Yes	noted	No
		R3‑247139	[TP to 38.423] AI/ML assisted Network Slicing	ZTE Corporation, Qualcomm, China Unicom	other	Agreement	Yes	No	available	No
		R3‑247201	(TP for BLCR for TS38.300) Support of enhancements on AI/ML for NG-RAN	NEC, ZTE, Qualcomm, Samsung, CMCC	other	Agreement	Yes	No	available	No
		R3‑247202	(TP for BLCR for TS38.401) Support of enhancements on AI/ML for NG-RAN	NEC	other	Agreement	Yes	No	available	No
		R3‑247297	Discussion on AI/ML enabled slicing	Samsung	discussion	Approval	Yes	No	available	No
		R3‑247323	UE Performance Data for AI/ML based Network Slicing	Rakuten Mobile, Inc	discussion	Discussion	Yes	No	available	No
		R3‑247325	Discussion on NG-RAN AI/ML for Network Slicing	Qualcomm Incorporated	discussion	Agreement	Yes	No	available	No
		R3‑247414	(TP for AI/ML BLCR to TS 38.423) Discussion on the AI/ML-based Network Slicing	Huawei	other	Agreement	Yes	No	available	No
		R3‑247442	(TP to BLCR 38.423) Discussion on AIML based network slicing	Lenovo	other	Agreement	Yes	No	available	No
		R3‑247453	(TP to TR 38.743) AI/ML assisted Network Slicing	Tejas Network Limited	other	Agreement	Yes	No	available	No
		R3‑247467	(TP on 38.423)Support of AI/ML enabled Slicing	CATT	other	Agreement	Yes	No	available	No
		R3‑247469	Enhancement of UE performance metrics	CATT, Jio, Qualcomm, CBN	discussion	Decision	Yes	No	available	No
		R3‑247533	Support for AI/ML enabled Network Slicing	Ericsson, InterDigital	discussion	Approval	Yes	No	available	No
		R3‑247534	(TP to TS38.423) AIML enabled Network Slicing	Ericsson, InterDigital	other	Agreement	Yes	No	available	No
		R3‑247596	Discussion on AIML based Network Slicing	Jio	discussion	Discussion	Yes	No	available	No
		R3‑247604	Discussion for AI/ML based Network Slicing	Rakuten Mobile, Inc	discussion	Discussion	Yes	No	available	No
		R3‑247616	(TP to BLCR to TS 38.423) AI/ML Slicing	Nokia	other	Agreement	Yes	No	available	No
		R3‑247677	Discussion on AI-based network slice	CMCC	discussion	Discussion	Yes	No	available	No
		R3‑247678	(TP for 38.423) AIML based slice	CMCC	other	Approval	Yes	No	available	No
		R3‑247785	CB:#AIRAN1_Slicing	Lenovo	discussion	discussion	No	No- Check the open issues above - Provide TPs capture the agreements	reserved	No
		R3‑247823	(TP to BLCR 38.423) AIML based network slicing	Lenovo	other	Agreement	No	No	reserved	No
11.3	AI/ML enabled Coverage and Capacity Optimization	R3‑247326	Discussion on AI/ML enabled CCO	Qualcomm Incorporated	discussion	Agreement	Yes	Yes	noted	No
		R3‑247521	AI/ML support for CCO	Ericsson, InterDigital, Deutsche Telekom	discussion	Approval	Yes	Yes	noted	No
		R3‑247564	Discussion on signalling for AI/ML-based CCO	Nokia, Jio	discussion	Discussion	Yes	No	available	No
		R3‑247651	Discussion on AI/ML assisted Coverage and Capacity Optimization	ZTE Corporation	discussion	Approval	Yes	No	available	No
		R3‑247204	(TP to BLCR TS38.423) AI/ML-based CCO	NEC	other	Agreement	Yes	No	available	No
		R3‑247233	Discussions on enhancements for AIML support for CCO	Jio	discussion	Discussion	Yes	No	available	No
		R3‑247236	Further Enhancements on AIML support for CCO	Jio	discussion	Discussion	Yes	No	available	No
		R3‑247238	Discussion on Timing Aspects for AIML support in CCO	Jio	discussion	Discussion	Yes	No	available	No
		R3‑247298	(TP to BL CR TS38.423) AI/ML enabled CCO	Samsung	other	Agreement	Yes	No	available	No
		R3‑247374	Discussion on AI/ML based Coverage and Capacity Optimization	China Telecom	discussion	Decision	Yes	No	available	No
		R3‑247375	(TP to TS38.423) Support of AI/ML based Coverage and Capacity Optimization	China Telecom	other	Agreement	Yes	No	available	No
		R3‑247415	Timing information and feedback for AI/ML-based Coverage and Capacity Optimization	Huawei	discussion	Agreement	Yes	No	available	No
		R3‑247416	(TPs for AI/ML BLCR to TS 38.423 and AI/ML BLCR to TS 38.473) Signalling details for AI/ML-based Coverage and Capacity Optimization	Huawei	other	Agreement	Yes	No	available	No
		R3‑247448	(TP to BLCR 38.473) Discussion on AIML based CCO	Lenovo	other	Agreement	Yes	No	available	No
		R3‑247468	(TP on 38.423/38.473) Open issues on the CCO use case	CATT	other	Agreement	Yes	No	available	No
		R3‑247522	(TP to 38.473) - AI/ML support for CCO	Ericsson, InterDigital, Deutsche Telekom	other	Agreement	Yes	No	available	No
		R3‑247523	(TP to 38.423) - AI/ML support for CCO	Ericsson, InterDigital, Deutsche Telekom	other	Agreement	Yes	No	available	No
		R3‑247563	A contribution to energy efficient AI/ML-based CCO issue prediction in split architecture	Nokia, Jio, Telecom Italia	discussion		Yes	No	available	No
		R3‑247652	[TP to 38.401] Support of AI/ML assisted CCO	ZTE Corporation, Lenovo, China Unicom	other	Agreement	Yes	No	available	No
		R3‑247653	[TP to 38.423 and 38.473] Support of AI/ML assisted Coverage and Capacity Optimization	ZTE Corporation	other	Agreement	Yes	No	available	No
		R3‑247679	Discussion on AI/ML-based CCO	CMCC	discussion	Discussion	Yes	No	available	No
		R3‑247695	Discussion on Xn and F1 impacts for AI/ML-based CCO	LG Electronics Inc.	discussion		Yes	No	available	No
		R3‑247696	(TP for NR_AIML_NGRAN_enh-Core for TS 38.423) Discussion on Xn and F1 impacts for AI/ML-based CCO	LG Electronics Inc.	other	Agreement	Yes	No	available	No
		R3‑247697	(TP for NR_AIML_NGRAN_enh-Core for TS 38.473) Discussion on Xn and F1 impacts for AI/ML-based CCO	LG Electronics Inc.	other	Agreement	Yes	No	available	No
		R3‑247749	Discussion of AI/ML based CCO	Rakuten Mobile, Inc	discussion	Discussion	Yes	No	available	No
		R3‑247750	Data Collection Aspects for AIML support in CCO	Jio	discussion	Discussion	Yes	No	available	No
		R3‑247787	CB:#AIRAN2_CCO	Qualcomm	discussion	discussion	No	No- Check the WA above - Provide TPs to capture the agreements	reserved	No
11.4	R18 leftovers	R3‑247141	(TP to 38.423) Discussion on Mobility Optimization for NR-DC	ZTE Corporation	other	Agreement	Yes	Yes	revised	No	R3‑247827
		R3‑247827	(TP to 38.423) Discussion on Mobility Optimization for NR-DC	ZTE Corporation	other	Agreement	No	No	reserved	No		R3‑247141
		R3‑247140	(TP to 38.423) Addition of predicted PSCell ID within DC procedure	ZTE Corporation, CATT, Samsung	other	Agreement	Yes	Yes	noted	No
		R3‑247535	AI/ML support for NR-DC	Ericsson	discussion	Approval	Yes	No	available	No
		R3‑247417	(TP for AI/ML BLCR to TS 38.423) AI/ML-based Mobility Optimization in NR-DC	Huawei	other	Agreement	Yes	No	available	No
		R3‑247206	(TP to BLCR TS38.423) NR-DC mobility optimization	NEC	other	Agreement	Yes	No	available	No
		R3‑247299	Discussion on AI/ML for mobility in NR-DC	Samsung	discussion	Approval	Yes	No	available	No
		R3‑247370	Discussion on AI/ML based Mobility Optimization for NR-DC	China Telecom	discussion	Discussion	Yes	No	available	No
		R3‑247371	(TP to TS38.423) Support of AIML based Mobility Optimization for NR-DC	China Telecom	other	Agreement	Yes	No	available	No
		R3‑247443	(TP to BLCR 38.423) Discussion on UE performance feedback in AIML for NR-DC	Lenovo	other	Agreement	Yes	No	available	No
		R3‑247445	TP to BLCR 37.340 AIML for NR-DC	Lenovo, CATT, ZTE Corporation, Samsung	other	Agreement	Yes	No	available	No
		R3‑247470	AI/ML in DC scenario	CATT	discussion	Decision	Yes	No	available	No
		R3‑247471	(TP for TS 38.423) Introducing essentially per-DRB UE performance result for DC	CATT	other	Agreement	Yes	No	available	No
		R3‑247536	(TP to TS38.423) - AI/ML support for NR-DC	Ericsson	other	Agreement	Yes	No	available	No
		R3‑247620	Procedures for AI/ML Mobility Optimization in NR-DC	Nokia	discussion		Yes	No	available	No
		R3‑247621	(TP to BLCR to TS 38.423) AI/ML Mobility for NR-DC	Nokia	other	Agreement	Yes	No	available	No
		R3‑247667	(TP to 38.423) Discussion on AIML based Mobility Optimization for NR-DC	CMCC	other	Agreement	Yes	No	available	No
		R3‑247788	CB:#AIRAN3_NRDC	ZTE	discussion	discussion	No	No- Check the open issue above - Provide TPs to capture agreements	reserved	No
		R3‑247671	Discussion on AIML for split architecure use casesv1	CMCC, ZTE, CATT	discussion	Discussion	Yes	Yes	noted	No
		R3‑247672	Discussion on transferring Energy Cost for split architecure	CMCC, Samsung	discussion	Discussion	Yes	No	available	No
		R3‑247524	Split architecture support for Release 18 use cases	Ericsson, AT&T, Verizon	discussion	Approval	Yes	No	available	No
		R3‑247142	(TP to 38.473, 37.483) Discussion on split architecture	ZTE Corporation	other	Agreement	Yes	No	available	No
		R3‑247207	(TP to BLCR TS38.473) Split architecture support	NEC	other	Agreement	Yes	No	available	No
		R3‑247300	Discussion on AI/ML for NG-RAN in split architecture	Samsung	discussion	Approval	Yes	No	available	No
		R3‑247301	(CR to 37.483) AI/ML for NG-RAN on split architecture	Samsung	CR	Agreement	Yes	No	available	No
		R3‑247376	(TP to TS38.470) Support of AI/ML for NG-RAN split architecutre	China Telecom	other	Agreement	Yes	No	available	No
		R3‑247418	(TP for AI/ML BLCR to TS 38.473) Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases	Huawei	other	Agreement	Yes	No	available	No
		R3‑247444	(TP to BLCR 38.473 and 37.483) Discussion on split architecture related issues for Rel18 use cases	Lenovo	other	Agreement	Yes	No	available	No
		R3‑247446	TP to BLCR 38.401 AIML for RAN in split architecture	Lenovo, CATT, ZTE Corporation	other	Agreement	Yes	No	available	No
		R3‑247472	(TP on 38.470/37.480) AI/ML in split gNBs	CATT	other	Agreement	Yes	No	available	No
		R3‑247525	(TP to 37.483) - Split architecture support for Release 18 use cases	Ericsson, AT&T, Verizon	other	Agreement	Yes	No	available	No
		R3‑247526	(TP to 38.473) - Split architecture support for Release 18 use cases	Ericsson, AT&T, Verizon	other	Agreement	Yes	No	available	No
		R3‑247527	(TP to 38.423) - Split architecture support for Release 18 use cases	Ericsson, AT&T, Verizon	other	Agreement	Yes	No	available	No
		R3‑247603	Discussion on AIML for split architecture	NTT DOCOMO INC..	discussion		Yes	No	available	No
		R3‑247617	Discussion on Energy Cost Reporting in Split Architecture	Nokia, Telecom Italia, Jio, Deutsche Telekom	discussion		Yes	No	available	No
		R3‑247618	Procedures over F1 for the exchange of Energy Cost index	Nokia, Telecom Italia, Jio, Deutsche Telekom	CR		Yes	No	available	No
		R3‑247619	[Draft] LS on New Energy Consumption Measurement for gNB-DU	Nokia, Telecom Italia, Jio, Deutsche Telekom	LS out	Agreement	Yes	No	available	No
		R3‑247622	Discussion on Rel-18 UE Performance measurements	Nokia	discussion		Yes	No	available	No
		R3‑247673	(TP to 38.401) OAM requirement for Energy Saving for split architecure	CMCC, Samsung	other	Agreement	Yes	No	available	No
		R3‑247789	CB:#AIRAN4_SplitArch	CMCC	discussion	discussion	No	No- Check the open issues	reserved	No
		R3‑247144	Discussion on requirements for Continuous MDT solution	Telecom Italia, Jio, BT, Deutsche Telekom	discussion	Decision	Yes	Yes	noted	No
		R3‑247537	Additional discussions on Continuous MDT	Ericsson, InterDigital, Jio	discussion	Approval	Yes	No	available	No
		R3‑247327	Discussion on Continuous MDT	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell	discussion	Agreement	Yes	No	available	No
		R3‑247143	Discussion on continuous MDT collection	ZTE Corporation	discussion		Yes	No	available	No
		R3‑247205	Continuous MDT collection for AI/ML	NEC	discussion	Decision	Yes	No	available	No
		R3‑247302	Discussion on continuous MDT collection targeting the same UE across RRC states	Samsung	discussion	Approval	Yes	No	available	No
		R3‑247377	Discussion on Continuous MDT measurement	China Telecom	discussion	Decision	Yes	No	available	No
		R3‑247393	Discussion on measurement correlation for continuous MDT	CATT	discussion	Decision	Yes	No	available	No
		R3‑247419	On Continuous MDT for AI/ML	Huawei	other	Agreement	Yes	No	available	No
		R3‑247538	(TP to TS38.423) Continuous MDT collection targeting the same UE across RRC states	Ericsson, InterDigital, Jio	other	Agreement	Yes	No	available	No
		R3‑247539	LS on correlation identifiers for Continuous MDT	Ericsson, InterDigital, Jio	LS out	Agreement	Yes	No	available	No
		R3‑247623	Continuous Management-based MDT	Nokia, Qualcomm, Jio, Deutsche Telekom	discussion		Yes	No	available	No
		R3‑247790	CB:#AIRAN5_ContinuousMDT	Ericsson	discussion	discussion	No	No- Check the solutions on the table taken the above principle into account.	reserved	No
12	Additional topological enhancements for NR WI (RAN3-led)
12.1	General	R3‑247029	Support for Wireless Access Backhaul	Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm	CR	Endorsement	Yes	Yes	endorsed	No		R3‑245840
		R3‑247030	(BL CR to 38.300) Introduction of NR Femto Architecture and Protocol Aspects	Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells	draftCR	Endorsement	Yes	Yes	revised	No	R3‑247825	R3‑245864
		R3‑247825	(BL CR to 38.300) Introduction of NR Femto Architecture and Protocol Aspects	Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells	draftCR	Endorsement	No	Yes	endorsed	No		R3‑247030
12.2	Wireless Access Backhaul (WAB)	R3‑247109	(TP for WAB BL CR for TS 38.401): Functional Aspects of WAB-Nodes	Ericsson	other	Agreement	Yes	No	available	No
		R3‑247343	(TP for TS 38.423) Discussion on WAB mobility	Nokia, Nokia Shanghai Bell	other	Agreement	Yes	No	available	No
		R3‑247363	(TPs for TS 38.413) Architecture and Access control for WAB	Huawei	other	Agreement	Yes	No	available	No

Agenda

Topic

TDoc

Title

Source

Type

For

Avail

Treated

Decision

Wdrn

Replaced-by

Replaces

Opening of the meeting

Reminders

2.1

IPR Declaration

2.2

Statement of Antitrust Compliance

2.3

Responsible IT Behavior

2.4

Additional reminders

Approval of the Agenda

R3‑247001

RAN3#126 Meeting Agenda

RAN3 Chair

agenda

Approval

Yes

approved

Approval of the minutes from previous meetings

R3‑247002

RAN3#125-bis Meeting Report

ETSI-MCC

report

Approval

Yes

approved

Documents for immediate consideration

R3‑247003

Guidelines for RAN3 Meetings

RAN3 Chair, RAN3 Vice-Chairs

discussion

Endorsement

Yes

endorsed

Organizational topics

General, protocol principles and issues

R3‑247004

TR 30.531 v1.55.0 Work Plan and Working Procedures - RAN WG3

ETSI-MCC

other

Endorsement

Yes

endorsed

Incoming LSs

8.1

New Incoming LSs

R3‑247009

Reply to SA2 LS on multi-modality awareness

RAN2(Huawei)

LS in

Discussion

Yes

noted

R3‑247113

LS for PDU Set Information Marking Support without QoS parameters

SA2(Vivo)

LS in

Discussion

Yes

noted

R3‑247015

Reply on FS_XRM_Ph2

RAN2(Nokia)

LS in

Discussion

Yes

noted

R3‑247339

Discussion on the LS related to XR

Nokia, Nokia Shanghai Bell

discussion

Yes

noted

R3‑247255

Discussion on LS on XR from SA2

vivo

discussion

Discussion

Yes

noted

R3‑247659

Discussion on SA2 LS on PDU Set Information

ZTE Corporation

discussion

Decision

Yes

noted

R3‑247359

Discussion on the usage of multi-modality information

Huawei

discussion

Yes

noted

R3‑247246

Discussion on on RAN3 support of multi-modality awareness

CMCC

discussion

Discussion

Yes

noted

R3‑247360

[draft] Reply LS on usage of multi-modality information

Huawei

LS out

Agreement

Yes

revised

R3‑247767

[draft] Reply LS on usage of multi-modality information

Huawei

LS out

Agreement

reserved

R3‑247360

R3‑247718

Disccsion on LS for PDU Set Information Marking Support without QoS parameters

CATT

discussion

Decision

Yes

available

R3‑247340

[Draft] Reply LS for PDU Set Information Marking Support without QoS parameters

Nokia, Nokia Shanghai Bell

LS out

Agreement

Yes

available

R3‑247245

Discussion on PDU Set Information Marking Support without QoS parameters

CMCC

discussion

Discussion

Yes

available

R3‑247361

Discussion on the PDU set information marking support without PDU set QoS parameters

Huawei

discussion

Yes

available

R3‑247362

[draft] Reply LS on PDU set information marking support without PDU set QoS parameters

Huawei

LS out

Agreement

Yes

available

R3‑247571

Discussion on SA2 LS regarding PDU Set Information Marking Support without QoS parameters

Ericsson

discussion

Discussion

Yes

available

R3‑247572

LS reply on PDU Set Information Marking Support without QoS parameters

Ericsson

LS out

Agreement

Yes

available

R3‑247660

[Draft]Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters

ZTE Corporation

other

Approval

Yes

available

R3‑247114

LS to RAN3 on renewable energy based LBO

SA5(Huawei)

LS in

Discussion

Yes

noted

R3‑247528

Reply LS on Renewable energy based LBO

Ericsson

LS out

Agreement

Yes

noted

R3‑247700

Discussion on renewable energy based LBO

ZTE Corporation

discussion

Yes

noted

R3‑247701

[Draft]Reply LS on renewable energy based LBO

ZTE Corporation

other

Yes

revised

R3‑247768

[Draft]Reply LS on renewable energy based LBO

ZTE Corporation

other

reserved

R3‑247701

R3‑247568

Discussion on LS from SA5 on renewable energy based LBO

Nokia

discussion

Yes

noted

R3‑247663

[Draft] Reply LS on renewable energy based LBO

Nokia

LS out

Agreement

Yes

noted

R3‑247631

Discussion on renewable energy based LBO

Huawei

discussion

Yes

noted

R3‑247632

[draft] Reply LS on renewable energy based LBO

Huawei

LS out

Agreement

Yes

noted

R3‑247011

LS on UL RRC message segmentation for UECapabilityInformation

RAN2(Qualcomm)

LS in

Discussion

Yes

noted

R3‑247117

Discussion on UL RRC message segmentation for UECapabilityInformation

ZTE Corporation

discussion

Agreement

Yes

noted

R3‑247118

NGAP on UL RRC message segmentation for UECapabilityInformation

ZTE Corporation

Approval

Yes

available

R3‑247119

NGAP on UL RRC message segmentation for UECapabilityInformation

ZTE Corporation

Approval

Yes

available

R3‑247120

Draft LS to SA2 on UL RRC message segmentation for UECapabilityInformation

ZTE Corporation

LS out

Agreement

Yes

available

R3‑247307

NR UE capability storing limitation discussion and draft reply LS

Qualcomm Incorporated

discussion

Agreement

Yes

noted

R3‑247335

Discussion on the UL RRC message segmentation for UECapabilityInformation

Nokia, Nokia Shanghai Bell

discussion

Yes

noted

R3‑247336

Introduction of the signalling of UE capability size of the AMF

Nokia, Nokia Shanghai Bell

Yes

available

R3‑247337

Introduction of the signalling of UE capability size of the AMF

Nokia, Nokia Shanghai Bell

Yes

available

R3‑247338

[DRAFT] Reply LS on UL RRC message segmentation for UECapabilityInformation

Nokia, Nokia Shanghai Bell

LS out

Agreement

Yes

available

R3‑247408

UL RRC message segmentation for UECapabilityInformation

Huawei

discussion

Yes

noted

R3‑247409

Introduction of Allowed UE Radio Capability Size for UECapabilityInformation [UL_Capa_Segmentation]

Huawei

Yes

available

R3‑247410

Introduction of Allowed UE Radio Capability Size for UECapabilityInformation [UL_Capa_Segmentation]

Huawei

Yes

available

R3‑247411

[draft] Reply LS on UL RRC message segmentation for UECapabilityInformation

Huawei

LS out

Agreement

Yes

available

R3‑247589

On the RAN2 LS on "UL RRC message segmentation for UECapabilityInformation"

Ericsson

discussion

Agreement

Yes

noted

R3‑247769

Reply LS to RAN2_(related to_CB:#3_RRCSegmentation)

Qualcomm

LS in

discussion

reserved

R3‑247005

LS on Multicast MBS session restoration procedure for N3mb path failure

CT4(Nokia)

LS in

Discussion

Yes

noted

R3‑247121

Recovery of N3mb path failure for unicast transport of multicast session

ZTE Corporation

Approval

Yes

noted

R3‑247748

Recovery of N3mb path failure for unicast transport of multicast session

ZTE Corporation

Approval

Yes

available

R3‑247240

Recovery of N3mb failure for Multicast Session

Nokia

discussion

Yes

noted

R3‑247247

Recovery of N3mb path failure for unicast transport of multicast session

Nokia

Agreement

Yes

available

R3‑247248

Recovery of N3mb path failure for unicast transport of multicast session

Nokia

Agreement

Yes

revised

R3‑247781

Recovery of N3mb path failure for unicast transport of multicast session

Nokia

Agreement

reserved

R3‑247248

R3‑247249

Recovery of N3mb path failure for unicast transport of multicast session

Nokia

draftCR

Endorsement

Yes

revised

R3‑247782

Recovery of N3mb path failure for unicast transport of multicast session

Nokia

draftCR

Endorsement

reserved

R3‑247249

R3‑247250

Reply LS on Multicast MBS Session Restoration procedure for N3mb path failure

Nokia

LS out

Agreement

Yes

revised

R3‑247783

Reply LS on Multicast MBS Session Restoration procedure for N3mb path failure

Nokia

LS out

Agreement

reserved

R3‑247250

R3‑247251

Consideration on Multicast MBS session restoration procedure for N3mb path failure

Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated

discussion

Agreement

Yes

noted

R3‑247252

Support of Multicast MBS session restoration procedure for N3mb path failure

Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated

Agreement

Yes

revised

R3‑247764

Support of Multicast MBS session restoration procedure for N3mb path failure

Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated

Agreement

Yes

revised

R3‑247802

R3‑247252

R3‑247802

Support of Multicast MBS session restoration procedure for N3mb path failure

Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated, Nokia

Agreement

reserved

R3‑247764

R3‑247253

Support of Multicast MBS session restoration procedure for N3mb path failure

Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated

Agreement

Yes

available

R3‑247254

[Draft] Reply LS on Multicast MBS session restoration procedure for N3mb path failure (Reply to C4-244467)

Huawei

LS out

Agreement

Yes

available

R3‑247720

Restoration of N3mb Failure for MBS multicast

Ericsson

Agreement

Yes

noted

R3‑247721

Restoration of N3mb Failure for MBS multicast

Ericsson

Agreement

Yes

available

R3‑247770

CB:#4_N3mb

Nokia

discussion

reserved

R3‑247010

Reply to SA5 LS on Number of UEs in RRC_INACTIVE state with data transmission

RAN2(Huawei)

LS in

Discussion

Yes

noted

R3‑247597

Counting number of RRC_INACTIVE SDT UEs

Nokia

discussion

Yes

noted

R3‑247752

Response to R3-247597 and R3-247599

ZTE Corporation

response

Yes

noted

R3‑247599

Response LS on number of UEs in RRC_INACTIVE state with data transmission

Nokia

LS out

Agreement

Yes

noted

R3‑247115

LS on AI/ML Model transfer/delivery to UE

SA5(NEC)

LS in

Discussion

Yes

noted

R3‑247759

LS on draft-ietf-raw-technologies, "Reliable and Available Wireless Technologies"

IETF

LS in

Discussion

Yes

noted

R3‑247167

Discussion on the support of semi-persistent CSI-RS resource for LTM candidate cells

ZTE Corporation

discussion

Yes

withdrawn

Yes

R3‑247168

[DRAFT] Reply LS on the support of semi-persistent CSI-RS resource for LTM candidate cells

ZTE Corporation

LS out

Yes

withdrawn

Yes

R3‑247169

[DRAFT] Reply LS on Early TA acquisition for the inter-DU scenario

ZTE Corporation

LS out

Yes

withdrawn

Yes

R3‑247170

Discussion on support of intra-SN SCPAC in MN format

ZTE Corporation

discussion

Yes

withdrawn

Yes

R3‑247171

Support intra-SN SCPAC in MN format - TS37.340

ZTE Corporation

draftCR

Yes

withdrawn

Yes

R3‑247172

Support intra-SN SCPAC in MN format over Xn - TS38.423

ZTE Corporation

Yes

withdrawn

Yes

R3‑247174

Discussion on L3 measurement based LTM support over F1

ZTE Corporation

discussion

Yes

withdrawn

Yes

R3‑247175

Support L3 measurement based LTM support over F1 - TS38.401

ZTE Corporation

Yes

withdrawn

Yes

R3‑247176

Support L3 measurement based LTM support over F1 - TS38.473

ZTE

Yes

withdrawn

Yes

R3‑247177

Support L3 measurement based LTM support over F1 - TS38.470

ZTE Corporation

Yes

withdrawn

Yes

R3‑247178

[Draft]reply LS on L3 measurement based LTM support over F1

ZTE Corporation

LS out

Yes

withdrawn

Yes

8.2

LSin received during the meeting

R3‑247784

Reply LS to SA5 on AIML data collection

RAN2(Nokia)

LS in

discussion

Yes

available

R3‑247798

Reply LS to SA2 on AIML data collection

RAN2(Interdigital)

LS in

discussion

Yes

available

8.3

Left over LSs / pending actions

R3‑247295

Issues for network based solution for SDT partial UE context transfer

Qualcomm Incorporated, ZTE

discussion

Agreement

Yes

noted

R3‑247503

Introduction of SDT network-based solution

Nokia, Ericsson, Huawei, LG Electronics

discussion

Yes

noted

R3‑247179

Discussion on SDT signalling optimization for partial context transfer

ZTE Corporation

discussion

Yes

noted

R3‑247180

[DRAFT] LS on network-based solution for SDT signalling optimization

ZTE Corporation

LS out

Agreement

Yes

available

R3‑247290

Further discussion on support of SDT network-based solution

CATT

discussion

Decision

Yes

available

R3‑247291

Support of SDT network-based solution

CATT, Nokia

draftCR

Approval

Yes

available

R3‑247292

Support of SDT network-based solution

CATT

Approval

Yes

available

R3‑247504

Introduction of SDT network-based solution

Nokia, Huawei, Ericsson, LG Electronics

Yes

available

R3‑247505

Response LS on SDT signalling optimization for partial context transfer

Nokia

LS out

Agreement

Yes

available

R3‑247163

Introduction of SDT network-based solution

Huawei, Nokia, Ericsson, LG Electronics

draftCR

Agreement

Yes

available

R3‑247164

Introduction of SDT network-based solution

Huawei, Nokia, Ericsson, LG Electronics

Agreement

Yes

available

R3‑247573

Introduction of SDT network-based solution

Ericsson, Nokia, Huawei, LG Electronics

Agreement

Yes

available

R3‑247613

Discussion on Improved KPIs involving end-to-end data volume transfer time analytics

Nokia

discussion

Yes

noted

R3‑247754

Response to R3-247613, R3-247506

ZTE Corporation

response

Yes

noted

R3‑247614

[Draft] Reply LS on Improved KPIs involving end-to-end data volume transfer time analytics

Nokia

LS out

Agreement

Yes

noted

R3‑247506

Further discussion related to the Reply LS on improved KPIs

Ericsson

discussion

Approval

Yes

noted

R3‑247507

Reply to Reply LS on improved KPIs involving end-to-end data volume transfer time analytics

Ericsson

LS out

Agreement

Yes

noted

R3‑247508

Correction of existing reference to TS28.552 by updating it to TS28.558

Ericsson

draftCR

Agreement

Yes

noted

Corrections to Rel-18 or earlier releases

9.1

LTE

R3‑247341

Correction of mapped cell support list

Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Thales

draftCR

Endorsement

Yes

noted

R3‑245339

R3‑247449

Correction of mapped cell support list

Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Thales

draftCR

Endorsement

Yes

noted

R3‑245485

R3‑247450

E-SMLC OAM Configuration for IoT NTN

Ericsson, Thales, Huawei

draftCR

Endorsement

Yes

noted

R3‑245482

R3‑247451

E-SMLC OAM Configuration for IoT NTN - Motivation

Ericsson, Huawei, Thales

discussion

Discussion

Yes

noted

R3‑247475

Correction of MT-EDT

Nokia, Peraton Labs

Agreement

Yes

noted

R3‑247476

Correction of MT-EDT

Nokia, Peraton Labs

Agreement

Yes

noted

R3‑247477

Correction of MT-EDT

Nokia, Peraton Labs

Yes

noted

R3‑247734

Correction on criticality of Measurement Result

ZTE Corporation, China Unicom

Agreement

Yes

noted

R3‑247735

Correction on criticality of Measurement Result

ZTE Corporation, China Unicom

Agreement

Yes

noted

R3‑247736

Correction on criticality of Measurement Result

ZTE Corporation, China Unicom

Agreement

Yes

noted

R3‑247739

Discussion on criticality of measurement result

ZTE Corporation, CATT, China Telecom, China Unicom

discussion

Approval

Yes

noted

R3‑247740

Correction on criticality of Measurement Result for Data Collection

ZTE Corporation, Lenovo, CMCC, China Telecom, China Unicom

Yes

noted

R3‑247464

Discussion on Configuration Update procedure

CATT

discussion

Decision

Yes

noted

9.2

R3‑247014

Reply LS on Early TA acquisition for the inter-DU scenario

RAN2(Google)

LS in

Discussion

Yes

noted

R3‑247124

Corrections for Early TA acquisition for PDCCH order in LTM

Google, ZTE, Huawei, Ericsson, Nokia, CATT, China Telecom, LG Electronics

Agreement

Yes

revised

R3‑247772

Corrections for Early TA acquisition for PDCCH order in LTM

Google, ZTE, Huawei, Ericsson, Nokia, CATT, China Telecom, LG Electronics, Samsung

Agreement

Yes

agreed

R3‑247124

R3‑247012

Reply LS on intra-SN SCPAC in MN format

RAN2(ZTE)

LS in

Discussion

Yes

noted

R3‑247173

[DRAFT] Reply LS on intra-SN SCPAC in MN format

ZTE Corporation

LS out

Agreement

Yes

noted

R3‑247729

Stage-2 updates for intra-SN S-CPAC with MN involvement

Ericsson, Nokia, CATT

draftCR

Endorsement

Yes

revised

R3‑247773

Stage-2 updates for intra-SN S-CPAC with MN involvement

Ericsson, Nokia, CATT

draftCR

Endorsement

reserved

R3‑247729

R3‑247742

Correction on “S-CPAC Request” IE description for Intra-SN S-CPAC in MN format

LG Electronics Inc.

Agreement

Yes

agreed

R3‑247013

L3 measurement based LTM support over F1

RAN2(Vodafone)

LS in

Discussion

Yes

noted

R3‑247105

Discussion on L3 L1/2 Triggered Mobility

Nokia, LG Electronics, NTT Docomo

discussion

Discussion

Yes

noted

R3‑247728

Triggering LTM without L1 measurements UE capability

Ericsson, Vodafone, CATT

discussion

Discussion

Yes

noted

R3‑247237

Signaling enhancements for L3 measurement based R18 LTM

Qualcomm Incorporated, Reliance JIO, Bharti Airtel

discussion

Decision

Yes

noted

R3‑247106

L3 based L1/2 Triggered Mobility

Nokia, NTT Docomo, LG Electronics

Agreement

Yes

noted

R3‑245401

R3‑247125

Corrections for L3 measurement triggered LTM cell switch

Google

Agreement

Yes

noted

R3‑245352

R3‑247265

Discussion on L3 measurement based LTM support over F1 (CRs included)

Huawei

discussion

Yes

noted

R3‑247349

Discussion on L3 measurement based LTM

Samsung

discussion

Approval

Yes

noted

R3‑247460

Stage 2 updates for support of L3 measurements based LTM

CATT, Ericsson, Vodafone

Approval

Yes

noted

R3‑245240

R3‑247725

F1 support for L3 measurements-based LTM

Ericsson, Vodafone, CATT

Agreement

Yes

noted

R3‑245564

R3‑247394

Correction on the presence issue of TCI states configuration List

CATT,Google, Huawei, Nokia, China Telecom, CMCC

Agreement

Yes

noted

R3‑247774

CB:#7_L3LTM

Vodafone

discussion

Yes

available

R3‑247465

Discussion on definition of UE performance metrics

CATT,Deutsche Telekom,China Unicom,ZTE,China Telecom,Jio

discussion

Decision

Yes

noted

R3‑247466

[DRAFT] LS on UE level measurements

CATT,Deutsche Telekom,China Unicom,ZTE,China Telecom,Jio

LS out

Agreement

Yes

noted

R3‑247412

On Rel-18 UE performance feedback for AI/ML for NG-RAN

Huawei, Lenovo, Deutsche Telekom, Telecom Italia, BT, InterDigital, Nokia

discussion

Decision

Yes

noted

R3‑247413

[Draft] LS on per-UE UE performance metrics

Huawei, Lenovo, Deutsche Telekom, Telecom Italia, BT, InterDigital, Nokia

LS out

Agreement

Yes

revised

R3‑247775

[Draft] LS on per-UE UE performance metrics

Huawei, Lenovo, Deutsche Telekom, Telecom Italia, BT, InterDigital, Nokia

LS out

Agreement

reserved

R3‑247413

R3‑247514

Correction for Data Collection Reporting procedure’s interaction with Handover Request procedure

Ericsson, Jio, AT&T, InterDigital, Lenovo

Agreement

Yes

noted

R3‑247288

Correction to area-specific SRS activation

CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated, Xiaomi, Huawei

draftCR

Endorsement

Yes

endorsed

R3‑247289

Correction to area-specific SRS activation

CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated, Xiaomi, Huawei

Agreement

Yes

agreed

R3‑245063

R3‑247738

Support of UE specific SRS reservation

ZTE Corporation, CATT, Huawei, Samsung, Nokia, Ericsson, Xiaomi

Agreement

Yes

revised

R3‑247776

R3‑245105

R3‑247776

Support of UE specific SRS reservation

ZTE Corporation, CATT, Huawei, Samsung, Nokia, Ericsson, Xiaomi

Agreement

agreed

R3‑247738

R3‑247605

Support of UE specific SRS reservation

Samsung, CATT, Huawei, ZTE, Ericsson, Nokia, Xiaomi

Agreement

Yes

agreed

R3‑245122

R3‑247333

Correction on Positioning SRS Resource in TS38.455

China Telecom, ZTE,CATT

Agreement

Yes

available

R3‑247334

Correction on Positioning SRS Resource in TS38.473

China Telecom, ZTE,CATT

Agreement

Yes

noted

R3‑247737

Correction on criticality of Time Window Information SRS

ZTE Corporation, CATT, Ericsson, Huawei, Nokia

Agreement

Yes

agreed

R3‑247397

Correction on Measurement Time Window

Huawei, CMCC, CUC, Ericsson, Nokia

Agreement

Yes

revised

R3‑247777

Correction on Measurement Time Window

Huawei, CMCC, CUC, Ericsson, Nokia

Agreement

reserved

R3‑247397

R3‑247575

Correction on Measurement Time Window

Ericsson, Huawei, CMCC, CUC, Nokia

Agreement

Yes

revised

R3‑247778

Correction on Measurement Time Window

Ericsson, Huawei, CMCC, CUC, Nokia

Agreement

reserved

R3‑247575

R3‑247570

Correction of UE Rx-Tx Time difference measurements

Ericsson, Polaris Wireless, CATT, Huawei

Agreement

Yes

revised

R3‑247779

R3‑245471

R3‑247779

Correction of UE Rx-Tx Time difference measurements

Ericsson, Polaris Wireless, CATT, Huawei, ZTE, China Telecom

Agreement

reserved

R3‑247570

R3‑247530

Discussion on Periodic E-CID Measurement Procedure

Jio

discussion

Agreement

Yes

noted

R3‑247532

Periodic E-CID measurement procedure

Jio

Agreement

Yes

noted

R3‑247562

NR-DC QMC Coordination for RRC Segmentation

Nokia, ZTE, Samsung

discussion

Yes

noted

R3‑247656

Discussion on NR-DC QMC Coordination for RRC Segmentation

ZTE Corporation, Samsung, Nokia, China Unicom, China Telecom

discussion

Approval

Yes

noted

R3‑247655

Introduction to coordination for QoE RRC segmentation in NR-DC

ZTE Corporation, Samsung, Nokia, China Unicom, China Telecom

draftCR

Agreement

Yes

noted

R3‑247606

Corrections to QMC support in NR-DC for RRC Segmentation

Samsung, ZTE Corporation, Nokia, China Unicom, China Telecom

Agreement

Yes

noted

R3‑247267

QoE measurement handling in idle mode

CATT, Ericsson, ZTE, Xiaomi

draftCR

Endorsement

Yes

endorsed

R3‑245251

R3‑247638

Further miscellaneous corrections to QMC procedure

Huawei, China Unicom, Lenovo

draftCR

Endorsement

Yes

noted

R3‑247218

Corrections for QoE intra-5GC inter-RATs mobility

NEC

draftCR

Endorsement

Yes

noted

R3‑247219

Corrections for QoE intra-5GC inter-RATs mobility on XnAP

NEC

Agreement

Yes

noted

R3‑247704

Discussion on abnormal case of Xn setup procedure

ZTE Corporation

discussion

Yes

noted

R3‑247705

Correction on Xn Setup message

ZTE Corporation

Yes

available

R3‑247706

Correction on Xn Setup message

ZTE Corporation

available

R3‑247707

Correction on Xn Setup message

ZTE Corporation

Yes

available

R3‑247708

Correction on Xn Setup message

ZTE Corporation

available

R3‑247515

Corrections on Xn Setup Duplication

Ericsson

Agreement

Yes

noted

R3‑247516

Corrections on Xn Setup Duplication

Ericsson

Agreement

Yes

available

R3‑247517

Corrections on Xn Setup Duplication

Ericsson

Agreement

Yes

available

R3‑247518

Corrections on Xn Setup Duplication

Ericsson

Agreement

Yes

available

R3‑247780

CB:#12_MultipleXnSetup

ZTE

discussion

reserved

R3‑247199

Correction on IAB RESOURCE COORDINATION

ZTE Corporation, Lenovo, Nokia, Nokia Shanghai Bell, Samsung

Agreement

Yes

agreed

R3‑247200

Correction on IAB RESOURCE COORDINATION

ZTE Corporation, Lenovo, Nokia, Nokia Shanghai Bell, Samsung

Agreement

Yes

agreed

R3‑247274

Correction for resource configuration

CATT

Agreement

Yes

revised

R3‑247765

Correction for resource configuration

CATT

Approval

Yes

noted

R3‑247274

R3‑247275

Correction for resource configuration

CATT

Approval

Yes

revised

R3‑247766

Correction for resource configuration

CATT

Approval

Yes

noted

R3‑247275

R3‑247478

Correction of MBS PDCP packets discard

Nokia, Huawei, Qualcomm, CMCC, CBN, China Broadnet

discussion

Yes

available

R3‑247479

Correction on PDCP packets discard in case of MBS broadcast path update

Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, Chnia Broadnet

Yes

revised

R3‑247807

Correction on PDCP packets discard in case of MBS broadcast path update

Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, Chnia Broadnet

reserved

R3‑247479

R3‑247481

Correction of MBS PDCP packets discard in case of MBS broadcast path update

Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, China Broadnet

Yes

revised

R3‑247808

Correction of MBS PDCP packets discard in case of MBS broadcast path update

Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, China Broadnet

reserved

R3‑247481

R3‑247122

Draft CR with rethinking on Rel-18 group paging design

ZTE Corporation, China Telecom, CMCC, Lenovo

draftCR

Endorsement

Yes

noted

R3‑247510

Stage 2 correction for network slice support during XN handover

Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia

draftCR

Endorsement

Yes

noted

R3‑245552

R3‑247511

Stage 2 correction for network slice support during XN handover

Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia

draftCR

Endorsement

Yes

noted

R3‑245553

R3‑247512

Stage 2 correction for network slice support during XN handover

Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia

draftCR

Endorsement

Yes

noted

R3‑245554

R3‑247513

Stage 2 correction for network slice support during XN handover

Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia

draftCR

Endorsement

Yes

noted

R3‑245555

R3‑247574

Corrections to Stage-2 for XR awareness

Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE, China Telecom, Xiaomi, CATT, CMCC, Lenovo

draftCR

Endorsement

Yes

revised

R3‑247817

Corrections to Stage-2 for XR awareness

Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE, China Telecom, Xiaomi, CATT, CMCC, Lenovo

draftCR

Endorsement

Yes

endorsed

R3‑247574

R3‑247358

Discussion on the PDCP SN gap report handling during UE’s handover

Huawei, CATT, Xiaomi, China Telecom, LG Electronics

discussion

Discussion

Yes

noted

R3‑247818

CB:#26_PDCPSN

Huawei

discussion

reserved

R3‑247155

Correction on CIoT optimization with 5GC

Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia

Agreement

Yes

available

R3‑247156

Correction on CIoT optimization with 5GC

Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia

Agreement

Yes

available

R3‑247157

Correction on CIoT optimization with 5GC

Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia

Agreement

Yes

available

R3‑247690

Clarification on the name of AP ID over Xn interface for Rel-15

CMCC, CATT, Huawei, ZTE

Approval

Yes

available

R3‑247691

Clarification on the name of AP ID over Xn interface for Rel-16

CMCC, CATT, Huawei, ZTE

Approval

Yes

available

R3‑247692

Clarification on the name of AP ID over Xn interface for Rel-17

CMCC, CATT, Huawei, ZTE

Approval

Yes

available

R3‑247693

Clarification on the name of AP ID over Xn interface for Rel-18

CMCC, CATT, Huawei, ZTE

Approval

Yes

available

R3‑247406

Introduction of AUN3 device access

Huawei, Nokia, Nokia Shanghai Bell, CATT

Yes

available

R3‑245379

R3‑247407

Introduction of AUN3 device access

Huawei, Nokia, Nokia Shanghai Bell, CATT

Yes

available

R3‑245380

R3‑247583

Support of AUN3 devices

Ericsson, BT, China Unicom

Agreement

Yes

available

R3‑245577

R3‑247584

Support of AUN3 devices

Ericsson, BT, China Unicom

Agreement

Yes

available

R3‑245578

R3‑247633

Correction of Unavailable GUAMI in AMF Status Indication message

Huawei, China Telecom, China Unicom

Yes

available

R3‑245405

R3‑247634

Correction of Unavailable GUAMI in AMF Status Indication message

Huawei, China Telecom, China Unicom

Yes

available

R3‑245406

R3‑247635

Correction of Unavailable GUAMI in AMF Status Indication message

Huawei, China Telecom, China Unicom

Yes

available

R3‑245407

R3‑247644

Addition of procedural description of CPAC Configuration

ZTE Corporation, Samsung, China Telecom

Approval

Yes

available

R3‑247395

Correction of mapped cell support list

Huawei, Ericsson, Nokia, Thales

draftCR

Agreement

Yes

noted

R3‑247396

Correction of mapped cell support list

Huawei, Ericsson, Nokia, Thales

draftCR

Agreement

Yes

noted

R3‑247540

Clarification on NTN time-based handover over NG

ZTE Corporation. CMCC, China Telecom

Approval

Yes

available

R3‑247541

Clarification on NTN time-based handover over S1

ZTE Corporation, CMCC, China Telecom

Approval

Yes

available

R3‑247542

Discussion on Location Reporting Control procedure for UPF Relocation

ZTE Corporation, CMCC, China Telecom

other

Approval

Yes

available

R3‑247543

Correction on Location Reporting Control procedure for NR NTN

ZTE Corporation, CMCC, China Telecom

Approval

Yes

available

R3‑247544

Correction on Location Reporting Control procedure for NR NTN

ZTE Corporation, CMCC, China Telecom

Approval

Yes

available

R3‑247553

Support MUSIM capability restriction over XnAP

Ericsson, Qualcomm Incorporated, Xiaomi

Agreement

Yes

available

R3‑241650

R3‑247554

Support MUSIM capability restriction

Ericsson, Qualcomm Incorporated, Xiaomi

discussion

Discussion

Yes

available

R3‑241653

R3‑247555

Support MUSIM capability restriction over NGAP

Ericsson, Qualcomm Incorporated, Xiaomi

Agreement

Yes

available

R3‑241654

R3‑247133

Clarification of the chapter title to match the description of the UE History Information

Nokia, ZTE, CMCC

draftCR

Endorsement

Yes

available

R3‑245477

R3‑247509

On the special case of Nrb 12 and Nrb 20 Transmission Bandwidth configurations

Ericsson, Strict, Qualcomm

discussion

Approval

Yes

available

R3‑247165

Editorial correction on TNL Configuration Info

NTTDOCOMO, INC.

Yes

available

R3‑245355

R3‑247166

Editorial correction on TNL Configuration Info

NTTDOCOMO, INC.

Yes

available

R3‑245356

R3‑247259

Clarification on resumption of non-SDT bearer in SDT termination

Google

Agreement

Yes

available

R3‑247266

Correction on the Signalling based MDT PLMN List

Huawei

draftCR

Yes

available

R3‑247134

Correction of a wrong description of the S-NG-RAN node Counter Check procedure

Nokia

Agreement

Yes

available

R3‑245478

R3‑247135

Correction of a wrong description of the S-NG-RAN node Counter Check procedure

Nokia

Agreement

Yes

available

R3‑245479

R3‑247136

Correction of a wrong description of the S-NG-RAN node Counter Check procedure

Nokia

Agreement

Yes

available

R3‑245480

R3‑247137

Correction of a wrong description of the S-NG-RAN node Counter Check procedure

Nokia

Agreement

Yes

available

R3‑245481

R3‑247711

Correction on DL LBT failure information

CATT

draftCR

Agreement

Yes

available

R3‑247743

Correction on the UE Initial Access procedure

Ericsson

Yes

available

R3‑247744

Correction on the UE Initial Access procedure

Ericsson

Yes

available

R3‑247745

Correction on the UE Initial Access procedure

Ericsson

Yes

available

R3‑247746

Correction on the UE Initial Access procedure

Ericsson

Yes

available

R3‑247107

L3 based L1/2 Triggered Mobility

Nokia

withdrawn

Yes

R3‑247194

Periodic E-CID measurement procedure

Jio

Agreement

Yes

withdrawn

Yes

R3‑247792

update of broadcast MCCH information

RAN3(Nokia)

LS out

Agreement

reserved

9.3

Endorsed TEI CRs Review

R3‑247037

Correction on configuration update for an inactive Multicast session

ZTE Corporation, Huawei, CATT, Nokia, Lenovo

Agreement

Yes

agreed

R3‑245042

R3‑247038

Correction of Positioning SI for connected UE

ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi

Agreement

Yes

agreed

R3‑245099

R3‑247039

Correction of Positioning SI for connected UE

ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi

Agreement

Yes

agreed

R3‑245100

R3‑247040

Correction of Positioning SI for connected UE

ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi

Agreement

Yes

agreed

R3‑245101

R3‑247041

Correction on conditional PSCell addition or change failure

CATT, CMCC, ZTE, Nokia, Nokia Shanghai Bell

draftCR

Endorsement

Yes

endorsed

R3‑245180

R3‑247042

Correcting IE reference in Cell Replacing Info

Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC

Agreement

Yes

agreed

R3‑245228

R3‑247043

Correcting IE reference in Cell Replacing Info

Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC

Agreement

Yes

agreed

R3‑245229

R3‑247044

Corrections on MP relay based PDCP duplication

ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑245301

R3‑247045

Clarification of the usage of the UE History Information

Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone

Agreement

Yes

agreed

R3‑245308

R3‑247046

L2 reset for intra-DU LTM

Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, Ericsson, CATT

Agreement

Yes

revised

R3‑247811

R3‑245341

R3‑247811

L2 reset for intra-DU LTM

Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, Ericsson, CATT

Agreement

agreed

R3‑247046

R3‑247047

Introduction of 2Rx XR devices support [2Rx_XR_Device]

Huawei, Qualcomm, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, China Telecom

Agreement

Yes

revised

R3‑247810

R3‑245385

R3‑247810

Introduction of 2Rx XR devices support [2Rx_XR_Device]

Huawei, Qualcomm, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, China Telecom

Agreement

Yes

agreed

R3‑247047

R3‑247048

Clarification of the usage of the UE History Information

Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone

Agreement

Yes

agreed

R3‑245400

R3‑247049

Clarification on indication of dormant cell re-activation

CATT, Nokia, Huawei, CMCC, ZTE, NEC, Samsung

Agreement

Yes

revised

R3‑247814

R3‑245687

R3‑247814

Clarification on indication of dormant cell re-activation

CATT, Nokia, Huawei, CMCC, ZTE, NEC, Samsung

Agreement

available

R3‑247049

R3‑247050

Positioning measurement correction related to “shall, if supported”

Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT

Agreement

Yes

agreed

R3‑245691

R3‑247051

Positioning measurement correction related to “shall, if supported”

Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT

Agreement

Yes

agreed

R3‑245692

R3‑247052

Positioning measurement correction related to “shall, if supported”

Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT

Agreement

Yes

agreed

R3‑245693

R3‑247053

Positioning measurement correction related to “shall, if supported”

Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT

Agreement

Yes

agreed

R3‑245694

R3‑247054

Positioning measurement correction related to “shall, if supported”

Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT

Agreement

Yes

agreed

R3‑245695

R3‑247055

Positioning measurement correction related to “shall, if supported”

Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT

Agreement

Yes

agreed

R3‑245696

R3‑247056

Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE]

Ericsson, CATT, Xiaomi, ZTE, Huawei, Qualcomm Inc.

Agreement

Yes

agreed

R3‑245697

R3‑247057

Option 2: Correction on DU collecting and reporting of DL LBT failure information

CATT, Ericsson, Nokia, Huawei, Samsung, ZTE

Agreement

Yes

revised

R3‑247812

R3‑245700

R3‑247812

Option 2: Correction on DU collecting and reporting of DL LBT failure information

CATT, Ericsson, Nokia, Huawei, Samsung, ZTE

Agreement

Yes

agreed

R3‑247057

R3‑247058

Correction for the semantics description

Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei

Agreement

Yes

agreed

R3‑245704

R3‑247059

Correction for the semantics description

Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei

Agreement

Yes

agreed

R3‑245705

R3‑247060

Correction for the semantics description

Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei

Agreement

Yes

agreed

R3‑245706

R3‑247061

Correction for the semantics description

Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei

Agreement

Yes

agreed

R3‑245707

R3‑247062

Corrections on SL relay procedure

LG Electronics, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT

Agreement

Yes

agreed

R3‑245708

R3‑247063

Stage-2 support for LTM L2 reset

Ericsson, Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, CATT

Agreement

Yes

agreed

R3‑245724

R3‑247064

Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑245726

R3‑247065

Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑245727

R3‑247066

Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑245729

R3‑247067

Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

revised

R3‑247821

R3‑245730

R3‑247821

Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑247067

R3‑247068

Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics

China Telecom, CATT, China Unicom, Ericsson, Huawei,ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑245731

R3‑247069

Correction to Requested DL PRS Transmission Characteristics

Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia

Agreement

Yes

agreed

R3‑245738

R3‑247070

Correction to Requested DL PRS Transmission Characteristics

Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia

Agreement

Yes

agreed

R3‑245739

R3‑247071

Correction for the reference specification on UE History Information for Rel-18

CMCC, Huawei, CATT, ZTE, Nokia

Agreement

Yes

revised

R3‑247813

R3‑245743

R3‑247813

Correction for the reference specification on UE History Information

CMCC, Huawei, CATT, ZTE, Nokia

Agreement

agreed

R3‑247071

R3‑247072

Clarification on SpCell ID replacement

Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE

Agreement

Yes

agreed

R3‑245749

R3‑247073

Clarification on SpCell ID replacement

Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE

Agreement

Yes

agreed

R3‑245750

R3‑247074

Clarification on SpCell ID replacement

Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE

Agreement

Yes

agreed

R3‑245751

R3‑247075

Correction on AI/ML Terminology

Nokia

draftCR

Endorsement

Yes

endorsed

R3‑245772

R3‑247076

OAM Requirements on Energy Cost index

Nokia, Jio, Telecom Italia

draftCR

Endorsement

Yes

endorsed

R3‑245773

R3‑247077

Correction on broadcast reception for eRedCap UE [RedcapMBS]

Huawei, Qualcomm Incorporated, ZTE, CBN, Nokia, CATT

Agreement

Yes

agreed

R3‑245776

R3‑247078

Correction on broadcast reception for eRedCap UE [RedcapMBS]

Huawei, Qualcomm Incorporated, ZTE, CBN, Nokia, CATT

Agreement

Yes

agreed

R3‑245777

R3‑247079

Correction on MBS Service Area

Huawei, CMCC, Ericsson, CBN, Nokia

Agreement

Yes

agreed

R3‑245778

R3‑247080

Correction on Retrieve UE Context Confirm

Huawei, Nokia, Qualcomm Incorporated

Agreement

Yes

agreed

R3‑245780

R3‑247081

Correction on Retrieve UE Context Confirm

Huawei, Nokia, Qualcomm Incorporated

Agreement

Yes

agreed

R3‑245781

R3‑247082

Correction of N3IWF user location information

Huawei, Nokia, Nokia Shanghai Bell, CATT

Agreement

Yes

agreed

R3‑245783

R3‑247083

Alignment of procedural text for LTM early sync procedure

CATT, China Telecom, CMCC, Huawei, Google, Nokia, LG Electronics, Ericsson, Samsung

Agreement

Yes

agreed

R3‑245786

R3‑247084

Correction on LTM procedures for Inter-DU case and CU-UP change

LG Electronics, CATT, CMCC, China Telecom, Ericsson, Google, Huawei, Lenovo, NEC, Nokia, NTT Docomo, Samsung, Qualcomm, ZTE

Agreement

Yes

agreed

R3‑245790

R3‑247085

Correction of TRP Geographical coordinates [PosLocalCoords]

Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE

Agreement

Yes

agreed

R3‑245791

R3‑247086

Correction of TRP Geographical coordinates [PosLocalCoords]

Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE

Agreement

Yes

agreed

R3‑245792

R3‑247087

Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑245803

R3‑247092

Correction of IAB F1-C transfer in NR-DC

ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung

draftCR

Endorsement

Yes

endorsed

R3‑245809

R3‑247093

Correction of IAB F1-C transfer in NR-DC

ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung

draftCR

Endorsement

Yes

endorsed

R3‑245810

R3‑247094

Correction on BAP mapping configuration for IAB

Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT

Agreement

Yes

agreed

R3‑245811

R3‑247095

Correction on BAP mapping configuration for IAB

Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT

Agreement

Yes

agreed

R3‑245812

R3‑247096

Correction on BAP mapping configuration for IAB

Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT

Agreement

Yes

agreed

R3‑245813

R3‑247098

Correction of mobility change procedure

Huawei, Nokia, Deutsche Telekom

Agreement

Yes

agreed

R3‑245816

R3‑247099

Coarse UE Location Information Reporting from MME to eNB for NB-IoT Ues

Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT

draftCR

Endorsement

Yes

revised

R3‑247815

R3‑245817

R3‑247815

Coarse UE Location Information Reporting from MME to eNB for NB-IoT Ues

Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT

draftCR

Endorsement

agreed

R3‑247099

R3‑247100

Coarse UE Location Information Reporting from MME to eNB – S1AP Impacts

Ericsson, Huawei, Qualcomm Incorporated, CATT, ZTE

Agreement

Yes

revised

R3‑247816

R3‑245818

R3‑247816

Coarse UE Location Information Reporting from MME to eNB – S1AP Impacts

Ericsson, Huawei, Qualcomm Incorporated, CATT, ZTE

Agreement

Yes

agreed

R3‑247100

R3‑247101

Correction of N3IWF user location information

Huawei, Nokia, Nokia Shanghai Bell, CATT

Agreement

Yes

agreed

R3‑245825

R3‑247127

introduction of Missing Bandwidths in FR1 SRS Bandwidth

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑247088

R3‑247128

introduction of Missing bandwidths in FR1 SRS Bandwidth

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑247089

R3‑247129

introduction of Missing bandwidths in FR1 SRS Bandwidth

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑247090

R3‑247130

introduction of Missing bandwidths in FR1 SRS Bandwidth

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

agreed

R3‑247091

R3‑247097

Stage 2 correction for AI/ML for NG-RAN

Ericsson, Huawei, Nokia, InterDigital

draftCR

Endorsement

Yes

endorsed

R3‑245814

R3‑247088

introduction of Missing Bandwidths in FR1 SRS Bandwidth

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

withdrawn

Yes

R3‑247127

R3‑245804

R3‑247089

introduction of Missing Bandwidths in FR1 SRS Bandwidth

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

withdrawn

Yes

R3‑247128

R3‑245805

R3‑247090

introduction of Missing Bandwidths in FR1 SRS Bandwidth

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

withdrawn

Yes

R3‑247129

R3‑245806

R3‑247091

introduction of Missing Bandwidths in FR1 SRS Bandwidth

China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell

Agreement

Yes

withdrawn

Yes

R3‑247130

R3‑245807

R3‑247123

Correction on configuration update for an inactive Multicast session

ZTE Corporation, Huawei, CATT

Approval

withdrawn

Yes

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

10.1

General

R3‑247019

(BL CR to 36.300 for SON) Addition of SON enhancements

Lenovo

draftCR

Endorsement

Yes

available

R3‑245028

R3‑247020

(BL CR to 36.423) Addition of SON enhancements

CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia

Endorsement

Yes

available

R3‑245851

R3‑247021

(BL CR to 37.340 for SON) on MRO for S-CPAC

CMCC

draftCR

Endorsement

Yes

available

R3‑245852

R3‑247022

(BL CR to 38.300 for SON) Addition of SON enhancements

China Unicom, Nokia, Huawei, Lenovo, CATT, Ericsson, Qualcomm Inc., Samsung, LG Electronics Inc, ZTE Corporation

draftCR

Endorsement

Yes

available

R3‑245853

R3‑247023

(BL CR to 38.401 for SON) Addition of SON enhancements

ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung

Endorsement

Yes

available

R3‑245854

R3‑247024

(BL CR to 38.413 for MDT) Addition of MDT enhancements

Nokia

Endorsement

Yes

available

R3‑245855

R3‑247025

(BL CR to 38.423 for MDT) Addition of MDT enhancements

CATT

Endorsement

Yes

available

R3‑245856

R3‑247026

(BL CR to 38.423 for SON) Addition of SON enhancements

ZTE Corporation, Samsung, Nokia, Lenovo, Jio

Endorsement

Yes

available

R3‑245857

R3‑247027

(BL CR to 38.473 for SON) Addition of SON enhancements

Huawei, Nokia, Jio

Endorsement

Yes

available

R3‑245858

R3‑247681

Workplan for Rel-19 SON_MDT Enhancement

CMCC, China Unicon

Work Plan

Information

Yes

available

10.2

MRO Enhancements

R3‑247494

(TP for BL CR to 38.300 for SON) MRO enhancements for LTM

Ericsson

other

Agreement

Yes

available

R3‑247151

MRO enhancements for R18 mobility mechanisms

Qualcomm Incorporated

discussion

Discussion

Yes

available

R3‑247159

(TP for BLCR for SON for 38.300, 38.401,38.473, 38.413, 37.340, 38.423) MRO enhancement for R18 mobility mechanisms

Huawei

other

Agreement

Yes

available

R3‑247223

(TP for SON BLCR of 38.473) MRO for LTM with RLF-report unavailible

NEC

other

Agreement

Yes

available

R3‑247296

(TP to BL CR TS38.401) MRO for LTM

Samsung

other

Agreement

Yes

available

R3‑247308

(TP for SON BL CR for TS 38.473)Discussion on LTM MRO

Google

other

Agreement

Yes

available

R3‑247309

Failure scenarios on MRO for CHO with candidate SCGs

Samsung, Cybercore, Lenovo

discussion

Approval

Yes

available

R3‑247310

(TP for SON BLCR TS38.300, TS37.340 and TS38.423) MRO for CHO with candidate SCGs and S-CPAC

Samsung

other

Approval

Yes

available

R3‑247321

(TP for SON BL CR for TS 38.473 and for TS 37.340) MRO Enhancements for LTM, CHO with Candidate SCG(s) and S-CPAC

Nokia

other

Agreement

Yes

available

R3‑247424

(TP for SON BLCR for 38.401) Discussion on MRO for LTM

Lenovo

other

Agreement

Yes

available

R3‑247425

(TP for SON BLCR for 37.340) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s)

Lenovo

other

Agreement

Yes

available

R3‑247601

Discussion on MRO enhancements for LTM

LG Electronics Inc.

discussion

Discussion

Yes

available

R3‑247645

Discussion on MRO Enhancements

China Unicom

discussion

Discussion

Yes

available

R3‑247702

(TP for TS 38.401 TS38.473) Discussion on MRO

ZTE Corporation

other

Agreement

Yes

available

R3‑247712

(TP 37.340) MRO for R18 mobility mechanisms

CATT

other

Agreement

Yes

available

10.3

SON/MDT for NTN and Slicing

10.3.1

Intra-NTN Mobility

R3‑247545

(TP to BL CR for 38.300) Further discussion on SONMDT enhancement for NTN

ZTE Corporation

other

Agreement

Yes

available

R3‑247495

SON-MDT enhancements for NTN

Ericsson

discussion

Yes

available

R3‑247713

(TP for 38.300 and 38.413) Intra-NTN mobility for SONMDT

CATT

other

Decision

Yes

available

R3‑247131

[TP to BL CR to 38.423, SON] Solution to avoid restarting MRO in NTN deployments

Nokia

other

Agreement

Yes

available

R3‑245311

R3‑247152

SON MDT for NTN

Qualcomm Incorporated

discussion

Discussion

Yes

available

R3‑247225

Discussion on SON/MDT enhancements for NTN

NEC

discussion

Decision

Yes

available

R3‑247264

(TP for MDT BLCRs for TS38.413, TS38.423, TS37.320) SON for Intra-NTN mobility

Huawei

other

Yes

available

R3‑247426

Discussion on MRO for intra-NTN mobility

Lenovo

discussion

Yes

available

R3‑247612

Discussion on SON enhancements for NTN

Samsung Electronics Polska

discussion

Yes

available

R3‑247646

Discussion on SONMDT enhancements for NTN mobility

China Unicom

discussion

Yes

available

R3‑247666

(TP to 38.300) Discussion on SONMDT enhancement for NTN

CMCC

other

Agreement

Yes

available

10.3.2

Network Slicing

R3‑247132

[TP to BL CR to 38.300, MDT] MDT solution for slice support and slice-related mobility enhancements

Nokia

other

Agreement

Yes

available

R3‑245312

R3‑247496

On MDT enhancements for Network Slicing

Ericsson, T-Mobile US, InterDigital, Jio, Telecom Italia, Deutsche Telekom

discussion

Agreement

Yes

available

R3‑247703

Further consideration on SON/MDT for Slicing

ZTE Corporation

discussion

Yes

available

R3‑247153

SON MDT for network slicing

Qualcomm Incorporated

discussion

Discussion

Yes

available

R3‑247160

SON and MDT for Network Slicing

Huawei

other

Yes

available

R3‑247497

On SON enhancements for Network Slicing

Ericsson, InterDigital, Jio

discussion

Agreement

Yes

available

R3‑247498

(TP for BLCR for MDT for TS 38.413) Addition of MDT enhancements

Ericsson

other

Agreement

Yes

available

R3‑247650

Discussion on SONMDT enhancements for network slicing

China Unicom

discussion

Yes

available

R3‑247668

Discussion on SONMDT for network slicing

CMCC

discussion

Discussion

Yes

available

R3‑247714

Network slicing for SONMDT

CATT

discussion

Decision

Yes

available

10.4

R18 leftovers

R3‑247682

MHI and UHI Enhancement for SCG Deactivation Activation

CMCC, Huawei, CATT, Lenovo, ZTE

discussion

Discussion

Yes

available

R3‑247162

[DRAFT] Reply LS on MHI enhancement solution for SCG deactivation/activation

Huawei, CMCC, ZTE, CATT [will be RAN3]

LS out

Agreement

Yes

available

R3‑247154

UHI enhancements for SCG (de)activation

Qualcomm Incorporated

discussion

Discussion

Yes

available

R3‑247161

(TP for BLCR for SON for 38.413, 36.423) Rel-18 SON and MDT leftovers

Huawei

other

Agreement

Yes

available

R3‑247311

(TP for SON BLCR TS38.423 and TS36.423) Rel-18 SON and MDT leftovers

Samsung

other

Agreement

Yes

available

R3‑247322

MHI/UHI Enhancement for SCG Deactivation/Activation

Nokia

discussion

Yes

available

R3‑247427

Discussion on MRO for R18 leftovers

Lenovo

discussion

Yes

available

R3‑247499

Further discussion on RACH optimization for SDT

Ericsson, CATT, ZTE Corporation

discussion

Yes

available

R3‑247500

(TP for BL CR to 38.413 for SON) UHI for SCG activation and deactivation

Ericsson

other

Agreement

Yes

available

R3‑247546

(TPs to BL CR for 38.300, 38.413) Further discussion on Rel-18 leftovers

ZTE Corporation

other

Agreement

Yes

available

R3‑247694

Discussion on RACH optimization for SDT

China Telecom

discussion

Discussion

Yes

available

R3‑247715

(TP for 37.340, 38.423, 36.423 and 38.413) SON enhancement for R18 leftover

CATT

other

Agreement

Yes

available

AI/ML for NG-RAN WI (RAN3-led)

11.1

General

R3‑247028

(BLCR to 38.423) Support of enhancements on AI/ML for NG-RAN

ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio, Rakuten

Endorsement

Yes

endorsed

R3‑245850

R3‑247741

Work plan for Rel-19 Enhancements for AI/ML for NG-RAN

ZTE Corporation, NEC

Work Plan

Yes

noted

11.2

AI/ML enabled Slicing

R3‑247203

(TP to BLCR TS38.423) AI/ML-based Slicing

NEC

other

Agreement

Yes

noted

R3‑247615

AI/ML Slicing Discussion

Nokia

discussion

Discussion

Yes

noted

R3‑247138

Discussion on AI/ML assisted Network Slicing

ZTE Corporation

discussion

Discussion

Yes

noted

R3‑247139

[TP to 38.423] AI/ML assisted Network Slicing

ZTE Corporation, Qualcomm, China Unicom

other

Agreement

Yes

available

R3‑247201

(TP for BLCR for TS38.300) Support of enhancements on AI/ML for NG-RAN

NEC, ZTE, Qualcomm, Samsung, CMCC

other

Agreement

Yes

available

R3‑247202

(TP for BLCR for TS38.401) Support of enhancements on AI/ML for NG-RAN

NEC

other

Agreement

Yes

available

R3‑247297

Discussion on AI/ML enabled slicing

Samsung

discussion

Approval

Yes

available

R3‑247323

UE Performance Data for AI/ML based Network Slicing

Rakuten Mobile, Inc

discussion

Discussion

Yes

available

R3‑247325

Discussion on NG-RAN AI/ML for Network Slicing

Qualcomm Incorporated

discussion

Agreement

Yes

available

R3‑247414

(TP for AI/ML BLCR to TS 38.423) Discussion on the AI/ML-based Network Slicing

Huawei

other

Agreement

Yes

available

R3‑247442

(TP to BLCR 38.423) Discussion on AIML based network slicing

Lenovo

other

Agreement

Yes

available

R3‑247453

(TP to TR 38.743) AI/ML assisted Network Slicing

Tejas Network Limited

other

Agreement

Yes

available

R3‑247467

(TP on 38.423)Support of AI/ML enabled Slicing

CATT

other

Agreement

Yes

available

R3‑247469

Enhancement of UE performance metrics

CATT, Jio, Qualcomm, CBN

discussion

Decision

Yes

available

R3‑247533

Support for AI/ML enabled Network Slicing

Ericsson, InterDigital

discussion

Approval

Yes

available

R3‑247534

(TP to TS38.423) AIML enabled Network Slicing

Ericsson, InterDigital

other

Agreement

Yes

available

R3‑247596

Discussion on AIML based Network Slicing

Jio

discussion

Discussion

Yes

available

R3‑247604

Discussion for AI/ML based Network Slicing

Rakuten Mobile, Inc

discussion

Discussion

Yes

available

R3‑247616

(TP to BLCR to TS 38.423) AI/ML Slicing

Nokia

other

Agreement

Yes

available

R3‑247677

Discussion on AI-based network slice

CMCC

discussion

Discussion

Yes

available

R3‑247678

(TP for 38.423) AIML based slice

CMCC

other

Approval

Yes

available

R3‑247785

CB:#AIRAN1_Slicing

Lenovo

discussion

reserved

R3‑247823

(TP to BLCR 38.423) AIML based network slicing

Lenovo

other

Agreement

reserved

11.3

AI/ML enabled Coverage and Capacity Optimization

R3‑247326

Discussion on AI/ML enabled CCO

Qualcomm Incorporated

discussion

Agreement

Yes

noted

R3‑247521

AI/ML support for CCO

Ericsson, InterDigital, Deutsche Telekom

discussion

Approval

Yes

noted

R3‑247564

Discussion on signalling for AI/ML-based CCO

Nokia, Jio

discussion

Discussion

Yes

available

R3‑247651

Discussion on AI/ML assisted Coverage and Capacity Optimization

ZTE Corporation

discussion

Approval

Yes

available

R3‑247204

(TP to BLCR TS38.423) AI/ML-based CCO

NEC

other

Agreement

Yes

available

R3‑247233

Discussions on enhancements for AIML support for CCO

Jio

discussion

Discussion

Yes

available

R3‑247236

Further Enhancements on AIML support for CCO

Jio

discussion

Discussion

Yes

available

R3‑247238

Discussion on Timing Aspects for AIML support in CCO

Jio

discussion

Discussion

Yes

available

R3‑247298

(TP to BL CR TS38.423) AI/ML enabled CCO

Samsung

other

Agreement

Yes

available

R3‑247374

Discussion on AI/ML based Coverage and Capacity Optimization

China Telecom

discussion

Decision

Yes

available

R3‑247375

(TP to TS38.423) Support of AI/ML based Coverage and Capacity Optimization

China Telecom

other

Agreement

Yes

available

R3‑247415

Timing information and feedback for AI/ML-based Coverage and Capacity Optimization

Huawei

discussion

Agreement

Yes

available

R3‑247416

(TPs for AI/ML BLCR to TS 38.423 and AI/ML BLCR to TS 38.473) Signalling details for AI/ML-based Coverage and Capacity Optimization

Huawei

other

Agreement

Yes

available

R3‑247448

(TP to BLCR 38.473) Discussion on AIML based CCO

Lenovo

other

Agreement

Yes

available

R3‑247468

(TP on 38.423/38.473) Open issues on the CCO use case

CATT

other

Agreement

Yes

available

R3‑247522

(TP to 38.473) - AI/ML support for CCO

Ericsson, InterDigital, Deutsche Telekom

other

Agreement

Yes

available

R3‑247523

(TP to 38.423) - AI/ML support for CCO

Ericsson, InterDigital, Deutsche Telekom

other

Agreement

Yes

available

R3‑247563

A contribution to energy efficient AI/ML-based CCO issue prediction in split architecture

Nokia, Jio, Telecom Italia

discussion

Yes

available

R3‑247652

[TP to 38.401] Support of AI/ML assisted CCO

ZTE Corporation, Lenovo, China Unicom

other

Agreement

Yes

available

R3‑247653

[TP to 38.423 and 38.473] Support of AI/ML assisted Coverage and Capacity Optimization

ZTE Corporation

other

Agreement

Yes

available

R3‑247679

Discussion on AI/ML-based CCO

CMCC

discussion

Discussion

Yes

available

R3‑247695

Discussion on Xn and F1 impacts for AI/ML-based CCO

LG Electronics Inc.

discussion

Yes

available

R3‑247696

(TP for NR_AIML_NGRAN_enh-Core for TS 38.423) Discussion on Xn and F1 impacts for AI/ML-based CCO

LG Electronics Inc.

other

Agreement

Yes

available

R3‑247697

(TP for NR_AIML_NGRAN_enh-Core for TS 38.473) Discussion on Xn and F1 impacts for AI/ML-based CCO

LG Electronics Inc.

other

Agreement

Yes

available

R3‑247749

Discussion of AI/ML based CCO

Rakuten Mobile, Inc

discussion

Discussion

Yes

available

R3‑247750

Data Collection Aspects for AIML support in CCO

Jio

discussion

Discussion

Yes

available

R3‑247787

CB:#AIRAN2_CCO

Qualcomm

discussion

reserved

11.4

R18 leftovers

R3‑247141

(TP to 38.423) Discussion on Mobility Optimization for NR-DC

ZTE Corporation

other

Agreement

Yes

revised

R3‑247827

(TP to 38.423) Discussion on Mobility Optimization for NR-DC

ZTE Corporation

other

Agreement

reserved

R3‑247141

R3‑247140

(TP to 38.423) Addition of predicted PSCell ID within DC procedure

ZTE Corporation, CATT, Samsung

other

Agreement

Yes

noted

R3‑247535

AI/ML support for NR-DC

Ericsson

discussion

Approval

Yes

available

R3‑247417

(TP for AI/ML BLCR to TS 38.423) AI/ML-based Mobility Optimization in NR-DC

Huawei

other

Agreement

Yes

available

R3‑247206

(TP to BLCR TS38.423) NR-DC mobility optimization

NEC

other

Agreement

Yes

available

R3‑247299

Discussion on AI/ML for mobility in NR-DC

Samsung

discussion

Approval

Yes

available

R3‑247370

Discussion on AI/ML based Mobility Optimization for NR-DC

China Telecom

discussion

Discussion

Yes

available

R3‑247371

(TP to TS38.423) Support of AIML based Mobility Optimization for NR-DC

China Telecom

other

Agreement

Yes

available

R3‑247443

(TP to BLCR 38.423) Discussion on UE performance feedback in AIML for NR-DC

Lenovo

other

Agreement

Yes

available

R3‑247445

TP to BLCR 37.340 AIML for NR-DC

Lenovo, CATT, ZTE Corporation, Samsung

other

Agreement

Yes

available

R3‑247470

AI/ML in DC scenario

CATT

discussion

Decision

Yes

available

R3‑247471

(TP for TS 38.423) Introducing essentially per-DRB UE performance result for DC

CATT

other

Agreement

Yes

available

R3‑247536

(TP to TS38.423) - AI/ML support for NR-DC

Ericsson

other

Agreement

Yes

available

R3‑247620

Procedures for AI/ML Mobility Optimization in NR-DC

Nokia

discussion

Yes

available

R3‑247621

(TP to BLCR to TS 38.423) AI/ML Mobility for NR-DC

Nokia

other

Agreement

Yes

available

R3‑247667

(TP to 38.423) Discussion on AIML based Mobility Optimization for NR-DC

CMCC

other

Agreement

Yes

available

R3‑247788

CB:#AIRAN3_NRDC

ZTE

discussion

reserved

R3‑247671

Discussion on AIML for split architecure use casesv1

CMCC, ZTE, CATT

discussion

Discussion

Yes

noted

R3‑247672

Discussion on transferring Energy Cost for split architecure

CMCC, Samsung

discussion

Discussion

Yes

available

R3‑247524

Split architecture support for Release 18 use cases

Ericsson, AT&T, Verizon

discussion

Approval

Yes

available

R3‑247142

(TP to 38.473, 37.483) Discussion on split architecture

ZTE Corporation

other

Agreement

Yes

available

R3‑247207

(TP to BLCR TS38.473) Split architecture support

NEC

other

Agreement

Yes

available

R3‑247300

Discussion on AI/ML for NG-RAN in split architecture

Samsung

discussion

Approval

Yes

available

R3‑247301

(CR to 37.483) AI/ML for NG-RAN on split architecture

Samsung

Agreement

Yes

available

R3‑247376

(TP to TS38.470) Support of AI/ML for NG-RAN split architecutre

China Telecom

other

Agreement

Yes

available

R3‑247418

(TP for AI/ML BLCR to TS 38.473) Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases

Huawei

other

Agreement

Yes

available

R3‑247444

(TP to BLCR 38.473 and 37.483) Discussion on split architecture related issues for Rel18 use cases

Lenovo

other

Agreement

Yes

available

R3‑247446

TP to BLCR 38.401 AIML for RAN in split architecture

Lenovo, CATT, ZTE Corporation

other

Agreement

Yes

available

R3‑247472

(TP on 38.470/37.480) AI/ML in split gNBs

CATT

other

Agreement

Yes

available

R3‑247525

(TP to 37.483) - Split architecture support for Release 18 use cases

Ericsson, AT&T, Verizon

other

Agreement

Yes

available

R3‑247526

(TP to 38.473) - Split architecture support for Release 18 use cases

Ericsson, AT&T, Verizon

other

Agreement

Yes

available

R3‑247527

(TP to 38.423) - Split architecture support for Release 18 use cases

Ericsson, AT&T, Verizon

other

Agreement

Yes

available

R3‑247603

Discussion on AIML for split architecture

NTT DOCOMO INC..

discussion

Yes

available

R3‑247617

Discussion on Energy Cost Reporting in Split Architecture

Nokia, Telecom Italia, Jio, Deutsche Telekom

discussion

Yes

available

R3‑247618

Procedures over F1 for the exchange of Energy Cost index

Nokia, Telecom Italia, Jio, Deutsche Telekom

Yes

available

R3‑247619

[Draft] LS on New Energy Consumption Measurement for gNB-DU

Nokia, Telecom Italia, Jio, Deutsche Telekom

LS out

Agreement

Yes

available

R3‑247622

Discussion on Rel-18 UE Performance measurements

Nokia

discussion

Yes

available

R3‑247673

(TP to 38.401) OAM requirement for Energy Saving for split architecure

CMCC, Samsung

other

Agreement

Yes

available

R3‑247789

CB:#AIRAN4_SplitArch

CMCC

discussion

reserved

R3‑247144

Discussion on requirements for Continuous MDT solution

Telecom Italia, Jio, BT, Deutsche Telekom

discussion

Decision

Yes

noted

R3‑247537

Additional discussions on Continuous MDT

Ericsson, InterDigital, Jio

discussion

Approval

Yes

available

R3‑247327

Discussion on Continuous MDT

Qualcomm Incorporated, Nokia, Nokia Shanghai Bell

discussion

Agreement

Yes

available

R3‑247143

Discussion on continuous MDT collection

ZTE Corporation

discussion

Yes

available

R3‑247205

Continuous MDT collection for AI/ML

NEC

discussion

Decision

Yes

available

R3‑247302

Discussion on continuous MDT collection targeting the same UE across RRC states

Samsung

discussion

Approval

Yes

available

R3‑247377

Discussion on Continuous MDT measurement

China Telecom

discussion

Decision

Yes

available

R3‑247393

Discussion on measurement correlation for continuous MDT

CATT

discussion

Decision

Yes

available

R3‑247419

On Continuous MDT for AI/ML

Huawei

other

Agreement

Yes

available

R3‑247538

(TP to TS38.423) Continuous MDT collection targeting the same UE across RRC states

Ericsson, InterDigital, Jio

other

Agreement

Yes

available

R3‑247539

LS on correlation identifiers for Continuous MDT

Ericsson, InterDigital, Jio

LS out

Agreement

Yes

available

R3‑247623

Continuous Management-based MDT

Nokia, Qualcomm, Jio, Deutsche Telekom

discussion

Yes

available

R3‑247790

CB:#AIRAN5_ContinuousMDT

Ericsson

discussion

reserved

Additional topological enhancements for NR WI (RAN3-led)

12.1

General

R3‑247029

Support for Wireless Access Backhaul

Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm

Endorsement

Yes

endorsed

R3‑245840

R3‑247030

(BL CR to 38.300) Introduction of NR Femto Architecture and Protocol Aspects

Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells

draftCR

Endorsement

Yes

revised

R3‑247825

R3‑245864

R3‑247825

(BL CR to 38.300) Introduction of NR Femto Architecture and Protocol Aspects

Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells

draftCR

Endorsement

endorsed

R3‑247030

12.2

Wireless Access Backhaul (WAB)

R3‑247109

(TP for WAB BL CR for TS 38.401): Functional Aspects of WAB-Nodes

Ericsson

other

Agreement

Yes

available

R3‑247343

(TP for TS 38.423) Discussion on WAB mobility

Nokia, Nokia Shanghai Bell

other

Agreement

Yes

available

R3‑247363

(TPs for TS 38.413) Architecture and Access control for WAB

Huawei

other

Agreement

Yes

available

R3‑247195

(TP to 38.401 36.300) Discussion on supporting WAB

ZTE Corporation

other

Agreement

Yes

available

R3‑247196

Discussion on other aspects for WAB and the reply LS to SA2

ZTE Corporation

other

Yes

available

R3‑247197

(TP to 38.305) Support of location service involving WAB-nodes

ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT

other

Agreement

Yes

available

R3‑247198

(TP to 38.455) Support of location service involving WAB-nodes

ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT

other

Agreement

Yes

available

R3‑247222

(TP to BL CR of 38.423 on WAB) Discussion on mobility and reliability for WAB

NEC

other

Agreement

Yes

available

R3‑247226

Discussion on enhancements for WAB

CANON Research Centre France

discussion

Discussion

Yes

available

R3‑247227

(draft Reply LS to SA2 – TP to BL CR 38.401) Discussion on SA2 questions on multi-hop WAB and UE ULI

Qualcomm Inc.

other

Agreement

Yes

available

R3‑247228

(TP to BL CR 38.401) Discussion of aspects related to WAB

Qualcomm Inc.

other

Agreement

Yes

available

R3‑247229

BL draft CR to TS 38.300 on Support of WAB

Qualcomm, Ericsson, CATT, ZTE, Nokia, Nokia Shanghai Bell

draftCR

Endorsement

Yes

available

R3‑247268

(draft Reply LSs to SA2) On support of WAB

CATT

discussion

Decision

Yes

available

R3‑247269

Discussion on enhancements for WAB

CATT

discussion

Decision

Yes

available

R3‑247279

Discussion on Wireless Access Backhaul

NTT DOCOMO INC.

discussion

Yes

available

R3‑247342

(TP for TS 38.401) Discussion on NG management and Xn management for WAB

Nokia, Nokia Shanghai Bell

other

Agreement

Yes

available

R3‑247110

Reply to SA2 Regarding UE Access Control and Additional ULI for WAB-Nodes

Ericsson

discussion

Agreement

Yes

revised

R3‑247771

Reply to SA2 Regarding UE Access Control and Additional ULI for WAB-Nodes

Ericsson

discussion

Agreement

Yes

available

R3‑247110

R3‑247353

(TP to BLCR for TS 38.410) Discussion on WAB mobility

Samsung

discussion

Agreement

Yes

available

R3‑247354

Discussion on other aspects for the support of WAB

Samsung

discussion

Agreement

Yes

available

R3‑247364

(TP for TS 38.401) Discussion on WAB related procedures

Huawei

other

Agreement

Yes

available

R3‑247428

Architecture and configuration for WAB-node

Lenovo

discussion

Yes

available

R3‑247429

Discussion on WAB node migration

Lenovo

discussion

Yes

available

R3‑247627

Discussion on RAN2 Impact and Functional Aspects of WAB

China Telecom

discussion

Discussion

Yes

available

R3‑247628

Discussion on Multi-hop Prevention and Authorization for WAB

China Telecom

discussion

Discussion

Yes

available

R3‑247722

Further consideration on support of WAB

LG Electronics

discussion

Yes

available

R3‑247723

(TP to TS 38.401 and 38.423) TP for WAB support

LG Electronics

other

Agreement

Yes

available

R3‑247793

Summary of Offline Discussion on additional topological enhancement

NTTDOCOMO, INC.

discussion

Yes

available

R3‑247826

Reply LS to R3-244019

RAN3(Samsung)

LS out

Agreement

reserved

R3‑247828

CB: WAB

DoCoMo

discussion

reserved

12.3

5G Femto

R3‑247018

Reply LS on Clarification regarding definition of 5G NR femto ownership

SA2(LGE)

LS in

Discussion

Yes

available

R3‑247280

Discussion on 5G femto

NTT DOCOMO INC.

discussion

Yes

available

R3‑247208

Open issues for NR Femto

NEC

discussion

Decision

Yes

available

R3‑247270

Discussion on stage-2 NR Femto

CATT

discussion

Decision

Yes

available

R3‑247355

(TP to TS 38.300) Discussion on NR Femto architecture and functional split

Samsung

other

Agreement

Yes

available

R3‑247365

(TP for TS 38.300/38.413) Architecture and functional split for NR Femto

Huawei

other

Agreement

Yes

available

R3‑247388

On NR Femto Architecture and functional split

China Telecom

discussion

Decision

Yes

available

R3‑247430

Architecture and access control for NR Femto

Lenovo

discussion

Yes

available

R3‑247431

TP to 38.300 for NR Femto

Lenovo

other

Agreement

Yes

available

R3‑247724

(TP for TS 38.300) Functional split and Access control on 5G Femto

LG Electronics

other

Agreement

Yes

available

R3‑247731

TP for 38.300&38.410 NR Femto

ZTE corporation

other

Agreement

Yes

available

R3‑247648

Discussion on NR Femto Architecture and Functionality

Baicells

discussion

Decision

Yes

available

R3‑247649

TP to BL CR for TS 38.300 on NR Femto

Baicells

other

Agreement

Yes

available

R3‑247452

NR Femto - Further Stage 2 Aspects

Ericsson LM

discussion

Discussion

Yes

available

R3‑247454

NR Femto - Stage 2 TP

Ericsson

other

Agreement

Yes

revised

R3‑247809

R3‑245487

R3‑247809

Access Control with NR Femto – Stage 2 TP

Ericsson

other

Agreement

reserved

R3‑247454

R3‑247482

Completion of Functional aspects of NR Femto Architecture

Nokia

discussion

Yes

available

R3‑247486

[TP for BL CR NR Femto 38.300] Introduction of Functional aspects of NR Femto architecture

Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, ZTE

other

Agreement

Yes

revised

R3‑247791

[TP for BL CR NR Femto 38.300] Introduction of Functional aspects of NR Femto architecture

Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, ZTE

other

Agreement

reserved

R3‑247486

R3‑247488

LS on Security verifications related to NR Femtos

Nokia

LS out

Agreement

Yes

available

R3‑247356

(TP to TS 38.300) Discussion on access control for NR Femto

Samsung

other

Agreement

Yes

available

R3‑247730

TP for access control for NR Femto

ZTE corporation, Nokia

discussion

Decision

Yes

available

R3‑247366

(TP for TS 38.300) Access control for NR Femto

Huawei

other

Agreement

Yes

available

R3‑247271

Impact to NGAP for NR Femto

CATT

discussion

Decision

Yes

available

R3‑247487

Introduction of NR Femto architecture with optional NR Femto GW

Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, ZTE

Yes

available

R3‑247796

(TP to 38.410) AMF selection for NR Femto

ZTE

other

Agreement

reserved

R3‑247799

(TP for TS 38.300) Architecture and Protocol stack for NR Femto

Huawei

other

Agreement

reserved

R3‑247800

(TP for TS 38.413) Functional split for NR Femto

Huawei, Nokia

other

Agreement

reserved

R3‑247804

(TP to 38.300) Architecture

ZTE

other

Agreement

reserved

R3‑247819

LS on NR Femto

RAN3(ZTE)

LS out

discussion

reserved

NR Mobility Enhancements WI

13.1

General

R3‑247031

(BL CR to 38.300) Support for Inter-CU LTM

Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung

draftCR

Endorsement

Yes

endorsed

R3‑245859

R3‑247032

(BL CR to 38.423) Xn support for inter-CU LTM

Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics

Endorsement

Yes

revised

R3‑247820

R3‑245860

R3‑247820

(BL CR to 38.423) Xn support for inter-CU LTM

Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics

Endorsement

endorsed

R3‑247032

13.2

Support for inter-CU LTM

R3‑247006

LS on the support of semi-persistent CSI-RS resource for LTM candidate cells

RAN1(Fujitsu)

LS in

Discussion

Yes

noted

R3‑247389

(draft reply LS) Discussion on support of semi-persistent CSI-RS resource

CATT

discussion

Decision

Yes

noted

R3‑247822

Reply LS for LS on the support of semi-persistent CSI-RS resource for LTM candidate cells

RAN3(CATT)

LS out

Agreement

reserved

R3‑247111

LS on RAN2 agreements for inter-CU LTM

RAN2(ZTE)

LS in

Discussion

Yes

noted

R3‑247762

Response to R3-247111 and R3-247112

LG Electronics Inc, ZTE, Fujitsu, KDDI, KT Corp., ITRI, Rakuten, ETRI, SK Telecom, LG Uplus

response

Decision

Yes

noted

R3‑247757

Reply LS on security handling for inter-CU LTM in non-DC cases

SA3(Samsung)

LS in

Discussion

Yes

available

R3‑247758

Reply LS on security key update of inter-CU SCG LTM

SA3(Xiaomi)

LS in

Discussion

Yes

available

R3‑247709

Initial considerations on Inter-CU LTM

Rakuten Mobile, Inc

discussion

Agreement

Yes

available

R3‑247747

Inter-gNB/CU LTM typical deployment scenarios and operational requirements

Jio, NTT DOCOMO, Qualcomm Incorporated, Vodafone, Sony, Bharti Airtel, Telstra

discussion

Yes

available

R3‑247234

Impact analysis of coupling LTM cell switch and CU anchor changes on subsequent inter-gNB LTM

Qualcomm Incorporated, Reliance JIO, Vodafone, NTT DoCoMo, Sony, Bharti Airtel

discussion

Decision

Yes

noted

R3‑247483

Comprehensive analysis of inter-CU LTM

Ericsson

discussion

Yes

available

R3‑247350

Discussion on inter-gNB-CU LTM

Samsung

discussion

Approval

Yes

available

R3‑247112

Support of Multiple Reference Configurations

Nokia. KDDI, LG Electronics, ZTE, Rakuten, Fujitsu

discussion

Agreement

Yes

available

R3‑247126

(TP to BL CR to 38.300 and 38.423) Support for reference configurations in the inter-CU MCG LTM

Google

other

Agreement

Yes

available

R3‑247260

Further analysis on the PDCP anchor based solution

Huawei, Ericsson, CATT, China Telecom, CMCC,Samsung

discussion

Yes

noted

R3‑247755

Response to R3-247260

Qualcomm Incorporated

response

Decision

Yes

noted

R3‑247235

Signalling enhancements for inter-CU LTM HO

Qualcomm Incorporated, Reliance JIO, Vodafone, NTT DoCoMo, Sony, Bharti Airtel

discussion

Decision

Yes

available

R3‑247661

Comparison of RRC/PDCP anchor and anchor switch-based solutions for inter-gNB LTM

Qualcomm Incorporated, Reliance JIO, Vodafone, NTT DOCOMO, Sony, Bharti Airtel

discussion

Decision

Yes

available

R3‑247368

Discussion on support of inter-CU LTM in NR-DC scenario

China Telecom

discussion

Decision

Yes

available

R3‑247102

Discussion on Inter-gNB-CU LTM Procedure

Nokia

discussion

Yes

available

R3‑247367

Discussion on signaling enhancement for inter-CU LTM

China Telecom

discussion

Decision

Yes

available

R3‑247630

[Draft] Reply LS on the support of semi-persistent CSI-RS resource for LTM candidate cells

NTT DOCOMO INC..

LS out

Agreement

Yes

available

R3‑247485

Network coordination for transmission of semi-persistent CSI-RS

Ericsson

discussion

Yes

available

R3‑247108

Discussion on semi-persistent CSI-RS resource for LTM

Nokia

discussion

Yes

available

R3‑247263

[DRAFT] Reply LS on the support of semi-persistent CSI-RS resource for LTM candidate cells

Huawei

LS out

Agreement

Yes

available

R3‑247182

TP for SN initiated inter-SN LTM

ZTE Corporation

other

Yes

available

R3‑247212

Rel-19 inter-CU LTM in DC scenario

NEC

discussion

Decision

Yes

available

R3‑247183

Discussion on inter-CU LTM

ZTE Corporation

discussion

Yes

available

R3‑247211

discussion of Rel-19 inter-CU LTM issues

NEC

discussion

Decision

Yes

available

R3‑247434

General aspects of inter-CU SCG LTM

Lenovo

discussion

Yes

available

R3‑247591

Keep continuing discussions on Inter-CU LTM signaling design

LG Electronics Inc.

discussion

Decision

Yes

available

R3‑247680

Discussion on inter-CU LTM

CMCC

discussion

Discussion

Yes

available

R3‑247629

Discussion on inter-CU LTM non-DC case

NTT DOCOMO INC..

discussion

Yes

available

R3‑247390

Discussion for Inter-CU LTM

CATT

discussion

Decision

Yes

available

R3‑247710

Data forwarding and transmission in Inter-CU LTM

Rakuten Mobile, Inc

discussion

Agreement

Yes

available

R3‑247351

Additional discussion on Inter-gNB-CU LTM

Samsung

discussion

Approval

Yes

available

R3‑247103

Discussion on Inter-CU LTM Dual Connectivity

Nokia

discussion

Yes

available

R3‑247751

Discussion on inter-CU LTM DC case

NTT DOCOMO INC..

discussion

Yes

available

R3‑247391

Discussion for Inter-CU LTM in DC

CATT

discussion

Decision

Yes

available

R3‑247590

Baseline CR for introducing Rel-19 Mobility enhancement in E1AP

LG Electronics Inc., Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, NEC

Approval

Yes

available

R3‑245569

R3‑247484

(TPs to BL CRs for TS 38.300 and 38.423) – Support for inter-CU LTM

Ericsson

other

Agreement

Yes

available

R3‑247432

[TP to BLCR for TS 38.300] Inter-CU LTM

Lenovo

other

Agreement

Yes

available

R3‑247262

(TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure

Huawei

other

Agreement

Yes

available

R3‑247369

(TP for TS38.300) On support of inter-CU LTM

China Telecom

other

Agreement

Yes

available

R3‑247352

(TP to BLCR for TS 38.401) Procedure on Inter-gNB-CU LTM

Samsung

other

Agreement

Yes

available

R3‑247181

(BL CR to 38.420) Support for Inter-CU LTM

ZTE Corporation

Endorsement

Yes

available

R3‑247433

[TP to BLCR for TS 38.423] Inter-CU LTM

Lenovo

other

Agreement

Yes

available

R3‑247592

(TP for NR_Mob_Ph4 TS 38.423 BL CR)

LG Electronics Inc.

other

Agreement

Yes

available

R3‑247213

(TP to 38.423 on inter-CU LTM) inter-CU LTM related information

NEC

other

Agreement

Yes

available

R3‑247261

(TP for LTM BLCR for TS38.473): Further discussion on inter-CU LTM procedure

Huawei

other

Agreement

Yes

available

R3‑247104

TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures

Nokia

other

Agreement

withdrawn

Yes

R3‑247232

Comparison of RRC/PDCP anchor and anchor switch-based solutions for inter-gNB LTM

Qualcomm Incorporated, Reliance JIO, Vodafone, NTT DoCoMo, Sony

discussion

Decision

Yes

withdrawn

Yes

R3‑247239

Inter-gNB/CU LTM typical deployment scenarios and operational requirements

Jio, Qualcomm, Sony, Bharti Airtel, NTT Docomo, Telstra

discussion

Discussion

Yes

withdrawn

Yes

R3‑247824

CB:#25_MobilityEnh

China Telecom

discussion

reserved

13.3

Support for Conditional LTM

NR NTN Enhancements WI

14.1

General

R3‑247033

(BL CR to 38.300) Support for Regenerative Payload and MBS broadcast 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, ETRI

draftCR

Endorsement

Yes

available

R3‑245861

R3‑247034

(BL CR to 38.410) Introduce NG Removal procedure

CMCC, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Qualcomm, Xiaomi, LG Electronics, China Telecom, Samsung, ZTE, NEC, ETRI

Endorsement

Yes

available

R3‑245862

R3‑247035

Support for Regenerative Payload and MBS broadcast in NR NTN

CATT, Thales, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Qualcomm, Samsung, Xiaomi, CMCC, China Telecom, Jio, LG Electronics, NEC, ETRI, SES, ESA

Endorsement

Yes

available

R3‑245863

14.2

Support MBS broadcast service

R3‑247282

Support of MBS broadcast service for NR NTN

CATT

discussion

Decision

Yes

available

R3‑247214

(TP for TS 38.300 and TS 38.413) Discussion on NR NTN supporting MBS broadcast service

NEC

other

Agreement

Yes

available

R3‑247344

(TP to BL CR for TS 38.300 and TS 38.413) Discussion on the support of MBS Broadcast Service

Nokia, Nokia Shanghai Bell

other

Agreement

Yes

available

R3‑247379

Support of MBS broadcast service for NTN

China Telecom

other

Decision

Yes

available

R3‑247399

(TP for TS 38.300 and TS 38.413) Support MBS broadcast service

Huawei

other

Agreement

Yes

available

R3‑247435

Broadcast service continuity in NTN

Lenovo

discussion

Discussion

Yes

available

R3‑247607

Further discussion on support broadcast service for NR NTN

Samsung

discussion

Agreement

Yes

available

R3‑247654

(TP for TS 38.300) Discussion on NTN broadcast service supporting

ZTE Corporation

other

Approval

Yes

available

R3‑247674

(TP to 38.300) Discussion on Supporting MBS broadcast service for NR NTN

CMCC

other

Discussion

Yes

available

R3‑247641

Further Discussion on Support of MBS Broadcast Service

TCL

discussion

Discussion

Yes

available

R3‑247383

Support of MBS broadcast service for NTN

China Telecom

other

Decision

withdrawn

Yes

14.3

Support of Regenerative payload

R3‑247016

Reply LS on Support of Regenerative-based Satellite Access

SA2(Qualcomm)

LS in

Discussion

Yes

available

R3‑247330

Draft Reply for LS on Support of Regenerative-based Satellite Access

Qualcomm Incorporated

LS out

Agreement

Yes

available

R3‑247283

(TP to BL CR for 38.413) Support of regenerative payload

CATT

other

Agreement

Yes

available

R3‑247316

Support of Inactive UE mobility NTN

Xiaomi, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, China Telecom, Lenovo

discussion

Agreement

Yes

available

R3‑247215

(TP for TS 38.300) Discussion on regenerative payload enhancement for NR NTN

NEC

other

Agreement

Yes

available

R3‑247345

(TP for TS 38.300) Discussion on the support of Regenerative payload

Nokia, Nokia Shanghai Bell

other

Agreement

Yes

available

R3‑247317

(TP for TS 38.300) Support of regenerative payload

Xiaomi

other

Approval

Yes

available

R3‑247328

(TP for TS 38.300) NR NTN Regenerative Payload Architecture

Qualcomm Incorporated, Xiaomi, LGE, NTT Docomo

other

Agreement

Yes

available

R3‑247329

(TP for TS 38.300) Discussion on RAN Signaling impacts for NR NTN Regenerative Payload

Qualcomm Incorporated

other

Agreement

Yes

available

R3‑247380

Discussion on regenerative payload enhancement

China Telecom

other

Decision

Yes

available

R3‑247400

(TP for TS 38.300) Support of regenerative payload

Huawei

other

Agreement

Yes

available

R3‑247436

Interface management for regenerative payload in NTN

Lenovo

discussion

Discussion

Yes

available

R3‑247461

Considerations on NG Interface Management over the Feeder Link

Ericsson, Thales

discussion

Discussion

Yes

available

R3‑247462

Making the Case for Location-Based CHO in Rel-19

Ericsson, Thales, ESA, Inmarsat, Viasat

discussion

Discussion

Yes

available

R3‑247463

Location-Based CHO in Rel-19 - XnAP Aspects

Ericsson, Thales, ESA, Inmarsat, Viasat

other

Agreement

Yes

available

R3‑247547

Further discussion on support of regenerative payload

ZTE Corporation

other

Agreement

Yes

available

R3‑247593

Discussions on NG management from satellite gNB and Inactive support

LG Electronics Inc.

discussion

Decision

Yes

available

R3‑247594

(TP for NR_NTN_Ph3 TS 38.300 BL CR)

LG Electronics Inc.

other

Agreement

Yes

available

R3‑247600

Discussion on NG interface management through ISL

ETRI

discussion

Discussion

Yes

available

R3‑247608

Further discussion on support of regenerative payload for NR NTN

Samsung

discussion

Agreement

Yes

available

R3‑247675

Discussion on support of regenerative payload for NR NTN

CMCC

discussion

Discussion

Yes

available

R3‑247398

(TP for BLCR for TS 38.300) Correction on stage 2

Huawei, Nokia, Nokia Shanghai Bell, Thales, CATT

other

Agreement

Yes

available

R3‑247642

Discussion on Support of NTN Regenerative Architecture

TCL

discussion

Yes

available

R3‑247384

Discussion on regenerative payload enhancement

China Telecom

other

Decision

withdrawn

Yes

IoT NTN Enhancements WI

15.1

General

R3‑247548

Updated Work Plan for IoT NTN

ZTE Corporation, CATT, MediaTek.Inc

Work Plan

Information

Yes

available

15.2

Support Full eNB as Regenerative Payload

R3‑247008

LS on PWS support for NB-IoT NTN

RAN2(InterDigital)

LS in

Discussion

Yes

available

R3‑247549

Further discussion on support of store and forward satellite operation for IoT NTN

ZTE Corporation

other

Agreement

Yes

available

R3‑247392

Discussion for IoT NTN

CATT

discussion

Decision

Yes

available

R3‑247318

Support of Store and Forward in IoT NTN

Xiaomi

discussion

Agreement

Yes

available

R3‑247331

Discussion on Support for IoT NTN for Regenerative Payload

Qualcomm Incorporated

discussion

Agreement

Yes

available

R3‑247346

Discussion on the support of IoT NTN

Nokia, Nokia Shanghai Bell

discussion

Yes

available

R3‑247378

Support for IoT NTN with regenerative payload

China Telecom

discussion

Decision

Yes

available

R3‑247401

(TP for TS 36.300) Support of store and forward for IoT NTN

Huawei

other

Agreement

Yes

available

R3‑247455

How to Specify Store & Forward (S&F) Architecture in RAN3

Ericsson, Sateliot, Thales, ESA, Deutsche Telekom

discussion

Discussion

Yes

available

R3‑247456

Store & Forward (S&F) Architecture - Stage 2 Impacts

Ericsson, Sateliot, Thales, ESA, Deutsche Telekom

other

Agreement

Yes

available

R3‑247457

Store & Forward (S&F) Architecture - S1 Removal

Ericsson, Sateliot, Thales, ESA, Deutsche Telekom

other

Agreement

Yes

available

R3‑247458

Store & Forward (S&F) Architecture - S1AP Impacts

Ericsson, Sateliot, Thales, ESA, Deutsche Telekom

other

Agreement

Yes

available

R3‑247531

PWS Support for NB-IoT NTN

Ericsson LM

discussion

Discussion

Yes

available

R3‑247595

Further discussions on support of Store and Forward operations in NTN

THALES, Sateliot, Novamint

discussion

Discussion

Yes

available

R3‑247609

Discussion on support of regenerative payload for IoT NTN

Samsung

discussion

Agreement

Yes

available

R3‑247676

Discussion on support of IoT NTN

CMCC

discussion

Discussion

Yes

available

R3‑247382

Support for IoT NTN with regenerative payload

China Telecom

discussion

Decision

withdrawn

Yes

Ambient IoT SI

16.1

General

R3‑247036

(BL pCR to TR 38.769) Study on solutions for Ambient IoT in NR

Huawei, CMCC, Ericsson, ZTE, CATT, NEC, Xiaomi, Lenovo

pCR

Endorsement

Yes

endorsed

R3‑245849

R3‑247683

Work Plan for Ambient IoT SI

CMCC, Huawei, T-Mobile USA

Work Plan

Information

Yes

noted

R3‑247684

(TP to TR 38.769) RAN3 Conclusions and Recommendations

CMCC, T-Mobile USA, Huawei

other

Agreement

Yes

noted

R3‑247761

Response to R3-247684

Nokia

response

Yes

noted

R3‑247192

[DRAFT] LS on RAN3 outcome of Ambient IoT study

Huawei

LS out

Agreement

Yes

noted

R3‑247685

(TP to TR 38.769) Uncritical Editor's Note Removal

CMCC, Huawei, Samsung, CATT, Lenovo, Xiaomi, ZTE, NEC, China Telecom

other

Agreement

Yes

noted

16.2

RAN Architecture

R3‑247189

(TP to TR 38.769) A-IoT RAN Architecture aspects

Huawei

other

Agreement

Yes

noted

R3‑247190

(TP to TR 38.769) Protocol Stacks for Topology 2 NAS/UP based solutions

Huawei, CMCC, ZTE, CATT, NEC, Xiaomi, Lenovo, China Telecom, Samsung, Qualcomm

other

Agreement

Yes

noted

R3‑247585

Further aspects on AIoT Architecture

Ericsson

discussion

Agreement

Yes

noted

R3‑247586

[TP for TR 38.769] on AIoT Architecture aspects

Ericsson

other

Agreement

Yes

noted

R3‑247147

(TP to 38.769) Conclusion for Topology 1 and updates to terminologies

Qualcomm Incorporated

other

Agreement

Yes

available

R3‑247148

(TP to 38.769) Conclusion for Topology 2

Qualcomm Incorporated

other

Agreement

Yes

available

R3‑247184

(TP for TR38.769) some leftover issues on RAN architecture aspects

ZTE Corporation

other

Agreement

Yes

available

R3‑247216

(TP to TR38.769) Discussion on architecture of Ambient IoT

NEC

other

Agreement

Yes

available

R3‑247284

(TP to TR 38.769) A-IoT architecture aspects

CATT

other

Agreement

Yes

available

R3‑247312

Discussion on AIoT RAN architecture

Xiaomi

discussion

Agreement

Yes

available

R3‑247381

A-IoT architecture aspects

China Telecom

other

Decision

Yes

available

R3‑247437

Considerations on bistatic mode of operation

Lenovo

discussion

Yes

available

R3‑247438

(TP to TR 38.769) Protocol Stack of UP based Solution for Topology 2

Lenovo

other

Agreement

Yes

available

R3‑247610

Remaining issues on RAN architecture for Ambient IoT

Samsung

discussion

Agreement

Yes

available

R3‑247686

Discussion on RAN Architecture for Ambient IoT

CMCC

discussion

Discussion

Yes

available

R3‑247726

Discussion on RAN impact for Ambient IoT

LG Electronics

discussion

Yes

available

R3‑247385

A-IoT architecture aspects

China Telecom

other

Decision

withdrawn

Yes

R3‑247794

CB:#AIoT1_ProtocolStack

Huawei

discussion

reserved

16.3

RAN-CN Interface Impact

R3‑247185

(TP to TR 38.769) Signaling and Procedures for NAS/UP based Topology 2

ZTE Corporation, Huawei, Xiaomi, NEC, Nokia, China Telecom, CATT, CMCC

other

Agreement

Yes

revised

R3‑247786

(TP to TR 38.769) Signaling and Procedures for NAS/UP based Topology 2

ZTE Corporation, Huawei, Xiaomi, NEC, Nokia, China Telecom, CATT, CMCC

other

Agreement

Yes

available

R3‑247185

R3‑247314

(TP for TR 38.769) Procedures for A-IoT command

Xiaomi, Huawei, ZTE, CATT, CMCC

other

Agreement

Yes

noted

R3‑247587

[TP for TR 38.769] Elements for AIoT RAN – AIoT CN communication and overall signalling

Ericsson

other

Agreement

Yes

available

R3‑247149

(TP to 38.769) Inventory and Command related procedures for Ambient IoT

Qualcomm Incorporated

other

Agreement

Yes

available

R3‑247186

(TP to TR 38.769) Completion of Signaling and Procedures for Topology 2

ZTE Corporation

other

Agreement

Yes

available

R3‑247187

(TP for TR38.769) Inventory content for Ambient-IoT

ZTE Corporation

other

Agreement

Yes

available

R3‑247191

(TP to TR 38.769) A-IoT Signalling and Procedures for Topology 1

Huawei

other

Agreement

Yes

available

R3‑247217

(TP to TR38.769) Discussion on RAN-CN interface impact on Ambient IoT

NEC

other

Agreement

Yes

available

R3‑247285

(TP to TR 38 769) A-IoT Procedures and Information exchange between A-IoT CN and RAN

CATT

other

Agreement

Yes

available

R3‑247286

(TP to TR 38.879) A-IoT reader selection

CATT

other

Agreement

Yes

available

R3‑247313

AIoT interface impacts between RAN and CN

Xiaomi

discussion

Approval

Yes

available

R3‑247439

Radio resource allocation and UE reader selection for topology 2

Lenovo

discussion

Discussion

Yes

available

R3‑247489

[TP for TR 38.769] Information exchanged between AIoT RAN and AIoT CN

Nokia

other

Agreement

Yes

available

R3‑247490

[TP for TR 38.769] Reader Selection Principles in AIoT Topology 2

Nokia

other

Agreement

Yes

available

R3‑247611

Remaining issues on RAN-CN interface impact for Ambient IoT

Samsung

discussion

Agreement

Yes

available

R3‑247643

Discussion on Signalling Procedure Based on Topology 1

China Telecom

discussion

Discussion

Yes

available

R3‑247687

Discussion on coordination between CN and RAN

CMCC

discussion

Discussion

Yes

available

R3‑247491

[TP for TR 38.769] Data Transport and Context Management for AIoT

Nokia

other

Agreement

withdrawn

Yes

R3‑247795

CB:#AIoT2_SignallingFlow

Ericsson

discussion

reserved

16.4

Others

R3‑247688

Discussion on locating Ambient IoT device

CMCC

discussion

Discussion

Yes

noted

R3‑247689

(TP to TR 38.769) locating ambient IoT devices

CMCC, Huawei, ZTE, CATT, Xiaomi, Nokia, LG Electronics, China Telecom

other

Agreement

Yes

noted

R3‑247492

[TP for TR 38.769] Locating AIoT Devices

Nokia

other

Agreement

Yes

noted

R3‑247588

[TP for TR 38.769] On locating AIoT devices

Ericsson

other

Agreement

Yes

available

R3‑247150

(TP to 38.769) Locating Ambient IoT devices

Qualcomm Incorporated

discussion

Discussion

Yes

available

R3‑247188

(TP for TR38.769) Locating an AIoT device

ZTE Corporation

other

Agreement

Yes

available

R3‑247193

Consideration on A-IoT Device Locating

Huawei

discussion

Agreement

Yes

available

R3‑247287

(TP to TR 38.879) Locating of A-IoT device

CATT

other

Decision

Yes

available

R3‑247727

Further discussion on locating A-IoT Device

LG Electronics

discussion

Discussion

Yes

available

R3‑247315

(TP for TR 38.769)) Locating AIoT device

Xiaomi

other

Approval

withdrawn

Yes

R3‑247797

CB:AIoT3_LocationReport

Nokia

discussion

reserved

Network ES Enhancements WI

17.1

General

R3‑247558

WI Work plan for R19 Network Energy Savings

Ericsson

Work Plan

noted

Yes

noted

R3‑245483

17.2

Support on-demand SSB SCell operation

R3‑247402

(TP for TS 38.473) Discussion on on-demand SSB SCell operation

Huawei

other

Agreement

Yes

noted

R3‑245218

R3‑247209

Support on-demand SSB operation

NEC

discussion

Decision

Yes

available

R3‑247241

(TP to BL CR for TS 38.473) Discussion on On-Demand SSB SCell Operation

CMCC

other

Discussion

Yes

available

R3‑247272

On support on-demand SSB SCell operation

CATT

discussion

Decision

Yes

available

R3‑247303

Discussion on on-demand SSB SCell operation in low-carbon green network

Samsung

discussion

Approval

Yes

available

R3‑247386

On support on-demand SSB SCell operation

China Telecom

discussion

Decision

Yes

available

R3‑247440

Discussion on On-demand SSB for SCell

Lenovo

discussion

Discussion

Yes

available

R3‑247550

(TP to BL CR for 38.473) Further discussion on on-demand SSB Scell operation

ZTE Corporation

other

Agreement

Yes

available

R3‑247805

CB:#ES1_OndemandSSB

Huawei

discussion

Discussion

reserved

17.3

Support on-demand SIB1 for UEs

R3‑247559

Xn impact of On-demand SIB1 for UEs in idle/inactive mode

Ericsson, Deutsche Telekom, China Unicom

other

Agreement

Yes

noted

R3‑245498

R3‑247551

(TP to BL CR for 38.423) Further discussion on on-demand SIB1

ZTE Corporation

other

Agreement

Yes

noted

R3‑247480

Discussion on gaps in Cell-A coverage for OD-SIB1 and automatic recovery

Ericsson

discussion

Decision

Yes

available

R3‑247158

Discussion on OD-SIB1

Rakuten Mobile, Inc

discussion

Decision

Yes

available

R3‑247210

Support on-demand SIB1

NEC

discussion

Decision

Yes

available

R3‑247230

Aspects of on-demand SIB1 for NES enhancements

Qualcomm Inc.

discussion

Discussion

Yes

available

R3‑247242

Support On-Demand SIB1 for UEs

CMCC

discussion

Discussion

Yes

available

R3‑247273

On support on-demand SIB1 for idle UE

CATT

discussion

Decision

Yes

available

R3‑247304

Discussion on on-demand SIB1 in low-carbon green network

Samsung

discussion

Approval

Yes

available

R3‑247324

On-demand SIB1 for UEs in idle/inactive mode

Fujitsu

discussion

Decision

Yes

available

R3‑247387

On support on-demand SIB1

China Telecom

discussion

Decision

Yes

available

R3‑247403

(TP for TS 38.473 and TS 38.423) Discussion on on-demand SIB1 for UEs in idle or inactive mode

Huawei

other

Agreement

Yes

available

R3‑245219

R3‑247441

Discussion on On-demand SIB1 for Idle/Inactive UE

Lenovo

discussion

Yes

available

R3‑247552

F1 impact of On-demand SIB1 for UEs in idle/inactive mode

Ericsson

discussion

Yes

available

R3‑245517

R3‑247565

Xn signalling for On-Demand SIB1

Nokia

discussion

Yes

available

R3‑247626

Discussion of new procedures to support OD-SIB1

Rakuten Mobile, Inc

discussion

Yes

available

R3‑247806

CB:#ES2

Ericsson

discussion

reserved

17.4

Others

R3‑247566

Initial discussion on adaptation of common signals/channels

Nokia

discussion

Yes

available

NR Low Power WUS/WUR WI

18.1

General

R3‑247256

Work plan for Rel-19 WI on LP-WUSWUR

vivo

Work Plan

Approval

Yes

available

18.2

Support LP-WUS Indicating Paging Monitoring

R3‑247007

LS on LP-WUS subgrouping

RAN2(vivo)

LS in

Discussion

Yes

available

R3‑247257

Discussion on LP-WUS for NR

vivo, NTT DOCOMO INC.

discussion

Discussion

Yes

available

R3‑247669

Discussion on supporting LP-WUS Indicating Paging Monitoring

CMCC

discussion

Discussion

Yes

available

R3‑247579

Discussion of LPWUS impacts on NG-RAN architecture

Ericsson

discussion

Discussion

Yes

available

R3‑247145

Discussion on RAN3 impacts for LP-WUS

ZTE Corporation

discussion

Agreement

Yes

available

R3‑247636

Further discussion on LP-WUS subgrouping

NTT DOCOMO INC..

discussion

Yes

available

R3‑247231

Support LP-WUS subgrouping in RRC_IDLE/RRC_INACTIVE

Qualcomm Inc.

discussion

Discussion

Yes

available

R3‑247404

(TP for TS 38.413 and TS 38.423) Discussion on Low-power wake-up signal and receiver for NR

Huawei

other

Agreement

Yes

available

R3‑247473

Potential RAN3 impacts of LP-WUS

CATT

discussion

Discussion

Yes

available

R3‑247474

[Draft] Reply to LS on LP-WUS subgrouping

CATT

LS out

Agreement

Yes

available

R3‑247493

Support of LP-WUS

Nokia

draftCR

Yes

available

R3‑247258

BLCR for TS 38.300 on support of LP-WUS

vivo, NTT DOCOMO INC.

draftCR

Discussion

Yes

available

R3‑247501

Support of LP-WUS

Nokia

Yes

available

R3‑247569

Introduction of LP-WUS paging monitoring

Ericsson

Endorsement

Yes

available

R3‑245338

R3‑247719

(TP to BLCR for TS 38.413, 38.423, 38.473) Discussion on LP-WUS subgrouping

Samsung

other

Agreement

Yes

available

R3‑247220

(TP to 38.413, 38.423, 38.473 on LP-WUS) LP-WUS RAN3 related aspect

NEC

other

Agreement

Yes

available

R3‑247146

(TP to TS 38.413, 38.473, 38.423) on support of LP-WUS

ZTE Corporation

other

Agreement

Yes

available

R3‑247637

(TP to TS 38.413 and 38.473) Further discussion on LP-WUS subgrouping

NTT DOCOMO INC..

other

Agreement

Yes

available

R3‑247670

(TP to BL CR for 38.473) support of LP-WUS

CMCC

other

Agreement

Yes

available

R3‑247405

Introduction of low-power wake-up signal and receiver for NR

Huawei

Yes

available

R3‑245221

Evolution of Duplex Operation WI

19.1

General

19.2

Support CLI Handling

R3‑247639

Further discussions on SBFD related information exchange

Huawei

discussion

Discussion

Yes

available

R3‑247224

Discussion on CLI handling support

NEC

discussion

Decision

Yes

available

R3‑247281

Signaling design to enable NR SBFD operation

Qualcomm Incorporated

discussion

Agreement

Yes

available

R3‑245068

R3‑247347

Discussion on information exchanges among gNBs for CLI handling

Samsung

discussion

Approval

Yes

available

R3‑247519

Discussion on RAN3 impacts to support enhancements for CLI handling for SBFD

Ericsson

discussion

Approval

Yes

available

R3‑247567

Further discussion on inter-gNB CLI mitigation for SBFD operation

Nokia

discussion

Yes

available

R3‑247598

SBFD related CLI measurement configuration, CLI mitigation and CLI testing

Charter Communications

discussion

Agreement

Yes

available

R3‑247664

Discussion on supporting CLI handling in SBFD

CMCC

discussion

Discussion

Yes

available

R3‑247698

Open issues on CLI handling in SBFD

LG Electronics Inc.

discussion

Yes

available

R3‑247716

Discussion on Evolution of Duplex Operation

CATT

discussion

Decision

Yes

available

R3‑247732

Discussion on Information exchange for SBFD

ZTE corporation

discussion

Decision

Yes

available

R3‑247348

TPs to BLCRs of TS38.423 and TS38.473 on CLI handling

Samsung

other

Agreement

Yes

available

R3‑247520

TP to TS38.423 on enhancements for CLI handling for SBFD

Ericsson

other

Agreement

Yes

available

R3‑247640

BL CR on the introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD)

Huawei

Endorsement

Yes

available

R3‑245217

R3‑247665

(TP for TS 38.423) Support CLI handling

CMCC

other

Agreement

Yes

available

R3‑247699

(TP for NR_duplex_evo-Core for TS 38.423 and TS 38.473) Open issues on CLI handling in SBFD

LG Electronics Inc.

other

Agreement

Yes

available

R3‑247717

(TP for 38.420, 38.423, 37.340 and 38.473) Support SBFD Operation

CATT

other

Agreement

Yes

available

R3‑247733

(TP for BLCR 38.300&401&420&423&473-36.423-37.340) SBFD

ZTE corporation

other

Agreement

Yes

available

AI/ML for Air Interface WI

20.1

General

R3‑247576

Work Plan for Rel-19 on AI/ML for PHY (Positioning)

Ericsson (Rapporteur)

Work Plan

noted

Yes

noted

R3‑247017

Reply LS on AIML data collection

SA2(InterDigital)

LS in

Discussion

Yes

noted

R3‑247116

Reply LS on AIML Data Collection

SA5(ZTE)

LS in

Discussion

Yes

noted

R3‑247422

[Draft LS] Discussion on reply LS on AIML data collection

ZTE Corporation

LS out

Agreement

Yes

revised

R3‑247801

Reply LS on AIML data collection

RAN3(ZTE)

LS out

Agreement

agreed

R3‑247422

R3‑247577

Analysis and discussion on the Reply LS on AIML data collection

Ericsson

discussion

Decision

Yes

noted

R3‑247625

Discussion on the LS on AI/ML Data Collection from SA2

Nokia

discussion

Yes

available

R3‑247332

Draft Reply for LS on AIML data collection

Qualcomm Incorporated

LS out

Agreement

Yes

available

R3‑247420

Discussion on the LS reply from SA2 on AI/ML Data Collection

Huawei

discussion

Decision

Yes

available

20.2

Support Positioning Accuracy Enhancements

R3‑247578

Discussion on NRPPa signalling design for AI/ML for PHY

Ericsson

discussion

Discussion

Yes

noted

R3‑247319

(TP for TS 38.455) Support of gNB-side model (case 3a)

Xiaomi

other

Agreement

Yes

available

R3‑247221

Discussion on AIML based Positioning Accuracy Enhancements

NEC

discussion

Decision

Yes

available

R3‑247243

Support AIML Assisted Positioning

CMCC

discussion

Discussion

Yes

available

R3‑247244

(TP to BL CR for TS 38.455) Support Direct AI/ML Positioning

CMCC

other

Agreement

Yes

available

R3‑247293

Discussion on Direct AIML positioning

CATT

discussion

Decision

Yes

available

R3‑247294

Discussion on AIML assisted positioning

CATT

discussion

Decision

Yes

available

R3‑247305

Discussion on Case 3a in AI/ML for positioning

Samsung

discussion

Approval

Yes

available

R3‑247306

Discussion on Case 3b in AI/ML for positioning

Samsung

discussion

Approval

Yes

available

R3‑247320

(TP for TS 38.455) Support of LMF-side model (case 3b)

Xiaomi

other

Agreement

Yes

available

R3‑247372

Discussion on support of direct AI/ML positioning (Case 3b)

China Telecom

discussion

Discussion

Yes

available

R3‑247373

Discussion on support of AI/ML assisted positioning (Case 3a)

China Telecom

discussion

Discussion

Yes

available

R3‑247421

Discussion on RAN3 impacts for AI/ML positioning

Huawei

discussion

Agreement

Yes

available

R3‑247423

Discussion on AIML assisted Positioning (Case 3a&3b)

ZTE Corporation

other

Yes

available

R3‑247447

AIML for gNB assisted positioning

Lenovo

discussion

Yes

available

R3‑247459

AI/ML based positioning accuracy enhancements

Qualcomm Incorporated

discussion

Yes

available

R3‑247529

AI/ML-Assisted Positioning Focused on Cases 3a and 3b

Jio

discussion

Discussion

Yes

available

R3‑247624

AI/ML Positioning for Case 3a and Case 3b

Nokia

discussion

Yes

available

R3‑247647

Discussion on support of AIML assisted positioning (Case 3a)

Baicells

discussion

Decision

Yes

available

R3‑247662

Discussion on AI/ML-based Positioning Accuracy Enhancements

CEWiT

discussion

Decision

Yes

available

R3‑247803

CB:#AIPHY

Ericsson

discussion

reserved

NR XR Enhancements WI

21.1

General

21.2

Support XR in DC

Corrections and Enhancements to Rel-19

31.1

Corrections

R3‑247357

Correction on UAI for support XR in DC

Samsung, Ericsson, Cybercore, Qualcomm

Agreement

Yes

noted

R3‑247502

Exchange of MBS multicast services in RRC inactive

Nokia, Huawei, CATT, Qualcomm Incorporated

Agreement

Yes

noted

R3‑247756

Response to R3-247502 on the need to exchange multicast services on XnAP

ZTE Corporation

response

Agreement

Yes

noted

31.2

Enhancements

R3‑247556

Referencing Fronthaul Interface in 38.401

Ericsson, Qualcomm, AT&T, Orange, Verizon, Deutsche Telekom, NTT Docomo, Vodafone, T-Mobile

discussion

Discussion

Yes

noted

R3‑247557

Referencing Fronthaul Interface in 38.401

Ericsson, Qualcomm, AT&T, Orange, Verizon, Deutsche Telekom, NTT Docomo, Vodafone, T-Mobile

Agreement

Yes

noted

R3‑247657

Correction to enhancing QoS Monitoring with Per-Packet Granularity

ZTE Corporation, China Telecom, China Unicom, CMCC

Agreement

Yes

noted

R3‑247658

Enhancing QoS Monitoring with Per-Packet Granularity

ZTE Corporation, China Telecom, China Unicom, CMCC

discussion

Decision

Yes

noted

R3‑247580

Discussion on improving E-CID positioning accuracy

Ericsson, NTT DOCOMO, Nokia, Polaris Wireless

discussion

Discussion

Yes

available

R3‑247581

E-CID measurement enhancement

Ericsson, NTT Docomo, Nokia, Polaris Wireless

Agreement

Yes

available

R3‑247582

E-CID measurement enhancement

Ericsson, NTT Docomo, Nokia, Polaris Wireless

Agreement

Yes

available

R3‑247276

Support cell DTXDRX for NES

CATT, ZTE, NEC

discussion

Decision

Yes

available

R3‑247760

Response to R3-247276, R3-247277, R3-247278

Nokia, Ericsson, BT

response

Yes

available

R3‑247277

Support Cell DTXDRX for NES

CATT, ZTE, NEC

draftCR

Approval

Yes

available

R3‑245261

R3‑247278

Support Cell DTXDRX for NES

CATT, ZTE, NEC

draftCR

Approval

Yes

available

R3‑245351

R3‑247602

Inactivity Timer for Fixed Wireless Access

Nokia

Yes

available

R3‑245375

R3‑247753

Response to R3-247602

ZTE Corporation

response

Yes

available

R3‑247560

Disabling Inactivity Monitoring over E1

Ericsson

discussion

Yes

available

R3‑247561

Disabling Inactivity Monitoring over E1

Ericsson

Agreement

Yes

available

R3‑247763

Reply LS on RAN3 vs RAN2 Basketball Match

RAN2(Oppo)

LS in

Discussion

available

Any other business

Closing of the meeting