RAN2#121bis-e

1: Opening of the meeting

TDoc	Title	Source
R2-2304511	(reserved)	Nathan's tdocs
R2-2304512	(reserved)	Nathan's tdocs
R2-2304513	(reserved)	Nathan's tdocs
R2-2304514	(reserved)	Nathan's tdocs
R2-2304515	(reserved)	Nathan's tdocs

2.1: Approval of the agenda

TDoc	Title	Source
R2-2302400	Agenda for RAN2#121bis-e	Chairman

2.2: Approval of the report of the previous meeting

TDoc	Title	Source
R2-2302401	RAN2#121 Meeting Report	MCC

2.4: Instructions

TDoc	Title	Source
R2-2302402	RAN2 Handbook	MCC

2.5: Others

TDoc	Title	Source
R2-2303634	Recommendations for RAN1 RRC Parameter Preparation	Ericsson

3: Incoming liaisons

TDoc	Title	Source
R2-2304488	Reply LS on Research highlighting potential 5G and 4G Bidding Down Attacks (C1-232756; contact: Ericsson)	CT1

4.1: EUTRA corrections Rel-17 and earlier

TDoc	Title	Source
R2-2303818	Correction on QoE configuration release	Google
R2-2303821	Correction on QoE configuration release	Google Inc.
R2-2303822	Correction on QoE configuration release	Google

4.2.1: General and Stage 2 corrections

TDoc	Title	Source
R2-2302422	LS on UE capability signalling for IoT-NTN (R3-230951; contact: Vodafone)	RAN3
R2-2302677	Stage-2 Corrections for Supporting Emergency Calls in IoT NTN	MediaTek Inc
R2-2303665	Clarification on Kmac definition	ZTE Corporation, Sanechips
R2-2303832	Correction for R17 IoT NTN	Ericsson
R2-2304260	Correction for R17 IoT NTN	Ericsson, OPPO, Thales

4.2.2: UP corrections

TDoc	Title	Source
R2-2302530	MAC correction on TDD support for IoT NTN	OPPO
R2-2303980	Corrections on MAC procedure upon validity timer expiry for IoT NTN	Nokia, Nokia Shanghai Bell
R2-2304267	Clarification on UL operation upon validity timer expiry for IoT NTN	Nokia, Nokia Shanghai Bell, Apple, Ericsson
R2-232467	MAC correction on TDD support for IoT NTN	OPPO

4.2.3: CP corrections

TDoc	Title	Source
R2-2302676	Corrections in TS 36.331 for Supporting Emergency Calls in IoT NTN	MediaTek Inc.
R2-2303040	Indication of GSO-NGSO cell type in SIB1	Qualcomm Incorporated
R2-2303194	Alignment of NPRACH preamble descriptions with RAN1 specification for IoT-NTN parameters	Nokia, Nokia Shanghai Bell
R2-2303667	User consent for location info in RLF-Report	ZTE Corporation, Sanechips
R2-2303961	UE location information in NB-IoT RLF report	Huawei, HiSilicon
R2-2303981	CR to 36.331 on T317 and T318	Huawei, HiSilicon
R2-2304082	CR to 36.331 on T317 and T318	Huawei, HiSilicon
R2-2304136	On reporting location in NB-IoT RLF Report	Samsung R&D Institute UK
R2-2304241	Report of [AT121bis-e][101][IoT NTN] CP corrections] (Huawei)	Huawei, HiSilicon
R2-2304261	Alignment of NPRACH preamble descriptions with RAN1 specification for IoT-NTN parameters	Nokia, Nokia Shanghai Bell
R2-2304262	CR to 36.331 on T317 and T318	Huawei, HiSilicon
R2-2304270	Alignment of NPRACH preamble descriptions with RAN1 specification for IoT-NTN parameters	Nokia, Nokia Shanghai Bell

4.4: Positioning corrections Rel-16 and earlier

TDoc	Title	Source
R2-2302625	Miscellaneous Corrections on Section 4 Functionality of Protocol in TS 37.355	CATT
R2-2302626	Miscellaneous Corrections on Section 4 Functionality of Protocol in TS 37.355	CATT
R2-2302627	Miscellaneous Corrections on Section 4 Functionality of Protocol in TS 37.355	CATT
R2-2302628	Miscellaneous Corrections on Section 5 LPP Procedures in TS 37.355	CATT
R2-2302629	Miscellaneous Corrections on Section 5 LPP Procedures in TS 37.355	CATT
R2-2302630	Miscellaneous Corrections on Section 5 LPP Procedures in TS 37.355	CATT
R2-2302631	Corrections on the descriptions in Positioning methods IEs	CATT
R2-2302632	Corrections on the descriptions in Positioning methods IEs	CATT
R2-2302633	Corrections on the descriptions in Positioning methods IEs	CATT
R2-2302634	Corrections on positioning assistance data transfer	CATT
R2-2302635	Corrections on positioning assistance data transfer	CATT
R2-2302636	Corrections on positioning assistance data transfer	CATT
R2-2304282	LTE positioning corrections (CATT)	CATT
R2-2304476	Corrections on Figure 4.1.1-1 and the descriptions in Positioning methods IEs	CATT
R2-2304477	Corrections on Figure 4.1.1-1 and the descriptions in Positioning methods IEs	CATT
R2-2304478	Corrections on Figure 4.1.1-1 and the descriptions in Positioning methods IEs	CATT
R2-2304509	LTE positioning corrections (CATT)	CATT
R2-2304520	Corrections on applicability of timing error margin of RxTEG in NR-Multi-RTT-SignalMeasurementInformation field descriptions and other Miscellaneous corrections	CATT

5.1.1: Stage 2 and Organisational

TDoc	Title	Source
R2-2304108	Correction to information delivered in Handover Request message	Huawei, HiSilicon
R2-2304109	Correction to information delivered in Handover Request message	Huawei, HiSilicon
R2-2304110	Correction to information delivered in Handover Request message	Huawei, HiSilicon
R2-2304531	Summary of [AT121bis-e][001][NR1516] Stage 2 and RRC 0	Huawei, HiSilicon

5.1.2.1: MAC

TDoc	Title	Source
R2-2303854	Clarification on handling of DCI for the deactivated configured grant	Samsung
R2-2303855	Clarification on handling of DCI for the deactivated configured grant	Samsung
R2-2303856	Clarification on handling of DCI for the deactivated configured grant	Samsung

5.1.3.1: NR RRC

TDoc	Title	Source
R2-2302595	38.331_R15_CR (Cat F)_Corrections to recommended bit rate query	Samsung Electronics Co., Ltd
R2-2302596	38.331_R16_CR (Cat A)_Corrections to recommended bit rate query	Samsung Electronics Co., Ltd
R2-2302597	38.331_R17_CR (Cat A)_Corrections to recommended bit rate query	Samsung Electronics Co., Ltd
R2-2302666	Clarifications on CG Parameters in NR-U	vivo
R2-2302667	Clarifications on CG Parameters in NR-U	vivo
R2-2302771	CSI-RS resource coordination in NR-DC	Nokia, Nokia Shanghai Bell
R2-2302772	CSI-RS resource coordination in NR-DC	Nokia, Nokia Shanghai Bell
R2-2302881	Correction on Need code of IE RLC-Config	Intel Corporation
R2-2302882	Correction on Need code of IE RLC-Config	Intel Corporation
R2-2303106	Clarification on RSSI measurement frequency	Samsung R&D Institute India
R2-2303107	Clarification on RSSI measurement frequency	Samsung R&D Institute India
R2-2303150	CSI-RS resource coordination in NR-DC	Nokia, Nokia Shanghai Bell
R2-2303151	CSI-RS resource coordination in NR-DC	Nokia, Nokia Shanghai Bell
R2-2303278	Further consideration on refServCellIndicator	ZTE Corporation, Sanechips
R2-2303279	Corrections on refServCellIndicator	ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2303280	Corrections on refServCellIndicator	ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2303281	Corrections on refServCellIndicator	ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2303282	Clarification on drb-ContinueROHC	ZTE Corporation, Sanechips
R2-2303283	Clarification on handling of Need N fields	ZTE Corporation, Sanechips
R2-2303284	Clarification on handling of Need N fields	ZTE Corporation, Sanechips
R2-2303285	Clarification on handling of Need N fields	ZTE Corporation, Sanechips
R2-2303464	Summary of need code for secondary DRX group	Huawei, HiSilicon
R2-2303465	Correction on the need code for secondary DRX group	Huawei, HiSilicon
R2-2303466	Correction on the need code for secondary DRX group	Huawei, HiSilicon
R2-2303635	SIB and PosSIB mappings to SI message	Ericsson, MediaTek Inc.
R2-2303636	SIB and PosSIB mappings to SI message	Ericsson, MediaTek Inc.
R2-2303871	Correction on reconfiguration including T316	Lenovo
R2-2303872	Correction on reconfiguration including T316	Lenovo
R2-2304090	Clarification on nas-SecurityParamFromNR field description	Ericsson
R2-2304091	Clarification on nas-SecurityParamFromNR field description	Ericsson
R2-2304092	Clarification on nas-SecurityParamFromNR field description	Ericsson
R2-2304093	Clarification on presence of Coreset0 for PSCell	Ericsson
R2-2304094	Clarification on presence of Coreset0 for PSCell	Ericsson
R2-2304095	Clarification on presence of Coreset0 for PSCell	Ericsson
R2-2304096	Clarification on the update of security algorithms	Ericsson
R2-2304133	CSI-RS resource coordination in NR-DC	Nokia, Nokia Shanghai Bell
R2-2304135	CSI-RS resource coordination in NR-DC	Nokia, Nokia Shanghai Bell
R2-2304138	CSI-RS resource coordination in NR-DC	Nokia, Nokia Shanghai Bell
R2-2304140	CSI-RS resource coordination in NR-DC	Nokia, Nokia Shanghai Bell
R2-2304438	Report of [AT121bis-e][003][NR1516] RRC 2 (Samsung)	Samsung Electronics Co., Ltd
R2-2304440	Clarification on nas-SecurityParamFromNR field description	Ericsson, Nokia, Nokia Shanghai Bell
R2-2304441	Clarification on nas-SecurityParamFromNR field description	Ericsson, Nokia, Nokia Shanghai Bell
R2-2304442	Clarification on nas-SecurityParamFromNR field description	Ericsson, Nokia, Nokia Shanghai Bell
R2-2304504	Clarification on RSSI measurement frequency	Samsung
R2-2304505	Clarification on RSSI measurement frequency	Samsung
R2-2304518	Correction on Need code of IE RLC-Config	Intel Corporation
R2-2304519	Correction on Need code of IE RLC-Config	Intel Corporation
R2-2304532	Correction on the need code for secondary DRX group	Huawei, HiSilicon, Ericsson
R2-2304533	Correction on the need code for secondary DRX group	Huawei, HiSilicon, Ericsson
R2-2304535	Clarifications on CG Parameters in NR-U	vivo
R2-2304536	Clarifications on CG Parameters in NR-U	vivo
R2-2304542	Corrections on refServCellIndicator	ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2304543	Corrections on refServCellIndicator	ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2304544	Corrections on refServCellIndicator	ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2304545	[AT121bis-e][002][NR1516] RRC 1	Ericsson
R2-2304546	SIB and PosSIB mappings to SI message	Ericsson, MediaTek Inc.
R2-2304547	SIB and PosSIB mappings to SI message	Ericsson, MediaTek Inc.

5.1.3.2: UE capabilities

TDoc	Title	Source
R2-2302437	LS on clarification on impact of SRS antenna switching for TDD-FDD band combinations (R4-2303633; contact: Huawei)	RAN4
R2-2303660	Handling of SRS Tx switching capability	Ericsson
R2-2303877	Miscellaneous Correction on UE capability-R15	ZTE Corporation, Sanechips
R2-2303878	Miscellaneous Correction on UE capability-R16	ZTE Corporation, Sanechips
R2-2303879	Miscellaneous Correction on UE capability-R17	ZTE Corporation, Sanechips
R2-2303880	Correction on PDCCH Blind Detection-R16	ZTE Corporation, Sanechips
R2-2303881	Correction on PDCCH Blind Detection-R17	ZTE Corporation, Sanechips
R2-2304161	Correction on pusch-RepetitionTypeB capability	Huawei, HiSilicon
R2-2304162	Correction on pusch-RepetitionTypeB capability	Huawei, HiSilicon
R2-2304163	Correction on pusch-RepetitionTypeB capability	Huawei, HiSilicon
R2-2304164	Correction on pusch-RepetitionTypeB capability	Huawei, HiSilicon
R2-2304165	Corrections on NR-DC capabilities	Huawei, HiSilicon
R2-2304166	Corrections on NR-DC capabilities	Huawei, HiSilicon
R2-2304448	Summary of offline [AT121bis-e][004][NR1516] UE cap (ZTE)	ZTE, Sanechips
R2-2304449	Miscellaneous Correction on UE capability-R15	ZTE Corporation, Sanechips
R2-2304450	Miscellaneous Correction on UE capability-R16	ZTE Corporation, Sanechips
R2-2304451	Miscellaneous Correction on UE capability-R17	ZTE Corporation, Sanechips
R2-2304464	Correction on pusch-RepetitionTypeB capability	Huawei, HiSilicon
R2-2304465	Correction on pusch-RepetitionTypeB capability	Huawei, HiSilicon

5.2: NR V2X

TDoc	Title	Source
R2-2302415	Reply LS to RAN4 on PSFCH configured power with multiple resource pools (R1-2302231; contac: LGE)	RAN1
R2-2302574	Left issue on SL CG clear during MAC-reset	OPPO
R2-2302799	Correction to sl-MaxTransPower	Nokia, Nokia Shanghai Bell
R2-2303157	Correction on PSFCH configured power for NR sidelink	CATT
R2-2303158	Correction on PSFCH configured power for NR sidelink	CATT
R2-2303210	Discussion on clear of SL CG upon MAC reset	Xiaomi
R2-2303211	Correction on PSFCH reception for NR sidelink	Xiaomi
R2-2303212	Correction on PSFCH reception for NR sidelink	Xiaomi
R2-2303632	TS 38.331 correction on carrier frequency for SL-RSRP measurement	Huawei, HiSilicon
R2-2303633	TS 38.331 correction on carrier frequency for SL-RSRP measurement	Huawei, HiSilicon
R2-2303742	Summary on user plane corrections for NR V2X	LG Electronics France
R2-2303906	Correction on field description for transmission power	ZTE Corporation, Sanechips
R2-2303909	Correction on field description for transmission power	ZTE Corporation, Sanechips
R2-2303912	Clarification on sl-MaxTransPower	vivo
R2-2303913	Clarification on sl-MaxTransPower	vivo
R2-2303915	Corrections on MAC reset regarding configured sidelink grant	ASUSTeK, Huawei, HiSilicon, Samsung, vivo
R2-2303928	Corrections on MAC reset regarding configured sidelink grant	ASUSTeK, Huawei, HiSilicon, Samsung, vivo
R2-2304078	Correction for Measurement Event Triggering Criteria	Sharp Corporation
R2-2304144	TS 38.331 correction on carrier frequency for SL-RSRP measurement	Huawei, HiSilicon
R2-2304145	TS 38.331 correction on carrier frequency for SL-RSRP measurement	Huawei, HiSilicon
R2-2304148	Summary on control plan corrections for NR V2X	Huawei, HiSilicon
R2-2304216	Summary on [AT121bis-e][501][V2X/SL] R16 RRC corrections (Huawei)	Huawei, HiSilicon
R2-2304217	Corrections including field description for transmission power	Huawei, HiSilicon (Rapporteur), ZTE Corporation, Sanechips, CATT
R2-2304218	Corrections including field description for transmission power	Huawei, HiSilicon (Rapporteur), ZTE Corporation, Sanechips, CATT
R2-2304219	Summary on [AT121bis-e][502][V2X/SL] Clear SL CG (ASUSTeK)	ASUSTeK
R2-2304237	Corrections on MAC reset regarding configured sidelink grant	ASUSTeK, Huawei, HiSilicon, Samsung, vivo

5.3.1: General and Stage 2 corrections

TDoc	Title	Source
R2-2303030	Yaw and APC clarifications for SSR positioning	Swift Navigation, Ericsson
R2-2303032	Zero Yaw and APC clarifications for SSR positioning	Swift Navigation
R2-2303658	GNSS PCO and PCV error analysis	u-blox AG
R2-2304044	LS on SSR orbit and clock correction reference for BDS in 3GPP LPP	RAN2
R2-2304045	Report from [Post121][401][POS] LS to RTCM on SSR orbit and clock correction reference for BDS (Ericsson)	Ericsson
R2-2304283	[AT121bis-e][408][POS] Yaw and APC (Swift)	Swift Navigation (Rapporteur)
R2-2304284	[AT121bis-e][409][POS] LS to RTCM (Ericsson)	Ericsson
R2-2304308	APC clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304309	APC clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304310	APC clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304311	APC clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304312	APC clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304313	APC clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304314	Zero Yaw clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304315	Zero Yaw clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304316	Zero Yaw clarification for SSR positioning	Swift Navigation, Ericsson
R2-2304317	Zero Yaw clarification for SSR positioning	Swift Navigation, Ericsson

5.3.2: RRC corrections

TDoc	Title	Source
R2-2302985	Correction on SI update for posSIB-r16	Huawei, HiSilicon
R2-2302986	Correction on SI update for posSIB-r17	Huawei, HiSilicon
R2-2304285	Rel-15/16 positioning stage 3 CRs	ZTE Corporation (Rapporteur)

5.3.3: LPP corrections

TDoc	Title	Source
R2-2302989	Correction to nr-DL-TDOA-AdditionalMeasurements-r16	Huawei, HiSilicon
R2-2302990	Correction to nr-DL-TDOA-AdditionalMeasurements-r17	Huawei, HiSilicon
R2-2304046	Correction of Location Server behaviour	Ericsson
R2-2304047	Correction of Location Server behaviour	Ericsson
R2-2304048	Correction of Location Server behaviour	Ericsson
R2-2304455	Correction to nr-DL-TDOA-AdditionalMeasurements-r17	Huawei, HiSilicon
R2-2304456	Correction of Location Server behaviour	Ericsson

5.3.4: MAC corrections

TDoc	Title	Source
R2-2303501	Correction on DL MAC CE for SP Positioning SRS	ZTE Corporation
R2-2303502	Correction on DL MAC CE for SP Positioning SRS	ZTE Corporation

5.4.3: RRC corrections

TDoc	Title	Source
R2-2302942	Clarification on RLF Cause	Samsung
R2-2302943	Clarification on RLF cause (Option 1)	Samsung
R2-2302952	Clarification on RLF cause (Option 2)	Samsung
R2-2303447	Correction on logging RLM resources in the RLF report	Ericsson, Qualcomm
R2-2303448	Correction on logging RLM resources in the RLF report	Ericsson, Qualcomm
R2-2303449	Correction to the setting of locationInfo in MeasResultSCG-Failure	Ericsson
R2-2303450	Correction to the setting of locationInfo in MeasResultSCG-Failure	Ericsson
R2-2303897	Discussion on location configuration for SON and MDT features	Huawei, HiSilicon

6.1.1: Stage 2 and Organisational

TDoc	Title	Source
R2-2302416	Reply LS on PDCCH skipping (R1-2302151; contact: MediaTek)	RAN1
R2-2302427	LS on Rel-17 RAN4 UE feature list for NR (R4-2300820; contact: CMCC)	RAN4
R2-2302453	LS on Mapping of F1-C IP addresses in the IAB inter-CU topology adaptation and backhaul RLF recovery procedures (S3-231603; contact: Qualcomm)	SA3
R2-2302454	LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#112 (R1-2302026; contact: NTT DOCOMO, AT&T)	RAN1
R2-2302456	Reply LS to RAN2 on further questions on feMIMO RRC parameters (R1-2302249; cintact: ZTE)	RAN1

6.1.2: User Plane corrections

TDoc	Title	Source
R2-2302659	Correction on separate initial BWP configuration for SDT initialization	vivo, Guangdong Genius
R2-2302660	Correction on SDT with separate initial BWP	vivo, Huawei, HiSilicon, Guangdong Genius
R2-2303136	Corrections on SDT using NCD-SSB for RedCap	Huawei, HiSilicon
R2-2303686	Correction on HARQ buffer flush at SCG deactivation	Nokia, Nokia Shanghai Bell
R2-2303756	CR for Miscellaneous Corrections for SDT operation	LG Electronics Inc.
R2-2303916	Corrections on interruption of random access procedure for SpCell BFR	ASUSTeK
R2-2304057	CR for Miscellaneous Corrections for initial BWP	LG Electronics.
R2-2304356	Summary of [AT121bis-e][301][R15-17 UP] UP related correction (LG)	LG Electronics (Rapporteur)
R2-2304443	Corrections on SDT using NCD-SSB for RedCap	Huawei, HiSilicon

6.1.3.1: NR RRC

TDoc	Title	Source
R2-2302405	LS to RAN2 on reference subcarrier spacing for FR2-2 (R1- 2302185; contact: Nokia)	RAN1
R2-2302408	LS to RAN2 on K2 indication for multi-PUSCH scheduling (R1-2302144; contact: LGE)	RAN1
R2-2302457	Reply LS on questions on RAN visible QoE (R3-226778; contact: Huawei)	RAN3
R2-2302529	Clarification on offset for cell specific RSRP thresholds for 1Rx Redcap UE	OPPO
R2-2302541	RRC correction on BFD/RLM relaxation	OPPO
R2-2302553	Discussion on MN Handover While the SCG is Deactivated	CATT
R2-2302554	Correction on scg-State in RRCConnectionReconfiguration including the mobilityControlInfo	CATT
R2-2302658	Correction on measCyclePSCell used during SCG deactivation	vivo, Ericsson, Guangdong Genius
R2-2302691	Miscellaneous corrections for Ext71GHz	Huawei, HiSilicon
R2-2302773	Clarification for configured grant periodicity	Nokia, Nokia Shanghai Bell
R2-2302800	Correction on RLM/BFD relaxation state reporting	Nokia, Nokia Shanghai Bell
R2-2302842	Correction to RRC for 71 GHz on channel occupancy duration	Ericsson
R2-2303021	Clarification to TS 38.331 on Enhanced BFR MAC CE for feMIMO	CATT
R2-2303057	The restriction addition for SCS in CO-DurationPerCell	NEC Corporation
R2-2303125	CO-Durations Reference subcarrier spacing for FR2-2	Nokia, Nokia Shanghai Bell
R2-2303133	Corrections on initial BWP configuration for RedCap	Huawei, HiSilicon
R2-2303134	Corrections on NCD-SSB for RedCap	Huawei, HiSilicon
R2-2303135	Corrections on RRM relaxation for RedCap	Huawei, HiSilicon, OPPO
R2-2303195	On aperiodic MUSIM gap handling during handover	Nokia, Nokia Shanghai Bell
R2-2303262	Discussion on MUSIM gap handling during handover	vivo
R2-2303286	Clarification on cell barring indications for RedCap UEs	ZTE Corporation, Sanechips
R2-2303287	Correction on cellBarredRedCap2Rx	ZTE Corporation, Sanechips
R2-2303346	Corrections on the unified TCI-state configuration for 38.331	Xiaomi
R2-2303467	Clarification on SubgroupID for UE_ID based subgrouping in RRC_INACTIVE state	Huawei, HiSilicon
R2-2303472	Discussion on RAN1 LS R1-2302144	Ericsson
R2-2303557	Correction to RRC for 71 GHz on multi-PUSCH	Ericsson
R2-2303616	Corrections for eDRX in RRC_INACTIVE	Ericsson
R2-2303617	RLM and BFD relaxation when SCG is deactivated	Ericsson
R2-2303661	Handling of MUSIM Scheduling Gap During Handover	Ericsson
R2-2303662	MN Handover with deactivated SCG	Ericsson
R2-2303679	Correction CR for QoE measurements in NR	Ericsson
R2-2303770	Discussion on CHO with T346g in MUSIM	Lenovo
R2-2303771	Correction on CHO execution while T346g is running	Lenovo
R2-2303814	Correction on application layer measurement configuration resume	Google
R2-2303831	Further discussion on handling of aperiodic MUSIM gap	Samsung Electronics Austria
R2-2303876	Further Clarification on the MUSIM Gap Handling During Handover	ZTE Corporation, Sanechips
R2-2303917	Correction K2 on multi-PUSCH scheduling	ASUSTeK
R2-2303918	Correction on condition for extendedK2	ASUSTeK
R2-2303942	Clarification on K2 indication for multi-PUSCH scheduling	LG Electronics Inc.
R2-2304012	Issues on dedicated configuration of RedCap-specific initial BWP	LG Electronics Inc.
R2-2304087	Corrections to on-demand SI request	ZTE Corporation, Sanechips
R2-2304125	Clarification for configured grant periodicity	Nokia, Nokia Shanghai Bell
R2-2304213	Summary of [AT121bis-e][005][NR17] CP Redcap Corrections (Huawei)	Huawei, HiSilicon
R2-2304326	Corrections for eDRX in RRC_INACTIVE	Ericsson, Huawei, HiSilicon
R2-2304436	Corrections on initial BWP configuration and NCD-SSB for RedCap	Huawei, HiSilicon
R2-2304437	Corrections on NCD-SSB for RedCap	Huawei, HiSilicon
R2-2304475	Corrections to on-demand SI request	ZTE Corporation, Sanechips
R2-2304483	Miscellaneous corrections for Ext71GHz	Huawei, HiSilicon
R2-2304485	Report of [AT121bis-e][009][NR17] RRC Misc Corrections (ZTE)	ZTE Corporation (Rapporteur)
R2-2304517	Report of [AT121bis-e][008][NR17] RRC MUSIM Corrections	vivo
R2-2304539	Clarification to TS 38.331 on Enhanced BFR MAC CE for feMIMO	CATT
R2-2304549	LS on unified TCI-state and fast Scell activation	RAN2
R2-2304551	Correction on scg-State in RRCConnectionReconfiguration including the mobilityControlInfo	CATT
R2-2304554	Correction to RRC for 71 GHz on multi-PUSCH	Ericsson
R2-2304555	Correction to RRC for 71 GHz on channel occupancy duration	Ericsson
R2-2304556	Correction on measCyclePSCell used during SCG deactivation	vivo, Ericsson, Huawei, HiSilicon
R2-2304560	Summary of [AT121bis-e][005][NR17] CP Redcap Corrections (Huawei)	Huawei, HiSilicon
R2-232466	Clarification on offset for cell specific RSRP thresholds for 1Rx Redcap UE	OPPO
R2-232478	RRC correction on BFD/RLM relaxation	OPPO

