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	Consensus Principles
2.4	Responsible IT Behavior
2.5	Additional reminders
3	Approval of the Agenda	R3‑258001	RAN3#130 Meeting Agenda	RAN3 Chair	agenda	Approval	Yes	Yes	approved	No
4	Approval of the minutes from previous meetings	R3‑258002	RAN3#129-bis Meeting Report	ETSI-MCC	report	Approval	Yes	Yes	approved	No
5	Documents for immediate consideration
6	Organizational topics
7	General, protocol principles and issues	R3‑258003	TR 30.531 v1.61.0 Work Plan and Working Procedures - RAN WG3	ETSI-MCC	draft TR	Endorsement	Yes	Yes	endorsed	No
8	Incoming LSs
8.1	New Incoming LSs	R3‑258006	Reply LS on the handling of inter-DU L2 reset for LTM	RAN2(Ericsson)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258385	Corrections on L2 reset for LTM	ZTE Corporation	CR	Approval	Yes	YesHW, E///, Lenovo: not needed, text is correct SS: R18 focus is only on intra-DU, ok for R19 LGE: flow shows one CU to one DU, so only concerns intra-DU Stage 2 clarification for R19 only?	noted	No
		R3‑258386	Corrections on L2 reset for LTM	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑258387	Corrections on L2 reset for LTM	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑258388	Corrections on L2 reset for LTM	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑258007	LS Response on compatibility issue for PEI and emergency PDU session	SA2(ZTE)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258379	Discussion on LS Response on compatibility issue for PEI and emergency PDU session	ZTE Corporation	discussion	Decision	Yes	Yes	noted	No
		R3‑258415	Handling of emergency PDU session and PEI	Nokia	discussion		Yes	Yes	noted	No
		R3‑258420	Reply LS on compatibility issue for PEI and emergency PDU session	Nokia	LS out		Yes	No	available	No
		R3‑258538	On Restriction of PEIPS during emergency PDU session	Ericsson	discussion	Discussion	Yes	YesClarification in NGAP for CN Paging case	noted	No
		R3‑258539	Correction on PEIPS	Ericsson	CR	Agreement	Yes	YesNok: seems incorrect, there is no UE context when CN paging SS: similar view as Nokia, UE has been released to Idle HW, ZTE: already captured in SA2 spec	noted	No
		R3‑258540	Correction on PEIPS	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑258541	Correction on PEIPS	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑258574	Finalizing the compatibility issue for PEI and emergency PDU session	Huawei	discussion		Yes	Yes	noted	No
		R3‑258575	PEI usage in case of emergency PDU session	Huawei	draftCR		Yes	Yes	noted	No
		R3‑258576	PEI usage in case of emergency PDU session	Huawei	draftCR		Yes	No	available	No
		R3‑258577	PEI usage in case of emergency PDU session	Huawei	draftCR		Yes	No	available	No
		R3‑258010	Reply to Reply LS on removal of support of PWS over satellite NG-RAN in Rel-17 and 18	SA2(Samsung)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258105	Discussion on R17 and R18 PWS for NTN feature removal alignment between RAN and SA	ZTE Corporation	discussion		Yes	Yes	noted	No
		R3‑258466	Discussion on removal of support of PWS over satellite NG-RAN in Rel-17 and Rel-18	Huawei	discussion	Agreement	Yes	YesClarify that the Cell Identity used for PWS is provided only for BL UEs and UEs in enhanced coverage, but not for NB-IoT for Rel-17 and Rel-18 ZTE: needs to be further checked in CT1 E///: need to wait for other groups to complete their discussion CATT: agree we should wait for final outcome of CT1/SA2	noted	No
		R3‑258467	Correction of PWS support for IoT NTN	Huawei	draftCR	Endorsement	Yes	No	available	No
		R3‑258468	Correction of PWS support for IoT NTN	Huawei	draftCR	Endorsement	Yes	No	available	No
		R3‑258469	Reply LS on removal of support of PWS for NR NTN and IoT NTN in Rel-17 and 18	Huawei	LS out	Agreement	Yes	No	available	No
		R3‑258013	Reply LS on UE data collection and data transfer	RAN2(Nokia)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258014	Reply LS on signalling feasibility of dataset and parameter sharing	RAN2(Samsung)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258015	Reply LS on temporary suspension of trace production	RAN2(Ericsson)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258104	LS on Rel-19 higher layers parameters list Post RAN1#122bis	RAN1(Ericsson)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258258	Progress of ETSI ISG ISAC Work Items	ETSI ISG ISAC(Interdigital)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258699	LS on DTLS for SCTP Progress Report	IETF Transport and Services WG(TSVWG)(Huawei)	LS in	Discussion	Yes	YesE///: DTLS solution that enhances SCTP without limiting the maximum size of application protocol messages	noted	No
		R3‑258628	Discussion on average window for alternative QoS	ZTE Corporation	discussion	Approval	No	Yes	withdrawn	Yes
8.2	LSin received during the meeting	R3‑258766	LS on the signalling design of SCG LTM related parameters	RAN2(ZTE)	LS in	discussion	Yes	Yes	noted	No
		R3‑258794	Reply to Reply LS on removal of support of PWS over satellite NG-RAN in Rel-17 and 18	SA2(Samsung)	LS in	discussion	Yes	Yes	noted	No
8.3	Left over LSs / pending actions
9	Corrections to Rel-19 or earlier releases
9.1	LTE
9.1.1	R19 IoT NTN enhancements	R3‑258091	LS to SA2 on the paging in Store and Forward	RAN2(Huawei)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258644	Discussion on paging in Store and Forward	ZTE Corporation	discussion	Discussion	Yes	YesWhether there is DL data buffered in the MME when the feeder link is unavailable should be known by the eNB. E///: eNB cannot know when feeder link is unavailable HW: better to wait for SA2 feedback first	noted	No
		R3‑258199	Correction on the OAM requirements for NTN	Nokia, Nokia Shanghai Bell, Qualcomm, LG Electronics, ZTE, CATT, Ericsson, Huawei	draftCR		Yes	Yes- update WI code to IoT_NTN_Ph3-Core - add Samsung to co-sources	revised	No	R3‑258704
		R3‑258704	Correction on the OAM requirements for NTN	Nokia, Nokia Shanghai Bell, Qualcomm, LG Electronics, ZTE, CATT, Ericsson, Huawei, Samsung	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258199
		R3‑258485	Inter-Satellite Links and Transparent Payloads - IoT NTN	Ericsson, Aalyria, Thales, Airbus	draftCR	Endorsement	Yes	No	available	No
9.1.2	R19 LTE-based 5G Broadcast	R3‑258127	Correction on LTE-based 5G Broadcast	Huawei, EBU, Qualcomm Incorporated, ZTE	CR	Agreement	Yes	Yes- remove changes in section 9.2.1.8 and 9.2.1.31	revised	No	R3‑258705
		R3‑258705	Correction on LTE-based 5G Broadcast	Huawei, EBU, Qualcomm Incorporated, ZTE	CR	Agreement	Yes	Yes- check RRC field names	revised	No	R3‑258742	R3‑258127
		R3‑258742	Correction on LTE-based 5G Broadcast	Huawei, EBU, Qualcomm Incorporated, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑258705
9.1.3	Other
9.2	NR
9.2.1	R19 SON/MDT	R3‑258515	Clarifying the MRO for LTM use-case	Ericsson	CR	Agreement	Yes	YesHW: already described in Stage 2	noted	No
		R3‑258516	BFR in CSI-RS beam	Ericsson	CR	Agreement	Yes	YesHW: support ZTE: wording should be made more general - check wording of the semantics	revised	No	R3‑258707
		R3‑258707	BFR in CSI-RS beam	Ericsson	CR	Agreement	Yes	Yes	agreed	No		R3‑258516
		R3‑258149	Correction on MRO for SCG failure in EN-DC	ZTE Corporation, China Telecom, Pengcheng Laboratory	draftCR	Endorsement	Yes	YesHW: We only describe cases that require internode signaling, so need to list Addition - check if 1st change is agreeable, and whether/how to revised 2nd/3rd change	revised	No	R3‑258708
		R3‑258708	Correction on MRO for SCG failure in EN-DC	ZTE Corporation, China Telecom, Pengcheng Laboratory	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258149
		R3‑258645	Correction on MRO for S-CPAC and CHO with candidate SCG for 37.340	CATT, Samsung	draftCR	Endorsement	Yes	Yes1st change: Nok: prefer to first clarify the scenario SS: scenario seems already clear by the following sentence	revised	No	R3‑258709
		R3‑258709	Correction on MRO for S-CPAC and CHO with candidate SCG for 37.340	CATT, Samsung	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258645
		R3‑258460	Correction of Failure report without RLF report	Huawei, Nokia, JIO plattforms, Ericsson	CR	Agreement	Yes	YesSS: prefer to make as simple as possible QC: we should try to include both scenarios	revised	No	R3‑258762
		R3‑258762	Correction of Failure report without RLF report	Huawei, Nokia, JIO plattforms, Ericsson	CR	Agreement	Yes	Yes- remove change on change	revised	No	R3‑258824	R3‑258460
		R3‑258824	Correction of Failure report without RLF report	Huawei, Nokia, JIO plattforms, Ericsson	CR	Agreement	No	Yes	agreed	No		R3‑258762
		R3‑258673	Correction of missing stage 2 description of LTM MRO without RLF Report	ZTE Corporation, Google, NEC	CR	Agreement	Yes	Yes	noted	No
		R3‑258005	Reply LS on geographical area scope MDT	SA5(CATT)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258650	Discussion on reply LS on geographical area scope MDT	CATT	discussion	Decision	Yes	Yesmoved from 8.1 Nothing further work needed in SA5 E///, ZTE: SA5 CR seems correct	noted	No
		R3‑258651	Reply LS on geographical area scope MDT	CATT	LS out	Approval	Yes	Yesmoved from 8.1 - Provide RAN3 feedback for SA5 to take into account	revised	No	R3‑258710
		R3‑258710	Reply LS on geographical area scope MDT	RAN3(CATT)	LS out	Approval	Yes	Yes- change “provides feedback” to “provide feedback” - remove revision mark	revised	No	R3‑258823	R3‑258651
		R3‑258823	Reply LS on geographical area scope MDT	RAN3(CATT)	LS out	Approval	Yes	Yes	approved	No		R3‑258710
		R3‑258320	Discussion on Reply LS on geographical area scope MDT	Huawei	discussion		Yes	YesSS, Nokia, QC: agree that new optional IE is needed	noted	No
		R3‑258321	[Draft]Reply LS on geographical area scope MDT	Huawei	LS out		Yes	Yes	noted	No
		R3‑258594	[DRAFT] Reply LS on geographical area scope MDT	Samsung	LS out	Agreement	Yes	No	available	No
		R3‑258765	summary of CB: # 1_R19_SONMDT	CATT	discussion	Agreement	Yes	Yes- Further discuss 38.401 corrections in 8460 and 8673, merge if agreeable - Reply LS to SA5 (if agreeable) to explain why in RAN3 we use two different PLMN lists - Further discuss all open CRs above	noted	No
9.2.2	R19 AI/ML for NG-RAN	R3‑258214	Miscellaneous corrections to E1AP for support of AI/ML NG-RAN	ZTE Corporation, CATT, China Unicom, China Telecom	CR	Agreement	Yes	YesHW: 1st change already agreed at bis meeting NEC: Change “Registration Request For Data Collection” to “Registration Request for Data Collection” NEC: newly added paragraph may not be in correct place SS: Further details need checking	revised	No	R3‑258711
		R3‑258711	Miscellaneous corrections to E1AP for support of AI/ML NG-RAN	ZTE Corporation, CATT, China Unicom, China Telecom	CR	Agreement	No	No	reserved	No		R3‑258214
		R3‑258271	Corrections of AI/ML-based CCO	Nokia, Ofinno, Jio Platforms	CR	Agreement	Yes	YesE///, HW, SS: Current signaling design was done intentionally CATT: May be useful in some scenario ZTE: This solution is more straight forward than abnormal conditions	noted	No
		R3‑258422	Correction on CCO prediction cancel	NEC	CR	Agreement	Yes	Yes	noted	No
		R3‑258477	Discussion on XnAP reporting of predicted radio resource status per slice	Huawei	discussion	Agreement	Yes	YesWhen the Slice To Report List for Data Collection IE is present in the DATA COLLECTION REQUEST message, the Rel-19 ‘predicted radio resource status per slice’ is also reported along with the Rel-18 ‘predicted radio resource status’ Nok: CR is not needed ZTE, SS, E///: Proposal is correct, but no CR is needed NEC: Already can be supported, no CR is needed	noted	No
		R3‑258476	Correction on procedural text for reporting of predicted radio resource status per slice	Huawei	CR	Agreement	Yes	Yes	noted	No
		R3‑258478	Support for partial reporting in Data Collection Reporting procedure	Huawei, FiberCop, Verizon, Jio Platforms, Qualcomm, ZTE	CR	Agreement	Yes	YesNok: Agreed previously that partial reporting over E1 is not supported in this release E///: No strong motivation for “alignment”	revised	No	R3‑258774
		R3‑258774	Support for partial reporting in Data Collection Reporting procedure	Huawei, FiberCop, Verizon, Jio Platforms, Qualcomm, ZTE	CR	Agreement	No	No	reserved	No		R3‑258478
		R3‑258514	Discussion on Exit Conditions	Nokia	discussion		Yes	No	available	No
		R3‑258172	Correction of Exit Conditions	Nokia	CR		Yes	No	available	No
		R3‑258434	Abnormal conditions for F1: gNB-CU Configuration Update	Ericsson, Jio Platforms, InterDigital, Fibercop	discussion	Approval	Yes	No	available	No
		R3‑258546	Abnormal conditions for gNB-CU Configuration Update with updated Presence IE	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	Yes	Yes	noted	No
		R3‑258436	Correction for gNB-DU Configuration Update	Ericsson, Jio Platforms, InterDigital, Fibercop	discussion	Approval	Yes	No	available	No
		R3‑258547	Correction for gNB-DU Configuration Update	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	Yes	No	available	No
		R3‑258215	Miscellaneous corrections to the support of split architecture	ZTE Corporation, CMCC, China Unicom, China Telecom	CR		Yes	Yes	revised	No	R3‑258812
		R3‑258812	Miscellaneous corrections to the support of split architecture	ZTE Corporation, CMCC, China Unicom, China Telecom	CR	Agreement	No	No	reserved	No		R3‑258215
		R3‑258270	Corrections of enhancements on AI/ML for NG-RAN	Nokia	CR		Yes	No	available	No
		R3‑258438	Stage 2 corrections for AI/ML based CCO	Ericsson, Jio Platforms, InterDigital, Fibercop	discussion	Approval	Yes	No	available	No
		R3‑258548	Stage 2 corrections for AI/ML based CCO	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	Yes	No	available	No
		R3‑258604	Correction on CCO in split architecture for 38.401	CMCC	CR	Approval	Yes	No	available	No
		R3‑258269	Corrections of enhancements on AI/ML for NG-RAN	Nokia	draftCR		Yes	No	available	No
		R3‑258605	Correction on R19 AIML F1-U stage2	CMCC, Samsung, Qualcomm, ZTE, CATT, Nokia	CR	Approval	Yes	Yes	revised	No	R3‑258836
		R3‑258836	Correction on AIML F1-U stage2	CMCC, Samsung, Qualcomm, ZTE, CATT, Nokia	CR	Approval	No	No	reserved	No		R3‑258605
		R3‑258433	Continuous MDT support	Ericsson, Deutsche Telekom, FiberCop, Jio Platforms, InterDigital, BT, Orange, Verizon, ZTE, Huawei, Telecom Italia, NEC, Samsung, CATT, China Telecom, China Unicom	CR	Agreement	Yes	YesAdd a new IE including the TR and TRSR assigned to the UE by the source NG-RAN node in the XnAP HANDOVER REQUEST and in the RETRIEVE UE CONTEXT RESPONSE messages	noted	No		R3‑257309
		R3‑258216	Support for Continuous Management-based MDT	ZTE Corporation, Huawei, CATT, CMCC, Samsung, China Unicom, China Telecom, Ericsson, FiberCop, Deutsche Telekom, Jio Platforms	draftCR	Endorsement	Yes	Yes	noted	No
		R3‑258458	Support for continuous management-based MDT	CATT, Ericsson,ZTE, CMCC, Samsung, NEC	draftCR	Agreement	Yes	Yes	revised	No	R3‑258799
		R3‑258799	Support for continuous management-based MDT	CATT, Ericsson,ZTE, CMCC, Samsung, NEC	draftCR	Agreement	No	No	reserved	No		R3‑258458
		R3‑258685	Support for Continuous Management-based MDT in split architecture	Samsung, CATT, ZTE, CMCC, China Telecom, Huawei, Ericsson, FiberCop, Deutsche Telekom, China Unicom, NEC	CR	Agreement	Yes	Yes	noted	No		R3‑256690
		R3‑258475	[Draft] Reply LS on Continuous MDT	Huawei, ZTE, FiberCop, Jio Platforms	LS out	Agreement	Yes	Yes	revised	No	R3‑258773
		R3‑258773	Reply LS on Continuous MDT	RAN3(Huawei)	LS out	Approval	No	No	reserved	No		R3‑258475
		R3‑258173	Discussion on Continuous Management Based MDT	Nokia, Qualcomm	discussion		Yes	YesResponse in R3-258698	noted	No
		R3‑258698	Response to R3-258173	ZTE Corporation	response		Yes	No	available	No
		R3‑258416	Support of Continuous Management Based MDT	Nokia	CR		Yes	No	available	No
		R3‑258417	Introduction of support for Continuous Management Based MDT in stage 2	Nokia	draftCR		Yes	No	available	No
		R3‑258606	Correction to support Continuous MDT through Xn interface	CMCC	CR	Approval	Yes	No	available	No
		R3‑258811	Summary of the offline discussion on CB: # 2_R19_AIMLNGRAN	ZTE Corporation	discussion	Approval	No	No	reserved	No
		R3‑258253	reserved	NEC	CR	Agreement	No	Yes	withdrawn	Yes
		R3‑258435	Abnormal conditions for gNB-CU Configuration Update with updated Presence IE	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	Yes	Yes	withdrawn	Yes
		R3‑258437	Correction for gNB-DU Configuration Update	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	Yes	Yes	withdrawn	Yes
		R3‑258439	Stage 2 corrections for AI/ML based CCO	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	Yes	Yes	withdrawn	Yes
		R3‑258497	Abnormal conditions for gNB-CU Configuration Update with updated Presence IE	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	No	Yes	withdrawn	Yes
		R3‑258498	Correction for gNB-DU Configuration Update	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	No	Yes	withdrawn	Yes
		R3‑258499	Stage 2 corrections for AI/ML based CCO	Ericsson, Jio Platforms, InterDigital, Fibercop	CR	Agreement	No	Yes	withdrawn	Yes
		R3‑258703	Response to R3-258173	Ericsson	response	Agreement	Yes	Yes	withdrawn	Yes
