RAN2#119bis-e

2.1: Approval of the agenda

TDoc	Title	Source
R2-2209300	Agenda for RAN2#119bis-e	Chairman

2.2: Approval of the report of the previous meeting

TDoc	Title	Source
R2-2209301	RAN2#119-e Meeting Report	MCC

3: Incoming liaisons

TDoc	Title	Source
R2-2210786	LS on the application of SCHC protocol on NB IOT (contact: Cisco)	IETF LPWAN WG

5: NR Rel-15 and Rel-16

TDoc	Title	Source
R2-2209319	Reply LS on eMIMO features defined in different granularity with prerequisite (R1-2208250; contact: Huawei)	RAN1
R2-2209320	Reply LS on the CSI periodic reporting for Dormant SCell state (R1-2208258; contact: Samsung)	RAN1
R2-2209335	LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier (R4-2214421; contact: vivo)	RAN4

6.0.1: RRC

TDoc	Title	Source
R2-2209466	Correction to explicit Indication of SI Scheduling window position [SI-SCHEDULING]	Huawei, HiSilicon
R2-2209925	Issues on Small Data Transmission under TN & NTN Mobility	FGI
R2-2209926	Corrections for Small Data Transmission under TN & NTN Mobility	FGI
R2-2210238	Correction to T331 handling	Nokia, Nokia Shanghai Bell
R2-2210639	Setup Modify Release structure for Rel-18 IEs	Ericsson
R2-2210997	Correction to explicit Indication of SI Scheduling window position [SI-SCHEDULING]	Huawei, HiSilicon
R2-2211051	Report for [AT119bis-e][003][NR17] RRC corrections	Huawei, HiSilicon

6.0.2: UE capabilities

TDoc	Title	Source
R2-2209492	Discussion on intra-ENDC band relevant UE capability	OPPO
R2-2210538	Discussion on intra-band EN-DC combination	Huawei, HiSilicon
R2-2210565	Corrections to NTN capabilities	LG Electronics
R2-2210585	Clarification on the MBS feature 33-1-2 and 33-3-2	Xiaomi
R2-2210638	Further guidelines on UE capability definitions	Ericsson
R2-2210660	Clairificaiton on the ue-PowerClassPerBandPerBC-r17	ZTE Corporation, Sanechips
R2-2210661	CR on the ue-PowerClassPerBandPerBC-r17	ZTE Corporation, Sanechips
R2-2210765	Discussion on intra-band EN-DC combinations	Google Inc., Comcast, CableLabs
R2-2211001	Report of [AT119b-e][004][NR17] UE caps Main (Intel)	Intel Corporation
R2-2211008	Clarification on the MBS feature 33-1-2 and 33-3-2	Xiaomi
R2-2211023	LS on the ue-PowerClassPerBandPerBC-r17(R4 16-8)	RAN2

6.0.4: Other

TDoc	Title	Source
R2-2209313	LS on BWP operation without restriction (R1-2208168; contact: Qualcomm)	RAN1
R2-2209333	LS on Feature Group 6-1a “bwp-WithoutRestriction” (R4-2214355; contact: Qualcomm)	RAN4
R2-2209415	Discussion on MBS Frequency Prioritization and Slice-specific Reselection	vivo
R2-2209477	Discussion on EHC for DAPS	CATT
R2-2209548	Corrections to TS 38.304 for MBS	CATT, CBN
R2-2209829	Configuration EHC for DAPS	CATT
R2-2209924	Configuration EHC for DAPS	CATT
R2-2210126	Reselection prioritization in release-17	Nokia, Nokia Shanghai Bell
R2-2210459	Coexistence between the highest priority and slice specific cell reselection priority	Kyocera Corporation
R2-2211025	Report of [AT119bis-e][005][NR17] Cell Reselection Frequency Prioritization	Kyocera

6.1.1: Organizational and Stage-2

TDoc	Title	Source
R2-2209302	Reply LS on AS-NAS layer interactions for MBS (C1-225249; contact: Huawei)	CT1
R2-2209352	Response LS on further outstanding issues in TS 23.247 (S2-2207389; contact: Huawei)	SA2
R2-2209353	LS on AS-NAS layer interactions for MBS (S2-2207409; contact: Huawei)	SA2
R2-2209360	LS on response to LS on parameters preconfigured in the UE to receive MBS service (S2-2207888; contact: Huawei)	SA2
R2-2209653	Rapporteur corrections on RRC	Huawei, HiSilicon
R2-2209866	Corrections on MBS	Nokia, Nokia Shanghai Bell
R2-2210051	Miscellaneous corrections for MBS 38.323	Xiaomi
R2-2211024	Corrections on MBS	Nokia, Nokia Shanghai Bell
R2-2211026	Miscellaneous corrections for MBS 38.323	Xiaomi

6.1.2: RRC corrections

TDoc	Title	Source
R2-2209399	RRC Corrections on MBS	vivo
R2-2209547	Miscellaneous Corrections to TS 38.331 for MBS	CATT, CBN
R2-2209654	Discussion on LCH re-association for MRB	Huawei, HiSilicon
R2-2209657	Discussion on PDCP window handling during PDCP suspend and AM PDCP re-establishment	Huawei, HiSilicon
R2-2209748	CR to TS 38.331 on MRB configuration	ZTE, Sanechips
R2-2209908	RRC corrections for MBS	Intel Corporation
R2-2210050	Broadcast MRB retention upon T300 expiry	Samsung
R2-2210130	Various small corrections to 38.331	Nokia, Nokia Shanghai Bell
R2-2210576	38.331 CR Correction on the ASN.1 violation or encoding error handling for MCCH message	Beijing Xiaomi Software Tech
R2-2210682	CR to TS 38.331 on MRB configuration	ZTE, Sanechips
R2-2210712	MBS service area and MCCH acquisition	Ericsson
R2-2210713	A closer look at the MBS broadcast neighbours	Ericsson
R2-2210717	Correction to full configuration for MBS	Google Inc.
R2-2210870	Report of [AT119bis-e][601][MBS-R17] RRC corrections	Huawei, HiSilicon
R2-2210871	Rapporteur corrections on RRC	Huawei, HiSilicon
R2-2210883	Rapporteur corrections on RRC	Huawei, HiSilicon

6.1.3: Other CP corrections

TDoc	Title	Source
R2-2209655	Correction on UE capability for MBS	Huawei, CBN, HiSilicon
R2-2209909	Remaining MBS UE capability open issues	Intel Corporation
R2-2210029	Correction on MBS capabilities	MediaTek inc.
R2-2210069	Correction to PEI monitoring for group notification	Samsung
R2-2210131	Various small corrections to 38.304	Nokia, Nokia Shanghai Bell
R2-2210549	CR to TS 38.304 on NR MBS	ZTE, Sanechips
R2-2210683	CR to TS 38.304 on NR MBS	ZTE, Sanechips
R2-2210711	When to monitor the MCCH on the MBS frequency	Ericsson, Nokia, Nokia Shanghai Bell
R2-2210714	DCI indicated repetitions for MBS broadcast	Ericsson
R2-2210872	Summary of offline discussion: [AT119bis-e][602][MBS-R17] Other CP corrections (CATT)	CATT
R2-2210876	Draft 38.306 CR for MBS UE capability corrections	MediaTek Inc.
R2-2210877	Draft 38.331 CR for MBS UE capability corrections	MediaTek Inc.
R2-2210881	MBS corrections for 38.304	CATT

6.1.4: UP corrections

TDoc	Title	Source
R2-2209416	UP Corrections on MBS	vivo
R2-2209417	Handling of PDCP State Variables	vivo
R2-2209438	Considerations on HARQ buffer flushing and CSI masking	Samsung
R2-2209549	Corrections to TS 38.321 for MBS	CATT
R2-2209550	Discussion on RX_DELIV for AM MRB	CATT
R2-2209551	Remaining PDCP issues for MBS	Nokia, Nokia Shanghai Bell
R2-2209656	Clarifications on DRX and HARQ buffer handling	Huawei, CBN, HiSilicon
R2-2209746	PDCP initialisation for multicast MRB	ZTE, Sanechips
R2-2209747	CR to TS 38.323 on PDCP initialisation	ZTE, Sanechips
R2-2209875	PDCP initialization for multicast MRB	MediaTek inc.
R2-2209910	UP corrections for MBS	Intel Corporation
R2-2209948	Correction on HARQ buffer flushing of MBS broadcast	Lenovo
R2-2209949	Discussion on PDCP initial values handling	Lenovo
R2-2210052	Clarification on the PDCP state variables	Xiaomi
R2-2210519	Removal of concept of UM MRB and AM MRB	LG Electronics Inc.
R2-2210575	38.321 CR Correction on the HARQ buffer flush for the MBS broadcast	Beijing Xiaomi Software Tech
R2-2210592	Clarification on reception of DRX Command MAC CE	LG Electronics Inc.
R2-2210594	Discussion on flushing HARQ buffers for MBS broadcast	LG Electronics Inc.
R2-2210609	PDCP Variable Handling for Multicast	Samsung
R2-2210681	CR to TS 38.323 on PDCP initialisation	ZTE, Sanechips
R2-2210684	Correction to DRX command reception	Google Inc.
R2-2210873	Report of Offline 603: UP Correction for Rel-17 MBS	Samsung
R2-2210874	Miscellaneous corrections for MBS 38.323	Xiaomi
R2-2210875	MBS corrections for 38.321	OPPO
R2-2211060	MBS corrections for 38.321	OPPO
R2-2211065	Report of [Post119bis-e][606][MBS-R17] MAC CR review (OPPO)	OPPO

6.2.1: Organizational and Stage-2 corrections

TDoc	Title	Source
R2-2210177	Report of [Post119-e][224][DCCA] Stage-2 description of CHO with MR-DC (ZTE)	ZTE Corporation, Sanechips
R2-2210524	Corrections for CHO with MR-DC	ZTE Corporation (Rapporteur), Sanechips; Ericsson; CATT
R2-2210721	Corrections for further MR-DC enhancements	Huawei, HiSilicon
R2-2210811	Report of [AT119bis-e][202][DCCA] Stage-3 Corrections to DCCA (Huawei)	Huawei
R2-2210826	Corrections for DCCA enhancement	ZTE Corporation (Rapporteur), Sanechips; Ericsson; CATT
R2-2210828	Corrections for further MR-DC enhancements	Huawei, HiSilicon

6.2.2: SCG deactivation and Temporary RS for SCell activation Corrections

TDoc	Title	Source
R2-2210127	BWP handling for deactivated SCG	Nokia, Nokia Shanghai Bell
R2-2210455	Correction on the BWP for PSCell in deactivation SCG and the timing requirement for SCG activation	CATT
R2-2210456	Correction on ASN.1 for sCellState and scg-State	CATT
R2-2210469	Remaining issues for BWP operation in deactivated SCG	Sharp
R2-2210672	Correction on BWP handling for deactivated SCG	Ericsson
R2-2210674	Handling of BWP during SCG deactivation	Ericsson
R2-2210818	Report of [AT119bis-e][205][DCCA] BWP handling for deactivated SCG (Ericsson)	Ericsson
R2-2210819	Correction on BWP handling for deactivated SCG	Ericsson

6.2.3: Conditional PSCell change addition Corrections

TDoc	Title	Source
R2-2209478	Correction on CHO with MR-DC in TS 37.340	vivo
R2-2210178	Clarification on conditionalReconfiguration	ZTE Corporation, Sanechips
R2-2210305	Correction on evaluations during CPAC execution	Ericsson
R2-2210343	On releasing conditional configurations when SCG is changed	Nokia, Nokia Shanghai Bell
R2-2210344	Draft NR RRC CR on releasing conditional configurations when SCG is changed	Nokia, Nokia Shanghai Bell
R2-2210457	Discussion on measurement for conditional reconfiguration	CATT
R2-2210718	UE measurement capability handling for conditional measurements without a corresponding conditional reconfiguration	Huawei, HiSilicon
R2-2210719	UE measurement requirements for conditional events in TS 38.331	Huawei, HiSilicon
R2-2210720	UE measurement requirements for conditional events in TS 36.331	Huawei, HiSilicon
R2-2210775	Discussion on measurement for conditional reconfiguration	CATT
R2-2210810	Report of [AT119bis-e][201][DCCA] Stage-2 Corrections to DCCA (ZTE)	ZTE
R2-2210820	Report of [AT119bis-e][209][DCCA] Corrections to measurements with CPAC (Huawei)	Huawei

6.3: Multi SIM

TDoc	Title	Source
R2-2209348	Reply LS on NAS busy indication in RRC_INACTIVE (S2-2207029; contact: Samsung)	SA2
R2-2209927	Conflict of UE Preferred RRC State Report	FGI
R2-2209928	Corrections for the Conflict of UE Preferred RRC state Report	FGI

6.5: NR IIoT URLLC

TDoc	Title	Source
R2-2211037	LS on Time Synchronization Status notification towards UE(s) (S2-2209876; contact: Nokia)	SA2

6.6: Small Data enhancements

TDoc	Title	Source
R2-2209312	Reply LS on common search space for small data transmission (R1-2208107; contact: ZTE)	RAN1
R2-2210676	Correction to CG-SDT	Google Inc.

6.7.1: Organizational

TDoc	Title	Source
R2-2209306	LS on setting RRC establishment cause value when relay UE has its own service (C1-225453; contact: vivo)	CT1
R2-2209812	[Draft] LS reply on setting RRC establishment casue value when relay UE has its own service	vivo
R2-2209813	Discussion on LS from R2-2209206(C1-225453)	vivo
R2-2209814	Correction to the L2 U2N Relay UE’s cause value setting behaviour	vivo
R2-2210011	RLC correction for SL relay	Samsung
R2-2210012	PDCP correction for SL relay	Samsung
R2-2210324	Misc correction in 38.304 for SL relay	Ericsson (Rapporteur)
R2-2210493	Misc RRC CR for SL relay	Huawei, HiSilicon
R2-2210900	Summary of [AT119bis-e][411][Relay] Relay cause value	vivo (Rapporteur)
R2-2210901	Report of\t[AT119bis-e][414][Relay] Rel-17 relay RRC CR (Huawei)	Huawei, HiSilicon
R2-2210902	Miscellaneous RRC CR for SL relay	Huawei, HiSilicon
R2-2210915	RLC correction for SL relay	Samsung
R2-2210916	PDCP correction for SL relay	Samsung
R2-2210970	Misc correction in 38.304 for SL relay	Ericsson (Rapporteur)
R2-2210978	[Summary of [AT119bis-e][411][Relay] Relay cause value - extended]	vivo
R2-2211031	Reply LS on Cast Type for Discovery message (S2-2209277; contact: Qualcomm)	SA2

6.7.2.1: Stage 2 corrections

TDoc	Title	Source
R2-2209815	Correction on Sidelink based U2N Relay	vivo
R2-2210110	Corrections on SL relay	ZTE, Sanechips

6.7.2.2: Control plane corrections

TDoc	Title	Source
R2-2209377	Correction for U2N Relay	OPPO
R2-2209378	Discussion on left issues for CP	OPPO
R2-2209500	Miscellaneous corrections for NR sidelink Relay in TS 38.304	OPPO
R2-2209545	Correction on relay UE RRC connection establishment failure	SHARP Corporation
R2-2209775	Discussion on remaining issues on CP procedure for SL Relay	Apple
R2-2209776	Correction on PC5 Relay RLC Channel configuration for L2 Relay UE and L2 Remote UE	Apple
R2-2209816	Discussion on NR SL communication transmission using exception pool during D2I path switch	vivo
R2-2209817	Corrections to MAC and RLC handling for L2 U2N Relay	vivo
R2-2209818	Correction to SL-RLC1	vivo
R2-2209847	Clarification on SL DRX operation for U2N Remote UE	ASUSTeK
R2-2209848	Correction on RRC connection re-establishment procedure	ASUSTeK
R2-2209860	Alignment between remote UE paging DRX and relay UE Uu DRX	Ericsson
R2-2209861	Corrections to 38321 on alignment between remote UE paging DRX and relay UE Uu DRX	Ericsson
R2-2209879	Correction on handover notification forwarding	Xiaomi
R2-2209880	Miscelleneous correction on 38.331	Xiaomi
R2-2209885	Correction on remote UE's resource allocation	Xiaomi
R2-2209892	Calarification on emergency service support in Rel-17 U2N relay	CATT
R2-2209902	Discussion on SL synchronization for SL relay	ZTE, Sanechips
R2-2209903	Correction on control plane for L2 U2N relay	ZTE, Sanechips
R2-2210170	Correction for receiving notification message during path switching	Lenovo Information Technology
R2-2210325	Clarification on UAC procedure for U2N Relay UE	Ericsson
R2-2210326	Clarification on setting the transaction identifier for sidelink	Ericsson
R2-2210378	Correction on SRAP handling for NR sidelink relay	Xiaomi
R2-2210432	Correction on derivation of serving Relay UE measurement results	Sharp
R2-2210433	Correction on full configuration for remote UE	Sharp
R2-2210434	Correction on RRC connection suspension of remote UE	Sharp
R2-2210494	Remaining CP correction for sidelink relay	Huawei, HiSilicon
R2-2210495	Discussion on support of QoE in L2 U2N relay	Huawei, HiSilicon
R2-2210496	RRC CR for clarification on no support of QoE for L2 U2N Remote UE	Huawei, HiSilicon
R2-2210625	U2N relay related clarifications	Nokia, Nokia Shanghai Bell
R2-2210890	[Pre119bis-e][401] Summary of AI 6.7.2.2 on relay control plane (Huawei)	Huawei, HiSilicon

6.7.2.3: User plane corrections

TDoc	Title	Source
R2-2209893	Correction on SRAP for L2 U2N Relay	CATT
R2-2209904	Correction on SRAP for L2 U2N relay	ZTE, Sanechips
R2-2210043	Miscellaneous corrections to 38.351	Samsung R&D Institute UK
R2-2210673	DraftCR 38.351 Miscellaneous SRAP changes	Nokia, Nokia Shanghai Bell
R2-2210770	Summary of AI 6.7.2.3	OPPO
R2-2210971	Report of [420]	OPPO
R2-2210972	Corrections for L2 U2N Relay	OPPO, ZTE, Samsung, Nokia

6.7.2.4: Discovery and re- selection

TDoc	Title	Source
R2-2209501	Miscellaneous corrections for NR sidelink Relay in TS 38.321	OPPO
R2-2209894	Correction on relay (re-)selection for remote UE	CATT
R2-2209971	Correction on Sidelink discovery transmission	CATT
R2-2210111	Support of SL CG for discovery message	Huawei, HiSilicon, Nokia, Kyocera
R2-2210169	Correction for relay selection for entering IDLE or INACTIVE	Lenovo Information Technology
R2-2210633	Discussion on Resource Allocation for Sidelink Discovery	CATT
R2-2210777	Summary of AI 6.7.2.4 on discovery and reselection	CATT
R2-2210908	[AT119bis-e][422][Relay] Remaining proposals on discovery and (re)selection (CATT)	CATT
R2-2210999	Summary report of [AT119bis-e][421][Relay] Rel-17 relay MAC CR (Apple)	Apple

6.8: RAN slicing

TDoc	Title	Source
R2-2209358	LS Out on LS on slice list and priority information for cell reselection and Random Access (S2-2207698; contact: ZTE)	SA2
R2-2210206	Discussion on LS on RAN dependency of FS_eNS_Ph3	Lenovo
R2-2210229	Draft reply LS to SA2 on FS_eNS_Ph3	Lenovo
R2-2210526	Clarification on the slice information for cell reselection	OPPO
R2-2210527	Clarification on the slice information for random access	OPPO
R2-2210749	Discussion on SA2 LS on slice list and priority information for cell reselection and Random Access	ZTE Corporation, Sanechips
R2-2210750	Correction on handling of the NSAG information in cell reselection	ZTE Corporation, Sanechips
R2-2210751	[Draft] Reply LS on slice list and priority information for cell reselection and Random Access	ZTE corporation, Sanechips
R2-2210783	Discussion on SA2 LS on slice list and priority information for cell reselection and Random Access	ZTE Corporation, Sanechips