6.1.3.2: UE capabilities

TDoc	Title	Source
R2-2302435	Reply LS on clarification for ue-PowerClassPerBandPerBC-r17 (R4 16-8) (R4-2303630; contact: Samsung)	RAN4
R2-2302436	Reply LS on new contiguous BW classes for legacy networks (R4-2303631; contact: Nokia)	RAN4
R2-2302439	LS on UE signalling for the maximum aggregated bandwidth for FR1 CA (R4-2303685; contact: Qualcomm)	RAN4
R2-2302440	LS on signaling for FR2 FBG5 CA BW classes (R4-2303689; contact: Apple)	RAN4
R2-2302575	Discussion on ue-PowerClassPerBandPerBC-r17	OPPO
R2-2302577	Discussion on maximum aggregated bandwidth	OPPO
R2-2302727	Summary of email discussion [Post121][043][NR17] Intraband ENDC UE cap	Qualcomm Incorporated
R2-2302728	DRAFT Reply LS on intraBandENDC-Support	Qualcomm Incorporated
R2-2302729	Maximum aggregated bandwidth for FR1 CA	Qualcomm Incorporated
R2-2302774	Clarification to description of independentGapConfig-maxCC-r17 [MaxCCPerFRGap]	Nokia, Nokia Shanghai Bell
R2-2302887	Clarifying band combination meaning for DMRS Bundling over TBoMS	Ericsson
R2-2302941	Clarification on ue-PowerClassPerBandPerBC	Samsung
R2-2303398	On servicing RAN4 request on aggregate BW signaling for FBG5 CA BW classes	Apple Inc, Ericsson Inc
R2-2303882	Miscellaneous Correction on UE capability-R17	ZTE Corporation,Sanechips
R2-2303883	Consideration on the FBG5 Signaling	ZTE Corporation, Sanechips
R2-2304167	Introduction of intra-band EN-DC contiguous capability for UL	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell
R2-2304168	Introduction of intra-band EN-DC contiguous capability for UL	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell
R2-2304169	Discussion on UE signaling for the maximum aggregated bandwidth	Huawei, HiSilicon
R2-2304431	Reply LS on intraBandENDC-Support	RAN2
R2-2304444	Summary of [AT121bis-e][011][NR17] UE Caps BW related Corrections (Qualcomm)	Qualcomm Incorporated
R2-2304452	Miscellaneous Correction on UE capability-R17	ZTE Corporation, Sanechips
R2-2304482	Clarifying band combination meaning for DMRS Bundling over TBoMS	Ericsson
R2-2304486	[AT121bis-e][010][NR17] UE Caps Misc Corrections (Samsung)	Samsung

6.1.3.3: Other

TDoc	Title	Source
R2-2302861	Relation between slice-based reselection information provided in dedicated signalling and SIB16	Nokia, Nokia Shanghai Bell
R2-2302862	Addition of slice-based cell re-selection parameters	Nokia, Nokia Shanghai Bell
R2-2302983	Discussion on reselection priorities in dedicated and broadcast signalling	CATT
R2-2303003	Correction to TS 38.321 on IAB beam management and DL Tx power adjustment	ZTE, Sanechips
R2-2303204	Report from email discussion [Post121][042][NR17] Stage 2 description for IAB beam management and power control (Lenovo)	Lenovo
R2-2303205	Introduction of stage 2 description for IAB resource management	Lenovo, Ericsson
R2-2303479	Corrections on the eIAB related capabilities	Huawei, HiSilicon
R2-2303480	Correction to MAC reset for eIAB	Huawei, HiSilicon
R2-2303637	Slice-based re-selection based on dedicated signalling only	Ericsson
R2-2303638	Slice-based re-selection based on dedicated signalling only	Ericsson
R2-2303740	Essentiality of SIB16 in RAN Slicing	Apple, OPPO
R2-2303900	Discussion on remaining issues for RAN Slicing	Huawei, HiSilicon
R2-2304039	Correction on handling on slice availabiliy in SIB16 in TS 38.304	CATT
R2-2304041	Availability of NSAG-Frequency pair present only in dedicated signaling	Samsung R&D Institute India
R2-2304097	Correction to restricted resources for eIAB	Ericsson
R2-2304215	Summary of [AT121bis-e][013][NR17] IAB Corrections	Huawei, HiSilicon
R2-2304439	Correction to restricted resources for eIAB	Ericsson
R2-2304524	Report from [AT121bis-e][012][NR17] Slicing Corrections (Nokia)	Nokia (Rapporteur)
R2-2304525	Correction on handling on slice availabiliy in SIB16 in TS 38.304	CATT, Nokia, Samsung
R2-2304526	Clarification on applicability of slice-based RA	Huawei, Nokia
R2-2304527	Clarification on the application of slice-based RACH configuration	Nokia, Huawei

6.2.1: Organizational and Stage-2 corrections

TDoc	Title	Source
R2-2302406	Reply LS on SPS configuration for unicast and multicast (R1- 2302209; contact: ASUSTek)	RAN1
R2-2303126	General MBS CR to 38.300	Nokia, Nokia Shanghai Bell
R2-2303618	Clarifications for MBS broadcast service continuity	Ericsson
R2-2304154	MBS broadcast reception via unicast	Ericsson
R2-2304324	General MBS CR to 38.300	Nokia, Nokia Shanghai Bell
R2-2304325	[AT121bis-e][602][MBS-R17] Stage-2 and UP issues (Nokia)	Nokia (Rapporteur)
R2-2304566	[AT121bis-e][007][NR17] RRC UpTo71GHz Corrections (Nokia)	Nokia (Rapporteur)

6.2.2: CP corrections

TDoc	Title	Source
R2-2302520	Remaining issues on Supporting MBS in SNPN	CATT
R2-2302521	Corrections to TS 38.331	CATT
R2-2302522	Remaining issues on Supporting MBS in SNPN	CATT, CBN
R2-2302523	Corrections to TS 38.331	CATT, CBN
R2-2302590	Correction to PDSCH Aggregation of MBS SPS	vivo
R2-2302823	CP Corrections for MBS	Samsung Electronics Co., Ltd
R2-2303031	Clarification on Key Refresh in MBS	vivo
R2-2303127	General MBS CR to 38.331	Nokia, Nokia Shanghai Bell
R2-2303552	Misc correction to TS 38.331 on NR MBS	ZTE, Sanechips
R2-2303619	Corrections for MBS with eDRX and MICO mode	Ericsson
R2-2303919	Corrections on MBS SPS configuration	ASUSTeK
R2-2303966	Miscellaneous RRC corrections for MBS	Huawei, HiSilicon
R2-2303967	Discussion on the remainning MBS issues	Huawei, HiSilicon
R2-2304146	Editorial modification to TS 38.331 on NR MBS	MediaTek inc.
R2-2304170	Editorial modification to TS 38.331 on NR MBS	MediaTek inc.
R2-2304321	Miscellaneous RRC corrections for MBS	Huawei, HiSilicon
R2-2304322	Correction on MBS capabilities	Huawei, HiSilicon
R2-2304323	Corrections to TS 38.331	CATT, CBN
R2-2304327	Report of [AT121bis-e][601][MBS-R17] CP issues (Ericsson)	Ericsson
R2-2304329	Misc correction to TS 38.331 on NR MBS	ZTE, Sanechips
R2-2304447	Correction to PDSCH Aggregation of MBS SPS	vivo
R2-2304469	Correction on Supporting MBS in SNPN	CATT, CBN
R2-2304470	CP Corrections for MBS	Samsung
R2-2304550	Corrections on MBS SPS configuration	ASUSTeK
R2-2304557	Correction to PDSCH Aggregation of MBS SPS	vivo
R2-2304558	Correction on Supporting MBS in SNPN	CATT, CBN

6.2.3: UP corrections

TDoc	Title	Source
R2-2302767	Corrections on cfr-ConfigMulticast and Multicast DRX	NEC Corporation, LG Electronics Inc, Nokia, Nokia Shanghai Bell, Samsung
R2-2302768	Discussion on the correction for cfr-ConfigMulticast and Multicast DRX	NEC Corporation, LG Electronics Inc, Nokia, Nokia Shanghai Bell, Samsung
R2-2303067	UP Corrections for MBS	Samsung R&D Institute India
R2-2304528	Corrections on SPS Initialization and Handling of Unknown, Unforeseen and Erroneous Protocol Data for MBS	Samsung
R2-2304561	Corrections on cfr-ConfigMulticast and Multicast DRX	NEC, LG Electronics Inc, Nokia, Nokia Shanghai Bell, Samsung

6.3.2: User Plane

TDoc	Title	Source
R2-2303920	Discussion on one-shot HARQ feedback	ASUSTeK
R2-2303921	Corrections on DRX for one shot HARQ feedback	ASUSTeK, Nokia, Nokia Shanghai Bell

6.4.1: User plane common aspects

TDoc	Title	Source
R2-2302664	Clarification on RA Resource Selection During CG-SDT	vivo
R2-2302988	Correction to CG-SDT LCH restriction	Huawei, HiSilicon
R2-2303699	Clarifying HD-FDD CG-SDT	Ericsson
R2-2304179	Correction to RA-SDT initiation	Google Inc.
R2-2304351	Correction to CG-SDT LCH restriction	Huawei, HiSilicon
R2-2304355	Report: [AT121bis-e][302][R17 SDT] SDT related correction (ZTE)	ZTE Corporation (rapporteur)
R2-2304446	Clarification on RA Resource Selection During CG-SDT	vivo. ZTE Corporation (rapporteur), Sanechips
R2-2304481	LS on Monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs, Ericsson	Ericsson
R2-2304562	LS on Monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs	RAN2

6.4.2: Control plane common aspects

TDoc	Title	Source
R2-2302665	Correction on UAI Reporting During SDT	vivo
R2-2303056	Correction on the restriction to periodicityExt	NEC Corporation
R2-2303594	Control plane corrections for SDT	Huawei, HiSilicon
R2-2303687	Clarification on RRCReject handling with UL data	Nokia, Nokia Shanghai Bell
R2-2303688	Clarification on unknown, unforeseen and erroneous protocol data	Nokia, Nokia Shanghai Bell
R2-2304352	Control plane corrections for SDT	Huawei, HiSilicon

6.5.1: General and stage 2 corrections

TDoc	Title	Source
R2-2303154	Correction on Direct to Indirect Path Switching	CATT
R2-2303155	Correction on the PC5 unicast link release in case of indirect to direct path switching	CATT
R2-2303384	Miscellaneous corrections for Stage 2 NR sidelink relay	Apple
R2-2303858	Corrections on relay (re)selection	ZTE Corporation, Sanechips

6.5.2: Control plane corrections

TDoc	Title	Source
R2-2302576	Discussion on paging monitoring by SL L2 U2N Relay	OPPO
R2-2302593	Corrections to paging monitoring via Relay UE	Samsung Electronics Co., Ltd
R2-2302594	38.331_CR_Corrections to paging monitoring via Relay UE	Samsung Electronics Co., Ltd
R2-2303115	Correction on 38.331	Xiaomi
R2-2303156	Correction on Field Description of Common Resource Pool	CATT
R2-2303175	Miscellaneous corrections to TS 38.331 for SL relay	ZTE Corporation, Sanechips
R2-2303176	Corrections on sorting quantity of Event X1 for SL relay	ZTE Corporation, Sanechips
R2-2303337	Correction on PC5 RLC channel release trigger due to SL RLF	vivo
R2-2303338	Correction on SRB0 handling when UE is acting as L2 U2N Remote UE	vivo
R2-2303385	Corrections on UE handling of Layer 2 UE-to-NW relay configurations	Apple
R2-2303386	Discussion on SRAP configuration in RRCReestablishment	Apple
R2-2303489	Clarification on sidelink communication resource configuration used by OoC L2 Remote UE	Huawei, HiSilicon
R2-2303656	Miscellaneous corrections to 38331	Nokia, Nokia Shanghai Bell
R2-2303739	Correction on L2 U2N Relay Remote UE RRC procedure	Philips International B.V.
R2-2303922	Correction on role of a L2 U2N Remote UE	ASUSTeK
R2-2303983	Correction on remote UE�s behavior upon SIB1 reception	Xiaomi
R2-2304066	Correction on Cell Barring for L2 U2N Remote UE	Ericsson Espa�a S.A.
R2-2304189	Summary of agenda item 6.5.2 on control plane corrections (Huawei)	Huawei
R2-2304291	[AT121bis-e][416][Relay] Paging monitoring by L2 relay (OPPO)	OPPO
R2-2304299	Report of [AT121bis-e][425][Relay] Rel-17 relay CP CRs (Huawei)	Huawei, HiSilicon
R2-2304466	Miscellaneous corrections for SL relay	Huawei, HiSilicon, CATT, ZTE Corporation, Sanechips, vivo, Apple, Nokia, Nokia Shanghai Bell, Philips International B.V.
R2-2304467	Clarification on sidelink communication resource configuration used by OoC L2 Remote UE	Huawei, HiSilicon
R2-2304508	Clarification on sidelink communication resource configuration used by OoC L2 Remote UE	Huawei, HiSilicon

6.5.3: User plane corrections

TDoc	Title	Source
R2-2302974	Corrections on SRAP for SL relay	NEC Corporation
R2-2303490	Clarification on the services expected from SRAP layer	Huawei, HiSilicon
R2-2303491	Clarification on the maximum Data field size for L2 U2N relay	Huawei, HiSilicon
R2-2304036	Corrections on SRAP for SL relay	NEC
R2-2304191	Summary of agenda item 6.5.3 (Samsung)	Samsung
R2-2304479	Summary of Relay-17 relay UP CR (Samsung)	Samsung
R2-2304480	Corrections on SRAP for SL relay	NEC, Apple, Samsung, ZTE

6.6.1: General and Stage 2 corrections

TDoc	Title	Source
R2-2302540	NTN stage-2 correction	OPPO, Ericsson, Thales
R2-2302654	Corrections to 38.300 related to Section Scheduling and Timing	THALES
R2-2302765	Corrections to 38.300 related to Section Scheduling and Timing	THALES
R2-2303764	Correction on Stage-2 descriptions for NR NTN	Samsung
R2-2303835	Correction for R17 NR NTN	Ericsson
R2-2304251	Summary of [AT121bis-e][111][NR NTN] Stage 2 corrections (OPPO)	OPPO
R2-2304259	NTN stage-2 correction	OPPO, Ericsson, Thales, Samsung
R2-2304268	NTN stage-2 correction	OPPO, Ericsson, Thales, Samsung
R2-232477	Stage-2 correction on Kmac	OPPO

6.6.2: UP corrections

TDoc	Title	Source
R2-2303413	Clarification on UL operation upon validity timer expiry	Apple
R2-2303820	Corrections to NR NTN for 38.321	CATT, Turkcell, Huawei, HiSilicon, Quectel, CAICT
R2-2303833	Correction for R17 NR NTN description of HARQ mode	Ericsson
R2-2303960	UE behaviour related to SR and RACH after validity timer expires	Huawei, HiSilicon
R2-2303979	Corrections on MAC procedure upon validity timer expiry for NR NTN	Nokia, Nokia Shanghai Bell
R2-2304000	Discussion on the restriction on the usage of the same HARQ mode to the configured grant	LG Electronics Inc.
R2-2304001	Discussion on the UE behaviour when the validity timer expires	LG Electronics Inc.
R2-2304242	Report of [AT121bis-e][102][NR NTN] UP corrections (Apple)	Apple
R2-2304263	Corrections to NR NTN for 38.321	CATT, Turkcell, Huawei, HiSilicon, Quectel, CAICT, Ericsson
R2-2304266	Clarification on UL operation upon validity timer expiry	Apple, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, LG Electronics Inc.

6.6.3: CP corrections

TDoc	Title	Source
R2-2302693	Correction on NR NTN UE capabilities	Intel Corporation
R2-2302755	Correction to 38.331 for kmac definition	THALES
R2-2302868	Features with different UE capability support in TN and NTN	Intel Corporation
R2-2303034	Clarification on TN EUTRA capability reporting	Qualcomm Incorporated
R2-2303035	Clarification on rounding the propagation delay difference value	Qualcomm Incorporated
R2-2303096	Remaining issues on SMTC	Huawei, HiSilicon, Google
R2-2303164	Correction to indicate the NTN cells belonging to the same satellite	Nokia, Nokia Shanghai Bell
R2-2303296	Conditions to Skip Neighbor Cell Measurement in NTN	Google Inc.
R2-2303412	Clarification on the relationship between SMTC and satellite	Apple
R2-2303460	Corrections for RLC-Config in TS 38.331	vivo
R2-2303461	Correction on Event D1 for Rel-17 NTN	vivo
R2-2303671	Correction on missing referencing of the NTN spec in 38.306	MediaTek
R2-2303675	Correction on missing referencing of the NTN spec in 38.331	MediaTek
R2-2303765	Correction on SMTC for NR NTN	Samsung
R2-2303785	Clarification on feature configurations upon TN NTN mobility in RRC_INACTIVE	Ericsson
R2-2303819	Discussion on SFTD Application for NTN cell	CATT
R2-2303923	Clarification on T430 handling for target cell	ASUSTeK, Samsung, Huawei, HiSilicon
R2-2303924	Correction on MIB configuration for NR NTN	ASUSTeK
R2-2304252	Report of [AT121bis-e][112][NR NTN] CP corrections 1 (Huawei)	Huawei, HiSilicon
R2-2304253	Report of [AT121bis-e][112][NR NTN] CP corrections 1 (Huawei)	Huawei, HiSilicon
R2-2304264	Correction on SMTC for NR NTN	Samsung, Huawei, HiSilicon, Google
R2-2304265	Correction on missing referencing of the NTN spec in 38.306	MediaTek
R2-2304269	Clarification on TN EUTRA capability reporting	Qualcomm Incorporated
R2-2304272	Report of email discussion [AT121bis-e][113][NR NTN] UE capabilities (Intel)	Intel Corporation

6.7.1: General and stage 2 corrections

TDoc	Title	Source
R2-2302404	LS on GNSS integrity requirement parameters definition (C4-230655; contact: Huawei)	CT4
R2-2302429	Reply LS on applicability of timing error margin of Rx TEG (R4-2303244; contact: CATT)	RAN4
R2-2302637	Miscellaneous corrections on 38.305	CATT
R2-2302744	Stage 2 procedure for deactivation of MG gap and PPW	Intel Corporation
R2-2302993	Correction to UEPositioningAssistanceInformation	Huawei, HiSilicon
R2-2304052	Update of information transfer from gNB to LMF	Ericsson
R2-2304053	Measurements and Assistance Data Transfer	Nokia, Nokia Shanghai Bell
R2-2304054	Protection Level and Target Integrity Risk	Nokia, Nokia Shanghai Bell
R2-2304178	Reply LS on GNSS integrity requirements parameters	Huawei, HiSilicon, Ericsson
R2-2304286	Offline [AT121bis-e][411] on Rel-17 Positioning Stage-2 CRs	Nokia (Rapporteur)
R2-2304292	[AT121bis-e][417][POS] LS on GNSS integrity parameters (Huawei)	Huawei, HiSilicon
R2-2304307	Reply LS on GNSS integrity requirement parameters definition	Huawei
R2-2304457	Update of information transfer from gNB to LMF	Ericsson
R2-2304463	Stage 2 procedure for deactivation of MG gap and PPW	Intel Corporation
R2-2304494	Measurements and Assistance Data Transfer	Nokia, Nokia Shanghai Bell
R2-2304495	Protection Level and Target Integrity Risk	Nokia, Nokia Shanghai Bell
R2-2304516	Miscellaneous corrections on 38.305	CATT
R2-2304540	Correction to UEPositioningAssistanceInformation	Huawei, HiSilicon

6.7.2: RRC corrections

TDoc	Title	Source
R2-2302638	Corrections on the figure of UE Positioning Assistance Information procedure	CATT
R2-2302992	Correction to UE positioning assistance information	Huawei, HiSilicon
R2-2304281	Corrections on the figure of UE Positioning Assistance Information procedure	CATT

6.7.3: LPP corrections

TDoc	Title	Source
R2-2302639	Corrections on applicability of timing error margin of RxTEG in NR-Multi-RTT-SignalMeasurementInformation field descriptions	CATT
R2-2302884	Miscellaneous corrections on LPP	Lenovo
R2-2302987	Correction to PRS validity area	Huawei, HiSilicon
R2-2304050	Missing LPP support for sub 1s location information reporting periodicity	Ericsson
R2-2304051	Missing finer periodicities than 1s	Ericsson
R2-2304055	Use of nr-DL-PRS-ExpectedAoD-or-AoA assistance by UE	Nokia, Nokia Shanghai Bell
R2-2304056	LOS-NLOS-Indicator Types	Nokia, Nokia Shanghai Bell
R2-2304139	Use of nr-DL-PRS-ExpectedAoD-or-AoA assistance by UE	Nokia, Nokia Shanghai Bell
R2-2304192	Summary of AI 6.7.3 - NR positioning enhancements, LPP corrections	Qualcomm Incorporated
R2-2304300	Summary of [AT121bis-e][427][POS] Rel-17 LPP CRs	Qualcomm Incorporated
R2-2304496	LOS-NLOS-Indicator Types	Nokia, Nokia Shanghai Bell

6.7.4: MAC corrections

TDoc	Title	Source
R2-2302991	Correction to posSRS transmission in RRC_INACTIVE	Huawei, HiSilicon
R2-2304049	Correction for trigger condition of Scheduling Request	Ericsson, OPPO

6.7.5: UE capabilities

TDoc	Title	Source
R2-2302745	LPP capability for FGs27-13a,14a and 14-2	Intel Corporation
R2-2304462	LPP capability for FGs27-13a,14a and 14-2	Intel Corporation

6.9.1: Stage-2

TDoc	Title	Source
R2-2302451	Reply LS on the user consent for trace reporting (S3-231398; contact: Huawei)	SA3
R2-2302460	LS on Excess Packet Delay Threshold for MDT (S5-232150; contact: Nokia)	SA5
R2-2302863	Correction to NR M3 measurement	Nokia, Nokia Shanghai Bell
R2-2303898	Discussion on the UL PDCP packet average delay measurement of split bearer	Huawei, HiSilicon
R2-2303899	Stage-2 correction on the UL PDCP packet average delay	Huawei, HiSilicon

6.9.3: SON Corrections