9.2.3	R19 WAB	R3‑258200	Correction of WAB-MT handover a target WAB-gNB	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT, China Telecom, Canon, Qualcomm	CR		Yes	YesE///: text should be aligned with current XnAP text	revised	No	R3‑258769	R3‑257259
		R3‑258769	Clarification of handover for WAB-MT	Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT, China Telecom, Canon, Qualcomm	CR	-	Yes	Yes	agreed	No		R3‑258200
		R3‑258331	Correction on multi-hop avoidance during handover	Huawei, Nokia, Nokia Shanghai Bell, China Telecom	CR	Approval	Yes	Yes	revised	No	R3‑258770
		R3‑258770	Clarification of handover for WAB-MT	Huawei, Nokia, Nokia Shanghai Bell, China Telecom	CR	Approval	Yes	Yes- add space in “TS 38.401[2]”	revised	No	R3‑258825	R3‑258331
		R3‑258825	Clarification of handover for WAB-MT	Huawei, Nokia, Nokia Shanghai Bell, China Telecom	CR	Approval	Yes	Yes	agreed	No		R3‑258770
		R3‑258380	Corrections for additional ULI for WAB	ZTE Corporation, China Telecom, Pengcheng Laboratory, Samsung	CR	Approval	Yes	Yes	noted	No
		R3‑258570	Correction of BH-gNB for WAB	China Telecom,CATT, Nokia, Nokia Shanghai Bell, ZTE	draftCR	Endorsement	Yes	YesE///: “stationary” was removed at the bis meeting	noted	No
		R3‑258265	Stage-2 Correction of WAB Xn Connection Management	Ericsson	CR	Agreement	Yes	YesSS: Normal gNB is able to reject Xn setup from WAB gNB QC: fine with CR HW: does it require legacy gNB to recognize the new IE	revised	No	R3‑258771
		R3‑258771	Stage-2 Correction of WAB Xn Connection Management	Ericsson	CR	Agreement	Yes	YesZTE, SS: remove “(e.g., by OAM)”, should be further discussed - revert changes to the last paragraph	revised	No	R3‑258828	R3‑258265
		R3‑258828	Stage-2 Correction of WAB Xn Connection Management	Ericsson	CR	Agreement	No	Yes	agreed	No		R3‑258771
		R3‑258571	Correction of BH-gNB and WAB-MT for WAB	China Telecom, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE	CR	Agreement	Yes	Yes	revised	No	R3‑258772
		R3‑258772	Correction of BH-gNB and WAB-MT for WAB	China Telecom, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE	CR	Agreement	Yes	Yes- add back the accepted removal of “gNB”	revised	No	R3‑258829	R3‑258571
		R3‑258829	Correction of BH-gNB and WAB-MT for WAB	China Telecom, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑258772
		R3‑258768	Clarification of handover for WAB-MT	Qualcomm	CR	Agreement	Yes	Yes	agreed	No
9.2.4	R19 NR Femto	R3‑258300	Correction on sending GW release indication	CATT	draftCR	Approval	Yes	YesSS: “handover to another NG-RAN node” to “handover to another target NG-RAN node” ZTE: text in Femto GW functions covers this HW: changes makes sense, indication needs to be sent with every Xn handover CB # 4_R19_Femto - Check detailed wording of the CR (CATT - moderator)	revised	No	R3‑258712
		R3‑258712	Correction on sending GW release indication	CATT	draftCR	Approval	Yes	Yes	endorsed	No		R3‑258300
		R3‑258381	Corrections on GUAMI List for Femto	ZTE Corporation, China Telecom, Pengcheng Laboratory	CR	Approval	Yes	YesNok, E///: new text doesn’t change the meaning HW: original text is clear enough	noted	No
9.2.5	R19 Mobility enhancements	R3‑258672	R19 correction (CSI-RS) on the CU-DU Mobility Initiation Request message	Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC	CR	Agreement	Yes	Yes	agreed	No
		R3‑258157	Correction to inter-CU LTM and conditional intra-CU LTM	Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Ericsson, LG Electronics, Qualcomm Incorporated, Google, Ofinno	CR		Yes	YesE///: 8.2.1.8 step 3 (and other sections) may clash with 8560/8561	revised	No	R3‑258778
		R3‑258778	Correction to inter-CU LTM and conditional intra-CU LTM	Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Ericsson, LG Electronics, Qualcomm Incorporated, Google, Ofinno	CR	-	No	No	reserved	No		R3‑258157
		R3‑258263	Correction on SN initiated inter-SN SCG LTM procedure	Ofinno, Ericsson, CATT, Qualcomm, Huawei, Google, LG Electronics, Nokia, Samsung, Lenovo, China Telecom	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑257033
		R3‑258293	Correction on LTM Cell Switch Notification	LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE	CR	Approval	Yes	Yes	agreed	No		R3‑257125
		R3‑258294	Correction related to LTM Security Information	LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE	CR	Approval	Yes	Yes	agreed	No		R3‑257126
		R3‑258390	Essential correction on inter-CU LTM in DC	CATT,Huawei, China Telecom, Nokia, Samsung, NEC, Ericsson	CR	Agreement	Yes	YesLenovo, LGE: don’t agree with proposal 4 - remove Proposal 4 - fix semantics “or LTM Candidate PSCell Change Information Required IE o” to “or the LTM Candidate PSCell Change Information Required IE”	revised	No	R3‑258713	R3‑256873
		R3‑258713	Essential correction on inter-CU LTM in DC	CATT,Huawei, China Telecom, Nokia, Samsung, NEC, Ericsson	CR	Agreement	No	Yes	agreed	No		R3‑258390
		R3‑258392	Essential correction for inter-CU LTM on F1AP	CATT,Huawei, China Telecom, LG Electronics, Nokia, Samsung, ZTE, Ofinno, Ericsson	CR	Agreement	Yes	YesE///: 8.2.1.8 step 3 (and other sections) may clash with 8560/8561	revised	No	R3‑258787	R3‑256871
		R3‑258787	Essential correction for inter-CU LTM on F1AP	CATT,Huawei, China Telecom, LG Electronics, Nokia, Samsung, ZTE, Ofinno, Ericsson	CR	Agreement	No	No	reserved	No		R3‑258392
		R3‑258508	Corrections on Inter-CU LTM	Ericsson, Lenovo, LG Electronics, Nokia, Samsung, ZTE, Ofinno	CR	Agreement	Yes	Yes	agreed	No		R3‑257175
		R3‑258510	Corrections for Rel-19 LTM	Ericsson, Jio Platforms, CATT, China Telecom, Lenovo, LG Electronics, Nokia, ZTE, Samsung, Ofinno	draftCR		Yes	Yes	endorsed	No
		R3‑258558	Support for Modification of LTM Configurations	Ericsson, Ofinno, Jio Platforms	discussion		Yes	Yesintroduce a new procedure, initiated by the candidate gNB, to update the LTM-related configurations. Updated configurations would include CSI-RS resource configurations, early UL sync and CFRA resource configurations. The candidate gNB may trigger configuration updates during both LTM preparation and subsequent LTM phases. Nok: RAN3 previously agreed this is an optimization, not needed SS: existing procedure can be reused by simply adding some IEs in the corresponding message (see 8665) QC: new procedure would be cleaner (fewer steps), Modification Request from candidate cells belong to serving DU or other DU	noted	No
		R3‑258559	Support for Modification of LTM Configurations	Ericsson, Ofinno, Jio Platforms	CR	Agreement	Yes	Yes	noted	No
		R3‑258695	Support for Modification of LTM Configurations	Ericsson, Jio Platforms, Ofinno	draftCR	Endorsement	Yes	Yes	noted	No
		R3‑258587	Discussion on candidate gNB initiated LTM modification (CRs included)	Huawei	discussion		Yes	Yesreuse the existing LTM cancel procedure to support the candidate gNB initiated LTM modification function by introducing a proper cause value, e.g., “LTM resources to be updated”. CATT, ZTE, Lenovo, Nokia, NEC: agree with this approach	noted	No
		R3‑258589	[Draft]LS on candidate gNB initiated LTM modification	Huawei	LS out	Approval	Yes	No	available	No
		R3‑258151	Exchange of early RACH Resources Requester ID for inter-CU LTM	Huawei, Ericsson, Samsung, Jio Platforms, CATT, CMCC, China Telecom, Lenovo, Nokia	discussion		Yes	Yesexchange the early RACH Resources Requester IDs in the Served Cell Information IE between neighbouring gNBs during Xn Setup and NG-RAN node configuration update for support of inter-CU LTM	noted	No
		R3‑258152	Exchange of early RACH Resources Requester ID for inter-CU LTM	Huawei, Ericsson, Samsung, Jio Platforms, CATT, CMCC, China Telecom, Lenovo, Nokia	CR	Approval	Yes	YesQC: prefers not to impact interface management procedure	noted	No
		R3‑258661	Corrections on Early RACH Resource Requester ID	ZTE Corporation	CR	Approval	Yes	YesAdd Early RACH Resource Request ID of the accepted candidate LTM cell in the Handover Request Acknowledge message and LTM Candidate PSCell Prepared List IE LGE: Requires 3 roundtrips rather than 2, nothing is broken (solved by implementation)	noted	No
		R3‑258662	Corrections on Early RACH Resource Requester ID	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑258509	Summary of Essential Corrections and Open Issues for Rel-19 LTM	Ericsson, CATT, Jio Platforms, Ofinno	discussion		Yes	No	available	No
		R3‑258153	Introduction of missing LTM Indicator for inter-CU LTM	Huawei, Nokia, LG Electronics, NTT DoCoMo. Offinno, Jio Platforms, CMCC	CR		Yes	Yes	revised	No	R3‑258780
		R3‑258780	Introduction of missing LTM Indicator for inter-CU LTM	Huawei, Nokia, LG Electronics, NTT DoCoMo. Offinno, Jio Platforms, CMCC, Ericsson	CR	-	No	No	reserved	No		R3‑258153
		R3‑258154	Correction on Reference Configuration in LTM Configuration Update for inter-CU LTM	Huawei, NTT DoCoMo, Offinno, Jio Platforms, CMCC, Lenovo, CATT	CR		Yes	No	available	No
		R3‑258155	Correction on the CSI-RS Coordination procedure	Huawei, LG Electronics, ZTE, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo	CR		Yes	Yes	revised	No	R3‑258779
		R3‑258779	Correction on the CSI-RS Coordination procedure	Huawei, LG Electronics, ZTE, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo	CR	-	No	No	reserved	No		R3‑258155
		R3‑258156	Interaction between Handover Success and Cell Switch Notification	Huawei, Nokia, LG Electronics, NTT DoCoMo, ZTE, Offinno, Jio Platforms, CMCC	CR		Yes	No	available	No
		R3‑258275	[Draft TP for TS 38.473, TS 38.423] Remaining issues in Inter-CU LTM	Qualcomm Incorporated	other	Agreement	Yes	No	available	No
		R3‑258312	Discussion on supporting inter-CU SCG LTM and the L2 reset function in inter-CU LTM	Google	discussion	Decision	Yes	No	available	No		R3‑257157
		R3‑258313	Correction to L2 reset in inter-CU LTM	Google, Nokia, CATT, Ericsson	CR	Agreement	Yes	No	available	No		R3‑257158
		R3‑258317	Correction to L2 reset in inter-CU LTM (option 2)	Google, Huawei	CR		Yes	Yes	revised	No	R3‑258781
		R3‑258781	Correction to L2 reset in inter-CU LTM (option 2)	Google, Huawei	CR	-	No	No	reserved	No		R3‑258317
		R3‑258319	Correction to LTM MCG configuration management for inter-CU SCG LTM	Google, Huawei	CR		Yes	No	available	No
		R3‑258322	Correction on the Rel-19 set ID assignment in inter-CU LTM	Huawei, Nokia, Jio Platforms, CATT, China Telecom, Lenovo	discussion		Yes	No	available	No
		R3‑258323	Correction on the Rel-19 set ID assignment in inter-CU LTM (Option 1)	Huawei, Jio Platforms, CATT, China Telecom, Lenovo	draftCR		Yes	No	available	No
		R3‑258324	Correction on the Rel-19 set ID assignment in inter-CU LTM (Option 2)	Huawei, Nokia, Jio Platforms, CATT, China Telecom	CR		Yes	No	available	No
		R3‑258325	Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM	Huawei, NEC,Jio Platforms, CMCC, China Telecom, Lenovo	discussion		Yes	No	available	No
		R3‑258326	Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1)	Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo	CR		Yes	No	available	No
		R3‑258328	Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2)	Huawei, NEC, Jio Platforms, CMCC, China Telecom	CR		Yes	No	available	No
		R3‑258341	Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1)	Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo	CR		Yes	No	available	No
		R3‑258342	Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2)	Huawei, NEC, Jio Platforms, CMCC, China Telecom	CR		Yes	No	available	No
		R3‑258459	Semi-Persistent CSI-RS activation with TCI state for CSI Acquisition	CATT	CR	Agreement	Yes	No	available	No
		R3‑258471	LTM Cell Swicth Type Indication	Nokia, LGE, Huawei	CR		Yes	No	available	No
		R3‑258473	LTM Cell Swicth Type Indication	Nokia, LGE, Huawei	CR		Yes	No	available	No
		R3‑258555	PRACH resources for Inter-CU LTM	Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno	discussion		Yes	No	available	No		R3‑257042
		R3‑258551	PRACH resources for Inter-CU LTM	Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno	CR	Agreement	Yes	No	available	No		R3‑257043
		R3‑258552	PRACH resources for Inter-CU LTM	Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno	CR	Agreement	Yes	No	available	No		R3‑257044
		R3‑258553	PRACH resource for Inter-CU LTM	Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno	CR	Agreement	Yes	No	available	No		R3‑257045
		R3‑258554	PRACH resources for Inter-CU LTM	Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno	draftCR	Endorsement	Yes	No	available	No		R3‑257046
		R3‑258556	Fast LTM recovery for Inter-CU LTM	Ericsson, Jio Platforms, Lenovo, Ofinno	discussion		Yes	No	available	No		R3‑257047
		R3‑258557	Fast LTM Recovery for Inter-CU LTM	Ericsson, Jio Platforms, Lenovo, Ofinno	CR	Agreement	Yes	No	available	No		R3‑257048
		R3‑258560	Removal of Request for CSI-RS resource configuration for Early CSI acquisition	Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE	CR	Agreement	Yes	Yes	revised	No	R3‑258837	R3‑257173
		R3‑258837	Removal of Request for CSI-RS resource configuration for Early CSI acquisition	Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE	CR	Agreement	No	No	reserved	No		R3‑258560
		R3‑258561	Removal of Request for CSI-RS resource configuration for Early CSI acquisition	Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE	CR	Agreement	Yes	Yes	revised	No	R3‑258838	R3‑257174
		R3‑258838	Removal of Request for CSI-RS resource configuration for Early CSI acquisition	Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE	CR	Agreement	No	No	reserved	No		R3‑258561
		R3‑258582	Correction on NG-RAN node UE XnAP IDs transfer after LTM failure	Huawei, Nokia, Offinno, Jio Platforms, CMCC	CR		Yes	No	available	No
		R3‑258583	UE context retrieval in the candidate gNB during subsequent LTM	Huawei, Nokia, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo	CR		Yes	No	available	No
		R3‑258584	Corrections on inter-CU MCG LTM without SN change	Huawei, Jio Platforms, Lenovo, Google	discussion		Yes	No	available	No
		R3‑258585	Stage 2 corrections to inter-CU MCG LTM	Huawei, Jio Platforms, Lenovo, Google	draftCR		Yes	No	available	No
		R3‑258586	Correction on security key update for inter-CU MCG LTM	Huawei, Jio Platforms, China Telecom, Lenovo, Google	CR		Yes	No	available	No
		R3‑258590	Stage 2 corrections on inter-CU LTM	Huawei	draftCR		Yes	No	available	No
		R3‑258659	Corrections on last target NG-RAN node UE XnAP ID transfer	ZTE Corporation, CATT, Huawei	CR	Approval	Yes	No	available	No
		R3‑258660	Discussion on remaining issues on early sync	ZTE Corporation	discussion	Decision	Yes	No	available	No
		R3‑258663	Corrections on LTM Early Sync resource update	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑258664	Corrections on LTM Early Sync resource update	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑258665	Remaining Issues on Inter-CU LTM	Samsung	discussion	Discussion	Yes	Yes	noted	No
		R3‑258666	XnAP correction on the Inter-CU LTM procedure	Samsung	CR	Agreement	Yes	Yes	revised	No	R3‑258775
		R3‑258775	XnAP correction on the Inter-CU LTM procedure	Samsung	CR	Agreement	No	No	reserved	No		R3‑258666
		R3‑258667	Correction on TA Information Transfer for inter-CU SCG LTM	Samsung, Huawei, Ericsson, Nokia, Google	CR	Agreement	Yes	No	available	No
		R3‑258668	Correction on Early UL Sync Configuration IE for inter-CU LTM	Samsung, Huawei, Ericsson, Nokia, China Telecom, Google	CR	Agreement	Yes	Yes	revised	No	R3‑258776
		R3‑258776	Correction on Early UL Sync Configuration IE for inter-CU LTM	Samsung, Huawei, Ericsson, Nokia, China Telecom, Google	CR	Agreement	No	No	reserved	No		R3‑258668
		R3‑258669	Correction on the LTM Indicator for C-LTM	Samsung, Huawei, Ericsson, LG Electronics, Nokia, China Telecom, Google	CR	Agreement	Yes	Yes	revised	No	R3‑258777
		R3‑258777	Correction on the LTM Indicator for C-LTM	Samsung, Huawei, Ericsson, LG Electronics, Nokia, China Telecom, Google	CR	Agreement	No	No	reserved	No		R3‑258669
		R3‑258090	Discussion on remaining Inter-CU LTM Issues	Nokia	discussion	Agreement	No	Yes	withdrawn	Yes
		R3‑258291	Correction on LTM Cell Switch Notification	LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE	CR	Approval	No	Yes	withdrawn	Yes
		R3‑258292	Correction related to LTM Security Information	LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE	CR	Approval	No	Yes	withdrawn	Yes
		R3‑258327	Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1)	Huawei	CR		No	Yes	withdrawn	Yes
		R3‑258329	Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2)	Huawei	CR		No	Yes	withdrawn	Yes
		R3‑258588	Candidate gNB-DU initiated LTM modification	Huawei	CR		No	Yes	withdrawn	Yes
		R3‑258813	Summary of the offline discussion on CB: # 5_R19_MobEnh	Samsung	discussion	Approval	No	No- Discuss 8560/8561 - Modification of LTM configurations - Early RACH resource requestor ID, can either 8152 or 8611 be agreed - Identify items where there’s consensus to address (e.g., as essential correction or “to be continued” for next meeting)	reserved	No
		R3‑258818	Removal of Request for CSI-RS resource configuration for Early CSI acquisition	LG Electronics, Ericsson, Jio Platforms, Verizon Wireless, ZTE, CATT, China Telecom, Google, Huawei, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Lenovo	draftCR	Endorsement	No	No	reserved	No
		R3‑258839	TBD	Ericsson	draftCR	Endorsement	No	No	reserved	No
		R3‑258840	TBD	Ericsson	draftCR	Endorsement	No	No	reserved	No