6.9: UE Power Saving

TDoc	Title	Source
R2-2209316	LS on PDCCH skipping (R1-2208210; contact: MediaTek)	RAN1
R2-2209338	Reply LS to RAN2 on RLM/BFD relaxation (R4-2214475; contact: vivo)	RAN4
R2-2210554	Report of [Post119-e][043][ePowSav] paging early indication with paging subgrouping during emergency call	MediaTek Inc.

6.10.1.1: LS in

TDoc	Title	Source
R2-2209337	LS to RAN2 on Network indication for applying enhanced cell reselection requirements (R4-2214472; contact: Huawei)	RAN4
R2-2209354	Reply LS on the deactivation of access stratum due to discontinuous coverage (S2-2207420; contact: Qualcomm)	SA2
R2-2210044	On LS Network indication for applying enhanced cell reselection requirements	Ericsson
R2-2210347	NR RRC CR: Introduction of enhanced and relaxed cell reselection for NTN	Nokia, Nokia Shanghai Bell
R2-2210348	NR IDLE-mode CR: Introduction of enhanced and relaxed cell reselection for NTN	Nokia, Nokia Shanghai Bell
R2-2210408	Discussion on enhanced cell reselection requirements for NTN	Huawei, HiSilicon
R2-2210409	CR on enhanced cell reselection requirements for NTN	Huawei, HiSilicon
R2-2210850	Report of [Offline-109][NR NTN] cell reselection requirements (Huawei)	Huawei, HiSilicon
R2-2210866	Reply LS on enhanced cell reselection requirements	RAN2
R2-2211035	LS on Satellite coverage data transfer to a UE using UP versus CP (S2-2209684; contact: Qualcomm)	SA2
R2-2211045	CR on enhanced cell reselection requirements for NTN	Huawei, HiSilicon

6.10.1.2: Rapporteur inputs

TDoc	Title	Source
R2-2210868	MAC corrections for Rel-17 NR NTN	InterDigital
R2-2210869	Idle mode corrections for Rel-17 NR NTN	ZTE Corporation
R2-2211018	RRC corrections for Rel-17 NR NTN	Ericsson

6.10.2: Stage 2 corrections

TDoc	Title	Source
R2-2209539	Correction on neighbour cells’ satellite ephemeris information (38.300)	MediaTek Inc.
R2-2209658	Correction on user consent for UE coarse location request	Huawei, HiSilicon
R2-2210086	NTN stage-2 correction	OPPO
R2-2210462	Corrections to TS 38.300 for Rel-17 NR NTN	Samsung Research America
R2-2210567	Corrections to TS 38.300 for Rel-17 NR NTN	Samsung Research America
R2-2210634	Corrections to the UE-Based SMTC Adjustment in NTN	Google Inc.
R2-2210742	Corrections on CHO evaluation for NTN	CATT
R2-2210759	R17 NR NTN Stage 2 corrections	Ericsson
R2-2210851	Summary of [AT119bis-e][110][NR NTN] Stage-2 CR (Thales)	Thales
R2-2210852	R17 NR NTN Stage 2 corrections	Thales
R2-2211046	R17 NR NTN Stage 2 corrections	Thales
R2-2211049	[Post119bis-e][110] Stage-2 corrections	Thales

6.10.3: UP corrections

TDoc	Title	Source
R2-2209503	On corrections on random access procedure in NR NTN	vivo
R2-2209849	Discussion on reported value for event-triggered TA report	ASUSTeK
R2-2210087	Correction to TA report triggered SR and DRX	OPPO
R2-2210463	Corrections to TS 38.321 for Rel-17 NR NTN	Samsung Research America
R2-2210568	Corrections to TS 38.321 for Rel-17 NR NTN	Samsung Research America
R2-2210641	Correction on SR cancellation and Random Access procedure stop for NTN	Nokia, Nokia Shanghai Bell
R2-2210708	Correction on SR triggered by TAR	ZTE Corporation, Sanechips
R2-2210760	R17 NR NTN epoch time and validity	Ericsson
R2-2210768	Corrections to TS 38.321 for Rel-17 NR NTN	Samsung Research America
R2-2210853	Report of [AT119bis-e][111][NR NTN] UP corrections	InterDigital

6.10.4.1: Idle/inactive mode corrections

TDoc	Title	Source
R2-2209504	Correction on the list of "PLMNs not allowed to operate at the present UE location" in TS 38.304	vivo
R2-2210034	Discussion on not being able to acquire SIB 19 for NR NTN	Xiaomi, CAICT
R2-2210035	Correction on the action upon not being able to acquire SIB19 for NR NTN	Xiaomi, CAICT
R2-2210464	Corrections to TS 38.304 for Rel-17 NR NTN	Samsung Research America
R2-2210569	Corrections to TS 38.304 for Rel-17 NR NTN	Samsung Research America
R2-2210584	Correction on cell status for NTN	Google Inc.
R2-2210640	Corrections to the Reselection Priorities Handling for NTN	Google Inc.
R2-2210854	Report of [AT119bis-e][112][NR NTN] idle mode corrections (ZTE)	ZTE corporation,Sanechips

6.10.4.2: RRC corrections

TDoc	Title	Source
R2-2209505	Correction on UE behavior on SMTC in TS 38.331	vivo
R2-2209506	Correction on UE coarse location reporting in TS 38.331	vivo
R2-2209507	Correction on UE behavior on T430 in TS 38.331	vivo
R2-2209526	On neighbour cell SI	Ericsson
R2-2209527	Correction for Release 17 NTN	Ericsson
R2-2209528	On timer T430 for Rel-17 NR NTN	Ericsson
R2-2209537	Correction on the coincidence of ECI and ECEF	MediaTek Inc.
R2-2209538	Correction on neighbour cells’ satellite ephemeris information (38.331)	MediaTek Inc.
R2-2209540	IOT bit for inter satellite measurement (38.331)	MediaTek Inc.
R2-2209799	Clarification on validity of the UL sync info	Apple
R2-2209800	Clarification on the concurrent measurement gap configuration	Apple
R2-2209803	Clarification on the necessity of SIB19 in NTN cell	Apple
R2-2209850	Discussion on configuration of satellite information for handover	ASUSTeK
R2-2209851	Discussion on T430 handling upon going to RRC_IDLE	ASUSTeK
R2-2209852	Clarification on validity timer for serving cell	ASUSTeK
R2-2209981	Discussion on the ephemeris information in CHO procedure	Spreadtrum Communications
R2-2210091	RRC correction on valid timer and SIB19 acquisition	OPPO
R2-2210092	Discussion on validity issue of satellite assistance information	OPPO
R2-2210093	DRAFT LS on the support of backward propagation in NTN	OPPO
R2-2210197	Draft 331 CR – Addition of missing descriptions of Event D1 and CondEvent T1	Interdigital, Inc.
R2-2210345	NR RRC CR on epochTime and validity timer	Nokia, Nokia Shanghai Bell
R2-2210346	NR RRC CR on neighbour cell ephemeris signalling	Nokia, Nokia Shanghai Bell
R2-2210410	CR on validity duration	Huawei, HiSilicon
R2-2210411	Discussion on epoch time	Huawei, HiSilicon
R2-2210412	Remaining issues on neighbour cell ephemeris	Huawei, HiSilicon
R2-2210465	Corrections to TS 38.331 for Rel-17 NR NTN	Samsung Research America
R2-2210466	Discussion on Epoch Time	Samsung Research America
R2-2210484	Clarification on the necessity of SIB19 in NTN cell	Apple
R2-2210570	Corrections to TS 38.331 for Rel-17 NR NTN	Samsung Research America
R2-2210646	Corrections to the SMTC Field Description in System Information	Google Inc.
R2-2210663	Further consideration on NTN neighbour cell list in SIB19	ZTE Corporation, Sanechips
R2-2210664	Clarification on the NTN neighbour cell list in SIB19	ZTE Corporation, Sanechips
R2-2210729	NTN Configuration at Handover and CHO	Sequans Communications
R2-2210740	Corrections on validity of SIB19	CATT
R2-2210741	Corrections on related issues of epoch time	CATT
R2-2210743	Discussion on leftover issues	CATT
R2-2210855	Summary of [AT119bis-e][113][NR-NTN] epoch time and validity timer (Samsung)	Samsung
R2-2210856	Summary of [AT119bis-e][114][NR NTN] Validity of assistance information (OPPO)	OPPO
R2-2210857	[DRAFT] LS on validity of assistance information	OPPO
R2-2210858	[offline-115] RRC corrections (Ericsson)	Ericsson
R2-2211047	LS on validity of assistance information	RAN2
R2-2211048	LS on validity of assistance information	RAN2

6.10.5: UE capabilities corrections

TDoc	Title	Source
R2-2209541	IOT bit for inter satellite measurement (38.306)	MediaTek Inc.
R2-2209707	Missing UE capability for eventD1	Qualcomm Incorporated
R2-2209708	Missing UE capability for eventD1	Qualcomm Incorporated
R2-2209801	Capability of the UE coarse location report	Apple
R2-2209802	Clarification on the support of DCCA in NTN network	Apple
R2-2210859	[offline-116] [NR NTN] UE capabilities	MediaTek

6.11.1: Organizational

TDoc	Title	Source
R2-2209331	LS on SRS-PosRRC-InactiveConfig configuration signalling (R3-225268; contact: Intel)	RAN3
R2-2209332	LS on Tx TEG framework (R4-2210603; contact: CATT)	RAN4
R2-2209342	Reply LS on the UE/TRP TEG framework (R4-2214493; contact: CATT)	RAN4
R2-2209432	Discussion on the “Reply LS on the UE/TRP TEG framework” from RAN4 (R4-2214493)	CATT
R2-2209433	[DRAFT] Reply LS on applicability of timing error margin of Rx TEG	CATT
R2-2209437	Discussion on LS on SRS-PosRRC-InactiveConfig configuration signalling	CATT
R2-2209610	UE RRC state transition during the positioning session for RAN3 LS (R2-2209331)	Intel Corporation
R2-2209611	Draft Reply LS on SRS-PosRRC-InactiveConfig configuration signalling	Intel Corporation
R2-2210119	Discussion on the LS on SRS-PosRRC-InactiveConfig configuration signalling	Xiaomi
R2-2210312	Miscellaneous correction for Positioning	Ericsson
R2-2210895	Report of [AT119bis-e][408][POS] State change during positioning (Intel)	Intel Corporation
R2-2210896	Draft reply LS on SRS-PosRRC-InactiveConfig configuration signalling	Intel
R2-2210897	[AT119bis-e][409][POS] LS on TEG framework (CATT)	CATT
R2-2210898	[DRAFT] Reply LS on applicability of timing error margin of Rx TEG	CATT
R2-2210899	Miscellaneous correction for Positioning	Ericsson
R2-2210919	[AT119bis-e][410][POS] Rel-17 positioning RRC CR (Ericsson)	Ericsson
R2-2210976	Reply LS on SRS-PosRRC-InactiveConfig configuration signalling	RAN2
R2-2210977	Reply LS on applicability of timing error margin of Rx TEG	RAN2
R2-2210980	Miscellaneous correction for Positioning	Ericsson
R2-2210983	Miscellaneous correction for Positioning	Ericsson

6.11.2.1: Stage 2 corrections

TDoc	Title	Source
R2-2210313	Missing Functional Impacts for UE TxTEG association	Ericsson
R2-2210314	Missing Functional Impacts for RRC Inactive Positioning	Ericsson
R2-2210315	Addition of Signaling of SRS Port Index when SRS resource for MIMO is used	Ericsson
R2-2210605	Miscellaneous corrections to TS 38.305	vivo

6.11.2.2: RRC corrections

TDoc	Title	Source
R2-2209429	Correction to RRC spec for RRC_INACTIVE positioning	Huawei, HiSilicon
R2-2210480	Cancellation of UL MAC CE for MG activation/deactivation	Samsung

6.11.2.3: LPP corrections

TDoc	Title	Source
R2-2209430	Correction to UE capability for DL-AoD	Huawei, HiSilicon
R2-2209431	Correction to TEG margin reporting	Huawei, HiSilicon
R2-2209434	Corrections on the timing error margins	CATT
R2-2209435	Change Request of missing UE capabilities	CATT
R2-2209436	Corrections on the LPP capabilities	CATT
R2-2209683	NR-DL-AoD-SignalMeasurementInformation corrections	Nokia, Nokia Shanghai Bell
R2-2210199	Correction on the maximum number of SRS and TxTEG association	ZTE, Sanechips
R2-2210606	Discussion on the provision of AL for achievable TIR calculation	vivo
R2-2210784	Summary of AI 6.11.2.3: LPP corrections	Qualcomm Incorporated
R2-2210904	Various LPP Corrections	Qualcomm Incorporated (Rapporteur)
R2-2210905	Summary of [AT119bis-e][416][POS] LPP CR (Qualcomm)	Qualcomm Incorporated
R2-2210906	Summary of [Offline-417][POS] Calculation of TIR and provision of AL to UE	vivo
R2-2210975	Correction to UE capability for DL-AoD	Huawei, HiSilicon

6.11.2.4: MAC corrections

TDoc	Title	Source
R2-2209427	Correction to MAC spec for Positioning enhancement	Huawei, HiSilicon
R2-2210311	Positioning Measurement Gap Activation/Deactivation Request MAC CE based upon Scheduling Request Configuration	Ericsson
R2-2210607	Clarification on the PPW index	vivo
R2-2210891	[Offline-418][POS] Positioning MAC CR (Huawei)	Huawei, HiSilicon
R2-2210894	Correction to MAC spec for Positioning enhancement	Huawei, HiSilicon

6.11.2.5: UE capabilities

TDoc	Title	Source
R2-2209428	Correction on PRS processing window capability	Huawei, HiSilicon
R2-2210310	Correcting PRS capability information reported to gNB	Ericsson
R2-2210907	Correcting PRS capability information reported to gNB	Ericsson

6.12: Reduced Capability

TDoc	Title	Source
R2-2209340	Reply LS on configuring margin for 1 Rx RedCap Ues (R4-2214484; contact: Ericsson)	RAN4
R2-2209341	Reply LS on RRM relaxation for Redcap (R4-2214487; contact: vivo)	RAN4
R2-2211039	LS On long eDRX support for RRC_INACTIVE (S2-2209958; contact: Ericsson)	SA2

6.13: SON MDT

TDoc	Title	Source
R2-2209321	LS on M6 Delay Threshold (R3-224079; contact: CATT)	RAN3
R2-2209327	Reply LS on the user consent for trace reporting (R3-225250; contact: Nokia)	RAN3
R2-2209363	LS on Reply LS on beam measurement reports (S5-223524; contact: Ericsson)	SA5
R2-2209366	Reply LS on beam measurement reports (R3-225273; contact: Ericsson)	RAN3

6.14: NR QoE

TDoc	Title	Source
R2-2209361	Reply LS to SA5 on TS 28.404/TS 28.405 Clarification (S4-221121; contact: Qualcomm)	SA4
R2-2209362	Reply LS on questions on RAN visible QoE (S4-221129; contact: Huawei)	SA4

6.15.1: Organizational

TDoc	Title	Source
R2-2209310	Reply LS to RAN2 on RRC parameters for IUC Scheme 1 and default CBR configuration (R1-2208090; contact: Huawei)	RAN1
R2-2209311	Reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig (R1-2208097; contact: vivo)	RAN1
R2-2209349	Reply LS to RAN2 on Tx profile (S2-2207033; contact: vivo)	SA2
R2-2211029	Reply LS on Tx profile (C1-226055; contact: OPPO)	CT1

6.15.2: Control plane corrections

TDoc	Title	Source
R2-2209379	Correction for SL DRX	OPPO
R2-2209380	Discussion on left issues on control plane procedure	OPPO
R2-2209462	Discussion on the LS in R1-2208121 on open-loop power control (OLPC) parameters for NR sidelink	vivo
R2-2209463	Discussion on the LS in R2-2209311 for default resource selection scheme	vivo
R2-2209674	correction on RRC spec for SUI initiation and IUC parameter	ZTE Corporation, Sanechips
R2-2209676	correction on SUI message	ZTE Corporation, Sanechips
R2-2209677	Correction on Tx profile operation	ZTE Corporation, Sanechips
R2-2209739	Miscellaneous corrections on TS 38.331 for SL DRX	CATT
R2-2209740	Miscellaneous corrections on TS 38.331 for SL enhancement	CATT
R2-2209772	Correction on SL transmission by OOC UE for SL communication and SL discovery	Apple
R2-2209857	Discussion on RAN1 LS R1-2208090	Ericsson
R2-2209858	Corrections to 38331 on OLPC parameters	Ericsson
R2-2209878	Correction on 38.331	Xiaomi
R2-2210259	Correction on LCID Assignment for SL LCH	InterDigital, ASUSTek
R2-2210260	Correction on LCID Assignment for SL LCH	InterDigital, ASUSTek
R2-2210373	Rapporteur CR on TS 38.331 for SL enhancements	Huawei, HiSilicon
R2-2210542	Miscellaneous corrections on 38.331	vivo
R2-2210543	Miscellaneous corrections to SL DRX	vivo
R2-2210544	Discussion and TP on LS of TX profile	vivo
R2-2210550	Clarification of default CBR parameters	Samsung Research America
R2-2210555	Clarification of default CBR parameters	Samsung Research America
R2-2210779	Discussion on left issues on control plane procedure	OPPO
R2-2210930	Rapporteur CR on TS 38.331 for SL enhancements	Huawei, HiSilicon (Rapporteur)
R2-2210931	Summary of [AT119bis-e][501][V2X/SL] 38.331 corrections (Huawei)	Huawei, HiSilicon

6.15.3: User plane corrections

TDoc	Title	Source
R2-2209387	Discussion on left issues on user plane procedure	OPPO
R2-2209388	Miscellaneous corrections on TS 38.321 for SL enhancements	OPPO
R2-2209542	Correction to resource (re-)selection for SL DRX	SHARP Corporation
R2-2209543	Correction to resource (re-)selection for UE configured with neither SL DRX nor IUC	SHARP Corporation
R2-2209544	Corrections to resource (re-)selection for Inter-UE coordination	SHARP Corporation
R2-2209675	Correction on MAC Spec for IUC	ZTE Corporation, Sanechips
R2-2209684	Clarification on quitting from active time	Huawei, HiSilicon
R2-2209741	Miscellaneous corrections on TS 38.321 for NR sidelink	CATT
R2-2209853	Corrections on SL enhancements	ASUSTeK
R2-2209859	Capturing TX profile in the MAC spec	Ericsson
R2-2209874	Corrections to BWP inactivity timer handling for SL	Samsung Electronics
R2-2209895	Clarification on destination UE(s) for SL DRX	Huawei, HiSilicon
R2-2210113	Correction on resource re-selection in IUC scheme 2	NEC Corporation
R2-2210188	User plane corrections on NR Sidelink enhancements	LG Electronics France
R2-2210258	Summary of [Post119-e][512][V2X/SL] Remaining Corrections (InterDigital)	InterDigital
R2-2210261	Correction on SL DRX Offset Calculation	InterDigital, ASUSTek
R2-2210262	UL/SL Prioritization for SL Relay	InterDigital, Ericsson
R2-2210309	IUC for random resource allocation	Nokia, Nokia Shanghai Bell
R2-2210335	Draft CR on IUC information transmission considerations	Nokia, Nokia Shanghai Bell
R2-2210374	Handling the running SL DRX timers upon receiving the SL DRX reconfiguration	Huawei, HiSilicon
R2-2210376	Miscellaneous corrections on TS 38.300 for NR sidelink	Xiaomi
R2-2210377	Miscellaneous corrections on TS 38.320 for NR sidelink	Xiaomi
R2-2210382	Miscellaneous corrections on TS 38.321 for NR sidelink	Xiaomi
R2-2210545	Miscellaneous corrections on 38.321	vivo
R2-2210551	Clarification of slot(s) associated with the announced periodic transmission(s)	Samsung Research America
R2-2210558	Clarification of slot(s) associated with the announced periodic transmission(s)	Samsung Research America
R2-2210608	Correction to transmission of IUC information request	Nokia, Nokia Shanghai Bell
R2-2210932	38.321 corrections for SL enhancement	LG Electronics France
R2-2210933	Summary of [AT119-e][502][V2X/SL] 38.321 corrections (LG)	LG