TDoc	Title	Source
R2-2302611	Correction on timeSinceCHO-Reconfig in TS 38.331	CATT
R2-2302612	Correction on SCG failure scenario of MHI in TS 38.331	CATT
R2-2302653	Report�of�new�packet�loss�rate	China Unicom
R2-2303451	Correction to the handling of RLF-Report after successful HO	Ericsson
R2-2303452	On including TAC in the SHR	Ericsson
R2-2303646	Correction to timeSCGFailure	Nokia, Nokia Shanghai Bell
R2-2303696	NB-IoT UE location Info in RLF report	Qualcomm Incorporated
R2-2303717	Correction on UE location information in NB-IoT RLF report	Qualcomm Inc.
R2-2304083	38.314 CR for the introduction of packet loss rate with delay threshold	China Unicom, CATT

6.10.1: General and Stage 2 corrections

TDoc	Title	Source
R2-2302410	Reply LS to RAN2 on default CBR configuration (R1-2302174; contact: OPPO)	RAN1
R2-2302684	Corrections on TS 38.300 for SL enhancements	Huawei, HiSilicon
R2-2302839	Correction to 38300 on IUC	Ericsson, Apple
R2-2302840	Correction to 38300 on IUC cast type	Ericsson
R2-2302841	Discussion on RAN1 LS R1-2302174	Ericsson
R2-2303213	Miscellaneous corrections on TS 38.300 for NR sidelink	Xiaomi
R2-2303383	Miscellaneous corrections for Stage 2 NR sidelink enhancements	Apple
R2-2304227	[AT121bis-e][503][V2X/SL] Default CBR configuration (OPPO)	OPPO
R2-2304229	Correction on the usage of default CBR values for NR sidelink	OPPO, Xiaomi, CATT

6.10.2: Control plane corrections

TDoc	Title	Source
R2-2302617	Miscellaneous RRC corrections for the usage of default CBR configuration	CATT
R2-2302683	Miscellaneous corrections on 38.331 for SL enhancements	Huawei, HiSilicon
R2-2302686	Corrections on TS 38.304 for SL enhancements	Huawei, HiSilicon
R2-2302795	On default CBR configuration	Nokia, Nokia Shanghai Bell
R2-2303907	Correction on field description for DRX timer	ZTE Corporation, Sanechips
R2-2303908	Correction on default CBR configuration	ZTE Corporation, Sanechips
R2-2303925	Discussion on deriving timer length for DRX timers	ASUSTeK
R2-2303926	Corrections on deriving timer length for DRX timers - option 1a	ASUSTeK
R2-2303927	Corrections on deriving timer length for DRX timers - option 1b	ASUSTeK, vivo
R2-2304150	Summary on control plane corrections for NR SL enhancements	Huawei, HiSilicon
R2-2304222	Summary on [AT121bis-e][504][V2X/SL] R17 CP Corrections (Huawei)	Huawei, HiSilicon
R2-2304223	Summary on [AT121bis-e][505][V2X/SL] DRX timer numerology (ASUSTeK)	ASUSTeK
R2-2304224	Correction on field description for DRX timer	ZTE Corporation, Sanechips, ASUSTeK, vivo
R2-2304235	Miscellaneous corrections on 38.331 for SL enhancements	Huawei, HiSilicon (Rapporteur), Xiaomi

6.10.3: User plane corrections

TDoc	Title	Source
R2-2302618	Correction on resource (re-)selection for NR sidelink	CATT
R2-2302619	Correction on case for default CBR configuration	CATT
R2-2302647	Discussion on default CBR	OPPO
R2-2302685	Correction on 38.321 for SL enhancements	Huawei, HiSilicon
R2-2302908	SL DRX timers BWP numerology	Nokia, Nokia Shanghai Bell
R2-2303214	Discussion on the usage of default CBR values for NR sidelink	Xiaomi
R2-2303215	Correction on the usage of default CBR values for NR sidelink	Xiaomi
R2-2303743	Summary on user plane corrections for NR SL enhancements	LG Electronics France
R2-2303744	Summary of email discussion [POST121][510][V2XSL] IUC procedure in re-evaluationpre-emptionconflict indicator (LG)	LG Electronics France
R2-2303745	User plane corrections on NR Sidelink enhancements	LG
R2-2304226	Summary of [AT121bis-e][506][V2XSL] R17 MAC Corrections (LG)	LG

6.11: RACH indication and partitioning

TDoc	Title	Source
R2-2302668	Clarification on the Selected Set of RA Resources	vivo

7.1.1: Organizational

TDoc	Title	Source
R2-2302414	LS to RAN2 on the RRC and MAC CE parameters for NCR (R1-2302227; contact: ZTE)	RAN1
R2-2302789	Draft 306 CR of Network controlled repeater UE capability	Intel Corporation
R2-2302790	Draft 331 CR of Network controlled repeater UE capability	Intel Corporation
R2-2303289	RRC running CR for R18 NCR	ZTE Corporation
R2-2303445	Introducing support for Network Controlled Repeaters to 38.321	Samsung
R2-2303901	38.304 running CR for R18 NCR	CATT
R2-2304113	38.300 Running CR for NCR	Ericsson
R2-2304413	38.300 Running CR for NCR	Ericsson
R2-2304414	RRC running CR for R18 NCR	ZTE Corporation
R2-2304415	Introducing support for Network Controlled Repeaters to 38.321	Samsung
R2-2304417	Draft 306 CR of Network controlled repeater UE capability	Intel Corporation
R2-2304418	Draft 331 CR of Network controlled repeater UE capability	Intel Corporation
R2-2304425	Running 38.331 CR for R18 Network-controlled repeaters	ZTE Corporation
R2-2304426	38.304 running CR for R18 NCR	CATT
R2-2304484	Summary of discussion [AT121bis-e][705][NCR] NCR MAC running CR (Samsung)	Samsung

7.1.2: Signalling for side control information

TDoc	Title	Source
R2-2302927	Further issues related to NCR ON/OFF behaviour and side control configuration	Nokia, Nokia Shanghai Bell
R2-2303237	Remaining issues for side control information	Lenovo
R2-2303263	MAC CE Design for Semi-Persistent Beam Configuration	vivo
R2-2303290	Remaining issues in NCR RRC running CR	ZTE Corporation, Sanechips
R2-2303446	Outstanding MAC issues	Samsung R&D Institute UK
R2-2303772	Considerations on signalling for side control information	China Telecom
R2-2303973	Discussion on MAC issues for NCR	Huawei, HiSilicon
R2-2304411	[Pre121bis-e][701][NCR] Summary of AI 7.1.2 on signalling for SCI	ZTE Corporation
R2-2304420	Summary of [AT121bis-e][704][NCR] NCR RRC running CR (ZTE)	ZTE Corporation (Rapporteur)

7.1.3: Other RAN2 aspects

TDoc	Title	Source
R2-2302787	Discussion on NCR remaining open issues	Intel Corporation
R2-2302788	Summary of [Post121][702][NCR] capabilities running CR for NCR (Intel)	Intel Corporation
R2-2302893	Beam reselection by RRC_INACTIVE NCR	Qualcomm Inc.
R2-2302928	RRC release with redirection for NCR	Nokia, Nokia Shanghai Bell
R2-2302944	Discussion on releasing NCR-MT to RRC_IDLE	Fujitsu
R2-2302947	Further discussion on remaining open issues when NCR-MT is in RRC Inactive and RRC idle	NEC
R2-2303238	Discussion on RRC states for NCR-MT	Lenovo
R2-2303264	Remaining Issues of Side Control Information Signaling	vivo
R2-2303276	Remaining issues on NCR	Kyocera
R2-2303288	Report of [Post121][703][NCR] Open issues on NCR RRC	ZTE Corporation
R2-2303291	Discussion on NCR remaining issues	ZTE Corporation, Sanechips
R2-2303387	Discussion on remaining issues for NCR-MT in IDLE/INACTIVE	Apple
R2-2303775	Discussion on remaining issues for NCR	China Telecom
R2-2303944	Cell selection for NR network-controlled repeaters	AT&T
R2-2303974	Discussion on CP issues for NCR	Huawei, HiSilicon
R2-2304004	Handling of NCR failure and reestablishment	Samsung R&D Institute UK
R2-2304015	Further considerations on NCR procedures and Stage 2 corrections	Samsung R&D Institute UK
R2-2304114	Remaining issues for NCR	Ericsson
R2-2304115	Transitioning from IDLE to CONNECTED	Ericsson
R2-2304412	Summary of AI 7.1.3 on other RAN2 aspects for NCR	Nokia, Nokia Shanghai Bell

7.2.1: Organizational

TDoc	Title	Source
R2-2302403	LS on LPP message and supplementary service event report over a user plane connection between UE and LMF (C1-231129; contact: Ericsson)	CT1
R2-2302409	LS Reply on PRU Procedures (R1-2302146; contact: Qualcomm)	RAN1
R2-2302446	LS on the requirement on low power or high accuracy positioning (S2-2303414; contact: Huawei)	SA2
R2-2302448	LS on support of multiple Target UEs (S2-2303837; contact: Qualcomm)	SA2
R2-2302449	LS on PRU procedures (S2-2303861; contact: Qualcomm)	SA2
R2-2302502	Work Plan on Rel-18 Positioning Work Item	CATT, Intel, Ericsson
R2-2302738	Further considerations on SLPP specification	Intel Corporation
R2-2302739	TS 38.355 skeleton	Intel Corporation
R2-2302875	PRU Procedures (draft response LS to R2-2301939 (S2-2303861))	Qualcomm Incorporated
R2-2302957	Discussion and draft LS reply on PRU procedures	vivo
R2-2303513	Support of Multiple Target UEs for Sidelink Positioning	Qualcomm Incorporated
R2-2303707	On the Positioning Reference Units aspects	Ericsson
R2-2304295	Summary of [AT121bis-e][421][POS] Reply LS to SA2 on PRU procedures	Qualcomm Incorporated
R2-2304296	[AT121bis-e][422][POS] SLPP specification baseline (Intel)	Intel Corporation
R2-2304306	TS 38.355 skeleton	Intel Corporation
R2-2304459	Response LS on PRU Procedures	RAN2
R2-2304499	Reply LS to Reply LS to LS on SL positioning groupcast and broadcast (S2-2305726; contact: Xiaomi)	SA2
R2-2304500	Reply LS to LS to SA2 on Sidelink positioning procedure (S2-2305735; contact: Xiaomi)	SA2

7.2.2: Sidelink positioning

TDoc	Title	Source
R2-2302503	Discussion on sidelink positioning	CATT
R2-2302582	Discussion on Sidelink Positioning	Huawei, HiSilicon
R2-2302588	UE Positioning using Sidelink	Fraunhofer IIS, Fraunhofer HHI
R2-2302655	Discussion of signalling procedures	Nokia Germany
R2-2302656	Discussion of session-based and session-less SL positioning	Nokia Germany
R2-2302740	Further considerations on sidelink positioning	Intel Corporation
R2-2302885	Discussion on further SLPP aspects	Lenovo
R2-2302958	Discussion on sidelink positioning	vivo
R2-2302982	Discussion on Anchor UE (Re)discovery and (Re)selection for SL positioning	KT Corp.
R2-2303048	Discussion on SL positioning discovery and selection procedure	Samsung
R2-2303078	Considerations on sidelink positioning resources	Sony
R2-2303131	Discussion on Sidelink Positioning	LG Electronics Inc.
R2-2303186	Further discussion on sidelink positioning	OPPO
R2-2303187	Further discussion on anchor UE reselection for sidelink positioning	OPPO
R2-2303298	On SL Positioning Architecture Aspects	Lenovo
R2-2303365	SL positioning groupcast and broadcast	Apple
R2-2303366	[DARFT] Reply LS on SL positioning groupcast and broadcast	Apple
R2-2303443	View on SL ranging and positioning architecture and signalling procedures	CEWiT
R2-2303497	Discussion on sidelink positioning	ZTE Corporation
R2-2303538	Considerations on Sidelink positioning	CMCC
R2-2303569	Discussion on potential solutions for SL positioning	Spreadtrum Communications
R2-2303591	Sidelink Positioning Protocol (SLPP) Signaling and Procedures	Qualcomm Incorporated
R2-2303703	Sidelink positioning	Ericsson
R2-2303753	Protocol considerations for Anchor UEs with(out) known location	Philips International B.V.
R2-2303993	Discussion on Sidelink positioning	InterDigital Communications
R2-2304005	Designing SLPP protocol in the session perspective	Samsung R&D Institute UK
R2-2304033	Discussion on SL positioning	Xiaomi
R2-2304182	On the support of SL positioning server functionality	Philips International B.V.
R2-2304297	[AT121bis-e][423][POS] Sidelink positioning parameters in discovery signalling (Nokia)	Nokia
R2-2304298	Report of [AT121bis-e][424][POS] Group positioning and multiple targets (Xiaomi/Qualcomm)	Xiaomi
R2-2304301	[AT121bis-e][428][POS] Sidelink positioning stage 2 (CATT)	CATT
R2-2304302	Report of [AT121bis-e][429][POS] Session-based SLPP (Samsung)	Samsung (Rapporteur)

7.2.3: RAT-dependent integrity

TDoc	Title	Source
R2-2302504	Discussion on RAT-Dependent integrity	CATT
R2-2302581	Discussion on RAT-dependent Integrity	Huawei, HiSilicon
R2-2302741	Further considerations on RAT dependent integrity	Intel Corporation
R2-2302959	Discussion on RAT-dependent positioning integrity	vivo
R2-2303184	Consideration on RAT-dependent positioning integrity	OPPO
R2-2303230	Discussion on RAT-dependent integrity	Lenovo
R2-2303433	Discussion on RAT-dependent positioning integrity	Xiaomi
R2-2303495	Discussion on RAT-dependent methods positioning integrity	ZTE Corporation
R2-2303540	Discussion on the integrity issues	CMCC
R2-2303571	Discussion on solutions for integrity of RAT-dependent positioning techniques	Spreadtrum Communications
R2-2303682	Integrity of NR Positioning Technologies	Qualcomm Incorporated
R2-2303705	RAT Dependent positioning Integrity	Ericsson
R2-2303994	Discussion on RAT dependent integrity	InterDigital Communications
R2-2304058	Spec impact of RAT-dependent error sources for positioning integrity	Nokia, Nokia Shanghai Bell
R2-2304193	Summary of AI 7.2.3 on RAT-dependent integrity	VIVO TECH GmbH
R2-2304460	Draft LS to RAN1 on RAT-dependent positioning integrity	OPPO
R2-2304468	Draft LS to RAN1 on RAT-dependent positioning integrity	OPPO
R2-2304563	LS on the RAT-dependent positioning integrity	RAN2

7.2.4: LPHAP

TDoc	Title	Source
R2-2302505	Discussion on LPHAP	CATT
R2-2302580	Discussion on LPHAP	Huawei, HiSilicon
R2-2302589	Enhancements for supporting LPHAP	Fraunhofer IIS, Fraunhofer HHI
R2-2302742	Further considerations on LPHAP	Intel Corporation
R2-2302960	Discussion on solution of LPHAP	vivo
R2-2303079	Considerations on Low Power High Accuracy Positioning	Sony
R2-2303185	Discussion on LPHAP	OPPO
R2-2303231	Discussion on low power high accuracy positioning	Lenovo
R2-2303367	Alignment between DRX and PRS	Apple
R2-2303434	Discussion on LPHA positioning	Xiaomi
R2-2303494	Discussion on LPHAP	ZTE Corporation
R2-2303539	Considerations�on�LPHAP	CMCC
R2-2303570	Discussion on LPHAP	Spreadtrum Communications
R2-2303697	Enhancements for LPHAP	Qualcomm Incorporated
R2-2303704	Discussion on Low Power High Accuracy Positioning	Ericsson
R2-2303886	Discussion on SRS configuration in RRC_INACTIVE	Samsung
R2-2303985	Discussion on LPHAP	LG Electronics Inc.
R2-2303995	Discussion on LPHAP	InterDigital Communications
R2-2304059	PRS and DRX configuration alignment	Nokia, Nokia Shanghai Bell
R2-2304197	Summary of 7.2.4 LPHAP	Apple (moderator)
R2-2304461	Reply LS to SA2 on Low Power High Accuracy Positioning	RAN2

7.2.5: RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning

TDoc	Title	Source
R2-2302506	Discussion on carrier phase positioning, bandwidth aggregation for positioning and Redcap positioning	CATT
R2-2302743	Considerations on other RAN1 led items	Intel Corporation
R2-2302818	Discussion on RAN1 led positioning topics	Huawei, HiSilicon
R2-2303435	Discussion on RedCap UE positioning	Xiaomi
R2-2303496	Discussion on BW aggregation and RedCap poositioning	ZTE Corporation
R2-2303541	Discussion on the RedCap UE positioning	CMCC
R2-2303706	RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning	Ericsson
R2-2303887	Discussion on bandwidth aggregation	Samsung
R2-2303996	Discussion on positioning for RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning	InterDigital Communications

7.3.1: Organizational

TDoc	Title	Source
R2-2303101	Work plan for NR network energy savings	Huawei, HiSilicon

7.3.2: DTX/DRX mechanism

TDoc	Title	Source
R2-2302487	Uplink transmission restrictions to support cell DRX-DTX	NEC
R2-2302763	Cell DTX/DRX impact on C-DRX	CATT, Dell Technologies, Turkcell
R2-2302796	Outcome of [POST121][312][NES] DTX/DRX - Configuration/ activation/ deactivation and alignment (Huawei)	Huawei, HiSilicon
R2-2302797	Discussion on cell DTX and DRX	Huawei, HiSilicon
R2-2302835	Further discussion on cell DTX and DRX	ZTE Corporation, Sanechips
R2-2302914	Cell DTX-DRX Mechanism	Qualcomm Incorporated
R2-2302976	Further considerations on Cell DTX and DRX	Intel Corporation
R2-2303152	Discussion on DTX/DRX mechanism	LG Electronics Inc.
R2-2303257	On Cell DTX and DRX	Fraunhofer IIS, Fraunhofer HHI
R2-2303310	Discussion on DTX/DRX mechanism	OPPO
R2-2303316	UE and gNB behaviors to support cell DTX/DRX	NEC Telecom MODUS Ltd.
R2-2303369	Further discussion on Cell DTX / DRX	Apple
R2-2303444	Expected cell - UE behaviour during cell DTX/DRX	BT plc
R2-2303600	Cell DTX/DRX mechanism	InterDigital
R2-2303604	Report of [POST121][311][NES] DTX/DRX - gNB and UE behaviours	InterDigital
R2-2303653	Alignment to Cell DRX and cell DTX	Lenovo
R2-2303663	Further aspects on cell DTX/DRX	Ericsson
R2-2303748	Discussion on DTX/DRX for NES	Samsung
R2-2303773	Discussion on Cell DTX/DRX configuration and operation	Xiaomi
R2-2303792	Discussion on cell DTX/DRX	CMCC
R2-2303823	discussion on cell DTX-DRX mechanism	vivo
R2-2303827	Issues on Cell DTX/DRX	ETRI
R2-2303860	Remaining issues on DTX/DRX	Nokia, Nokia Shanghai Bell
R2-2303978	Considerations on Cell DTX/DRX	KDDI Corporation
R2-2303984	Discussion on Cell DRX/DTX	Rakuten Mobile, Inc
R2-2304080	Discussion on Cell DTX/DRX	NTT DOCOMO INC.
R2-2304181	Further considerations on the Cell DTX/DRX	MediaTek Inc.
R2-2304357	DRAFT LS on Cell DTX/DRX activation/deactivation	Huawei
R2-2304568	LS on Cell DTX/DRX activation/deactivation	RAN2

7.3.3: SSB-less Scell operation

TDoc	Title	Source
R2-2303603	SSB-less Scell operation	InterDigital

7.3.4: Cell selection/re-selection

TDoc	Title	Source
R2-2302915	Barring legacy UEs for NES Cells	Qualcomm Incorporated, T-Mobile US
R2-2303247	Cell selection/re-selection in NES	Lenovo
R2-2303514	Discussion on cell barring and reselection for NES	CMCC
R2-2303601	Cell selection and resection for NES	InterDigital
R2-2304070	Discussion on Cell selection	NTT DOCOMO INC.

7.3.5: Connected mode mobility