9.2.6	R19 NR NTN enhancements	R3‑258239	Correction to stage 2 description of Hard Feeder Link Switchover for regenerative payload	NEC	draftCR	Agreement	Yes	YesE///: current text is sufficient, radio link is general (transport link) CATT, ZTE: does “radio link” mean only Uu? OK without the change HW: same understanding as E/// Thales: important to keep “radio link”	noted	No
		R3‑258472	Inter-Satellite Links and Transparent Payloads	Ericsson, Aalyria, Thales, Airbus	discussion	Discussion	Yes	YesRemove the limitation from stage 2, that ISL is only defined between two regenerative NTN payloads Nok: why must ISL use additional hop, i.e. regenerative payloads cannot connect directly? E///: similar to terrestrial topologies HW: current definition matches specifications QC: is it necessary to reflect this case in 3GPP specs? Thales: This is a real scenario	noted	No
		R3‑258474	Inter-Satellite Links and Transparent Payloads - NR NTN	Ericsson, Aalyria, Thales, Airbus	draftCR	Endorsement	Yes	Yes	noted	No
9.2.7	R19 Ambient IoT	R3‑258011	LS on integrity failure	RAN2(Xiaomi)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258012	Reply LS on Structure updates of AIoT Identifiers	SA2(CATT)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258092	Reply LS on the maximum supported AIoT NAS container length	RAN2(Lenovo)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258121	Consideration on A-IoT dedicated Cause values	Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson	discussion	Agreement	Yes	YesXmi: For NAS cause, it is discussed in RAN2 QC: Generally OK, CR needs some refinement CATT: Some aspects are pending RAN2 SS: Most of the values are beneficial, but NAS needs further discussion	noted	No
		R3‑258122	Correction on A-IoT dedicated Cause values	Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson	CR	Agreement	Yes	Yes- Remove NAS cause value - “device” to “A-IoT device” - “unknown” spelling, further editorials - Add CATT, NEC, Xiaomi, Samsung, ZTE as co-sources	revised	No	R3‑258732
		R3‑258732	Correction on A-IoT dedicated Cause values	Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson, CATT, NEC, Xiaomi, Samsung, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑258122
		R3‑258336	Discussion on Cause values for Ambient IoT	CATT	discussion	Decision	Yes	No	available	No
		R3‑258691	Correction to A-IoT specific cause values	CATT	CR	Approval	Yes	No	available	No
		R3‑258338	Correction to A-IoT security information	CATT	CR	Approval	Yes	YesBIT STRING (SIZE(128)) mandatory E///: SA3 has reached clear decision on mandatory CB # 9_AIoTsecurity - check if SA3 has changed decision, if not CR will be agreed	noted	No
		R3‑258620	Correction on A-IoT security aspects	CMCC, Huawei	CR	Approval	Yes	YesBIT STRING (SIZE (128, ...)) optional Nok: prefer constrained size and optional Xmi: RAN2 has sent LS to SA3 about making it O	noted	No
		R3‑258619	Correction on A-IoT security aspects	CMCC, Huawei	draftCR	Approval	Yes	No	available	No
		R3‑258632	Correction on A-IoT Paging related information	ZTE Corporation,	CR	Approval	Yes	YesOCTET STRING optional	noted	No
		R3‑258241	Discussion on Device identifier privacy protection impact on RAN3	NEC	discussion	Agreement	Yes	YesIntroduce an Identifier Protection in the Inventory Request message. If the Identifier Protection is included in the Inventory Request message, the Reader will not include the device's permanent IDs in the Inventory Report message HW: outside RAN3 scope, does not impact RAN3 spec QC, ZTE: similar view as HW	noted	No
		R3‑258242	Correction on A-IoT device identifier privacy protection impact on RAN3	NEC	CR	Agreement	Yes	Yes	noted	No		R3‑256790
		R3‑258123	Correction on A-IoT related Network Identities	Huawei, Nokia, Ericsson, CMCC, China Unicom, China Telecom	draftCR	Agreement	Yes	YesQC: last bullet is not needed CATT: 2nd change is already covered in stage 3 Nok: last bullet is useful with further update - remove last bullet - add “as specified in TS 38.413” to first change	revised	No	R3‑258733
		R3‑258733	Correction on A-IoT related Network Identities	Huawei, Nokia, Ericsson, CMCC, China Unicom, China Telecom	draftCR	Agreement	Yes	Yes	endorsed	No		R3‑258123
		R3‑258124	Consideration on the presence of Reader Report List	Huawei, CMCC, China Unicom, China Telecom	discussion	Agreement	Yes	YesCATT, ZTE, SS, Nok, Xmi: support the change E///: do not support, we should not overload message with too many functions	noted	No
		R3‑258125	Correction on the presence of Reader Report List	Huawei, CMCC, China Unicom, China Telecom	CR	Agreement	Yes	Yes- remove “it was agreed that…” paragraph from cover page - add CATT, ZTE, Samsung, Nokia, Xiaomi as co-sources	revised	No	R3‑258735
		R3‑258735	Correction on the presence of Reader Report List	Huawei, CMCC, China Unicom, China Telecom, CATT, ZTE, Samsung, Nokia, Xiaomi	CR	Agreement	Yes	Yes	agreed	No		R3‑258125
		R3‑258185	Consideration on A-IoT Device Identification	Huawei, CMCC, China Unicom, China Telecom, Lenovo	discussion	Agreement	Yes	Yes	noted	No
		R3‑258186	Correction on A-IoT Device Identification	Huawei, CMCC, China Unicom, China Telecom, Lenovo	CR	Agreement	Yes	YesNok: current semantics are OK E///: reference should be to a stage 3 specification	noted	No
		R3‑258240	Correction on A-IoT Inventory and Command procedure figures	NEC	draftCR	Agreement	Yes	Yes- change “as defined in clause 16.23.6” to “as defined in clause 16.23.6 steps 1 to 6” - cover page: fix typos - add Nokia, Huawei as co-sources	revised	No	R3‑258736
		R3‑258736	Correction on A-IoT Inventory and Command procedure figures	NEC	draftCR	Agreement	Yes	Yes	endorsed	No		R3‑258240
		R3‑258595	Discussion on the encoding of AIOTF identifier	Samsung, Huawei, CMCC	discussion	Agreement	Yes	YesThe size of AIOTF Identifier IE is 16 octets ZTE: agree E///: “this is the binary representation …” with BIT STRING CB # 10_AIoTidentifer - further check encoding details, e.g. reference (Samsung - moderator)	noted	No
		R3‑258759	LS on the encoding of AIOTF Identifier	RAN3(Samsung)	LS out	Approval	Yes	Yes	approved	No
		R3‑258596	Correction to the encoding of AIOTF Identifier IE	Samsung, Huawei, CMCC	CR	Agreement	Yes	Yes	noted	No
		R3‑258407	Correction of Inventory Report	Nokia	CR		Yes	No	available	No
		R3‑258633	Correction on AIoT Reader Report List	ZTE Corporation	CR	Approval	Yes	Yes	merged	No
		R3‑258337	Correction to A-IoT specific cause values	CATT	CR	Approval	Yes	Yes	withdrawn	Yes
9.2.8	R19 Network Energy Saving	R3‑258150	Correction on procedural description of Cell A ID	ZTE Corporation, CATT, Samsung	CR	Approval	Yes	YesCMCC: repeats previous paragraph that already indicates “transmit” E///: could be clarified in Stage 2 CATT: should be clarified in Stage 3, 38.300 spec should be simpler, details belong in Stage 3 HW: procedure text should not describe when IE is not present QC: Stage 2 change would be agreeable (300 or 401) NEC: Proposed stage 3 text is not agreeable SS: Support this CR	noted	No
		R3‑258504	Addition of OAM support for on-demand SIB1	Ericsson, China Telecom, Jio Platforms, Lenovo	draftCR	Approval	Yes	Yes	noted	No
		R3‑258301	Correction on OD-SIB1 Configuration Provision Failure	CATT, ZTE, Samsung	CR	Approval	Yes	Yes	noted	No
		R3‑258254	Correction on inter-gNB Cell A indicator transfer	NEC, Nokia	CR	Agreement	Yes	YesCMCC: previously discussed, and agreed that capability is known via OAM ZTE: optimization (not essential) SS: CR is beneficial CATT: Not necessary to signal the capability (static) E///: agreed during WI phase that capability is provided by OAM, information is static	noted	No
		R3‑258423	Correction on OD-SIB1 failure cause	NEC, Rakuten	CR	Agreement	Yes	YesRakuten: adds value E///, SS, ZTE: existing “cell not available” can be reused Nok: cause value doesn’t really solve this scenario	noted	No
		R3‑258453	Corrections to OD-SIB1 Configuration Provision Status Update	Ericsson	CR	Agreement	Yes	YesHW: fine with rewording in 1st change. 2nd change not needed. ZTE: rewording is not needed, already clear CATT: 1st change is generally OK but could be refined QC: rewording is fine, also 2nd change is fine CMCC: support 1st change, 2nd change should only fix SIBxx	revised	No	R3‑258809	R3‑257091
		R3‑258809	Corrections to OD-SIB1 Configuration Provision Status Update	Ericsson, ZTE, Samsung	CR	Agreement	No	No	reserved	No		R3‑258453
		R3‑258503	Corrections to F1 support of Network Energy Saving Enhancement	Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten	CR	Approval	Yes	YesQC: agree, CR is essential ZTE, SS, HW: support CR Nokia: CU should coordinate with neighbors to cleanup - Add ZTE, Samsung, Huawei, Qualcomm, Telecom Italia, Deutsche Telekom to co-sources	revised	No	R3‑258743
		R3‑258743	Corrections to F1 support of Network Energy Saving Enhancement	Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten	CR	Approval	Yes	Yes	revised	No	R3‑258807	R3‑258503
		R3‑258807	Corrections to F1 support of Network Energy Saving Enhancement	Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten	CR	Approval	Yes	Yes	agreed	No		R3‑258743
		R3‑258280	Correction on Criticality in the OD-SIB1 Configuration Provision Response and Failure message	ZTE Corporation	CR	Approval	Yes	Yes	noted	No
		R3‑258402	Correction on Criticality in the OD-SIB1 Configuration Provision Status Update message	ZTE Corporation	CR	Approval	Yes	No	available	No
		R3‑258170	Correction of the NES Cell ID criticality in OD-SIB1 configuration provision response message	Huawei, CMCC, Deutsche Telekom, CATT	CR		Yes	No	available	No
		R3‑258374	Correction on assigned criticality for NES	Samsung	CR	Agreement	Yes	No	available	No
		R3‑258171	Correction of references of NES Cell and Cell A for OD-SIB1 configuration provision procedure	Huawei, CMCC, Deutsche Telekom, CATT	CR		Yes	Yes	noted	No
		R3‑258302	Corrections on termination of OD-SIB1 operation and status update	CATT, Huawei	CR	Approval	Yes	Yes	revised	No	R3‑258810	R3‑256765
		R3‑258810	Corrections on termination of OD-SIB1 operation and status update	CATT, Huawei, Ericsson, CMCC	CR	Approval	No	No	reserved	No		R3‑258302
		R3‑258502	Corrections to stage-2 specification for support for on-demand SIB1	Ericsson, Jio Platforms, China Telecom, Rakuten	CR	Agreement	Yes	No	available	No		R3‑257087
		R3‑258614	Correction on support for on-demand SIB1	CMCC, Huawei	CR	Approval	Yes	No	available	No
		R3‑258452	Corrections to TS 38.420 on support of Network Energy Saving Enhancement	Ericsson	CR	Agreement	Yes	YesHW, ZTE: should avoid changing legacy text	noted	No		R3‑257090
		R3‑258808	Summary of the offline discussion on CB # 11_Rel-19 Network Energy Saving	Ericsson	discussion	Approval	No	NoCB: # 11_FolderName - description of Cell A ID is absent and related O&M requirements, further discuss based on 8150, 8301 & 8504 - check 8453, refine wording of the 1st change, fix SIBxx, consider further semantics clarification if agreeable - fix criticalities, if needed, based on 8280, 8402, 8170, 8374 - check 38.401 cleanup, based on 8171, 8302, 8502, 8614	reserved	No
9.2.9	R19 Low Power WUS/WUR	R3‑258008	Reply LS on allocation of CN assigned subgroup ID for LP-WUS	SA2(Ericsson)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258524	CN assigned subgroup ID for LP-WUS	Ericsson	discussion	Discussion	Yes	Yes	noted	No
		R3‑258525	Clarification on allocation of CN assigned subgroup ID for LP-WUS	Ericsson	draftCR	Endorsement	Yes	No	available	No
		R3‑258526	DRAFT Reply LS on CN assigned subgroup ID for LP-WUS	Ericsson	LS out	Agreement	Yes	Yes	revised	No	R3‑258761
		R3‑258761	DRAFT Reply LS on CN assigned subgroup ID for LP-WUS	RAN3(Ericsson)	LS out	Agreement	Yes	No	available	No		R3‑258526
		R3‑258314	Discussion on allocation of CN assigned subgroup ID for LP-WUS	Huawei, Qualcomm, vivo	discussion		Yes	Yes	noted	No
		R3‑258315	Allocation of CN assigned subgroup ID for LP-WUS	Huawei, Qualcomm, vivo	draftCR		Yes	Yes	revised	No	R3‑258760
		R3‑258760	Allocation of CN assigned subgroup ID for LP-WUS	Huawei, Ericsson	draftCR	-	No	No	reserved	No		R3‑258315
		R3‑258316	[Draft] Reply LS on allocation of CN assigned subgroup ID for LP-WUS	Huawei, Qualcomm, vivo	LS out		Yes	No	available	No
		R3‑258382	Discussion on the reply LS on allocation of CN assigned subgroup ID for LP-WUS	ZTE Corporation	discussion	Decision	Yes	Yes	noted	No
		R3‑258383	[draft] Reply LS on allocation of CN assigned subgroup ID for LP-WUS	ZTE Corporation	other	Approval	Yes	No	available	No
		R3‑258303	On maximum number of subgroups and RAN paging	CATT	CR	Approval	Yes	Yes	withdrawn	Yes
		R3‑258410	Correction of LP-WUS	Nokia	CR	Agreement	Yes	YesAlready covered in 8059	noted	No
		R3‑258804	On maximum number of subgroups and RAN paging	CATT	draftCR	Endorsement	Yes	No	available	No