6.17.1: Organizational

TDoc	Title	Source
R2-2209315	LS on TCI state indication of CORESET#0 associated with SS#0 (R1-2208203; contact: Intel, vivo)	RAN1
R2-2209317	Reply LS on LS on further questions on feMIMO RRC parameters (R1-2208224; contact: Ericsson)	RAN1
R2-2209345	LS on active TCI state list for UL TCI (R4-2214972; contact: Nokia)	RAN4
R2-2209868	Miscellaneous MAC Corrections on feMIMO	Samsung
R2-2211007	Miscellaneous MAC Corrections on feMIMO	Samsung

6.17.2: RRC centric Corrections

TDoc	Title	Source
R2-2209493	Discussion on pathloss reference signal	OPPO
R2-2209494	Reply LS on pathloss reference signal	OPPO
R2-2209529	On LS on active TCI state list for UL TCI	Ericsson
R2-2210077	Corrections for Release-17 feMIMO	Ericsson
R2-2210124	Discussion on configurations for Rel-17 unified TCI	CATT
R2-2210236	PL-RS handling for UL TCI states	Nokia, Nokia Shanghai Bell
R2-2210655	CR on 38.331 for unified TCI state in SRS-Config	ZTE Corporation, Sanechips
R2-2210725	FeMIMO RRC corrections	Huawei, HiSilicon
R2-2210785	Summary on RRC MIMO Rel-17	Ericsson
R2-2210790	Discussion on pathloss reference signal	OPPO
R2-2210791	Reply LS on pathloss reference signal	OPPO
R2-2211011	Corrections for Release-17 feMIMO	Ericsson
R2-2211012	[AT119bis-e][018][feMIMO] RRC related Corrections (Ericsson)	Ericsson
R2-2211013	LS on further further questions on feMIMO RRC parameters	RAN2
R2-2211027	Corrections for Release-17 feMIMO	Ericsson
R2-2211028	LS on further further questions on feMIMO RRC parameters	RAN2

6.17.3: MAC centric Corrections

TDoc	Title	Source
R2-2209479	Correction on TCI state indication of CORESET#0 associated with SS#0	vivo, Intel Corporation
R2-2209497	Draft CR on TCI state indication of CORESET#0	OPPO
R2-2209530	On LS on activating two TCI states for CORESET#0	Ericsson
R2-2209887	Corrections to M-TRP Beam Failure Recovery	Samsung Electronics
R2-2210080	Correction on Enhanced TCI States Indication for UE-specific PDCCH MAC CE	Qualcomm Incorporated
R2-2210125	Miscellaneous Corrections to TS 38.321 for feMIMO	CATT
R2-2210190	Miscellaneous MAC corrections for feMIMO	Nokia Germany
R2-2210726	Corrections to FeMIMO MAC	Huawei, HiSilicon
R2-2210771	CR on 38.321 for SPAP SRS TCI State Indication MAC CE	ZTE Corporation, Sanechips
R2-2210796	[Pre119-e][001][feMIMO] MAC centric summary (Samsung)	Samsung
R2-2211006	Summary of [AT119bis-e][019][feMIMO] MAC related Corrections (Samsung)	Samsung

6.20.1: Organizational

TDoc	Title	Source
R2-2209318	LS on condition to apply channel access procedure (R1-2208231; contact: OPPO)	RAN1
R2-2209339	LS reply on TCI assumption for RSSI measurement for FR2-2 (R4-2214477; contact: Apple)	RAN4

6.20.2: Corrections to 71 GHz operation

TDoc	Title	Source
R2-2209534	Discussion on TCI-state indication for inter-RAT HO from E-UTRA to FR2-2	Huawei, HiSilicon
R2-2209593	Correction for condition to apply channel access procedure	OPPO
R2-2209599	Clarification on channelAccessMode2	vivo
R2-2209651	CP corrections for NR operation to 71GHz	ZTE Wistron Telecom AB
R2-2209652	UP corrections for NR operation to 71GHz	ZTE Wistron Telecom AB
R2-2209862	Discussion on RAN1 LS R1-2208231	Ericsson
R2-2209863	Discussion on inter-RAT RSSI measurement	Ericsson
R2-2210727	Release FR2-2 related preference indication configurations in RRC resume	Google Inc.
R2-2210812	Report of [AT119bis-e][203][71 GHz] Corrections to 71 GHz (ZTE)	ZTE
R2-2211055	CP corrections for NR operation to 71GHz	ZTE Wistron Telecom AB

6.21.1: TEI proposals

TDoc	Title	Source
R2-2209326	Reply LS on Flexible Global RAN Node ID (R3-225248; contact: Ericsson)	RAN3
R2-2209495	Discussion on per FR gap UE capability	OPPO
R2-2209496	Draft CR on per FR gap report R17	OPPO
R2-2209581	Discussion on per-FR gap	Intel Corporation
R2-2209792	Discussion on Per FR gap	Apple
R2-2209911	Discussion on per-FR gap capability	vivo
R2-2209912	38.331 CR on per-RF gap capability	vivo
R2-2209913	38.306 CR on per-RF gap capability	vivo
R2-2209914	Discussion on Emergency Service Enhancement	vivo
R2-2209915	36.304 CR on Emergency Service Enhancement	vivo
R2-2209916	38.331 CR on Emergency Service Enhancement	vivo
R2-2210006	Discussion on per-FR-gaps	Huawei, HiSilicon
R2-2210237	Discussion on per-FR gaps	Nokia, Nokia Shanghai Bell
R2-2210296	Discussion on per-FR gap capability	ZTE Corporation, Sanechips
R2-2210448	higher granularity for per-FR gap capability	Qualcomm Incorporated
R2-2210449	higher granularity for per-FR gap capability	Qualcomm Incorporated
R2-2210450	higher granularity for per-FR gap capability discussion	Qualcomm Incorporated
R2-2210491	Updated report of [Post119-e][037][NRTEI17] Emergency Service Enhancement	Huawei, HiSilicon
R2-2210492	Correction on E-UTRA cell selection during emergency service fallback and EPS fallback for emergency call [CellSelection_EmergencyFallback]	Huawei, HiSilicon, Ericsson, China Unicom, CATT, CMCC, BT, Telecom Italia, China Telecom
R2-2210518	Discussion on per-BC granularity of per-FR gap capability	MediaTek Inc.
R2-2210635	Capability for per-FR gaps	Ericsson
R2-2211003	Correction on E-UTRA cell selection during emergency service fallback and EPS fallback for emergency call [CellSelection_EmergencyFallback]	Huawei, HiSilicon, Ericsson, China Unicom, CATT, CMCC, BT, Telecom Italia, China Telecom
R2-2211004	Adding optional feature without capability sigannaling for E-UTRA cell selection during EPS fallback for emergency call [CellSelection_EmergencyFallback]	Huawei, HiSilicon, Ericsson
R2-2211005	Adding optional features without capability sigannaling for E-UTRA cell selection during emergency service fallback and EPS fallback for emergency call [CellSelection_EmergencyFallback]	Huawei, HiSilicon
R2-2211058	Correction on E-UTRA cell selection during emergency service fallback and EPS fallback for emergency call [CellSelection_EmergencyFallback]	Huawei, HiSilicon, Ericsson, China Unicom, CATT, CMCC, BT, Telecom Italia, China Telecom
R2-2211059	Introduction of capabilities for emergency service related fallback [CellSelection_EmergencyFallback]	Huawei, HiSilicon

6.22: NR and MR-DC measurement gap enhancements

TDoc	Title	Source
R2-2209346	LS on priority for legacy gaps (R4-2215132; contact: Nokia)	RAN4

6.24.1: RAN4 led Items

TDoc	Title	Source
R2-2209309	Reply LS on clarification of RACH prioritisation rules between LTE and NR-U (R1-2207935; contact: Ericsson)	RAN1
R2-2209334	LS on intra-band UL CA DC default location clarification (R4-2214419; contact: Apple)	RAN4
R2-2209343	Reply LS on clarification of dualPA-Architecture capability (R4-2214924; contact: Samsung)	RAN4
R2-2209347	LS on new contiguous BW classes for legacy networks (R4-2215160; contact: Qualcomm)	RAN4
R2-2209381	Correction to definition of dualPA-Architecture capability indication	Ericsson, OPPO, Samsung
R2-2209382	Correction to definition of dualPA-Architecture capability indication	Ericsson, OPPO, Samsung
R2-2209383	Discussion on R4 LS on dual-PA architecture clarification	OPPO, Ericsson, Samsung
R2-2209384	Discussion on R4 LS on new FR2 BW Class	OPPO
R2-2209620	CRS-IM default network configuration assumptions for MBSFN configuration in non-DSS scenario	Qualcomm Incorporated
R2-2209621	Introduction of maximum aggregated BW for FBG5	Qualcomm Incorporated
R2-2209622	Introduction of maximum aggregated BW for FBG5	Qualcomm Incorporated
R2-2209796	Correction on FR2 UL gap	Apple
R2-2209797	[Draft] LS on FR2 UL gap	Apple
R2-2209798	Clarification on the NR HST configuration	Apple
R2-2210081	Handling of FR2 UL gap	Samsung
R2-2210134	Correction to definition of dualPA-Architecture capability indication	Ericsson, OPPO, Samsung
R2-2210239	Clarification to dualPA-Architecture capability	Nokia, Nokia Shanghai Bell
R2-2210240	Clarification to intra-band UL CA DC default location clarification	Nokia, Nokia Shanghai Bell
R2-2210241	Reply LS on release independence aspects of newly introduced FR2 CA BW Classes and CBM/IBM UE capability	Nokia, Nokia Shanghai Bell
R2-2210243	Introduction of FR2 FBG2 CA BW classes	Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips, Qualcomm, Xiaomi Communications
R2-2210244	Signalling impacts due to FBG5	Nokia, Nokia Shanghai Bell
R2-2210245	Introduction of FR2 FBG2 CA BW classes	Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips, Qualcomm, Xiaomi Communications
R2-2210322	[Draft] Reply LS on clarification of RACH prioritisation rules between LTE and NR-U	Ericsson
R2-2210323	Discussion on RACH prioritisation rules between LTE and NR-U	Ericsson
R2-2210396	On UE capabilities for simultaneous Rx-Tx	Ericsson
R2-2210539	Discussion on the fallback of new contiguous BW classes	Huawei, HiSilicon
R2-2210540	Introduction of FR2 FBG5 CA BW classes	Huawei, HiSilicon
R2-2210659	Correction to description of secondPA-TxDirectCurrent field	Ericsson, Samsung, OPPO
R2-2210662	Consideration on the FR2 Fallback Group 5	ZTE Corporation, Sanechips
R2-2210693	Discussion on default DC location	ZTE Corporation, Sanechips
R2-2210694	38331_CR_Correction on DC location	ZTE Corporation, Sanechips
R2-2210695	Discussion on RACH prioritization rules between LTE and NR-U	ZTE Corporation, Sanechips
R2-2210696	Reply LS to RAN1 on RACH prioritisation rules between LTE and NR-U	ZTE Corporation, Sanechips
R2-2210701	(Draft)Reply LS on new contiguous BW classes for legacy networks	ZTE Corporation, Sanechips
R2-2210773	Addition of missing need codes in CC-State-r17 and other corrections	Lenovo
R2-2210788	Clarification of the interpretation of intra-band UL CA DC default location	Apple Inc.
R2-2210989	Summary of email discussion [AT119bis-e][009][NR17] DC Location Reporting (Apple)	Apple Inc
R2-2210991	Clarification to intra-band UL CA DC default location clarification	Apple Inc., Lenovo, Nokia, Nokia Shanghai Bell
R2-2211002	Report of [AT119bis-e][008][NR17] Dual PA (Samsung)	Samsung
R2-2211009	Summary of email discussion [AT119bis-e][010][NR17] FBG5 BW Classes (Qualcomm)	Qualcomm Incorporated
R2-2211010	CRS-IM default network configuration assumptions for MBSFN configuration in non-DSS scenario	Qualcomm Incorporated
R2-2211014	Summary of [AT119bis-e][007][NR17] RACH Prioritization	Ericsson
R2-2211015	Reply LS on clarification of RACH prioritisation rules between LTE and NR-U	RAN2
R2-2211042	Correction on FR2 UL gap	Apple
R2-2211043	LS on FR2 UL gap	RAN2
R2-2211057	Clarification on the NR HST configuration	Apple

6.24.3: Other

TDoc	Title	Source
R2-2209305	Reply LS on system information extensions for minimization of service interruption (MINT) (C1-225386; contact: Ericsson)	CT1
R2-2210657	Correction to disasterRoamingFromAnyPLMN	Ericsson, Lenovo
R2-2210658	Correction to disasterRoamingFromAnyPLMN	Ericsson, Lenovo
R2-2210809	Report from [AT119bis-e][012][NR17] MINT (Ericsson)	Ericsson
R2-2210973	Correction to disasterRoamingFromAnyPLMN [MINT]	Ericsson, Lenovo
R2-2210974	Correction to disasterRoamingFromAnyPLMN [MINT]	Ericsson, Lenovo

7.1: Common

TDoc	Title	Source
R2-2209308	LS on updated Rel-17 RAN1 UE features lists for LTE after RAN1#110 Thursday (R1-2207926; contact: NTT DOCOMO, AT&T)	RAN1

7.2.1: Organizational

TDoc	Title	Source
R2-2209359	Reply to LS on UE capability signalling for IoT-NTN (S2-2207839; contact: Vodafone)	SA2
R2-2209659	Discussion of the LS on the deactivation of AS functions	Huawei, HiSilicon
R2-2209712	Discussion on SA2 LS reply on UE capability for IoT NTN	Qualcomm Incorporated
R2-2209715	[Draft] Reply LS on the deactivation of access stratum due to discontinuous coverage	Qualcomm Incorporated
R2-2209716	Clarification on RAT search during discontinuous coverage	Qualcomm Incorporated
R2-2210075	Analysis on the CN impacts for TN and NTN capabilities based on SA2 LS	Nokia, Nokia Shanghai Bell
R2-2210076	[draft] Reply to LS on SA2	Nokia, Nokia Shanghai Bell
R2-2210246	Discussion on SA2 LS on the deactivation of access stratum due to discontinuous coverage	Samsung R&D Institute UK
R2-2210414	UE capability signalling for IoT-NTN	Huawei, HiSilicon
R2-2210525	Applicable cases of AS functions deactivation due to DC	ZTE Corporation, Sanechips
R2-2210528	[DRAFT] Reply LS on RAN feedback for UE capabilities signalling for IoT NTN	ZTE Corporation, Sanechips
R2-2210734	UE capability signalling in IoT NTN	Ericsson
R2-2210744	Corrections on HandoverPreparationInformation in 36.331	CATT
R2-2210763	Deactivation of access stratum due to discontinuous coverage	Ericsson
R2-2210829	Response to “Reply to LS on UE capability signaling for IoT-NTN”	RAN2
R2-2210843	[offline-104] AS deactivation	Qualcomm Incorporated
R2-2210844	[Draft] Reply LS on the deactivation of access stratum due to discontinuous coverage	Qualcomm Incorporated
R2-2210845	[AT119bis-e][105][IoT NTN] Capability signalling (Nokia)	Nokia
R2-2210846	Response to “Reply to LS on UE capability signaling for IoT-NTN”	RAN2
R2-2210865	Reply LS on the deactivation of access stratum due to discontinuous coverage	RAN2
R2-2210867	[AT119bis-e][105][IoT NTN] Capability signalling - second round (Nokia)	Nokia

7.2.2: Stage 2 corrections

TDoc	Title	Source
R2-2209661	Correction on user consent for UE coarse location request	Huawei, HiSilicon

7.2.3: UP corrections

TDoc	Title	Source
R2-2209441	Correction on UE-eNB RTT calculation	MediaTek Inc.
R2-2209660	Discussion on the retransmission timer handling in IoT NTN	Huawei, HiSilicon
R2-2210094	DRX correction for IoT NTN	OPPO
R2-2210571	Correction on UE-eNB RTT calculation	MediaTek Inc.
R2-2210642	Discussion on DRX HARQ RTT timer for IoT NTN	Nokia, Nokia Shanghai Bell
R2-2210697	Clarifications for IoT NTN MAC CEs	Samsung R&D Institute UK
R2-2210699	Correction on HARQ RTT timer with Koffset	ZTE Corporation, Sanechips
R2-2210755	Correction to (UL) HARQ RTT Timer for eMTC in NTNs	Ericsson
R2-2210756	R17 IoT NTN User Plane issues	Ericsson
R2-2210847	Summary [AT119bis-e][106][IoT NTN] UP corrections (Ericsson)	Ericsson
R2-2211019	MAC corrections for Rel-17 IoT NTN	MediaTek Inc.

7.2.4.1: RRC corrections

TDoc	Title	Source
R2-2209440	Miscellaneous corrections to TS 36.331 for IoT NTN	MediaTek Inc.
R2-2210079	Miscellaneous corrections for IoT-NTN	Nokia Solutions & Networks (I)
R2-2210413	Discussion on the update of SIB32	Huawei, HiSilicon
R2-2210530	Clarification on epochTime in SIB31	ZTE Corporation, Sanechips
R2-2210531	Clarification on dedicated SIB31	ZTE Corporation, Sanechips
R2-2210698	CR for RRC corrections for IoT NTN	Samsung R&D Institute UK
R2-2210704	Add a new field for access stratum release	Google Inc.
R2-2210706	Discussion on RRC corrections for IoT NTN	Samsung R&D Institute UK
R2-2210736	Discussion on neighbour cell information	Ericsson
R2-2210745	Corrections on introducing UL gap configuration in 36.331	CATT
R2-2210746	Corrections on SIB32 update notification in 36.331	CATT
R2-2210747	Discussion on the NTN configuration at CHO	CATT
R2-2210848	Report of [Offline-107][IoT NTN] RRC corrections (Huawei)	Huawei, HiSilicon
R2-2211020	RRC corrections for Rel-17 IoT NTN	Huawei

7.2.4.2: Idle/Inactive mode corrections

TDoc	Title	Source
R2-2210700	Corrections on IoT NTN idle mode	Samsung R&D Institute UK
R2-2210731	Miscellaneous idle mode corrections	Ericsson
R2-2211016	Idle mode corrections for Rel-17 IoT NTN	Ericsson

7.2.5: UE capabilities corrections

TDoc	Title	Source
R2-2209439	Add support of reception of SIB32	MediaTek Inc.
R2-2209713	NTN UE capability signaling modification for eMTC	Qualcomm Incorporated
R2-2209714	NTN UE capability signaling modification for NB-IoT	Qualcomm Incorporated
R2-2210078	Corrections for capability for NPRACH segmentated Transmission	Nokia Solutions & Networks (I)
R2-2210776	Correction in the description of ntn-Connectivity-EPC-r17	Lenovo, Motorola Mobility (rapporteur)
R2-2210849	[AT119bis-e][108][IoT NTN] UE Capabilities (MediaTek)	MediaTek

8.1.1: Organizational

TDoc	Title	Source
R2-2209328	LS on NCR Solutions (R3-225253; contact: ZTE)	RAN3
R2-2209329	Progress on NCR identification and authorization (R3-225254; contact: ZTE)	RAN3
R2-2210294	Work plan for Network-controlled repeaters	ZTE Corporation, Sanechips

8.1.2: Signalling for side control information