TDoc	Title	Source
R2-2302764	CHO enhancement for NES	CATT, Turkcell
R2-2302837	Further discussion on connected mode mobility	ZTE Corporation, Sanechips
R2-2302925	NES Connected mode mobility	Qualcomm Incorporated
R2-2303077	CHO for NES	Ericsson
R2-2303080	Handover enhancement for NES	Sony
R2-2303102	Discussion on CHO enhancement for NES	Huawei, HiSilicon
R2-2303128	CHO on NES	Nokia, Nokia Shanghai Bell
R2-2303146	Discussion on CHO enhancements for NES	Sharp
R2-2303161	Triggering conditions and other aspects of the Handover to/from DTX/DRX cells	Vodafone Espa�a SA, Apple
R2-2303259	Discussion on Connected mode mobility for network energy savings	Fujitsu Limited
R2-2303311	Discussion on connected mode mobility	OPPO
R2-2303317	CHO procedure enhancement to support NES mode	NEC Telecom MODUS Ltd.
R2-2303370	Discussion on CHO enhancement in NES	Apple
R2-2303481	DRAFT LS for Enhanced handovers towards cells with activated cell DTX/DRX or cells which are going to be switched off	Vodafone
R2-2303512	CHO procedure enhancements for NES	Intel Corporation
R2-2303602	NES mobility aspects	InterDigital
R2-2303654	CHO Procedure in NES Mode	Lenovo
R2-2303749	Discussion on Connected mode mobility for NES	Samsung
R2-2303793	Discussion on Connected mode mobility enhancement for NES	CMCC
R2-2303824	Conditional handover enhancement for network energy saving	vivo
R2-2303853	Discussion on UE mobility due to NES cell	Xiaomi
R2-2304155	Discussion on CHO procedure enhancements in case source/target cell is in NES mode	Turkcell
R2-2304180	Connected Mode Mobility	LG Electronics Inc.
R2-2304353	Summary of EMAIL DISC [121bis#xxx] on AI 7.3.5 Connected Mode Mobility	Lenovo (Rapporteur)

7.4.1: Organizational

TDoc	Title	Source
R2-2302412	LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM (R1-2302194; contact: Fujitsu, CATT)	RAN1
R2-2302432	Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility (R4-2303308; contact: CATT)	RAN4
R2-2302450	Reply LS R2-2213337 LS on security for selective SCG activation (S3-231397; contact: Nokia)	SA3
R2-2302458	LS on Approaches during execution for inter-DU LTM (R3-230889; contact: Ericsson)	RAN3
R2-2304522	Summary of [AT121bis-e][016][eMob] Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM (Fujitsu)	Fujitsu
R2-2304523	[Draft] Reply LS on PDCCH ordered RACH for LTM	Fujitsu, CATT
R2-2304553	Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM	RAN2

7.4.2: L1L2 Triggered Mobility

TDoc	Title	Source
R2-2304101	RRC running CR for LTM	Ericsson
R2-2304537	Summary of [AT121bis-e][017][eMob] RRC	Ericsson

7.4.2.1: General and Stage-2

TDoc	Title	Source
R2-2302485	Failure handling for L1/L2 triggered mobility	NEC
R2-2302486	UE identification during cell swtich	NEC
R2-2302507	Discussion on RACH-less LTM	CATT
R2-2302508	Discussion on Applicable Scenarios and Procedure	CATT
R2-2302591	Early Timing Advance Management for LTM	Samsung Electronics Co., Ltd
R2-2302605	On combined triggering of mobility changes and RACH-less in sequential LTM	Futurewei
R2-2302607	Discussion on issues with L1L2 dynamic mobility and RACH-less	Futurewei
R2-2302731	Security impacts of inter gNB-DU LTM	Rakuten Symphony
R2-2302750	Discussion on the early TA acquisition	Intel Corporation
R2-2302752	Discussion on RACH-less LTM	Intel Corporation
R2-2302766	Discussion on RACH-less Handover for L1/L2 Triggered Mobility	Rakuten Symphony
R2-2302778	Performance Enhancements for L1/L2 Triggered Mobility	Rakuten Symphony
R2-2302779	Delayed Resource Reservation for inter gNB-DU L1/L2 Triggered Mobility	Rakuten Symphony
R2-2302804	Discussion on LTM procedures	vivo
R2-2302829	Discussion on LTM procedures	Qualcomm Inc.
R2-2302945	[Draft] Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM	Fujitsu, CATT
R2-2302946	Discussion on replying to the RAN1 LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM	Fujitsu, CATT
R2-2303008	LTM procedure for different scenarios	Fujitsu
R2-2303024	Discussion on general procedure for LTM	OPPO
R2-2303061	Early TA Acquisition in L1L2-triggered Mobility	MediaTek Inc.
R2-2303165	On RA, TA Acquisition and Maintenance in LTM	Nokia, Nokia Shanghai Bell
R2-2303348	RACH-less in LTM	Xiaomi
R2-2303393	RACH-less LTM, LTM MAC CE and TA management	Apple
R2-2303425	Discussion on LTM overall procedure	ZTE Corporation, Sanechips
R2-2303535	Considerations on failure handling	CMCC
R2-2303536	Considerations on Timing Advance management for LTM	CMCC
R2-2303549	LTM procedure including RAN3 LS and miscellaneous issues	Huawei, HiSilicon
R2-2303550	RACH-less cell switch (inter-DU issues, RAR options from R1 LS) and L1 measurement configuration	Huawei, HiSilicon
R2-2303649	Details of Early TA work	Lenovo
R2-2303650	LTM stage-2 design models	Lenovo
R2-2303709	LTM Stage 2 open issues	Interdigital, Inc.
R2-2303751	Remaining issues of LTM execution procedure	LG Electronics
R2-2303754	Data Loss at LTM	MediaTek Inc.
R2-2303869	Discussion on potential enhancement for LTM	Samsung
R2-2303940	Discussion on TA of candidate cells for LTM	LG Electronics Inc.
R2-2304102	Discussion on RAN3 LS on approaches during execution for inter-DU LTM	Ericsson
R2-2304104	TA handling aspects for LTM	Ericsson
R2-2304156	Discussion on RAN1 related issue of LTM	NTT DOCOMO INC.
R2-2304185	Discussion on RAN1 related issue of LTM	NTT DOCOMO INC.
R2-2304214	Summary of [AT121bis-e][018][eMob] Procedure Consolidation (Huawei)	Huawei, HiSilicon

7.4.2.2: RRC

TDoc	Title	Source
R2-2302484	L1 Measurement for Cell Switch	NEC
R2-2302552	Discussion on RRC aspects for LTM	CATT
R2-2302606	Configuration and handling of sequential LTM and RACH-less	Futurewei
R2-2302732	Discussion of reference configuration for LTM	Intel Corporation
R2-2302754	Considerations on L1 measurement configuration for LTM	Panasonic
R2-2302805	Configurations of Candidate Cell for LTM	vivo
R2-2302830	Race conditions in LTM	Qualcomm Inc.
R2-2302831	RRC Aspects of LTM	Qualcomm Inc.
R2-2302832	Dynamic switch in LTM	Qualcomm Inc.
R2-2302876	RRC aspects for LTM	Huawei, HiSilicon
R2-2303009	RRC aspects of L1/L2 triggered mobility	Fujitsu
R2-2303025	Discussion on RRC related issues for LTM	OPPO
R2-2303062	RRC Aspects of L1L2-triggered Mobility	MediaTek Inc.
R2-2303072	Discussion on RRC Reconfiguration Aspects	Nokia, Nokia Shanghai Bell
R2-2303166	On RRC Configuration for LTM: Reference, Delta and Validity Check	Nokia, Nokia Shanghai Bell
R2-2303220	RRC issues for LTM configuration	Lenovo
R2-2303347	Remaining issues of RRC configured Layer-2 reset	Xiaomi
R2-2303355	Details of delta configurations in LTM	NEC
R2-2303392	RRC based L2 reset config	Apple
R2-2303395	LTM cell switch and link failure handling	Apple
R2-2303426	Remaining issues on LTM RRC aspects	ZTE Corporation, Sanechips
R2-2303533	Considerations on measurment related issues	CMCC
R2-2303534	[Draft] LS on measurement related issues for L1L2-based inter-cell mobility	CMCC
R2-2303592	Discussion on RRC Reconfiguration Aspects	Nokia, Nokia Shanghai Bell
R2-2303710	LTM Measurement considerations	Interdigital, Inc.
R2-2303711	RRC Open issues for LTM	Interdigital, Inc.
R2-2303843	Discussion on reference configuration	LG Electronics France
R2-2303847	Discussion on candidate and reference configuration for LTM	Xiaomi
R2-2304071	Remaining issues for RRC Configurations of LTM	Sharp
R2-2304103	L1 measurements aspects for LTM	Ericsson
R2-2304105	Discussion on RRC aspects for LTM	Ericsson
R2-2304548	[AT121bis-e][019][eMob] L1 Measurements (Qualcomm)	Qualcomm Incorporated

7.4.2.3: Cell Switch

TDoc	Title	Source
R2-2302509	Discussions on Cell Switch	CATT
R2-2302592	Open issues for Cell Switching	Samsung Electronics Co., Ltd
R2-2302733	Discussion on LTM cell switch	Intel Corporation
R2-2302806	L2 Reset and triggering MAC CE for LTM	vivo
R2-2302877	Cell switch solutions and L2 behaviours in LTM	Huawei, HiSilicon
R2-2303026	Open issues on dynamic switching for LTM	OPPO
R2-2303065	Considerations on Cell Switch for LTM	Samsung
R2-2303073	On the cell switch in LTM	Nokia, Nokia Shanghai Bell
R2-2303277	Discussion on partial MAC reset for LTM	KDDI Corporation
R2-2303345	Discussion on LTM Failure Handling	FGI
R2-2303349	Handling of connection failure for LTM	Xiaomi
R2-2303356	Further discussion on Cell switch	NEC
R2-2303473	Further discussion on LTM cell switch procedure	Transsion Holdings
R2-2303474	Discussion on measurement enhancement of L1L2 triggered mobility	Transsion Holdings
R2-2303537	Considerations on cell switch	CMCC
R2-2303575	Discussion on cell switch for LTM	Spreadtrum Communications
R2-2303593	On the cell switch in LTM	Nokia, Nokia Shanghai Bell
R2-2303651	Securing LTM	Lenovo
R2-2303712	LTM MAC CE content and functionality	Interdigital, Inc.
R2-2303752	Discussion on LTM timer operation	LG Electronics
R2-2303759	Partial MAC Reset during Intra-DU LTM	MediaTek Inc.
R2-2303929	Discussion on L1L2-triggered mobility	ASUSTeK
R2-2304072	Cell Switch for LTM	Sharp
R2-2304106	RRC-MAC cross-layer aspects during LTM cell switch execution	Ericsson
R2-2304130	Further Considerations On Cell Switch Command and MAC Paritial Reset	ZTE Corporation, Sanechips

7.4.3: NR-DC with selective activation cell of groups

TDoc	Title	Source
R2-2302510	Discussion on Selective Activation of Cell Groups in NR-DC	CATT
R2-2302734	Discussion on selective activation of cell groups	Intel Corporation
R2-2302807	Remaining issues for NR-DC with selective activation cell of groups	vivo
R2-2302878	NR-DC with selective SCG activatiion	Huawei, HiSilicon
R2-2302934	Report of [Post121][044][eMob] SCG Selective Activation in NR-DC Signalling interaction	Qualcomm Incorporated
R2-2302936	SCG Selective Activation in NR-DC	Qualcomm Incorporated
R2-2303027	Discussion on selective activation of SCGs for NR-DC	OPPO
R2-2303028	TP of 38.331 for selective activation of SCGs for NR-DC	OPPO
R2-2303066	Considerations on Subsequent CPAC after SCG Change	Samsung
R2-2303191	Further analysis on remaining issues for selective activation	Nokia, Nokia Shanghai Bell
R2-2303239	Discussion on issues related to SCG selective activation	Lenovo
R2-2303335	SCG failure handling with selective activation	ITRI
R2-2303357	Further discussion on selective SCG activation	NEC
R2-2303394	Avoiding keystream re-use with selective activation of cell-groups	Apple
R2-2303408	Execution condition in selective SCG activation	Apple
R2-2303427	Consideration on SCG selective activation	ZTE Corporation, Sanechips
R2-2303428	TP to 37.340 for SCG selective activation and CHO with candidate SCGs	ZTE Corporation, Sanechips
R2-2303475	Discussion on Selective Activation of Cell Groups in NR-DC	Transsion Holdings
R2-2303516	Discussion on NR-DC with selective activation of cell groups	CMCC
R2-2303566	Discussion on NR-DC with SCG selective activation	Spreadtrum Communications
R2-2303606	Discussion on selective SCG activation	MediaTek Inc.
R2-2303625	Subsequent change of SCGs and selective activation	Interdigital Inc.
R2-2303680	NR-DC with selective activation	Ericsson
R2-2303848	Discussion on NR-DC with selective activation of the cell groups	Xiaomi
R2-2303890	Discussion on NR-DC with selective activation of the cell groups.	DENSO CORPORATION
R2-2304024	Additional Aspects for Selective Cell Group Activation	LG Electronics
R2-2304073	Discussion of SCG selective activation	Sharp
R2-2304158	Discussion on selective activation	NTT DOCOMO INC.
R2-2304186	Discussion on selective activation	NTT DOCOMO INC.

7.4.4: CHO including target MCG and candidate SCGs for CPC CPA in NR-DC

TDoc	Title	Source
R2-2302511	Discussion on CHO including target MCG and candidate SCGs	CATT
R2-2302751	Discussion on CHO including candidate SCGs	Intel Corporation
R2-2302808	Discussion on evaluation and execution of CHO with CPAC	vivo
R2-2302809	Discussion on CHO with CPAC signaling procedure	vivo
R2-2302935	CHO with multiple candidate SCGs	Qualcomm Incorporated
R2-2303029	Discussions on CHO including target MCG and candidate SCGs	OPPO
R2-2303167	Next Steps for CHO with CPAC in Rel-18	Nokia, Nokia Shanghai Bell
R2-2303221	Consideration on CHO with candidate SCG for CPAC	Lenovo
R2-2303344	Discussion on Conditional Handover with Candidate SCGs for CPAC	FGI
R2-2303414	HO execution of CHO with candidate SCGs	Apple
R2-2303429	Discussion on CHO with candidate SCGs	ZTE Corporation, Sanechips
R2-2303551	CHO including target MCG and candidate SCGs for CPC/CPA	Huawei, HiSilicon
R2-2303567	Discussion on CHO with CPAC in NR-DC	Spreadtrum Communications
R2-2303607	Discussion on CHO with candidate SCG	MediaTek Inc.
R2-2303626	CHO with associated SCG	Interdigital Inc.
R2-2303681	CHO with associated CPC or CPA	Ericsson
R2-2303794	Discussion CHO including target MCG and candidate SCGs for CPAC	CMCC
R2-2303849	Discussion on CHO with CPAC	Xiaomi
R2-2303870	Considerations on CHO with CPA/CPC	Samsung
R2-2304025	Simultaneous Evaluation for CHO with CPAC	LG Electronics

7.5.1: Organizational

TDoc	Title	Source
R2-2302715	Work Plan for Rel-18 WI on XR Enhancements for NR	Nokia, Qualcomm (Rapporteurs)
R2-2302716	SA2 Status for XR	Nokia, Qualcomm (Rapporteurs)
R2-2302717	SA4 Status for XR	Nokia, Qualcomm (Rapporteurs)
R2-2302718	Stage 2 Overview of XR Enhancements	Nokia, Qualcomm (Rapporteurs)
R2-2304392	[DRAFT] LS on TSCAI for XR	Nokia
R2-2304393	Stage 2 Overview of XR Enhancements	Nokia, Qualcomm (Rapporteurs)
R2-2304400	LS on TSCAI for XR	RAN2
R2-2304493	LS out on the N6 PDU Set Identification (S4-230739; contact: Intel)	SA4
R2-2304569	LS on TSCAI for XR	RAN2

7.5.2: XR awareness

TDoc	Title	Source
R2-2302513	Discussion on XR awareness	Qualcomm Incorporated
R2-2302711	Discussion on XR awareness	Xiaomi Communications
R2-2302719	PDU Set and Data Burst Information	Nokia, Nokia Shanghai Bell
R2-2302756	Enhancements for XR awareness	CATT
R2-2302810	Discussion on XR awareness	vivo
R2-2302850	XR Awareness	ZTE Corporation, Sanechips
R2-2302895	XR awareness	InterDigital
R2-2302909	XR awareness enhancements in RAN	Intel Corporation
R2-2302938	Discussion on XR awareness	Futurewei
R2-2302950	Considerations on XR awareness	NEC
R2-2302996	Considerations on delay reporting and UL traffic arrival information	KDDI Corporation
R2-2303081	Considerations on XR PDU prioritization	Sony
R2-2303082	Some considerations on PDU set information and UL traffic arrival information	Sony
R2-2303124	Discussion on XR awareness	TCL Communication
R2-2303226	Discussion on PDU sets awareness in RAN	Lenovo
R2-2303301	RAN awareness of XR characteristics	MediaTek Inc.
R2-2303312	Discussion on XR awareness	OPPO
R2-2303358	Views on Enhancements for XR-Awareness	Apple
R2-2303578	Discussion on XR awareness	Spreadtrum Communications
R2-2303595	Discussion on UL assistance information for XR traffic	Huawei, HiSilicon
R2-2303719	Discussion on XR awareness	Ericsson
R2-2303741	On XR awareness	Google Inc.
R2-2303786	Discussion on XR-awareness	NTT DOCOMO, INC.
R2-2303800	Considerations on PDU sets and Traffic assistance information for XR	CMCC
R2-2303930	Discussion on PDU Set Information on UL for UE	ASUSTeK
R2-2303986	Discussion on UL jitter handling	Samsung
R2-2303998	Discussion on PDCP duplication based on PDU set importance	LG Electronics Inc.
R2-2304445	Report of [AT121bis-e][006][NR17] CP PowSav and DCCA Corrections (1st round)	CATT
R2-2304538	Report of [AT121bis-e][006][NR17] CP PowSav and DCCA Corrections (2nd round)	CATT

7.5.3: XR-specific power saving

TDoc	Title	Source
R2-2302514	DRX enhancements for XR	Qualcomm Incorporated, MediaTek, CATT, vivo, NEC
R2-2302583	Discussion on the SFN wrap-around problem for XR	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R2-2302599	Discussion on power saving aspects for XR	Continental Automotive
R2-2302710	Discussing on XR-specific C-DRX enhancements	Xiaomi Communications
R2-2302793	XR-specific power saving enhancement	Google Inc.
R2-2302811	Discussion on DRX enhancements for XR Power Saving	vivo
R2-2302853	XR-specific power saving	ZTE Corporation, Sanechips
R2-2302896	XR-specific power saving	InterDigital
R2-2302910	Summary of DRX enhancements for XR traffic	Intel Corporation, Sony
R2-2303132	Discussion on C-DRX enhancement for XR	NEC Corporation
R2-2303227	Discussion of DRX enhancement	Lenovo
R2-2303302	SFN wrap-around solution for XR DRX	MediaTek Inc., CATT, LGE, Ericsson, NEC, DENSO
R2-2303359	C-DRX enhancements for XR	Apple
R2-2303544	Discussion on DRX enhancements	CMCC
R2-2303720	Discussion on XR-specific power saving	Ericsson
R2-2303755	Multiple DRX configuration for XR power saving	LG Electronics Inc., InterDigital, NEC, ZTE
R2-2303861	DRX cycle alignment for XR	Nokia, Nokia Shanghai Bell, CMCC, China Unicom, DENSO CORPORATION, Ericsson, Intel, Google Inc., Huawei, HiSilicon, Samsung, Xiaomi
R2-2303867	Discussion on power saving scheme for XR	Samsung
R2-2303892	Discussion on various frame rates supported for XR-specific power saving	III
R2-2304172	C-DRX enhancements for XR-specific power saving	DENSO CORPORATION

7.5.4.1: BSR enhancements for XR

TDoc	Title	Source
R2-2302515	BSR enhancements for XR	Qualcomm Incorporated
R2-2302527	Discussion on BSR enhancements for XR	Futurewei
R2-2302615	BSR enhancements for XR	MediaTek Inc.
R2-2302709	Discussing on BSR enhancements for XR capacity	Xiaomi Communications
R2-2302757	New BSR tables and delay report	CATT, Dell Technologies
R2-2302758	PDU set BSR	CATT, Dell Technologies
R2-2302812	Discussion on BSR enhancements for XR	vivo
R2-2302851	BSR enhancements for XR	ZTE Corporation, Sanechips
R2-2302911	BSR enhancements for XR	Intel Corporation
R2-2302972	Discussion on BSR enhancements for XR	TCL Communication Ltd.
R2-2302998	Considerations on XR capacity improvements	KDDI Corporation
R2-2303010	Discussions on delay information reporting	Fujitsu
R2-2303083	Considerations on XR UL PDU set information	Sony
R2-2303114	Discussion on BSR enhancement for delay information report	NEC Corporation
R2-2303203	Discussion on UE Feedback enhancements	Lenovo
R2-2303313	Discussion on BSR enhancement for XR	OPPO
R2-2303328	New BS table(s) and BSR trigger(s)	NEC
R2-2303343	Considerations on new buffer status report table	FGI
R2-2303360	Views on BSR Enhancements for XR	Apple
R2-2303530	Consideration on BSR enhancement for XR	CMCC
R2-2303584	BSR enhancement on XR	Spreadtrum Communications
R2-2303629	BSR enhancements for XR	Interdigital Inc.
R2-2303701	Discussion on BSR Enhancements and Delay Information	Meta
R2-2303721	Discussion on BSR enhancements for XR	Ericsson
R2-2303826	Discussion on MAC enhancements for XR-specific capacity improvement	Huawei, HiSilicon
R2-2303862	BSR enhancements for XR	Nokia, Nokia Shanghai Bell
R2-2303889	Discussion on BSR enhancements for XR	III
R2-2303982	Discussion on BSR enhancements for XR	Samsung
R2-2304008	Discussion on BSR enhancement and delay information report	LG Electronics Inc.
R2-2304043	Discussion on BSR enhancements for XR	Google Inc.
R2-2304089	Discussion on residual resource allocation for XR	Google Inc.
R2-2304394	Report of [AT121bis-e][212][XR] BSR solutions (Qualcomm)	Qualcomm

7.5.4.2: Discard operation for XR

TDoc	Title	Source
R2-2302516	Discussion on discard operation for XR	Qualcomm Incorporated
R2-2302708	Discussing on PDU discarding of XR traffic	Xiaomi Communications
R2-2302720	Discard operation for XR	Nokia, Nokia Shanghai Bell
R2-2302759	Discard Operation for XR	CATT
R2-2302813	Discussion on discard operation for XR	vivo
R2-2302854	PDU discard for XR	ZTE Corporation, Sanechips
R2-2302897	Discard operation for XR	InterDigital
R2-2302912	Discard operation for XR	Intel Corporation
R2-2302937	Discussion on discard operation for XR	Futurewei
R2-2302964	Discard Operation for XR	Samsung R&D Institute India
R2-2302970	Discussions on discard operation for XR	TCL Communication Ltd.
R2-2303011	Discussions on PDU discard based on PDU Set Importance	Fujitsu
R2-2303199	Discussion on discarding operation for XR	Motorola Mobility France S.A.S
R2-2303303	PDU discard based on PSDB and PDU set importance	MediaTek Inc.
R2-2303314	Discussion on discard operation for XR	OPPO
R2-2303329	PDU discard	NEC
R2-2303361	Views on PDU Discard Operation for XR	Apple
R2-2303579	Discussion on XR discard	Spreadtrum Communications
R2-2303700	Discussion on PDU Discard Operation for XR	Meta
R2-2303722	Discussion on PDU Discard	Ericsson
R2-2303788	Discussion on PDU discard	NTT DOCOMO, INC.
R2-2303801	Discard operation for XR	CMCC
R2-2303830	Discussion on PDU set discarding for XR traffic	Huawei, HiSilicon
R2-2303931	Discussion on PDU Set discard in PDCP layer for DL and UL	ASUSTeK
R2-2303999	Discussion on the discard for XR	LG Electronics Inc.

7.5.4.3: Configured Grant enhancements for XR

TDoc	Title	Source
R2-2302517	Enhancements to configured grant for XR	Qualcomm Incorporated
R2-2302584	Discussion on retransmission-less CG for XR	Huawei, Apple, Google, HiSilicon, Intel, Lenovo, MediaTek, Meta, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated
R2-2302760	On the need for retransmission-less CG for XR	CATT
R2-2302792	Configured Grant enhancements for XR	Google Inc.
R2-2302814	Discussion on CG enhancements for XR	vivo
R2-2302852	Configured Grant enhancements for XR	ZTE Corporation, Sanechips
R2-2302898	Configured Grant enhancements for XR	InterDigital
R2-2303084	Retransmission-less CG for some XR traffic	Sony
R2-2303085	Configured Grant enhancements for XR	Sony
R2-2303198	Discussion of CG enhancements	Lenovo
R2-2303315	Discussion on configured grant enhancement for XR	OPPO
R2-2303362	Views on Configured Grant Enhancements for XR	Apple
R2-2303531	Consideration on Configured Grant enhancement for XR	CMCC
R2-2303839	Configured Grant enhancements for XR	Ericsson
R2-2303863	CG enhancements for XR	Nokia, Nokia Shanghai Bell
R2-2303891	Discussion on Configured Grant enhancements for XR	III
R2-2303987	Multiple CG occasions and retransmission-less CG	Samsung
R2-2304009	Discussion on retransmission-less CG for XR	LG Electronics Inc.
R2-2304120	Retransmission-less CG for XR	MediaTek Inc.
R2-2304391	Report of [AT121bis-e][210] Retransmission-less CG for XR (Huawei)	Huawei

7.6.1: Organizational

TDoc	Title	Source
R2-2302675	Stage-3 running CR for TS 36.321 for Rel-18 IoT-NTN	MediaTek Inc.
R2-2303097	36331 running CR for IOT NTN	Huawei, HiSilicon
R2-2303838	Running CR for R18 IoT NTN	Ericsson
R2-2303950	Stage-3 running CR for TS 36.321 for Rel-18 IoT-NTN	MediaTek Inc.

7.6.2.1: HARQ enhancements

TDoc	Title	Source
R2-2302533	Discussion on HARQ enhancement for IoT NTN	OPPO
R2-2302534	Draft LS to RAN1 on HARQ enhancement for IoT NTN	OPPO
R2-2302557	Discussion on the HARQ enhancements in IoT NTN	CATT
R2-2302672	On Disabling HARQ Feedback in IoT-NTN	MediaTek Inc.
R2-2302819	Further discussion on HARQ enhancements	ZTE Corporation, Sanechips
R2-2303041	Enhancement for UL and DL HARQ processes	Qualcomm Incorporated
R2-2303517	Discussion on the HARQ enhancement for IoT-NTN	CMCC
R2-2303644	Discussion on Timing Advance Report MAC CE transmission in eMTC NTN	Nokia, Nokia Shanghai Bell, Huawei, HiSilicon
R2-2303713	Disabling HARQ feedback for IoT-NTN	Interdigital, Inc.
R2-2303837	R18 IoT NTN HARQ enhancements	Ericsson
R2-2303964	Discussion on HARQ enhancements	Huawei, HiSilicon
R2-2304030	Discussion on HARQ enhancement	Xiaomi
R2-2304032	LS on NPDCCH monitoring for HARQ mode B	Xiaomi
R2-2304243	Summary of [AT121bis-e][103][ IoT NTN Enh] HARQ enhancements (OPPO)	OPPO
R2-2304254	Summary of [AT121bis-e][103][ IoT NTN Enh] HARQ enhancements (OPPO) - second round	OPPO
R2-2304255	Draft LS on HARQ Enhancements	OPPO
R2-2304274	LS on HARQ Enhancements	RAN2
R2-232470	Discussion on HARQ enhancement for IoT NTN	OPPO
R2-232471	Draft LS to RAN1 on HARQ enhancement for IoT NTN	OPPO

7.6.2.2: GNSS operation enhancements

TDoc	Title	Source
R2-2302543	Discussion on GNSS operation for IoT NTN	OPPO
R2-2302558	Discussion on GNSS operation in connected mode	CATT
R2-2302673	GNSS operation enhancements	MediaTek Inc.
R2-2302820	Procedure of GNSS reacquisition	ZTE Corporation, Sanechips
R2-2303044	GNSS fix in RRC_CONNECTED	Qualcomm Incorporated
R2-2303250	On GNSS position fix in RRC_CONNECTED for IoT NTN	Lenovo
R2-2303297	Discussion on the GNSS Validity Reporting in Connected State	Google Inc.
R2-2303330	GNSS fix in connected mode	NEC
R2-2303404	Improved GNSS Operation	Apple
R2-2303518	Discussion on GNSS enhancement for IoT-NTN	CMCC
R2-2303645	Discussion on enhancements on GNSS operation for IoT NTN	Nokia, Nokia Shanghai Bell
R2-2303714	GNSS acquisition and reporting for IoT NTN	Interdigital, Inc.
R2-2303836	R18 IoT NTN GNSS operation enhancements	Ericsson
R2-2303965	Discussion on GNSS operation enhancements	Huawei, HiSilicon
R2-2304017	On improved GNSS operation for IoT NTN	Samsung R&D Institute UK
R2-2304029	Discussion on GNSS operation enhancement	Xiaomi
R2-2304183	GNSS acquisition and reporting for IoT NTN	InterDigital, Europe, Ltd.
R2-2304244	[AT121bis-e][104][IoT NTN Enh] GNSS operation enhancements (Mediatek)	MediaTek Inc.
R2-2304256	[AT121bis-e][104][IoT NTN Enh] GNSS operation enhancements (Mediatek) - second round	MediaTek Inc.
R2-232480	Discussion on GNSS operation for IoT NTN	OPPO

7.6.3.1: Enhancements for neighbour cell measurements

TDoc	Title	Source
R2-2302512	NTN mobility enhancements for earth-moving cell scenario ito. measurement initiation, cell reselection and handover	PANASONIC R&D Center Germany
R2-2302535	Discussion on measurement enhancement for IoT NTN	OPPO
R2-2302559	Discussion on the mobility enhancements for IoT NTN UE	CATT
R2-2302674	Enhancements for neighbour cell measurements	MediaTek Inc.
R2-2302700	Discussion on neighbour cell measurements in IoT NTN	Intel Corporation
R2-2302821	Details of new triggers for neighbor cell measurement	ZTE Corporation, Sanechips
R2-2303043	Satellite and coverage information signalling	Qualcomm Incorporated
R2-2303098	Discussion on mobility enhancements	Huawei, HiSilicon, Turkcell
R2-2303192	connected mode measurement triggering conditions and RLF enhancements for IoT-NTN	Nokia, Nokia Shanghai Bell
R2-2303251	Further considerations on neighbour cell measurement in RRC_CONNECTED	Lenovo
R2-2303406	Neighbour cell measurements before RLF for NB-IoT	Apple
R2-2303436	Consideration on enhancements for the neighbour cell measurement	Xiaomi
R2-2303519	Discussion on mobility enhancements for IoT-NTN	CMCC
R2-2303652	Report of [POST121][105][IoT NTN Enh] Neighbour cell assistance information	Qualcomm Technologies Ireland
R2-2303715	Neighbour cell measurements before RLF	Interdigital, Inc.
R2-2304016	On enhancements for neighbour cell measurements	Samsung R&D Institute UK
R2-2304065	Neighbour cell measurements before RLF	Ericsson
R2-2304257	[offline-114] Neighbour cell measurements	Qualcomm Incorporated
R2-232472	Discussion on measurement enhancement for IoT NTN	OPPO

7.6.3.2: Other

TDoc	Title	Source
R2-2303252	IDLE mobility for moving cells in IoT NTN	Lenovo
R2-2303405	Mobility enhancement in IoT NTN	Apple
R2-2304018	On IoT NTN CHO and other mobility enhancements	Samsung R&D Institute UK

7.6.4: Enhancements to discontinuous coverage

TDoc	Title	Source
R2-2302560	Discussion on enhancements to discontinuous coverage	CATT
R2-2302822	RAN2 enhancements for discontinuous coverage	ZTE Corporation, Sanechips
R2-2303042	RRC release procedure in discontinuous coverage	Qualcomm Incorporated
R2-2303052	Enhancements to discontinuous coverage	Samsung R&D Institute UK
R2-2303111	Considerations on Supporting Discontinuous Coverage	NEC Europe Ltd
R2-2303193	On RAN impacts for Discontineous coverage enhancements	Nokia, Nokia Shanghai Bell
R2-2303253	On mobility and power saving issues for discontinuous coverage	Lenovo
R2-2303407	Support on discontinuous coverage in IoT NTN	Apple
R2-2303437	Enhancements to discontinuous coverage	Xiaomi
R2-2303476	Discussion on enhancement to discontinuous coverage for IoT NTN	Transsion Holdings
R2-2303520	Discussion on the discontinuous coverage for IoT-NTN	CMCC
R2-2303576	Discussion on power saving enhancements for supporting discontinuous coverage	Spreadtrum Communications
R2-2303716	IoT-NTN discontinuous coverage enhancements	Interdigital, Inc.
R2-2303735	Enhancements to discontinuous coverage	Ericsson
R2-2303963	Discussion on discontinuous coverage	Huawei, HiSilicon
R2-2304081	Discussion on the UE Unreachability Periods	Google Inc.
R2-2304160	Discussion on Enhancements related to discontinuous coverage	Rakuten Mobile, Inc
R2-2304258	[offline-115] Discontinuous coverage enhancements	InterDigital

7.7.1: Organizational

TDoc	Title	Source
R2-2302428	Reply LS on RACH-less handover in NTN (R4-2303239; contact: OPPO)	RAN4
R2-2302694	Discussion on NR NTN UE capabilities	Intel Corporation
R2-2302695	Draft 331 CR for NR NTN UE capabilities	Intel Corporation
R2-2302696	Draft 306 CR for NR NTN UE capabilities	Intel Corporation
R2-2303137	Stage-3 running 304 CR for NTN	ZTE Corporation, Sanechips
R2-2303162	R18 WI NR-NTN-enh work plan at RAN1, 2 and 3	THALES
R2-2303726	Stage 3 NTN running CR for 38.321 - RAN2#121bise	InterDigital
R2-2303737	Stage 3 Running RRC CR for NR NTN Rel-18	Ericsson

7.7.2: Coverage Enhancements

TDoc	Title	Source
R2-2302536	Discussion on initial blind Msg3 retransmission for NTN	OPPO
R2-2302798	Discussion on blind Msg3 retransmission	Huawei, HiSilicon
R2-2303326	Discussion on coverage enhancement for R18 NTN	vivo
R2-2303458	Discussion on coverage enhancement for R18 NTN	vivo
R2-2303727	Blind Msg3 retransmission in Rel-18 NTN	InterDigital
R2-2303834	R18 NR NTN Coverage enhancements	Ericsson
R2-2303997	Discussion on inital blind Msg3 retransmssion	LG Electronics Inc.
R2-2304245	Report of [AT121bis-e][105][NR NTN enh] Coverage enhancements	InterDigital (Rapporteur)
R2-232473	Discussion on initial blind Msg3 retransmission for NTN	OPPO

7.7.3: Network verified UE location

TDoc	Title	Source
R2-2302556	Discussion on multiple-RTT based positioning in NTN	Quectel
R2-2302561	Discussion on Network Verified UE Location	CATT
R2-2302679	On Network Verified UE Location in NR NTN	MediaTek Inc.
R2-2302794	On Network verified UE location	Nokia, Nokia Shanghai Bell
R2-2302848	Discussion on network verified UE location	Ericsson
R2-2303036	Single satellite Multi-RTT based positioning	Qualcomm Incorporated
R2-2303138	Consideration on NW verified UE location	ZTE Corporation, Sanechips
R2-2303261	Discussion on network verified UE location in NR NTN	THALES
R2-2303299	Discussion on NTN NW verified UE location	Lenovo
R2-2303438	Discussion on network verified UE location	Xiaomi
R2-2303524	Discussion on network verified UE location	CMCC
R2-2303666	Network Verified UE Location in NTN	Samsung R&D Institute UK
R2-2303955	Discussion on Network Verified UE Location	TCL Communication Ltd.
R2-2303962	Discussion on the network verfied UE location	Huawei, HiSilicon
R2-2304188	Discussion on network verified UE location	Ericsson

7.7.4.1.1: NTN-TN enhancements

TDoc	Title	Source
R2-2302539	Discussion on NTN-TN cell reselection enhancement	OPPO
R2-2302562	Discussion on Cell Reselection Enhancements in NTN-TN	CATT
R2-2302680	On TN-NTN Cell Selection Re-selection in NR NTN	MediaTek Inc.
R2-2302699	Discussion on TN-NTN cell reselection enhancements	Intel Corporation
R2-2302780	Discussion on TN-NTN cell reselection enhancements	CAICT
R2-2303037	TN cell coverage info and measurement relaxation	Qualcomm Incorporated
R2-2303086	Cell selection/reselection enhancements in NTN-TN	Sony
R2-2303100	Discussion on the NTN-TN cell reselection enhancements	Huawei, HiSilicon, Turkcell
R2-2303139	Consideration on cell reselection enhancements for NTN-TN	ZTE Corporation, Sanechips
R2-2303168	On TN Coverage Area Information - signaling, validity and definition aspects	Nokia, Nokia Shanghai Bell
R2-2303255	Indication of TN area for neighbour cell measurement in NTN	Lenovo
R2-2303300	Signaling the TN Coverage Information with a 2-step Approach	Google Inc.
R2-2303318	Details of the TN coverage data signalling	NEC Telecom MODUS Ltd.
R2-2303325	Discussion on Power saving for NTN-TN mobility	vivo
R2-2303334	Discussion on the assistance information for NTN-TN cell reselection	ITRI
R2-2303415	NTN-TN cell reselection enhancement	Apple
R2-2303439	Cell reselection enhancements for NTN-TN mobility	Xiaomi
R2-2303457	Discussion on Power saving for NTN-TN mobility	vivo
R2-2303477	Discussion on NR NTN-TN cell reselection enhancements	Transsion Holdings
R2-2303525	NTN-TN cell reselection enhancements	CMCC
R2-2303724	NTN-TN Mobility Cell Reselection and PCI Values	SHARP Corporation
R2-2303728	NTN-TN mobility and service continuity	InterDigital
R2-2303736	TN NTN mobility enhancements	Ericsson
R2-2303766	Discussion on NTN-TN Cell Reselection Enhancements	Samsung Research America
R2-2303790	Further discussion on NTN-TN cell reselection enhancements	NTT DOCOMO, INC.
R2-2303975	Discussion on NTN-TN cell reselection enhancements	LG Electronics France
R2-2304014	Discussion on NTN-TN Cell re-selection	ITL
R2-2304246	Report from [AT121bis-e][106][NR NTN Enh] Signalling of TN coverage (Nokia)	Nokia, Nokia Shanghai Bell
R2-2304247	Report of [AT121bis-e][107][NR NTN Enh] NW type information (Samsung)	Samsung
R2-232476	Discussion on NTN-TN cell reselection enhancement	OPPO

7.7.4.1.2: NTN-NTN enhancements

TDoc	Title	Source
R2-2302538	Discussion on NTN-NTN cell reselection enhancement	OPPO
R2-2303140	Report of [Post121][106][NR NTN enh] NTN-NTN cell reselection (ZTE)	ZTE Corporation, Sanechips
R2-2303169	On NTN-NTN Reselections in EMC	Nokia, Nokia Shanghai Bell
R2-2303254	Neighbour cell measurement triggering for reselection in NTN moving cells	Lenovo
R2-2303324	Discussion on cell reselection enhancement for earth-moving cell	vivo
R2-2303416	NTN-NTN cell reselection enhancement	Apple
R2-2303440	Cell reselection enhancements for NTN-NTN mobility	Xiaomi
R2-2303456	Discussion on cell reselection enhancement for earth-moving cell	vivo
R2-2303577	Discussion on NTN-NTN mobility enhancements	Spreadtrum Communications
R2-2303729	Cell reselection enhancements for Earth moving cell	InterDigital
R2-2303767	Discussion on NTN-NTN Cell Reselection Enhancements	Samsung Research America
R2-2303976	Discussion on NTN-NTN cell reselection enhancements	LG Electronics France
R2-232475	Discussion on NTN-NTN cell reselection enhancement	OPPO

7.7.4.2: Handover enhancements

TDoc	Title	Source
R2-2302545	Discussion on NTN handover enhancements	OPPO
R2-2302563	Discussion on PCI Unchanged Scenario	CATT
R2-2302564	Discussion on NTN HO Enhancements	CATT
R2-2302678	Handover Enhancement in Earth Moving Cells	MediaTek Inc.
R2-2302697	Discussion on NTN 2-step handover	Intel Corporation
R2-2302698	Discussion on NTN RACH-less handover	Intel Corporation
R2-2303038	RACH-less handover for NTN	Qualcomm Incorporated
R2-2303039	Further handover enhancement for NTN	Qualcomm Incorporated
R2-2303076	Consideration of HO common signaling gain in NTN	China Telecom
R2-2303087	Signaling overhead reduction and group handover during NTN-NTN HOs	Sony
R2-2303099	Discussion on NTN handover enhancements	Huawei, HiSilicon, Turkcell
R2-2303141	Consideration on HO enhancements in NTN	ZTE Corporation, Sanechips
R2-2303142	Consideration on RACH-less HO in NTN	ZTE Corporation, Sanechips
R2-2303160	Discussion on NTN handover enhancements	TCL Communication Ltd.
R2-2303170	Even Further Aspects on Connected-mode Mobility in Rel-18 NTN	Nokia, Nokia Shanghai Bell
R2-2303256	Considerations on supporting RACH-less HO in NTN	Lenovo
R2-2303258	Discussion on Handover enhancements for NTN	Fujitsu Limited
R2-2303327	On handover enhancement for signalling overhead reduction in NR NTN	vivo
R2-2303331	Satellite switch_PCI change without L3 handover	NEC
R2-2303332	Support RACH-less HO and CHO	NEC
R2-2303417	Signaling optimization on common HO configuration	Apple
R2-2303418	NTN specific handover enhancement	Apple
R2-2303441	Discussion on handover enhancements for NTN-NTN mobility	Xiaomi
R2-2303459	On handover enhancement for signalling overhead reduction in NR NTN	vivo
R2-2303478	Discussion on NR NTN-NTN handover enhancements	Transsion Holdings
R2-2303526	Discussion on common (C)HO configuration, RACH-less HO and group HO for NTN	CMCC
R2-2303730	NTN mobility enhancements for RRC_CONNECTED	InterDigital
R2-2303734	Handover enhancements	Ericsson
R2-2303768	Discussion on NTN handover enhancements	Samsung Research America
R2-2303802	Further discussion on PCI unchanged	CMCC
R2-2303932	Discussion on RACH-less handover for NTN	ASUSTeK
R2-2303933	Discussion on handover enhancement with common signalling	ASUSTeK
R2-2303977	Discussion on handover enhancements	LG Electronics France
R2-2304079	Discussion on handover enhancements	Sharp
R2-2304134	NTN-NTN handover enhancements	Sequans Communications
R2-2304137	HO/CHO Signaling Overhead Reduction by NTN-config omission	Sequans Communications
R2-2304147	Considerations on unchanged PCI solution	Sequans Communications
R2-2304248	Report of [AT121bis-e][108][NR NTN Enh] Common (C)HO configuration (Ericsson)	Ericsson
R2-2304249	Report of [AT121bis-e][109][NR NTN Enh] RACH-less HO (Samsung)	Samsung
R2-2304250	DRAFT LS to RAN1 on unchanged PCI	CATT
R2-2304271	LS on RACH-less Handover	RAN2
R2-2304273	LS on unchanged PCI	RAN2
R2-232482	Discussion on NTN handover enhancements	OPPO

7.8.1: Organizational

TDoc	Title	Source
R2-2302443	LS on PC5 based Detect and Avoid mechanism (S2-2301854; contact: LGE)	SA2
R2-2302444	LS on RAN dependency for UAS (S2-2303285; contact: LGE)	SA2
R2-2302459	Reply to LS to 3GPP on ECC request for standardisation support related to ECC Decision (22)07 on �harmonised framework on aerial UE usage in MFCN harmonised bands� (RP-230804; contact: Ericsson)	RAN
R2-2302464	LS to 3GPP on ECC request for standardisation support related to ECC Decision (22)07 on �harmonised framework on aerial UE usage in MFCN harmonised bands� (TFES(23)074033r1_LS_to_3GPP_on_aerial_UE; contact: Ericsson)	ETSI TC MSG/TFES
R2-2303171	Uncrewed Aerial Vehicles in Rel-18 - Updated Workplan	Nokia, Nokia Shanghai Bell
R2-2303172	Stage-2 Text Proposal for Rel-18 UAVs	Nokia, Nokia Shanghai Bell

7.8.2: Measurement reporting for mobility and interference control

TDoc	Title	Source
R2-2302681	Report of [POST121][313][UAV] Height-dependent configuration	Qualcomm Incorporated (Moderator)
R2-2302865	Interference control for combined event	Intel Corporation
R2-2302866	Height dependent RRM configuration to reduce measurement reporting	Intel Corporation
R2-2303058	Measurement and reporting enhancements	Qualcomm Incorporated
R2-2303068	UAV measurement reports	Ericsson
R2-2303095	Discussion on Measurement Reports Enhancements	NEC Europe Ltd
R2-2303147	Discussion on measurement reporting for NR UAV	Sharp
R2-2303173	On Interference Reporting and Height-dependent Configuration Adjustments for UAVs	Nokia, Nokia Shanghai Bell
R2-2303235	Discussion on height dependent measurement for NR UAV	Lenovo
R2-2303402	Measurement reporting enhancement in UAV	Apple
R2-2303430	Measurement reporting enhancement in NR UAV	ZTE Corporation, Sanechips
R2-2303431	Height-dependent measurement configuration	ZTE Corporation, Sanechips
R2-2303527	Measurement Reporting for NR UAV	CMCC
R2-2303805	Further discussion on NR support for UAV	NTT DOCOMO, INC.
R2-2303808	Discussion on measurement report for UAV	Huawei, HiSilicon
R2-2303846	Remaining issues on measurement reporting enhancements in NR UAV	Samsung Electronics Austria
R2-2303850	Discussion on measurement reporting for NR UAV	Xiaomi
R2-2303951	Discussion on measurement reporting enhancement for NR UAV	vivo
R2-2304176	Measurement Report Enhancement	LG Electronics
R2-2304491	Report of [AT121bis-e][306][UAV] Measurement Reporting (Qualcomm)	Qualcomm Incorporated (Moderator)

7.8.3: Flight path reporting

TDoc	Title	Source
R2-2302726	Consideration on flight path reporting for NR UAV	DENSO CORPORATION
R2-2302864	Flight path update triggering for UAV	Intel Corporation
R2-2302867	Report from [Post121][314][UAV] Flight path reporting	Intel Corporation
R2-2302901	On Flight Path Plan (FPP)	Nokia, Nokia Shanghai Bell
R2-2302905	UAV Flight Path Reporting	Ericsson Espa�a S.A.
R2-2303059	Flight path reporting enhancements	Qualcomm Incorporated
R2-2303105	Discussion on Flight Path Reporting	NEC Europe Ltd
R2-2303148	Discussion on flight path reporting for NR UAV	Sharp
R2-2303260	Remaining issues of flight path reporting for NR UAV	Lenovo
R2-2303401	Flight path reporting in UAV	Apple
R2-2303432	On flight path reporting	ZTE Corporation, Sanechips
R2-2303731	Flight path notification and reporting for UAV	InterDigital
R2-2303781	Further consideration on flight path reporting for NR UAV	China Telecom
R2-2303791	Discussion on opening issues for Flight path Reporting	CMCC
R2-2303809	Further discussion on flight path reporting	Huawei, HiSilicon
R2-2303851	Discussion on flight path reporting for NR UAV	Xiaomi
R2-2303888	Discussion on flight path reporting	Samsung
R2-2303902	Leftover Issue on Flight Path Reporting	CATT
R2-2303952	Discussion on flight path reporting	vivo
R2-2303992	[DRAFT] LS on flightpath information forwarding for UAV	Intel Corporation
R2-2304177	Flight Path Information Report	LG Electronics
R2-2304453	LS on flightpath information forwarding for UAV	Intel Corporation
R2-2304474	LS on flightpath information forwarding for UAV	RAN2

7.8.4: Subscription-based aerial-UE identification

TDoc	Title	Source
R2-2302682	Subscription-based Aerial-UE Identification in NR	Qualcomm Incorporated
R2-2302906	Subscription-Based Aerial UEs Identification	Ericsson Espa�a S.A
R2-2303528	Subscription-based aerial-UE identification for NR UAV	CMCC
R2-2303810	Discussion on subscription-based UAV identification	Huawei, HiSilicon
R2-2303844	Discussion on subscription-based aerial-UE identification for NR UAV	Samsung Electronics Austria
R2-2303953	Discussion on subscription-based aerial-UE identification	vivo

7.8.5: UAV identification broadcast

TDoc	Title	Source
R2-2302907	On Broadcasting UAV Identification	Ericsson Espa�a S.A.
R2-2303060	RAN2 aspects of PC5-based BRID and DAA support	Qualcomm Incorporated
R2-2303174	RAN2 Aspects of BRID and DAA for UAVs in Rel-18	Nokia, Nokia Shanghai Bell
R2-2303236	Discussion on broadcasting remote id for UAV	Lenovo
R2-2303403	Network enabling indication on UAV over PC5	Apple
R2-2303529	Further discussion on UAV identification broadcast	CMCC
R2-2303784	UAV Analysis of BRID and DAA Broadcast over PC5	Beijing Xiaomi Mobile Software
R2-2303811	Further discussion on UAV remote identification broadcast	Huawei, HiSilicon
R2-2303903	Re Discussion on the LS from SA2 for NR UAV	CATT
R2-2303904	The Gap for Supporting DAA as BRID	CATT
R2-2303954	Discussion on UAV identification broadcast	vivo
R2-2303988	Discussion on UAV identification and DAA broadcast	Samsung
R2-2304157	On UAV identification broadcast	ZTE Corporation, Sanechips
R2-2304354	[AT121bis-e][304][UAV] BRID and DAA(Xiaomi)	Xiaomi
R2-2304564	LS on BRID and DAA broadcast over LTE and NR PC5	RAN2

7.9.1: Organizational

TDoc	Title	Source
R2-2302442	LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN (S2-2207518; contact: LGE)	SA2
R2-2302445	Reply LS on Differentiation of Layer2 ID and Coexistence of U2N/U2U (S2-2303381; contact: CATT)	SA2
R2-2302994	Contents for rel-18 38.300 CR draft	LG Electronics Inc.
R2-2304293	[AT121bis-e][418][Relay] 38.300 relay CR draft (LG)	LG
R2-2304501	Reply LS on 5G ProSe Layer-2 UE-to-UE Relay QoS enforcement (S2-2305915; contact: Qualcomm)	SA2

7.9.2: UE-to-UE relay

TDoc	Title	Source
R2-2302492	Identification for bearer mapping and Connection establishment	NEC
R2-2302601	Discussion on U2U Relay	CATT
R2-2302643	Discussion on U2U relay	OPPO
R2-2302701	Discussion on L2 UE-to-UE relaying aspects	Intel Corporation
R2-2302791	Considerations on U2U relay (re)selection and Local ID assignment	Nokia, Nokia Shanghai Bell
R2-2302836	Control Plane Procedures for Layer-2 UE-to-UE Relays	Ericsson Espa�a S.A.
R2-2302902	Discussion on Relay (Re-)selection and Discovery	Ericsson Espa�a S.A.
R2-2302921	Discovery and Relay Selection for UE-to-UE Relays	InterDigital
R2-2302922	QoS and Adaptation Layer for UE-to-UE Relays	InterDigital
R2-2302997	Control plane procedure and adaptaion layer for U2U relay	LG Electronics Inc.
R2-2303004	Discussion on U2U Relay discovery and (re)selection	ZTE, Sanechips
R2-2303005	Discussion on U2U relay L2-specific functionality	ZTE, Sanechips
R2-2303012	Multiplexing and UE ID in the adaptation layer	Fujitsu
R2-2303088	UE-to-UE relay (re)selection	Sony
R2-2303222	Discussion on L2 U2U relay	Lenovo
R2-2303336	SRAP design for U2U Sidelink Relay	Samsung R&D Institute UK
R2-2303339	Discussion on the common L2 L3 parts for U2U relaying	vivo
R2-2303340	Discussion on the L2 specific parts for U2U relaying	vivo
R2-2303388	Discussion on open issues on UE-to-UE Relay	Apple
R2-2303486	Discussion on UE-to-UE relay	Huawei, HiSilicon
R2-2303506	Layer-2 specific part on U2U Relay	Qualcomm Incorporated
R2-2303545	Discussion on U2U relay	CMCC
R2-2303572	Discussion on UE-to-UE relay	Spreadtrum Communications
R2-2303608	Discussion on U2U relay	China Telecom
R2-2303648	Considerations for U2U L2 relay operations	Kyocera
R2-2303782	U2U relay � Relay UE discovery / (re)selection, SRAP, QoS Handling	Beijing Xiaomi Mobile Software
R2-2303934	Discussion on aspects of AS layer configuration for L2 U2U Relay	ASUSTeK
R2-2303935	Discussion on E2E security for supporting L2 UE-to-UE relay	ASUSTeK
R2-2303989	Integrated U2U relay discovery	Samsung
R2-2303990	QoS and Bearer configuration for U2U relaying	Samsung
R2-2303991	Discovery and relay reselection open aspects	Intel Corporation
R2-2304074	UE-to-UE relay (re)selection	Sharp
R2-2304123	Discussion on L2 U2U Relay	MediaTek Inc.
R2-2304194	Summary of AI 7.9.2 on UE-to-UE relay	Lenovo (Rapporteur)
R2-2304304	[AT121bis-e][431][Relay] SRAP proposals on U2U relay	Lenovo (Rapporteur)
R2-2304559	LS to SA3 on security for L2 UE-to-UE relay	RAN2

7.9.3: Service continuity enhancements for L2 UE-to-network relay

TDoc	Title	Source
R2-2302493	Support of Lossless Path Switching	NEC
R2-2302602	Considerations on Service Continuity Enhancements for L2 U2N Relay	CATT
R2-2302859	Discussion on lossless data delivery during inter-gNB path switching	Nokia, Nokia Shanghai Bell
R2-2302860	Discussion on service continuity issues for Inter-gNB path switching of L2 U2N relay	Nokia, Nokia Shanghai Bell
R2-2302869	Discussion on lossless path switching and measurement events	Intel Corporation
R2-2302903	Discussion on Inter-gNB Service Continuity	Ericsson Espa�a S.A.
R2-2302923	Lossless path switching from indirect to indirect/direct	InterDigital
R2-2302971	Discussion on Service Continuity Enhancements	NEC Corporation
R2-2302995	Path switching procedure for the service continuity enhancement	LG Electronics Inc.
R2-2303006	Further discussion on service continuity for SL relay	ZTE, Sanechips
R2-2303089	Service continuity enhancements for UE sidelink relay	Sony
R2-2303110	Discussion on lossless data forwarding for inter-gNB service continuity	OPPO, Xiaomi, Qualcomm Incorporated, Ericsson, Lenovo
R2-2303117	Discussion on service continuity enhancement	Xiaomi
R2-2303223	Service continuity for Inter-gNB path switching	Lenovo
R2-2303341	Remaining issues on service continuity enhancement for L2 U2N relay	vivo
R2-2303389	Discussion on Service continuity enhancement of L2 U2N relay	Apple
R2-2303507	Scenarios and solution on lossless delivery during path switch from indirect path to target path	Qualcomm Incorporated
R2-2303546	Discussion on service continuity	CMCC
R2-2303558	Discussion on Service Continuity	Huawei, HiSilicon
R2-2303564	Service continuity enhancements support for L2 U2N relay	Spreadtrum Communications
R2-2303609	CP and UP aspects of inter-gNB path switching	China Telecom
R2-2304075	remaining issues for U2N path switching with lossless delivery	Sharp
R2-2304124	Lossless data delivery in the inter-gNB cases	MediaTek Inc.
R2-2304305	Summary of [AT121bis-e][432] Candidate solutions for lossless delivery	NEC (Email Discussion Rapporteur)

7.9.4: Multi-path relaying

TDoc	Title	Source
R2-2302569	Discussion on multi-path SL relay	OPPO
R2-2302603	Discussion on Multi-path Scenario 1	CATT
R2-2302604	Discussion on Multi-path Scenario 2	CATT
R2-2302702	Open aspects of multi-path relaying	Intel Corporation
R2-2302904	Discussion on Multipath Relays	Ericsson Espa�a S.A.
R2-2302924	Design Aspects for Multi-path	InterDigital
R2-2302973	Discussion on Multi-path Relaying	NEC Corporation
R2-2303007	Further discussion on the support of multi-path relaying	ZTE, Sanechips
R2-2303013	Discussions on multi-path	Fujitsu
R2-2303090	Multi-path relaying discussion	Sony
R2-2303116	Discussion on multi-path	Xiaomi
R2-2303208	Remaining issues on multipath SL relay	Nokia, Nokia Shanghai Bell
R2-2303224	Multi-path establishment and operation	Lenovo
R2-2303342	Remaining Issues for Multi-path Scenario 1&2	vivo
R2-2303390	Discussion on control plan design for Multi-path	Apple
R2-2303391	Discussion on remaining issues on Scenario 2 for Multi-path	Apple
R2-2303487	Discussion on multi-path operation	Huawei, HiSilicon
R2-2303508	Open issues on multi-path relay for Scenario 1 and Scenario 2	Qualcomm Incorporated
R2-2303547	Discussion on multi-path scenario 1	CMCC
R2-2303548	Considerations on multi-path scenario 2	CMCC
R2-2303565	Discussion on multi-path relaying	Spreadtrum Communications
R2-2303610	Discussion on remaining issues of multi-path relaying	China Telecom
R2-2303647	Considerations for multipath relay operations for Scenario 1	Kyocera
R2-2303655	Discussion on Multi-path relaying	Lenovo
R2-2303659	Discussion on Sidelink Relay multi-path control plane procedure for Scenario 1	Philips International B.V.
R2-2303738	Discussion on Throughput Enhancements in Sidelink Multiplath Relaying	Fraunhofer IIS, Fraunhofer HHI
R2-2303857	Resubmitted proposals from [Pre121][407] Summary of AI 8.9.4	LG Electronics France
R2-2303859	Multi-path relaying for NR sidelink relay enhancements	LG Electronics France
R2-2303868	Discussion sidelink relay enhancement for scenario 1&2	Samsung
R2-2303936	Resource allocation and BSR reporting for multi-path	ASUSTeK
R2-2304076	C-plane aspects of multi-path	Sharp
R2-2304077	remaining issue for supporting senario2	Sharp
R2-2304122	Discussion on Multipath	MediaTek Inc.
R2-2304294	Report of [AT121bis-e][419][Relay] Remaining high-priority proposals on multi-path (LG)	LG Electronics Inc.
R2-2304303	Summary of [AT121bis-e][430][Relay] Multi-path relay idle/inactive cases (InterDigital)	InterDigital
R2-2304458	[draft] LS to SA2 on authorization for multi-path Scenario 2	vivo
R2-2304506	LS to SA2 on authorization for multi-path Scenario 2	RAN2

7.9.5: DRX

TDoc	Title	Source
R2-2302644	Discussion on DRX for L2 U2N relay	OPPO
R2-2303118	Discussion on SL DRX in U2N relay	Xiaomi
R2-2303488	Discussion on sidelink DRX for L2 U2N relay	Huawei, HiSilicon
R2-2303509	SL DRX for L2 U2N relay	Qualcomm Incorporated

7.10: IDC enhancements for NR and MR-DC

TDoc	Title	Source
R2-2302978	[Post121][654][IDC] Capability CRs on IDC (Intel)	Intel Corporation
R2-2302979	38.306 running CR for Rel-18 IDC UE capabilities	Intel Corporation
R2-2302980	38.331 running CR for Rel-18 IDC UE capabilities	Intel Corporation
R2-2303353	38.331 running CR for introduction of IDC	Xiaomi
R2-2303884	37.340 Running CR for Introduction of IDC	ZTE Corporation, Sanechips
R2-2304107	38.300 running CR for IDC Enhancements	Huawei, HiSilicon
R2-2304331	38.331 running CR for introduction of IDC	Xiaomi

7.11.1: Organizational

TDoc	Title	Source
R2-2302426	Reply LS on FS_5MBS_Ph2 progress (R3-231030; contact: Huawei)	RAN3
R2-2303630	Ensuring desired level of reliability for an MBS session in RRC_INACTIVE	Interdigital Inc.
R2-2303795	38.300 Running CR for MBS enhancements	CMCC
R2-2303971	RRC running CR for eMBS	Huawei, HiSilicon

7.11.2.1: Control plane

TDoc	Title	Source
R2-2302524	Discussions on PTM Configuration and Mobility	CATT, CBN
R2-2302525	Notifications for multicast reception in RRC_INACTIVE	CATT, CBN
R2-2302579	Multicast MCCH design for multicast in RRC INACTIVE	MediaTek inc.
R2-2302608	Control plane for multicast reception in RRC_INACTIVE state	TD Tech, Chengdu TD Tech
R2-2302669	Further Discussion on eMBS from CP	vivo
R2-2302769	Discussion on control plane for Multicast reception in RRC_INACTIVE	NEC Corporation
R2-2302962	CP aspects for Multicast reception in RRC_INACTIVE	Samsung R&D Institute India
R2-2303049	Service continuity, RRC state transitions and notifications	Qualcomm Incorporated
R2-2303129	Control plane aspects of multicast reception in RRC_INACTIVE	Nokia, Nokia Shanghai Bell
R2-2303159	Discussion for UEs receiving Multicast in RRC_INACTIVE state	TCL Communication Ltd.
R2-2303228	Discussion on CP aspects for multicast reception in RRC_INACTIVE	Lenovo
R2-2303271	Further consideration of PTM configuration and mobility aspects on multicast reception in RRC INACTIVE	Kyocera
R2-2303272	Notification and RRC state transition aspects on multicast reception in RRC INACTIVE	Kyocera
R2-2303307	PTM configuration for multicast reception in RRC_INACTIVE	LG Electronics Inc.
R2-2303308	Multicast activationdeactivation notification and RRC state transitions	LG Electronics Inc.
R2-2303419	PTM configuration for multicast reception in RRC_INACTIVE	Apple
R2-2303553	Summary of [Post121][606][eMBS] Service continuity and notifications (ZTE)	ZTE, Sanechips
R2-2303554	Misc CP issues on multicast reception in RRC_INACTIVE	ZTE, Sanechips
R2-2303585	Discussion on service continuity and RRC state transitions	Spreadtrum Communications
R2-2303620	Multicast reception in RRC_INACTIVE	Ericsson
R2-2303621	MBS multicast with eDRX and MICO mode	Ericsson
R2-2303776	RRC Resume for Multicast in RRC_INACTIVE	Sharp
R2-2303796	Discussion on PTM configuration related open issues	CMCC
R2-2303797	Discussion on RRC_INACTIVE UE join procedure	CMCC
R2-2303943	Consideration on the notifications for multicast reception in RRC_INACTIVE	Beijing Xiaomi Software Tech
R2-2303968	Multicast reception for RRC INACTIVE UE	Huawei, HiSilicon
R2-2304021	Control plane aspects for multicast reception in RRC_INACTIVE	Intel Corporation
R2-2304121	Discussion on PTM configuration	Shanghai Jiao Tong University
R2-2304328	Report of [AT121bis-e][603][eMBS] Service continuity and notifications (ZTE)	ZTE

7.11.2.2: User plane

TDoc	Title	Source
R2-2302494	HARQ operation during RRC state transitions for multicast reception	NEC
R2-2302609	User plane for multicast reception in RRC_INCTIVE state	TD Tech, Chengdu TD Tech
R2-2302670	Further Discussion on eMBS from UP	vivo
R2-2303050	Further views on multicast CFR configuration aspects	Qualcomm Incorporated
R2-2303130	User plane aspects of multicast reception in RRC_INACTIVE	Nokia, Nokia Shanghai Bell
R2-2303153	Discussion on UP issues for Multicast in RRC Inactive	LG Electronics Inc.
R2-2303201	Discussion on UP issues for multicast in RRC INACTIVE	MediaTek inc.
R2-2303229	Discussion on UP aspects for multicast reception in RRC_INACTIVE	Lenovo
R2-2303420	Summary of [Post121][607][eMBS] UP issues for Multicast in RRC Inactive (Apple)	Apple
R2-2303555	BWP and CFR for multicast reception in RRC_INACTIVE	ZTE, Sanechips
R2-2303959	Consideration on the support of PDCP count continuity	Beijing Xiaomi Software Tech
R2-2303969	Remaining UP issues for multicast reception in RRC_INACTIVE	Huawei, CBN, HiSilicon
R2-2304022	User plane aspects for multicast reception in RRC_INACTIVE	Intel Corporation
R2-2304151	User Plane Aspects for Multicast in INACTIVE	Samsung
R2-2304330	LS to RAN1 on multicast reception in RRC_INACTIVE	RAN2
R2-2304521	Report of [AT121bis-e][604][eMBS] UP issues for Multicast in RRC Inactive (Apple)	Apple

7.11.3: Shared processing for MBS broadcast and Unicast reception

TDoc	Title	Source
R2-2302526	Remaining issues on Shared Processing	CATT, CBN
R2-2302610	Simultaneous unicast reception and broadcast reception	TD Tech, Chengdu TD Tech
R2-2302671	Further Discussion on Shared Processing in eMBS	vivo
R2-2302770	Discussion on shared process for MBS broadcast and unicast	NEC Corporation
R2-2302961	Shared processing for MBS broadcast and unicast reception	Samsung R&D Institute India
R2-2303051	Shared processing for MBS broadcast and Unicast reception	Qualcomm Incorporated
R2-2303202	Discuss on Shared processing for broadcast and unicast reception	MediaTek inc.
R2-2303273	Shared processing for inter-PLMN MBS broadcast reception	Kyocera
R2-2303354	Remaining issues for shared processing of MBS	Xiaomi
R2-2303421	Shared processing of MBS broadcast and unicast reception	Apple
R2-2303556	Shared processing for MBS broadcast and Unicast reception	ZTE, Sanechips
R2-2303622	Shared processing for MBS broadcast and Unicast reception	Ericsson
R2-2303970	Discussion on shared processing for MBS broadcast and Unicast reception	Huawei, HiSilicon
R2-2304023	Shared processing for simultaneous MBS broadcast and Unicast reception	Intel Corporation
R2-2304060	Bandwidth signalling and scenarios for shared processing	Nokia, Nokia Shanghai Bell
R2-2304149	Discussion on Shared processing for MBS broadcast and unicast reception	CMCC

7.12.1: Organizational

TDoc	Title	Source
R2-2302424	Reply LS on FS_VMR solutions review (R3-231011; contact: Qualcomm)	RAN3
R2-2302890	Workplan for Rel-18 mobile IAB	Qualcomm Inc. (Rapporteur)

7.12.2: Mobility Enhancements

TDoc	Title	Source
R2-2302712	Enhancements for mobility of IAB-node together with Ues	CATT
R2-2303265	Mobile IAB remaining issues	vivo
R2-2304002	Discussion on the cell reselection and cell type indication aspects	Samsung R&D Institute UK
R2-2304003	Discussion on mIAB Connected mode mobility enhancement aspects	Samsung R&D Institute UK

7.12.2.1: Connected mode

TDoc	Title	Source
R2-2302784	mobile IAB mobility enhancement for connected UEs	Intel Corporation
R2-2302891	Support of mobile-IAB indicator in Msg 5	Qualcomm Inc.
R2-2302929	Mobile IAB connected mode issues and enhancements	Nokia, Nokia Shanghai Bell
R2-2303000	Discussion on mobility enhancement for UE in connected mode	ZTE, Sanechips
R2-2303047	Considerations on adopting LTM to mobile IAB use case	KDDI Corporation
R2-2303112	Discussion on mobility enhancements for mobile IAB	NEC Corporation
R2-2303242	Mobility enhancements for mobile IAB-node and its connected UE	Lenovo
R2-2303275	Connected mode mobility enhancements for mobile IAB	Kyocera
R2-2303380	RACH-less handover in mobile IAB	Apple
R2-2303503	Connected mode UE mobility enhancement for mobile IAB	Huawei, HiSilicon
R2-2303789	Connected mode mobility enhancements for mobile IAB	InterDigital Inc.
R2-2303852	On the need for connected mode mobility enhancements for mIAB	LG Electronics France
R2-2303945	Enhancements for IAB-node mobility and onboard UEs	AT&T
R2-2304098	Issues on supporting RACH-less for mobile IAB	Ericsson
R2-2304471	Summary of [AT121bis-e][015][eIAB] Beam handling RACH-less HO (Intel)	Intel Corporation

7.12.2.2: Idle/Inactive mode

TDoc	Title	Source
R2-2302785	UE cell (re)selection towards mobile IAB cell	Intel Corporation
R2-2302883	UE prioritization in cell reselection for mobile-IAB cells	SHARP Corporation
R2-2302930	Autonomous search for mobile IAB cells	Nokia, Nokia Shanghai Bell
R2-2303001	Discussion on mobility enhancement for UE in idle or inactive mode	ZTE, Sanechips
R2-2303091	Mobile IAB cell indication to UE behaviour	Sony
R2-2303274	IDLE/INACTIVE mode mobility enhancements for mobile IAB	Kyocera
R2-2303381	Discussion on IDLE/INACTIVE UE mobility enhancement	Apple
R2-2303504	Idle/Inactive mode UE mobility enhancement for mobile IAB	Huawei, HiSilicon
R2-2303631	IDLE/INACTIVE mobility enhancements for mobile IAB	Interdigital Inc.
R2-2303845	Idle mode mobility related to mIAB	LG Electronics France
R2-2304099	Behaviour for IDLE mode UEs under a mIAB node	Ericsson
R2-2304100	Consideration of CAG feature for mobile IAB	Ericsson

7.12.3: Other

TDoc	Title	Source
R2-2302713	Other aspects for mobile IAB	CATT
R2-2302786	TAC/RANAC update of mobile IAB-node	Intel Corporation
R2-2302892	Enhancements to default BAP configuration during DU migration	Qualcomm Inc.
R2-2302931	Mobile IAB BAP configuration issues	Nokia, Nokia Shanghai Bell
R2-2303002	Discussion on TAC and RNAC configuration of mobile IAB node	ZTE, Sanechips
R2-2303014	Discussions on BAP configurations supporting two logical DUs	Fujitsu
R2-2303092	PCI collision in mobile IAB	Sony
R2-2303243	Discussion on BAP handling and PCI collision avoidance	Lenovo
R2-2303333	Interference mitigation and PCI collision	Samsung R&D Institute UK
R2-2303505	Interference mitigation and BAP impacts	Huawei, HiSilicon
R2-2303941	Remaining BAP issues on full migration	LG Electronics Inc.

7.13.1: Organizational

TDoc	Title	Source
R2-2302423	LS on MRO for CPC and CPA and fast MCG recovery (R3-230992; contact: Huawei)	RAN3
R2-2302452	Reply LS on user consent of Non-public Network (S3-231399; contact: Vodafone)	SA3

7.13.2: MRO for inter-system handover for voice fallback

TDoc	Title	Source
R2-2302613	Consideration on Inter-system Handover for Voice Fallback	CATT
R2-2303143	Consideration on MRO for inter-system handover for voice fallback	ZTE Corporation, Sanechips
R2-2303183	Further discussion on MRO of inter-system HO voice fallback	OPPO
R2-2303244	MRO for inter-system handover for voice fallback	Lenovo
R2-2303453	MRO for inter-system handover for voice fallback	Ericsson
R2-2303683	MRO for inter-system handover for voice fallback	Samsung R&D Institute India
R2-2303694	Data collection for MRO for inter-system handover for voice fallback	Qualcomm Incorporated
R2-2303956	Discussion on MRO for inter-system handover for voice fallback	Huawei, HiSilicon
R2-2304198	[Pre121bis-e][822][SONMDT] Summary of agenda item 7.13.2 on MRO for inter-system handover for voice fallback	CATT

7.13.4: SHR and SPCR

TDoc	Title	Source
R2-2303804	Discussion on SPR	NTT DOCOMO, INC.

7.13.5: SON for NR-U

TDoc	Title	Source
R2-2302857	Discussion on SON for NR-U	Nokia, Nokia Shanghai Bell
R2-2302858	Discussion on storing LBT-FailureRecoveryConfig (Reply LS to R2-2300031)	Nokia, Nokia Shanghai Bell
R2-2303113	SON Enhancement for NR-U	CATT
R2-2303144	Consideration on NR-U related SON	ZTE Corporation, Sanechips
R2-2303245	Discussion on MRO for NR-U	Lenovo
R2-2303673	SON/MDT enhancements for NR-U	Samsung R&D Institute India
R2-2303695	Discussion on NR-U Related Enhancements	Qualcomm Incorporated
R2-2303803	SONMDT enhancement for NR-U	CMCC
R2-2304031	Discussion on SON for NR-U	Xiaomi
R2-2304111	Enhancements of SON reports for NR-U	Ericsson
R2-2304200	Summary of AI 7.13.5 SON for NR-U (Ericsson)	Ericsson

7.13.6: RACH enhancement

TDoc	Title	Source
R2-2302614	RACH enhancement for SON	CATT
R2-2302856	RA report retrieval	Nokia, Nokia Shanghai Bell
R2-2303145	Consideration on RACH enhancements	ZTE Corporation, Sanechips
R2-2303368	Remaining issues of SON enhancements for RACH	Apple
R2-2303454	RA report enhancement	Ericsson
R2-2303670	SON/MDT enhancements for RACH	Samsung R&D Institute India
R2-2303783	Discussion on RACH enhancement for SON	China Telecom
R2-2303798	Further considerations on RACH Enhancement	CMCC
R2-2303806	Consideration on the SON enhancements for RACH report	Beijing Xiaomi Software Tech
R2-2303829	SON enhancement for RA report	Sharp
R2-2303957	Discussion on RACH enhancement	Huawei, HiSilicon
R2-2304196	Summary of 7.13.6 RACH enhancement	Apple (moderator)

7.13.7: SON/MDT enhancements for Non-Public Networks

TDoc	Title	Source
R2-2303958	Discussion on SON MDT enhancements for NPN and NR-U	Huawei, HiSilicon

7.13.8: Other

TDoc	Title	Source
R2-2303182	SON on fast MCG recovery	OPPO
R2-2303246	Discussion on MRO for CPAC and fast MCG link recovery	Lenovo
R2-2303787	Discussion on CPAC failure report	NTT DOCOMO, INC.
R2-2303799	Further considerations on fast MCG recovery	CMCC

7.14.1: Organizational

TDoc	Title	Source
R2-2302425	LS on assistance information for handling of QoE reporting upon RAN overload (R3-231028; contact: Huawei)	RAN3
R2-2302461	Reply LS on QoE measurements in RRC IDLE/INACTIVE states (S5-232760; contact: Huawei)	SA5
R2-2302463	LS on Approval of eQoE CRs for NR (S5-232997; contact: Ericsson)	SA5
R2-2303597	[DRAFT] Further reply LS to SA4 on QoE measurements in RRC IDLE/INACTIVE	Huawei, HiSilicon
R2-2303599	[DRAFT] Further reply LS to SA5 on QoE measurements in RRC IDLEINACTIVE states	Huawei, HiSilicon
R2-2303676	Running CR for QoE measurements	Ericsson
R2-2304019	Draft reply LS on eQoE CRs for NR	Lenovo
R2-2304084	Revised Work Plan for Rel-18 NR QoE Enhancement	China Unicom
R2-2304396	Draft reply LS on eQoE CRs for NR	Lenovo
R2-2304399	[DRAFT] Further reply LS to SA4 on QoE measurements in RRC IDLE/INACTIVE	Huawei, HiSilicon
R2-2304401	Reply LS on Approval of eQoE CRs for NR	RAN2
R2-2304492	Reply LS on buffer level threshold-based RVQoE reporting (S4-230684; contact: Apple)	SA4
R2-2304529	Report of [AT121bis-e][221][QoE] LS replies to QoE	Huawei, HiSilicon

7.14.2: QoE measurements in RRC_IDLE INACTIVE

TDoc	Title	Source
R2-2302886	Discussion on support of QoE measurements in RRC_IDLE and RRC_INACTIVE	Lenovo
R2-2303108	Discussion on QoE measurement in IDLE and INACTIVE	ZTE Corporation, Sanechips
R2-2303319	Discussion on QoE measurement in RRC_IDLE and RRC_INACTIVE	Samsung
R2-2303363	QoE Measurements in IDLE/INACTIVE States	Apple
R2-2303510	QoE collection for IDLE and Inactive state	Qualcomm Incorporated
R2-2303532	Consideration on QoE measurement in RRC_IDLE and RRC_INACTIVE	CMCC
R2-2303596	Discussion on QoE measurements for MBS broadcast services	Huawei, HiSilicon
R2-2303642	On QoE measurements in RRC IDLE and INACTIVE	Nokia, Nokia Shanghai Bell
R2-2303677	QoE measurements in RRC_INACTIVE and RRC_IDLE	Ericsson
R2-2303780	Considerations on QoE measurements in RRC_IDLE and RRC_INACTICE	China Telecom
R2-2304037	Discussion on QoE measurements in RRC IDLE and INACTIVE state	CATT
R2-2304086	Discussion on QoE measurements in RRC_IDLE and INACTIVE states	China Unicom

7.14.4: Support of QoE measurements for NR-DC

TDoc	Title	Source
R2-2302951	Discussion on SRB5 configuration and procedure	NEC
R2-2303109	Discussion on QoE measurement for NR-DC	ZTE Corporation, Sanechips
R2-2303309	Support of QoE measurements for NR-DC	LG Electronics Inc.
R2-2303320	Discussion on switching reporting leg in NR-DC	Samsung
R2-2303364	Views on QoE Reporting for NR-DC	Apple
R2-2303511	RAN2 issues to support QoE collection in NR-DC	Qualcomm Incorporated
R2-2303598	Discussion on QoE measurements in NR-DC	Huawei, HiSilicon
R2-2303643	QoE configuration and reporting in NR-DC	Nokia, Nokia Shanghai Bell
R2-2303678	QoE measurements in NR-DC	Ericsson
R2-2304038	Discussion on support of QoE measurement for NR-DC	CATT
R2-2304085	Discussion on QoE configuration and reporting for NR-DC	China Unicom
R2-2304395	Report of [AT121bis-e][220][QoE] SRB5 configuration and usage (China Unicom)	China Unicom

7.15.1: Organizational

TDoc	Title	Source
R2-2302407	Reply LS on SL LBT failure indication and consistent SL LBT failure (R1-2302118; contact: vivo)	RAN1
R2-2302441	LS on co-channel coexistence (R4-2303718; contact: Huawei)	RAN4
R2-2302501	[Draft] LS Response to �Reply LS on SL LBT failure indication and consistent SL LBT failure�	vivo
R2-2302570	Work plan of R18 SL-Evo	OPPO, LG
R2-2304233	LS response on SL LBT failure indication and SL consistent LBT failure granularity	RAN2

7.15.2: SL-U: SL Consistent LBT failure

TDoc	Title	Source
R2-2302483	Further discussion on SL consistent LBT failure	vivo
R2-2302586	Discussion on SL consistent LBT failure for SL-U	Huawei, HiSilicon
R2-2302620	SL Consistent LBT failure	CATT
R2-2302645	Discussion on LBT impact in SL-U	OPPO
R2-2302838	LBT failure detection and recovery	Nokia, Nokia Shanghai Bell
R2-2302843	Handling consistent LBT failure	Ericsson
R2-2302872	On SL-U LBT failure	Intel Corporation
R2-2302916	LBT Failure for SL Unlicensed	InterDigital
R2-2302940	Discussion on left issues for SL-U LBT	SHARP Corporation
R2-2302948	Dicsussion on SL consistent LBT failure	NEC
R2-2302967	Discussion on SL Consistent LBT failure	LG Electronics France
R2-2303177	Discussion on Sidelink consistent LBT failure handling	ZTE Corporation, Sanechips
R2-2303216	Discussion on SL consistent LBT failure	Xiaomi
R2-2303232	Discussion on Consistent LBT for NR SL-U	Lenovo
R2-2303375	Discussion on SL consistent LBT failure	Apple
R2-2303573	Consistent LBT failure handling for SL-U	Spreadtrum Communications
R2-2303586	Discussion on SL Consistent LBT failure	Qualcomm India Pvt Ltd
R2-2304006	Discussion on SL Consistent LBT failure	ITL
R2-2304234	Summary of [AT121bis-e][509][V2X/SL] The need of Assistance Information (Xiaomi)	Xiaomi
R2-232465	Further discussion on SL consistent LBT failure	vivo

7.15.3: SL-U: COT sharing and LCP

TDoc	Title	Source
R2-2302498	COT and LCP enhancement	NEC
R2-2302571	Discussion on COT-Sharing and LCP Enhancement	OPPO
R2-2302587	Dissuccion on COT sharing and LCP for SL-U	Huawei, HiSilicon
R2-2302621	Discussion on COT sharing and LCP	CATT
R2-2302844	U2U COT sharing and LCP	Ericsson
R2-2302849	On COT sharing and LCP	Nokia, Nokia Shanghai Bell
R2-2302871	Discussion on COT sharing and LCP in SL-U	Intel Corporation
R2-2302917	COT Sharing for SL Unlicensed	InterDigital
R2-2302918	Implementing LCP for SL Unlicensed	InterDigital
R2-2302963	Discussion on COT sharing and LCP	LG Electronics France
R2-2303178	Discussion on COT sharing and LCP	ZTE Corporation, Sanechips
R2-2303197	LCP procedure for SL-U	Lenovo
R2-2303217	Discussion on assistance information for COT sharing	Xiaomi
R2-2303218	Discussion on aspects related to COT sharing	Xiaomi
R2-2303270	Discussion on assistance information for COT sharing	Xiaomi, Ericsson
R2-2303376	Discussion on COT sharing and LCP impact	Apple
R2-2303587	Discussion on COT sharing and LCP	Qualcomm India Pvt Ltd
R2-2303911	Discussion on changed-LCP and how UE behaves if shared-COT cannot be used	vivo
R2-2304020	Discussion on assistance information for COT sharing	Xiaomi, Ericsson, vivo

7.15.4: SL-U: Others

TDoc	Title	Source
R2-2302499	SL resource (re)selection	NEC
R2-2302572	Discussion on 'Best-Match'	OPPO, Apple, ZTE, Xiaomi, Qualcomm, MTK
R2-2302585	Discussion on remaining issues for SL-U	Huawei, HiSilicon
R2-2302622	Consideration on CAPC and LBT Impacts	CATT
R2-2302846	Other aspects on SL-U	Ericsson
R2-2302855	DTX operation in sidelink unlicensed	Nokia, Nokia Shanghai Bell
R2-2302873	Open aspects on SL-U operation	Intel Corporation
R2-2302919	Mode 2 Resource Selection for SL Unlicensed	InterDigital
R2-2302965	Discussion on remaining issues of SL-U	LG Electronics France
R2-2303179	Discussion on resouce allocation and CAPC in SL-U	ZTE Corporation, Sanechips
R2-2303233	Other remaining issue for NR SL-U	Lenovo
R2-2303377	Discussion on resource (re)selection, SL DRX and SL CG in SL-U	Apple
R2-2303588	Discussion on other design considerations for SL-U	Qualcomm India Pvt Ltd
R2-2303611	Discussion on SL CAPC leftovers	China Telecom
R2-2303914	Discussion on CAPC for non-standardized PQI to decide 'best match'	vivo, Lenovo, InterDigital, ASUSTeK, Huawei, HiSilicon
R2-2304013	Discussion on SL DRX	ITL

7.15.5: SL-FR2

TDoc	Title	Source
R2-2302500	Sidelink Operation on FR2	NEC
R2-2302623	Discussion on Sidelink Operation on FR2	CATT
R2-2302646	Discussion on SL-FR2 impact	OPPO
R2-2302657	Discussion on SL-FR2 aspects in RAN2	Nokia Germany
R2-2302687	Discussion on SL-FR2	Huawei, HiSilicon
R2-2302845	SL in FR2	Ericsson
R2-2302870	RAN2 aspects to support SL FR2	Intel Corporation
R2-2302968	Discussion on RAN2 aspects of SL-FR2	LG Electronics France
R2-2303119	Discussion on SL-FR2 impact to RAN2	Xiaomi
R2-2303180	Initial consideration on sidelink FR2	ZTE Corporation, Sanechips
R2-2303234	Discussion on FR2 operation for NR SL-U	Lenovo
R2-2303378	Discussion on RAN2 work of SL FR2	Apple
R2-2303483	RAN2 Aspects of NR Sidelink Operation in FR2	Fraunhofer IIS, Fraunhofer HHI
R2-2303574	Discussion on sidelink operation on FR2	Spreadtrum Communications
R2-2303589	Discussion on SL FR2	Qualcomm India Pvt Ltd
R2-2303910	Discussion on RAN2 aspects for FR2 licensed spectrum	vivo

7.15.6: SL CA Enhancements

TDoc	Title	Source
R2-2302555	Support of CA for NR Sidelink Mode-2	vivo
R2-2302573	Discussion on Carrier Aggregation	OPPO
R2-2302624	Discussion on NR sidelink CA	CATT
R2-2302688	Discussion on SL CA operation	Huawei, HiSilicon
R2-2302847	Aspects of SL CA	Ericsson
R2-2302874	Discussion on NR SL Carrier Aggregation	Intel Corporation
R2-2302920	Carrier Aggregation for NR SL	InterDigital
R2-2302969	Discussion on RAN2 aspects of SL-CA enhancements	LG Electronics France
R2-2303181	Initial consideration on sidelink CA	ZTE Corporation, Sanechips
R2-2303207	On the scope of NR sidelink CA	Nokia, Nokia Shanghai Bell
R2-2303219	Discussion on carrier aggregation for NR sidelink	Xiaomi
R2-2303379	Initial discussion on Sidelink CA	Apple
R2-2303482	RAN2 Aspects of NR Sidelink Carrier Aggregation	Fraunhofer IIS, Fraunhofer HHI
R2-2303590	Discussion on SL CA	Qualcomm India Pvt Ltd
R2-2304232	Summary report of [AT121bis-e][507] Applicability of carrier mapping from V2X layer to UC (Apple)	Apple
R2-2304236	LS on carrier mapping for unicast SL CA	RAN2

7.16.2.1: Architecture General

TDoc	Title	Source
R2-2302488	AIML Architecture Assumptions	NEC
R2-2302546	Discussion on Model ID and Model Meta Data	OPPO
R2-2302547	Functionality Mapping for LCM Purposes	OPPO
R2-2302649	AIML architecture	Nokia, Nokia Shanghai Bell, T-Mobile US
R2-2302746	General architecture assumptions, model ID and entity mapping	Intel Corporation
R2-2302899	Architecture General	InterDigital
R2-2302953	Discussion on Architecture General	vivo
R2-2303017	Further discussions on architecture general aspects of AIML for NR air-interface	CATT, Turkcell
R2-2303053	AI/ML functionality and model-ID based LCM procedure	Samsung R&D Institute UK
R2-2303093	Some considerations about EVEX and CP/UP solutions	Sony
R2-2303122	Discussion on architecture aspects	Xiaomi
R2-2303240	Discussion on AI/ML functionality mapping	Lenovo
R2-2303371	Discussion on AI/ML model identification, LCM and capability	Apple
R2-2303372	Discussion on AI/ML functionality mapping to network entities	Apple
R2-2303521	Discussion on general architecture for AIML for NR air interface	CMCC
R2-2303580	Discussion on general AI architecture	Spreadtrum Communications
R2-2303672	Discussion on AI/ML Capability Reporting and Model LCM	SHARP Corporation
R2-2303674	Discussion on AI/ML Architecture General	Qualcomm Incorporated
R2-2303760	Model ID and Mapping of Functions to Physical Entities	MediaTek Inc.
R2-2303885	Discussion on AI/ML model identification and functionality identification	Futurewei Technologies
R2-2303893	Discussion on model ID and mapping of functionality to entities	Huawei, HiSilicon
R2-2303946	Model identification and LCM aspects of AI/ML for NR air interface	AT&T
R2-2304116	Architecture and management for AIML	Ericsson
R2-2304126	Discussion on Functionality Mapping within NW	ZTE Corporation, Sanechips
R2-2304173	AIML method_Architecture General	LG Electronics
R2-2304195	Report of [AT121bis-e][014][AIML18] Model ID (incl meta data) progress (OPPO)	OPPO

7.16.2.2: Data Collection

TDoc	Title	Source
R2-2302489	AIML Data Collection	NEC
R2-2302548	Data Collection for LCM Purposes	OPPO
R2-2302650	AIML data collection	Nokia, Nokia Shanghai Bell
R2-2302747	Further analysis on data collection framework	Intel Corporation
R2-2302954	Discussion on data collection	vivo
R2-2303018	Considerations on data collection of AIML for NR air-interface	CATT, Turkcell
R2-2303121	Discussion on data collection	Xiaomi
R2-2303241	Qualitative analysis on data collection requirements	Lenovo
R2-2303373	Further discussion on data collection for AI/ML	Apple
R2-2303522	Discussion on data collection for AIML model	CMCC
R2-2303581	Discussion on data collection	Spreadtrum Communications
R2-2303627	Data collection for AIML	Interdigital Inc.
R2-2303668	Further discussion on Data Collection for AI/ML	Samsung R&D Institute UK
R2-2303684	Discussion on Data Collection for Offline Model Training	Qualcomm Incorporated
R2-2303761	Discussion on Data Collection	MediaTek Inc.
R2-2303894	Discussion on data collection	Huawei, HiSilicon
R2-2303947	Data collection aspects of AI/ML for NR air interface	AT&T
R2-2304035	Data collection for AIML methods	TCL Communication Ltd.
R2-2304112	Data collection for AI/ML	Ericsson
R2-2304127	Discussion On the Purpose Driven Data Collection in LCM	ZTE Corporation, Sanechips
R2-2304159	Discussion on relations between LCM and Data collection	NTT DOCOMO INC.
R2-2304174	AIML method_Data Collection	LG Electronics
R2-2304187	Discussion on relations between LCM and Data collection	NTT DOCOMO INC.
R2-2304534	Report of [AT121bis-e][024][AIML18] on Data Collection Table (Nokia)	Nokia (Rapporteur)
R2-2304541	Report of [AT121bis-e][024][AIML18] on Data Collection Table (Nokia)	Nokia (Rapporteur)

7.16.2.3: Model transfer ? delivery

TDoc	Title	Source
R2-2302490	AIML Model transfer	NEC
R2-2302491	AIML Model transfer for mobility	NEC
R2-2302549	Open Issue Discussion on Model Transfer/Delivery	OPPO
R2-2302651	AIML model transfer delivery	Nokia, Nokia Shanghai Bell
R2-2302748	architecture impact on model transfer method	Intel Corporation
R2-2302955	Discussion on model transfer	vivo
R2-2303015	Discussions on AIML model transfer via air interface	Fujitsu
R2-2303019	Further discussions on AIML model transfer	CATT, Turkcell
R2-2303054	Model transfer/delivery solutions	Samsung R&D Institute UK
R2-2303094	Some considerations about CSI compression	Sony
R2-2303120	Discussion on model delivery	Xiaomi
R2-2303374	Further discussion on model transfer	Apple
R2-2303523	Discussion on AIML model transfer delivery	CMCC
R2-2303582	Discussion on model transfer-delivery	Spreadtrum Communications
R2-2303628	Way forward for AIML Model transfer/delivery	Interdigital Inc.
R2-2303693	Discussion on Model Transfer/Delivery	Qualcomm Incorporated
R2-2303762	Discussion on AI/ML Model Transfer/Delivery	MediaTek Inc.
R2-2303778	Discussion on gNB LMF awareness of UE side model	Lenovo
R2-2303895	Discussion on model transfer and model delivery	Huawei, HiSilicon
R2-2303948	AI/ML model transfer and delivery	AT&T
R2-2304040	Discussion on Model transfer/delivery for AIML methods	TCL Communication Ltd.
R2-2304117	On the need for model transfer	Ericsson
R2-2304128	urther Considerations On the Model Transfer study in RAN2	ZTE Corporation, Sanechips
R2-2304175	AIML method_Model Transfer Delivery	LG Electronics

7.16.2.4: Model Control other

TDoc	Title	Source
R2-2302652	AIML control and other topics	Nokia, Nokia Shanghai Bell
R2-2302749	model control procedure: RAN2 impact	Intel Corporation
R2-2302753	AI ML model management during RRC state transitions and mobility	Rakuten Symphony
R2-2302900	Decision and Signaling for AI/ML Model Switching	InterDigital
R2-2302956	Discussion on model monitoring	vivo
R2-2303020	Considerations on other model control procedures	CATT, Turkcell
R2-2303055	Indication of supported AI/ML models and functionalities	Samsung R&D Institute UK
R2-2303442	AI/ML model control for positioning accuracy enhancement	Xiaomi
R2-2303583	Discussion on other model control method	Spreadtrum Communications
R2-2303685	Discussion on Model Life Cycle Management	Qualcomm Incorporated
R2-2303763	Model Control and Model Monitoring	MediaTek Inc.
R2-2303896	Discussion on model control and others	Huawei, HiSilicon
R2-2303949	AI/ML model control	AT&T
R2-2304118	Applicability reporting	Ericsson
R2-2304129	Consideration on General Porocedure For Different Use Cases	ZTE Corporation, Sanechips

7.17.1: Organizational

TDoc	Title	Source
R2-2302430	LS on priority for MUSIM gaps (R4-2303249; contact: vivo)	RAN4
R2-2303266	MUSIM Stage 2 running CR	vivo

7.17.2: Procedures for MUSIM temporary capability restriction

TDoc	Title	Source
R2-2302550	Procedures for MUSIM temporary capability restriction	OPPO
R2-2302721	UE Capability restrictions for Dual-Active MUSIM	Qualcomm Incorporated
R2-2302725	Consideration on capability restriction for dual Rx/Tx MUSIM	DENSO CORPORATION
R2-2302781	Further considerations on the capability restriction request for Rel-18 MUSIM	Intel Corporation
R2-2303188	Baseline signalling procedure options for temporary capability restrictions.	Nokia, Nokia Shanghai Bell
R2-2303225	Procedure of dual Tx/Rx Multi-SIM	Lenovo
R2-2303267	Procedures for MUSIM temporary capability restriction	vivo
R2-2303409	Procedures for MUSIM temporary capability restriction	Apple
R2-2303455	Further discussion on the UE-initiated SCell/SCG deactivation and activation for MUSIM	Huawei, HiSilicon, Vodafone, Vivo
R2-2303639	Overall Dual-RX/TX MUSIM procedure	Ericsson
R2-2303669	Procedures for MUSIM temporary capability restriction	Samsung R&D Institute India
R2-2303774	Procedure of UE Capability Restriction for eMUSIM	Sharp
R2-2303874	Temporary Capability Restriction for Idle/Inactive State Transfer	ZTE Corporation, Sanechips
R2-2304026	Procedures for MUSIM Temporary Capa Restriction	LG Electronics

7.17.3: Allowed MUSIM temporary capability restrictions

TDoc	Title	Source
R2-2302551	Allowed MUSIM temporary capability restrictions	OPPO
R2-2302782	Signalling to indicate temporary capability reduction for Rel-18 MUSIM	Intel Corporation
R2-2302966	Allowed MUSIM temporary capability restrictions	Samsung R&D Institute India
R2-2303189	Adidtional aspects related to capability restriction signalling	Nokia, Nokia Shanghai Bell
R2-2303268	Discussion on temporary capability restriction for Rel-18 Multi-SIM	vivo
R2-2303350	Capability sharing issue for SRS Tx switching capability	Xiaomi
R2-2303351	Remaining issues on band combination restrictions due to band conflict	Xiaomi
R2-2303410	Parameters for MUSIM temporary capability restriction	Apple
R2-2303470	Further discussion on MUSIM temporary capability restrictions	Huawei, HiSilicon
R2-2303623	Discussion on temporary UE capability restriction for MUSIM	MediaTek Inc.
R2-2303624	Disucssion on UE capability restriction signaling	China Telecommunications
R2-2303640	Discussion on restricted UE capabilities	Ericsson
R2-2303779	Support of UE requesting SCell/SCG Deactivation for eMUSIM	Sharp
R2-2303873	Consideration on the Temporary Capability Restriction	ZTE Corporation, Sanechips
R2-2303938	Discussion on temporary capability restriction for Dual Tx/Rx Multi-SIM	ASUSTeK
R2-2304027	Simple Methods for MUSIM Temporary Capa Restriction	LG Electronics
R2-2304397	Report of [AT121bis-e][230][MUSIM] UE capability restrictions (vivo)	vivo

7.17.4: MUSIM gap priorities and other RAN4 impacts

TDoc	Title	Source
R2-2302724	Remaining issues for MUSIM gaps	Qualcomm Incorporated
R2-2302783	Gap collision handling for Rel-17 gaps	Intel Corporation
R2-2303190	On MUSIM gap priority and uplink power sharing aspects of MUSIM operation	Nokia, Nokia Shanghai Bell
R2-2303269	Discussion on MUSIM gap priorities	vivo
R2-2303352	Discussion on MUSIM gap priorities	Xiaomi
R2-2303411	Views on RAN4 LS for MUSIM gap priorities	Apple
R2-2303471	Discussion on MUSIM gaps and other RAN4 topics	Huawei, HiSilicon
R2-2303641	MUSIM gap priorities	Ericsson
R2-2303828	Discussion on MUSIM gap priorities and maximum UL power change	Samsung Electronics Austria
R2-2303875	Consideration on the Scheduling Gap Priority	ZTE Corporation, Sanechips
R2-2303937	Discussion on maximum UL power change for Dual Tx/Rx Multi-SIM	ASUSTeK
R2-2304028	MUSIM Gap Priority	LG Electronics
R2-2304398	Report of [AT121bis-e][231][MUSIM] RAN4 aspects of MUSIM (Samsung)	Samsung

7.19.1: Organizational

TDoc	Title	Source
R2-2302417	Reply LS on long eDRX support for RRC_INACTIVE (R3-230803; contact: Ericsson)	RAN3
R2-2304497	Reply LS on Paging Policy Information for Network Triggered Connection Resume (S2-2305617; contact: Ericsson)	SA2
R2-2304498	Reply LS on INACTIVE eDRX above 10.24sec and SDT (S2-2305619; contact: Intel)	SA2

7.19.2: Enhanced eDRX in RRC_INACTIVE

TDoc	Title	Source
R2-2302496	Fallback behaviour for eRedcap UE	NEC
R2-2302497	Paging monitoring for Inactive UE in enhanced eDRX	NEC
R2-2302531	Discussion on enhanced eDRX in RRC_INACTIVE	OPPO
R2-2302565	Discussion on enhanced eDRX in RRC_INACTIVE	CATT
R2-2302642	Discussion on enhanced eDRX in RRC_INACTIVE	China Telecommunications
R2-2302703	Discussion on e-DRX for eRedcap Devices	Xiaomi Communications
R2-2302735	RAN2 impacts to support eDRX in RRC_INACTIVE above 10.24 sec	Intel Corporation
R2-2302803	On eDRX for enhanced RedCap	Nokia, Nokia Shanghai Bell
R2-2302815	Discussion on UE fallback behaviour for INACTIVE eDRX	vivo, Guangdong Genius
R2-2302816	Enhanced eDRX cycle in RRC_INACTIVE for eRedCap UEs	vivo, Guangdong Genius
R2-2302824	Further discussion on longer eDRX in RRC_INACTIVE	ZTE Corporation, Sanechips
R2-2303304	Enhanced eDRX in RRC_INACTIVE	MediaTek Inc.
R2-2303321	Discussion on available eDRX configurations	Samsung
R2-2303322	Discussion on enhanced eDRX in RRC_INACTIVE	Samsung
R2-2303396	RedCap PTW/PH operation for >10.24sec INACTIVE eDRX	Apple
R2-2303397	RedCap UE behavior in cells not supporting R18 eDRX	Apple
R2-2303468	Discussion on enhanced eDRX in RRC_INACTIVE	Huawei, HiSilicon
R2-2303542	Discussion on eDRX in RRC_INACTIVE	CMCC
R2-2303561	Discussion on enhanced eDRX in RRC inactive	Qualcomm Incorporated
R2-2304063	Extending eDRX cycles in RRC_INACTIVE	Ericsson
R2-2304361	Summary of [AT121bis-e][751][eRedCap] eDRX for RRC_INACTIVE (OPPO)	OPPO
R2-232468	Discussion on enhanced eDRX in RRC_INACTIVE	OPPO

7.19.3: Further reduced UE complexity in FR1

TDoc	Title	Source
R2-2302528	Discussion on access restriction for eRedCap	Futurewei
R2-2302532	Discussion on early indication for eRedCap UE	OPPO
R2-2302544	Discussion on cellbarring for eRedCap UEs	OPPO
R2-2302566	Discussion on further UE complexity reduction	CATT
R2-2302640	Discussion on access restriction and capability related for eREDCAP	China Telecommunications
R2-2302641	Discussion on Early Indication for eREDCAP	China Telecommunications
R2-2302704	Discussion on early indication for eRedcap devices	Xiaomi Communications
R2-2302705	Discussion on UE access restrictions and other impacts for eRedcap devices	Xiaomi Communications
R2-2302736	RAN2 impacts to support Rel-18 RedCap UEs	Intel Corporation
R2-2302737	Capability impacts to support Rel-18 RedCap UEs	Intel Corporation
R2-2302802	On access restrictions for enhanced RedCap	Nokia, Nokia Shanghai Bell
R2-2302817	Discussion on access restriction and capability for eRedCap	vivo, Guangdong Genius
R2-2302825	Early indication and access restriction for eRedCap UE	ZTE Corporation, Sanechips
R2-2302826	Capability definition and report for eRedCap UE	ZTE Corporation, Sanechips
R2-2302949	Discussion on early indication and access restriction for eRedCap	NEC
R2-2303069	Early identification and access restriction for eRedCap UEs	Huawei, HiSilicon
R2-2303070	Discussion on how to define and capture the capability of eRedCap UEs	Huawei, HiSilicon
R2-2303149	Discussion on access restriction for eRedCap	Sharp
R2-2303305	Early identification for eRedCap devices	MediaTek Inc.
R2-2303306	Access restrictions for eRedCap devices	MediaTek Inc.
R2-2303323	Discussion on early indication and access restriction	Samsung
R2-2303543	Discussion on further reduced UE complexity	CMCC
R2-2303562	Discussion on further complexity reduction for eRedCap UE	Qualcomm Incorporated
R2-2303563	Discussion on optional UE capability filter for eRedCap UE	Qualcomm Incorporated, Ericsson, Intel
R2-2303568	Discussion on further reduced UE complexity in FR1 for Rel-18 RedCap UE	Spreadtrum Communications
R2-2303657	Early indication and access restrictions for eRedCap UE	Sierra Wireless. S.A.
R2-2303689	On early indication for enhanced RedCap	Nokia, Nokia Shanghai Bell
R2-2304010	Further discussion on early indication for Rel-18 RedCap UE	LG Electronics Inc.
R2-2304062	Early indication for eRedCap UEs	Ericsson
R2-2304064	Discussion on cell barring for eRedCap UEs	Ericsson
R2-2304069	Discussion on further UE complexity reduction for eRedCap	NTT DOCOMO INC.
R2-2304171	Considerations on Further reduced UE complexity for eRedcap	Sequans Communications
R2-2304190	Discussion on further UE complexity reduction for eRedCap	NTT DOCOMO INC.
R2-2304362	Summary of [AT121bis-e][752] Further reduced UE complexity in FR1 (Huawei)	Huawei, HiSilicon
R2-232469	Discussion on early indication for eRedCap UE	OPPO
R2-232481	Discussion on cellbarring for eRedCap UEs	OPPO

7.20.1: Organizational

TDoc	Title	Source
R2-2302455	LS to RAN2/4 on Agreements for Rel-18 MIMO (R1-2302226; contact: Samsung)	RAN1
R2-2302616	RAN2 work plan for MIMO evolution	NTT DOCOMO, INC., Samsung, Huawei, HiSilicon

7.20.2: Two TAs for multi-DCI multi-TRP

TDoc	Title	Source
R2-2302568	Discussion on multiple TAG	OPPO
R2-2302692	Discussion on multi-DCI multi-TRP with two TAs	Intel Corporation
R2-2302879	Two TAs for multi-DCI multi-TRP	Huawei, HiSilicon
R2-2302939	Discussion on Multi-TRP with two TAs	SHARP Corporation
R2-2302975	Discussion on two TAs for multi-TRP	NEC Corporation
R2-2303016	Considerations on multi-DCI multi-TRP operation with two TAs	Fujitsu
R2-2303022	Discussions on Two TAs for multi-DCI multi-TRP	CATT
R2-2303248	Discussion on the impacts of Two TAs for multi-DCI multi-TRP operation	Lenovo
R2-2303249	Discussion on the UE-initiated RACH procedure in multi-TRP operation	Lenovo
R2-2303422	Support of Two TAs for multi-DCI multi-TRP	Apple
R2-2303560	Discussion on multi-DCI multi-TRP with two TAs	Qualcomm Incorporated
R2-2303690	On multi-DCI multi-TRP with two TAs	Nokia, Nokia Shanghai Bell
R2-2303691	RA procedure while SpCell is configured with 2 TAGs	Nokia, Nokia Shanghai Bell
R2-2303708	On 2TA operation	Ericsson
R2-2303732	UL time alignment in multi-DCI based multi-TRP with two TAs	InterDigital
R2-2303757	Discussion on TA maintenance in two TAs for multi-TRP	LG Electronics Inc.
R2-2303769	Discussion on two TAs for multi-DCI multi-TRP	Samsung Research America
R2-2304042	Discussion on two TAs for multi-TRP	Xiaomi
R2-2304131	Intial Discussion On 2TA for unified TCI state based mPDCCH mTRP	ZTE Corporation,Sanechips
R2-2304132	Considerations on the PDCCH order RACH for acquiring the TRP sepcific TA	ZTE Corporation,Sanechips
R2-2304341	DRAFT LS on 2TA operation for Rel-18 MIMO	Ericsson
R2-2304342	LS on 2TA for multi-DCI multi-TRP	RAN2

7.20.3: Other

TDoc	Title	Source
R2-2302880	Extension of unified TCI framework for mTRP	Huawei, HiSilicon
R2-2303023	Discussion on Unified TCI Framework Extension for Multi-TRP	CATT
R2-2303064	MAC impacts on the enhancements of the unified TCI state framework	Samsung
R2-2303725	On incoming LSs on Rel-18 MIMO	Ericsson
R2-2303758	Discussion on power control for multi-TRP	LG Electronics Inc.
R2-2303939	Intra-UE prioritization for simultaneous multi-panel transmission	ASUSTeK

7.21.1: Organizational

TDoc	Title	Source
R2-2303074	Work plan for Further NR coverage enhancements	China Telecom

7.21.2: General

TDoc	Title	Source
R2-2302567	Discussion on PRACH coverage enhancements	CATT
R2-2302598	RAN2 Impacts of Further NR Coverage Enhancements	vivo
R2-2302600	RAN2 Impacts for further NR Coverage Enhancements	Samsung Electronics Co., Ltd
R2-2302888	Discussion on Multiple PRACH transmissions	Ericsson
R2-2302926	Uplink Coverage Enhancement	Qualcomm Incorporated
R2-2303075	RAN2 impacts of Coverage Enhancement	China Telecom
R2-2303292	RAN2 impacts on R18 PRACH coverage enhancements	ZTE Corporation, Sanechips
R2-2303605	Multiple PRACH transmissions	InterDigital
R2-2303692	RAN2 impacts of PRACH CE	Nokia, Nokia Shanghai Bell
R2-2303815	Discussion on RAN2 impacts for PRACH coverage enhancement	Huawei, HiSilicon
R2-2304011	RAN2 aspects on support of multiple PRACH transmission	LG Electronics Inc.
R2-2304034	Discussion on RAN2 impact of PRACH enhancement	Xiaomi

7.22.1: Organizational

TDoc	Title	Source
R2-2302661	Scope of Rel-18 SI on LP-WUS/WUR	vivo (Rapporteur)
R2-2303462	Update of TR 38.869 for LP-WUS WUR	vivo (Rapporteur)
R2-2303463	Work Plan for Rel-18 SI on LP-WUS/WUR	vivo (Rapporteur)

7.22.2: General

TDoc	Title	Source
R2-2302518	Use of low-power receiver in RRC Idle/Inactive	Qualcomm Incorporated
R2-2302519	Use of low-power receiver in RRC Connected	Qualcomm Incorporated
R2-2302537	Discussion on RRM measurement for LP-WUR	OPPO
R2-2302542	Discussion on LP-WUR�s operation	OPPO
R2-2302662	Discussion on LP-WUS/WUR in RRC_Idle/Inactive	vivo
R2-2302663	Discussion on LP-WUS/WUR in RRC_Connected	vivo
R2-2302706	General considerations on the procedure of LP-WUS	Xiaomi Communications
R2-2302707	Discussiong on LP-WUS monitoring	Xiaomi Communications
R2-2302777	Discussion on general aspect for LPWUS from RAN2 perspective	NEC Corporation
R2-2302801	On low-power wake-up signal in RRC IDLE and INACTIVE	Nokia, Nokia Shanghai Bell
R2-2302827	Considerations on RAN2 impacts of LP-WUS	ZTE Corporation, Sanechips
R2-2302828	Paging mechanism with LP-WUS	ZTE Corporation, Sanechips
R2-2302977	Impact of LP-WUR in RRC Idle/Inactive	Intel Corporation
R2-2302981	Impact of LP-WUR in RRC Connected mode	Intel Corporation
R2-2302984	Discussion on LP-WUS impact on higher layer procedures	CATT
R2-2303209	Low-power WUS in RRC_CONNECTED	Nokia, Nokia Shanghai Bell
R2-2303423	RAN2 impact on LP-WUS	Apple
R2-2303469	High layer procedures for low-power WUS in IDLE and INACTIVE state	Huawei, HiSilicon
R2-2303493	RAN2 impacts to support LP-WUS	Huawei, HiSilicon
R2-2303747	Discussion on impact to IDLE/INACTIVE procedures to support LP-WUR	SAMSUNG R&D INSTITUTE INDIA
R2-2303750	Discussion on impact to Connected mode procedures to support LP-WUR	SAMSUNG R&D INSTITUTE INDIA
R2-2304067	LP-WUS design and L1 procedure	Ericsson
R2-2304068	LP-WUR Higher-Layer Aspects	Ericsson
R2-232474	Discussion on RRM measurement for LP-WUR	OPPO
R2-232479	Discussion on LP-WUR�s operation	OPPO

7.23.1: Organizational

TDoc	Title	Source
R2-2302418	Reply LS on proposed method for time synchronization status reporting to UE(s) (R3-230811; contact: Nokia)	RAN3
R2-2303864	Timing Resiliency and URLLC enh Workplan	Nokia, Nokia Shanghai Bell
R2-2304489	Response to Reply LS on Proposed method for Time Synchronization status reporting to UE(s) (C1-232942; contact: Nokia)	CT1

7.23.2: General

TDoc	Title	Source
R2-2302689	Discussion on 5GS Clock quality information delivery to UE	Huawei, HiSilicon
R2-2302690	Discussion on UL reactive RAN feedback for burst sending time adjustment	Huawei, HiSilicon
R2-2302722	Discussion on RAN Feedback for Low Latency Communication	vivo
R2-2302723	Discussion on 5GS Network Timing Synchronization Status and Reporting	vivo
R2-2302761	RAN2 Impact of timing synchronization status information delivery in CONNECTED mode	CATT
R2-2302762	Impact of timing synchronization status and reporting in IDLE/INACTIVE mode	CATT
R2-2302833	Considerations on BAT offset	ZTE Corporation, Sanechips
R2-2302834	Considerations on time synchronization status and reporting	ZTE Corporation, Sanechips
R2-2302932	Timing Synchronization Reporting	Qualcomm Incorporated
R2-2302933	UL BAT Reporting and Adjustment	Qualcomm Incorporated
R2-2303382	Views on RAN feedback for burst sending time adjustment	Apple
R2-2303723	Discussion on NR Timing Resiliency	Ericsson
R2-2303733	RAN2 impact of DL and UL scheduling adaptation and BAT offset deviation	Ericsson
R2-2303777	Discussion on timing resiliency and URLLC enhancements	China Telecom
R2-2303816	5GS network timing synchronization status and reporting	Intel Corporation
R2-2303817	RAN reactive UL feedback for burst sending time adjustment	Intel Corporation
R2-2303865	5GS network timing synchronization status and reporting	Nokia, Nokia Shanghai Bell
R2-2303866	Reactive RAN feedback for upstream scheduling	Nokia, Nokia Shanghai Bell
R2-2304152	Delivery of 5G Clock Quality Information	Samsung
R2-2304153	Adaptive Upstream Scheduling Based on RAN Feedback	Samsung

7.24.1: TEI proposals by Other Groups

TDoc	Title	Source
R2-2302411	LS on SR periodicity (R1-2302187; contact: Ericsson)	RAN1
R2-2302413	LS on 1-symbol PRS (R1-2302201; contact: ZTE)	RAN1
R2-2302889	CR to add SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz]	Ericsson
R2-2302894	CR to add SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz]	Ericsson
R2-2303498	Correction on 1-symbol PRS in 38.331	ZTE Corporation
R2-2303499	Correction on 1-symbol PRS in 37.355	ZTE Corporation
R2-2303500	[Draft] Reply LS on 1-symbol PRS	ZTE Corporation
R2-2304510	Reply LS on 1-symbol PRS	RAN2