9.2.10	R19 Evolution of Duplex Operation	R3‑258549	Corrections on SBFD support	Ericsson	CR	Agreement	Yes	Yes	noted	No
		R3‑258637	Discussion on CLI Indication message structure	ZTE Corporation, Pengcheng Laboratory	discussion	Approval	Yes	Yes	noted	No
		R3‑258635	Correction to XnAP on CLI Indication	ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei	CR	Approval	Yes	Yes- Rename to CLI Measurement Result List - revise semantics as proposed in 8549 - Add Samsung, Qualcomm, Ericsson, Charter, Nokia, LG Electronics, CATT, CMCC	revised	No	R3‑258788	R3‑257162
		R3‑258788	Correction to XnAP on CLI Indication	ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei, Qualcomm, Samsung, Eircsson, Charter, Nokia, LGE, CATT, CMCC	CR	Approval	No	Yes	agreed	No		R3‑258635
		R3‑258636	Correction to F1AP on CLI Indication	ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei	CR	Approval	Yes	Yes- revise semantics in alignment with 8788 - Add Samsung, Qualcomm, Ericsson, Charter, Nokia, LG Electronics, CATT, CMCC	revised	No	R3‑258789	R3‑257163
		R3‑258789	Correction to F1AP on CLI Indication	ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei	CR	Approval	No	Yes	agreed	No		R3‑258636
		R3‑258647	Correction on SBFD RACH configuration for F1AP	CATT	CR	Approval	Yes	YesE///: SBFD Additional RACH Configuration is not needed, and “RACH configuration option 2” should be “dual configuration” SS, QC: SBFD Additional RACH Configuration is needed	revised	No	R3‑258835
		R3‑258835	Correction on SBFD RACH configuration for F1AP	CATT	CR	Approval	No	No	reserved	No		R3‑258647
		R3‑258686	Discussion on the open issues regarding L1 UE-to-UE CLI configuration	Samsung, Qualcomm, Charter	discussion	Agreement	Yes	YesIt should be DU that generates and compiles the CellGroupConfig, and CU only compiles the RRC message with the CellGroupConfig included as OCTET STRING. Include an indication for L1 UE-to-UE CLI configuration from DU to CU in the DU to CU RRC Information IE over F1. HW: It’s optimization, not essential QC: L1 and L3 should not be configured simultaneously and needed to avoid it ZTE, Nokia, CATT: CR is beneficial E///: solution does not ensure that L3 measurements are not configured, e.g. due to F1 delay. OAM solution is most reliable	noted	No
		R3‑258687	Correction on the indication of L1 UE-to-UE CLI	Samsung, Qualcomm, Charter	CR	Agreement	Yes	Yes	noted	No		R3‑256692
		R3‑258272	Revocation of NZP CSI-RS resources	Nokia	CR		Yes	YesHW: Don’t see any problem to solve, and proposal has issues. Aggressor can decide on its own whether to stop E///: “Revoke” can be achieved by removing configuration from message? CATT: similar view as E///, can be achieved by other means SS: Don’t see there is a big issue	noted	No
		R3‑258273	Revocation of NZP CSI-RS resources	Nokia	CR		Yes	No	available	No
		R3‑258607	Correction on Evolution of NR duplex operation for 38.420	CMCC, CATT	CR	Approval	Yes	No	available	No
		R3‑258639	Clarification to UE-to-UE CLI mitigation in SBFD operation	Huawei, CATT, China Unicom	draftCR	Approval	Yes	Yes	revised	No	R3‑258830
		R3‑258830	Clarification to UE-to-UE CLI mitigation in SBFD operation	Huawei, CATT, China Unicom	draftCR	Approval	No	No	reserved	No		R3‑258639
		R3‑258640	Clarification to CLI mitigation in SBFD operation	Huawei	CR	Approval	Yes	No	available	No		R3‑257177
		R3‑258802	Summary of the offline discussion on CB # 24_R19	CATT	discussion	Agreement	No	NoCB: # 24_R19 - Further discuss 8647, e.g. whether SBFD Additional RACH Configuration is needed - Further discuss benefits of 8686 - Check Stage 2 (38.420, 38.300, 38.401), whether agreeable	reserved	No
		R3‑258440	Corrections on SBFD support	Ericsson	CR	Agreement	Yes	Yes	withdrawn	Yes
		R3‑258500	Corrections on SBFD support	Ericsson	CR	Agreement	No	Yes	withdrawn	Yes
		R3‑258622	Correction to XnAP on CLI Indication	ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei	CR	Approval	No	Yes	withdrawn	Yes
		R3‑258623	Correction to F1AP on CLI Indication	ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei	CR	Approval	No	Yes	withdrawn	Yes
		R3‑258624	Correction to F1AP on SBFD RACH configuration	ZTE Corporation	CR	Approval	No	Yes	withdrawn	Yes
		R3‑258646	Correction on Evolution of NR duplex operation for 38.470	CATT	CR	Approval	Yes	Yes	withdrawn	Yes
9.2.11	R19 AI/ML for air interface	R3‑258004	Reply LS on AI/ML Positioning Case 3a	SA2(CATT)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258142	Discussion on the reply LS on AI/ML assisted positioning	ZTE Corporation, Ericsson, Xiaomi, CATT	discussion		Yes	YesIntroduce the new codepoint "no user consent" in the Positioning Data Unavailable IE	noted	No
		R3‑258143	Correction on Positioning Data Unavailable IE	ZTE Corporation, Ericsson, Xiaomi, CATT	CR		Yes	Yes	noted	No
		R3‑258480	Discussion on the Reply LS from SA2 on AI/ML Positioning Case 3a	Huawei, Nokia, Qualcomm, Samsung	discussion	Decision	Yes	Yes	noted	No
		R3‑258700	Response to R3-258480	Ericsson	response		Yes	Yes	noted	No
		R3‑258174	Clarification of procedural text for POSITIONING DATA COLLECTION REPORT message	Nokia, CATT, Ericsson	CR		Yes	Yes	revised	No	R3‑258793
		R3‑258793	Clarification of procedural text for POSITIONING DATA COLLECTION REPORT message	Nokia, CATT, Ericsson	CR	-	No	Yes	agreed	No		R3‑258174
		R3‑258238	Correction on positioning data collection for assisting in the pairing with the TRP's measurement.	NEC	CR	Decision	Yes	Yes	noted	No
		R3‑258527	Correction of Data Collection Report procedure and others	Ericsson, Huawei, Nokia, Xiaomi, ZTE, CATT, NEC, Samsung, Qualcomm Inc., CEWiT	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258795
		R3‑258795	Correction of Data Collection Report procedure and others	Ericsson, Huawei, Nokia, Xiaomi, ZTE, CATT, NEC, Samsung, Qualcomm Inc., CEWiT	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258527
		R3‑258479	[Draft] LS on definition of “ground truth label” in AI/ML-based Positioning Case 3a	Huawei, Ericsson, Nokia	LS out	Agreement	Yes	Yes	revised	No	R3‑258796
		R3‑258796	[Draft] LS on definition of “ground truth label” in AI/ML-based Positioning Case 3a	Huawei, Ericsson, Nokia	LS out	Agreement	Yes	Yes	approved	No		R3‑258479
9.2.12	R19 NR XR Enhancements	R3‑258009	LS Reply on uplink rate control	SA2(vivo)	LS in	Discussion	Yes	Yes	noted	No
		R3‑258201	Add the missing behavior text for the MMSID IE and the Indication of Bitrate Adaptation IE	Nokia, Nokia Shanghai Bell, Ericsson, Ofinno, China Telecom, Qualcomm, ZTE, Samsung, Huawei, Lenovo	CR	Agreement	Yes	Yes	agreed	No
		R3‑258332	Correction on multi-modality, uplink rate control and available bit rate monitoring	Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Ofinno, ZTE, Lenovo	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258797
		R3‑258797	Correction on multi-modality, uplink rate control and available bit rate monitoring	Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Ofinno, ZTE, Lenovo	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258332
		R3‑258375	Correction on Burst Size for XR	Samsung	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258798
		R3‑258798	Correction on Burst Size for XR	Samsung	draftCR	Endorsement	No	Yes	endorsed	No		R3‑258375
		R3‑258615	Corrections on uplink rate control	CMCC	CR	Agreement	Yes	Yes	noted	No
		R3‑258625	Correction on semantic description for Notification Cause IE in NGAP	ZTE Corporation	CR	Approval	No	Yes	withdrawn	Yes
		R3‑258626	Correction on stage 3 description on Indication of Bitrate Adaptation IE in NGAP	ZTE Corporation, Nokia, Nokia Shanghai Bell,CATT, Qualcomm, Huawei, Ericsson,	CR	Approval	No	Yes	withdrawn	Yes
		R3‑258627	Discussion on UL Rate Control on XR with the correction and draft LS	ZTE Corporation	discussion	Approval	No	Yes	withdrawn	Yes