TDoc	Title	Source
R2-2209367	Signaling for side control information and RRM functions	CATT
R2-2209630	Discussion on C-plane aspects for NCR-MT	Fujitsu
R2-2209639	Signalling of side control information for NCR	Intel Corporation
R2-2209667	Discussion on NCR configuration signaling and RRM functions	Huawei, HiSilicon
R2-2209680	NCR side control signalling and other RRC and RRM aspects	Nokia, Nokia Shanghai Bell
R2-2209697	Signalling for side control information to support NR network-controlled repeaters	AT&T, FirstNet
R2-2209705	Configuration of signaling for side control information	Qualcomm Inc.
R2-2209773	Discussion on Signaling for Side Control Information	Apple
R2-2209933	Discussion on Signaling and procedures for side control information	Lenovo
R2-2210135	Control plane signaling and procedures of network-controlled repeater	NEC Corporation
R2-2210155	Discussion on signalling for side control information	CMCC
R2-2210200	Network-controlled repeaters - key issues	Samsung R&D Institute UK
R2-2210207	Considerations on NCR fwd link config	Sony
R2-2210279	Signalling for NCR side control information	MediaTek Inc.
R2-2210295	Consideration on NCR signalling and RRM functions	ZTE Corporation, Sanechips
R2-2210334	Discussion on RAN2 topics for NCR	Ericsson
R2-2210386	Discussion on NCR Related Procedures	vivo
R2-2210431	Consideration of network-controlled repeaters	Kyocera
R2-2210454	Discussion on NCR capability framework	Philips International B.V.
R2-2210563	Discussion on RAN2 issues for NCR	LG Electronics
R2-2210572	On RAN2 impact of Network-Controlled Repeaters	China Telecom Corporation Ltd.
R2-2210920	Report of [AT119bis-e][NCR] NCR open issues (ZTE)	ZTE Corporation

8.1.3: Repeater management

TDoc	Title	Source
R2-2209706	Management of Network-Controlled Repeater	Qualcomm Inc.

8.2.1: Organizational

TDoc	Title	Source
R2-2209402	Draft Reply LS on Terminology Alignment for Ranging/Sidelink Positioning	CATT
R2-2209588	Work Plan for Study Item on Expanded and Improved NR Positioning	CATT, Intel Corporation, Ericsson
R2-2210040	Discussion on Terminology alignment with SA2	Xiaomi
R2-2210041	Draft Reply LS on Terminology Alignment for Ranging & Sidelink Positioning	Xiaomi
R2-2210909	Report of [AT119bis-e][423][POS] LS to SA2 on SL positioning terminology (Xiaomi)	Xiaomi
R2-2210910	Reply LS on Terminology Alignment for Ranging/Sidelink Positioning	RAN2
R2-2210982	Reply LS on Terminology Alignment for Ranging/Sidelink Positioning	RAN2
R2-2211033	LS Out on Positioning Reference Units (S2-2209590; contact: CATT)	SA2
R2-2211034	LS on LPHAP information delivery to RAN (S2-2209591; contact: Huawei)	SA2
R2-2211052	LS on RAN dependency for Ranging/Sidelink Positioning (S2-2209961; contact: Xiaomi)	SA2

8.2.2: Sidelink positioning

TDoc	Title	Source
R2-2209400	Discussion on SL Positioning	CATT
R2-2209425	Discussion on sidelink positioning	Huawei, HiSilicon
R2-2209536	SL-PRS configuration	MediaTek Inc.
R2-2209560	Discussion on sidelink positioning	vivo
R2-2209606	Support of sidelink positioning	Intel Corporation
R2-2209607	Report of email discussion 406 on sidelink	Intel Corporation
R2-2209671	Protocol aspects of sidelink positioning	Nokia Germany
R2-2209693	Discussion on Sidelink Positioning	InterDigital, Inc.
R2-2209729	Further discussion on sidelink positioning	OPPO
R2-2209767	Sidelink Positioning Architecture and Protocol Stack	Apple
R2-2209979	Discussion on potential solutions for SL positioning	Spreadtrum Communications
R2-2210003	On SL Positioning Protocol and Architecture Aspects	Lenovo
R2-2210042	Discussion on SL positioning	Xiaomi
R2-2210085	Discussion on sidelink positioning	ZTE, Sanechips
R2-2210115	Discussion on Sidelink Positioning	LG Electronics Deutschland
R2-2210167	Considerations on Sidelink positioning	CMCC
R2-2210210	Considerations on sidelink positioning	Sony
R2-2210316	SL positioning Terminology and Protocol Aspects	Ericsson
R2-2210363	Study of Sidelink Positioning Architecture, Signaling and Procedures	Qualcomm Incorporated
R2-2210481	Discussion on SL positioning	Samsung
R2-2210546	Discussion on out-of-coverage sidelink positioning	Samsung R&D Institute UK
R2-2210911	Summary of [AT119bis-e][424][POS] SLPP/RSPP protocol design (Qualcomm)	Qualcomm Incorporated

8.2.3: RAT-dependent integrity

TDoc	Title	Source
R2-2209403	Discussion on RAT dependent integrity	CATT
R2-2209426	Discussion on RAT-dependent integrity	Huawei, HiSilicon
R2-2209561	Discussion on RAT-dependent integrity	vivo
R2-2209608	Integrity for RAT dependent positioning methods	Intel Corporation
R2-2209694	Discussion on RAT-dependent Integrity	InterDigital, Inc.
R2-2209725	Consideration on RAT-dependent integrity	OPPO
R2-2209961	Discussion on RAT-dependent positioning integrity	Lenovo
R2-2209980	Discussion on solutions for integrity of RAT-dependent positioning techniques	Spreadtrum Communications
R2-2210084	Discussion on RAT-dependent methods positioning integrity	ZTE, Sanechips
R2-2210116	Discussion on RAT-dependent positioning integrity	Xiaomi
R2-2210140	Discussion on RAT-dependent integrity	CMCC
R2-2210211	Considerations on solution for integrity of RAT dependent positioning	Sony
R2-2210317	RAT-dependent integrity and TP for TR	Ericsson
R2-2210364	Integrity of NR Positioning Technologies	Qualcomm Incorporated
R2-2210547	Discussion on integrity of RAT dependent positioning techniques	Samsung R&D Institute UK
R2-2210892	[Pre119bis-e][405] Summary of AI 8.2.3 on RAT-dependent integrity (Samsung)	Samsung
R2-2210918	[AT119bis-e][429][POS] Rel-18 integrity text proposal (CATT)	CATT
R2-2210979	[AT119bis-e][429][POS] Rel-18 integrity text proposal (CATT)	CATT

8.2.4: LPHAP

TDoc	Title	Source
R2-2209401	Discussion on LPHAP	CATT
R2-2209405	Report of [Post119-e][407][POS] LPHAP upper layer enhancements (CATT)	CATT
R2-2209424	Discussion on the LPHAP	Huawei, HiSilicon
R2-2209562	Discussion on LPHAP	vivo
R2-2209609	Support of LPHAP	Intel Corporation
R2-2209695	Discussion on LPHAP	InterDigital, Inc.
R2-2209727	Further consideration on LPHAP	OPPO
R2-2209768	Potential LPHAP enhancements	Apple
R2-2209962	Discussion on low power high accuracy positioning	Lenovo
R2-2210083	Discussion on LPHAP	ZTE, Sanechips
R2-2210117	Discussion on LPHA positioning	Xiaomi
R2-2210168	Considerations on LPHAP	CMCC
R2-2210212	Considerations on on solution for Low Power High Accuracy Positioning	Sony
R2-2210318	LPHAP and Text Proposal for TR	Ericsson
R2-2210365	Enhancements to Positioning in RRC_INACTIVE State for LPHAP	Qualcomm Incorporated
R2-2210482	Discussion on LPHAP	Samsung
R2-2210917	LS on SRS in multiple cells	RAN2

8.2.5: RedCap positioning

TDoc	Title	Source
R2-2209404	Discussion on RedCap Positioning	CATT
R2-2209563	Discussion on RedCap positioning	vivo
R2-2209643	Discussion on RedCap Positioning	Huawei, HiSilicon
R2-2209696	Discussion on Redcap Positioning	InterDigital, Inc.
R2-2209756	RedCap positioning	Intel Corporation
R2-2209963	Discussion on RedCap positioning	Lenovo
R2-2210082	Discussion on RedCap positioning	ZTE, Sanechips
R2-2210118	Discussion on RedCap UE positioning	Xiaomi
R2-2210319	Positioning for RedCap UEs	Ericsson

8.3.1: Organizational

TDoc	Title	Source
R2-2209365	LS on skeleton of TR 38.864 for NR network energy savings (R3-225203; contact: Huawei)	RAN3
R2-2210415	Work plan for NR network energy savings	Huawei, HiSilicon
R2-2210416	TR 38.864 skeleton for study on network energy savings for NR	Huawei, HiSilicon
R2-2210417	Report of [POST119-e][313][NES] Details of solutions (Huawei)	Huawei, HiSilicon
R2-2210792	Report of [POST119-e][313][NES] Details of solutions (Huawei)	Huawei, HiSilicon
R2-2211067	TP on Cell DTX DRX to TR 38.864	Huawei, HiSilicon, Apple

8.3.2: gNB and UE supporting techniques