7.24.2: TEI proposals by RAN2

TDoc	Title	Source
R2-2302495	Discusssion on impact of MBS Broadcast CFR for Redcap UE	NEC
R2-2302648	Discussion on emergency service for SL Relay	OPPO
R2-2302775	Signalling overhead reduction of DC location reporting signalling [DCLoc-Overhead]	Nokia, Nokia Shanghai Bell
R2-2303033	Updated proposal on Yaw and APC extensions	Swift Navigation
R2-2303123	Discussion on how to support posSIB(s) forwarding	Xiaomi
R2-2303163	GNSS LOS/NLOS assistance information-Follow up	Vodafone, Spirent, Ericsson, Telecom Italia
R2-2303196	GNSS LOS/NLOS assistance information	Vodafone, Spirent, Ericsson, Telecom Italia
R2-2303200	GNSS LOS/NLOS posSIB broadcast assistance information	Vodafone, Spirent, Ericsson, Telecom Italia
R2-2303206	GNSS LOS/NLOS posSIB broadcast assistance information	Vodafone, Spirent, Ericsson, Telecom Italia
R2-2303424	RRC segment transmission continuity	Apple
R2-2303492	Support of releasing cross-carrier scheduling configuration	Huawei, HiSilicon, Telecom Italia, China Unicom
R2-2303515	Discussion on the issue of unpredictable measurement sequence for inter-frequency measurement reporting	CMCC
R2-2303559	Positioning of remote UEs	MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo
R2-2303698	Support of Local Cartesian Coordinates in LPP	Qualcomm Incorporated
R2-2303702	Relay based Positioning for emergency calls and posSIB forwarding	Ericsson
R2-2303718	SDT Enhancements for Configured grants [SDT-Enh-CG]	Ericsson, Intel Corporation, ZTE Corporation
R2-2303746	U2N Relay UE operation Threshold Conditions: Impact of UE Mobility	Philips International B.V., FirstNet, ASUSTek, NEC, MediaTek, Lenovo
R2-2303972	Discussion on the seperated CFR for Redcap UE	Huawei, CBN, HiSilicon
R2-2304007	Introduction of multiple QoS in positioning for latency reduction	Samsung R&D Institute UK
R2-2304061	RedCap CFR for MBS Broadcast	Nokia, Nokia Shanghai Bell
R2-2304287	[AT121bis-e][412][POS] GNSS LOS/NLOS information	Vodafone (Rapporteur)
R2-2304288	[AT121bis-e][413][POS] Positioning for remote UEs (CATT)	CATT
R2-2304289	Summary of [AT121bis-e][414][POS] Local Cartesian Coordinates	Qualcomm Incorporated
R2-2304290	[AT121bis-e][415][Relay] Emergency service for relays (OPPO)	OPPO
R2-2304318	Positioning restrictions for UE-to-network remote UE [PosL2RemoteUE]	MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo
R2-2304319	Support positioning of L2 UE-to-network remote UEs [PosL2RemoteUE]	MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo
R2-2304320	Downlink positioning support and posSIB request for L2 UE-to-network remote UE [PosL2RemoteUE]	MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo
R2-2304454	Capabilities of L2 UE-to-network relay UEs for positioning [PosL2RemoteUE]	MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo

7.25.1: RAN4 led items

TDoc	Title	Source
R2-2302431	LS on measurements without gap (R4-2303306; contact: Intel, CATT)	RAN4
R2-2302434	LS on the UE SRS IL imbalance issue (R4-2303519; contact: Huawei)	RAN4
R2-2302438	LS on applicability of SIB19 for NR ATG (R4-2303684; contact: Qualcomm)	RAN4
R2-2302776	Discussion on RAN4 LS for Rel-18 measurement gaps	Nokia, Nokia Shanghai Bell
R2-2303045	Discussion on the support of Air to ground access	Qualcomm Incorporated
R2-2303046	[Draft] Reply LS on applicability of SIB19 for NR ATG	Qualcomm Incorporated
R2-2303071	Consideration on measurement without gap	CATT
R2-2303103	Discussion on NeedForGaps with interruption	Huawei, HiSilicon
R2-2303294	Discussion on R18 no gap with interruption	ZTE Corporation, Sanechips
R2-2303400	Discussion on Rel-18 gap enhancement	Apple
R2-2303612	Introduction of measurements without gap with interruption	MediaTek Inc.
R2-2303613	Introduction of measurements without gap with interruption	MediaTek Inc.
R2-2303614	Introduction of measurements without gap with interruption	MediaTek Inc.
R2-2303615	Introduction of measurements without gap with interruption	MediaTek Inc.
R2-2303840	RRM measurement on NCD-SSB for non-RedCap UE	vivo, Guangdong Genius
R2-2303841	Correction on 38.300 for BWP Wor	vivo
R2-2303842	Correction on 38.331for BWP Wor	vivo
R2-2304088	Discussion on applicability of SIB19 for NR ATG	CMCC
R2-2304141	Support for BWP operation without restriction	ZTE Corporation, Sanechips
R2-2304142	Support for BWP operation without restriction	ZTE Corporation, Sanechips
R2-2304199	Report of [AT121bis-e][023][MGE] Measurements without gap with interruption	MediaTek
R2-2304432	Introduction of measurements without gap with interruption	MediaTek Inc.
R2-2304433	Introduction of measurements without gap with interruption	MediaTek Inc.
R2-2304434	Introduction of measurements without gap with interruption	MediaTek Inc.
R2-2304435	Introduction of measurements without gap with interruption	MediaTek Inc.
R2-2304552	[Draft] Reply LS on applicability of SIB19 for NR ATG	Qualcomm Inc.
R2-2304565	Reply LS on applicability of SIB19 for NR ATG	RAN2