9.2.13	R19 NR Sidelink Multi-hop Relay
9.2.14	Other	R3‑258220	Correction of time-based handover for NR NTN	Huawei, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, Samsung	draftCR	Endorsement	Yes	No	available	No
		R3‑258221	Correction of time-based handover for NR NTN	Huawei, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, Samsung	draftCR	Endorsement	Yes	No	available	No
		R3‑258343	Avoiding paging capability loss after handover resource allocation and path switch request procedure	Huawei, China Unicom, China Telecom, CATT	CR		Yes	Yes	noted	No		R3‑256816
		R3‑258344	Avoiding paging capability loss after handover resource allocation and path switch request procedure	Huawei, China Unicom, China Telecom, CATT	CR		Yes	No	available	No		R3‑256817
		R3‑258345	Avoiding paging capability loss after handover resource allocation and path switch request procedure	Huawei, China Unicom, China Telecom, CATT	CR		Yes	No	available	No		R3‑256818
		R3‑258346	Avoiding paging capability loss after handover resource allocation and path switch request procedure	Huawei, China Unicom, China Telecom	draftCR		Yes	Yes	noted	No		R3‑256819
		R3‑258347	Avoiding paging capability loss after handover resource allocation and path switch request procedure	Huawei, China Unicom, China Telecom	draftCR		Yes	No	available	No		R3‑256820
		R3‑258348	Avoiding paging capability loss after handover resource allocation and path switch request procedure	Huawei, China Unicom, China Telecom	draftCR		Yes	No	available	No		R3‑256821
		R3‑258349	[Draft] Reply LS on paging capability loss issue	Huawei, China Unicom, China Telecom	LS out	Approval	Yes	Yes	revised	No	R3‑258723
		R3‑258723	Reply LS on paging capability loss issue	RAN3(Huawei)	LS out	Approval	Yes	Yes	revised	No	R3‑258831	R3‑258349
		R3‑258831	Reply LS on paging capability loss issue	RAN3(Huawei)	LS out	Approval	No	Yes	approved	No		R3‑258723
		R3‑258394	Paging capability loss in RAN	Vodafone	CR	Agreement	Yes	Yes	noted	No
		R3‑258401	Paging capability loss in RAN	Vodafone Ireland Plc	CR	Agreement	Yes	No	available	No
		R3‑258403	Paging capability loss in RAN	Vodafone Ireland Plc	CR	Agreement	Yes	No	available	No
		R3‑258534	Correction on Paging Loss issue	Ericsson	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258752
		R3‑258752	Correction on Paging Loss issue	Ericsson, Nokia, Huawei, CATT	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258534
		R3‑258535	Correction on Paging Loss issue	Ericsson	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258753
		R3‑258753	Correction on Paging Loss issue	Ericsson, Nokia	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258535
		R3‑258536	Correction on Paging Loss issue	Ericsson	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258754
		R3‑258754	Correction on Paging Loss issue	Ericsson, Nokia	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258536
		R3‑258537	[DRAFT] Reply LS on Response to Reply LS on paging capability loss issue	Ericsson	LS out	Agreement	Yes	No	available	No
		R3‑258304	Correction of URCP for RAN paging	CATT	CR	Approval	Yes	Yes	revised	No	R3‑258755
		R3‑258755	Correction of URCP for RAN paging	CATT, Huawei	CR	Approval	Yes	Yes	agreed	No		R3‑258304
		R3‑258305	Correction of URCP for RAN paging	CATT	CR	Approval	Yes	Yes	revised	No	R3‑258756
		R3‑258756	Correction of URCP for RAN paging	CATT, Huawei	CR	Approval	Yes	Yes	agreed	No		R3‑258305
		R3‑258306	Correction of URCP for RAN paging	CATT	CR	Approval	Yes	Yes	revised	No	R3‑258757
		R3‑258757	Correction of URCP for RAN paging	CATT, Huawei	CR	Approval	Yes	Yes	agreed	No		R3‑258306
		R3‑258106	Additional procedure text for Data Collection Update	ZTE Corporation, Ercisson, Samsung, NEC, Nokia, Huawei, CATT, Jio Platforms, Qualcomm, FiberCop, Orange	CR	Agreement	Yes	Yes	revised	No	R3‑258724	R3‑256563
		R3‑258724	Additional procedure text for Data Collection Update	ZTE Corporation, Ercisson, Samsung, NEC, Nokia, Huawei, CATT, Jio Platforms, Qualcomm, FiberCop, Orange	CR	Agreement	Yes	Yes	agreed	No		R3‑258106
		R3‑258118	Specifying procedure texts for the Core Network Assistance Information for RRC INACTIVE IE	Huawei, Ericsson, Nokia, ZTE	CR	Agreement	Yes	Yes	agreed	No		R3‑256682
		R3‑258299	Correction on the description of UE Context Information – Retrieve UE Context Response	ZTE Corporation, Nokia, Huawei, CATT, Samsung	CR	Agreement	Yes	Yes	revised	No	R3‑258725	R3‑256564
		R3‑258725	Correction on the description of UE Context Information – Retrieve UE Context Response	ZTE Corporation, Nokia, Huawei, CATT, Samsung	CR	Agreement	Yes	Yes	agreed	No		R3‑258299
		R3‑258486	Extensions for enumerated type definitions over several Releases - and what can go wrong	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	discussion	Discussion	Yes	Yes	noted	No
		R3‑258701	Response to R3-258486	Huawei	response	Discussion	Yes	Yes	noted	No
		R3‑258487	Correcting the extension of FR1-bandwidth type definition	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	revised	No	R3‑258737	R3‑256996
		R3‑258737	Correcting the extension of FR1-bandwidth type definition	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes[MCC] Issues should be fixed from the release where the was introduced.	agreed	No		R3‑258487
		R3‑258488	Correcting the extension of FR1-bandwidth type definition	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	revised	No	R3‑258738	R3‑256997
		R3‑258738	Correcting the extension of FR1-bandwidth type definition	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	agreed	No		R3‑258488
		R3‑258489	Correcting the IE extension definition for bandwidth SRS	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	revised	No	R3‑258739	R3‑256998
		R3‑258739	Correcting the IE extension definition for bandwidth SRS	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	agreed	No		R3‑258489
		R3‑258490	Correcting the IE extension definition for bandwidth SRS	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	revised	No	R3‑258740	R3‑256999
		R3‑258740	Correcting the IE extension definition for bandwidth SRS	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	agreed	No		R3‑258490
		R3‑258491	Correcting the IE extension definition for SRS Pos SIB Type	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	revised	No	R3‑258741	R3‑257000
		R3‑258741	Correcting the IE extension definition for SRS Pos SIB Type	Ericsson, Jio Platforms, China Telecom, CMCC, Nokia	CR	Agreement	Yes	Yes	agreed	No		R3‑258491
		R3‑258528	Addition of PDCP discard timer for scheduling with DSR	Ericsson, Qualcomm Inc., Jio Platforms	CR	Agreement	Yes	Yes	noted	No		R3‑257037
		R3‑258529	Addition of PDCP discard timer for scheduling with DSR	Ericsson, Qualcomm Inc., Jio Platforms	CR	Agreement	Yes	No	available	No		R3‑257039
		R3‑258658	Clarification for propagation of roaming and access restrictions	Samsung	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258726
		R3‑258726	Clarification for propagation of roaming and access restrictions	Samsung	draftCR	Endorsement	No	Yes	endorsed	No		R3‑258658
		R3‑258670	R18 correction (SSB) on the CU-DU Mobility Initiation Request message	Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC	CR	Agreement	Yes	Yes	revised	No	R3‑258728	R3‑256859
		R3‑258728	Correction (SSB) on the CU-DU Mobility Initiation Request message	Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC	CR	Agreement	Yes	Yes	agreed	No		R3‑258670
		R3‑258671	R18 correction (SSB) on the CU-DU Mobility Initiation Request message	Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC	CR	Agreement	Yes	Yes	revised	No	R3‑258729	R3‑256860
		R3‑258729	Correction (SSB) on the CU-DU Mobility Initiation Request message	Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC	CR	Agreement	Yes	Yes	agreed	No		R3‑258671
		R3‑258675	Clarify on UE context retrieval	ZTE Corporation	discussion		Yes	Yes	noted	No
		R3‑258674	Clarification for propagation of MDT Configuration in stage2	ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei	other		Yes	Yes	revised	No	R3‑258727	R3‑256527
		R3‑258727	Clarification for propagation of MDT Configuration in stage2	ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258816	R3‑258674
		R3‑258816	Clarification for propagation of MDT Configuration in stage2	ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258727
		R3‑258790	Clarification for propagation of MDT Configuration in stage2	ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei	draftCR	Endorsement	Yes	Yes	revised	No	R3‑258817
		R3‑258817	Clarification for propagation of MDT Configuration in stage2	ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑258790
		R3‑258094	Correction of Transmission Bandwidth Asymmetric	Nokia, Huawei, Qualcomm, China Telecom	CR	Agreement	Yes	Yes	noted	No		R3‑256566
		R3‑258095	Correction of Transmission Bandwidth Asymmetric	Nokia, Huawei, Qualcomm, China Telecom	CR	Agreement	Yes	No	available	No		R3‑256567
		R3‑258096	Correction of Transmission Bandwidth Asymmetric	Nokia, Huawei, Qualcomm, China Telecom	CR	Agreement	Yes	No	available	No		R3‑256568
		R3‑258097	Correction of Transmission Bandwidth Asymmetric	Nokia, Huawei, Qualcomm, China Telecom	CR	Agreement	Yes	No	available	No		R3‑256569
		R3‑258098	Correction of Transmission Bandwidth Asymmetric	Nokia, Huawei, Qualcomm, China Telecom	CR	Agreement	Yes	No	available	No		R3‑256570
		R3‑258099	Correction of Transmission Bandwidth Asymmetric	Huawei, Nokia, Qualcomm, China Telecom	CR		Yes	No	available	No		R3‑256669
		R3‑258100	Correction of Transmission Bandwidth Asymmetric	Huawei, Nokia, Qualcomm, China Telecom	CR		Yes	No	available	No		R3‑256670
		R3‑258101	Correction of Transmission Bandwidth Asymmetric	Huawei, Nokia, Qualcomm, China Telecom	CR		Yes	No	available	No		R3‑256671
		R3‑258102	Correction of Transmission Bandwidth Asymmetric	Huawei, Nokia, Qualcomm, China Telecom	CR		Yes	No	available	No		R3‑256672
		R3‑258103	Correction of Transmission Bandwidth Asymmetric	Huawei, Nokia, Qualcomm, China Telecom	CR		Yes	No	available	No		R3‑256673
		R3‑258162	Discussion on AQP priority	ZTE Corporation, Nokia, Ericsson, Huawei	discussion	Approval	Yes	Yes	noted	No
		R3‑258163	Correction on prioritized alternative QoS profile	ZTE Corporation, Nokia, Ericsson, Huawei	CR	Approval	Yes	Yes	noted	No
		R3‑258164	Correction on prioritized alternative QoS profile	ZTE Corporation, Nokia, Ericsson, Huawei	CR	Approval	Yes	Yes	noted	No
		R3‑258165	Correction on prioritized alternative QoS profile	ZTE Corporation, Nokia, Ericsson, Huawei	CR	Approval	Yes	Yes	noted	No
		R3‑258166	Correction on prioritized alternative QoS profile	ZTE Corporation, Nokia, Ericsson, Huawei	CR	Approval	Yes	Yes	noted	No
		R3‑258222	Correction on prioritized alternative QoS profile	Ericsson, ZTE Corporation, Huawei, Nokia	CR	Agreement	Yes	No	available	No
		R3‑258223	Correction on prioritized alternative QoS profile	Ericsson, ZTE Corporation, Huawei, Nokia	CR	Agreement	Yes	No	available	No
		R3‑258224	Correction on prioritized alternative QoS profile	Ericsson, ZTE Corporation, Huawei, Nokia	CR	Agreement	Yes	No	available	No
		R3‑258225	Correction on prioritized alternative QoS profile	Ericsson, ZTE Corporation, Huawei, Nokia	CR	Agreement	Yes	No	available	No
		R3‑258227	Correction on prioritized alternative QoS profile	Nokia, Ericsson, ZTE Corporation, Huawei	CR		Yes	No	available	No
		R3‑258228	Correction on prioritized alternative QoS profile	Nokia, Ericsson, ZTE Corporation, Huawei	CR		Yes	No	available	No
		R3‑258230	Correction on prioritized alternative QoS profile	Nokia, Ericsson, ZTE Corporation, Huawei	CR		Yes	No	available	No
		R3‑258231	Correction on prioritized alternative QoS profile	Nokia, Ericsson, ZTE Corporation, Huawei	CR		Yes	No	available	No
		R3‑258276	Correction on prioritized alternative QoS profile	Huawei, ZTE, Ericsson, Nokia	CR		Yes	No	available	No
		R3‑258277	Correction on prioritized alternative QoS profile	Huawei, ZTE, Ericsson, Nokia	CR	Agreement	Yes	No	available	No
		R3‑258278	Correction on prioritized alternative QoS profile	Huawei, ZTE, Ericsson, Nokia	CR	Agreement	Yes	No	available	No
		R3‑258279	Correction on prioritized alternative QoS profile	Huawei, ZTE, Ericsson, Nokia	CR	Agreement	Yes	No	available	No
		R3‑258167	Correction on Configured TAC	Huawei, China Unicom, China Telecom, Lenovo	CR	Agreement	Yes	No	available	No
		R3‑258202	Correction on Notification Control Indication	Nokia, Nokia Shanghai Bell, Huawei, CMCC, China Telecom	CR		Yes	No	available	No		R3‑256892
		R3‑258203	Correction on Notification Control Indication	Nokia, Nokia Shanghai Bell, Huawei, CMCC, China Telecom	CR		Yes	No	available	No		R3‑256893
		R3‑258211	Beam measurement report quantity	Huawei, Ericsson, Nokia, ZTE	CR		Yes	No	available	No
		R3‑258212	Beam measurement report quantity	Huawei, Ericsson, Nokia, ZTE	CR		Yes	No	available	No
		R3‑258213	Beam measurement report quantity	Huawei, Ericsson, Nokia, ZTE	CR		Yes	No	available	No
		R3‑258261	Beam measurement report quantity	Ericsson, Jio Platforms, Huawei, Nokia, ZTE	CR		Yes	No	available	No
		R3‑258260	Beam measurement report quantity	Ericsson, Jio Platforms, Huawei, Nokia, ZTE	CR		Yes	No	available	No
		R3‑258259	Beam measurement report quantity	Ericsson, Jio Platforms, Huawei, Nokia, ZTE	CR		Yes	No	available	No
		R3‑258217	Correction on procedural text for Coverage and Capacity Optimization	ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom	CR		Yes	No	available	No
		R3‑258218	Correction on procedural text for Coverage and Capacity Optimization	ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom	CR		Yes	No	available	No
		R3‑258219	Correction on procedural text for Coverage and Capacity Optimization	ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom	CR		Yes	No	available	No
		R3‑258295	Correction on load measurement function	ZTE Corporation, Jio Platforms, China Unicom, China Telecom	CR		Yes	No	available	No
		R3‑258296	Correction on load measurement function	ZTE Corporation, Jio Platforms, China Unicom, China Telecom	CR		Yes	No	available	No
		R3‑258297	Correction on load measurement function	ZTE Corporation, Jio Platforms, China Unicom, China Telecom	CR		Yes	No	available	No
		R3‑258333	Correction on QoS parameters for QoS Notification Control	Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CMCC	draftCR		Yes	No	available	No		R3‑256804
		R3‑258334	Correction on QoS parameters for QoS Notification Control	Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CMCC	draftCR		Yes	No	available	No		R3‑256805
		R3‑258384	Correction on the Extended UE Identity Index Value for PEI	ZTE Corporation, CATT, China Telecom	draftCR	Approval	Yes	No	available	No
		R3‑258307	Correction on Extended UE Identity Index Value for PEI	CATT, ZTE, China Telecomm	draftCR	Approval	Yes	No	available	No
		R3‑258308	Correction on Extended UE Identity Index Value for PEI	CATT, ZTE, China Telecomm	draftCR	Approval	Yes	No	available	No
		R3‑258396	Rel-17 Introduction of IAB-related Definitions	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑258397	Rel-18 Introduction of IAB-related Definitions	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑258398	Rel-19 Introduction of IAB-related Definitions	Ericsson	CR	Agreement	Yes	No	available	No
		R3‑258406	Discussion on TNLA handling during Xn handover	NTT DOCOMO INC..	discussion		Yes	No	available	No
		R3‑258408	Clarification on TNLA handling during Xn handover	NTT DOCOMO	CR	Agreement	Yes	No	available	No		R3‑257134
		R3‑258411	Clarification on TNLA handling during Xn handover	NTT DOCOMO	CR	Agreement	Yes	No	available	No		R3‑257135
		R3‑258413	Clarification on TNLA handling during Xn handover	NTT DOCOMO	CR	Agreement	Yes	No	available	No		R3‑257136
		R3‑258414	Clarification on TNLA handling during Xn handover	NTT DOCOMO	CR	Agreement	Yes	No	available	No		R3‑257137
		R3‑258412	Correction of Served PLMN	Nokia	CR		Yes	No	available	No
		R3‑258429	SRB ID correction	Ericsson, Jio Platforms, Nokia	CR	Approval	Yes	No	available	No
		R3‑258430	SRB ID correction	Ericsson, Jio Platforms, Nokia	CR	Agreement	Yes	No	available	No
		R3‑258451	Discussion on UL data forwarding	CATT,Huawei	discussion	Decision	Yes	No	available	No
		R3‑258464	UE Retention in NG-RAN	Ericsson, Huawei, Jio Platforms, Thales	discussion	Discussion	Yes	No	available	No
		R3‑258465	UE Context Retention for NG - Stage 2	Ericsson, Huawei, Jio Platforms, Thales	draftCR	Endorsement	Yes	No	available	No
		R3‑258470	UE Context Retention for NG - Stage 2	Ericsson, Huawei, Jio Platforms, Thales	draftCR	Endorsement	Yes	No	available	No
		R3‑258493	Correction on ETA resource release in DU	Ofinno, Ericsson	CR	Agreement	Yes	No	available	No		R3‑257036
		R3‑258494	Correction on ETA resource release in DU	Ofinno, Ericsson	CR	Agreement	Yes	No	available	No		R3‑257117
		R3‑258495	LTM Resource consumption for the target cells	SONY, Ericsson, vivo, Jio Platforms, LG Electronics	discussion		Yes	No	available	No
		R3‑258496	Correction for Cell Switch execution	SONY, Ericsson, vivo, Jio Platforms, LG Electronics	draftCR		Yes	No	available	No
		R3‑258506	Correction on the UE Initial Access procedure	Ericsson	CR	Agreement	Yes	No	available	No		R3‑252063
		R3‑258507	Correction on the UE Initial Access procedure	Ericsson	CR	Agreement	Yes	No	available	No		R3‑252064
		R3‑258511	Correction on the UE Initial Access procedure	Ericsson	CR	Agreement	Yes	No	available	No		R3‑252065
		R3‑258512	Correction on the UE Initial Access procedure	Ericsson	CR	Agreement	Yes	No	available	No		R3‑252068
		R3‑258513	Correction on the UE Initial Access procedure	Ericsson	CR		Yes	No	available	No
		R3‑258530	Addition of 2Rx XR UE Capability	Ericsson, Qualcomm inc. Nokia, Nokia Shanghai Bell, ZTE	CR	Agreement	Yes	No	available	No		R3‑257013
		R3‑258531	Addition of 2Rx XR UE Capability	Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, ZTE	CR	Agreement	Yes	No	available	No		R3‑257014
		R3‑258562	Correction for Cell Switch execution	Ericsson, Sony, Jio Platforms, LG Electronics, vivo, Qualcomm	CR	Agreement	Yes	No	available	No		R3‑257028
		R3‑258563	Correction for Cell Switch execution	Ericsson, Sony, Jio Platforms, LG Electronics, vivo, Qualcomm	CR	Agreement	Yes	No	available	No		R3‑257029
		R3‑258676	Correction on UHI	ZTE Corporation,China Telecom, Pengcheng Laboratory	CR		Yes	No	available	No		R3‑256753
		R3‑258677	Correction on UHI	ZTE Corporation,China Telecom, Pengcheng Laboratory	CR		Yes	No	available	No		R3‑256754
		R3‑258692	Connection of Secondary RAT Data Usage Report for NG based handover	Huawei, China Unicom, China Telecom	CR		Yes	No	available	No		R3‑257182
		R3‑258693	Connection of Secondary RAT Data Usage Report for Xn based handover	Huawei, China Unicom, China Telecom	CR		Yes	No	available	No		R3‑257183
		R3‑258111	Introduction of NR TA Type 1 measurement in NR E-CID	Comtech Telecommunications Corp, Polaris Wireless, FirstNet, Verizon	discussion	Decision	Yes	No	available	No
		R3‑258112	Add Tadv Type 1 measurement in NR UL E-CID	Comtech Telecommunications Corp, Polaris Wireless, FirstNet, Verizon	CR	Agreement	Yes	No	available	No
9.3	R19 Rapporteur Corrections	R3‑258205	Rapporteur corrections	Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	noted	No
		R3‑258206	Rapporteur corrections	Nokia, Nokia Shanghai Bell	CR		Yes	Yes	noted	No
		R3‑258210	Correction on the reference to TS 36.331 IEs	Nokia, Nokia Shanghai Bell	CR	Agreement	Yes	Yes	noted	No		R3‑257226
		R3‑258404	Rapporteur correction of TS 38.410	Nokia	CR	Agreement	Yes	Yes	revised	No	R3‑258718
		R3‑258718	Rapporteur correction of TS 38.410	Nokia	CR	Agreement	No	No	reserved	No		R3‑258404
		R3‑258405	Rapporteur correction of TS 38.415	Nokia	CR	Agreement	Yes	Yes	revised	No	R3‑258719
		R3‑258719	Rapporteur correction of TS 38.415	Nokia	CR	Agreement	No	No	reserved	No		R3‑258405
		R3‑258443	Rapporteur Corrections	Huawei	CR	Agreement	Yes	Yes	noted	No		R3‑256965
		R3‑258461	Rapporteur Corrections	Huawei	CR	Agreement	Yes	Yes	noted	No
		R3‑258492	X2AP rapporteur corrections	Ericsson	CR		Yes	Yes	revised	No	R3‑258720
		R3‑258720	X2AP rapporteur corrections	Ericsson	CR	-	Yes	No	available	No		R3‑258492
		R3‑258532	NRPPa Rapporteur Corrections	Rapporteur (Ericsson)	CR	Agreement	Yes	Yes	revised	No	R3‑258721
		R3‑258721	NRPPa Rapporteur Corrections	Rapporteur (Ericsson)	CR	Agreement	Yes	No	available	No		R3‑258532
		R3‑258542	Rapporteur Rel-19 Corrections	Ericsson	CR	Agreement	Yes	Yes	revised	No	R3‑258722
		R3‑258722	Rapporteur Rel-19 Corrections	Ericsson	CR	Agreement	Yes	No	available	No		R3‑258542
		R3‑258566	Rapporteur's editorial corrections for E1AP	Ericsson	CR	Agreement	Yes	Yes	revised	No	R3‑258827	R3‑257120
		R3‑258827	Rapporteur's editorial corrections for E1AP	Ericsson	CR	Agreement	Yes	No	available	No		R3‑258566
		R3‑258204	Rapporteur update	Nokia, Nokia Shanghai Bell	CR		No	Yes	withdrawn	Yes
9.4	Endorsed CRs Review	R3‑258016	Correction on UE Performance metrics	Huawei, FiberCop, BT, Jio Platforms, NEC, ZTE, Samsung, CATT, Ericsson, Nokia, CMCC	CR	Agreement	Yes	Yes	agreed	No		R3‑257302
		R3‑258017	Correction on UE Performance metrics	Huawei, FiberCop, BT, Jio Platforms, NEC, ZTE, Samsung, CATT, Ericsson, Nokia, CMCC	CR	Agreement	Yes	Yes	agreed	No		R3‑257303
		R3‑258018	Clarification on S1 Removal for IoT NTN	ZTE Corporation, LG Electronics, Ericsson, CMCC, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Deutsche Telekom, Jio Platforms	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑257199
		R3‑258019	Correction on the MME Name IE in the S1 REMOVAL RESPONSE message	Nokia, Nokia Shanghai Bell, Xiaomi, Qualcomm, Ericsson, CATT, Airbus, Jio Platforms, ZTE, LG Electronics, Huawei	CR	Agreement	Yes	Yes	agreed	No		R3‑257200
		R3‑258020	Provision of S&F Mode Indication Information	Huawei, Deutsche Telekom, Jio Platforms, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, CATT, ZTE, CMCC, NEC	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑257201
		R3‑258021	Correction of Time Interleaving parameters	ZTE Corporation, Pengcheng Laboratory, China Unicom, China Telecom	CR	Agreement	Yes	Yes	agreed	No		R3‑257202
		R3‑258022	Correction of time-based handover for IoT NTN	Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics	draftCR	Endorsement	Yes	Yes	endorsed	No		R3‑257214

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

Consensus Principles

2.4

Responsible IT Behavior

2.5

Additional reminders

Approval of the Agenda

R3‑258001

RAN3#130 Meeting Agenda

RAN3 Chair

agenda

Approval

Yes

approved

Approval of the minutes from previous meetings

R3‑258002

RAN3#129-bis Meeting Report

ETSI-MCC

report

Approval

Yes

approved

Documents for immediate consideration

Organizational topics

General, protocol principles and issues

R3‑258003

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

ETSI-MCC

draft TR

Endorsement

Yes

endorsed

Incoming LSs

8.1

New Incoming LSs

R3‑258006

Reply LS on the handling of inter-DU L2 reset for LTM

RAN2(Ericsson)

LS in

Discussion

Yes

noted

R3‑258385

Corrections on L2 reset for LTM

ZTE Corporation

Approval

Yes

noted

R3‑258386

Corrections on L2 reset for LTM

ZTE Corporation

Approval

Yes

available

R3‑258387

Corrections on L2 reset for LTM

ZTE Corporation

Approval

Yes

available

R3‑258388

Corrections on L2 reset for LTM

ZTE Corporation

Approval

Yes

available

R3‑258007

LS Response on compatibility issue for PEI and emergency PDU session

SA2(ZTE)

LS in

Discussion

Yes

noted

R3‑258379

Discussion on LS Response on compatibility issue for PEI and emergency PDU session

ZTE Corporation

discussion

Decision

Yes

noted

R3‑258415

Handling of emergency PDU session and PEI

Nokia

discussion

Yes

noted

R3‑258420

Reply LS on compatibility issue for PEI and emergency PDU session

Nokia

LS out

Yes

available

R3‑258538

On Restriction of PEIPS during emergency PDU session

Ericsson

discussion

Discussion

Yes

noted

R3‑258539

Correction on PEIPS