TDoc	Title	Source
R2-2209474	On solutions aiming at reducing periodic DL transmissions (1-4)	CATT
R2-2209475	Autonomous SCell activation and gNB DTX/DRX	CATT
R2-2209476	Assistance Information from the UE	CATT
R2-2209735	Group signalling for network energy saving techniques	Intel Corporation
R2-2209736	Assistance information from UE	Intel Corporation
R2-2209757	Further discussion on NW DTX-DRX	Apple
R2-2209758	Discussion on Network energy saving for CONNECTED UE - group CHO and BWP adaptation	Apple
R2-2209759	Discussion on Network energy saving for IDLE and INACTIVE UE - cell (re)selection and SSB-less	Apple
R2-2209809	Discussions on time domain techniques for network energy saving	vivo
R2-2209810	cell (re)selection and handover considering network energy saving	vivo
R2-2209811	Discussions on frequency domain techniques for network energy saving	vivo
R2-2209886	Aspects on Network energy savings	VODAFONE Group Plc
R2-2209964	Discussion on supporting of network energy savings for NR	Lenovo
R2-2209965	NES impact to RRC_CONNECTED UE	Lenovo
R2-2210019	Discussion on network energy savings	OPPO
R2-2210020	Discussion on the UE assistance information	OPPO, Apple
R2-2210053	Energy saving for On-demand other SIBs	Xiaomi
R2-2210105	Consideration on network energy saving	Fujitsu
R2-2210128	Common Channel Updates for NES	Nokia, Nokia Shanghai Bell
R2-2210129	Mobility and Access Control for NES	Nokia, Nokia Shanghai Bell
R2-2210141	Discussion on time domain NES solutions	CMCC
R2-2210142	Discussion on UE assistance information for NES	CMCC
R2-2210143	Discussion on Mobility issues	CMCC
R2-2210185	Details on time domain solutions for NES	Nokia, Nokia Shanghai Bell
R2-2210225	Discussion on idle and inactive state UE grouping for NES gNB DTX	Sony
R2-2210226	SIB-less and UE wake up request signal	Sony
R2-2210227	Handover enhancement for NES	Sony
R2-2210235	Aspects on Network Energy Saving Techniques	Fraunhofer IIS, Fraunhofer HHI
R2-2210252	Energy Saving from RRC Idle Operation	Lenovo
R2-2210253	Further aspects on NW DTX/DRX	Ericsson
R2-2210254	Paging Enhancements for Beams	Ericsson
R2-2210255	Handling of Legacy UEs on a NES Capable Cell	Ericsson
R2-2210282	Time domain NES aspects	InterDigital
R2-2210283	Frequency domain NES aspects	InterDigital
R2-2210284	UE assistance information for NES	InterDigital
R2-2210337	UE awareness by gNB and coexistence with legacy UEs for NES	NEC Telecom MODUS Ltd.
R2-2210369	Network energy saving techniques	Qualcomm Incorporated
R2-2210370	NES Proposed Common Signalling Techniques Assessment	Qualcomm Incorporated
R2-2210383	NW DTX/DRX operation for NES	ETRI
R2-2210418	Discussion on SSB-less and SIB1-less techniques for NES	Huawei, HiSilicon
R2-2210419	Discussion on cell activation triggered by UL WUS	Huawei, HiSilicon
R2-2210420	Discussion on network DTX	Huawei, HiSilicon
R2-2210478	Discussion on network energy saving	Sharp
R2-2210556	Considerations on Energy saving	KDDI Corporation
R2-2210595	Discussion on resource adaptation for NES	LG Electronics Inc.
R2-2210611	Assistance Information for NES	Samsung
R2-2210612	Cell Prioritization for NES	Samsung
R2-2210613	Resource Adaptation for NES	Samsung
R2-2210653	SSB/SIB/Paging and Group HO	LG Electronics Finland
R2-2210656	Considerations on Network Energy Saving techniques	MediaTek Inc.
R2-2210665	Supporting access via NES cell	ZTE corporation, Sanechips
R2-2210666	Techniques in various domains and UE assistance information for network energy saving	ZTE corporation, Sanechips
R2-2210667	Supporting multiple power states	ZTE corporation, Sanechips
R2-2210707	Discussion on Network Energy Saving in RAN2 study	NTT DOCOMO INC.
R2-2210772	Considerations on Network Energy Saving techniques	MediaTek Inc.
R2-2210995	Report of [Offline-302][NES] Cell Selection/Reseletion and SSB/SIB-less (Huawei	Huawei
R2-2211066	Report of [POST119bis][303][NES] TP on NW DTX/DRX (Huawei/Apple)	Huawei, HiSilicon, Apple

8.4.1: Organizational

TDoc	Title	Source
R2-2210500	RAN2 Work Plan for Rel-18 Further NR Mobility Enhancements WI	MediaTek Inc., Apple

8.4.2.1: Target Performance Enhancements

TDoc	Title	Source
R2-2209394	Open Issues on Target Performance Enhancements	CATT
R2-2209480	Enhancements to improve performance for L1 L2 mobility	vivo
R2-2209600	Discussion on latency model of L1 L2 mobility	Intel Corporation
R2-2209625	Latency reduction for synchronization procedure for L1/L2 mobility	OPPO
R2-2209722	Discussion of the major delay components and possible solutions	Futurewei
R2-2209929	Target Performance Enhancements for L1L2-based Inter-cell Mobility	MediaTek Inc.
R2-2210055	Latency reduction required for high performance beam	Xiaomi
R2-2210065	Considerations on reducing HO interruption time	Samsung
R2-2210106	Consideration on L1/L2 based inter-cell mobility	Fujitsu
R2-2210163	Considerations on target performance enhancements	CMCC
R2-2210192	Target enhancements and latency model for L1/2 triggered handover	Interdigital, Inc.
R2-2210230	Framework fulfilling WID Objectives	Lenovo
R2-2210330	Enhancements on delay components for L1/L2 inter-cell mobility	Ericsson
R2-2210349	On Interruption Time Reduction in LLM	Nokia, Nokia Shanghai Bell
R2-2210470	Consideration for Target Performance Enhancements of L1/L2 mobility	Sharp
R2-2210590	Discussion on TA for candidate cell for L1L2 mobility	LG Electronics Inc.
R2-2210616	Further Considerations on L1/L2 Signaling Based Mobility	ZTE Corporation,Sanechips
R2-2210722	Target Performance Enhancements and supported scenarios	Huawei, HiSilicon

8.4.2.2: RRC

TDoc	Title	Source
R2-2209395	Discussion on RRC Configuration for L1L2 Mobility	CATT
R2-2209481	RRC configurations of candidate target cell for L1/L2 mobility	vivo
R2-2209524	RRC configuration and modelling for L1/L2 mobility	Huawei, HiSilicon
R2-2209601	Discussion on configurations for multiple candidate cells of L1 L2 mobility	Intel Corporation
R2-2209628	Discussion on configuration related issues for L1/L2 mobility	OPPO
R2-2209723	Dynamic RRC pre-configuration for L1L2 mobility	Futurewei
R2-2209787	Conditional handover and other critical aspects in L2/L1 mobility	Apple
R2-2209869	RRC Modeling for Candidate Cells in L1/L2 Inter-cell Mobility	Samsung
R2-2209930	RRC Configurations for L1L2-based Inter-cell Mobility	MediaTek Inc.
R2-2209941	RRC configuration for lower layer based mobility	Lenovo
R2-2210056	Selection between Model 1 and Model 2 for candidate cell configuration	Xiaomi
R2-2210107	Configuration and maintenance for multiple candidate target cells	Fujitsu
R2-2210164	Considerations on RRC related issues	CMCC
R2-2210171	Discussion on candidate cell configuration and maintenance	ZTE Corporation, Sanechips
R2-2210193	RRC Support for L1/2 Triggered Handover	Interdigital, Inc.
R2-2210329	[Post119-e][048][feMob] Candidate target configurations for L1/L2 mobility	Ericsson
R2-2210333	RRC aspects of L1/L2 based inter-cell mobility	Ericsson
R2-2210350	On RRC Configuration Options for LLM	Nokia, Nokia Shanghai Bell
R2-2210351	On Dynamic Switching in LLM	Nokia, Nokia Shanghai Bell
R2-2210398	Considerations on possible restrictions in RRC configuration	NEC
R2-2210444	Discussion on RRC model for L1L2 mobility	LG Electronics
R2-2210471	RRC Configurations of L1/L2 mobility	Sharp
R2-2210561	Signaling structure with flexibility and efficiency	LG Electronics
R2-2210824	Report of [AT119bis-e][023][feMob] Terminology (Nokia)	Nokia

8.4.2.3: Dynamic Switch

TDoc	Title	Source
R2-2209396	Discussion on Dynamic Switch Mechanism	CATT
R2-2209482	Discussion on dynamic switch for L1 L2 mobility	vivo
R2-2209525	Solutions for dynamic cell switch in L1/L2 mobility	Huawei, HiSilicon
R2-2209546	Discussion on scenarios for dynamic switch	SHARP Corporation
R2-2209590	Discussion on some issues in L1L2 mobility	NTT DOCOMO, INC.
R2-2209602	Discussion on synchronization enhancements for dynamic switch	Intel Corporation
R2-2209627	Open issues on dynamic switching for L1/L2 mobility	OPPO
R2-2209701	L1/L2 Mobility Considerations	Qualcomm Incorporated
R2-2209724	Discussion on L1/L2 Mobility operations	Futurewei
R2-2209786	Viewing SpCell/SCell dynamic switch as an intra-DU L2/L1 handover	Apple
R2-2209854	Discussion on L1 L2 mobility procedure	ASUSTeK
R2-2209870	L1/L2 signalling for inter-cell mobility	Samsung
R2-2209931	Cell Switch for L1L2-based Inter-cell Mobility	MediaTek Inc.
R2-2209942	Lower layer based dynamic mobility	Lenovo
R2-2209977	Discussion on L1/L2 based inter-cell mobility	Spreadtrum Communications
R2-2210058	Discussion on the dynamic switching procedure	Xiaomi
R2-2210165	Considerations on dynamic switch	CMCC
R2-2210172	Discussion on dynamic switch for L1L2 mobility	ZTE Corporation, Sanechips
R2-2210194	L1/2 handover trigger	Interdigital, Inc.
R2-2210331	Execution procedure for L1/L2 based inter-cell mobility	Ericsson
R2-2210399	Basic considerations on dynamic switch	NEC
R2-2210445	Discussion on dynamic switch for L1L2 mobility	LG Electronics
R2-2210762	Consideration on L1L2 mobility	KDDI Corporation

8.4.2.4: Inter cell BM L1 measurements and beam ind

TDoc	Title	Source
R2-2209397	Discussion on L1 inter-cell beam measurement and indication	CATT
R2-2209483	Discussion on L1 measurements and beam indication	vivo
R2-2209603	Discussion on enhancements to L1 measurements	Intel Corporation
R2-2209626	Discussion on measurement related issue of L1/L2 mobility	OPPO
R2-2209871	Considerations on the L1 Measurement and Report	Samsung
R2-2209932	RAN2 Aspects of L1 Enhancements for L1L2-based Inter-cell Mobility	MediaTek Inc.
R2-2209992	Discussion on the issue of L1 enhancements for ICBM	Spreadtrum Communications
R2-2210057	Discussion on inter-cell beam management	Xiaomi
R2-2210166	Potential solutions for L1 measurements	CMCC
R2-2210173	Discussion on inter-cell L1 measurements	ZTE Corporation, Sanechips
R2-2210231	Mobility procedural delegation to lower layers	Lenovo
R2-2210332	L1 measurements and beam indication for L1/L2 based inter-cell mobility	Ericsson
R2-2210352	On Configuration of Inter-Cell LLM	Nokia, Nokia Shanghai Bell
R2-2210451	Measurements for L1/L2 mobility	InterDigital, Inc.
R2-2210472	Inter-cell beam management enhancements for L1/L2 mobility	Sharp
R2-2210723	L1 measurement and beam indication for L1L2 mobility	Huawei, HiSilicon
R2-2211000	LS on L1 measurement, beam indication, RRC, and dynamic cell switching	RAN2
R2-2211061	LS on RAN2 agreements about L1/L2-triggered mobility (LTM)	RAN2

8.4.3: NR-DC with selective activation cell of groups

TDoc	Title	Source
R2-2209398	Consideration on Selective Activation of Cell Groups in NR-DC	CATT
R2-2209484	Discussion on NR-DC with selective activation cell of groups	vivo
R2-2209589	Discussion on NR-DC with selective activation cell of groups	NTT DOCOMO, INC.
R2-2209594	Further mobility enhancements for NR-DC	Vodafone
R2-2209604	Discussion on NR-DC with selective activation cell of groups	Intel Corporation
R2-2209629	Discussion on selective activation of SCGs for NR-DC	OPPO
R2-2209685	Selective activation of cell groups in NR-DC	Qualcomm Incorporated
R2-2209788	Description of a Reference Config for multi-SN handling	Apple
R2-2209789	Security from UE mobility across SNs and limiting SN changes to within a single MN	Apple
R2-2209872	Considerations on Subsequent CPAC after SCG Change	Samsung
R2-2209950	Discussion on SCG selective activation	Lenovo
R2-2209974	Discussion on NR-DC with selective activation cell of groups	Spreadtrum Communications
R2-2210073	Further analysis on the solution aspects for selective activation	Nokia, Nokia Shanghai Bell
R2-2210156	Discussion on NR-DC with selective activation cell of groups	CMCC
R2-2210174	Discussion on NR-DC with selective activation of the cell groups	ZTE Corporation, Sanechips
R2-2210308	NR-DC with selective activation	Ericsson
R2-2210400	Possible flows of selective SCG activation	NEC
R2-2210401	Consideration on selective SCG activation	NEC
R2-2210452	Selective activation of cell groups	InterDigital, Inc.
R2-2210473	Discussion of selective activation	Sharp
R2-2210488	Discussion on NR-DC with selective activation of the cell groups	Xiaomi
R2-2210516	Discussion on selective SCG activation	MediaTek Inc.
R2-2210581	Selective Cell Group Activation	LG Electronics
R2-2210617	Discussion on NR-DC with selective activation of the cell groups	China Telecom
R2-2210671	Discussion on NR-DC with selective activation of the cell groups	DENSO CORPORATION
R2-2210724	NR-DC with selective activation of cell groups	Huawei, HiSilicon

8.5.1: Organizational

TDoc	Title	Source
R2-2209552	Work Plan for Rel-18 SI on XR Enhancements for NR	Nokia, Qualcomm (Rapporteurs)
R2-2209553	SA2 Status for XR	Nokia (Rapporteur)
R2-2209554	SA4 Status for XR	Nokia (Rapporteur)
R2-2211041	LS on XR and Media Services (S2-2209979; contact: vivo)	SA2

8.5.2.1: PDU sets and data bursts

TDoc	Title	Source
R2-2209414	On mapping PDU Sets for XR	Futurewei
R2-2209450	Discuss on PDU Sets	Qualcomm Incorporated
R2-2209467	PDU sets characterization and mapping	CATT
R2-2209485	Discussion on PDU sets and data bursts for XR awareness	vivo
R2-2209555	PDU Set Identification Details	Nokia, Nokia Shanghai Bell
R2-2209631	DRB mapping for XR traffic	Intel Corporation
R2-2209635	XR related information for awareness in RAN	Intel Corporation
R2-2209644	PDU-set to DRB mapping for XR	ZTE Corporation, Sanechips
R2-2209668	Discussion on QoS support with PDU Set granularity	Xiaomi Communications
R2-2209686	Discussion on PDU sets and data bursts	InterDigital, Inc.
R2-2209698	Support for XR-aware scheduling	AT&T
R2-2209777	PDU Sets and Mapping of QoS flows and DRBs for XR	Apple
R2-2209846	Discussion on PDU Set for XR-awareness	NEC Corporation
R2-2209873	Number of DRBs for XR	VODAFONE Group Plc
R2-2209937	Discussion on PDU sets and data burst awareness in RAN	Lenovo
R2-2209987	Discussion on XR-awareness info	Spreadtrum Communications
R2-2210005	Discussion on handling and usage of PDU sets and data bursts related information in RAN2	Samsung R&D Institute India
R2-2210008	Discussion on PDU-Sets handling	KT Corp.
R2-2210021	Discussion on PDU Set awareness	OPPO
R2-2210108	Considerations on PDU Set handling	Fujitsu
R2-2210201	Handling of XR PDU sets in RAN	Huawei, HiSilicon
R2-2210213	Considerations on XR awarness	Sony
R2-2210360	Discussion on PDU Sets and Data Bursts for XR	Google Inc.
R2-2210381	Discussion XR-Awareness for XR services	Meta
R2-2210508	Considerations on PDU sets and Data bursts in RAN	CMCC
R2-2210593	Discussion on PDU sets and data bursts	LG Electronics Inc.
R2-2210603	Discussion on PDU Sets mapping to DRBs	TCL Communication
R2-2210619	Discussion on PDU set parameters for XR-awareness	III
R2-2210628	Discussion on PDU sets and data bursts	NTT DOCOMO, INC.
R2-2210689	Discussion on PDU Set and Data Burst	Ericsson

8.5.2.2: PDU prioritization

TDoc	Title	Source
R2-2209451	Discussion on PDU prioritization	Qualcomm Incorporated
R2-2209468	Prioritization of XR traffic	CATT
R2-2209486	Discussion on PDU prioritization for XR awareness	vivo
R2-2209556	LCP Impacts for XR	Nokia, Nokia Shanghai Bell
R2-2209632	Handling and in-sequence delivery of XR packets with different priorities	Intel Corporation
R2-2209646	PDU-set prioritization for XR	ZTE Corporation, Sanechips
R2-2209687	Discussion on PDU prioritization	InterDigital, Inc.
R2-2209778	Enhancements for Traffic Prioritization in XR	Apple
R2-2209889	Discussion on PDU prioritization	Lenovo
R2-2209990	Some LCP enhancements based on the traffic awareness	Spreadtrum Communications
R2-2210013	Discussion on LCP impact	Samsung
R2-2210022	Discussion on PDU prioritization	OPPO
R2-2210046	Discussion on the LCP enhancements for XR	ITRI
R2-2210202	Discussion about XR-awareness impacts on LCP	Huawei, HiSilicon
R2-2210361	Discussion on PDU prioritization	Google Inc.
R2-2210507	Impact on PDU Prioritization by XR Awareness	CMCC
R2-2210536	Discussion on traffic prioritization of XR traffic	Beijing Xiaomi Mobile Software
R2-2210560	Discussion on the prioritization for XR	LG Electronics Inc.
R2-2210620	Discussion on PDU prioritization for XR-awareness	III
R2-2210649	On PDU prioritisation	MediaTek Inc.
R2-2210688	Discussion on PDU Prioritization	Ericsson

8.5.2.3: PDU discard

TDoc	Title	Source
R2-2209452	Discussion on PDU discard	Qualcomm Incorporated
R2-2209469	PDU Discard for XR Services	CATT
R2-2209487	Discussion on PDU discard for XR awareness	vivo
R2-2209557	PDU Discard for XR	Nokia, Nokia Shanghai Bell
R2-2209586	PDU Set and PDCP Discard for XR	Samsung
R2-2209633	Packet discard optimizations for XR traffic	Intel Corporation
R2-2209645	PDU-set discard functionality for XR	ZTE Corporation, Sanechips
R2-2209669	Discussing on PDU discarding of XR traffic	Xiaomi Communications
R2-2209688	Discussion on PDU discard	InterDigital, Inc.
R2-2209779	Enhancements for PDU Discarding in XR	Apple
R2-2209888	Discussion on PDU discarding	Lenovo
R2-2209993	PDU discard of XR traffic	Spreadtrum Communications
R2-2210023	Discussion on PDU discard	OPPO
R2-2210203	Discussion on PDU discarding for XR traffic	Huawei, HiSilicon
R2-2210362	Discussion on PDUs Discarding	Google Inc.
R2-2210371	Discussion on PDU discard for XR video traffic	Futurewei
R2-2210375	PDU Set Handling	Meta
R2-2210506	Considerations on PDU Discarding of XR Traffic	CMCC
R2-2210559	Discussion on the discard and retransmission for XR	LG Electronics Inc.
R2-2210627	Discussion on PDU discard	NTT DOCOMO, INC.
R2-2210650	On the need and impact of PDU discard in the RAN	MediaTek Inc.
R2-2210687	Discussion on PDU Discard	Ericsson
R2-2210814	TP to 38.835	Nokia
R2-2210815	TP to 38.835	Nokia

8.5.3.1: DRX enhancements

TDoc	Title	Source
R2-2209453	DRX enhancements for XR	Qualcomm Incorporated
R2-2209470	DRX Enhancements to Address Cycle Mismatch	CATT
R2-2209471	Serving XR traffic with minimum power consumption	CATT
R2-2209488	Discussion on DRX enhancements for XR power saving	vivo
R2-2209502	On DRX enhancements for handling non-integer traffic periodicity	Futurewei
R2-2209511	Discussion on CDRX enhancement for XR based on outputs from RAN1	OPPO
R2-2209512	Discussion on CDRX enhancement for Power saving	OPPO
R2-2209515	Analysis on XR traffic characteristics for C-DRX enhancement	Huawei, HiSilicon
R2-2209516	Further discussion on C-DRX enhancements for XR	Huawei, HiSilicon
R2-2209634	C-DRX enhancements for XR traffic	Intel Corporation
R2-2209649	DRX enhancements for XR	ZTE Corporation, Sanechips
R2-2209670	Discussing on XR-specific C-DRX enhancements	Xiaomi Communications
R2-2209689	Discussion on DRX enhancements	InterDigital, Inc.
R2-2209780	On C-DRX Enhancement for HARQ Handling in XR	Apple
R2-2209938	Discussion of DRX enhancement	Lenovo
R2-2210009	DRX enhancement for power saving in XR	LG Electronics Inc.
R2-2210061	Discussion on power saving scheme for XR	Samsung
R2-2210144	Discussion on DRX enhancements for XR-specific power saving	CMCC
R2-2210186	DRX enhancements for XR	Nokia, Nokia Shanghai Bell
R2-2210189	Candidate Solutions on C-DRX Enhancements	NEC Telecom MODUS Ltd.
R2-2210214	Considerations on XR specific C-DRX power saving enhancements	Sony
R2-2210359	DRX Enhancement for XR	Google Inc.
R2-2210501	C-DRX enhancements for XR-specific power saving	DENSO CORPORATION
R2-2210651	C-DRX enhancements for XR	MediaTek Inc.
R2-2210690	Discussion on RAN2-specific CDRX aspects	Ericsson
R2-2210692	Discussion on solutions for DRX cycle mismatch and jitter	Ericsson
R2-2210705	Discussion on DRX enhancements for XR-specific power saving	III

8.5.3.2: Other enhancements

TDoc	Title	Source
R2-2209454	Non-DRX power saving enhancements for XR	Qualcomm Incorporated
R2-2209455	Information to RAN for UE power savings	Qualcomm Incorporated
R2-2209489	XR specific information for RAN power saving	vivo
R2-2209648	Other Power Saving enhancements for XR	ZTE Corporation, Sanechips
R2-2209690	Discussion on PDCCH monitoring enhancements	InterDigital, Inc.
R2-2209781	XR-Specific Power Saving for Configured Scheduling	Apple
R2-2209939	Discussion of PDCCH monitoring enhancement	Lenovo
R2-2209982	Discussion on power saving in XR	Spreadtrum Communications
R2-2210010	Enhancement in legacy power saving for XR	LG Electronics Inc.
R2-2210062	Discussion on XR-awareness for power saving scheme design	Samsung
R2-2210145	Discussion on XR-specific power saving	CMCC
R2-2210187	Multiple CG configurations for XR	Nokia, Nokia Shanghai Bell
R2-2210825	Information to RAN for UE power savings	Qualcomm Incorporated

8.5.4: XR-specific capacity improvements

TDoc	Title	Source
R2-2210764	On XR Capacity Enhancements	Dell Technologies

8.5.4.1: Feedback enhancements

TDoc	Title	Source
R2-2209456	UE feedback enhancements for capacity improvement	Qualcomm Incorporated
R2-2209472	BSR enhancement for XR capacity	CATT
R2-2209490	Discussion on feedback enhancements for XR-specific capacity improvements	vivo
R2-2209517	Discussion on buffer status report for XR	Google Inc.
R2-2209558	BSR for XR	Nokia, Nokia Shanghai Bell
R2-2209591	BSR enhancement for XR capacity	MediaTek Inc.
R2-2209636	Enhancements to Buffer Status Reporting for XR Traffic	Intel Corporation
R2-2209650	UE feedback enhancements for XR capacity	ZTE Corporation, Sanechips
R2-2209672	Discussing on UE feedback enhancements for XR capacity	Xiaomi Communications
R2-2209691	Discussion on XR-specific feedback enhancements	InterDigital, Inc.
R2-2209782	BSR Enhancements for XR	Apple
R2-2209828	Discussion on BSR enhancements for XR	Samsung
R2-2209890	Discussion on UE Feedback enhancements	Lenovo
R2-2209983	Some feedback enhancements on XR capacity	Spreadtrum Communications
R2-2210024	Discussion on feedback enhancement	OPPO
R2-2210047	Discussion on the UE feedback enhancements for XR	ITRI
R2-2210150	Consideration on BSR enhancement for XR	CMCC
R2-2210191	Feedback Enhancements for Capacity Improvement	NEC Telecom MODUS Ltd.
R2-2210215	Considerations on BSR	Sony
R2-2210502	Discussion on UE feedback enhancements for XR capacity	DENSO CORPORATION
R2-2210537	Discussion on BSR enhancement for XR-specific capacity improvement	Huawei, HiSilicon
R2-2210599	Discussion on BSR enahancement for timing information in XR	LG Electronics Inc.
R2-2210621	Discussion on Feedback enhancements for XR-specific capacity improvements	III
R2-2210686	Discussion on BSR enhancements	Ericsson
R2-2210816	Report of [AT119bis-e][207][XR] BSR enhancements for XR (NN)	NN
R2-2210817	TP to 38.835 on BSR enhancements for XR	NN

8.5.4.2: Scheduling enhancements

TDoc	Title	Source
R2-2209457	Scheduling enhancements for capacity improvement	Qualcomm Incorporated
R2-2209473	Discussion on CG enhancements	CATT
R2-2209491	Discussion on scheduling enhancements XR-specific capacity improvements	vivo
R2-2209559	Capacity Enhancements for XR	Nokia, Nokia Shanghai Bell
R2-2209592	Scheduling enhancement for XR capacity	MediaTek Inc.
R2-2209647	Scheduling enhancements for XR	ZTE Corporation, Sanechips
R2-2209673	Discussing on XR-specific scheduling enhancements	Xiaomi Communications
R2-2209692	Discussion on scheduling enhancements	InterDigital, Inc.
R2-2209783	Considerations of Scheduling Enhancement for XR	Apple
R2-2209907	Scheduling and measurement gap enhancements for XR traffic	Intel Corporation
R2-2209940	Discussion of scheduling enhancement	Lenovo
R2-2209991	Some enhancements on XR scheduling	Spreadtrum Communications
R2-2209994	Enhancement to measurement gap	Spreadtrum Communications
R2-2210025	Discussion on scheduling enhancement	OPPO
R2-2210151	Consideration on scheduler enhancement for XR	CMCC
R2-2210216	Considerations on XR specific capacity improvements	Sony
R2-2210358	Scheduling Enhancement for XR	Google Inc.
R2-2210483	Discussion on CG enhancement	Samsung
R2-2210541	Discussion on scheduling enhancement for XR traffic	Huawei, HiSilicon
R2-2210600	Discussion on Scheduling enahancement for XR	LG Electronics Inc.
R2-2210604	Further discussion on DG for XR uplink traffic transmission	TCL Communication
R2-2210691	Discussion on Scheduling enhancements	Ericsson

8.6.1: Organizational

TDoc	Title	Source
R2-2210368	List of RAN2 Agreements in IoT-NTN	MediaTek Inc.

8.6.2.1: HARQ enhancements

TDoc	Title	Source
R2-2209410	Discussion on the HARQ disabling in IoT NTN	CATT
R2-2209442	Discussion on disabling HARQ Feedback in IoT-NTN	MediaTek Inc.
R2-2209666	Discussion on disabling DL HARQ feedback	Huawei, HiSilicon
R2-2209717	Enhancement for UL and DL HARQ processes	Qualcomm Incorporated
R2-2209750	Discussion on performance enhancement for IoT NTN	Transsion Holdings
R2-2209834	Further discussion on HARQ enhancements	ZTE Corporation, Sanechips
R2-2210036	Discussion on disabling of HARQ feedback	Xiaomi
R2-2210088	Discussion on HARQ enhancement for IoT NTN	OPPO
R2-2210152	Discussion on the HARQ enhancement for IoT-NTN	CMCC
R2-2210195	Disabling HARQ feedback for IoT-NTN	Interdigital, Inc.
R2-2210643	On HARQ enhancements for IoT NTN	Nokia, Nokia Shanghai Bell
R2-2210702	On HARQ enhancements for IoT NTN	Samsung R&D Institute UK
R2-2210761	R18 IoT NTN performance enhancement	Ericsson
R2-2210863	Report for [AT119bis-e][120][IoT NTN Enh] HARQ enhancements (CMCC)	CMCC

8.6.2.2: GNSS operation enhancements

TDoc	Title	Source
R2-2209409	Discussion on the issues of GNSS operation in connected mode	CATT
R2-2209835	Further discussion on GNSS enhancements	ZTE Corporation, Sanechips
R2-2209966	Considerations on reducing UE GNSS operations in long connection time	Lenovo
R2-2210097	Discussion on GNSS operation in connected mode	OPPO
R2-2210153	Discussion on the GNSS enhancement for IoT-NTN	CMCC
R2-2210406	Discussion on GNSS operation	Huawei, HiSilicon
R2-2210440	GNSS acquisition and reporting for IoT NTN	InterDigital
R2-2210644	Regarding GNSS operation enhancements for IoT NTN	Nokia, Nokia Shanghai Bell
R2-2210703	On improved GNSS operation for IoT NTN	Samsung R&D Institute UK
R2-2210840	Report of [AT119bis-e][101][R18 IoT-NTN] GNSS operation (CATT)	CATT

8.6.3: Mobility Enhancements

TDoc	Title	Source
R2-2209411	Discussion on IoT NTN Mobility Enhancements	CATT
R2-2209443	On Mobility Enhancements in IoT-NTN	MediaTek Inc.
R2-2209580	Discussion on neighbour cell measurements in IoT NTN	Intel Corporation
R2-2209718	Connected mode mobility enhancements	Qualcomm Incorporated
R2-2209719	RLF detection in earth fixed cell	Qualcomm Incorporated
R2-2209751	Discussion on mobility enhancement for IoT NTN	Transsion Holdings
R2-2209794	Neighbour cell measurements before RLF	Apple
R2-2209836	Further discussion on mobility enhancements	ZTE Corporation, Sanechips
R2-2209967	NTN-specific CONNECTED neighbour cell measurement for NB-IoT	Lenovo
R2-2209968	On IDLE mobility for IoT NTN	Lenovo
R2-2209978	Discussion on triggering neighbour cell measurement before RLF	Spreadtrum Communications
R2-2210074	On the applicability of mobility enhancements features for IoT-NTN	Nokia, Nokia Shanghai Bell
R2-2210089	Discussion on mobility enhancement for IoT NTN	OPPO
R2-2210122	Enhancements on the neighbour cell measurement	Xiaomi
R2-2210154	Discussion on the mobility enhancement for IoT-NTN	CMCC
R2-2210196	IoT-NTN mobility enhancements	Interdigital, Inc.
R2-2210321	Mobility Enhancement for IoT NTN	Samsung R&D Institute UK
R2-2210372	Use of Elevation Angle Threshold for IoT NTN Neighbour Cell Measurements	SHARP Corporation
R2-2210407	Discussion on mobility enhancements	Huawei, HiSilicon
R2-2210597	Discussion on Mobility Enhancements of IoT NTN	TURKCELL
R2-2210733	Discussion on Conditional Handover in IoT NTN	Ericsson
R2-2210735	Discussion on connected mode measurements	Ericsson
R2-2210861	Report of [AT119bis-e][118][IoT NTN Enh] Mobility enhancements	ZTE (rapporteur)

8.7.1: Organizational

TDoc	Title	Source
R2-2210766	R18 WI NR-NTN-enh work plan at RAN1, 2 and 3	THALES
R2-2211032	Response LS on LCS framework for Network verified UE location (NTN) (S2-2209589; contact: CATT)	SA2

8.7.2: Coverage Enhancements

TDoc	Title	Source
R2-2209389	Discussion on coverage enhancement in NR NTN	CAICT
R2-2209406	Discussion on NTN Coverage Enhancement	CATT
R2-2209508	Discussion on RAN overhead reduction for VoNR support in NTN	vivo
R2-2209709	Frame aggregation for coverage enhancement	Qualcomm Incorporated
R2-2209710	Protocol overhead reduction for coverage enhancement	Qualcomm Incorporated
R2-2209804	Consideration on NTN Coverage Enhancement	Apple
R2-2209969	Potential issues for Msg3 repetition in NTN	Lenovo
R2-2210033	Discussion on coverage enhancement for NR NTN	Xiaomi
R2-2210285	Consideration on coverage enhancements	ZTE Corporation, Sanechips
R2-2210460	Discussion on Coverage Enhancements for NR NTN	Hyundai Motor Company
R2-2210566	Discussion on the L2 header reduction in NTN	LG Electronics Inc.
R2-2210645	Discussion on Coverage Enhancements for NR NTN	Nokia, Nokia Shanghai Bell
R2-2210685	Discussion on RAN protocol overhead reduction	Huawei, HiSilicon
R2-2210758	R18 NR NTN Coverage enhancements	Ericsson
R2-2210842	[offline-103] Coverage enhancements	Qualcomm Incorporated

8.7.3: Network verified UE location

TDoc	Title	Source
R2-2209407	Discussion on UE Location Verification	CATT
R2-2209444	On Network Verified UE Location in NR NTN	MediaTek Inc.
R2-2209509	Discussion on Network verification of UE location in Rel-18 NR NTN	vivo
R2-2209579	Discussion on the technical issues of positioning methods in single-satellite NTN	Intel Corporation
R2-2209597	Summary of POST119-e [108] NW verified UE location (Thales)	THALES
R2-2209665	Discussion on the network verfied UE location	Huawei, HiSilicon
R2-2209793	Discussion on network verified UE location	Apple
R2-2209984	Discussion on UE location verify procedure	Spreadtrum Communications
R2-2210004	On NTN NW verified UE location aspects	Lenovo
R2-2210096	Discussion on network verified UE location	OPPO
R2-2210120	Discussion on network verified UE location	Xiaomi, CAICT
R2-2210242	Network Verified UE Location	Samsung R&D Institute UK
R2-2210286	Consideration on NW verified UE location	ZTE Corporation, Sanechips
R2-2210336	On network verified position	Nokia, Nokia Shanghai Bell
R2-2210443	Discussion on Network Verified UE Location	NTT DOCOMO INC.
R2-2210509	Considerations on UE Location Verification via Network	CMCC
R2-2210709	UE location verification in NTN	Deutsche Telekom, Huawei, HiSilicon
R2-2210757	R18 NR NTN Network verified UE location	Ericsson
R2-2210841	[AT119bis-e][102][R18 NR-NTN] NW verified UE location (Thales)	Thales
R2-2211044	Latency impact for NTN verified UE location	RAN2

8.7.4: NTN-TN and NTN-NTN mobility and service continuity enhancements

TDoc	Title	Source
R2-2209390	Discussion on NTN-NTN mobility	CAICT
R2-2209408	Discussion on NTN Mobility Enhancements	CATT
R2-2209445	Handover Enhancement in LEO NTN with Earth-moving Cells	MediaTek Inc.
R2-2209510	Discussion on mobility and service continuity enhancement	vivo
R2-2209577	Discussion on NTN handover enhancements	Intel Corporation
R2-2209578	Discussion on NTN cell reselection enhancements	Intel Corporation
R2-2209711	Signaling and congestion reduction in satellite switch	Qualcomm Incorporated
R2-2209733	Discussion of NTN-TN and NTN-NTN mobility	China Telecom
R2-2209752	Discussion on NTN-NTN CONNECTED mobility and service continuity enhancements	Transsion Holdings
R2-2209753	Discussion on NTN-TN IDLE and INACTIVATE mobility and service continuity enhancements	Transsion Holdings
R2-2209805	NTN Mobility Enhancement	Apple
R2-2209855	Discussion on RACH-less handover	ASUSTeK
R2-2209921	NTN handover enhancements	LG Electronics Inc.
R2-2209970	Further considerations on IDLE/INACTIVE mobility	Lenovo
R2-2209985	Some enhancements in NTN handover	Spreadtrum Communications
R2-2210045	Discussion on assistance information of cell reselection for NTN-TN mobility	ITRI
R2-2210090	Discussion on mobility enhancements for idle and inactive Ues	OPPO
R2-2210095	Discussion on NTN handover enhancements	OPPO
R2-2210121	Cell reselection enhancements and handover signaling overhead reduction	Xiaomi, CAICT
R2-2210159	Cell reselection enhancements	CMCC
R2-2210160	Mobility enhancements for connected mode	CMCC
R2-2210198	NR NTN connected mode mobility enhancement	NEC Telecom MODUS Ltd.
R2-2210217	NTN-TN mobility enhancements	Sony
R2-2210218	Signaling overhead reduction during NTN-NTN HOs	Sony
R2-2210338	NTN-NTN handover enhancement for RRC_CONNECTED UEs	NEC Telecom MODUS Ltd.
R2-2210353	Further view on Idle- and Connected-mode NTN mobility in Rel-18	Nokia, Nokia Shanghai Bell
R2-2210405	Discussion on NTN mobility enhancements	Huawei, HiSilicon
R2-2210438	RRC Idle/Inactive mobility enhancements	InterDigital
R2-2210439	RRC Connected mobility enhancements	InterDigital
R2-2210467	NTN mobility enhancements in connected mode	Samsung Research America
R2-2210468	NTN cell reselection enhancements	Samsung Research America
R2-2210479	Discussion on NTN mobility	Sharp
R2-2210589	Discussion on NTN-TN mobility and NTN-NTN mobility	ITL
R2-2210598	Discussion on mobility and service continuity enhancements for NR NTN	Turkcell, Deutsche Telekom
R2-2210629	Further discussion on NTN-TN and NTN-NTN mobility	NTT DOCOMO, INC.
R2-2210668	Discussion on NTN-NTN and NTN-TN mobility	ZTE corporation, Sanechips
R2-2210732	R18 NR NTN Mobility enhancements	Ericsson
R2-2210737	Discussion on idle mode aspects for NTN	LG Electronics Inc.
R2-2210767	Discussion on cell reselection enhancements for RRC_IDLE/INACTIVE UEs to reduce UE power consumption	PANASONIC
R2-2210769	Network-driven NTN-NTN Mobility Considerations	Lockheed Martin
R2-2210789	Discussion on NTN-NTN and NTN-TN mobility	ZTE Corporation, Sanechips, CAICT
R2-2210860	Report of [AT119bis-e][117][NR NTN Enh] cell reselection enhancements (Intel)	Intel Corporation
R2-2210862	Report from [AT119bis-e][119][NR NTN Enh] HO enhancements (Nokia)	Nokia, Nokia Shanghai Bell
R2-2210864	[Draft] LS on RACH-less HO in NTN	OPPO
R2-2210990	[offline-117] cell reselection enhancements	Intel
R2-2211017	LS on RACH-less handover in NTN	RAN2

8.8.1: Organizational

TDoc	Title	Source
R2-2209307	LS response to 3GPP RAN on Location Services for Drones (LI(21)P61035r1; contact: ETSI)	ETSI TC LI
R2-2210354	Uncrewed Aerial Vehicles in Rel-18 - updated workplan	Nokia, Nokia Shanghai Bell

8.8.2: Measurement reporting

TDoc	Title	Source
R2-2209368	Conditional HO in NR UAV	CATT
R2-2209418	Measurement Enhancement for UAV	OPPO
R2-2209446	Measurement and reporting enhancements	Qualcomm Incorporated
R2-2209532	Measurement reports	Ericsson
R2-2209582	UAV support for NR	Intel Corporation
R2-2209754	Considerations on Measurement Reports Enhancements	NEC Europe Ltd
R2-2209795	User consent on UAV location reporting	Apple
R2-2209934	Measurement enhancement for NR UAV	Lenovo
R2-2210161	Measurement Reporting for NR UAV	CMCC
R2-2210175	On measurement reporting enhancements for NR UAV	ZTE Corporation, Sanechips
R2-2210219	Considerations about UAV mobility and user consent	Sony
R2-2210355	On measurements and measurement reporting enhancements for Rel-18 UAVs	Nokia, Nokia Shanghai Bell
R2-2210356	On measurement reporting based on a configured number of cells triggering – evaluation results	Nokia, Nokia Shanghai Bell
R2-2210435	Discussion on measurement reporting for NR UAV	Sharp
R2-2210441	Measurement reporting for UAV	InterDigital
R2-2210489	Discussion on measurement reporting for NR UAV	Xiaomi
R2-2210504	Potential issues and enhancements for UAV measurements	Huawei, HiSilicon
R2-2210535	Consideration on flight path reporting of UAV for NR	DENSO CORPORATION
R2-2210601	Discussion on measurement reporting enhancement for NR UAV	vivo
R2-2210602	Discussion on flight path reporting for NR UAV	vivo
R2-2210623	Further discussion on NR support for UAV	NTT DOCOMO, INC.
R2-2210648	Measurement Report Enhancement	LG Electronics Finland
R2-2210652	Flight path information report enhancement	LG Electronics Finland
R2-2210675	Draft LS on Scaling the RRM Parameters for UAV UE	CMCC
R2-2210753	Discussion on flight path reporting and user consent for location reporting	Samsung
R2-2210885	[PRE119bis-e][UAV][301] Summary of UAV papers 8.8.2	Nokia, Nokia Shanghai Bell

8.8.3: Subscription-based aerial-UE identification

TDoc	Title	Source
R2-2209369	Subscription-based Aerial-UE Identification for NR	CATT
R2-2209419	Subscription-based aerial-UE identification	OPPO
R2-2209447	Enhancements for subscription-based aerial-UE identification	Qualcomm Incorporated
R2-2209755	Considerations on Subscription-based Identification for NR UAV	NEC Europe Ltd
R2-2210162	Subscription-based aerial-UE identification for NR UAV	CMCC
R2-2210176	Discussion on subscription based identification for NR UAV	ZTE Corporation, Sanechips
R2-2210505	Consideration on subscription-based UAV identification	Huawei, HiSilicon
R2-2210739	Discussion on subscription-based aerial-UE identification for NR UAV	Samsung Electronics Co., Ltd

8.8.4: UAV identification broadcast

TDoc	Title	Source
R2-2209531	On broadcasting UAV identification	Ericsson
R2-2209923	UAV Identity broadcast and Identification	Beijing Xiaomi Mobile Software
R2-2209935	Discussion on broadcasting remote id for UAV	Lenovo
R2-2210220	UAV identification broadcast	Sony
R2-2210781	OG0022_LS-MITRE-Engenuity Open Generation DAA input_PC5_DAA_RID_PRS OG0022 (contact: vivo)	MITRE Engenuity Open Generation 5G Consortium

8.9.1: Organizational

TDoc	Title	Source
R2-2209357	LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN (S2-2207518; contact: LGE)	SA2
R2-2210903	[AT119bis-e][415][Relay] LS on authorization for UE-to-UE relay (LG)	LG Electronics Inc.

8.9.2: UE-to-UE relay

TDoc	Title	Source
R2-2209370	Discussion on U2U Relay Discovery and (Re)selection	CATT
R2-2209499	Discussion on NR sidelink UE to UE relay	OPPO
R2-2209518	Relay discovery and (re)selection for UE-to-UE relay	MediaTek Inc.
R2-2209519	Connection management and procedures for L2 UE-to-UE relay	MediaTek Inc.
R2-2209583	Discovery and reselection with UE-to-UE relaying	Intel Corporation
R2-2209619	Discussion on U2U relay communication	ZTE, Sanechips
R2-2209731	Discussion on UE-to-UE relay	China Telecom
R2-2209769	Discussion on U2U Relay Discovery and Relay (Re)-selection	Apple
R2-2209819	Discussion on the common L2/L3 parts for U2U relaying	vivo
R2-2209839	Discovery and Relay (re-)selection for UE-to-UE relay	Qualcomm Incorporated
R2-2209922	Further considerations on U2U relay discovery and relay selection	Beijing Xiaomi Mobile Software
R2-2209972	Discussion on relay discovery and (re)selection for U2U relay	Spreadtrum Communications
R2-2210048	U2U sidelink relay	Samsung R&D Institute UK
R2-2210136	Discussion on U2U relay	CMCC
R2-2210221	UE-to-UE relay (re)selection	Sony
R2-2210232	Basic aspects for U2U Relay work	Lenovo
R2-2210247	Design aspects of relay selection and reselection for U2U relay	Ericsson
R2-2210248	Discussion on U2U coverage scenarios and RRC states	Ericsson, vivo, InterDigital Inc
R2-2210251	Discussion on SL UE-to-UE Relay Discovery and (Re-)Selection	Fraunhofer IIS, Fraunhofer HHI
R2-2210263	Discovery and Relay Selection for UE-to-UE Relays	InterDigital
R2-2210276	Initial considerations for U2U relay discovery and (re)selection	Kyocera
R2-2210277	Initial considerations for U2U L2 relay CP operations	Kyocera
R2-2210339	On L2 and L3 U2U relays	Nokia, Nokia Shanghai Bell
R2-2210475	UE-to-UE relay discovery and (re)selection	Sharp
R2-2210498	Discussion on UE-to-UE relay	Huawei, HiSilicon
R2-2210580	Relay selection and connection establishment	LG Electronics France
R2-2210893	Summary of AI 8.9.2 – UE to UE Relay (InterDigital)	InterDigital
R2-2210914	Summary of \t[AT119bis-e][427][Relay] Remaining proposals on UE-to-UE relay (InterDigital)	InterDigital
R2-2210981	Summary of \t[AT119bis-e][427][Relay] Remaining proposals on UE-to-UE relay (InterDigital)	InterDigital

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

TDoc	Title	Source
R2-2209371	Consideration on Service Continuity Enhancements for L2 U2N Relay	CATT
R2-2209460	Considerations on Service Continuity Enhancement	NEC Corporation
R2-2209498	Discussion on further enhancement of service continuity	OPPO
R2-2209520	Inter-gNB path switch to Relay UE in RRC_Idle, RRC_Inactive	MediaTek Inc.
R2-2209584	Service continuity enhancements for L2 U2N relay	Intel Corporation
R2-2209642	Inter-gNB Aspects of Service Continuity for Layer-2 UE-to-Network Relays	Ericsson España S.A.
R2-2209730	Service continuity enhancements for L2 U2N relay	China Telecom
R2-2209770	Discussion on Service continuity enhancement of L2 U2N relay	Apple
R2-2209820	On service continuity enhancement for L2 U2N relay	vivo
R2-2209841	Service continuity for UE-to-Network relay	Qualcomm Incorporated
R2-2209882	Discussion on service continuity enhancement	Xiaomi
R2-2209901	Service continuity enhancement for L2 U2N relay	ZTE, Sanechips
R2-2209943	Service continuity in L2 U2N relay case	Lenovo
R2-2209975	Service continuity enhancements support for L2 U2N relay	Spreadtrum Communications
R2-2210014	Service continuity enhancements for L2 U2N relay	Samsung
R2-2210101	Discussion on service continuity enhancement for Inter-gNB path switching of L2 U2N relay	Nokia, Nokia Shanghai Bell
R2-2210102	Discussion on service continuity enhancement for Inter-gNB path switching via relay UE in RRC_IDLE/INACTIVE state	Nokia, Nokia Shanghai Bell
R2-2210112	Discussion on Service Continuity	Huawei, HiSilicon
R2-2210137	Service continuity on U2N relay	CMCC
R2-2210223	Service continuity enhancements for UE sidelink relay	Sony
R2-2210264	Open Issues on Service Continuity for Rel18	InterDigital
R2-2210278	L2 U2N inter-gNB service continuity	Kyocera
R2-2210442	Open Issues on Service Continuity for Rel18	InterDigital France R&D, SAS
R2-2210474	Service Continuity Enhancements for Layer-2 U2N Relay	Sharp
R2-2210578	Service continuity enhancements for L2 U2N relay	LG Electronics France
R2-2210782	Summary of AI 8.9.3, Service Continuity Enhancements	Ericsson

8.9.4: Multi-path relaying

TDoc	Title	Source
R2-2209372	Discussion on Multi-path for Scenario 1	CATT
R2-2209373	Discussion on the Details of Scenario 2	CATT
R2-2209375	Discussion on multi-path Relay	OPPO
R2-2209461	Considerations on Multipath of Sidelink Relay	NEC Corporation
R2-2209585	Discussion on Multi-path Relaying	Intel Corporation
R2-2209617	Further discussion on the multi-path relaying	ZTE, Sanechips
R2-2209618	Design consideration on the UE aggregation	ZTE, Sanechips
R2-2209681	Multipath support for remote UE	MediaTek Inc.
R2-2209682	Multipath Relaying for Scenario-1 and Scenario-2	Ericsson España S.A.
R2-2209732	Discussion on RLF handling for multi-path relaying	China Telecom
R2-2209749	Support of Multi-path Relaying	Nokia, Nokia Shanghai Bell
R2-2209771	Discussion on multi-path relaying support	Apple
R2-2209821	Multi-path UE aggregation on PC5 and Ideal-link	vivo
R2-2209840	Discussion on multi-path relay for Scenario 1 and Scenario 2	Qualcomm Incorporated
R2-2209881	Discussion on multi-path	Xiaomi
R2-2209944	Discussion on Multi-path relaying	Lenovo
R2-2209945	Second path establishment for Multi-Path	Lenovo
R2-2209976	Discussion on multi-path relaying	Spreadtrum Communications
R2-2210027	Report of [Post119-e][408][Relay] Path operations in multi-path relaying	LG Electronics France
R2-2210031	Multi-path relaying for NR sidelink relay enhancements	LG Electronics France
R2-2210063	Discussion on primary path for CP in sidelink relay enhancement	Samsung
R2-2210064	Discussion on key issues for multipath in sidelink relay enhancement	Samsung
R2-2210138	Primary path for CP in multi-path	CMCC
R2-2210139	Consideration on UE aggregation	CMCC
R2-2210224	Multi-path relaying discussion	Sony
R2-2210265	Architecture Assumptions for Multi-path	InterDigital
R2-2210266	SRB and DRB Configurations for Multi-path	InterDigital
R2-2210425	SRB and DRB Configurations for Multi-path	InterDigital France R&D, SAS
R2-2210476	discussion on multi-path bearer	Sharp
R2-2210477	resource allocation for multi-path relaying	Sharp
R2-2210497	Discussion on Rel-18 multi-path via SL relay and UE aggregation	Huawei, HiSilicon
R2-2210780	Discussion on multi-path Relay	OPPO
R2-2210912	Report of [AT119bis-e][425][Relay] Adaptation layer for scenario 2 (LG)	LG Electronics Inc.
R2-2210913	Summary of [AT119bis-e][426][Relay] Control plane aspects for multi-path (OPPO)	OPPO

8.9.5: DRX

TDoc	Title	Source
R2-2209376	Discussion on SL-DRX for Relay	OPPO
R2-2209774	Discussion on SL DRX for L2 Relay	Apple
R2-2209822	Discussion on SL DRX for L2 U2N Remote UE	vivo
R2-2209842	SL DRX for L2 U2N relay	Qualcomm Incorporated
R2-2209883	Discussion on SL DRX in U2N relay	Xiaomi
R2-2210222	Discussions on Sidelink Relay DRX	Sony
R2-2210499	On sidelink DRX for L2 U2N relay	Huawei, HiSilicon
R2-2210579	SL DRX for L2 U2N relay	LG Electronics France

8.11.1: Organizational

TDoc	Title	Source
R2-2209356	LS on FS_5MBS_Ph2 progress (S2-2207470; contact: Huawei)	SA2
R2-2209664	Consideration on replying to the SA2 LS on MBS progress	Huawei, HiSilicon
R2-2210878	Report of [AT119bis-e][604][eMBS] Reply LS to SA2 (Huawei)	Huawei, HiSilicon
R2-2210879	Reply LS on FS_5MBS_Ph2 progress	RAN2
R2-2210882	Reply LS on FS_5MBS_Ph2 progress	RAN2

8.11.2: Multicast reception in RRC_INACTIVE

TDoc	Title	Source
R2-2209412	Supporting Multicast Reception in RRC_INACTIVE	vivo
R2-2209449	Multicast reception by UEs in RRC_INACTIVE state	Qualcomm Incorporated
R2-2209458	Discussion on multicast reception in RRC_INACTIVE state	TD Tech Ltd, Chengdu TD Tech
R2-2209513	Discussion on multicast reception in RRC_INACTIVE state	OPPO
R2-2209514	LS on multicast reception in RRC_INACTIVE	OPPO
R2-2209533	MBS pre-configuration and PTM configuration in RRC_INACTIVE state	CANON Research Centre France
R2-2209587	Multicast Reception in RRC_INACTIVE	Samsung
R2-2209613	Session state change for UEs receiving Multicast in RRC_INACTIVE state	TCL Communication Ltd.
R2-2209614	PTM configuration for UEs receiving Multicast in RRC_INACTIVE state	TCL Communication Ltd.
R2-2209623	Discussion on multicast reception in RRC_INACTIVE	NEC Europe Ltd
R2-2209662	Multicast reception for RRC_INACTIVE	Huawei, HiSilicon
R2-2209744	Multicast reception in RRC_INACTIVE	ZTE, Sanechips
R2-2209806	Multicast Reception in INACTIVE State	Apple
R2-2209876	Discussion on multicast reception in RRC INACTIVE	MediaTek inc.
R2-2209919	Multicast reception in RRC_INACTIVE	LG Electronics Inc.
R2-2209946	PTM configuration for multicast reception in RRC_INACTIVE	Lenovo
R2-2209947	Mobility and state transition for multicast reception in RRC_INACTIVE	Lenovo
R2-2209988	Discussion on Multicast Reception in RRC_INACTIVE	Spreadtrum Communications
R2-2210026	Considerations on security issues for multicast MCCH	Beijing Xiaomi Software Tech
R2-2210066	Discussion on multicast reception in RRC_INACTIVE	CATT, CBN
R2-2210068	Report of [Post119-e][610][eMBS] PTM configuration for INACTIVE (CATT)	CATT
R2-2210114	Discussion on supporting group scheduling for RRC_INACTIVE UEs	FGI
R2-2210132	Multicast reception in RRC_INACTIVE	Nokia, Nokia Shanghai Bell
R2-2210146	Discussion on multicast reception in RRC_INACTIVE	CMCC
R2-2210384	Multicast reception in RRC_INACTIVE	Intel Corporation
R2-2210423	PTM Configuration for RRC_INACTIVE	Sharp
R2-2210424	Paging message for Multicast session received in RRC_INACTIVE	Sharp
R2-2210428	Details of multicast reception in RRC INACTIVE	Kyocera
R2-2210453	Discussion on Mobility during Multicast Reception in RRC Inactive State	TCL Communication Ltd.
R2-2210458	Discussion on RAN based Notification Area for Multicast Mobility in Inactive State	TCL Communication Ltd.
R2-2210557	Provision of reliable MBS in RRC_INACTIVE	InterDigital, Inc.
R2-2210715	Service availability for mission critical UEs during RAN congestion	Ericsson
R2-2210880	Report of [AT119bis-e][605][eMBS] PTM configuration for INACTIVE (CATT)	CATT

8.11.3: Shared processing for MBS broadcast and Unicast reception

TDoc	Title	Source
R2-2209413	Supporting Shared Processing for MBS Broadcast and Unicast	vivo
R2-2209448	Shared processing for MBS broadcast and unicast reception	Qualcomm Incorporated
R2-2209459	CFR configuration for multicast reception in RRC_INACTIVE state	TD Tech Ltd, Chengdu TD Tech
R2-2209624	Discussion on shared process for unicast and broadcast reception	NEC Europe Ltd
R2-2209663	Discussion on shared processing for MBS broadcast and Unicast reception	Huawei, CBN, HiSilicon
R2-2209745	On signaling framework for shared processing	ZTE, Sanechips
R2-2209807	Sharing processing of MBS broadcast and unicast reception	Apple
R2-2209867	Shared Processing for MBS broadcast and unicast reception	Nokia, Nokia Shanghai Bell
R2-2209877	Discussion on broadcast coexistence and signaling enhancement	MediaTek inc.
R2-2209920	Shared processing for broadcast and unicast	LG Electronics Inc.
R2-2209989	Discussion on shared processing for MBS broadcast and Unicast Reception	Spreadtrum Communications
R2-2210054	Discussion on shared processing for MBS broadcast and unicast reception	Xiaomi
R2-2210067	Discussions on shared processing for MBS broadcast and unicast reception	CATT, CBN
R2-2210147	Discussion on shared processing for broadcast and unicast reception	CMCC
R2-2210385	Shared processing for simultaneous MBS broadcast and Unicast reception	Intel Corporation
R2-2210427	Shared processing for inter-PLMN MBS broadcast reception	Kyocera
R2-2210610	Uu Signalling Enhancements for MBS	Samsung
R2-2210716	MBS broadcast and unicast reception with shared resources	Ericsson

8.12.1: Organizational

TDoc	Title	Source
R2-2209350	LS on FS_VMR solutions review (S2-2207070; contact: Qualcomm)	SA2
R2-2209615	Discussion on LS on VMR solutions from SA2	ZTE, Sanechips
R2-2209702	Workplan for Rel-18 mobile IAB	Qualcomm Inc. (Rapporteur)
R2-2211022	[DRAFT] Reply LS on FS_VMR solutions review	Qualcomm
R2-2211056	[AT119bis-e][020][eIAB] Reply LS on FS_VMR solutions review	Qualcomm (Rapporteur)
R2-2211062	Reply LS on FS_VMR solutions review	RAN2

8.12.2: Mobility Enhancements

TDoc	Title	Source
R2-2209522	Mobile IAB mobility enhancement	Huawei, HiSilicon
R2-2209616	Discussion on mobility enhancement for mobile IAB	ZTE, Sanechips
R2-2209640	Mobility Enhancement of mobile IAB-node and served UEs	Intel Corporation
R2-2209699	Mobility enhancements for group mobility	AT&T
R2-2209703	Enhancements for IAB-node mobility	Qualcomm Inc.
R2-2209763	Mobility enhancement in mobile IAB	Apple
R2-2209953	Mobility enhancements for mobile IAB-node and its served UE	Lenovo
R2-2209997	Discussion on mobility enhancements for mobile IAB	CANON Research Centre France
R2-2210208	Mobility enhancement for mobile IAB	Sony
R2-2210272	RAN impacts due to IAB-node mobility	Nokia, Nokia Shanghai Bell
R2-2210327	Mobility enhancements for mIAB node	Ericsson
R2-2210387	Discussion on mobile IAB open issues	vivo
R2-2210429	Mobility enhancements for mobile IAB	Kyocera
R2-2210447	Scenarios for consideration in mIAB cell selection and reselection	Beijing Xiaomi Mobile Software
R2-2210522	Discussion on the enhancement of IAB node mobility	Samsung R&D Institute UK
R2-2210548	IAB node mobility state and UE measurements	InterDigital, Inc.
R2-2210562	Handover and cell reselection enhancements for on-board UE mobility	LG Electronics
R2-2210577	Dynamic PCI change for mobile IAB	InterDigital, Inc.
R2-2210778	RAN impacts due to IAB-node mobility	Nokia, Nokia Shanghai Bell
R2-2211021	Report of [AT119bis-e][021][eIAB] Enhancements for Idle Inactive UE	Huawei, HiSilicon

8.12.3: Other

TDoc	Title	Source
R2-2209523	Full migration, interference mitigation and SA2 LS related issues	Huawei, HiSilicon
R2-2209641	Discussion on Migration and PCI handling of mobile IAB-node	Intel Corporation
R2-2209704	Other enhancements for mobile IAB	Qualcomm Inc.
R2-2209764	Inter-donor full migration and mitigation of interference in mobile IAB	Apple
R2-2209954	Discussion on inter-donor full migration of mobile IAB	Lenovo
R2-2210049	mIAB - other key issues	Samsung R&D Institute UK
R2-2210109	Discussion on UE handover during IAB-node mobility	Fujitsu
R2-2210209	PCI collision in mobile IAB	Sony
R2-2210273	Interference mitigation	Nokia, Nokia Shanghai Bell
R2-2210328	General aspects on mobile IAB support	Ericsson
R2-2210404	Consideration on PCI collisions for Mobile IAB	Sharp
R2-2210430	PCI and RACH collisions on mobile IAB	Kyocera
R2-2210591	Consideration on full migration, PCI and RACH configuration collision	LG Electronics Inc.
R2-2211054	[AT119bis-e][022][eIAB] Dual Cells LS (AT&T)	AT&T (Rapporteur of the offline)

8.13.1: Organizational

TDoc	Title	Source
R2-2209324	LS on the scope for the support of SON/MDT enhancements (R3-225238; contact: Nokia)	RAN3
R2-2209325	LS on NR-U support for MRO (R3-225241; contact: Ericsson)	RAN3
R2-2211036	Progress and open issues for NPN enhancements in Rel-18 (S2-2209860; contact: Ericsson)	SA2

8.13.2: MRO for inter-system handover for voice fallback

TDoc	Title	Source
R2-2209569	Data Collection for MRO Related Enhancements	CATT
R2-2209728	Further discussion on MRO of inter-system HO voice fallback	OPPO
R2-2209827	MRO for inter-system handover for voice fallback	Samsung R&D Institute India
R2-2209864	Discussion on the inter-system handover for voice fallback	Huawei, HiSilicon
R2-2209955	MRO for inter-system handover for voice fallback	Lenovo
R2-2210037	Discussion on inter-system handover voice fallback	Xiaomi
R2-2210183	MRO for inter-system handover for voice fallback	Ericsson
R2-2210287	Consideration on MRO for inter-system handover for voice fallback	ZTE Corporation, Sanechips
R2-2210300	Data collection for MRO for inter-system handover for voice fallback	Qualcomm Incorporated
R2-2210510	MRO for inter-system handover for voice fallback	CMCC
R2-2210632	Further discussion on MRO enhancement for inter-system handover for voice fallback	NTT DOCOMO, INC.
R2-2210794	Summary of AI 8.13.2 on MRO for inter-system handover for voice fallback (ZTE)	ZTE Corporation, Sanechips

8.13.3: MDT override

TDoc	Title	Source
R2-2209570	Discussion on Inter-RAT Signaling Based Logged MDT Override Protection	CATT
R2-2209808	Inter-RAT signalling based logged MDT override protection	Samsung R&D Institute India
R2-2209896	Discussion on the inter-system signalling based MDT override protection	Huawei, HiSilicon
R2-2210028	Considerations on the signaling based logged MDT override protection for E-UTRAN	Beijing Xiaomi Software Tech
R2-2210182	MDT enhancements	Ericsson
R2-2210267	Signalling based Logged MDT override protection	Nokia, Nokia Shanghai Bell
R2-2210288	Consideration on MDT override issues	ZTE Corporation, Sanechips
R2-2210301	Signalling based logged MDT override protection	Qualcomm Incorporated
R2-2210787	Summary on 8.13.3 ‘MDT override	Nokia
R2-2210797	Summary on 8.13.3 ‘MDT override	Nokia
R2-2210996	Report on [AT119bis-e][801][R18 SON/MDT] MDT override solution direction (Nokia)?	Nokia

8.13.4: SHR and SPCR

TDoc	Title	Source
R2-2209566	Discussion on SON enhancement for SPCR	vivo
R2-2209571	Discussion on Miscellaneous MRO Enhancements	CATT
R2-2209826	SON/MDT enhancements for SHR and SPCR	Samsung R&D Institute India
R2-2209865	Discussion on SHR and SPCR	Huawei, HiSilicon
R2-2209956	Successful Handover Report for inter-RAT HO	Lenovo
R2-2209957	SON enhancements for successful PSCell change report	Lenovo
R2-2209998	Discussion on successful PSCell change report	NEC
R2-2210038	Discussion on SHR and SPCR	Xiaomi
R2-2210184	SPR and SHR enhancements	Ericsson
R2-2210268	Successful PSCell Change report	Nokia, Nokia Shanghai Bell
R2-2210289	Consideration on SHR and SPCR	ZTE Corporation, Sanechips
R2-2210302	Discussion on SHR for inter-RAT handover and successful PSCell change reporting	Qualcomm Incorporated
R2-2210521	Discussion on successful PSCell change report	SHARP Corporation
R2-2210624	Discussion on SPCR	NTT DOCOMO, INC.
R2-2210798	Pre-meeting summary of 8.13.4 SHR and SPCR (Ericsson)	Ericsson (Summary rapporteur)
R2-2210986	[AT119bis-e][802][R18 SON/MDT] SHR and SPR (Ericsson)	Ericsson (Rapporteur of the offline)

8.13.5: SON for NR-U

TDoc	Title	Source
R2-2209573	NR-U enhancements for SON	CATT
R2-2209765	SON enhancements for NR-U	Apple
R2-2209824	SON/MDT enhancements for NR-U	Samsung R&D Institute India
R2-2209897	Discussion on SON for NR-U	Huawei, HiSilicon
R2-2209958	Discussion on MRO for NR-U	Lenovo
R2-2210039	Discussion on SON for NR-U	Xiaomi
R2-2210148	SONMDT enhancement for NR-U	CMCC
R2-2210180	Enhancements of SON reports for NR-U	Ericsson
R2-2210270	MRO and MDT enhancements for NR-U	Nokia, Nokia Shanghai Bell
R2-2210290	Consideration on NR-U related SON	ZTE Corporation, Sanechips
R2-2210799	Pre-meeting summary of 8.13.5 SON for NR-U (Ericsson)	Ericsson (Summary rapporteur)
R2-2210987	[AT119bis-e][803][R18 SON/MDT] SON of NR-U (Ericsson)	Ericsson (Rapporteur of the offline)
R2-2210998	[AT119bis-e][803][R18 SON/MDT] SON of NR-U (Ericsson)	Ericsson (Rapporteur of the offline)
R2-2211063	LS on Possibility on LBT-FailureRecoveryConfig	RAN2

8.13.6: RACH enhancement

TDoc	Title	Source
R2-2209567	Discussion on RACH report enhancement for RACH partitioning	vivo
R2-2209572	RACH enhancement for SON	CATT
R2-2209766	SON enhancements for RACH partitioning	Apple
R2-2209825	SON/MDT Enhancements for RACH	Samsung R&D Institute India
R2-2209898	Discussion on RACH enhancement	Huawei, HiSilicon
R2-2209986	RACH report enhancements for RACH partition	Spreadtrum Communications
R2-2209999	Discussion on RACH enhancements	NEC
R2-2210030	Discussion on the SON/MDT enhancement for RACH report	Beijing Xiaomi Software Tech
R2-2210179	RACH report enhancements	Ericsson
R2-2210271	RACH report related enhancements	Nokia, Nokia Shanghai Bell
R2-2210291	Consideration on RACH enhancements	ZTE Corporation, Sanechips
R2-2210511	SONMDT enhancement for RACH Enhancement.	CMCC
R2-2210574	Discussion on RACH partitioning	China Telecom Corporation Ltd.
R2-2210793	Pre-meeting summary of 8.13.6	Huawei

8.13.7: SON/MDT enhancements for Non-Public Networks

TDoc	Title	Source
R2-2209568	Discussion on SON enhancement for NPN	vivo
R2-2209574	SON and MDT Enhancement for NPN	CATT
R2-2209823	SON/MDT enhancements for NPN	Samsung R&D Institute India
R2-2209899	Discussion on SON and MDT enhancements for NPN	Huawei, HiSilicon
R2-2210032	Discussion on the SON/MDT enhancement for NPN	Beijing Xiaomi Software Tech
R2-2210104	Impact of SNPN on MDT and MRO	Nokia, Nokia Shanghai Bell
R2-2210149	SONMDT enhancement for NPN	CMCC
R2-2210181	SON support for NPN	Ericsson
R2-2210292	Consideration on SON-MDT support for NPN	ZTE Corporation, Sanechips
R2-2210303	Discussion on SON/MDT enhancements for Non-Public Networks	Qualcomm Incorporated
R2-2210795	Pre-meeting summary of 8.13.7	CATT
R2-2210800	Pre-meeting summary of 8.13.7	CATT

8.13.8: Other

TDoc	Title	Source
R2-2209726	Discussion of SON on MR-DC CPAC	OPPO
R2-2209959	MRO for fast MCG link recovery and SCG failure	Lenovo
R2-2209960	SON enhancements for CPAC	Lenovo
R2-2210269	MRO for Fast MCG Recovery and MR-DC CPAC	Nokia, Nokia Shanghai Bell
R2-2210304	Discussion on SONMDT enhancements for MR-DC CPAC and fast MCG Recovery	Qualcomm Incorporated
R2-2210426	SON on fast MCG recovery	OPPO
R2-2210512	SON/MDT enhancement for fast MCG recovery	CMCC
R2-2210513	SON MDT enhancement for MR-DC CPAC	CMCC
R2-2210517	Discussion on failure information for CPAC	SHARP Corporation
R2-2210523	Discussion on RLF report in fast MCG recovery	SHARP Corporation
R2-2210626	Discussion on CPAC failure report	NTT DOCOMO, INC.
R2-2210630	Discussion on MRO for MR-DC SCG failure scenario and fast MCG recovery failure	NTT DOCOMO, INC.

8.14.1: Organizational

TDoc	Title	Source
R2-2209323	LS to SA4 on Rel-18 enhancement of NR QoE (R3-225227; contact: Huawei)	RAN3
R2-2209330	LS to RAN2 on RAN3 agreement of QoE reporting in NR-DC (R3-225256; contact: China Unicom)	RAN3
R2-2210748	Revised work plan for Rel-18 NR QoE Enhancement	China Unicom

8.14.2: QoE measurements in RRC_IDLE INACTIVE

TDoc	Title	Source
R2-2209843	QoE collection for IDLE and Inactive state	Qualcomm Incorporated
R2-2210307	Support of QoE in NR-DC	Ericsson
R2-2210754	Discussion on QoE measurements in RRC_IDLE and INACTIVE states	China Unicom

8.14.3: Rel-17 leftover topics for QoE

TDoc	Title	Source
R2-2209784	Views on QoE Reporting for Overload Scenarios	Apple
R2-2209830	Discussion on Rel-17 leftover features for QoE	Lenovo
R2-2209833	Discussion on Rel-17 leftover issues for QoE	ZTE Corporation, Sanechips
R2-2209837	Event-based RAN visible QoE report	Samsung
R2-2209845	Discussion on RAN visible QoE trigger event	Qualcomm Incorporated
R2-2210015	Discussion on Rel-17 leftover issues for QoE	CATT
R2-2210204	Support of R17 left-over features	Huawei, HiSilicon
R2-2210275	QMC enhancements for RAN overload	Nokia, Nokia Shanghai Bell
R2-2210306	Discussion on rel-17 leftovers	Ericsson
R2-2210573	Discussion on QoE Rel-17 leftover issues	China Telecom Corporation Ltd.
R2-2210813	Report of [AT119bis-e][204][QoE] Summary of Rel-17 leftovers for QoE (China Telecom)	China Telecom

8.14.4: Support of QoE measurements for NR-DC

TDoc	Title	Source
R2-2209785	Support of QoE in NR-DC	Apple
R2-2209831	Discussion on support of QoE measurements for NR-DC	Lenovo
R2-2209832	Discussion on Rel-18 QoE measurement for NR-DC	ZTE Corporation, Sanechips
R2-2209838	Support of QoE measurements for NR-DC	Samsung
R2-2209844	RAN2 issues to support QoE collection in NR-DC	Qualcomm Incorporated
R2-2210016	Discussion on QoE measurement in NR-DC	CATT
R2-2210205	Discussion on QoE measurements in NR-DC	Huawei, HiSilicon
R2-2210274	QMC support on NR-DC	Nokia, Nokia Shanghai Bell
R2-2210752	Discussion on QoE configuration and reporting for NR-DC	China Unicom

8.15.1: Organizational

TDoc	Title	Source
R2-2209374	Work plan of R18 SL-Evo	OPPO

8.15.2: SL-U: RAN2 scope

TDoc	Title	Source
R2-2209385	Discussion on CAPC definition in SL-U	OPPO
R2-2209386	Discussion on LBT impact in SL-U	OPPO
R2-2209464	Discussion on RAN2 aspects for SL-U	vivo
R2-2209465	On CAPC in SL-U	vivo
R2-2209521	Channel Access Priority Classes for SL-U	MediaTek Inc.
R2-2209535	Discussion on LBT for SL-U	Huawei, HiSilicon
R2-2209598	Discussion on CAPC for SL-U	Huawei, HiSilicon
R2-2209612	Discussion on RAN2 aspects in SL-U	LG Electronics France
R2-2209678	Discussion on RAN2 scope of SL-U	ZTE Corporation, Sanechips
R2-2209679	Discussion on CAPC definition and consistent sidelink LBT failure handling	ZTE Corporation, Sanechips
R2-2209737	On CAPC for SL-U	Intel Corporation
R2-2209738	MAC related aspects for SL-U	Intel Corporation
R2-2209742	Consideration on CAPC for SL-U	CATT
R2-2209743	Discussion on the SL-U Scenarios and LBT	CATT
R2-2209761	Control plane aspects of sidelink on unlicensed spectrum (SL-U)	Apple
R2-2209762	User plane aspects of sidelink on unlicensed spectrum (SL-U)	Apple
R2-2209891	Discussion on channel access priority for NR SL-U	Lenovo
R2-2209936	Discussion on LBT impact to MAC for NR SL-U	Lenovo
R2-2209973	Consideration on channel access priority in SL-U	Spreadtrum Communications
R2-2209996	LBT failure handling for SL-U	Spreadtrum Communications
R2-2210002	Discussion on consistent LBT failure for SL-U	NEC
R2-2210249	Aspects of channel access mechanisms	Ericsson
R2-2210250	CAPC table and MAC multiplex rules	Ericsson
R2-2210256	CAPC and COT sharing for SL Unlicensed	InterDigital
R2-2210257	LBT Impacts to the MAC Layer	InterDigital
R2-2210280	Discussion on sidelink CAPC	Qualcomm India Pvt Ltd
R2-2210281	Discussion on sidelink LBT impact	Qualcomm India Pvt Ltd
R2-2210342	Considerations on resource allocation for SL-U	Nokia, Nokia Shanghai Bell
R2-2210357	On channel access priority class and HARQ feedback	Nokia, Nokia Shanghai Bell
R2-2210366	Discussion on RAN2 Aspects in SL-U	Fraunhofer IIS, Fraunhofer HHI
R2-2210379	Discussion on channel access for sidelink operation on unlicensed spectrum	Xiaomi
R2-2210380	Discussion on LBT for sidelink operation on unlicensed spectrum	Xiaomi
R2-2210486	HARQ-based Sidelink RLF due to LBT failure	MediaTek Inc.
R2-2210552	SL CAPC	Samsung Research America
R2-2210553	SL resource allocation	Samsung Research America
R2-2210588	Discussion on sidelink un-licensed	ITL
R2-2210934	Summary of [AT119bis-e][503][V2X/SL] CAPC (OPPO)	OPPO
R2-2210935	Summary of [AT119bis-e][504][V2X/SL] Consistent SL LBT failure (vivo)	vivo (Rapporteur)
R2-2210936	LS on SL LBT failure indication and consistent SL LBT failure	RAN2

8.16.1: Organizational

TDoc	Title	Source
R2-2210677	RAN2 Work Plan for Rel-18 SI on AI/ML for NR air interface	Ericsson, Qualcomm Inc.

8.16.2: AIML methods

TDoc	Title	Source
R2-2209420	Work Split Consideration for Air Interface AIML	OPPO
R2-2209421	Life Cycle Management for Air Interface AIML	OPPO
R2-2209564	Discussion on general aspects of AIML methods	vivo
R2-2209595	Discussion on RAN2 Aspects of AI/ML over Air Interface	MediaTek Inc.
R2-2209605	General framework of AI/ML over air interface	Intel Corporation
R2-2209700	Protocol aspects of AI/ML framework for NR air interface	AT&T
R2-2209720	Consideration on General Aspects of AIML for NR Air-interface	CATT
R2-2209760	Discussion on RAN2 aspects of AI/ML for air interface	Apple
R2-2209884	Discussion on AIML for NR air interface	Xiaomi
R2-2209905	AI/ML Model Management	Samsung R&D Institute UK
R2-2209906	AI/ML Capability Indication	Samsung R&D Institute UK
R2-2209951	General issues on AI for air interface	Lenovo
R2-2209995	Discussion on AMML methods	Spreadtrum Communications
R2-2210157	Discussion on AIML methods for NR air interface	CMCC
R2-2210228	Considerations about AI/ML framework	Sony
R2-2210233	On the impact of AI/ML methods	Nokia, Nokia Shanghai Bell
R2-2210293	Discussion on AI/ML methods	Qualcomm Incorporated
R2-2210340	Discussion on common framework and RAN2 impacts	Huawei, HiSilicon
R2-2210402	Framework of AI/ML for air interface	NEC
R2-2210436	Discussion on AIML methods	InterDigital, Inc.
R2-2210461	Discussion on AI/ML Model Management Framework for Positioning Enhancement Use-case	TCL Communication Ltd.
R2-2210520	Discussion on AIML Methods	Rakuten Mobile, Inc
R2-2210564	Aspect of ML model provisioning between UE and network	LG Electronics
R2-2210614	Initial Discussion on General Aspect of AI/ML study	ZTE Corporation,Sanechips
R2-2210678	General aspects for AI/ML for NR air interface	Ericsson
R2-2210774	Life Cycle Management for Air Interface AIML	OPPO

8.16.3: Use case specific aspects

TDoc	Title	Source
R2-2209565	Consideration of use case specific aspects	vivo
R2-2209721	Consideration on the Use Case Specific AIML for NR Air-interface	CATT
R2-2209952	Discussion on AI for air interface use cases	Lenovo
R2-2210123	Discussion on AI/ML for positioning accuracy enhancement	Xiaomi
R2-2210158	Discussion on use case specific aspects for AIML for NR air interface	CMCC
R2-2210234	Potential impacts for use case specific aspects	Nokia, Nokia Shanghai Bell
R2-2210299	Discussion on use case specific aspects	Qualcomm Incorporated
R2-2210341	Discussion on use case specific aspects	Huawei, HiSilicon
R2-2210487	Discussion on AI/ML Based Positioning Methods Selection	TCL Communication Ltd.
R2-2210615	Initial Discussion on Use Cases for AI/ML Study	ZTE Corporation,Sanechips
R2-2210654	Use case specific RAN2 impact	LG Electronics Finland
R2-2210679	Use cases for AI/ML for NR air interface	Ericsson

8.17.1: Organizational

TDoc	Title	Source
R2-2210388	Work planning of R18 MUSIM	vivo

8.17.2: Temporary capability restriction for MUSIM

TDoc	Title	Source
R2-2210393	Support of Dual-RX/Dual-TX MUSIM UE	Ericsson

8.17.2.1: Scenarios

TDoc	Title	Source
R2-2209391	Consideration on the Dual (Tx/Rx) MUSIM Scenarios	ZTE Corporation, Sanechips
R2-2209422	Scenarios Clarification for R18 MUSIM	OPPO
R2-2209576	Scenarios for Dual-Active MUSIM	Qualcomm Incorporated
R2-2209637	Considerations on Rel-18 MUSIM	Intel Corporation
R2-2209734	Discussion of temporary UE capability switching for MUSIM	China Telecom
R2-2210000	Scenarios of Temporary capability restriction for MUSIM	NEC
R2-2210017	Applicable scenarios for R18 MUSIM WI	Huawei, HiSilicon
R2-2210059	Discussion on prioritized scenarios for temporary UE capability restriction	Xiaomi
R2-2210070	UE Architecture, assumptions and Primary scenarios for Dual TX/RX MUSIM operation	Nokia, Nokia Shanghai Bell
R2-2210389	Scenarios for Rel-18 Multi-SIM	vivo
R2-2210392	Scenarios and assumptions for Dual-RX/Dual-TX MUSIM UE	Ericsson
R2-2210421	eMUSIM Scenarios	Sharp
R2-2210503	Discussion on R18 MUSIM Scenarios	MediaTek Inc.
R2-2210533	Applicable scenarios for dual Tx/Rx MUSIM devices	DENSO CORPORATION
R2-2210582	Scenarios for Rel-18 MUSIM	LG Electronics
R2-2210728	General considerations on potential scenarios for MUSIM	Samsung
R2-2210738	Discussion on MN-SN MUSIM gaps coordination in INM	Samsung

8.17.2.2: Solutions

TDoc	Title	Source
R2-2209392	Consideration on the Temporary UE Capability Restriction for the Dual (Tx/Rx) MUSIM	ZTE Corporation, Sanechips
R2-2209423	Potential Solutions on temporary UE capability restriction and removal of restriction	OPPO
R2-2209575	UE Capability Update for Dual-Active MUSIM	Qualcomm Incorporated
R2-2209596	Discussion on Dual Tx/Rx Multi-SIM for NR	Vodafone
R2-2209638	Possible solutions to indicate temporary capability reduction for Rel-18 MUSIM	Intel Corporation
R2-2209856	Discussion on Dual Tx/Rx Multi-SIM	ASUSTeK
R2-2210001	Solutions of Temporary capability restriction for MUSIM	NEC
R2-2210007	Discussion on UE capability update for MUSIM	Huawei, HiSilicon
R2-2210018	Discussion on UE-initiated SCell deactivation and activation	Huawei, HiSilicon
R2-2210060	Capability sharing issue for SRS Tx switching capability	Xiaomi
R2-2210071	Candidate solutions for Dual TX/RX MUSIM operation	Nokia, Nokia Shanghai Bell
R2-2210390	Potential solutions for Rel-18 Multi-SIM	vivo
R2-2210422	eMUSIM Solutions	Sharp
R2-2210446	[Draft] LS on DLUL interruption due to capability switching	vivo
R2-2210514	Discussion on R18 MUSIM Solutions	MediaTek Inc.
R2-2210534	Possible solution for dual Rx/Tx MUSIM devices	DENSO CORPORATION
R2-2210583	General soluion for Rel-18 MUSIM	LG Electronics
R2-2210596	Analysis on dual Tx/Rx Multi-SIM	Lenovo Information Technology
R2-2210730	Discussion on capability coordination for MUSIM	Samsung
R2-2210823	Report of [AT119bis-e][211][MUSIM] MUSIM solutions for Rel-18 (QC)	Qualcomm Incorporated

8.17.3: Other

TDoc	Title	Source
R2-2209393	Considering on the Scheduling Gap Enhancement for the MR-DC	ZTE Corporation, Sanechips
R2-2210072	Additional scenarios for Dual TX/RX MUSIM UE	Nokia, Nokia Shanghai Bell
R2-2210391	Discussion on MUSIM gap collision handling	vivo
R2-2210394	Discussion on MUSIM gaps for a Dual-RX/Dual-TX UE	Ericsson
R2-2210485	Band Conflict Issue and Mitigation for MUSIM	Apple

8.18: R18 Other

TDoc	Title	Source
R2-2209303	LS on starting a timer in RRC-inactive state (C1-225319; contact: Huawei)	CT1
R2-2209304	LS on SENSE feature (C1-225338; contact: Huawei)	CT1
R2-2209314	LS to RAN2 on two overlapping LTE-CRS patterns in Rel-18 DSS (R1-2208194; contact: ZTE)	RAN1
R2-2209322	Reply LS on FS_REDCAP_Ph2 option feasibility (R3-225119; contact: ZTE)	RAN3
R2-2209336	Reply LS on UL Tx switching across 3 or 4 bands (R4-2214464; contact: China Telecom)	RAN4
R2-2209344	LS on extending the maximum range for NS values (R4-2214953; contact: Apple)	RAN4
R2-2209351	LS on Terminology Alignment for Ranging/Sidelink Positioning (S2-2207129; contact: Xiaomi)	SA2
R2-2209355	LS Out on RAN dependency of FS_eNS_Ph3 (S2-2207435; contact: ZTE)	SA2
R2-2209364	LS on RAN feedback for low latency (S2-2201767; contact: Huawei)	SA2
R2-2209790	On extending the maximum range of NS values	Apple
R2-2209791	[Draft] LS reply on extending the maximum range for NS values	Apple
R2-2209900	Discussion on RAN dependency of FS_eNS_Ph3	Huawei, HiSilicon
R2-2209917	Reply LS on SENSE feature	vivo
R2-2209918	Discussion on SENSE feature	vivo
R2-2210098	Discussion on RAN2’s impact of SENSE	OPPO
R2-2210099	36.304 CR on SENSE	OPPO
R2-2210100	38.304 CR on SENSE	OPPO
R2-2210103	Proposed answers to SA2 LS on RAN dependency of FS_eNS_Ph3 (R2-2209355/SA2-2207435)	Nokia, Nokia Shanghai Bell
R2-2210133	RRC configuration and UE capability for PDCCH on CRS	Nokia, Nokia Shanghai Bell
R2-2210297	Discussion on two overlapping LTE-CRS patterns in Rel-18 DSS	ZTE Corporation, Sanechips, Ericsson
R2-2210298	Consideration on Rel-18 UL Tx switching capability and configuration	ZTE Corporation, Sanechips
R2-2210320	Relaying of posSIBs	Ericsson
R2-2210367	On Positioning Support for L2 UE-to-Network Remote UEs	Qualcomm Incorporated
R2-2210395	Increasing NS value range	Ericsson
R2-2210397	On FS_eNS_Ph3	Ericsson
R2-2210403	Considerations on SA2 Key issue #3	NEC
R2-2210437	Current status of Rel-18 UL Tx switching in RAN2	NTT DOCOMO INC.
R2-2210490	RAN2 impact to support Rel-18 UL Tx switching enhancements	Huawei, HiSilicon
R2-2210515	38.304 CR on SENSE feature	vivo
R2-2210529	Discussion on RAN Aspects of Signal Level Enhanced Network Selection	Huawei, HiSilicon
R2-2210532	Reply LS on SENSE feature	Huawei, HiSilicon
R2-2210586	Clarification on the DSS UE capability	Xiaomi
R2-2210587	Clarification on the DSS UE capability	Xiaomi
R2-2210618	Discussion on SENSE feature	Deutsche Telekom, Thales, Ericsson, Telecom Italia
R2-2210622	[Draft] Reply LS Out on RAN dependency of FS_eNS_Ph3	Ericsson
R2-2210631	Draft Reply LS on SENSE feature	Deutsche Telekom
R2-2210636	Work plan for Rel18 WI on Enhancement of NR Dynamic spectrum sharing (DSS)	Ericsson
R2-2210637	On RAN2 aspects for UL TX switching Rel-18	Ericsson
R2-2210647	Discussion on the LS on RAN dependency of FS_eNS-Ph3	CATT
R2-2210669	Consideration on RAN dependency of FS_eNS_Ph3	ZTE corporation, Sanechips
R2-2210670	[Draft] Reply LS on RAN dependency of FS_eNS_Ph3	ZTE corporation, Sanechips
R2-2210680	Protection of system information	Ericsson
R2-2210710	Enhancements of Public Warning System	Ericsson
R2-2210821	Report of [AT119bis-e][210][R18 Slicing] RAN dependency of FS_eNS_Ph3 (ZTE)	ZTE
R2-2210822	[Draft] Reply LS on RAN dependency of FS_eNS_Ph3	ZTE corporation, Sanechips
R2-2210827	Reply LS on RAN dependency of FS_eNS_Ph3	RAN2
R2-2210985	[AT119bis-e][014][NR18] SENSE	Huawei, HiSilicon
R2-2210988	Summary of email discussion [AT119bis-e][013][NR17] NS Value Extension (Apple)	Apple Inc
R2-2210992	Report of [AT119bis-e][016][NR18] DSS enhancement	ZTE Corporation
R2-2210993	Running 38.331 CR for R18 DSS	Ericsson, ZTE Corporation
R2-2210994	Running 38.306 CR for R18 DSS	ZTE Corporation, Ericsson
R2-2211030	Reply LS on starting a timer in RRC-inactive state (S2-2209265; contact: Huawei)	SA2
R2-2211038	LS on UL scenario of reactive RAN feedback for burst sending time adjustment (S2-2209879; contact: Huawei)	SA2
R2-2211040	LS on GNSS integrity requirement provisioning (S2-2209966; contact: Huawei)	SA2
R2-2211053	Response to LS on extending the maximum range for NS values	RAN2
R2-2211064	Response to LS on extending the maximum range for NS values	RAN2

9.1: Session on NTN, IoT NTN, RedCap and CE

TDoc	Title	Source
R2-2210801	Report from Break-Out Session on NTN, IoT NTN, RedCap and CE	Vice Chairman (ZTE)

9.2: Session on LTE legacy, 71 GHz, DCCA, Multi-SIM, RAN slicing, QoE and XR

TDoc	Title	Source
R2-2210802	Report from session on LTE legacy, 71 GHz, DCCA, Multi-SIM, RAN slicing, QoE and XR	Vice Chairman (Nokia)

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

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

9.4: Session on positioning and sidelink relay

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

9.5: Session on LTE V2X and NR SL

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

9.6: Session on SON/MDT

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

9.7: Session on MBS

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

9.8: Session on NC Repeater

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