7.25.2: RAN1 led items

TDoc	Title	Source
R2-2302433	LS on Rel-18 Multi-carrier enhancement for NR (R4-2303507; contact: China Telecom)	RAN4
R2-2302578	Discussion on R18 UL Tx Switching	OPPO
R2-2302714	Discussion on Rel-18 UL Tx Switching	CATT
R2-2302730	Summary of [Post121][045][MCE] UL TX Switching (Docomo)	NTT DOCOMO INC.
R2-2303063	Current status of issues on Rel-18 UL Tx switching	NTT DOCOMO INC.
R2-2303293	Discussion on Rel-18 UL Tx switching capability	ZTE Corporation, Sanechips
R2-2303399	UL Tx switching scenarios and 1T-1T band pairs	Apple
R2-2303484	Introduction of Rel-18 UL Tx switching enhancements	Huawei, HiSilicon, NTT DOCOMO INC.
R2-2303485	Introduction of Rel-18 UL Tx switching enhancements	Huawei, HiSilicon, NTT DOCOMO INC.
R2-2303664	On RAN2 aspects for UL TX switching Rel-18	Ericsson
R2-2303825	discussion on UE capability and RRC configuration for UL tx switching	vivo
R2-2304472	LS on RRC configuration of Tx state in Rel-18 UL Tx switching	RAN2
R2-2304473	Summary of [AT121bis-e][021][MCE] UL TX Switching (NTT Docomo)	NTT DOCOMO, INC.
R2-2304530	LS on RRC configuration of Tx state in Rel-18 UL Tx switching	RAN2
R2-2304567	LS on report of switching periods in Rel-18 UL Tx switching	RAN2