Ericsson

Agreement

Yes

noted

R3‑258540

Correction on PEIPS

Ericsson

Agreement

Yes

available

R3‑258541

Correction on PEIPS

Ericsson

Agreement

Yes

available

R3‑258574

Finalizing the compatibility issue for PEI and emergency PDU session

Huawei

discussion

Yes

noted

R3‑258575

PEI usage in case of emergency PDU session

Huawei

draftCR

Yes

noted

R3‑258576

PEI usage in case of emergency PDU session

Huawei

draftCR

Yes

available

R3‑258577

PEI usage in case of emergency PDU session

Huawei

draftCR

Yes

available

R3‑258010

Reply to Reply LS on removal of support of PWS over satellite NG-RAN in Rel-17 and 18

SA2(Samsung)

LS in

Discussion

Yes

noted

R3‑258105

Discussion on R17 and R18 PWS for NTN feature removal alignment between RAN and SA

ZTE Corporation

discussion

Yes

noted

R3‑258466

Discussion on removal of support of PWS over satellite NG-RAN in Rel-17 and Rel-18

Huawei

discussion

Agreement

Yes

noted

R3‑258467

Correction of PWS support for IoT NTN

Huawei

draftCR

Endorsement

Yes

available

R3‑258468

Correction of PWS support for IoT NTN

Huawei

draftCR

Endorsement

Yes

available

R3‑258469

Reply LS on removal of support of PWS for NR NTN and IoT NTN in Rel-17 and 18

Huawei

LS out

Agreement

Yes

available

R3‑258013

Reply LS on UE data collection and data transfer

RAN2(Nokia)

LS in

Discussion

Yes

noted

R3‑258014

Reply LS on signalling feasibility of dataset and parameter sharing

RAN2(Samsung)

LS in

Discussion

Yes

noted

R3‑258015

Reply LS on temporary suspension of trace production

RAN2(Ericsson)

LS in

Discussion

Yes

noted

R3‑258104

LS on Rel-19 higher layers parameters list Post RAN1#122bis

RAN1(Ericsson)

LS in

Discussion

Yes

noted

R3‑258258

Progress of ETSI ISG ISAC Work Items

ETSI ISG ISAC(Interdigital)

LS in

Discussion

Yes

noted

R3‑258699

LS on DTLS for SCTP Progress Report

IETF Transport and Services WG(TSVWG)(Huawei)

LS in

Discussion

Yes

noted

R3‑258628

Discussion on average window for alternative QoS

ZTE Corporation

discussion

Approval

withdrawn

Yes

8.2

LSin received during the meeting

R3‑258766

LS on the signalling design of SCG LTM related parameters

RAN2(ZTE)

LS in

discussion

Yes

noted

R3‑258794

Reply to Reply LS on removal of support of PWS over satellite NG-RAN in Rel-17 and 18

SA2(Samsung)

LS in

discussion

Yes

noted

8.3

Left over LSs / pending actions

Corrections to Rel-19 or earlier releases

9.1

LTE

9.1.1

R19 IoT NTN enhancements

R3‑258091

LS to SA2 on the paging in Store and Forward

RAN2(Huawei)

LS in

Discussion

Yes

noted

R3‑258644

Discussion on paging in Store and Forward

ZTE Corporation

discussion

Discussion

Yes

noted

R3‑258199

Correction on the OAM requirements for NTN

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

draftCR

Yes

revised

R3‑258704

Correction on the OAM requirements for NTN

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

draftCR

Endorsement

Yes

endorsed

R3‑258199

R3‑258485

Inter-Satellite Links and Transparent Payloads - IoT NTN

Ericsson, Aalyria, Thales, Airbus

draftCR

Endorsement

Yes

available

9.1.2

R19 LTE-based 5G Broadcast

R3‑258127

Correction on LTE-based 5G Broadcast

Huawei, EBU, Qualcomm Incorporated, ZTE

Agreement

Yes

revised

R3‑258705

Correction on LTE-based 5G Broadcast

Huawei, EBU, Qualcomm Incorporated, ZTE

Agreement

Yes

revised

R3‑258742

R3‑258127

R3‑258742

Correction on LTE-based 5G Broadcast

Huawei, EBU, Qualcomm Incorporated, ZTE

Agreement

Yes

agreed

R3‑258705

9.1.3

Other

9.2

9.2.1

R19 SON/MDT

R3‑258515

Clarifying the MRO for LTM use-case

Ericsson

Agreement

Yes

noted

R3‑258516

BFR in CSI-RS beam

Ericsson

Agreement

Yes

revised

R3‑258707

BFR in CSI-RS beam

Ericsson

Agreement

Yes

agreed

R3‑258516

R3‑258149

Correction on MRO for SCG failure in EN-DC

ZTE Corporation, China Telecom, Pengcheng Laboratory

draftCR

Endorsement

Yes

revised

R3‑258708

Correction on MRO for SCG failure in EN-DC

ZTE Corporation, China Telecom, Pengcheng Laboratory

draftCR

Endorsement

Yes

endorsed

R3‑258149

R3‑258645

Correction on MRO for S-CPAC and CHO with candidate SCG for 37.340

CATT, Samsung

draftCR

Endorsement

Yes

revised

R3‑258709

Correction on MRO for S-CPAC and CHO with candidate SCG for 37.340

CATT, Samsung

draftCR

Endorsement

Yes

endorsed

R3‑258645

R3‑258460

Correction of Failure report without RLF report

Huawei, Nokia, JIO plattforms, Ericsson

Agreement

Yes

revised

R3‑258762

Correction of Failure report without RLF report

Huawei, Nokia, JIO plattforms, Ericsson

Agreement

Yes

revised

R3‑258824

R3‑258460

R3‑258824

Correction of Failure report without RLF report

Huawei, Nokia, JIO plattforms, Ericsson

Agreement

agreed

R3‑258762

R3‑258673

Correction of missing stage 2 description of LTM MRO without RLF Report

ZTE Corporation, Google, NEC

Agreement

Yes

noted

R3‑258005

Reply LS on geographical area scope MDT

SA5(CATT)

LS in

Discussion

Yes

noted

R3‑258650

Discussion on reply LS on geographical area scope MDT

CATT

discussion

Decision

Yes

noted

R3‑258651

Reply LS on geographical area scope MDT

CATT

LS out

Approval

Yes

revised

R3‑258710

Reply LS on geographical area scope MDT

RAN3(CATT)

LS out

Approval

Yes

revised

R3‑258823

R3‑258651

R3‑258823

Reply LS on geographical area scope MDT

RAN3(CATT)

LS out

Approval

Yes

approved

R3‑258710

R3‑258320

Discussion on Reply LS on geographical area scope MDT

Huawei

discussion

Yes

noted

R3‑258321

[Draft]Reply LS on geographical area scope MDT

Huawei

LS out

Yes

noted

R3‑258594

[DRAFT] Reply LS on geographical area scope MDT

Samsung

LS out

Agreement

Yes

available

R3‑258765

summary of CB: # 1_R19_SONMDT

CATT

discussion

Agreement

Yes

noted

9.2.2

R19 AI/ML for NG-RAN

R3‑258214

Miscellaneous corrections to E1AP for support of AI/ML NG-RAN

ZTE Corporation, CATT, China Unicom, China Telecom

Agreement

Yes

revised

R3‑258711

Miscellaneous corrections to E1AP for support of AI/ML NG-RAN

ZTE Corporation, CATT, China Unicom, China Telecom

Agreement

reserved

R3‑258214

R3‑258271

Corrections of AI/ML-based CCO

Nokia, Ofinno, Jio Platforms

Agreement

Yes

noted

R3‑258422

Correction on CCO prediction cancel

NEC

Agreement

Yes

noted

R3‑258477

Discussion on XnAP reporting of predicted radio resource status per slice

Huawei

discussion

Agreement

Yes

noted

R3‑258476

Correction on procedural text for reporting of predicted radio resource status per slice

Huawei

Agreement

Yes

noted

R3‑258478

Support for partial reporting in Data Collection Reporting procedure

Huawei, FiberCop, Verizon, Jio Platforms, Qualcomm, ZTE

Agreement

Yes

revised

R3‑258774

Support for partial reporting in Data Collection Reporting procedure

Huawei, FiberCop, Verizon, Jio Platforms, Qualcomm, ZTE

Agreement

reserved

R3‑258478

R3‑258514

Discussion on Exit Conditions

Nokia

discussion

Yes

available

R3‑258172

Correction of Exit Conditions

Nokia

Yes

available

R3‑258434

Abnormal conditions for F1: gNB-CU Configuration Update

Ericsson, Jio Platforms, InterDigital, Fibercop

discussion

Approval

Yes

available

R3‑258546

Abnormal conditions for gNB-CU Configuration Update with updated Presence IE

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

Yes

noted

R3‑258436

Correction for gNB-DU Configuration Update

Ericsson, Jio Platforms, InterDigital, Fibercop

discussion

Approval

Yes

available

R3‑258547

Correction for gNB-DU Configuration Update

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

Yes

available

R3‑258215

Miscellaneous corrections to the support of split architecture

ZTE Corporation, CMCC, China Unicom, China Telecom

Yes

revised

R3‑258812

Miscellaneous corrections to the support of split architecture

ZTE Corporation, CMCC, China Unicom, China Telecom

Agreement

reserved

R3‑258215

R3‑258270

Corrections of enhancements on AI/ML for NG-RAN

Nokia

Yes

available

R3‑258438

Stage 2 corrections for AI/ML based CCO

Ericsson, Jio Platforms, InterDigital, Fibercop

discussion

Approval

Yes

available

R3‑258548

Stage 2 corrections for AI/ML based CCO

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

Yes

available

R3‑258604

Correction on CCO in split architecture for 38.401

CMCC

Approval

Yes

available

R3‑258269

Corrections of enhancements on AI/ML for NG-RAN

Nokia

draftCR

Yes

available

R3‑258605

Correction on R19 AIML F1-U stage2

CMCC, Samsung, Qualcomm, ZTE, CATT, Nokia

Approval

Yes

revised

R3‑258836

Correction on AIML F1-U stage2

CMCC, Samsung, Qualcomm, ZTE, CATT, Nokia

Approval

reserved

R3‑258605

R3‑258433

Continuous MDT support

Ericsson, Deutsche Telekom, FiberCop, Jio Platforms, InterDigital, BT, Orange, Verizon, ZTE, Huawei, Telecom Italia, NEC, Samsung, CATT, China Telecom, China Unicom

Agreement

Yes

noted

R3‑257309

R3‑258216

Support for Continuous Management-based MDT

ZTE Corporation, Huawei, CATT, CMCC, Samsung, China Unicom, China Telecom, Ericsson, FiberCop, Deutsche Telekom, Jio Platforms

draftCR

Endorsement

Yes

noted

R3‑258458

Support for continuous management-based MDT

CATT, Ericsson,ZTE, CMCC, Samsung, NEC

draftCR

Agreement

Yes

revised

R3‑258799

Support for continuous management-based MDT

CATT, Ericsson,ZTE, CMCC, Samsung, NEC

draftCR

Agreement

reserved

R3‑258458

R3‑258685

Support for Continuous Management-based MDT in split architecture

Samsung, CATT, ZTE, CMCC, China Telecom, Huawei, Ericsson, FiberCop, Deutsche Telekom, China Unicom, NEC

Agreement

Yes

noted

R3‑256690

R3‑258475

[Draft] Reply LS on Continuous MDT

Huawei, ZTE, FiberCop, Jio Platforms

LS out

Agreement

Yes

revised

R3‑258773

Reply LS on Continuous MDT

RAN3(Huawei)

LS out

Approval

reserved

R3‑258475

R3‑258173

Discussion on Continuous Management Based MDT

Nokia, Qualcomm

discussion

Yes

noted

R3‑258698

Response to R3-258173

ZTE Corporation

response

Yes

available

R3‑258416

Support of Continuous Management Based MDT

Nokia

Yes

available

R3‑258417

Introduction of support for Continuous Management Based MDT in stage 2

Nokia

draftCR

Yes

available

R3‑258606

Correction to support Continuous MDT through Xn interface

CMCC

Approval

Yes

available

R3‑258811

Summary of the offline discussion on CB: # 2_R19_AIMLNGRAN

ZTE Corporation

discussion

Approval

reserved

R3‑258253

reserved

NEC

Agreement

withdrawn

Yes

R3‑258435

Abnormal conditions for gNB-CU Configuration Update with updated Presence IE

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

Yes

withdrawn

Yes

R3‑258437

Correction for gNB-DU Configuration Update

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

Yes

withdrawn

Yes

R3‑258439

Stage 2 corrections for AI/ML based CCO

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

Yes

withdrawn

Yes

R3‑258497

Abnormal conditions for gNB-CU Configuration Update with updated Presence IE

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

withdrawn

Yes

R3‑258498

Correction for gNB-DU Configuration Update

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

withdrawn

Yes

R3‑258499

Stage 2 corrections for AI/ML based CCO

Ericsson, Jio Platforms, InterDigital, Fibercop

Agreement

withdrawn

Yes

R3‑258703

Response to R3-258173

Ericsson

response

Agreement

Yes

withdrawn

Yes

9.2.3

R19 WAB

R3‑258200

Correction of WAB-MT handover a target WAB-gNB

Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT, China Telecom, Canon, Qualcomm

Yes

revised

R3‑258769

R3‑257259

R3‑258769

Clarification of handover for WAB-MT

Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT, China Telecom, Canon, Qualcomm

Yes

agreed

R3‑258200

R3‑258331

Correction on multi-hop avoidance during handover

Huawei, Nokia, Nokia Shanghai Bell, China Telecom

Approval

Yes

revised

R3‑258770

Clarification of handover for WAB-MT

Huawei, Nokia, Nokia Shanghai Bell, China Telecom

Approval

Yes

revised

R3‑258825

R3‑258331

R3‑258825

Clarification of handover for WAB-MT

Huawei, Nokia, Nokia Shanghai Bell, China Telecom

Approval

Yes

agreed

R3‑258770

R3‑258380

Corrections for additional ULI for WAB

ZTE Corporation, China Telecom, Pengcheng Laboratory, Samsung

Approval

Yes

noted

R3‑258570

Correction of BH-gNB for WAB

China Telecom,CATT, Nokia, Nokia Shanghai Bell, ZTE

draftCR

Endorsement

Yes

noted

R3‑258265

Stage-2 Correction of WAB Xn Connection Management

Ericsson

Agreement

Yes

revised

R3‑258771

Stage-2 Correction of WAB Xn Connection Management

Ericsson

Agreement

Yes

revised

R3‑258828

R3‑258265

R3‑258828

Stage-2 Correction of WAB Xn Connection Management

Ericsson

Agreement

agreed

R3‑258771

R3‑258571

Correction of BH-gNB and WAB-MT for WAB

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

Agreement

Yes

revised

R3‑258772

Correction of BH-gNB and WAB-MT for WAB

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

Agreement

Yes

revised

R3‑258829

R3‑258571

R3‑258829

Correction of BH-gNB and WAB-MT for WAB

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

Agreement

Yes

agreed

R3‑258772

R3‑258768

Clarification of handover for WAB-MT

Qualcomm

Agreement

Yes

agreed

9.2.4

R19 NR Femto

R3‑258300

Correction on sending GW release indication

CATT

draftCR

Approval

Yes

revised

R3‑258712

Correction on sending GW release indication

CATT

draftCR

Approval

Yes

endorsed

R3‑258300

R3‑258381

Corrections on GUAMI List for Femto

ZTE Corporation, China Telecom, Pengcheng Laboratory

Approval

Yes

noted

9.2.5

R19 Mobility enhancements

R3‑258672

R19 correction (CSI-RS) on the CU-DU Mobility Initiation Request message

Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC

Agreement

Yes

agreed

R3‑258157

Correction to inter-CU LTM and conditional intra-CU LTM

Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Ericsson, LG Electronics, Qualcomm Incorporated, Google, Ofinno

Yes

revised

R3‑258778

Correction to inter-CU LTM and conditional intra-CU LTM

Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Ericsson, LG Electronics, Qualcomm Incorporated, Google, Ofinno

reserved

R3‑258157

R3‑258263

Correction on SN initiated inter-SN SCG LTM procedure

Ofinno, Ericsson, CATT, Qualcomm, Huawei, Google, LG Electronics, Nokia, Samsung, Lenovo, China Telecom

draftCR

Endorsement

Yes

endorsed

R3‑257033

R3‑258293

Correction on LTM Cell Switch Notification

LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE

Approval

Yes

agreed

R3‑257125

R3‑258294

Correction related to LTM Security Information

LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE

Approval

Yes

agreed

R3‑257126

R3‑258390

Essential correction on inter-CU LTM in DC

CATT,Huawei, China Telecom, Nokia, Samsung, NEC, Ericsson

Agreement

Yes

revised

R3‑258713

R3‑256873

R3‑258713

Essential correction on inter-CU LTM in DC

CATT,Huawei, China Telecom, Nokia, Samsung, NEC, Ericsson

Agreement

agreed

R3‑258390

R3‑258392

Essential correction for inter-CU LTM on F1AP

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

Agreement

Yes

revised

R3‑258787

R3‑256871

R3‑258787

Essential correction for inter-CU LTM on F1AP

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

Agreement

reserved

R3‑258392

R3‑258508

Corrections on Inter-CU LTM

Ericsson, Lenovo, LG Electronics, Nokia, Samsung, ZTE, Ofinno

Agreement

Yes

agreed

R3‑257175

R3‑258510

Corrections for Rel-19 LTM

Ericsson, Jio Platforms, CATT, China Telecom, Lenovo, LG Electronics, Nokia, ZTE, Samsung, Ofinno

draftCR

Yes

endorsed

R3‑258558

Support for Modification of LTM Configurations

Ericsson, Ofinno, Jio Platforms

discussion

Yes

noted

R3‑258559

Support for Modification of LTM Configurations

Ericsson, Ofinno, Jio Platforms

Agreement

Yes

noted

R3‑258695

Support for Modification of LTM Configurations

Ericsson, Jio Platforms, Ofinno

draftCR

Endorsement

Yes

noted

R3‑258587

Discussion on candidate gNB initiated LTM modification (CRs included)

Huawei

discussion

Yes

noted

R3‑258589

[Draft]LS on candidate gNB initiated LTM modification

Huawei

LS out

Approval

Yes

available

R3‑258151

Exchange of early RACH Resources Requester ID for inter-CU LTM

Huawei, Ericsson, Samsung, Jio Platforms, CATT, CMCC, China Telecom, Lenovo, Nokia

discussion

Yes

noted

R3‑258152

Exchange of early RACH Resources Requester ID for inter-CU LTM

Huawei, Ericsson, Samsung, Jio Platforms, CATT, CMCC, China Telecom, Lenovo, Nokia

Approval

Yes

noted

R3‑258661

Corrections on Early RACH Resource Requester ID

ZTE Corporation

Approval

Yes

noted

R3‑258662

Corrections on Early RACH Resource Requester ID

ZTE Corporation

Approval

Yes

available

R3‑258509

Summary of Essential Corrections and Open Issues for Rel-19 LTM

Ericsson, CATT, Jio Platforms, Ofinno

discussion

Yes

available

R3‑258153

Introduction of missing LTM Indicator for inter-CU LTM

Huawei, Nokia, LG Electronics, NTT DoCoMo. Offinno, Jio Platforms, CMCC

Yes

revised

R3‑258780

Introduction of missing LTM Indicator for inter-CU LTM

Huawei, Nokia, LG Electronics, NTT DoCoMo. Offinno, Jio Platforms, CMCC, Ericsson

reserved

R3‑258153

R3‑258154

Correction on Reference Configuration in LTM Configuration Update for inter-CU LTM

Huawei, NTT DoCoMo, Offinno, Jio Platforms, CMCC, Lenovo, CATT

Yes

available

R3‑258155

Correction on the CSI-RS Coordination procedure

Huawei, LG Electronics, ZTE, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo

Yes

revised

R3‑258779

Correction on the CSI-RS Coordination procedure

Huawei, LG Electronics, ZTE, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo

reserved

R3‑258155

R3‑258156

Interaction between Handover Success and Cell Switch Notification

Huawei, Nokia, LG Electronics, NTT DoCoMo, ZTE, Offinno, Jio Platforms, CMCC

Yes

available

R3‑258275

[Draft TP for TS 38.473, TS 38.423] Remaining issues in Inter-CU LTM

Qualcomm Incorporated

other

Agreement

Yes

available

R3‑258312

Discussion on supporting inter-CU SCG LTM and the L2 reset function in inter-CU LTM

Google

discussion

Decision

Yes

available

R3‑257157

R3‑258313

Correction to L2 reset in inter-CU LTM

Google, Nokia, CATT, Ericsson

Agreement

Yes

available

R3‑257158

R3‑258317

Correction to L2 reset in inter-CU LTM (option 2)

Google, Huawei

Yes

revised

R3‑258781

Correction to L2 reset in inter-CU LTM (option 2)

Google, Huawei

reserved

R3‑258317

R3‑258319

Correction to LTM MCG configuration management for inter-CU SCG LTM

Google, Huawei

Yes

available

R3‑258322

Correction on the Rel-19 set ID assignment in inter-CU LTM

Huawei, Nokia, Jio Platforms, CATT, China Telecom, Lenovo

discussion

Yes

available

R3‑258323

Correction on the Rel-19 set ID assignment in inter-CU LTM (Option 1)

Huawei, Jio Platforms, CATT, China Telecom, Lenovo

draftCR

Yes

available

R3‑258324

Correction on the Rel-19 set ID assignment in inter-CU LTM (Option 2)

Huawei, Nokia, Jio Platforms, CATT, China Telecom

Yes

available

R3‑258325

Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM

Huawei, NEC,Jio Platforms, CMCC, China Telecom, Lenovo

discussion

Yes

available

R3‑258326

Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1)

Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo

Yes

available

R3‑258328

Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2)

Huawei, NEC, Jio Platforms, CMCC, China Telecom

Yes

available

R3‑258341

Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1)

Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo

Yes

available

R3‑258342

Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2)

Huawei, NEC, Jio Platforms, CMCC, China Telecom

Yes

available

R3‑258459

Semi-Persistent CSI-RS activation with TCI state for CSI Acquisition

CATT

Agreement

Yes

available

R3‑258471

LTM Cell Swicth Type Indication

Nokia, LGE, Huawei

Yes

available

R3‑258473

LTM Cell Swicth Type Indication

Nokia, LGE, Huawei

Yes

available

R3‑258555

PRACH resources for Inter-CU LTM

Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno

discussion

Yes

available

R3‑257042

R3‑258551

PRACH resources for Inter-CU LTM

Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno

Agreement

Yes

available

R3‑257043

R3‑258552

PRACH resources for Inter-CU LTM

Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno

Agreement

Yes

available

R3‑257044

R3‑258553

PRACH resource for Inter-CU LTM

Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno

Agreement

Yes

available

R3‑257045

R3‑258554

PRACH resources for Inter-CU LTM

Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno

draftCR

Endorsement

Yes

available

R3‑257046

R3‑258556

Fast LTM recovery for Inter-CU LTM

Ericsson, Jio Platforms, Lenovo, Ofinno

discussion

Yes

available

R3‑257047

R3‑258557

Fast LTM Recovery for Inter-CU LTM

Ericsson, Jio Platforms, Lenovo, Ofinno

Agreement

Yes

available

R3‑257048

R3‑258560

Removal of Request for CSI-RS resource configuration for Early CSI acquisition

Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE

Agreement

Yes

revised

R3‑258837

R3‑257173

R3‑258837

Removal of Request for CSI-RS resource configuration for Early CSI acquisition

Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE

Agreement

reserved

R3‑258560

R3‑258561

Removal of Request for CSI-RS resource configuration for Early CSI acquisition

Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE

Agreement

Yes

revised

R3‑258838

R3‑257174

R3‑258838

Removal of Request for CSI-RS resource configuration for Early CSI acquisition

Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE

Agreement

reserved

R3‑258561

R3‑258582

Correction on NG-RAN node UE XnAP IDs transfer after LTM failure

Huawei, Nokia, Offinno, Jio Platforms, CMCC

Yes

available

R3‑258583

UE context retrieval in the candidate gNB during subsequent LTM

Huawei, Nokia, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo

Yes

available

R3‑258584

Corrections on inter-CU MCG LTM without SN change

Huawei, Jio Platforms, Lenovo, Google

discussion

Yes

available

R3‑258585

Stage 2 corrections to inter-CU MCG LTM

Huawei, Jio Platforms, Lenovo, Google

draftCR

Yes

available

R3‑258586

Correction on security key update for inter-CU MCG LTM

Huawei, Jio Platforms, China Telecom, Lenovo, Google

Yes

available

R3‑258590

Stage 2 corrections on inter-CU LTM

Huawei

draftCR

Yes

available

R3‑258659

Corrections on last target NG-RAN node UE XnAP ID transfer

ZTE Corporation, CATT, Huawei

Approval

Yes

available

R3‑258660

Discussion on remaining issues on early sync

ZTE Corporation

discussion

Decision

Yes

available

R3‑258663

Corrections on LTM Early Sync resource update

ZTE Corporation

Approval

Yes

available

R3‑258664

Corrections on LTM Early Sync resource update

ZTE Corporation

Approval

Yes

available

R3‑258665

Remaining Issues on Inter-CU LTM

Samsung

discussion

Discussion

Yes

noted

R3‑258666

XnAP correction on the Inter-CU LTM procedure

Samsung

Agreement

Yes

revised

R3‑258775

XnAP correction on the Inter-CU LTM procedure

Samsung

Agreement

reserved

R3‑258666

R3‑258667

Correction on TA Information Transfer for inter-CU SCG LTM

Samsung, Huawei, Ericsson, Nokia, Google

Agreement

Yes

available

R3‑258668

Correction on Early UL Sync Configuration IE for inter-CU LTM

Samsung, Huawei, Ericsson, Nokia, China Telecom, Google

Agreement

Yes

revised

R3‑258776

Correction on Early UL Sync Configuration IE for inter-CU LTM

Samsung, Huawei, Ericsson, Nokia, China Telecom, Google

Agreement

reserved

R3‑258668

R3‑258669

Correction on the LTM Indicator for C-LTM

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

Agreement

Yes

revised

R3‑258777

Correction on the LTM Indicator for C-LTM

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

Agreement

reserved

R3‑258669

R3‑258090

Discussion on remaining Inter-CU LTM Issues

Nokia

discussion

Agreement

withdrawn

Yes

R3‑258291

Correction on LTM Cell Switch Notification

LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE

Approval

withdrawn

Yes

R3‑258292

Correction related to LTM Security Information

LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE

Approval

withdrawn

Yes

R3‑258327

Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1)

Huawei

withdrawn

Yes

R3‑258329

Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2)

Huawei

withdrawn

Yes

R3‑258588

Candidate gNB-DU initiated LTM modification

Huawei

withdrawn

Yes

R3‑258813

Summary of the offline discussion on CB: # 5_R19_MobEnh

Samsung

discussion

Approval

reserved

R3‑258818

Removal of Request for CSI-RS resource configuration for Early CSI acquisition

LG Electronics, Ericsson, Jio Platforms, Verizon Wireless, ZTE, CATT, China Telecom, Google, Huawei, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Lenovo

draftCR

Endorsement

reserved

R3‑258839

TBD

Ericsson

draftCR

Endorsement

reserved

R3‑258840

TBD

Ericsson

draftCR

Endorsement

reserved

9.2.6

R19 NR NTN enhancements

R3‑258239

Correction to stage 2 description of Hard Feeder Link Switchover for regenerative payload

NEC

draftCR

Agreement

Yes

noted

R3‑258472

Inter-Satellite Links and Transparent Payloads

Ericsson, Aalyria, Thales, Airbus

discussion

Discussion

Yes

noted

R3‑258474

Inter-Satellite Links and Transparent Payloads - NR NTN

Ericsson, Aalyria, Thales, Airbus

draftCR

Endorsement

Yes

noted

9.2.7

R19 Ambient IoT

R3‑258011

LS on integrity failure

RAN2(Xiaomi)

LS in

Discussion

Yes

noted

R3‑258012

Reply LS on Structure updates of AIoT Identifiers

SA2(CATT)

LS in

Discussion

Yes

noted

R3‑258092

Reply LS on the maximum supported AIoT NAS container length

RAN2(Lenovo)

LS in

Discussion

Yes

noted

R3‑258121

Consideration on A-IoT dedicated Cause values

Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson

discussion

Agreement

Yes

noted

R3‑258122

Correction on A-IoT dedicated Cause values

Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson

Agreement

Yes

revised

R3‑258732

Correction on A-IoT dedicated Cause values

Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson, CATT, NEC, Xiaomi, Samsung, ZTE

Agreement

Yes

agreed

R3‑258122

R3‑258336

Discussion on Cause values for Ambient IoT

CATT

discussion

Decision

Yes

available

R3‑258691

Correction to A-IoT specific cause values

CATT

Approval

Yes

available

R3‑258338

Correction to A-IoT security information

CATT

Approval

Yes

noted

R3‑258620

Correction on A-IoT security aspects

CMCC, Huawei

Approval

Yes

noted

R3‑258619

Correction on A-IoT security aspects

CMCC, Huawei

draftCR

Approval

Yes

available

R3‑258632

Correction on A-IoT Paging related information

ZTE Corporation,

Approval

Yes

noted

R3‑258241

Discussion on Device identifier privacy protection impact on RAN3

NEC

discussion

Agreement

Yes

noted

R3‑258242

Correction on A-IoT device identifier privacy protection impact on RAN3

NEC

Agreement

Yes

noted

R3‑256790

R3‑258123

Correction on A-IoT related Network Identities

Huawei, Nokia, Ericsson, CMCC, China Unicom, China Telecom

draftCR

Agreement

Yes

revised

R3‑258733

Correction on A-IoT related Network Identities

Huawei, Nokia, Ericsson, CMCC, China Unicom, China Telecom

draftCR

Agreement

Yes

endorsed

R3‑258123

R3‑258124

Consideration on the presence of Reader Report List

Huawei, CMCC, China Unicom, China Telecom

discussion

Agreement

Yes

noted

R3‑258125

Correction on the presence of Reader Report List

Huawei, CMCC, China Unicom, China Telecom

Agreement

Yes

revised

R3‑258735

Correction on the presence of Reader Report List

Huawei, CMCC, China Unicom, China Telecom, CATT, ZTE, Samsung, Nokia, Xiaomi

Agreement

Yes

agreed

R3‑258125

R3‑258185

Consideration on A-IoT Device Identification

Huawei, CMCC, China Unicom, China Telecom, Lenovo

discussion

Agreement

Yes

noted

R3‑258186

Correction on A-IoT Device Identification

Huawei, CMCC, China Unicom, China Telecom, Lenovo

Agreement

Yes

noted

R3‑258240

Correction on A-IoT Inventory and Command procedure figures

NEC

draftCR

Agreement

Yes

revised

R3‑258736

Correction on A-IoT Inventory and Command procedure figures

NEC

draftCR

Agreement

Yes

endorsed

R3‑258240

R3‑258595

Discussion on the encoding of AIOTF identifier

Samsung, Huawei, CMCC

discussion

Agreement

Yes

noted

R3‑258759

LS on the encoding of AIOTF Identifier

RAN3(Samsung)

LS out

Approval

Yes

approved

R3‑258596

Correction to the encoding of AIOTF Identifier IE

Samsung, Huawei, CMCC

Agreement

Yes

noted

R3‑258407

Correction of Inventory Report

Nokia

Yes

available

R3‑258633

Correction on AIoT Reader Report List

ZTE Corporation

Approval

Yes

merged

R3‑258337

Correction to A-IoT specific cause values

CATT

Approval

Yes

withdrawn

Yes

9.2.8

R19 Network Energy Saving

R3‑258150

Correction on procedural description of Cell A ID

ZTE Corporation, CATT, Samsung

Approval

Yes

noted

R3‑258504

Addition of OAM support for on-demand SIB1

Ericsson, China Telecom, Jio Platforms, Lenovo

draftCR

Approval

Yes

noted

R3‑258301

Correction on OD-SIB1 Configuration Provision Failure

CATT, ZTE, Samsung

Approval

Yes

noted

R3‑258254

Correction on inter-gNB Cell A indicator transfer

NEC, Nokia

Agreement

Yes

noted

R3‑258423

Correction on OD-SIB1 failure cause

NEC, Rakuten

Agreement

Yes

noted

R3‑258453

Corrections to OD-SIB1 Configuration Provision Status Update

Ericsson

Agreement

Yes

revised

R3‑258809

R3‑257091

R3‑258809

Corrections to OD-SIB1 Configuration Provision Status Update

Ericsson, ZTE, Samsung

Agreement

reserved

R3‑258453

R3‑258503

Corrections to F1 support of Network Energy Saving Enhancement

Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten

Approval

Yes

revised

R3‑258743

Corrections to F1 support of Network Energy Saving Enhancement

Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten

Approval

Yes

revised

R3‑258807

R3‑258503

R3‑258807

Corrections to F1 support of Network Energy Saving Enhancement

Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten

Approval

Yes

agreed

R3‑258743

R3‑258280

Correction on Criticality in the OD-SIB1 Configuration Provision Response and Failure message

ZTE Corporation

Approval

Yes

noted

R3‑258402

Correction on Criticality in the OD-SIB1 Configuration Provision Status Update message

ZTE Corporation

Approval

Yes

available

R3‑258170

Correction of the NES Cell ID criticality in OD-SIB1 configuration provision response message

Huawei, CMCC, Deutsche Telekom, CATT

Yes

available

R3‑258374

Correction on assigned criticality for NES

Samsung

Agreement

Yes

available

R3‑258171

Correction of references of NES Cell and Cell A for OD-SIB1 configuration provision procedure

Huawei, CMCC, Deutsche Telekom, CATT

Yes

noted

R3‑258302

Corrections on termination of OD-SIB1 operation and status update

CATT, Huawei

Approval

Yes

revised

R3‑258810

R3‑256765

R3‑258810

Corrections on termination of OD-SIB1 operation and status update

CATT, Huawei, Ericsson, CMCC

Approval

reserved

R3‑258302

R3‑258502

Corrections to stage-2 specification for support for on-demand SIB1

Ericsson, Jio Platforms, China Telecom, Rakuten

Agreement

Yes

available

R3‑257087

R3‑258614

Correction on support for on-demand SIB1

CMCC, Huawei

Approval

Yes

available

R3‑258452

Corrections to TS 38.420 on support of Network Energy Saving Enhancement

Ericsson

Agreement

Yes

noted

R3‑257090

R3‑258808

Summary of the offline discussion on CB # 11_Rel-19 Network Energy Saving

Ericsson

discussion

Approval

reserved

9.2.9

R19 Low Power WUS/WUR

R3‑258008

Reply LS on allocation of CN assigned subgroup ID for LP-WUS

SA2(Ericsson)

LS in

Discussion

Yes

noted

R3‑258524

CN assigned subgroup ID for LP-WUS

Ericsson

discussion

Discussion

Yes

noted

R3‑258525

Clarification on allocation of CN assigned subgroup ID for LP-WUS

Ericsson

draftCR

Endorsement

Yes

available

R3‑258526