7.25.3: Other

TDoc	Title	Source
R2-2302419	Reply LS on RAN impact for NPN enhancement in Rel-18 (R3-230813; contact: Qualcomm)	RAN3
R2-2302420	Reply LS on Support of network slices which have area of service not matching deployed tracking areas (R3-230899; contact: Nokia)	RAN3
R2-2302421	Reply LS on Partially allowed/rejected NSSAI (R3-230923; Contact: Ericsson)	RAN3
R2-2302447	Reply LS on Progress and open issues for NPN enhancements in Rel-18 (S2-2303689; contact: Qualcomm)	SA2
R2-2302462	LS on 3GPP work on Energy Efficiency (S5-232903; contact: Huawei)	SA5
R2-2302913	RAN2 impact on Rel-18 NPN enhancement	Intel Corporation
R2-2302999	RAN2 Impact on Further Enhancement NPN	CATT
R2-2303104	Discussion on RAN impact for NPN enhancement in Rel-18	Huawei, HiSilicon
R2-2303295	RAN2 impacts on R18 eNPN	ZTE Corporation, Sanechips
R2-2303807	General considerations on potential RAN2 works for NPN enhancement in Rel-18	Samsung Electronics Austria
R2-2303812	(draft CR to TS 38.300) On introduction of R18 eNPN	China Telecom,ZTE Corporation, Sanechips, CATT
R2-2303813	Draft CR to TS 38.304 on introduction of R18 eNPN	China Telecom, ZTE Corporation, Sanechips, CATT, Huawei, HiSilicon
R2-2303905	Discussion on further enhancement of private network support for NG-RAN	vivo
R2-2304119	Discussion and text proposal for NPN Rel-18	Ericsson
R2-2304143	Discussion on further enhancement of NPN in R18	China Telecom
R2-2304184	SI work plan for Study on self-evaluation towards the IMT-2020 submission of the 3GPP Satellite Radio Interface Technology	Ericsson
R2-2304487	Reply LS on 3GPP work on Energy Efficiency (C1-232650; contact: Huawei)	CT1
R2-2304490	LS on NAS-AS interaction in terms of NS-AoS (C1-232944; contact: Nokia)	CT1
R2-2304502	Reply LS on Support of network slices which have area of service not matching deployed tracking areas (S2-2306045; contact: Ericsson)	SA2
R2-2304503	Reply LS on partially allowed/rejected S-NSSAI (S2-2306254; contact: Nokia)	SA2

8.1: Session on NR NTN and IoT NTN

TDoc	Title	Source
R2-2304201	Report from Break-Out Session on NR NTN and IoT NTN	Vice Chairman (ZTE)

8.2: Session on LTE legacy, XR, QoE and Multi-SIM

TDoc	Title	Source
R2-2304202	Report from session on LTE legacy, XR, QoE and Multi-SIM	Vice Chairman (Nokia)

8.3: Session on UP, Small data, URLLC/IIoT, RACH indication, NWES and UAV

TDoc	Title	Source
R2-2304203	Report from UP, Small data, URLLC/IIoT, RACH indication, NWES and UAV	Session chair (InterDigital)

8.4: Session on positioning and sidelink relay

TDoc	Title	Source
R2-2304204	Report from session on positioning and sidelink relay	Session chair (MediaTek)

8.5: Session on LTE V2X and NR SL

TDoc	Title	Source
R2-2304205	Report from session on LTE V2X and NR SL	Session chair (OPPO)

8.6: Session on SON/MDT

TDoc	Title	Source
R2-2304206	Report from SON/MDT session	Session chair (CMCC)

8.7: Session on MBS

TDoc	Title	Source
R2-2304207	Report from MBS breakout session	Session chair (Huawei)

8.8: Session on IDC

TDoc	Title	Source
R2-2304208	Report from IDC breakout session	Session chair (Intel)

8.9: Session on NC Repeater

TDoc	Title	Source
R2-2304209	Report from NC Repeater breakout session	Session chair (Apple)

8.10: Session on eRedCap

TDoc	Title	Source
R2-2304210	Report from eRedCap breakout session	Session chair (Ericsson)

8.11: Session on Further NR coverage enhancements

TDoc	Title	Source
R2-2304211	Report from Further NR coverage enhancements session	Session chair (ZTE)

8.12: Session on NR MIMO evolution

TDoc	Title	Source
R2-2304212	Report from NR MIMO evolution session	Session chair (CATT)