DRAFT Reply LS on CN assigned subgroup ID for LP-WUS

Ericsson

LS out

Agreement

Yes

revised

R3‑258761

DRAFT Reply LS on CN assigned subgroup ID for LP-WUS

RAN3(Ericsson)

LS out

Agreement

Yes

available

R3‑258526

R3‑258314

Discussion on allocation of CN assigned subgroup ID for LP-WUS

Huawei, Qualcomm, vivo

discussion

Yes

noted

R3‑258315

Allocation of CN assigned subgroup ID for LP-WUS

Huawei, Qualcomm, vivo

draftCR

Yes

revised

R3‑258760

Allocation of CN assigned subgroup ID for LP-WUS

Huawei, Ericsson

draftCR

reserved

R3‑258315

R3‑258316

[Draft] Reply LS on allocation of CN assigned subgroup ID for LP-WUS

Huawei, Qualcomm, vivo

LS out

Yes

available

R3‑258382

Discussion on the reply LS on allocation of CN assigned subgroup ID for LP-WUS

ZTE Corporation

discussion

Decision

Yes

noted

R3‑258383

[draft] Reply LS on allocation of CN assigned subgroup ID for LP-WUS

ZTE Corporation

other

Approval

Yes

available

R3‑258303

On maximum number of subgroups and RAN paging

CATT

Approval

Yes

withdrawn

Yes

R3‑258410

Correction of LP-WUS

Nokia

Agreement

Yes

noted

R3‑258804

On maximum number of subgroups and RAN paging

CATT

draftCR

Endorsement

Yes

available

9.2.10

R19 Evolution of Duplex Operation

R3‑258549

Corrections on SBFD support

Ericsson

Agreement

Yes

noted

R3‑258637

Discussion on CLI Indication message structure

ZTE Corporation, Pengcheng Laboratory

discussion

Approval

Yes

noted

R3‑258635

Correction to XnAP on CLI Indication

ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei

Approval

Yes

revised

R3‑258788

R3‑257162

R3‑258788

Correction to XnAP on CLI Indication

ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei, Qualcomm, Samsung, Eircsson, Charter, Nokia, LGE, CATT, CMCC

Approval

agreed

R3‑258635

R3‑258636

Correction to F1AP on CLI Indication

ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei

Approval

Yes

revised

R3‑258789

R3‑257163

R3‑258789

Correction to F1AP on CLI Indication

ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei

Approval

agreed

R3‑258636

R3‑258647

Correction on SBFD RACH configuration for F1AP

CATT

Approval

Yes

revised

R3‑258835

Correction on SBFD RACH configuration for F1AP

CATT

Approval

reserved

R3‑258647

R3‑258686

Discussion on the open issues regarding L1 UE-to-UE CLI configuration

Samsung, Qualcomm, Charter

discussion

Agreement

Yes

noted

R3‑258687

Correction on the indication of L1 UE-to-UE CLI

Samsung, Qualcomm, Charter

Agreement

Yes

noted

R3‑256692

R3‑258272

Revocation of NZP CSI-RS resources

Nokia

Yes

noted

R3‑258273

Revocation of NZP CSI-RS resources

Nokia

Yes

available

R3‑258607

Correction on Evolution of NR duplex operation for 38.420

CMCC, CATT

Approval

Yes

available

R3‑258639

Clarification to UE-to-UE CLI mitigation in SBFD operation

Huawei, CATT, China Unicom

draftCR

Approval

Yes

revised

R3‑258830

Clarification to UE-to-UE CLI mitigation in SBFD operation

Huawei, CATT, China Unicom

draftCR

Approval

reserved

R3‑258639

R3‑258640

Clarification to CLI mitigation in SBFD operation

Huawei

Approval

Yes

available

R3‑257177

R3‑258802

Summary of the offline discussion on CB # 24_R19

CATT

discussion

Agreement

reserved

R3‑258440

Corrections on SBFD support

Ericsson

Agreement

Yes

withdrawn

Yes

R3‑258500

Corrections on SBFD support

Ericsson

Agreement

withdrawn

Yes

R3‑258622

Correction to XnAP on CLI Indication

ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei

Approval

withdrawn

Yes

R3‑258623

Correction to F1AP on CLI Indication

ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei

Approval

withdrawn

Yes

R3‑258624

Correction to F1AP on SBFD RACH configuration

ZTE Corporation

Approval

withdrawn

Yes

R3‑258646

Correction on Evolution of NR duplex operation for 38.470

CATT

Approval

Yes

withdrawn

Yes

9.2.11

R19 AI/ML for air interface

R3‑258004

Reply LS on AI/ML Positioning Case 3a

SA2(CATT)

LS in

Discussion

Yes

noted

R3‑258142

Discussion on the reply LS on AI/ML assisted positioning

ZTE Corporation, Ericsson, Xiaomi, CATT

discussion

Yes

noted

R3‑258143

Correction on Positioning Data Unavailable IE

ZTE Corporation, Ericsson, Xiaomi, CATT

Yes

noted

R3‑258480

Discussion on the Reply LS from SA2 on AI/ML Positioning Case 3a

Huawei, Nokia, Qualcomm, Samsung

discussion

Decision

Yes

noted

R3‑258700

Response to R3-258480

Ericsson

response

Yes

noted

R3‑258174

Clarification of procedural text for POSITIONING DATA COLLECTION REPORT message

Nokia, CATT, Ericsson

Yes

revised

R3‑258793

Clarification of procedural text for POSITIONING DATA COLLECTION REPORT message

Nokia, CATT, Ericsson

agreed

R3‑258174

R3‑258238

Correction on positioning data collection for assisting in the pairing with the TRP's measurement.

NEC

Decision

Yes

noted

R3‑258527

Correction of Data Collection Report procedure and others

Ericsson, Huawei, Nokia, Xiaomi, ZTE, CATT, NEC, Samsung, Qualcomm Inc., CEWiT

draftCR

Endorsement

Yes

revised

R3‑258795

Correction of Data Collection Report procedure and others

Ericsson, Huawei, Nokia, Xiaomi, ZTE, CATT, NEC, Samsung, Qualcomm Inc., CEWiT

draftCR

Endorsement

Yes

endorsed

R3‑258527

R3‑258479

[Draft] LS on definition of “ground truth label” in AI/ML-based Positioning Case 3a

Huawei, Ericsson, Nokia

LS out

Agreement

Yes

revised

R3‑258796

[Draft] LS on definition of “ground truth label” in AI/ML-based Positioning Case 3a

Huawei, Ericsson, Nokia

LS out

Agreement

Yes

approved

R3‑258479

9.2.12

R19 NR XR Enhancements

R3‑258009

LS Reply on uplink rate control

SA2(vivo)

LS in

Discussion

Yes

noted

R3‑258201

Add the missing behavior text for the MMSID IE and the Indication of Bitrate Adaptation IE

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

Agreement

Yes

agreed

R3‑258332

Correction on multi-modality, uplink rate control and available bit rate monitoring

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

draftCR

Endorsement

Yes

revised

R3‑258797

Correction on multi-modality, uplink rate control and available bit rate monitoring

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

draftCR

Endorsement

Yes

endorsed

R3‑258332

R3‑258375

Correction on Burst Size for XR

Samsung

draftCR

Endorsement

Yes

revised

R3‑258798

Correction on Burst Size for XR

Samsung

draftCR

Endorsement

endorsed

R3‑258375

R3‑258615

Corrections on uplink rate control

CMCC

Agreement

Yes

noted

R3‑258625

Correction on semantic description for Notification Cause IE in NGAP

ZTE Corporation

Approval

withdrawn

Yes

R3‑258626

Correction on stage 3 description on Indication of Bitrate Adaptation IE in NGAP

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

Approval

withdrawn

Yes

R3‑258627

Discussion on UL Rate Control on XR with the correction and draft LS

ZTE Corporation

discussion

Approval

withdrawn

Yes

9.2.13

R19 NR Sidelink Multi-hop Relay

9.2.14

Other

R3‑258220

Correction of time-based handover for NR NTN

Huawei, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, Samsung

draftCR

Endorsement

Yes

available

R3‑258221

Correction of time-based handover for NR NTN

Huawei, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, Samsung

draftCR

Endorsement

Yes

available

R3‑258343

Avoiding paging capability loss after handover resource allocation and path switch request procedure

Huawei, China Unicom, China Telecom, CATT

Yes

noted

R3‑256816

R3‑258344

Avoiding paging capability loss after handover resource allocation and path switch request procedure

Huawei, China Unicom, China Telecom, CATT

Yes

available

R3‑256817

R3‑258345

Avoiding paging capability loss after handover resource allocation and path switch request procedure

Huawei, China Unicom, China Telecom, CATT

Yes

available

R3‑256818

R3‑258346

Avoiding paging capability loss after handover resource allocation and path switch request procedure

Huawei, China Unicom, China Telecom

draftCR

Yes

noted

R3‑256819

R3‑258347

Avoiding paging capability loss after handover resource allocation and path switch request procedure

Huawei, China Unicom, China Telecom

draftCR

Yes

available

R3‑256820

R3‑258348

Avoiding paging capability loss after handover resource allocation and path switch request procedure

Huawei, China Unicom, China Telecom

draftCR

Yes

available

R3‑256821

R3‑258349

[Draft] Reply LS on paging capability loss issue

Huawei, China Unicom, China Telecom

LS out

Approval

Yes

revised

R3‑258723

Reply LS on paging capability loss issue

RAN3(Huawei)

LS out

Approval

Yes

revised

R3‑258831

R3‑258349

R3‑258831

Reply LS on paging capability loss issue

RAN3(Huawei)

LS out

Approval

approved

R3‑258723

R3‑258394

Paging capability loss in RAN

Vodafone

Agreement

Yes

noted

R3‑258401

Paging capability loss in RAN

Vodafone Ireland Plc

Agreement

Yes

available

R3‑258403

Paging capability loss in RAN

Vodafone Ireland Plc

Agreement

Yes

available

R3‑258534

Correction on Paging Loss issue

Ericsson

draftCR

Endorsement

Yes

revised

R3‑258752

Correction on Paging Loss issue

Ericsson, Nokia, Huawei, CATT

draftCR

Endorsement

Yes

endorsed

R3‑258534

R3‑258535

Correction on Paging Loss issue

Ericsson

draftCR

Endorsement

Yes

revised

R3‑258753

Correction on Paging Loss issue

Ericsson, Nokia

draftCR

Endorsement

Yes

endorsed

R3‑258535

R3‑258536

Correction on Paging Loss issue

Ericsson

draftCR

Endorsement

Yes

revised

R3‑258754

Correction on Paging Loss issue

Ericsson, Nokia

draftCR

Endorsement

Yes

endorsed

R3‑258536

R3‑258537

[DRAFT] Reply LS on Response to Reply LS on paging capability loss issue

Ericsson

LS out

Agreement

Yes

available

R3‑258304

Correction of URCP for RAN paging

CATT

Approval

Yes

revised

R3‑258755

Correction of URCP for RAN paging

CATT, Huawei

Approval

Yes

agreed

R3‑258304

R3‑258305

Correction of URCP for RAN paging

CATT

Approval

Yes

revised

R3‑258756

Correction of URCP for RAN paging

CATT, Huawei

Approval

Yes

agreed

R3‑258305

R3‑258306

Correction of URCP for RAN paging

CATT

Approval

Yes

revised

R3‑258757

Correction of URCP for RAN paging

CATT, Huawei

Approval

Yes

agreed

R3‑258306

R3‑258106

Additional procedure text for Data Collection Update

ZTE Corporation, Ercisson, Samsung, NEC, Nokia, Huawei, CATT, Jio Platforms, Qualcomm, FiberCop, Orange

Agreement

Yes

revised

R3‑258724

R3‑256563

R3‑258724

Additional procedure text for Data Collection Update

ZTE Corporation, Ercisson, Samsung, NEC, Nokia, Huawei, CATT, Jio Platforms, Qualcomm, FiberCop, Orange

Agreement

Yes

agreed

R3‑258106

R3‑258118

Specifying procedure texts for the Core Network Assistance Information for RRC INACTIVE IE

Huawei, Ericsson, Nokia, ZTE

Agreement

Yes

agreed

R3‑256682

R3‑258299

Correction on the description of UE Context Information – Retrieve UE Context Response

ZTE Corporation, Nokia, Huawei, CATT, Samsung

Agreement

Yes

revised

R3‑258725

R3‑256564

R3‑258725

Correction on the description of UE Context Information – Retrieve UE Context Response

ZTE Corporation, Nokia, Huawei, CATT, Samsung

Agreement

Yes

agreed

R3‑258299

R3‑258486

Extensions for enumerated type definitions over several Releases - and what can go wrong

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

discussion

Discussion

Yes

noted

R3‑258701

Response to R3-258486

Huawei

response

Discussion

Yes

noted

R3‑258487

Correcting the extension of FR1-bandwidth type definition

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

revised

R3‑258737

R3‑256996

R3‑258737

Correcting the extension of FR1-bandwidth type definition

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

agreed

R3‑258487

R3‑258488

Correcting the extension of FR1-bandwidth type definition

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

revised

R3‑258738

R3‑256997

R3‑258738

Correcting the extension of FR1-bandwidth type definition

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

agreed

R3‑258488

R3‑258489

Correcting the IE extension definition for bandwidth SRS

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

revised

R3‑258739

R3‑256998

R3‑258739

Correcting the IE extension definition for bandwidth SRS

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

agreed

R3‑258489

R3‑258490

Correcting the IE extension definition for bandwidth SRS

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

revised

R3‑258740

R3‑256999

R3‑258740

Correcting the IE extension definition for bandwidth SRS

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

agreed

R3‑258490

R3‑258491

Correcting the IE extension definition for SRS Pos SIB Type

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

revised

R3‑258741

R3‑257000

R3‑258741

Correcting the IE extension definition for SRS Pos SIB Type

Ericsson, Jio Platforms, China Telecom, CMCC, Nokia

Agreement

Yes

agreed

R3‑258491

R3‑258528

Addition of PDCP discard timer for scheduling with DSR

Ericsson, Qualcomm Inc., Jio Platforms

Agreement

Yes

noted

R3‑257037

R3‑258529

Addition of PDCP discard timer for scheduling with DSR

Ericsson, Qualcomm Inc., Jio Platforms

Agreement

Yes

available

R3‑257039

R3‑258658

Clarification for propagation of roaming and access restrictions

Samsung

draftCR

Endorsement

Yes

revised

R3‑258726

Clarification for propagation of roaming and access restrictions

Samsung

draftCR

Endorsement

endorsed

R3‑258658

R3‑258670

R18 correction (SSB) on the CU-DU Mobility Initiation Request message

Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC

Agreement

Yes

revised

R3‑258728

R3‑256859

R3‑258728

Correction (SSB) on the CU-DU Mobility Initiation Request message

Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC

Agreement

Yes

agreed

R3‑258670

R3‑258671

R18 correction (SSB) on the CU-DU Mobility Initiation Request message

Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC

Agreement

Yes

revised

R3‑258729

R3‑256860

R3‑258729

Correction (SSB) on the CU-DU Mobility Initiation Request message

Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC

Agreement

Yes

agreed

R3‑258671

R3‑258675

Clarify on UE context retrieval

ZTE Corporation

discussion

Yes

noted

R3‑258674

Clarification for propagation of MDT Configuration in stage2

ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei

other

Yes

revised

R3‑258727

R3‑256527

R3‑258727

Clarification for propagation of MDT Configuration in stage2

ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei

draftCR

Endorsement

Yes

revised

R3‑258816

R3‑258674

R3‑258816

Clarification for propagation of MDT Configuration in stage2

ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei

draftCR

Endorsement

Yes

endorsed

R3‑258727

R3‑258790

Clarification for propagation of MDT Configuration in stage2

ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei

draftCR

Endorsement

Yes

revised

R3‑258817

Clarification for propagation of MDT Configuration in stage2

ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei

draftCR

Endorsement

Yes

endorsed

R3‑258790

R3‑258094

Correction of Transmission Bandwidth Asymmetric

Nokia, Huawei, Qualcomm, China Telecom

Agreement

Yes

noted

R3‑256566

R3‑258095

Correction of Transmission Bandwidth Asymmetric

Nokia, Huawei, Qualcomm, China Telecom

Agreement

Yes

available

R3‑256567

R3‑258096

Correction of Transmission Bandwidth Asymmetric

Nokia, Huawei, Qualcomm, China Telecom

Agreement

Yes

available

R3‑256568

R3‑258097

Correction of Transmission Bandwidth Asymmetric

Nokia, Huawei, Qualcomm, China Telecom

Agreement

Yes

available

R3‑256569

R3‑258098

Correction of Transmission Bandwidth Asymmetric

Nokia, Huawei, Qualcomm, China Telecom

Agreement

Yes

available

R3‑256570

R3‑258099

Correction of Transmission Bandwidth Asymmetric

Huawei, Nokia, Qualcomm, China Telecom

Yes

available

R3‑256669

R3‑258100

Correction of Transmission Bandwidth Asymmetric

Huawei, Nokia, Qualcomm, China Telecom

Yes

available

R3‑256670

R3‑258101

Correction of Transmission Bandwidth Asymmetric

Huawei, Nokia, Qualcomm, China Telecom

Yes

available

R3‑256671

R3‑258102

Correction of Transmission Bandwidth Asymmetric

Huawei, Nokia, Qualcomm, China Telecom

Yes

available

R3‑256672

R3‑258103

Correction of Transmission Bandwidth Asymmetric

Huawei, Nokia, Qualcomm, China Telecom

Yes

available

R3‑256673

R3‑258162

Discussion on AQP priority

ZTE Corporation, Nokia, Ericsson, Huawei

discussion

Approval

Yes

noted

R3‑258163