RAN2#121

1: Opening of the meeting

TDoc	Title	Source
R2-2301968	[Reserved]	[Reserved]

2.1: Approval of the agenda

TDoc	Title	Source
R2-2300001	Agenda for RAN2#121	Chairman

2.2: Approval of the report of the previous meeting

TDoc	Title	Source
R2-2300002	RAN2#120 Meeting Report	MCC

2.4: Instructions

TDoc	Title	Source
R2-2300003	RAN2 Handbook	MCC

2.5: Others

TDoc	Title	Source
R2-2300464	Discussion on communication via satellite to unmodified UEs	Vodafone
R2-2301498	Guidelines on writing a CR	MCC
R2-2301990	Xn-U Address Information delivery in CPAC	R3 (Huawei, Intel Corporation, Lenovo, China Telecom, ZTE, Deutsche Telekom, Ericsson)
R2-2301991	PDCP PDU early transmission in CPAC	R3 (Huawei, Lenovo, China Telecom, Intel Corporation,CATT)
R2-2301992	Correction to the description of the CHO	R3 (Nokia, Nokia Shanghai Bell, ZTE, Intel Corporation, CATT, Ericsson)
R2-2301993	Clarifications on prepared PSCell addition by candidate SN in CPC-A	R3 (NEC, ZTE, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Google Inc. Intel Corporation, Lenovo)
R2-2301994	Correction on SCG reconfiguration when MN initiated conditional reconfiguration is prepared	R3 (Lenovo, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Intel Corporation)
R2-2302083	Correction to the description of the CHO	R3 (Nokia, Nokia Shanghai Bell, ZTE, Intel Corporation, CATT, Ericsson)
R2-2302084	Clarifications on prepared PSCell addition by candidate SN in CPC-A	R3 (NEC, ZTE, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Google Inc. Intel Corporation, Lenovo)
R2-2302119	Correction to the description of the CHO	R3 (Nokia, Nokia Shanghai Bell, ZTE, Intel Corporation, CATT, Ericsson)

3: Incoming liaisons

TDoc	Title	Source
R2-2301930	Research highlighting potential 5G and 4G Bidding Down Attacks	GSMA
R2-2301932	Response to “LS from NRG to 3GPP SA2 on UEs behaviour on detecting an emergency call whilst in Limited Service State” (S2-2303306; contact: Vodafone)	SA2

4.1: EUTRA corrections Rel-16 and earlier

TDoc	Title	Source
R2-2301131	Introduction of Cell Individual Offset for inter-RAT measurement Event B2	Reliance Jio
R2-2301133	Introduction of Cell Individual Offset for inter-RAT measurement Event B2	Reliance Jio
R2-2301928	Introduction of Cell Individual Offset in LTE inter-RAT measurements for NR neighbors	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs
R2-2301929	Introduction of new UE capability towards updated LTE inter-RAT measurement for NR neighbors	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs
R2-2302180	Introduction of Cell Individual Offset in LTE inter-RAT measurements for NR neighbors	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs, Samsung
R2-2302218	Introduction of cell-specific offset for inter-RAT measurement in LTE for NR neighbors	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs, Samsung
R2-2302219	Introduction of UE capability parameter cellIndividualOffsetForNR	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs, Samsung
R2-2302248	Report of [AT121][203][LTE] CIO for Inter-RAT HO from LTE to NR	CEWiT, Samsung (offline email discussion rapporteur)
R2-2302282	Introduction of UE capability parameter cellIndividualOffsetForNR	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs, Samsung
R2-2302291	Report of [AT121][203][LTE] CIO for Inter-RAT HO from LTE to NR	CEWiT, Samsung (offline email discussion rapporteur)
R2-2302292	Introduction of new UE capability towards updated LTE inter-RAT measurement for NR neighbors	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs
R2-2302298	Introduction of UE capability parameter cellIndividualOffsetForNR [CIO-IRAT-HO-ToNR]	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs, Samsung
R2-2302299	Introduction of cell-specific offset for inter-RAT measurement in LTE for NR neighbors [CIO-IRAT-HO-ToNR]	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs, Samsung
R2-2302300	Introduction of UE capability parameter cellIndividualOffsetForNR [CIO-IRAT-HO-ToNR]	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs, Samsung
R2-2302301	Introduction of cell-specific offset for inter-RAT measurement in LTE for NR neighbors [CIO-IRAT-HO-ToNR]	Reliance Jio, CEWiT, Indian Institute of Technology Madras, Indian Institute of Technology Hyderabad, Saankhya Labs, Samsung

5.1.1: Stage 2 and Organisational

TDoc	Title	Source
R2-2301679	Correction on RLC re-establishment in handover	vivo
R2-2301680	Correction on RLC re-establishment in handover	vivo
R2-2301681	Correction on RLC re-establishment in handover	vivo
R2-2301783	Clarification on the PDCCH Ordered RACH for SCell in 38.300	ZTE Corporation, Nokia(Rapporteur), Sanechips
R2-2301784	Clarification on the PDCCH Ordered RACH for SCell in 38.300	ZTE Corporation, Nokia(Rapporteur), Sanechips
R2-2301785	Clarification on the PDCCH Ordered RACH for SCell in 38.300	ZTE Corporation, Nokia(Rapporteur), Sanechips
R2-2302015	LS on clarification on impact of SRS antenna switching for TDD-FDD band combinations (R4-2303633; contact: Huawei)	RAN4
R2-2302203	Clarification on the PDCCH Ordered RACH for SCell in 38.300	ZTE Corporation, Nokia(Rapporteur), Sanechips
R2-2302204	Clarification on the PDCCH Ordered RACH for SCell in 38.300	ZTE Corporation, Nokia(Rapporteur), Sanechips
R2-2302205	Clarification on the PDCCH Ordered RACH for SCell in 38.300	ZTE Corporation, Nokia(Rapporteur), Sanechips

5.1.2.1: MAC

TDoc	Title	Source
R2-2300490	NRU and 2Step RA Corrections on Rel-16 MAC	vivo
R2-2300493	NRU and 2Step RA Corrections on Rel-17 MAC	vivo
R2-2300508	Clarification on triggering condition of SR	Samsung R&D Institute India
R2-2300510	Clarification on triggering condition of SR	Samsung R&D Institute India
R2-2300512	Clarification on triggering condition of SR	Samsung R&D Institute India
R2-2301465	Correction on L1-RSRP measurement of SSB or CSI-RS for RACH	Apple Inc
R2-2301466	Correction on L1-RSRP measurement of SSB or CSI-RS for RACH	Apple Inc
R2-2301782	Reconsiderations on CG Type 1 Resources Calculation at BWP activation	ZTE, Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, OPPO, vivo, Huawei, Hisilicon, CATT, Sanechips

5.1.2.2: RLC PDCP SDAP BAP

TDoc	Title	Source
R2-2301381	Clarification on the setting of the split secondary RLC for the PDCP entity associated with only two RLC entities.	Samsung
R2-2301382	Clarification on the setting of the split secondary RLC for the PDCP entity associated with only two RLC entities.	Samsung
R2-2301913	Order of performing integrity protection and setting PDCP SN in Transmit operation	Nokia, Nokia Shanghai Bell
R2-2301914	Order of performing integrity protection and setting PDCP SN in Transmit operation	Nokia, Nokia Shanghai Bell
R2-2301915	Order of performing integrity protection and setting PDCP SN in Transmit operation	Nokia, Nokia Shanghai Bell
R2-2301916	Removal of redundant word on interpretation of the bits in the parameters	Nokia, Nokia Shanghai Bell
R2-2301917	Removal of redundant word on interpretation of the bits in the parameters	Nokia, Nokia Shanghai Bell
R2-2301918	Removal of redundant word on interpretation of the bits in the parameters	Nokia, Nokia Shanghai Bell

5.1.3.1: NR RRC

TDoc	Title	Source
R2-2300214	Corrections to on-demand SI request	Lenovo
R2-2300239	Editorial change for IE RateMatchPatternId referenced section in TS 38.214	RadiSys
R2-2300240	Modify presence of the IE precodingAndNumberOfLayers within rrc-ConfiguredUplinkGrant	RadiSys
R2-2300395	Correction on T350 stop	Xiaomi, Ericsson
R2-2300396	Correction on T350 stop	Xiaomi, Ericsson
R2-2300469	Correction to nas-SecurityParamFromNR in Mobility from NR command	Nokia, Nokia Shanghai Bell
R2-2300546	Correction to fullConfig	Nokia, Nokia Shanghai Bell
R2-2300547	Correction to fullConfig	Nokia, Nokia Shanghai Bell
R2-2300548	Correction to fullConfig	Nokia, Nokia Shanghai Bell
R2-2300549	Correction to usage of pusch-TimeDomainAllocation	Nokia, Nokia Shanghai Bell
R2-2300550	Correction to usage of pusch-TimeDomainAllocation	Nokia, Nokia Shanghai Bell
R2-2300551	Correction to usage of pusch-TimeDomainAllocation	Nokia, Nokia Shanghai Bell
R2-2300552	Correction to usage of pusch-TimeDomainAllocation	Nokia, Nokia Shanghai Bell
R2-2300571	Clarification of PUCCH SCell Definition	Nokia, Nokia Shanghai Bell
R2-2300572	Clarification of PUCCH SCell Definition	Nokia, Nokia Shanghai Bell
R2-2300573	Clarification of PUCCH SCell Definition	Nokia, Nokia Shanghai Bell
R2-2300629	Miscellaneous corrections for Rel-16 RRC	Lenovo
R2-2300779	Discussion on PUCCH SCell Operation	MediaTek Inc.
R2-2300781	Corrections for PUCCH SCell	Huawei, HiSilicon, Ericsson
R2-2300782	Corrections for PUCCH SCell	Huawei, HiSilicon, Ericsson
R2-2300783	Corrections for PUCCH SCell	Huawei, HiSilicon, Ericsson
R2-2300784	Clarification of DC location report for non-RRC Configured BWP0	Huawei, HiSilicon
R2-2300785	Clarification of DC location report for non-RRC Configured BWP0	Huawei, HiSilicon
R2-2300786	Clarification of DC location report for non-RRC Configured BWP0	Huawei, HiSilicon
R2-2300787	Correction on the need code for secondary DRX group	Huawei, HiSilicon
R2-2300788	Correction on the need code for secondary DRX group	Huawei, HiSilicon
R2-2300801	Discussion on 1 second UAI resend rule after RRCReconfiguration including fullConfig	MediaTek Inc.
R2-2300802	Clarification on 1 second UAI resend rule after RRCReconfiguration including fullConfig	MediaTek Inc.
R2-2300809	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2300812	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2300813	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2301311	Discussion on PUCCH SCell	ZTE Corporation, Sanechips
R2-2301312	Corrections on refServCellIndicator	ZTE Corporation, Sanechips
R2-2301313	Corrections on refServCellIndicator	ZTE Corporation, Sanechips
R2-2301314	Corrections on refServCellIndicator	ZTE Corporation, Sanechips
R2-2301342	RRC connection re-establishment with CPC configuration	Ericsson
R2-2301451	SIB and PosSIB mappings to SI message	Ericsson
R2-2301452	SIB and PosSIB mappings to SI message	Ericsson
R2-2301455	Miscellaneous non-controversial corrections Set XVII	Ericsson
R2-2301456	Miscellaneous non-controversial corrections Set XVII	Ericsson
R2-2301555	Clarification on PSCell CORESET#0 configuration mismatch	Samsung Electronics Austria
R2-2301682	Correction on the description of RRC reconfiguration with sync	vivo
R2-2301683	Correction on the description of RRC reconfiguration with sync	vivo
R2-2301684	Correction on the description of RRC reconfiguration with sync	vivo
R2-2302012	Correction to usage of pusch-TimeDomainAllocation	Nokia, Nokia Shanghai Bell
R2-2302013	Correction to usage of pusch-TimeDomainAllocation	Nokia, Nokia Shanghai Bell
R2-2302176	Correction on T350 stop	Xiaomi
R2-2302177	Correction on T350 stop	Xiaomi
R2-2302238	Correction on T350 stop	Xiaomi, Ericsson
R2-2302243	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2302244	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2302245	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2302252	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2302253	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2302254	Clarification on RLC bearer re-association	MediaTek Inc.
R2-2302272	Report of [AT121][003][R1516] Corrections on refServCellIndicator (ZTE)	ZTE Corporation
R2-2302273	Corrections on refServCellIndicator	ZTE Corporation, Sanechips
R2-2302274	Corrections on refServCellIndicator	ZTE Corporation, Sanechips
R2-2302275	Corrections on refServCellIndicator	ZTE Corporation, Sanechips

5.1.3.2: UE capabilities

TDoc	Title	Source
R2-2300007	Reply LS on eMIMO features defined in different granularity with prerequisite (R1-2208250; contact: Huawei)	RAN1
R2-2300048	LS to RAN2 on simultaneous Rx-Tx for band pairs of an advertised BC (R4-2220520; contact: Ericsson)	RAN4
R2-2300049	LS to RAN2 on intraBandFreqSeparationUL-AggBW-GapBW-r16 (R4-2220534; contact: Samsung)	RAN4
R2-2300058	LS on Duty Cycle capability for PC1.5 (R4-2220807; contact: T-Mobile USA)	RAN4
R2-2300140	Discussion on the order of Intra-band feature set	OPPO
R2-2300553	Clarification on simultaneous Rx-Tx	Nokia, Nokia Shanghai Bell
R2-2300574	Support of different PCell duplex for UL Tx switching	Nokia, Nokia Shanghai Bell
R2-2301403	Correction on Duty Cycle capability for PC1.5	Ericsson
R2-2301404	Correction on Duty Cycle capability for PC1.5	Ericsson
R2-2301406	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2301407	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2301408	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2301409	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2301450	On modified UE capabilities for simultaneous Rx/Tx	Ericsson
R2-2301607	Clarification on supportedCellGrouping capability	Huawei, HiSilicon
R2-2301608	Clarification on supportedCellGrouping capability	Huawei, HiSilicon
R2-2301609	Clarification on capabilities reported in different granularity with prerequisite	Huawei, HiSilicon
R2-2301610	Clarification on capabilities reported in different granularity with prerequisite	Huawei, HiSilicon
R2-2301612	Discussion on simultaneousRxTx capability	Huawei, HiSilicon
R2-2301629	Discussion on intraBandFreqSeparationUL-AggBW-GapBW-r16	CATT
R2-2301713	CR on the intraBandFreqSeparationUL-AggBW-GapBW-r16 _R16	ZTE Corporation, Sanechips
R2-2301714	CR on the intraBandFreqSeparationUL-AggBW-GapBW-r16 _R17	ZTE Corporation, Sanechips
R2-2301715	CR on Simultaneous Rx-Tx for Band Pairs_R15	ZTE Corporation, Sanechips
R2-2301716	CR on Simultaneous Rx-Tx for Band Pairs_R16	ZTE Corporation, Sanechips
R2-2301717	CR on Simultaneous Rx-Tx for Band Pairs_R17	ZTE Corporation, Sanechips
R2-2301718	Consideration on the Simultaneous Rx-Tx	ZTE Corporation, Sanechips
R2-2301746	Band differentiation for capability pusch-RepetitionTypeA-r16	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2301747	Band differentiation for capability pusch-RepetitionTypeA-r16	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2301748	Band differentiation for capability pusch-RepetitionTypeA-r16	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2301749	Band differentiation for capability pusch-RepetitionTypeA-r16	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2301897	CR on the intraBandFreqSeparationUL-AggBW-GapBW-r16 _R16	ZTE Corporation, Sanechips, Samsung
R2-2301898	CR on the intraBandFreqSeparationUL-AggBW-GapBW-r16 _R17	ZTE Corporation, Sanechips, Samsung
R2-2301948	Band differentiation for capability pusch-RepetitionTypeA-r16	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2302098	CR on the intraBandFreqSeparationUL-AggBW-GapBW-r16_R16	ZTE Corporation, Sanechips, Samsung
R2-2302099	Band differentiation for capability pusch-RepetitionTypeA-r16	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2302109	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2302197	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2302198	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2302199	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2302200	Correction on UL RRC segmentation processing delay requirements	Ericsson
R2-2302208	[AT121][009][R1516] Simultaneous RxTx (Ericsson)	Ericsson
R2-2302213	Clarification on supportedCellGrouping capability	Huawei, HiSilicon
R2-2302214	Clarification on supportedCellGrouping capability	Huawei, HiSilicon
R2-2302215	Clarification on capabilities reported in different granularity with prerequisite	Huawei, HiSilicon
R2-2302216	Clarification on capabilities reported in different granularity with prerequisite	Huawei, HiSilicon

5.1.3.3: Other

TDoc	Title	Source
R2-2300700	Further Discussion on SI-request Period Issue	vivo, Huawei, HiSilicon
R2-2301127	Corrections in TS 36.331 on IFRI handling by IAB-MT for IAB	Huawei, HiSilicon
R2-2301128	Corrections in TS 36.331 on IFRI handling by IAB-MT for eIAB	Huawei, HiSilicon
R2-2301129	Corrections in TS 38.331 on IFRI handling by IAB-MT for IAB	Huawei, HiSilicon
R2-2301130	Corrections in TS 38.331 on IFRI handling by IAB-MT for eIAB	Huawei, HiSilicon
R2-2301297	Clarification of the UE actions when iab-support is not included in SIB1	Ericsson
R2-2301298	Clarification of the UE actions when iab-support is not included in SIB1	Ericsson
R2-2302112	Corrections in TS 36.304 on csg-Indication handling by IAB-MT for IAB	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE, Sanechips
R2-2302115	Corrections in TS 36.331 on IFRI handling by IAB-MT for eIAB	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell
R2-2302116	Clarification that IAB-MT follows the UE behaviour for cell barring procedure as defined in TS 38.304	Ericsson, Intel Corporation
R2-2302223	Corrections in TS 36.304 on csg-Indication handling by IAB-MT for IAB	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE, Sanechips
R2-2302224	Corrections in TS 36.304 on csg-Indication handling by IAB-MT for IAB	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE, Sanechips
R2-2302250	Corrections in TS 36.331 on IFRI handling by IAB-MT for IAB	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell
R2-2302251	Corrections in TS 36.331 on IFRI handling by IAB-MT for eIAB	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell
R2-2302258	Clarification that IAB-MT follows the UE behaviour for cell barring procedure as defined in TS 38.304	Ericsson
R2-2302259	Clarification that IAB-MT follows the UE behaviour for cell barring procedure as defined in TS 38.304	Ericsson
R2-2302265	Clarification that IAB-MT follows the UE behaviour for cell barring procedure as defined in TS 38.304	Ericsson, Intel Corporation
R2-2302266	Clarification that IAB-MT follows the UE behaviour for cell barring procedure as defined in TS 38.304	Ericsson, Intel Corporation

5.2.1: General and Stage-2 corrections

TDoc	Title	Source
R2-2300040	LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier (R4-2214421; contact: vivo)	RAN4
R2-2300051	LS on PSFCH configured power with multiple resource pools (R4-2220553; contact: LGE)	RAN4
R2-2300914	(draft)Reply LS to RAN4 on Pemax,c of S-SSB transmission	ZTE Corporation, Sanechips
R2-2301379	[draft]Reply LS on Pemax,c of S-SSB transmission	vivo
R2-2302021	[draft] Reply LS on Pemax,c of S-SSB transmission	vivo
R2-2302040	Reply LS on Pemax,c of S-SSB transmission	RAN2
R2-2302058	Reply LS to RAN4 on PSFCH configured power with multiple resource pools (R1-2302231; contac: LGE)	RAN1

5.2.2: Control plane corrections

TDoc	Title	Source
R2-2300485	Miscellaneous corrections on 38.331	Huawei, HiSilicon
R2-2300486	Miscellaneous corrections on 38.331	Huawei, HiSilicon
R2-2300836	Miscellaneous corrections on TS 38.331 for NR sidelink	Xiaomi
R2-2300837	Miscellaneous corrections on TS 38.331 for NR sidelink	Xiaomi
R2-2301021	Clarification on retransmission number in SL-PSSCH-TxConfigList	vivo
R2-2301022	Clarification on retransmission number in SL-PSSCH-TxConfigList	vivo
R2-2301377	Clarification on sl-MaxTransPower	vivo
R2-2301378	Clarification on sl-MaxTransPower	vivo
R2-2301461	Summary on RRC CRs	Huawei, HiSilicon
R2-2301762	Clarification on cell reselection priority handling for V2X/NR sidelink and deprioritization request.	Kyocera, vivo, LG Electronics, Ericsson, Samsung, Nokia, Nokia Shanghai Bell
R2-2302024	Summary of [AT121][502][V2X/SL] R16 RRC corrections (Huawei)	Huawei, HiSilicon

5.2.3: User plane corrections

TDoc	Title	Source
R2-2300834	Correction on resource (re-)selection for NR sidelink	Xiaomi
R2-2300835	Correction on resource (re-)selection for NR sidelink	Xiaomi
R2-2300861	Correction on the cast type indicator setting of MAC PDU only containing MAC CE	CATT
R2-2300862	Correction on the cast type indicator setting of MAC PDU only containing MAC CE(s)	CATT
R2-2301525	Corrections on MAC reset regarding SL configured grant	ASUSTeK
R2-2301526	Corrections on MAC reset regarding SL configured grant	ASUSTeK
R2-2301926	Summary on MAC CRs	LG Electronics
R2-2302027	Summary of [AT121][503][V2X/SL] R16 MAC corrections (LG)	LG

5.3.1: General and Stage 2 corrections

TDoc	Title	Source
R2-2301899	Summary of [Pre121][401] Rel-15 and Rel-16 NR Positioning Support AIs 5.3.2 and 5.3.3	CATT

5.3.2: RRC corrections

TDoc	Title	Source
R2-2300107	Correction for SRS-PosResourcesPerBand	Huawei, HiSilicon
R2-2300108	Correction for SRS-PosResourcesPerBand	Huawei, HiSilicon
R2-2300109	Correction on PosSIB broadcasting	Huawei, HiSilicon
R2-2300110	Correction on PosSIB broadcasting	Huawei, HiSilicon
R2-2300937	Correction on SRS for positioning	ZTE Corporation
R2-2300938	Correction on SRS for positioning	ZTE Corporation
R2-2301347	Conditional inclusion of SBAS ID in posSIBs	MediaTek Inc.
R2-2301348	Conditional inclusion of SBAS ID in posSIBs	MediaTek Inc.
R2-2301349	Mapping of posSIB/SIB segments to SI messages	MediaTek Inc., Nokia, Nokia Shanghai Bell, Ericsson
R2-2302022	Correction for SRS-PosResourcesPerBand	Huawei, HiSilicon
R2-2302023	Correction for SRS-PosResourcesPerBand	Huawei, HiSilicon
R2-2302097	Correction on SRS for positioning	ZTE Corporation
R2-2302123	Correction for SRS-PosResourcesPerBand	Huawei, HiSilicon
R2-2302124	Correction for SRS-PosResourcesPerBand	Huawei, HiSilicon
R2-2302125	Conditional inclusion of SBAS ID in posSIBs	MediaTek Inc.
R2-2302126	Conditional inclusion of SBAS ID in posSIBs	MediaTek Inc.

5.3.3: LPP corrections

TDoc	Title	Source
R2-2300328	Addition of missing field description for ‘nr-AdType-r16’ in NR-Multi-RTT-RequestAssistanceData IE	Lenovo
R2-2300329	Addition of missing field description for ‘nr-AdType-r16’ in NR-Multi-RTT-RequestAssistanceData IE	Lenovo
R2-2301431	Adding GNSS Types in GNSS-SSR-OrbitCorrections to clarify SSR clock correction signal reference and clarification of GNSS Troposperic Delay Correction	Ericsson
R2-2301432	Correction of Note in NR-DL-PRS-AssistanceData field descriptions	Ericsson
R2-2301433	Adding GNSS Types in GNSS-SSR-OrbitCorrections to clarify SSR clock correction signal reference and clarification of GNSS Troposperic Delay Correction	Ericsson
R2-2301434	Correction of Note in NR-DL-PRS-AssistanceData field descriptions	Ericsson
R2-2302127	Correction of Note in NR-DL-PRS-AssistanceData field descriptions and Addition of missing field description	Ericsson, Lenovo
R2-2302128	Correction of Note in NR-DL-PRS-AssistanceData field descriptions and Addition of missing field description	Ericsson, Lenovo
R2-2302187	[AT121][402][POS] GNSS-SSR-OrbitCorrections (Ericsson)	Ericsson
R2-2302229	Clarifying Galileo NAV message in the GNSS Navigation model to clarify SSR clock correction signal reference	Ericsson
R2-2302230	Clarifying Galileo NAV message in the GNSS Navigation model to clarify SSR clock correction signal reference	Ericsson

5.4.3: RRC corrections

TDoc	Title	Source
R2-2301270	Correction on logging RLM resources in the RLF report	Ericsson
R2-2301271	Correction on logging RLM resources in the RLF report	Ericsson
R2-2301499	Clarification on RLF Cause	Samsung
R2-2301502	Clarification on RLF cause	Samsung
R2-2301505	Clarification on RLF cause	Samsung
R2-2301567	Discussion on location configuration for SON and MDT features	Huawei, HiSilicon

6.1.1: Stage 2 and Organisational

TDoc	Title	Source
R2-2300054	Reply LS on FR2 UL gap (R4-2220730; contact: Apple)	RAN4
R2-2300059	LS on DC location reporting (R4-2220814; contact: vivo, OPPO)	RAN4
R2-2300215	Corrections to description of RAN Visible QoE Measurements	Lenovo
R2-2300468	Correction Stage-2 on CPAC	Nokia, Nokia Shanghai Bell
R2-2300718	Clarification of UE Behaviour upon Pause of QoE Reporting	Apple, Ericsson, MediaTek, Huawei, HiSilicon, China Unicom, Nokia, Nokia Shanghai Bell
R2-2300857	Clarification on coexistence of DAPS and CPA	CATT, Nokia (Rapporteur)
R2-2300858	Clarification on coexistence of DAPS and CPA	CATT, Nokia (Rapporteur)
R2-2300868	Removal of editor's note on sequence length 1151 for PRACH usage	Nokia, Nokia Shanghai Bell
R2-2301126	Corrections on routing and bearer mapping configuration for eIAB	Huawei, HiSilicon, Nokia (Rapporteur)
R2-2301215	Corrections for DCCA further enhancements	ZTE Corporation (Rapporteur), Sanechips, Ericsson
R2-2301299	Clarfication on DL power adjustment for IAB	Ericsson
R2-2301334	Discussion on naming of QoE	Ericsson
R2-2301558	Clarification on paging collision avoidance for MUSIM	Samsung
R2-2301893	Clarification of UE Behaviour upon Pause of QoE Reporting	Apple, Ericsson, MediaTek, Huawei, HiSilicon, China Unicom, Nokia, Nokia Shanghai Bell, Samsung
R2-2301896	Introduction of stage 2 description for IAB beam management and power control	Lenovo
R2-2301997	LS on Rel-17 RAN4 UE feature list for NR (R4-2300820; contact: CMCC)	RAN4
R2-2302006	Reply LS on clarification for ue-PowerClassPerBandPerBC-r17 (R4 16-8) (R4-2303630; contact: Samsung)	RAN4
R2-2302014	Reply LS on new contiguous BW classes for legacy networks (R4-2303631; contact: Nokia)	RAN4
R2-2302017	LS on UE signalling for the maximum aggregated bandwidth for FR1 CA (R4-2303685; contact: Qualcomm)	RAN4
R2-2302018	LS on signaling for FR2 FBG5 CA BW classes (R4-2303689; contact: Apple)	RAN4
R2-2302047	LS to RAN2 on K2 indication for multi-PUSCH scheduling (R1-2302144; contact: LGE)	RAN1
R2-2302049	Reply LS on PDCCH skipping (R2-2302049; contact: MediaTek)	RAN1
R2-2302051	LS to RAN2 on reference subcarrier spacing for FR2-2 (R1- 2302185; contact: Nokia)	RAN1
R2-2302096	Removal of editor’s note on sequence length 1151 for PRACH usage	Nokia, Nokia Shanghai Bell
R2-2302241	Clarification of UE Behaviour upon Pause of QoE Reporting	Apple, Ericsson, MediaTek, Huawei, HiSilicon, China Unicom, Nokia, Nokia Shanghai Bell, Samsung
R2-2302242	Corrections for DCCA enhancement	ZTE Corporation (Rapporteur), Sanechips, Ericsson, Nokia, Nokia Shanghai Bell

6.1.2: User Plane corrections

TDoc	Title	Source
R2-2300494	MAC Clarification on Msg3 Repetition	vivo
R2-2301368	Inclusion of drx-LastTransmissionUL in DRX parameters list	MediaTek Inc.
R2-2301730	Corrections on slice-based RACH	LG Electronics.
R2-2302111	Miscellaneous editorial changes for 38.321	MediaTek Inc., Nokia, vivo, LGE
R2-2302217	Miscellaneous editorial changes for 38.321	MediaTek Inc., Nokia, vivo, LGE

6.1.3.1: NR RRC

TDoc	Title	Source
R2-2300005	LS on the information provided from the UE NAS layer for slice based Random Access (C1-227207; contact: CMCC)	CT1
R2-2300013	LS to RAN4 and RAN2 on L3-RSSI measurement for NR up to 71GHz (R1-2212830; contact: Qualcomm)	RAN1
R2-2300017	LS to RAN2 on msg1/msgA transmission channel access control in SIB1 (R1-2212965; contact: Qualcomm)	RAN1
R2-2300030	Reply LS on questions on RAN visible QoE (R3-226061; contact: Huawei)	RAN3
R2-2300055	Reply LS to RAN2 on RLM/BFD relaxation for ePowSav (R4-2220731; contact: vivo)	RAN4
R2-2300132	Discussion on RAN1 LS on msg1/msgA transmission channel access control	OPPO
R2-2300170	RRC correction on TRS availability	OPPO
R2-2300171	Discussion on ignoring PDCCH skipping	OPPO
R2-2300216	Corrections to Application layer measurement reporting procedure and alignment of terminologies	Lenovo
R2-2300307	Corrections to eIAB in TS 38.331	Nokia, Nokia Shanghai Bell
R2-2300308	Discussion on RLM/BFD relaxation for SCG deactivation	vivo
R2-2300309	[Draft] Reply LS to RAN4 on RLM/BFD relaxation for deactivated SCG	vivo
R2-2300482	Discussion on msg1/msgA transmission channel access control in SIB1	Huawei, HiSilicon
R2-2300506	Discussion on remaining aspects for channel access	Ericsson
R2-2300507	Correction to RRC for 71 GHz	Ericsson
R2-2300515	Clarification on ensuring valid version of SIB17	Samsung R&D Institute India
R2-2300554	Correction to DC location signalling	Nokia, Nokia Shanghai Bell
R2-2300558	CP corrections for NR operation to 71GHz	ZTE Corporation, Sanechips
R2-2300606	Correction to RAN visible periodicity definition	Huawei, HiSilicon
R2-2300630	Miscellaneous corrections for Rel-17 RRC	Lenovo
R2-2300778	DRAFT Reply LS on msg1/msgA transmission channel access control	Qualcomm Incorporated
R2-2300780	Channel Access Control for msg1/msgA in FR2-2	Qualcomm Incorporated
R2-2300791	Correction on TRS availability handling	Huawei, HiSilicon
R2-2300793	CR for clarification of the starting SFN of MUSIM aperiodic gap	Huawei, HiSilicon
R2-2300859	Discussion on MN Handover While the SCG is Deactivated	CATT
R2-2300860	Correction on scg-State in RRCConnectionReconfiguration including the mobilityControlInfo	CATT
R2-2300869	RA channel access mode in FR2-2	Nokia, Nokia Shanghai Bell
R2-2300898	Miscellaneous correction of NR RRC support for MUSIM	vivo
R2-2301008	Clarification on QoE configuration for Layer-2 based UE-to-Network Relay	Qualcomm Incorporated
R2-2301039	Correction on QoE reporting during PCell change	LG Electronics Inc.
R2-2301074	Aligning paging cause terminology between RAN2, CT1 and SA2	Huawei, HiSilicon
R2-2301104	Inclusion of SIB17 in Dedicated SIB request	Sony
R2-2301201	RLM and BFD relaxation when SCG is deactivated	Ericsson
R2-2301249	Correction on the access attempt associated NSAG info for RACH	CMCC
R2-2301250	Correction on the access attempt associated NSAG info for RACH	CMCC
R2-2301383	Correction on the field descriptions of nrofDownlinkSlots/nrofUplinkSlots	Samsung
R2-2301453	Correction to slice-support cell lists	Ericsson
R2-2301454	Dedicated and broadcast signalling of re-selection priorities	Ericsson
R2-2301457	Miscellaneous non-controversial corrections Set XVII	Ericsson
R2-2301618	Correction to conditional presence of parameters for SRB4	LG Electronics
R2-2301711	Further Clarification on the MUSIM Scheduling Gap Handling During Handover	ZTE Corporation, Sanechips
R2-2301786	Clarification on the BFD and RLM relaxation in the case of SCG deactivation	ZTE Corporation, Sanechips
R2-2301795	Correction on the access attempt associated NSAG info for RACH	CMCC
R2-2301830	Correction to security protection requirement for ULDedicatedMessageSegment	Google Inc.
R2-2301942	Reply LS on msg1/msgA transmission channel access control	RAN2
R2-2301985	Miscellaneous non-controversial corrections Set XVII	Ericsson (Rapporteur)
R2-2302108	Miscellaneous non-controversial corrections Set XVII	Ericsson (Rapporteur)
R2-2302114	Correction to slice-support cell lists	Ericsson
R2-2302172	CP corrections for NR operation to 71GHz	ZTE Corporation, Sanechips
R2-2302181	Clarification on ensuring valid version of SIB17	Samsung R&D Institute India
R2-2302206	Miscellaneous correction of NR RRC support for MUSIM	vivo
R2-2302207	Clarification on ensuring valid version of SIB17	Samsung, Sony
R2-2302236	Correction to security protection requirement for ULDedicatedMessageSegment	Google Inc.
R2-2302237	Correction to slice-support cell lists	Ericsson
R2-2302283	Corrections to Application layer measurement reporting procedure and alignment of terminologies	Lenovo
R2-2302293	Report of [AT121][014][PowSav] RLMBFD relaxation for SCG deactivation (vivo)	vivo
R2-2302294	Correction on RLMBFD relaxation for SCG deactivation	vivo

6.1.3.2: UE capabilities

TDoc	Title	Source
R2-2300014	LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#111 (R1-2212897; contact: NTT Docomo, AT&T)	RAN1
R2-2300052	LS on UE capability for network flag deriveSSB-IndexFromCellInter (R4-2220723; contact: CMCC)	RAN4
R2-2300060	LS on intraBandENDC-Support (R4-2220837; contact: Huawei)	RAN4
R2-2300141	Discussion on intrabandENDC	OPPO
R2-2300142	Discussion on UE capability ‘intraBandENDC-Support’	Qualcomm Incorporated
R2-2300143	DM-RS bundling for coverage enhancements	Qualcomm Incorporated
R2-2300443	Discussion on Capability for DMRS Bundling	Ericsson España S.A.
R2-2300612	Release-17 UE capabilities updates/corrections based on R1 and R4 feature lists (TS38.306)	Intel Corporation
R2-2300621	UE Feature List for Rel-17	Intel Corporation
R2-2300741	UE capability to indicate supporting flag deriveSSB-IndexFromCell-inter-r17	Apple
R2-2300770	Correction on NCSG gap pattern capability	MediaTek Inc., Apple, Intel Corporation
R2-2300789	RRC Correction on the capability for 1024QAM	Huawei, HiSilicon
R2-2300790	Correction on the capability for 1024QAM	Huawei, HiSilicon
R2-2301315	Discussion on UE capability for deriveSSB-IndexFromCellInter	ZTE Corporation, Sanechips
R2-2301464	UE capability to indicate supporting flag deriveSSB-IndexFromCell-inter-r17	Apple
R2-2301611	Discussion on intra-band EN-DC combination	Huawei, HiSilicon
R2-2301630	Discussion on network flag deriveSSB-IndexFromCellInter	CATT
R2-2301656	Non-NCSG UE capability for flag deriveSSB-IndexFromCellInter	Nokia, Nokia Shanghai Bell
R2-2301657	Non-NCSG UE capability for flag deriveSSB-IndexFromCellInter	Nokia, Nokia Shanghai Bell
R2-2301712	Further Consideration on the Intra-band EN-DC Capability	ZTE Corporation, Sanechips
R2-2301739	Correction on NCSG gap pattern capability	MediaTek Inc., Apple, Intel Corporation
R2-2301851	Further discussion on intraBandENDC-Support	MediaTek Inc.
R2-2301852	Support of mixed intra-band contiguous and non-contiguous EN-DC	MediaTek Inc.
R2-2301853	Support of mixed intra-band contiguous and non-contiguous EN-DC	MediaTek Inc.
R2-2301989	[Reserved]	[Reserved]
R2-2302025	Correction on the capability for 1024QAM	Huawei, HiSilicon
R2-2302056	Reply LS on reduced 1024QAM capability (R1-2302211; contact: Huawei)	RAN1
R2-2302077	Release-17 MBS UE capabilities based on latest R1 feature list (TS 38.306)	Intel Corporation
R2-2302078	Release-17 MBS UE capabilities based on latest R1 feature list (TS 38.331)	Intel Corporation
R2-2302220	Release-17 UE capabilities updates/corrections based on R1 and R4 feature lists (TS38.306)	Intel Corporation
R2-2302221	UE Feature List for Rel-17	Intel Corporation
R2-2302239	Editorial corrections to Release-15 UE capabilities (TS38.306)	Intel Corporation
R2-2302240	Editorial corrections to Release-16 UE capabilities (TS38.306)	Intel Corporation
R2-2302256	Release-17 UE capabilities updates/corrections based on latest R1 and R4 feature lists (TS38.306)	Intel Corporation
R2-2302276	Introducing deriveSSB-IndexFromCellInter capability for non-NCSG UEs	ZTE Corporation, Apple, Nokia, CMCC
R2-2302277	Introducing deriveSSB-IndexFromCellInter capability for non-NCSG UEs	ZTE Corporation, Apple, Nokia, CMCC

6.1.3.3: Other

TDoc	Title	Source
R2-2300310	Discussion on PEI monitoring for L2 U2N Remote UE	vivo
R2-2300792	Clarification on the DRX cycle for the misalignment issue in RRC_INACTIVE state	Huawei, HiSilicon
R2-2301080	Clarification on desired IAB-MT PSD range	ZTE, Sanechips
R2-2301124	Corrections on the inter-CU routing and header rewriting for eIAB	Huawei, HiSilicon
R2-2301125	Correction to add the missing eIAB MAC CEs	Huawei, HiSilicon
R2-2301200	Power saving during an emergency PDU session	Ericsson
R2-2301208	Correction to 38.321 on Integrated Access and Backhaul for NR Rel-17 concerning DL TX power adjustment range extension	Samsung
R2-2301300	Clarification on DL TX Power Adjustment range	Ericsson
R2-2301482	PEI handling during emergency services	Huawei, HiSilicon
R2-2301838	Coexistance of PEI in case of SL relay	Ericsson
R2-2301840	Clarification on configuration of SDT with SL relay	Ericsson
R2-2301946	LS on Mapping of F1-C IP addresses in the IAB inter-CU topology adaptation and backhaul RLF recovery procedures (S3-231603; contact: Qualcomm)	SA3
R2-2301950	Corrections on the inter-CU routing and header rewriting for eIAB	Huawei, HiSilicon
R2-2302281	LS on the use of PEI during an emergency PDU session	Ericsson
R2-2302302	LS on the use of PEI during an emergency PDU session	RAN2

6.2.1: Organizational and Stage-2 corrections

TDoc	Title	Source
R2-2300008	LS on the RRC parameter for multicast HARQ-ACK feedback (R1-2210703; contact: Huawei)	RAN1
R2-2300039	LS on potential de-synchronisation of a multicast MRB’s PDCP HFN and SN (R3-226903; contact: Ericsson)	RAN3
R2-2300193	MBS corrections for 38.300	CATT, CBN
R2-2302055	Reply LS on SPS configuration for unicast and multicast (R1- 2302209; contact: ASUSTek)	RAN1
R2-2302093	MBS corrections for multicast configuration and service continuity	CATT, CBN
R2-2302225	MBS corrections for 38.300	CATT, CBN

6.2.2: CP corrections

TDoc	Title	Source
R2-2300194	Corrections to TS 38.331	CATT, CBN
R2-2300195	Discussions on Remaining Issues of MBS	CATT
R2-2300795	Discussion on MBS Support within NPN	vivo Mobile Com. (Chongqing)
R2-2300796	Further Discussion on Multicast Session ID Configuration	vivo Mobile Com. (Chongqing)
R2-2300870	PLMN-Index usage and SNPN with MBS	Nokia, Nokia Shanghai Bell
R2-2301120	Clarification on DCI enabled Multicast HARQ feedback	Samsung R&D Institute India
R2-2301132	Clarification on MBS neighbour cell list	Samsung
R2-2301159	Discussion on the plmn-index usage for multicast	Huawei, CBN, HiSilicon
R2-2301160	MBS support for NPN	Huawei, CBN, HiSilicon
R2-2301202	Miscellaneous clarifications for MBS	Ericsson
R2-2301203	MBS and NPN	Ericsson
R2-2301204	MBS reception when eDRX or MICO mode is configured	Ericsson
R2-2301669	MBS corrections for RRC Release procedure	Sharp
R2-2301690	Discussion and TP on the MBS support in NPN scenario	Beijing Xiaomi Software Tech
R2-2301750	MBS neighbour cell list signalling	Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Sanechips, Huawei, HiSilicon, Qualcomm Incorporated
R2-2301755	Discussion on Supporting MBS services through SNPN	Samsung Electronics Czech
R2-2301779	CR to TS 38.331 on MBS neighbour cell list	ZTE, Nokia, Ericsson, Nokia Shanghai Bell, Qualcomm Inc., Huawei, Sanechips
R2-2301780	Misc CR to TS 38.331 on NR MBS	ZTE, Sanechips
R2-2301781	Correction options on RedCap and SNPN support of NR MBS in Rel-17	ZTE, Sanechips
R2-2301806	Correction to UL configuration for multicast MRB	Google Inc.
R2-2302086	Report of [AT121][601][MBS-R17] NPN and PLMN ID (Huawei)	Huawei, HiSilicon
R2-2302087	Report of [AT121][602][MBS-R17] Remaining RRC CRs (Huawei)	Huawei, HiSilicon
R2-2302088	iscellaneous RRC corrections for MBS	Huawei, ZTE, Google Inc., Sharp, CATT, CBN, Sanechips, HiSilicon
R2-2302094	Miscellaneous RRC corrections for MBS	Huawei, ZTE, Google Inc., Sharp, CATT, CBN, Ericsson, Sanechips, HiSilicon

6.2.3: UP corrections

TDoc	Title	Source
R2-2300299	MBS multicast MRB desync of PDCP COUNT	Nokia, Nokia Shanghai Bell
R2-2301118	Answers to the RAN3 LS on de-synchronisation of MRB HFN and SN	Xiaomi
R2-2301161	MBS user plane Issues	Huawei, CBN, HiSilicon
R2-2301459	MAC Corrections on MBS	vivo
R2-2301731	Clarification on DRX for retransmission of multicast SPS	LG Electronics Inc.
R2-2301732	Clarification on HARQ feedback transmission for the first multicast SPS transmission	LG Electronics Inc.
R2-2302089	[DRAFT] Reply LS on potential de-synchronisation of a multicast MRB’s PDCP HFN and SN	Nokia
R2-2302090	Report of [AT121][604][MBS-R17] Remaining UP issues	vivo
R2-2302091	MBS MAC Corrections	vivo, Huawei, LG Electronics Inc., HiSilicon
R2-2302092	Reply LS on potential de-synchronisation of a multicast MRB’s PDCP HFN and SN	RAN2
R2-2302095	MBS MAC Corrections	vivo, Huawei, LG Electronics Inc., HiSilicon

6.3.2: User Plane

TDoc	Title	Source
R2-2301884	Corrections on one shot HARQ feedback	ASUSTeK

6.4.1: User plane common aspects

TDoc	Title	Source
R2-2300114	Correction to misc issues to MAC spec for Small Data Transmission	Huawei, HiSilicon
R2-2300184	DTCH MAC SDU in MsgB and Msg4	Samsung Electronics Co., Ltd
R2-2300449	Changing the wording for TA reference derivation	Ericsson España S.A.
R2-2300513	MAC Corrections on SDT	vivo
R2-2300776	CR for Miscellaneous Corrections for SDT operation	LG Electronics.
R2-2300803	Corrections on RNTI usage for SDT	NEC, Huawei, HiSilicon
R2-2301280	Corrections for 2-step RA-SDT	Ericsson España S.A.
R2-2301831	Correction to RA-SDT	Google Inc.
R2-2302103	Correction to RA-SDT	Google Inc.
R2-2302179	Corrections for 2-step RA-SDT	Ericsson, LGE
R2-2302184	Corrections for RA-SDT and CG-SDT	Ericsson, NEC, Huawei, LGE

6.4.2: Control plane common aspects

TDoc	Title	Source
R2-2300376	Clarification on pending UL NAS message transmission during SDT	MediaTek Inc.
R2-2300566	SDT CP corrections	ZTE Corporation, Sanechips
R2-2300604	Consideration on UDC and EHC applicability after SDT	Huawei, HiSilicon
R2-2300607	Correction to SI acquisition during SDT	Huawei, HiSilicon
R2-2300771	RRC Clarification on SDT	vivo
R2-2300775	Clarification for SDT configuration	LG Electronics.
R2-2301282	Correction on unsuccessful SDT events	Nokia, Nokia Shanghai Bell
R2-2301283	Correction on RRCReject handling for SDT	Nokia, Nokia Shanghai Bell
R2-2301808	Clarification on SDT-Config in the inter-node message	Google Inc.
R2-2302102	Correction on unsuccessful SDT events	Nokia, Nokia Shanghai Bell
R2-2302104	Correction on RRCReject handling for SDT	Nokia, Nokia Shanghai Bell
R2-2302171	SDT CP corrections	ZTE Corporation, Sanechips, Huawei, HiSilicon

6.5.1: General and stage 2 corrections

TDoc	Title	Source
R2-2301223	Correction to 38.300 on SRAP operation	Samsung

6.5.2: Control plane corrections

TDoc	Title	Source
R2-2300137	Discussion on left issues for CP	OPPO
R2-2300388	Correction on remote UE's resource allocation	Xiaomi, Ericsson, CATT, ZTE
R2-2300389	Correction on 38.331	Xiaomi
R2-2300686	Correction on SRAP entity release	vivo
R2-2300863	Issues on L2 ID(s) for D2I path switching of L2 U2N relay	CATT
R2-2300864	LS on L2 ID issue for D2I path switching of L2 U2N relay	CATT
R2-2300865	Correction on the Description of RRC Functions	CATT
R2-2300998	Correction in Remote UE synchronization	Nokia, Nokia Shanghai Bell
R2-2301017	Correction on Sidelink Synchronisation Reference	Ericsson España S.A.
R2-2301019	Correction on Field Description for SRAP Config	Ericsson España S.A.
R2-2301121	Miscellaneous corrections to TS 38.331 for SL relay	ZTE Corporation, Sanechips
R2-2301122	Corrections on SL discovery	ZTE Corporation, Sanechips
R2-2301167	Correction for receiving PC5 unicast link release during path switching	Lenovo
R2-2301174	Correction for Uu message transfer procedure	Lenovo
R2-2301175	Clarification on dl-P0-PSBCH, dl-P0-PSSCH-PSCCH and dl-P0-PSFCH for OoC Remote UE	Huawei, HiSilicon
R2-2301212	Discussion on Sidelink Synchronization Reference	Ericsson España S.A.
R2-2301922	Summary of agenda item 6.5.2 on relay control plane (Huawei)	Huawei
R2-2302134	Miscellaneous correction to SL Relay	Huawei, HiSilicon, CATT, ZTE, Lenovo, Ericsson España S.A.
R2-2302190	Report of [AT121][407][Relay] Miscellaneous Rel-17 relay CP CR (Huawei)	Huawei, HiSilicon
R2-2302228	Corrections on SL Relay	ZTE Corporation, Sanechips
R2-2302232	Correction in Remote UE synchronization	Nokia, Nokia Shanghai Bell, Ericsson

6.5.3: User plane corrections

TDoc	Title	Source
R2-2300758	Correction on handling of unforeseen SRAP Data PDU	Apple
R2-2301123	Corrections on SRAP for SL relay	ZTE Corporation, Sanechips
R2-2301176	Correction to error handling in SRAP	Huawei, HiSilicon
R2-2301329	Correction on SRAP for L2 U2N Relay	Philips International B.V.
R2-2301351	SRAP layer corrections	Nokia, Nokia Shanghai Bell
R2-2301483	Correction on discovery message filtering	Huawei, HiSilicon
R2-2301527	Clarification on PDCP for L2 U2N Relay	ASUSTeK
R2-2301528	Clarification on data volume consideration for L2 U2N Relay	ASUSTeK
R2-2301548	PDCP PDU delivery to SRAP for sidelink relay	Nokia, Nokia Shanghai Bell
R2-2301919	Summary of AI 6.5.3 on user plane corrections (OPPO)	OPPO
R2-2302135	Corrections on SRAP for SL relay	ZTE Corporation, Sanechips
R2-2302136	Correction to error handling in SRAP	Huawei, HiSilicon
R2-2302137	SRAP layer corrections	Nokia, Nokia Shanghai Bell
R2-2302138	Correction on SRAP for L2 U2N Relay	Philips International B.V.
R2-2302139	Clarification on PDCP for L2 U2N Relay	ASUSTeK, Nokia, Nokia Shanghai Bell
R2-2302140	PDCP PDU delivery to SRAP for sidelink relay	Nokia, Nokia Shanghai Bell
R2-2302148	PDCP PDU delivery to SRAP for sidelink relay	Nokia, Nokia Shanghai Bell
R2-2302149	Summary of [AT121][408][Relay] Wording for Rel-17 relay UP CRs (OPPO)	OPPO
R2-2302150	38.351 SRAP corrections	Nokia, Nokia Shanghai Bell
R2-2302195	Correction on discovery message filtering	Huawei, HiSilicon
R2-2302233	Correction on SRAP for L2 U2N Relay	Philips International B.V.

6.6.1: General and Stage 2 corrections

TDoc	Title	Source
R2-2300018	Reply LS on validity of assistance information (R1-2212984; contact: OPPO)	RAN1
R2-2300043	LS to RAN2 on inter-operability testing (IOT) bit for inter-satellite measurement (R4-2220425; contact: MediaTek)	RAN4
R2-2300044	LS on capability description for enhanced cell reselection requirements in NTN (R4-2220427; contact: Nokia)	RAN4
R2-2300057	Reply LS on enhanced cell reselection requirements (R4-2220741; contact: Huawei)	RAN4
R2-2300123	Correction on Stage-2 descriptions for NR NTN	vivo, Nokia, Nokia Shanghai Bell
R2-2300166	NTN Stage-2 correction	OPPO
R2-2300271	[Draft] Reply LS on inter-operability testing (IOT) bit for inter-satellite measurement	MediaTek Inc.
R2-2300471	[DRAFT] Response LS on enhanced cell reselection requirements in NTN	Nokia, Nokia Shanghai Bell
R2-2300881	Clarification on support of TN NTN mobility during RRC_INACTIVE	Qualcomm Incorporated
R2-2301139	Corrections on neighboring cell measurement	ZTE Corporation, Sanechips
R2-2301445	Corrections to 38.300 related to Section Scheduling and Timing	THALES
R2-2301685	Corrections on the description related to the timing advance pre-compensation	CATT
R2-2301966	Response LS on enhanced cell reselection requirements in NTN	RAN2
R2-2301967	Correction on Stage-2 descriptions for NR NTN	vivo, Nokia, Nokia Shanghai Bell

6.6.2: UP corrections

TDoc	Title	Source
R2-2300124	Corrections to NR Non-Terrestrial Networks (NTN) for TS 38.321	vivo
R2-2300729	Clarification on CG-SDT Timer in NTN	Apple
R2-2301157	Clarification on UE behaviour when the validity timer expires	Huawei, HiSilicon
R2-2301636	Clarification on HARQ feedback transmission after SPS activation	LG Electronics Inc.
R2-2301658	Corrections on MAC procedure upon validity timer expiry	Nokia, Nokia Shanghai Bell
R2-2301704	Preamble Group Selection for TA Reporting	Google Inc.
R2-2301974	Clarification on HARQ feedback transmission after SPS activation	LG Electronics Inc.
R2-2301983	Corrections to NR NTN for 38.321	LG Electronics Inc., vivo

6.6.3: CP corrections

TDoc	Title	Source
R2-2300125	Remaining issue on PDD reporting	vivo, Samsung, Huawei, HiSilicon
R2-2300168	RRC correction on epochTime and distanceThreshold	OPPO
R2-2300169	RRC correction on inactiveStateNTN	OPPO
R2-2300201	Correction for RLC-Config-v1700	RadiSys
R2-2300202	Correction for RLC-Config-v1700	RadiSys
R2-2300213	Additional IE inclusion within SI-SchedulingInfo-v1700	RadiSys
R2-2300218	Additional IE inclusion within SI-SchedulingInfo-v1700	RadiSys
R2-2300219	Correction in Need Code for cellSpecificKoffset-r17 and kmac-r17 in NTN-Config-r17	RadiSys
R2-2300234	Remaining issues on SMTC	Huawei, HiSilicon, vivo, Samsung
R2-2300235	CR to 38.304 on relaxed measurements	Huawei, HiSilicon
R2-2300236	CR to 38.331 on event D1	Huawei, HiSilicon
R2-2300267	Correction on missing referencing of the NTN spec in 38.331	MediaTek Inc.
R2-2300268	Correction on missing referencing of the NTN spec in 38.306	MediaTek Inc.
R2-2300269	IOT bit for inter satellite measurement (38.306)	MediaTek Inc.
R2-2300270	IOT bit for inter satellite measurement (38.331)	MediaTek Inc.
R2-2300301	Correction in Need Code for UplinkHARQ-mode-r17 and DownlinkHARQ-FeedbackDisabled-r17	RadiSys
R2-2300302	Correction in Need Code for UplinkHARQ-mode-r17 and DownlinkHARQ-FeedbackDisabled-r17	RadiSys
R2-2300365	Correction on NR NTN UE capability for enhanced measurement requirements for cell reselection	Intel Corporation
R2-2300370	Clarification on NR NTN UE capability eventA4BasedCondHandover-r17	Intel Corporation
R2-2300470	Correction to Enhanced RRM requirements for NTN measurements in IDLE and INACTIVE	Nokia, Nokia Shanghai Bell
R2-2300472	On T430 and epochTime related aspects	Nokia, Nokia Shanghai Bell
R2-2300614	Handling of features with different UE support in TN and NTN	Intel Corporation
R2-2300730	Clarification on measurement relaxation in NTN	Apple
R2-2300879	Clarification on TN EUTRA capability reporting	Qualcomm Incorporated
R2-2300880	Clarification on use of feature upon TN NTN mobility during RRC_INACTIVE	Qualcomm Incorporated
R2-2300910	NR NTN Rel-17 neighbor cell measurements	Ericsson
R2-2301042	Clarification on essential SIB19 for NR NTN	Xiaomi, CAICT, Lenovo, Samsung, MediaTek, Apple, OPPO, CATT, CMCC, Qualcomm
R2-2301137	Clarification on neighboring cell measurements for NTN	ZTE Corporation, Sanechips
R2-2301138	Corrections on neighboring cell measurement	ZTE Corporation, Sanechips
R2-2301392	Correction on missing referencing of the NTN spec in 38.306	Mediatek Inc.
R2-2301436	Correction related to a missing description of a parameter of the number of HARQ processes	Thales
R2-2301476	Discussion on IoT bit for inter-satellite measurement	Samsung Research America
R2-2301477	Correction for NR NTN on reconfiguration with sync	Samsung
R2-2301478	Correction for NR NTN on relaxed measurement	Samsung
R2-2301529	Clarification on T430 handling for target cell	ASUSTeK
R2-2301686	Corrections on the relaxed cell reselection requirements	CATT
R2-2301687	Discussion on the RAT type of TN and NTN	CATT
R2-2301703	Skip Measurements of a Neighbour Frequency or Cell	Google Inc.
R2-2301847	Clarification on measurement relaxation target for NTN	LG Electronics Inc.
R2-2301848	Clarification on measurement relaxation source for NTN	LG Electronics France
R2-2301969	IOT bit for inter satellite measurement (38.331)	MediaTek
R2-2301970	CR to 38.304 on relaxed measurements	Huawei, HiSilicon
R2-2301971	RRC correction on epochTime	OPPO
R2-2301972	[AT121][103][NR NTN] Neighbour cell measurements (Ericsson)	Ericsson
R2-2301973	[AT121][116][NR NTN] CP corrections (Samsung)	Samsung
R2-2301975	Clarification on use of feature upon TN NTN mobility during RRC_INACTIVE	Qualcomm Incorporated, Intel Corporation, OPPO
R2-2301980	Correction to PDD reporting	vivo, Samsung, Huawei, HiSilicon
R2-2301981	CR to 38.304 on relaxed measurements	Huawei, HiSilicon
R2-2301982	Corrections on satellite ephemeris indication	Ericsson
R2-2301984	Clarification on measurement relaxation in NTN	Apple, Samsung
R2-2301988	IOT bit for inter satellite measurement (38.306)	MediaTek
R2-2301995	Clarification on use of feature upon TN NTN mobility during RRC_INACTIVE	Qualcomm Incorporated, Intel Corporation, OPPO

6.7.1: General and stage 2 corrections

TDoc	Title	Source
R2-2300041	Reply LS on support of positioning in FR2-2 (R4-2220391; contact: Huawei)	RAN4
R2-2300042	Reply LS on capability for PRS measurement without MG (R4-2220392; contact: CATT)	RAN4
R2-2300053	Reply LS on applicability of timing error margin of Rx TEG (R4-2220729; contact: Ericsson)	RAN4
R2-2300217	Corrections to stage 2 descriptions for NR positioning	Lenovo
R2-2300415	Miscellaneous corrections for Positioning Stage2	Intel Corporation
R2-2300416	Miscellaneous corrections for Positioning Stage2	Intel Corporation
R2-2300673	38.305 CR for miscellaneous corrections	vivo
R2-2300933	Correction on the gNB's behaviour for pre-configured MG	ZTE Corporation
R2-2301619	Corrections on TS38.305	CATT
R2-2301999	Reply LS on applicability of timing error margin of Rx TEG (R4-2303244; contact: CATT)	RAN4
R2-2302129	Corrections to stage 2 descriptions for NR positioning	Lenovo
R2-2302188	[AT121][406][POS] Remaining Rel-17 stage 2 issues (Intel)	Intel Corporation
R2-2302189	Miscellaneous corrections for Positioning Stage2	Intel Corporation, Ericsson
R2-2302247	Miscellaneous corrections for Positioning Stage2	Intel Corporation, Ericsson, ZTE

6.7.2: RRC corrections

TDoc	Title	Source
R2-2301303	Discussion on NW configuration for UL MAC CE	Ericsson, Huawei, Hi-Silicon, Intel Corporation
R2-2301304	RRC Configuration for Positioning Measurement Gap Activation/Deactivation Request MAC CE	Ericsson, Huawei, HiSilicon, Intel Corporation
R2-2302113	RRC Configuration for Positioning Measurement Gap Activation/Deactivation Request MAC CE	Ericsson, Huawei, HiSilicon, Intel Corporation
R2-2302192	[AT121][403][POS] Network control for MG activation/deactivation UL MAC CE	Ericsson
R2-2302226	RRC Configuration for Positioning Measurement Gap Activation/Deactivation Request MAC CE	Ericsson, Huawei, HiSilicon, Intel Corporation

6.7.3: LPP corrections

TDoc	Title	Source
R2-2300106	Correction on QCL information for On-demand PRS	Huawei, HiSilicon
R2-2300111	Miscellaneous Corrections to LPP	Huawei, HiSilicon
R2-2300112	Correction to UE capability for MG (de-)activation	Huawei, HiSilicon, Ericsson
R2-2300414	Miscellaneous corrections for Positioning capabilities	Intel Corporation
R2-2300674	Change request about UE capability for PRS measurement within a PPW	vivo
R2-2300934	Correction on the scheduled location time	ZTE Corporation
R2-2301809	Clarification of FR2-2 capability support of subcarrier spacing for the DL PRS resource	Ericsson
R2-2301829	Correction to UE capability for MG (de-)activation	Huawei, HiSilicon, Ericsson, Intel
R2-2301900	Summary of AI 6.7.3 - NR positioning enhancements, LPP corrections	Qualcomm Incorporated
R2-2302130	Miscellaneous Corrections to LPP	Huawei, HiSilicon
R2-2302131	Correction to UE capability for PRS measurement within a PPW	vivo
R2-2302132	Miscellaneous corrections for Positioning capabilities	Intel Corporation
R2-2302227	Correction to UE capability for MG (de-)activation	Huawei, HiSilicon, Ericsson, Intel
R2-2302279	Correction to UE capability for MG (de-)activation	Huawei, HiSilicon, Ericsson, Intel

6.7.4: MAC corrections

TDoc	Title	Source
R2-2300113	Correction to validation for INACTIVE posSRS transmission	Huawei, HiSilicon
R2-2300280	Correction to posMG (de-)activation request	Huawei, HiSilicon, Ericsson
R2-2300935	Correction on uplink TA maintenance for positioning	ZTE Corporation
R2-2300936	Correction to MAC spec for positioning	ZTE Corporation
R2-2301815	Correction for trigger condition of Scheduling Request	Ericsson
R2-2301828	Correction to PosMG Activation/Deactivation Request	Huawei, HiSilicon, Ericsson, Intel
R2-2301832	Correction to validation for INACTIVE posSRS transmission	Huawei, HiSilicon
R2-2302121	Summary of AI 6.7.4 for POS MAC corrections	Huawei, Hi-Silicon
R2-2302193	[AT121][405][POS] Editorial MAC issues and interaction with PHY (Huawei)	Huawei, HiSilicon
R2-2302194	Correction to validation for INACTIVE posSRS transmission	Huawei, HiSilicon
R2-2302196	Correction on uplink TA maintenance for positioning	ZTE Corporation
R2-2302231	Correction to PosMG Activation/Deactivation Request	Huawei, HiSilicon, Ericsson, Intel
R2-2302235	Correction to INACTIVE posSRS transmission	Huawei, HiSilicon, ZTE

6.8.1: General

TDoc	Title	Source
R2-2300173	Discussion on CG-SDT for RedCap Ues	OPPO

6.8.2: CP corrections

TDoc	Title	Source
R2-2300157	Correction on offset for cell specific RSRP thresholds for 1Rx Redcap UE	OPPO
R2-2300172	Correction on eDRX	OPPO
R2-2300183	CG-SDT for RedCap UEs	Samsung Electronics Co., Ltd
R2-2300190	Discussion on SSB for SDT procedures in RedCap-specific initial BWP	Qualcomm Incorporated
R2-2300191	Correction to control plane procedures for RedCap UEs	Qualcomm Incorporated
R2-2300192	Correction to A1 and A2 events for RedCap UEs	Qualcomm Incorporated
R2-2300311	Correction on 38.304 for RedCap	vivo, Guangdong Genius
R2-2300312	Correction on RACH configure for RedCap	vivo, Qualcomm, ZTE Corporation, Guangdong Genius
R2-2300556	SDT for REDCAP UEs on BWP without CD-SSB	ZTE Corporation, Sanechips, vivo
R2-2300557	Corrections for SDT operation for REDCAP without CD-SSB	ZTE Corporation, Sanechips, vivo
R2-2301134	Corrections for eDRX on IDLE eDRX cycle	Huawei, HiSilicon
R2-2301135	Correction for hyperSFN on SI update	Huawei, HiSilicon
R2-2301136	Correction on the RedCap UE capability of supportOfRedCap	Huawei, HiSilicon
R2-2301284	CG-SDT on RedCap specific initial BWP	Nokia, Nokia Shanghai Bell
R2-2301316	Correction on RRC configuration for RedCap	ZTE Corporation, Sanechips
R2-2301330	Correction on eDRX	Nokia, Nokia Shanghai Bell
R2-2301513	Clarification on BWP capabilities of RedCap UEs	T-Mobile USA Inc.
R2-2301688	Correction on the filed descriptions of NeedForGaps in 38.331	CATT, ZTE, vivo
R2-2301689	Discussion on the CG-SDT configuration for RedCap UE	CATT
R2-2301694	Initial BWP for RedCap UEs configured with RA and CG-SDT	Ericsson
R2-2301727	SDT support in RedCap-specific initial BWP without CD-SSB	LG Electronics Inc.
R2-2301728	Issues on dedicated configuration of RedCap-specific initial BWP	LG Electronics Inc.
R2-2301954	Corrections for SDT operation for REDCAP without CD-SSB	ZTE Corporation, Sanechips, vivo
R2-2301955	Corrections to control plane procedures for RedCap UEs	Qualcomm Incorporated
R2-2301956	Corrections for SDT operation for REDCAP without CD-SSB	ZTE Corporation, Sanechips
R2-2301957	Correction on RACH configuration for RedCap	vivo, Qualcomm, ZTE Corporation, Intel Corporation, Guangdong Genius
R2-2301958	Correction on RRC configuration for RedCap	ZTE Corporation, Sanechips
R2-2301959	Clarification on BWP capabilities of RedCap UEs	T-Mobile USA Inc.
R2-2301960	Correction on the filed descriptions of NeedForGaps in 38.331	CATT, ZTE, vivo
R2-2301961	Summary of [AT121][109][RedCap] eDRX corrections (OPPO)	OPPO
R2-2302038	Correction on eDRX	Nokia, Nokia Shanghai Bell
R2-2302043	Corrections for SDT operation for REDCAP without CD-SSB	ZTE Corporation, Sanechips, Vivo, Mediatek, China Unicom, China Telecom
R2-2302044	Corrections for SDT operation for REDCAP without CD-SSB	ZTE Corporation, Sanechips, Vivo, Mediatek, China Unicom, China Telecom
R2-2302100	Correction on RRC configuration for RedCap	ZTE Corporation, Sanechips
R2-2302117	Corrections for SDT operation for REDCAP without CD-SSB	ZTE Corporation, Sanechips, Vivo, Mediatek, China Unicom, China Telecom
R2-2302118	UE capability for NCD SSB for REDCAP for SDT	ZTE Corporation, Sanechips, Vivo, Mediatek, China Unicom, China Telecom
R2-2302249	Clarification on BWP capabilities of RedCap UEs	T-Mobile USA, Qualcomm Incorporated
R2-2302280	Corrections for eDRX on IDLE eDRX cycle	Huawei, HiSilicon
R2-2302305	Corrections for SDT operation for REDCAP without CD-SSB	ZTE Corporation, Sanechips, Vivo, Mediatek, China Unicom, China Telecom
R2-2302306	UE capability for NCD SSB for REDCAP for SDT	ZTE Corporation, Sanechips, Vivo, Mediatek, China Unicom, China Telecom

6.8.3: UP corrections

TDoc	Title	Source
R2-2300313	BWP switch for SDT with seperate initial BWP	vivo, Guangdong Genius
R2-2301285	Correction on CG-SDT handling with RedCap specific initial BWP	Nokia, Nokia Shanghai Bell
R2-2301695	Clarification on the validity of SS-RSRP measurement for RedCap UEs with CG-SDT	Ericsson
R2-2301729	Correction on determination of whether the RedCap is applicable for RA procedure	LG Electronics.
R2-2301962	Correction SDT with separate initial BWP	Guangdong Genius

6.9.1: Stage-2

TDoc	Title	Source
R2-2300023	LS on M6 Delay Threshold (R3-224079; contact: CATT)	RAN3
R2-2300024	Reply LS on the user consent for trace reporting (R3-225250; contact: Nokia)	RAN3
R2-2300025	Reply LS on beam measurement reports (R3-225273; contact: Ericsson)	RAN3
R2-2300035	LS on Excess Packet Delay for MDT (R3-226873; contact: Huawei)	RAN3
R2-2300088	LS on Reply LS on beam measurement reports (S5-223524; contact: Ericsson)	SA5
R2-2300089	LS Reply on LS on M6 Delay Threshold (S5-227040; contact: Ericsson, Huawei)	SA5
R2-2300291	Miscellaneous Corrections on TS 37.320 for MDT	CATT
R2-2301944	Reply LS on the user consent for trace reporting (S3-231398; contact: Huawei)	SA3
R2-2301945	Reply LS on user consent of Non-public Network (S3-231399; contact: Vodafone)	SA3
R2-2302068	Miscellaneous corrections on TS 37.320 for MDT	CATT

6.9.3: SON Corrections

TDoc	Title	Source
R2-2300292	Correction on timeSinceCHO-Reconfig in TS 38.331	CATT
R2-2301272	User plane interruption time in SHR	Ericsson
R2-2301273	On inability to comply with the RRC Reconfiguration when being configured with conditional reconfiguration	Ericsson
R2-2301568	Correction on UE history information	Huawei, HiSilicon
R2-2301569	Correction on UE capability of SON	Huawei, HiSilicon
R2-2301580	Further discussion on PSCell MHI storage and RLF report content determination	Samsung Electronics Austria
R2-2302174	Correction to the handling of RLF-Report after successful HO	Ericsson

6.9.4: MDT Corrections

TDoc	Title	Source
R2-2301556	Correction on IDC issues in logged MDT	Samsung
R2-2301855	Introduction of packet loss rate with delay threshold	China Unicom, CMCC, CATT
R2-2301858	38.314 CR for the introduction of packet loss rate with delay threshold	China Unicom, CMCC, CATT
R2-2302079	Rel.17 SON/MDT RRC Corrections	Ericsson

6.10.1: Control plane corrections

TDoc	Title	Source
R2-2300138	Discussion on left issues on Tx Profile	OPPO, Ericsson, Huawei, HiSilicon, ZTE, Apple, CATT, vivo
R2-2300387	Correction on 38.331	Xiaomi
R2-2300504	Correction to 38300 on IUC	Ericsson
R2-2300894	Corrections on SL DRX and IUC	CATT
R2-2300911	Correction on description of IUC cast type	ZTE Corporation, Sanechips
R2-2301352	Correction to resource exclusion field description	Nokia, Nokia Shanghai Bell
R2-2301376	Correction on mode-1 trigger condition in SUI procedure	vivo
R2-2301458	Summary on control plan CRs	Huawei, HiSilicon
R2-2301530	Corrections on DRX timers for SL	ASUSTeK
R2-2301822	Correction for NR sidelink communication	Sharp
R2-2301825	Correction for Measurement Event Triggering Criteria	Sharp Corporation
R2-2302028	Miscellaneous corrections on TS 38.300 for NR sidelink	CATT, ZTE, Ericsson
R2-2302029	Summary of [AT121][504][V2X/SL] R17 38.300 corrections (CATT)	CATT
R2-2302030	Corrections on 38.331	Huawei, HiSilicon (Rapporteur), vivo, Xiaomi, Sharp Corporation, Nokia, Nokia Shanghai Bell, OPPO
R2-2302031	Summary of [AT121][505][V2X/SL] R17 RRC corrections (Huawei)	Huawei, HiSilicon
R2-2302045	Miscellaneous corrections on TS 38.300 for NR sidelink	CATT, ZTE, Ericsson
R2-2302211	Corrections on PSBCH Symbols number for NR sidelink	CATT, Sharp
R2-2302212	Corrections on PSBCH Symbols number for NR sidelink	CATT, Sharp
R2-2302246	Miscellaneous corrections on TS 38.300 for NR sidelink	CATT, ZTE, Ericsson

6.10.2: User plane corrections

TDoc	Title	Source
R2-2300012	LS on cast types for IUC scheme 1 (R1-2212822; contact: LGE)	RAN1
R2-2300130	Discussion on left issues on user plane procedure	OPPO
R2-2300131	Corrections on user plane for SL enhancement	OPPO
R2-2300487	Corrections on TS 38.321 for SL enhancements	Huawei, HiSilicon
R2-2300488	GC and BC transmission for IUC information	Huawei, HiSilicon
R2-2300503	discussion on IUC aspects in case of GC and BC	Ericsson
R2-2300505	Correction to 38331 on IUC	Ericsson
R2-2300755	Discussion on the MAC layer procedure for non-preferred resource set	Apple, Ericsson, ZTE, Intel, Qualcomm, Huawei, HiSilicon, OPPO, InterDigital
R2-2300756	Correction on the handling of IUC with non-preferred resource set	Apple, Ericsson, ZTE, Intel, Qualcomm, Huawei, HiSilicon, OPPO, InterDigital
R2-2300757	Discussion on IUC broadcast and groupcast	Apple
R2-2300838	Discussion on the remaining issues for NR sidelink	Xiaomi
R2-2300839	Miscellaneous corrections on TS 38.321 for NR sidelink	Xiaomi
R2-2300895	Correction on SL IUC Information and Request MAC CE	CATT
R2-2300896	Discussion on the cast type of IUC scheme 1	CATT
R2-2300912	Miscellaneous Correction on MAC for IUC	ZTE Corporation, Sanechips
R2-2300913	Correction on restriction of using IUC information	ZTE Corporation, Sanechips
R2-2301353	IUC open issues	Nokia, Nokia Shanghai Bell
R2-2301375	Clarification on IUC related transmission	vivo
R2-2301473	BC/GC for IUC transmission	Samsung Research America
R2-2301531	Correction on IUC request MAC CE	ASUSTeK
R2-2301620	Correction on number of MAC CEs in a MAC PDU	Sharp
R2-2301724	Discussion on L2 ID for GC/BC IUC	LG Electronics France
R2-2301745	User plane corrections on NR Sidelink enhancements	LG
R2-2301927	Summary on user plan CRs	LG Electronics
R2-2302032	R17 MAC corrections	LG, Apple
R2-2302033	Summary of [AT121][506][V2X/SL] R17 MAC corrections (LG)	LG
R2-2302034	[Draft] Reply LS on cast types for IUC scheme 1	Apple
R2-2302041	Reply LS on cast types for IUC scheme 1	RAN2
R2-2302046	R17 MAC corrections	LG, Apple
R2-2302050	Reply LS to RAN2 on default CBR configuration (R1-2302174; contact: OPPO)	RAN1

6.11.1: RRC centric Corrections

TDoc	Title	Source
R2-2300906	Misc clarifications for feMIMO RRC	Ericsson
R2-2301112	Corrections on the unified TCI-state configuration for 38.331	Xiaomi
R2-2301361	FeMIMO control plane issues in TS 38.331 and TS 38.306	Huawei, HiSilicon
R2-2301675	Corrections on feMIMO	CATT
R2-2302037	Corrections on the unified TCI-state configuration for cross cell referencing	Ericsson, Huawei
R2-2302110	Correction on codebook mode configuration for Rel-17 NCJT CSI measurement	Huawei, HiSilicon
R2-2302201	Correction on BWP for CSI-RS in TCI-State	Huawei, HiSilicon
R2-2302202	Correction on codebook mode configuration for Rel-17 NCJT CSI measurement	Huawei, HiSilicon
R2-2302284	Corrections on feMIMO	CATT
R2-2302289	DRAFTLS on further questions on feMIMO RRC parameters	Ericsson
R2-2302295	LS on further questions on feMIMO RRC parameters	RAN2
R2-2302297	Corrections on feMIMO	CATT

6.11.2: MAC centric Corrections

TDoc	Title	Source
R2-2301023	Misalignment on the identity of the BFD-RS set	Fujitsu
R2-2301024	Correction to misalignment on the identity of the BFD-RS set	Fujitsu
R2-2301286	Correction on implicit BFD-RS change	Nokia, Nokia Shanghai Bell
R2-2301287	Correction on implicit BFD-RS change	Nokia, Nokia Shanghai Bell
R2-2301362	Correction for BFR on SpCell configured with two BFD-RS sets	Huawei, HiSilicon
R2-2302183	Correction on implicit BFD-RS change	Nokia, Nokia Shanghai Bell
R2-2302287	Correction to misalignment on the identity of the BFD-RS set	Fujitsu, Nokia, Nokia Shanghai Bell
R2-2302288	Clarification on BFD-RS configuration	Fujitsu, Nokia, Nokia Shanghai Bell
R2-2302296	Clarification on the Serving Cell configured with two BFD-RS sets	Fujitsu, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon

6.12: RACH indication and partitioning

TDoc	Title	Source
R2-2300772	MAC Corrections on RACH Partitioning	vivo Mobile Com. (Chongqing)
R2-2301288	Clarification on RA resource set applicability for NSAG	Nokia, Nokia Shanghai Bell

7.1: Common

TDoc	Title	Source
R2-2300845	CR to 36.331 on NPUSCH-ConfigDedicated-NB-v1700	Huawei, HiSilicon, ZTE Corporation, Sanechips
R2-2301310	Small corrections on coverage-based paging	ZTE Corporation, Sanechips
R2-2302011	Small corrections on coverage-based paging	ZTE Corporation, Sanechips, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, HiSilicon

7.2.1: General and Stage 2 corrections

TDoc	Title	Source
R2-2300069	Response to “Response to “Reply to LS on UE capability signaling for IoT-NTN”” (S2-2211431; contact: Vodafone)	SA2
R2-2300158	Discussion on TDD support in R17 IoT NTN	OPPO
R2-2300167	IoT-NTN Stage-2 correction	OPPO
R2-2300357	Stage-2 correction on TDD support for IoT NTN	OPPO
R2-2300495	Further considerations on AS deactivation due to discontinuous coverage	Telit Communications S.p.A.
R2-2301158	CR to 36.300 on neighbour cell measurements	Huawei, HiSilicon
R2-2301380	Correction related to AS deactivation due to discontinuous coverage	Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, Thales, Vodafone, Telit, BT, Telstra, Telecom Italia, Turkcell
R2-2301393	Considerations on AS deactivation due to discontinuous coverage	Deutsche Telekom, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, Thales, Vodafone, Telit, BT, Telstra, Telecom Italia, Turkcell
R2-2301863	Correction related to AS deactivation due to discontinuous coverage	Deutsche Telekom, ?okia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, Thales, Vodafone, Telit, BT, Telstra, Telecom Italia, Turkcell
R2-2301963	IoT-NTN Stage-2 correction	OPPO
R2-2301976	Correction related to AS deactivation due to discontinuous coverage	Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, Thales, Vodafone, Telit, BT, Telstra, Telecom Italia, Turkcell
R2-2302064	LS on UE capability signalling for IoT-NTN (R3-230951; contact: Vodafone)	RAN3

7.2.2: UP corrections

TDoc	Title	Source
R2-2300258	Misc corrections on MAC for IoT NTN	MediaTek Inc
R2-2300358	MAC correction on TDD support for IoT NTN	OPPO
R2-2300886	NB-IoT UE location Info in RLF report	Qualcomm Incorporated
R2-2300887	Correction on UE location information in NB-IoT RLF report	Qualcomm Incorporated
R2-2300888	Correction on figure clarifying HARQ RTT timer	Qualcomm Incorporated
R2-2301051	Clarification on the generation of TA reporting for IoT NTN	ZTE Corporation, Sanechips
R2-2301878	Correction for IoT NTN	Ericsson
R2-2301879	R17 IoT NTN user plane corrections	Ericsson
R2-2301964	[offline 111] UP corrections	MediaTek
R2-2301986	Correction on figure clarifying HARQ RTT timer	Qualcomm Inc.
R2-2301987	Clarification on the generation of TA reporting for IoT NTN	ZTE Corporation, Sanechips

7.2.3: CP corrections

TDoc	Title	Source
R2-2300237	Remaining issues on T317	Huawei, HiSilicon
R2-2300238	CR to 36.331 on UE capability update	Huawei, HiSilicon
R2-2300259	Miscellaneous corrections to TS 36.331 for IoT NTN	MediaTek Inc.
R2-2300260	Discussion on epoch time	MediaTek Inc.
R2-2300261	Correct the references for IoT NTN to 36.306	MediaTek Inc.
R2-2300367	Discussion on the deactivation of AS functions due to DC	Intel Corporation
R2-2300927	Analysis on Reference time estimation issues of implicit Epoch time	Nokia, Nokia Shanghai Bell
R2-2300928	RRC parameter alignment with RAN1 specification for pre-compensation gap configuration	Nokia, Nokia Shanghai Bell
R2-2301049	Clarification on reference to TS 36.108 for IoT NTN	ZTE Corporation, Sanechips
R2-2301050	Correction on handling of T317 timer during HO	ZTE Corporation, Sanechips
R2-2301388	Correction related to AS deactivation due to discontinuous coverage	Deutsche Telekom, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, Thales, Vodafone, Telit, BT, Telstra, Telecom Italia, Turkcell
R2-2301389	Miscellaneous correction for IoT-NTN	Nokia, Nokia Shanghai Bell
R2-2301390	Discussion on epoch time	Mediatek Inc.
R2-2301391	Correct the references for IoT NTN	MediaTek Inc
R2-2301490	Discussion on deactivation of AS and out-of-coverage monitoring in discontinuous coverage	Samsung Electronics Benelux BV
R2-2301491	Deactivation of AS and out-of-coverage monitoring in discontinuous coverage	Samsung Electronics Benelux BV
R2-2301492	UE supporting discontinuous coverage acquiring SIB32 in idle mode	Samsung Electronics Benelux BV
R2-2301865	Correction related to AS deactivation due to discontinuous coverage	Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, Thales, Vodafone, Telit, BT, Telstra, Telecom Italia, Turkcell
R2-2301965	[AT121][112][IoT NTN] CP corrections (Huawei)	Huawei, HiSilicon
R2-2301977	Correction related to AS deactivation due to discontinuous coverage	Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, Thales, Vodafone, Telit, BT, Telstra, Telecom Italia, Turkcell
R2-2301978	Miscellaneous corrections to TS 36.331 for IoT NTN	MediaTek Inc.
R2-2301979	Correction for T317 in the Timers table	Huawei, HiSilicon
R2-2302107	Miscellaneous corrections to TS 36.331 for IoT NTN	MediaTek Inc

8.1.1: Organizational

TDoc	Title	Source
R2-2300441	draft 306 CR of Network controlled repeater UE capability	Intel Corporation
R2-2300442	draft 331 CR of Network controlled repeater UE capability	Intel Corporation
R2-2301295	MAC impact of RAN1 agreements	Samsung R&D Institute UK
R2-2301317	Running 38.331 CR for R18 Network-controlled repeaters	ZTE Corporation
R2-2301345	Running 38.304 CR for R18 Network-controlled repeaters	CATT
R2-2301437	38.300 Running CR for NCR	Ericsson
R2-2301520	Introducing support for Network Controlled Repeaters to 38.321	Samsung R&D Institute UK
R2-2302057	LS to RAN2 on the RRC and MAC CE parameters for NCR (R1-2302227; contact: ZTE)	RAN1
R2-2302151	38.300 Running CR for NCR	Ericsson
R2-2302152	draft 306 CR of Network controlled repeater UE capability	Intel Corporation
R2-2302153	Running 38.331 CR for R18 Network-controlled repeaters	ZTE Corporation
R2-2302154	Running 38.304 CR for R18 Network-controlled repeaters	CATT
R2-2302157	draft 331 CR of Network controlled repeater UE capability	Intel Corporation

8.1.2: Signalling for side control information

TDoc	Title	Source
R2-2300303	NCR side control signalling for access link beam management	Nokia, Nokia Shanghai Bell
R2-2300348	Signalling design for the side control information	Huawei, HiSilicon
R2-2300759	Discussion on remaining issues on NCR	Apple
R2-2300899	Discussion on Semi-static NCR-Fwd ON-OFF Configuration	vivo
R2-2301011	Signalling for side control information	NEC
R2-2301085	Considerations on side control information	Sony
R2-2301318	Consideration on signalling for side control information	ZTE Corporation, Sanechips
R2-2301426	Signalling for NCR side control information	MediaTek Inc.
R2-2301590	Remaining issues on NCR	Kyocera
R2-2301591	Multi-beam and sub-band operation for NCR	Kyocera
R2-2301632	SMTC configuration for NR network-controlled repeaters	AT&T
R2-2301814	Signalling for NCR side control information	China Telecom
R2-2302155	[AT121][706][NCR] Access Link (Nokia)	Nokia, Nokia Shanghai Bell
R2-2302156	Report of [AT121][707][NCR] MAC-design (Huawei)	Huawei, HiSilicon

8.1.3: Other RAN2 aspects

TDoc	Title	Source
R2-2300304	NCR capabilities and RRC_IDLE functionality	Nokia, Nokia Shanghai Bell
R2-2300349	Discussion on the support of per-PLMN NCR and RRC states for NCR-MT	Huawei, HiSilicon
R2-2300439	Leftover issue of NCR functionality and capability	Intel Corporation
R2-2300639	Management of Network-controlled Repeater	Qualcomm Inc.
R2-2300808	Handling of NCR failure	Samsung Electronics Romania
R2-2300846	Discussion on state transition for NCR-MT	Fujitsu
R2-2300900	Discussion on the Remaining Issues of Side Control	vivo
R2-2300975	Discussion on RRC states for NCR-MT	Lenovo
R2-2300986	Discussion on remaining RAN2 aspects for NCR supporting	NEC
R2-2301025	Discussion on NCR-Fwd’s behaviours in NCR-MT RRC_INACTIVE	Fujitsu
R2-2301319	Consideration on NCR open issues	ZTE Corporation, Sanechips
R2-2301346	Functions and signaling to support NCR	CATT
R2-2301438	Discussion on capabilities and remaining issues for NCR	Ericsson
R2-2301439	Support of IDLE with RRCRelease for NCR	Ericsson
R2-2301496	On NCR RRC states and procedures related to idle mode	Samsung Electronics Benelux BV
R2-2301617	Resolving open issues for NCR	LG Electronics Inc.

8.1.4: Repeater management

TDoc	Title	Source
R2-2300440	Initial access signalling for NCR-MT	Intel Corporation
R2-2300976	Discussion on repeater management for NCR-MT	Lenovo

8.2.1: Organizational

TDoc	Title	Source
R2-2300009	Reply LS on Positioning Reference Units (R1-2212715; contact: CATT)	RAN1
R2-2300010	Reply LS on LPHAP information delivery to RAN (R1-2212725; contact: Huawei)	RAN1
R2-2300011	Reply LS on SRS in multiple cells (R1-2212728; contact: Huawei)	RAN1
R2-2300015	Reply LS on RAN dependency for Ranging/Sidelink Positioning (R1-2212926; contact: Xiaomi)	RAN1
R2-2300037	LS on Study on expanded and improved NR positioning (R3-226889; contact: Huawei)	RAN3
R2-2300046	LS on RRM agreements on expanded and improved NR positioning (R4-2220439; contact: Ericsson)	RAN4
R2-2300076	Reply LS on Reply LS on RAN dependency for Ranging/Sidelink Positioning (S2-2301464; contact: Xiaomi)	SA2
R2-2300079	Reply LS on SL positioning groupcast and broadcast (S2-2301786; contact: Qualcomm)	SA2
R2-2300081	LS on LPP message and supplementary service event report over a user plane connection between UE and LMF (S2-2301857; contact: Ericsson)	SA2
R2-2300084	Reply LS to LS on SL positioning groupcast and broadcast (S3-230430; contact: Apple)	SA3
R2-2300196	Work Plan for Rel-18 WI on Expanded and Improved NR Positioning	CATT, Intel, Ericsson
R2-2300409	Considerations on new SLPP specification	Intel Corporation
R2-2301047	Draft Reply LS on RAN dependency for Ranging & Sidelink Positioning	Xiaomi
R2-2301308	User Plane solution and draft LS response to SA2	Ericsson
R2-2301935	LS on the requirement on low power or high accuracy positioning (S2-2303414; contact: Huawei)	SA2
R2-2301937	LS on GNSS measurement of PRU for location correction (S2-2303743; contact: Inspur)	SA2
R2-2301938	LS on support of multiple Target UEs (S2-2303837; contact: Qualcomm)	SA2
R2-2301939	LS on PRU procedures (S2-2303861; contact: Qualcomm)	SA2
R2-2301996	LS on LPP message and supplementary service event report over a user plane connection between UE and LMF (C1-231129; contact: Ericsson)	CT1
R2-2302048	LS Reply on PRU Procedures (R1-2302146; contact: Qualcomm)	RAN1
R2-2302054	LS on 1-symbol PRS (R1-2302201; contact: ZTE)	RAN1
R2-2302076	LS on GNSS integrity requirement parameters definition (C4-230655; contact: Huawei)	RAN3
R2-2302141	Draft Reply LS on RAN dependency for Ranging & Sidelink Positioning	Xiaomi
R2-2302142	Draft Reply LS to SA2 on satellite access for PRUs	CATT
R2-2302147	[AT121][411][POS] SLPP specification (Intel)	Intel Corporation
R2-2302255	Reply LS on RAN dependency for Ranging & Sidelink Positioning	RAN2
R2-2302270	Reply LS to SA2 on satellite access for PRUs	RAN2

8.2.2: Sidelink positioning

TDoc	Title	Source
R2-2300117	Discussion on Sidelink Positioning	Huawei, HiSilicon
R2-2300197	Discussion on sidelink positioning methods	CATT
R2-2300198	Architecture and Signaling procedure on support of PC5-only and joint PC5-Uu scenarios	CATT
R2-2300254	Considerations on SLPP broadcast / groupcast and related aspects	Nokia Germany
R2-2300410	Support of sidelink positioning	Intel Corporation
R2-2300455	Further discussion on sidelink positioning	OPPO
R2-2300529	Sidelink Positioning Protocol (SLPP) Signaling and Procedures	Qualcomm Incorporated
R2-2300585	Considerations on anchor UE discovery, selection and utilization	Nokia Netherlands
R2-2300586	Considerations on SL positioning sessions and related aspects	Nokia Netherlands
R2-2300593	UE Positioning using Sidelink	Fraunhofer IIS, Fraunhofer HHI
R2-2300642	Discussion on transport layer of SLPP	Samsung
R2-2300662	Discussion on potential solutions for SL positioning	Spreadtrum Communications
R2-2300675	Discussion on sidelink positioning	vivo
R2-2300712	SL positioning groupcast and broadcast	Apple
R2-2300715	[DRAFT] Reply LS on SL positioning groupcast and broadcast	Apple
R2-2300810	Designing SLPP protocol in the session perspective	Samsung Electronics Romania
R2-2300932	Discussion on sidelink positioning	ZTE Corporation
R2-2301048	Discussion on SL positioning	Xiaomi
R2-2301067	On SL Positioning Protocol and Architectural Aspects	Lenovo
R2-2301086	Considerations on sidelink positioning	Sony
R2-2301262	Considerations on Sidelink positioning	CMCC
R2-2301305	Sidelink positioning	Ericsson
R2-2301350	Assistant UEs in Rel-18	MediaTek Inc.
R2-2301410	Considerations on sidelink positioning	Sony
R2-2301545	Considerations on Anchor UE selection in sidelink positioning	LG Electronics Inc.
R2-2301546	Considerations on session-based SLPP operation	LG Electronics Inc.
R2-2301792	Discussion on Sidelink positioning	InterDigital, Inc.
R2-2301885	View on SL ranging and positioning architecture and signalling procedures	CEWiT
R2-2301889	Procedures for Sidelink Positioning	Philips International B.V.
R2-2301890	Protocol considerations for Anchor UEs with(out) known location	Philips International B.V.
R2-2301911	Discussion on SL positioning	Xiaomi
R2-2301921	[Pre121][406] Summary of AI 8.2.2 Sidelink Positioning (Intel)	Intel Corporation
R2-2301924	Discussion on Anchor UE (Re)discovery (Re)Selection for sidelink positioning	KT Corp.
R2-2302143	Draft LS to SA2 on Sidelink positioning procedure	Intel
R2-2302191	Draft LS to SA2 on Sidelink positioning procedure	Intel Corporation
R2-2302260	Draft LS to SA2 on Sidelink positioning procedure	Intel Corporation
R2-2302285	LS to SA2 on Sidelink positioning procedure	RAN2

8.2.3: RAT-dependent integrity

TDoc	Title	Source
R2-2300116	Discussion on RAT-dependent Integrity	Huawei, HiSilicon
R2-2300200	Discussion on RAT-dependent integrity	CATT
R2-2300411	Integrity for RAT dependent positioning methods	Intel Corporation
R2-2300453	Consideration on RAT-dependent positioning integrity	OPPO
R2-2300530	Integrity of NR Positioning Technologies	Qualcomm Incorporated
R2-2300663	Discussion on solutions for integrity of RAT-dependent positioning techniques	Spreadtrum Communications
R2-2300676	Discussion on RAT-dependent integrity	vivo
R2-2300930	Discussion on RAT-dependent methods positioning integrity	ZTE Corporation
R2-2300960	Discussion on RAT-dependent integrity	Lenovo
R2-2301189	Discussion on RAT-dependent positioning integrity	Xiaomi
R2-2301238	Discussion on the integrity issues	CMCC
R2-2301307	Signaling for LMF-based RAT-dependent positioning Integrity	Ericsson
R2-2301793	Discussion on RAT-dependent integrity	InterDigital, Inc.
R2-2302144	Draft LS to RAN1 on error source distributions	CATT
R2-2302271	LS on error source distributions	RAN2

8.2.4: LPHAP

TDoc	Title	Source
R2-2300115	Discussion on LPHAP	Huawei, HiSilicon
R2-2300199	Discussion on LPHAP	CATT
R2-2300412	Support of LPHAP	Intel Corporation
R2-2300454	Discussion on LPHAP	OPPO
R2-2300531	Enhancements for LPHAP	Qualcomm Incorporated
R2-2300594	Enhancements for supporting LPHAP	Fraunhofer IIS, Fraunhofer HHI
R2-2300664	Discussion on LPHAP	Spreadtrum Communications
R2-2300677	Discussion on LPHAP	vivo
R2-2300713	Alignment between DRX and PRS	Apple
R2-2300714	[DRAFT] LS on PRS and DRX alignment	Apple
R2-2300929	Discussion on LPHAP	ZTE Corporation
R2-2300961	Discussion on low power high accuracy positioning	Lenovo
R2-2301087	Considerations on Low Power High Accuracy Positioning	Sony
R2-2301190	Discussion on LPHA positioning	Xiaomi
R2-2301263	Considerations on LPHAP	CMCC
R2-2301306	Discussion on Low Power High Accuracy Positioning	Ericsson
R2-2301384	Discussion on SRS configuration in RRC_INACTIVE	Samsung
R2-2301411	Considerations on Low Power High Accuracy Positioning	Sony
R2-2301547	Discussion on LPHAP	LG Electronics Inc.
R2-2301752	PRS and DRX configuration alignment	Nokia, Nokia Shanghai Bell
R2-2301794	Discussion on LPHAP	InterDigital, Inc.
R2-2301891	DL Positioning measurement report	Telit Cinterion
R2-2302145	[Draft] LS on SRS configuration request	Huawei, HiSilicon
R2-2302278	LS on SRS configuration request	RAN2

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

TDoc	Title	Source
R2-2300300	Discussion on RAN1 lead positioning topics	Huawei, HiSilicon
R2-2300413	Considerations on other RAN1 led items	Intel Corporation
R2-2300678	Discussion on RedCap positioning	vivo
R2-2300931	Discussion on BW aggregation and RedCap poositioning	ZTE Corporation
R2-2300962	Discussion on RedCap, carrier phase Positioning and bandwidth aggregation	Lenovo
R2-2301309	RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning	Ericsson
R2-2301385	Discussion on bandwidth aggregation	Samsung
R2-2301796	Discussion on positioning for RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning	InterDigital, Inc.

8.3.1: Organizational

TDoc	Title	Source
R2-2300038	LS on network energy saving techniques (R3-226898; contact: Huawei)	RAN3
R2-2300279	Work plan for NR network energy savings	Huawei, HiSilicon

8.3.2: DTX/DRX mechanism

TDoc	Title	Source
R2-2300230	Discussion on cell DTX/DRX	Huawei, HiSilicon
R2-2300247	Cell DTX and DRX support	NEC
R2-2300378	Considerations on Cell DTX/DRX	KDDI Corporation
R2-2300444	Initial discussion on DTX-DRX mechanism	vivo
R2-2300456	Discussion on DTX DRX mechanism	OPPO
R2-2300491	Alignment to Cell DRX	Lenovo
R2-2300492	Alignment to Cell DTX	Lenovo
R2-2300539	Cell DTX-DRX Mechanism	Qualcomm Incorporated
R2-2300611	Considerations of Cell DTX and DRX	Intel Corporation
R2-2300632	Cell DTX/DRX mechanism	InterDigital
R2-2300701	Discussion on Cell DTX / DRX	Apple
R2-2300819	Discussion on Cell DTX/DRX	CATT
R2-2301064	Discussion on cell DTX and DRX mechanism for NES	ZTE Corporation, Sanechips
R2-2301230	Discussion on network DTX/DRX	CMCC
R2-2301399	Further aspects on cell DTX/DRX	Ericsson
R2-2301515	Further details on Cell DTX/DRX	Nokia, Nokia Shanghai Bell
R2-2301550	Discussion on DTX/DRX for NES	Samsung
R2-2301733	Discussion on DTX/DRX mechanism	LG Electronics Inc.
R2-2301776	Discussion for Cell DTX/DRX	NTT DOCOMO, INC.
R2-2301854	Further discussion on Cell DTX/DRX	MediaTek Inc.
R2-2301882	Cell DTX and DRX	Fraunhofer IIS

8.3.3: SSB-less Scell operation

TDoc	Title	Source
R2-2300228	Discussion on SSB-less SCell operation	Huawei, HiSilicon
R2-2300255	On remaining issues of SBB/SIB-less NES solutions	Dell Technologies
R2-2300445	RAN2 impact from inter-band SSB-less Scell operation	vivo
R2-2300540	SSB-less Scell Operation	Qualcomm Incorporated
R2-2300610	SSB-less SCell operation for inter-band CA	Intel Corporation
R2-2300635	SSB-less Scell operation	InterDigital
R2-2300704	Discussion on RAN2 work of inter-band SSB-less CA	Apple
R2-2300820	Enhancements on SCell activation procedures	CATT
R2-2301068	Discussion on SSB-less SCell operation for NES	ZTE Corporation, Sanechips
R2-2301231	Discussion on SSB-less SCell operation	CMCC
R2-2301343	SSB-less Scell operation	Nokia, Nokia Shanghai Bell
R2-2301400	SSB-less SCell operation on inter-band CA for FR1	Ericsson
R2-2301521	Enhancements on SSB-less activation	NEC Telecom MODUS Ltd.
R2-2301551	Discussion on SSB/SIB-less Solutions for NES	Samsung

8.3.4: Cell selection/re-selection

TDoc	Title	Source
R2-2300231	Discussion on cell selection/reselection for NES	Huawei, HiSilicon
R2-2300377	Considerations on Cell selection/re-selection	KDDI Corporation
R2-2300446	Discussion on cell selection/re-selection	vivo
R2-2300457	Discussion on cell selection reselection	OPPO
R2-2300541	NES Cell Selection Mechanism	Qualcomm Incorporated
R2-2300609	Cell (re)selection for handling legacy UEs in NES	Intel Corporation
R2-2300633	Cell selection and resection for NES	InterDigital
R2-2300703	Mechanism of legacy UE barring in NES cell	Apple
R2-2300821	Consideration on Cell selection/re-selection on NES cells	CATT
R2-2300871	Cell selection and reselection handling for legacy Ues	Nokia, Nokia Shanghai Bell
R2-2300977	Cell selection/re-selection in NES	Lenovo
R2-2301063	Preventing legacy UEs camping on NES cell	ZTE Corporation, Sanechips
R2-2301232	Discussion on cell barring and reselection for NES	CMCC
R2-2301401	NES Cell selection/reselection	Ericsson
R2-2301463	RRC Inactive/Idle UE handling for NES	ETRI
R2-2301522	Procedure for legacy UEs camping on NES cells	NEC Telecom MODUS Ltd.
R2-2301552	Discussion on Cell Selection and Reselection for NES	Samsung
R2-2301616	Access restriction enhancement for NES	LG Electronics Inc.
R2-2301777	Discussion for Cell selection	NTT DOCOMO, INC.
R2-2301857	Legacy UEs and NES UEs accessing to NES cells	BT plc, NTT DOCOMO, Turkcell
R2-2301873	Cell Selection and Re-Selection for NES	Fraunhofer IIS, Fraunhofer HHI

8.3.5: Connected mode mobility

TDoc	Title	Source
R2-2300229	Discussion on CHO enhancement for NES	Huawei, HiSilicon
R2-2300248	CHO procedure enhancement to support NES mode	NEC
R2-2300447	Conditional handover enhancement for network energy saving	vivo
R2-2300458	Discussion on connected mode mobility	OPPO
R2-2300542	NES Connected mode mobility	Qualcomm Incorporated
R2-2300608	CHO procedure enhancement for NES	Intel Corporation
R2-2300634	NES mobility aspects	InterDigital
R2-2300702	Discussion on CHO enhancement in NES	Apple
R2-2300822	Consideration on CHO enhancement for NES	CATT
R2-2300872	CHO on NES	Nokia, Nokia Shanghai Bell
R2-2300893	CHO for NES	Ericsson
R2-2300940	Discussion on CHO enhancements for NES	Sharp
R2-2300978	NES impact to UE mobility	Lenovo
R2-2301066	Discussion on CHO enhancements for NES	ZTE Corporation, Sanechips
R2-2301088	Handover enhancement for NES	Sony
R2-2301233	Discussion on CHO enhancements for NES	CMCC
R2-2301503	Discussion on Connected mode mobility for network energy savings	Fujitsu Limited
R2-2301553	Discussion on Connected mode mobility for NES	Samsung
R2-2301768	Connected Mode Mobility	LG Electronics

8.4.1: Organizational

TDoc	Title	Source
R2-2300016	LS on RAN1 agreements for L1/L2-based inter-cell mobility (R1-2212948; contact: Fujitsu, CATT)	RAN1
R2-2300033	Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility (R3-226829; contact: ZTE, CATT, Fujitsu)	RAN3
R2-2300056	Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility (R4-2220733; contact: CATT)	RAN4
R2-2300375	38.300 running CR for introduction of NR further mobility enhancements	MediaTek Inc.
R2-2301943	Reply LS R2-2213337 LS on security for selective SCG activation (S3-231397; contact: Nokia)	SA3
R2-2302002	Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility (R4-2303308; contact: CATT)	RAN4
R2-2302039	38.300 running CR for introduction of NR further mobility enhancements	MediaTek Inc.
R2-2302053	LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM (R1-2302194; contact: Fujitsu, CATT)	RAN1

8.4.2.1: General and Stage-2

TDoc	Title	Source
R2-2300092	Discussion on Applicable Scenarios and Procedure	CATT
R2-2300220	LTM stage-2 design models	Lenovo
R2-2300221	Details of Early TA work	Lenovo
R2-2300246	L1 Measurement Report for Cell Switch	NEC
R2-2300314	Discussion on scenarios and aspects with other WGs	vivo
R2-2300372	LTM Procedure and Support of Inter-DU LTM	MediaTek Inc.
R2-2300380	Discussion on general pocedure for LTM	OPPO
R2-2300400	Procedure descriptions of LTM	Intel Corporation
R2-2300408	Discussion on the early TA acquisition	Intel Corporation
R2-2300473	On Early TA Acquisition in LTM	Nokia, Nokia Shanghai Bell
R2-2300568	Configuring measurements and reporting of LTM cell	Qualcomm Inc.
R2-2300575	LTM Overall Procedure	Interdigital, Inc.
R2-2300576	LTM Measurement considerations	Interdigital, Inc.
R2-2300767	MAC TA RAN2 aspects for LTM	Apple
R2-2301113	Remaining stage-2 issues for LTM	Xiaomi
R2-2301150	RACH-less cell switch in LTM	Huawei, HiSilicon
R2-2301196	Discussion on procedures for LTM	Ericsson
R2-2301258	Considerations on general aspects of LTM	CMCC
R2-2301259	Considerations on failure handling	CMCC
R2-2301260	Considerations on measurement configuration	CMCC
R2-2301325	Discussion on potential enhancement before LTM cell switch	Samsung
R2-2301358	LTM procedure descriptions and stage 2 aspects	Huawei, HiSilicon
R2-2301549	Conditional handover in L2/L1 mobility	Apple
R2-2301593	Discussion on measurement enhancement of L1L2 triggered mobility	Transsion Holdings
R2-2301817	Discussion on L1 measurement configuration for LTM	NTT DOCOMO INC.
R2-2301846	Discussion on Early sync phase of LTM	NTT DOCOMO INC.
R2-2301859	Discussion on RACH-less Handover for L1/L2 Triggered Mobility	Rakuten Symphony
R2-2301860	Performance Enhancements for L1/L2 Triggered Mobility	Rakuten Symphony
R2-2301874	Delayed Resource Reservation for inter gNB-DU L1/L2 Triggered Mobility	Rakuten Symphony
R2-2301888	LTM Overall Procedure	Interdigital, Inc.

8.4.2.2: RRC

TDoc	Title	Source
R2-2300121	Further Analysis on IEs to Include in LTM Candidate Cell Configuration	CATT
R2-2300122	Discussion on RRC Remaining Issues for LTM	CATT
R2-2300277	RRC Aspects of L1L2-triggered Mobility	MediaTek Inc.
R2-2300315	Configurations of Candidate Cell for LTM	vivo
R2-2300350	Configuration and upper layer handling for sequential LTM	Futurewei
R2-2300383	Discussion on configuration related issues for LTM	OPPO
R2-2300402	Discussion on LTM RRC model	Intel Corporation
R2-2300474	On RRC Configuration for LTM	Nokia, Nokia Shanghai Bell
R2-2300567	Race conditions in LTM	Qualcomm Inc.
R2-2300569	RRC Aspects of LTM	Qualcomm Inc.
R2-2300577	LTM candidate configurations	Interdigital, Inc.
R2-2300766	On Measurement and reference config for LTM	Apple
R2-2300963	Compliance check for LTM configuration	Lenovo
R2-2301026	RRC aspects of L1/L2 triggered mobility	Fujitsu
R2-2301154	RRC aspects in LTM	NEC
R2-2301197	Discussion on RRC aspects for LTM	Ericsson
R2-2301198	TP for RRC models of LTM	Ericsson
R2-2301216	Discussion on candidate cell configuration and maintenance	ZTE Corporation, Sanechips
R2-2301359	RRC aspects for LTM	Huawei, HiSilicon
R2-2301394	Discussion on RRC configurations of LTM	Xiaomi
R2-2301562	RRC issues on the LTM	Samsung
R2-2301615	Candidate cell configuration structure for LTM	LG Electronics Inc.
R2-2301818	RRC Configurations of LTM	Sharp
R2-2302175	Way Forward on Reference and Candidate Configurations for LTM	MediaTek, Ericsson, Huawei, Nokia, Apple, ZTE
R2-2302290	Pave the way to RRC TP for LTM	Ericsson

8.4.2.3: Cell Switch

TDoc	Title	Source
R2-2300093	Discussions on Cell Switch	CATT
R2-2300181	MAC_RLC Reset and BWP Handling for LTM	Samsung Electronics Co., Ltd
R2-2300232	Securing LTM	Lenovo
R2-2300278	Triggering MAC CE for L1L2-triggered Mobility	MediaTek Inc.
R2-2300316	Discussion on dynamic switch for LTM	vivo
R2-2300351	Discussion on issues with L1L2 dynamic mobility	Futurewei
R2-2300373	Partial MAC Reset during Intra-DU LTM	MediaTek Inc.
R2-2300381	Discussion on partial MAC reset for LTM	OPPO
R2-2300382	Open issues on dynamic switching for LTM	OPPO
R2-2300403	Discussion on LTM cell switch	Intel Corporation
R2-2300570	Dynamic switch in LTM	Qualcomm Inc.
R2-2300578	LTM cell switch and triggering	Interdigital, Inc.
R2-2300653	Discussion on cell switch for LTM	Spreadtrum Communications
R2-2300698	LTM Failure Handling	FGI
R2-2300768	LTM cell switch and link failure handling	Apple
R2-2300804	Discussion on L2 handling for LTM	NEC
R2-2301027	Cell switch for L1/L2 triggered mobility	Fujitsu
R2-2301114	Handling of connection failure for LTM	Xiaomi
R2-2301115	L2 handling at cell switch	Xiaomi
R2-2301151	L2 behaviours and cell switch solutions in LTM	Huawei, HiSilicon
R2-2301153	Discussion on partial MAC reset	KDDI Corporation
R2-2301155	Cell switch overview	NEC
R2-2301199	Partial and full MAC reset in LTM	Ericsson
R2-2301217	Remaining issues for LTM execution	ZTE Corporation, Sanechips
R2-2301261	Considerations on cell switch	CMCC
R2-2301289	On resetting the UP entities	Nokia, Nokia Shanghai Bell
R2-2301412	Considerations on Cell Switch Triggering in LTM	Nokia, Nokia Shanghai Bell
R2-2301500	Discussion on LTM timer operation	LG Electronics
R2-2301501	Remaining issues of LTM execution procedure	LG Electronics
R2-2301514	Discussion on L2 reset for LTM	LG Electronics Inc.
R2-2301532	Discussion on L1L2-triggered mobility	ASUSTeK
R2-2301563	Considerations on Cell Switch for LTM	Samsung
R2-2301595	Discussion on detailed LTM cell switch procedure	Transsion Holdings
R2-2301621	Discussion on measurement enhancement of L1L2 triggered mobility	Transsion Holdings
R2-2301622	Discussion on detailed LTM cell switch procedure	Transsion Holdings
R2-2301789	Further Considerations on Cell Switch Command	ZTE Corporation,Sanechips
R2-2301790	Further Considerations on Intra-DU LTM and Partial MAC Reset	ZTE Corporation,Sanechips
R2-2301819	Cell Switch for LTM	Sharp

8.4.3: NR-DC with selective activation cell of groups

TDoc	Title	Source
R2-2300094	Discussion on Selective Activation of Cell Groups in NR-DC	CATT
R2-2300281	SCG Selective Activation in NR-DC	Qualcomm Incorporated
R2-2300317	Discussion on NR-DC with selective activation cell of groups	vivo
R2-2300352	Discussion on selective activation of cell groups and sequential LTM	Futurewei
R2-2300384	Discussion on selective activation of SCGs for NR-DC	OPPO
R2-2300404	Discussion on selective activation of cell groups	Intel Corporation
R2-2300465	Further discussion on selective activation of cell groups	Vodafone
R2-2300649	Discussion on NR-DC with SCG selective activation	Spreadtrum Communications
R2-2300752	Execution condition in selective SCG activation	Apple
R2-2300817	Discussion on selective SCG activation	MediaTek Inc.
R2-2300921	Discussion on NR-DC with selective activation of the cell groups.	DENSO CORPORATION
R2-2300924	Further analysis on configuration and signalling aspects for SAPC	Nokia, Nokia Shanghai Bell
R2-2300949	On SCG selective activation	Lenovo
R2-2301007	Discussion on NR-DC with selective activation cell of groups	KDDI Corporation
R2-2301060	Subsequent change of SCGs and selective activation	InterDigital Inc.
R2-2301156	Discussions on selective SCG activation	NEC
R2-2301218	Discussion on selective activation of the cell groups	ZTE Corporation, Sanechips
R2-2301255	Discussion on NR-DC with selective activation of cell groups	CMCC
R2-2301340	NR-DC with selective activation	Ericsson
R2-2301360	NR-DC selective activation of SCG	Huawei, HiSilicon
R2-2301395	Discussion on NR-DC with selective activation of the cell groups	Xiaomi
R2-2301564	Considerations on Subsequent CPAC after SCG Change	Samsung
R2-2301597	Discussion on Selective Activation of Cell Groups in NR-DC	Transsion Holdings
R2-2301623	Discussion on Selective Activation of Cell Groups in NR-DC	Transsion Holdings
R2-2301740	Selective Cell Group Activation	LG Electronics
R2-2301820	Discussion of selective activation	Sharp
R2-2301842	Discussion on scenarios for selective activation of the cell groups	China Telecom

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

TDoc	Title	Source
R2-2300095	Discussion on CHO including target MCG and candidate SCGs	CATT
R2-2300282	CHO with multiple candidate SCGs	Qualcomm Incorporated
R2-2300318	Discussion on evaluation and execution of CHO with CPAC	vivo
R2-2300319	Discussion on CHO with CPAC signaling procedure	vivo
R2-2300379	Discussion on CHO with CPAC	KDDI Corporation
R2-2300385	Discussions on CHO including target MCG and candidate SCGs	OPPO
R2-2300401	Discussion on CHO including candidate SCGs	Intel Corporation
R2-2300475	On Conditional Handover with Candidate SCGs for CPAC	Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, InterDigital Inc., CATT
R2-2300650	Discussion on CHO with CPAC in NR-DC	Spreadtrum Communications
R2-2300740	CHO with Candidate SCGs	Apple
R2-2300818	Discussion on CHO with candidate SCG	MediaTek Inc.
R2-2300964	Consideration on CHO with candidate SCG for CPAC	Lenovo
R2-2301062	CHO with associated SCG	InterDigital Inc.
R2-2301152	CHO including target MCG and candidate SCGs for CPC/CPA	Huawei, HiSilicon
R2-2301219	Discussion on CHO with candidate SCGs	ZTE Corporation, Sanechips
R2-2301234	Discussion CHO including target MCG and candidate SCGs for CPAC	CMCC
R2-2301328	Considerations on CHO with CPA/CPC	Samsung
R2-2301341	CHO with associated CPC or CPA	Ericsson
R2-2301396	Discussion on CHO with CPAC	Xiaomi
R2-2301741	Simultaneous Evaluation for CHO with CPAC	LG Electronics

8.5.1: Organizational (SI and WI)

TDoc	Title	Source
R2-2300019	Reply LS on XR and Media Services (R1-2212994; contact: vivo)	RAN1
R2-2300022	LS to capture Text Proposal for TR 38.835 (R1-2213016; contact: Nokia)	RAN1
R2-2300036	Reply LS on XR and Media Services (R3-226885; contact: Ericsson)	RAN3
R2-2300071	Reply LS on PDU Set Handling (S2-2301378; contact: Tencent)	SA2
R2-2300072	LS reply on reply LS on XR and Media Services (S2-2301384; contact: vivo)	SA2
R2-2300086	Reply LS on Pose Information for XR (S4-221626; contact: Qualcomm)	SA4
R2-2300087	Reply LS on PDU Set Handling (S4aR230035; contact: Ericsson)	SA4
R2-2300149	Work Plan for Rel-18 SI and WI on XR Enhancements for NR	Nokia, Qualcomm (Rapporteurs), Ericsson (RAN1 FL)
R2-2300150	SA2 Status for XR	Nokia, Qualcomm (Rapporteurs)
R2-2300151	SA4 Status for XR	Nokia, Qualcomm (Rapporteurs)
R2-2300152	Update of TR 38.835	Nokia (Rapporteur)
R2-2301941	LS on the Design of RTP Header Extension for PDU set handling (S4-230419; contact: Intel)	SA4
R2-2302009	Summary of [AT121][204][XR] Reply LS to SA2 on PSER usage (CMCC)	CMCC
R2-2302010	Reply LS on PDU Set Handling	RAN2
R2-2302309	NR; Study on XR enhancements for NR	Nokia

8.5.2.1: PDU set and data burst information

TDoc	Title	Source
R2-2300153	PDU Set and Data Burst Information	Nokia, Nokia Shanghai Bell
R2-2300185	Discussion on PDU Sets and data bursts	Qualcomm Incorporated
R2-2300222	PDU set and data burst information	CATT
R2-2300320	Discussion on PDU set and data burst information	vivo
R2-2300428	RAN2 implications on PDU Set and Data Burst based on SA2 inputs	Intel Corporation
R2-2300459	Discussion on PDU Set	OPPO
R2-2300564	PDU set and data burst information	ZTE Corporation, Sanechips
R2-2300587	Discussion on PDU Set and Data Burst Information	Google Inc.
R2-2300596	Discussion on PDU set and data burst information	Huawei, HiSilicon
R2-2300656	Discussion on PDU set and data burst information	Spreadtrum Communications
R2-2300691	PDU set and data burst information	InterDigital
R2-2300723	PDU Set Information and Uplink Jitter	Apple
R2-2300944	Discussion on PDU sets awareness in RAN	Lenovo
R2-2301009	PDU set and data burst information	NEC
R2-2301168	Discussion on PDU set information	Samsung
R2-2301369	PDU set characteristics and their usage in RAN	MediaTek Inc.
R2-2301510	Discussion on PDU Sets and Data Burst	Ericsson
R2-2301533	Discussion on PDU set information and remaining time for PSDB	ASUSTeK
R2-2301646	Discussion on PDU set handling and data burst information	LG Electronics Inc.
R2-2301797	Discussion on PDU set and data burst information	III
R2-2301849	Discussions on PDU Set information	TCL Communication
R2-2301861	Discussion on PDU sets and data bursts	Futurewei

8.5.2.2: PDU prioritization

TDoc	Title	Source
R2-2300154	PDU Set prioritization	Nokia, Nokia Shanghai Bell
R2-2300223	Discussion on the PDU Prioritization	CATT
R2-2300321	Discussion on PDU prioritization for XR awareness	vivo
R2-2300341	Discussion on PDU prioritization	Futurewei
R2-2300427	Discussion on traffic prioritization of XR traffic	Xiaomi Communications
R2-2300429	Differentiated handling of PDU sets with different importance in a QoS flow	Intel Corporation
R2-2300460	Discussion on PDU prioritization	OPPO
R2-2300502	Discussion on PDU prioritization	Lenovo
R2-2300563	PDU prioritization for XR	ZTE Corporation, Sanechips
R2-2300588	Discussion on PDU prioritization	Google Inc.
R2-2300597	Discussion on PDU prioritization at RAN	Huawei, HiSilicon
R2-2300640	Discussion on PDU Prioritization	Meta USA
R2-2300657	Discussion on PDU prioritization	Spreadtrum Communications
R2-2300685	Discussion on PDU prioritization for XR	Google Inc.
R2-2300692	PDU prioritization	InterDigital
R2-2300724	Views on XR-awareness and PDU Prioritization	Apple
R2-2300842	Discussion on LCP enhancement for XR	NEC Corporation
R2-2300939	Discussion on the PDU prioritization for XR	ITRI
R2-2301089	Considerations on XR PDU prioritization	Sony
R2-2301267	RAN2 Impact Analysis on PDU Prioritization	CMCC
R2-2301370	On the need for modifications to LCP	MediaTek Inc.
R2-2301511	Discussion on PDU Prioritization	Ericsson
R2-2301648	Discussion on the prioritization for XR	LG Electronics Inc.
R2-2301751	Discussion on handling of PDU set prioritization.	Samsung Electronics Czech
R2-2301774	Discussion on PDU prioritization	NTT DOCOMO, INC.
R2-2301798	Discussion on PDU prioritization	III

8.5.2.3: PDU discard

TDoc	Title	Source
R2-2300155	PDU Set Discard	Nokia, Nokia Shanghai Bell
R2-2300186	Discussion on PDU discard	Qualcomm Incorporated
R2-2300224	On PDU Discarding	CATT
R2-2300322	Discussion on PDU discard for XR awareness	vivo
R2-2300340	Discussion on PDU discard	Futurewei
R2-2300426	Discussing on PDU discarding of XR traffic	Xiaomi Communications
R2-2300430	Criteria and Mechanism of PDU Discard for XR traffic	Intel Corporation
R2-2300461	Discussion on PDU discard	OPPO
R2-2300518	PDU Set and PDCP Discard Handling	Samsung R&D Institute India
R2-2300562	PDU discard for XR	ZTE Corporation, Sanechips
R2-2300589	Discussion on PDU Discard	Google Inc.
R2-2300598	Discussion on PDU set discarding for XR traffic	Huawei, HiSilicon
R2-2300658	Discussion on PDU discard	Spreadtrum Communications
R2-2300693	PDU discard	InterDigital
R2-2300725	Views on Packet Discarding and Reordering	Apple
R2-2300908	Discussion on PDU discarding	Lenovo
R2-2301010	PDU discard	NEC
R2-2301028	Discussions on PDU discard	Fujitsu
R2-2301090	Considerations on XR UL PDU discard	Sony
R2-2301266	Further Considerations on PDU Discard	CMCC
R2-2301371	PDU discard based on PSDB and PDU set importance	MediaTek Inc.
R2-2301413	Considerations on XR UL PDU discard	Sony
R2-2301416	Discussion on PDU Discard	Meta USA
R2-2301509	Discussion on PDU Discard	Ericsson
R2-2301534	Discussion on PDU set discard operation	ASUSTeK
R2-2301647	Discussion on the discard for XR	LG Electronics Inc.
R2-2301767	Discussion on PDU discard	NTT DOCOMO, INC.

8.5.2.4: Protocol stack impacts

TDoc	Title	Source
R2-2300156	PDU set protocol stack impacts	Nokia, Nokia Shanghai Bell
R2-2300187	Discussion on impacts of PDU Sets on protocol stacks	Qualcomm Incorporated
R2-2300225	Protocol stack impacts from serving an XR QoS flow	CATT
R2-2300323	Discussion on protocol stack impacts and in-sequence delivery	vivo
R2-2300425	Discussion on the impact of DRB mapping alternatives	Xiaomi Communications
R2-2300431	DRB mapping to the RLC bearers for XR traffic	Intel Corporation
R2-2300462	Discussion on protocol stack impacts	OPPO
R2-2300500	Discussion on Protocol Stack impacts	Lenovo
R2-2300561	Protocol stack impacts for XR	ZTE Corporation, Sanechips
R2-2300590	Discussion on protocol Stack impact	Google Inc.
R2-2300599	Discussion on L2 protocol stack for differentiated PDU set handling at RAN	Huawei, HiSilicon
R2-2300659	Discussion on protocol stack impacts	Spreadtrum Communications
R2-2300694	Protocol stack impacts	InterDigital
R2-2300726	Views on QoS Mapping and PS Impacts	Apple
R2-2300987	Discussion on mapping the PDU set into DRB/LCH	NEC
R2-2301029	Discussions on protocol stack impacts of XR	Fujitsu
R2-2301268	L2 Protocol Stack for PDU Set	CMCC
R2-2301386	Discussion on protocol stack impact	Samsung
R2-2301435	Discussion on protocol stack impacts	Futurewei
R2-2301506	Discussion on Protocol stack impacts	Ericsson
R2-2301734	Discussion on XR impacts on protocol stack	LG Electronics Inc.
R2-2301850	Discussions on Protocol stack impacts from PUD Set	TCL Communication

8.5.3: XR-specific power saving

TDoc	Title	Source
R2-2300118	Discussion on XR power saving	Huawei, HiSilicon
R2-2300188	DRX enhancements for XR	Qualcomm Incorporated
R2-2300226	DRX enhancements for XR Power Saving	CATT
R2-2300324	Discussion on DRX Enhancements for XR Power Saving	vivo
R2-2300423	Discussing on XR-specific C-DRX enhancement	Xiaomi Communications
R2-2300432	C-DRX enhancements for XR traffic	Intel Corporation
R2-2300565	XR-Specific power saving	ZTE Corporation, Sanechips
R2-2300591	XR-specific power saving enhancement	Google Inc.
R2-2300695	XR-specific power saving	InterDigital
R2-2300699	Discussion on XR data periodicity mismatch	FGI
R2-2300774	DRX enhancement for power saving in XR	LG Electronics Inc.
R2-2300843	Discussion on C-DRX enhancement for XR	NEC Corporation
R2-2300909	C-DRX enhancements for XR-specific power saving	DENSO CORPORATION
R2-2300945	Discussion of DRX enhancement	Lenovo
R2-2301091	Proposals on XR specific C-DRX power saving enhancements	Sony
R2-2301237	Discussion on DRX enhancements	CMCC
R2-2301323	Discussion on power saving scheme for XR	Samsung
R2-2301372	C-DRX enhancements for XR	MediaTek Inc.
R2-2301508	Discussion on XR-specific power saving	Ericsson
R2-2301516	Power saving enhancements for XR	Nokia, Nokia Shanghai Bell
R2-2301834	Discussion on various frame rates supported for XR-specific power saving	III

8.5.4: XR-specific capacity improvements

TDoc	Title	Source
R2-2300189	Enhancements for capacity improvements	Qualcomm Incorporated
R2-2300227	The Issues of XR-specific Capacity Improvements	CATT
R2-2300256	Dynamic BSR formulation and reporting for XR	Dell Technologies
R2-2300325	Discussion on Feedback Enhancements for XR	vivo
R2-2300397	Discussion on BSR enhancement for XR capacity improvements	TCL Communication Ltd.
R2-2300422	Discussing on UE feedback enhancements for XR capacity	Xiaomi Communications
R2-2300433	Enhancements to Buffer Status Reporting for XR Traffic	Intel Corporation
R2-2300463	Discussion on capacity improvement	OPPO
R2-2300560	BSR enhancements for XR	ZTE Corporation, Sanechips
R2-2300592	XR-Specific capacity improvements	Google Inc.
R2-2300641	Considerations on XR capacity improvements	KDDI Corporation
R2-2300665	BSR enhancements for XR	Spreadtrum Communications
R2-2300684	Discussion on capacity improvements for XR	Google Inc.
R2-2300696	XR-specific capacity improvements	InterDigital
R2-2300727	Views on BSR Enhancements for XR	Apple
R2-2300728	Views on Configured Grant Enhancements for XR	Apple
R2-2300826	Discussion on BSR enhancement for XR	NEC Corporation
R2-2300918	Discussion on XR-specific capacity improvements	DENSO CORPORATION
R2-2300946	Discussion on UE Feedback enhancements	Lenovo
R2-2301030	Discussions on XR-specific capacity improvements	Fujitsu
R2-2301092	Considerations on XR specific capacity improvements	Sony
R2-2301248	Discussion on XR-specific capacity improvement	CMCC
R2-2301423	Capacity enhancement for XR	MediaTek Inc.
R2-2301507	Discussion on XR-specific capacity improvements	Ericsson
R2-2301517	Capacity improvements	Nokia, Nokia Shanghai Bell
R2-2301721	Discussion on MAC enhancement for XR-specific capacity improvement	Huawei, HiSilicon
R2-2301725	Discussion on BSR enhancement and delay information report	LG Electronics Inc.
R2-2301773	Discussion on BSR enhancements for XR	Samsung
R2-2301805	Discussion on XR-specific capacity improvements	III

8.6.1: Organizational

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

8.6.2: Performance Enhancements

TDoc	Title	Source
R2-2301880	R18 IoT NTN performance enhancement	Ericsson

8.6.2.1: HARQ enhancements

TDoc	Title	Source
R2-2300161	Discussion on HARQ enhancement for IoT NTN	OPPO
R2-2300203	Discussion on the HARQ handling in IoT NTN	CATT
R2-2300262	On Disabling HARQ Feedback in IoT-NTN	MediaTek Inc.
R2-2300579	Disabling HARQ feedback for IoT-NTN	Interdigital, Inc.
R2-2300889	Enhancement for UL and DL HARQ processes	Qualcomm Incorporated
R2-2301043	Discussion on HARQ enhancement	Xiaomi
R2-2301046	Draft LS on NPDCCH monitoring for HARQ mode B	Xiaomi
R2-2301251	Discussion on the HARQ enhancement for IoT-NTN	CMCC
R2-2301659	Discussion on Timing Advance Report MAC CE transmission in eMTC NTN	Nokia, Nokia Shanghai Bell, Huawei, HiSilicon

8.6.2.2: GNSS operation enhancements

TDoc	Title	Source
R2-2300175	Discussion on GNSS operation in connected mode	OPPO
R2-2300204	Discussion on GNSS operation in connected mode	CATT
R2-2300263	Enhancements on GNSS operation	MediaTek Inc.
R2-2300580	GNSS acquisition and reporting for IoT NTN	Interdigital, Inc.
R2-2300739	Improved GNSS Operation	Apple
R2-2300892	GNSS fix in RRC_CONNECTED	Qualcomm Incorporated
R2-2300979	Considerations on long GNSS operation in CONNECTED state	Lenovo
R2-2301041	Discussion on GNSS operation enhancement	Xiaomi
R2-2301053	Further discussion on GNSS enhancements	ZTE Corporation, Sanechips
R2-2301209	Discussion on the enhancement of GNSS operation	Huawei, Turkcell, HiSilicon
R2-2301252	Discussion on the GNSS enhancement for IoT-NTN	CMCC
R2-2301493	On improved GNSS operation for IoT NTN	Samsung Electronics Benelux BV
R2-2301660	On GNSS operation enhancements for IoT NTN	Nokia, Nokia Shanghai Bell
R2-2301895	Discussion on GNSS operation enhancement	Xiaomi
R2-2301951	Report of [AT121][101][IoT NTN enh] GNSS operation (CATT)	CATT

8.6.3: Mobility Enhancements

TDoc	Title	Source
R2-2300925	Analysis on mobility enhancements for IoT-NTN	Nokia, Nokia Shanghai Bell

8.6.3.1: Enhancements for neighbour cell measurements

TDoc	Title	Source
R2-2300144	Enhancements for neighbour cell measurements	Huawei, HiSilicon, Turkcell
R2-2300162	Discussion on measurement enhancement for IoT NTN	OPPO
R2-2300205	Enhancements for Neighbor Cell Measurements	CATT
R2-2300264	Enhancements on neighbour cell measurement	MediaTek Inc.
R2-2300366	Discussion on neighbour cell measurements in IoT NTN	Intel Corporation
R2-2300581	Neighbour cell measurements before RLF	Interdigital, Inc.
R2-2300750	Neighbour cell measurements before RLF for NB-IoT	Apple
R2-2300891	Neighbour satellite and coverage information signalling	Qualcomm Incorporated
R2-2300980	CONNECTED neighbour cell measurement for NB-IoT in NTN	Lenovo
R2-2301012	Enhancements for neighbor cell measurements	NEC
R2-2301054	Further discussion on neighbor cell measurement	ZTE Corporation, Sanechips
R2-2301056	Further discussion on other mobility enhancements	ZTE Corporation, Sanechips
R2-2301187	Consideration on enhancements for the neighbour cell measurement	Xiaomi
R2-2301253	Discussion on enhancements for neighbour cell measurements	CMCC
R2-2301494	On enhancements for neighbour cell measurements	Samsung Electronics Benelux BV
R2-2301602	Discussion on Enhancements for neighbour cell measurements	Transsion Holdings
R2-2301624	Discussion on Enhancements for neighbour cell measurements	Transsion Holdings
R2-2301693	Discussion on neighbour cell measurements before RLF	Ericsson

8.6.3.2: Other

TDoc	Title	Source
R2-2300145	Discussion on CHO enhancements	Huawei, HiSilicon, Turkcell
R2-2300163	Discussion on mobility enhancements for eMTC NTN	OPPO
R2-2300265	On Mobility Enhancements in IoT-NTN	MediaTek Inc.
R2-2300749	Mobility enhancement in IoT NTN	Apple
R2-2300981	IDLE mobility for moving cells in IoT NTN	Lenovo
R2-2301495	Other mobility enhancements	Samsung Electronics Benelux BV
R2-2301871	Conditional Handover in IoT NTN	Ericsson

8.6.4: Enhancements to discontinuous coverage

TDoc	Title	Source
R2-2300206	Discussion on enhancements to discontinuous coverage	CATT
R2-2300266	On Enhancements to discontinuous coverage	MediaTek Inc.
R2-2300501	Impact of the UE Unreachability Periods on UE AS	Google Inc.
R2-2300582	IoT-NTN discontinuous coverage enhancements	Interdigital, Inc.
R2-2300654	Discussion on power saving enhancements for supporting discontinuous coverage	Spreadtrum Communications
R2-2300751	Support on discontinuous coverage in IoT NTN	Apple
R2-2300878	Considerations on Supporting Discontinuous Coverage	NEC Europe Ltd
R2-2300890	RRC release procedure in discontinuous coverage	Qualcomm Incorporated
R2-2300926	On IoT-NTN enhancements for discontinuous coverage	Nokia, Nokia Shanghai Bell
R2-2300982	On mobility and power saving issues for discontinuous coverage	Lenovo
R2-2301057	Discussion on discontinuous coverage enhancements	ZTE Corporation, Sanechips
R2-2301106	Discontinuous coverage enhancements	Samsung Electronics Nordic AB
R2-2301188	Discussion on enhancements to discontinuous coverage	Xiaomi
R2-2301210	Discussion on the discontinuous coverage	Huawei, Turkcell, HiSilicon
R2-2301254	Discussion on the discontinuous coverage for IoT-NTN	CMCC
R2-2301603	Discussion on enhancement to discontinuous coverage for IoT NTN	Transsion Holdings
R2-2301625	Discussion on enhancement to discontinuous coverage for IoT NTN	Transsion Holdings
R2-2301862	Complementing discontinuous coverage with minimum support for discontinuous feeder link operation	Sateliot, GateHouse, Novamint, Intelsat, Airbus
R2-2301870	IoT NTN Enhancements to discontinuous coverage	Ericsson
R2-2301886	Complementing discontinuous coverage with minimum support for discontinuous feeder link operation	Sateliot, GateHouse, Novamint, Intelsat, Airbus, Hispasat, ESA, TNO

8.7.1: Organizational

TDoc	Title	Source
R2-2300020	Reply LS on RACH-less handover in NTN (R1-2213001; contact: OPPO)	RAN1
R2-2300062	Reply LS on Latency impact for NTN verified UE location (S1-223539; contact: Xiaomi)	SA1
R2-2300066	LS Response on Latency impact for NTN verified UE location (S2-2211199; contact: Qualcomm)	SA2
R2-2301344	R18 WI NR-NTN-enh work plan at RAN1, 2 and 3	THALES
R2-2301998	Reply LS on RACH-less handover in NTN (R4-2303239; contact: OPPO)	RAN4

8.7.2: Coverage Enhancements

TDoc	Title	Source
R2-2300347	Discussion on coverage enhancement for R18 NTN	vivo
R2-2301363	Blind Msg3 retransmission in Rel-18 NTN	InterDigital
R2-2301524	Modification of Msg3 for coverage enhancements	NEC Telecom MODUS Ltd.
R2-2301637	Discussion on inital blind Msg3 retransmssion	LG Electronics Inc.
R2-2301661	Discussion on Coverage Enhancement for NR NTN	Nokia, Nokia Shanghai Bell

8.7.3: Network verified UE location

TDoc	Title	Source
R2-2300176	Discussion on network verified UE location	OPPO
R2-2300207	Discussion on Network Verified UE Location	CATT
R2-2300272	On Network Verified UE Location in NR NTN	MediaTek Inc.
R2-2300364	Discussion on the single satellite Multi-RTT positioning method in NTN	Intel Corporation
R2-2300528	discussion on network verified UE location	Ericsson
R2-2300731	Network Verified UE Location	Apple
R2-2300882	Single satellite Multi-RTT based positioning	Qualcomm Incorporated
R2-2301069	Discussion on NTN NW verified UE location	Lenovo
R2-2301119	Further discussion on Network Verified UE Location in NTN	Samsung Electronics Nordic AB
R2-2301140	Consideration on NW verified UE location	ZTE Corporation, Sanechips
R2-2301183	Discussion on network verified UE location	Xiaomi
R2-2301211	Further consideration on network verified UE location	Huawei, Turkcell, HiSilicon
R2-2301354	On Network verified UE location	Nokia, Nokia Shanghai Bell
R2-2301837	Discussion on Network Verified Location	TCL Communication Ltd.

8.7.4.1.1: NTN-TN enhancements

TDoc	Title	Source
R2-2300146	Discussion on NTN-TN cell reselection enhancements	Huawei, HiSilicon, Turkcell
R2-2300164	Discussion on NTN-TN cell reselection enhancement	OPPO
R2-2300208	Discussion on Cell Reselection Enhancements in NTN-TN Scenario	CATT
R2-2300345	Discussion on power saving for NTN-TN mobility	vivo
R2-2300363	Discussion on TN-NTN cell reselection enhancements	Intel Corporation
R2-2300476	On Enhanced Cell Reselection in Rel-18 NTN	Nokia, Nokia Shanghai Bell
R2-2300511	Discussion on NTN-TN Mobility Enhancements in Idle State	Google Inc.
R2-2300732	NTN-TN Cell Reselection Enhancement	Apple
R2-2300798	Discussion on NTN-TN cell reselection enhancement	LG Electronics France
R2-2300883	TN neighbour cell coverage information	Qualcomm Incorporated
R2-2300983	IDLE mobility regarding NTN moving cells	Lenovo
R2-2300996	Discussion on NTN-TN Cell re-selection	ITL
R2-2301093	Cell selection/reselection enhancements in NTN-TN	Sony
R2-2301141	Consideration on cell reselection enhancements for NTN-TN	ZTE Corporation, Sanechips
R2-2301184	Cell reselection enhancements for NTN-TN mobility	Xiaomi
R2-2301225	Discussion on NTN-TN reselection	CMCC
R2-2301365	NTN-TN mobility and service continuity	InterDigital
R2-2301460	NTN-TN Mobility Cell Reselection	SHARP Corporation
R2-2301479	Discussion on NTN-TN cell reselection enhancements	Samsung Research America
R2-2301523	Details of the TN coverage data signalling	NEC Telecom MODUS Ltd.
R2-2301604	Further discussion on NTN-TN cell reselection enhancements	Transsion Holdings
R2-2301626	Further discussion on NTN-TN cell reselection enhancements	Transsion Holdings
R2-2301764	Further discussion on NTN-TN cell reselection enhancements	NTT DOCOMO, INC.
R2-2301869	TN NTN mobility enhancements	Ericsson

8.7.4.1.2: NTN-NTN enhancements

TDoc	Title	Source
R2-2300147	Discussion on NTN-NTN cell reselection enhancements	Huawei, HiSilicon, Turkcell
R2-2300165	Discussion on NTN-NTN cell reselection enhancement	OPPO
R2-2300241	Issues on NTN Mobility	Lockheed Martin
R2-2300344	Discussion on cell reselection enhancements for earth-moving cell	vivo
R2-2300362	Discussion on NTN-NTN cell reselection enhancements	Intel Corporation
R2-2300451	Discussion on cell reselection in earth moving cell	Quectel
R2-2300466	Neighbour cell signalling overhead reduction	PANASONIC
R2-2300509	Discussion on NTN-NTN Mobility Enhancements in Idle State	Google Inc.
R2-2300655	Discussion on NTN-NTN cell reselection enhancements	Spreadtrum Communications
R2-2300733	NTN-NTN Cell Reselection Enhancement	Apple
R2-2300799	Discussion on NTN-NTN cell reselection enhancement	LG Electronics France
R2-2300884	Neighbor cell measurement relaxation	Qualcomm Incorporated
R2-2300984	Measurement for cell reselection in NTN with TN cells involved	Lenovo
R2-2300995	Discussion on NTN-NTN Cell re-selection	ITL
R2-2301142	Consideration on cell reselection enhancements for NTN-NTN	ZTE Corporation, Sanechips
R2-2301185	Cell reselection enhancements for NTN-NTN mobility	Xiaomi
R2-2301226	Discussion on NTN-NTN reselection	CMCC
R2-2301364	Cell reselection enhancements for Earth moving cell	InterDigital
R2-2301480	Discussion on Cell Reselection with Earth-moving Cell	Samsung Research America
R2-2301535	Discussion on reference location for moving cell	ASUSTeK
R2-2301605	Further discussion on NTN-NTN cell reselection enhancements	Transsion Holdings
R2-2301627	Further discussion on NTN-NTN cell reselection enhancements	Transsion Holdings
R2-2301868	NTN NTN mobility enhancements	Ericsson
R2-2301953	[AT121][104][NR NTN enh] NTN-NTN cell reselection (ZTE)	ZTE Corporation, Sanechips

8.7.4.2: Handover enhancements

TDoc	Title	Source
R2-2300148	Discussion on NTN handover enhancements	Huawei, HiSilicon, Turkcell
R2-2300177	Discussion on NTN handover enhancements	OPPO
R2-2300209	Discussion on PCI unchanged scenario	CATT
R2-2300210	Discussion on NTN HO Enhancements	CATT
R2-2300274	Handover Enhancement in LEO NTN with Earth-moving Cells	MediaTek Inc.
R2-2300346	On handover enhancement for siganlling overhead reduction in NR NTN	vivo
R2-2300361	Discussion on NTN 2-step handover	Intel Corporation
R2-2300450	Discussion on NTN HO enhancnment	CAICT
R2-2300467	Handover timing improvement	PANASONIC
R2-2300477	On Enhanced NTN Connected-mode Mobility in Rel-18	Nokia, Nokia Shanghai Bell
R2-2300514	SMTC and Measurement Gap Enhancements for Connected UEs	Google Inc.
R2-2300516	Discussion on NTN-TN Mobility Enhancements in Connected State	Google Inc.
R2-2300734	NTN specific Handover Enhancement	Apple
R2-2300800	Discussion on handover enhancement	LG Electronics France
R2-2300856	Discussion of HO common signaling reduction in NTN	China Telecom
R2-2300885	Further handover enhancement for NTN	Qualcomm Incorporated
R2-2300985	Considerations on common signalling for CONNECTED mobility in NTN	Lenovo
R2-2301013	NTN-NTN handover enhancement	NEC
R2-2301094	Signaling overhead reduction and group handover during NTN-NTN HOs	Sony
R2-2301143	Consideration on HO enhancements in NTN	ZTE Corporation, Sanechips
R2-2301186	Discussion on handover enhancements for NTN-NTN mobility	Xiaomi
R2-2301269	Service Link Switching with PCI unchanged	CMCC,CATT,Huawei,HiSilicon,Lenovo,vivo
R2-2301366	NTN mobility enhancements for RRC_CONNECTED	InterDigital
R2-2301481	Discussion on NTN handover enhancements	Samsung Research America
R2-2301504	Discussion on Handover enhancements for NTN	Fujitsu Limited
R2-2301536	Discussion on RACH-less handover for NTN	ASUSTeK
R2-2301537	Discussion on handover enhancement with common signalling	ASUSTeK
R2-2301606	Further discussion on NTN-NTN handover enhancements	Transsion Holdings
R2-2301628	Further discussion on NTN-NTN handover enhancements	Transsion Holdings
R2-2301766	Further discussion on NTN-NTN handover enhancements	NTT DOCOMO, INC.
R2-2301821	Discussion on handover enhancements	Sharp
R2-2301864	NTN-NTN handover enhancements	Sequans Communications
R2-2301866	HO/CHO Signaling Overhead Reduction by NTN-config omission	Sequans Communications
R2-2301867	Handover enhancements	Ericsson

8.8.1: Organizational

TDoc	Title	Source
R2-2300006	OG0022_LS-MITRE-Engenuity Open Generation DAA input_PC5_DAA_RID_PRS OG0022 (contact: vivo)	MITRE Engenuity Open Generation 5G Consortium
R2-2300061	LS response to ETSI TC LI on Location Services for Drones (RP-223555; contact: Ericsson)	RAN
R2-2300080	LS on PC5 based Detect and Avoid mechanism (S2-2301854; contact: LGE)	SA2
R2-2300478	Uncrewed Aerial Vehicles in Rel-18 - Updated Workplan	Nokia, Nokia Shanghai Bell
R2-2301875	Discussion on the LS from SA2 for NR UAV	CATT
R2-2301931	LS on RAN dependency for UAS (S2-2303285; contact: LGE)	SA2

8.8.2: Measurement reporting for mobility and interference control

TDoc	Title	Source
R2-2300369	Interference control for UAV	Intel Corporation
R2-2300371	mobility control for UAV	Intel Corporation
R2-2300479	Report from [Post120][312][UAV] Mobility Control for UAVs (Nokia)	Nokia, Nokia Shanghai Bell
R2-2300583	Measurement and reporting enhancements	Qualcomm Incorporated
R2-2300595	On Interference Reporting for UAV UEs	Nokia, Nokia Shanghai Bell
R2-2300746	Measurement reporting enhancement in UAV	Apple
R2-2300852	Discussion on Measurement Reports Enhancements	NEC Europe Ltd
R2-2300897	UAV measurement reports	Ericsson
R2-2300941	Discussion on measurement reporting for NR UAV	Sharp
R2-2300972	measurement enhancement for NR UAV	Lenovo
R2-2300991	Measurement reporting for mobility and interference control	Huawei, HiSilicon
R2-2300997	Report of [Post120][313][UAV] Interference Control for UAVs (Huawei)	Huawei (email rapporteur)
R2-2301095	Considerations about UAV mobility and user consent	Sony
R2-2301220	On UAV mobility and interference control	ZTE Corporation, Sanechips
R2-2301227	Measurement Reporting for NR UAV	CMCC
R2-2301397	Discussion on measurement reporting for NR UAV	Xiaomi
R2-2301592	On measurement reporting enhancements in NR UAV	Samsung Electronics Austria
R2-2301677	Discussion on measurement reporting enhancement for NR UAV	vivo
R2-2301765	Further discussion on NR support for UAV	NTT DOCOMO, INC.
R2-2301771	Measurement Report Enhancement	LG Electronics
R2-2301772	Number of changed cell related Enhancement	LG Electronics
R2-2301807	Discussion on measurement reporting for NR UAV	China Telecom
R2-2301952	On measurement reporting enhancements in NR UAV	Samsung
R2-2302210	Report of [AT121][305][UAV] More than a single config, each for a specific height region	Qualcomm Incorporated (Moderator)

8.8.3: Flight path reporting

TDoc	Title	Source
R2-2300368	Flight path update triggering for UAV	Intel Corporation
R2-2300480	On Flight Path Plan (FPP) and Height-dependent Configurations	Nokia, Nokia Shanghai Bell
R2-2300584	Flight path reporting enhancements	Qualcomm Incorporated
R2-2300747	Flight path reporting in UAV	Apple
R2-2300853	Discussion on Flight Path Reporting	NEC Europe Ltd
R2-2300905	Flight path reporting	Ericsson
R2-2300942	Discussion on flight path reporting for NR UAV	Sharp
R2-2300973	Remaining issues of flight path reporting for NR UAV	Lenovo
R2-2300992	Flight path reporting	Huawei, HiSilicon
R2-2301221	On flight path reporting	ZTE Corporation, Sanechips
R2-2301228	Flight path Reporting for NR UAV	CMCC
R2-2301367	Flight path notification and reporting for UAV	InterDigital
R2-2301387	Discussion on flight path reporting	Samsung
R2-2301398	Discussion on flight path reporting for NR UAV	Xiaomi
R2-2301676	Discussion on flight path reporting for NR UAV	vivo
R2-2301810	Discussion on flight path reporting for NR UAV	China Telecom
R2-2301876	Leftover Issues on Flight Path Reporting	CATT
R2-2301883	Consideration on flight path reporting of NR support for UAV	DENSO CORPORATION

8.8.5: UAV identification broadcast

TDoc	Title	Source
R2-2300333	RAN2 aspects of PC5-based BRID and DAA support	Qualcomm Incorporated
R2-2300481	RAN2 Impacts of PC5-based BRID and DAA for UAVs	Nokia, Nokia Shanghai Bell
R2-2300538	On broadcasting UAV identification	Ericsson España S.A.
R2-2300748	UAV identification broadcast over PC5	Apple
R2-2300854	Considerations on Enhancements for UAV identification broadcast	NEC Europe Ltd
R2-2300974	Discussion on broadcasting remote id for UAV	Lenovo
R2-2300993	Consideration on UAV remote identification broadcast	Huawei, HiSilicon
R2-2301096	UAV identification broadcast	Sony
R2-2301169	Discussion on UAV identification broadcast	Samsung
R2-2301222	On UAV identification broadcast	ZTE Corporation, Sanechips
R2-2301229	UAV identification broadcast	CMCC
R2-2301418	UAV Broadcast of Remote IDentification and Detect And Avoid	Beijing Xiaomi Mobile Software
R2-2301678	Discussion on UAV identification broadcast	vivo
R2-2301737	Draft Reply LS on PC5 based Detect and Avoid mechanism	LG Electronics France
R2-2301877	RAN2 impact analysis to support UAV ID Broadcast	CATT
R2-2302105	Reply LS on PC5 based Detect and Avoid mechanism	RAN2
R2-2302182	Draft Reply LS on PC5 based Detect and Avoid mechanism	LG Electronics France
R2-2302222	Draft Reply LS on PC5 based Detect and Avoid mechanism	LG Electronics
R2-2302262	Reply LS on PC5 based Detect and Avoid mechanism	RAN2

8.9.1: Organizational

TDoc	Title	Source
R2-2300032	Reply LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN (R3-226822; contact: LGE)	RAN3
R2-2300064	LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN (S2-2207518; contact: LGE)	SA2
R2-2300068	LS on Multi-path Authorization information to NG-RAN (S2-2211269; contact: LGE)	SA2
R2-2300847	Revised work plan for NR sidelink relay enhancements	LG Electronics France
R2-2301933	Reply LS on Differentiation of Layer2 ID and Coexistence of U2N/U2U (S2-2303381; contact: CATT)	SA2

8.9.2: UE-to-UE relay

TDoc	Title	Source
R2-2300102	Discussion on U2U Relay Discovery and (Re)Selection	CATT
R2-2300134	Discussion on U2U relay	OPPO
R2-2300250	Adaptation layer and connection establishment for L2 UE to UE relay	NEC
R2-2300534	Relay (Re-)Selection and Discovery for Layer-2 UE-to-UE Relays	Ericsson España S.A.
R2-2300536	Control Plane Procedures for Layer-2 UE-to-UE Relays	Ericsson España S.A.
R2-2300619	Discussion on L2 UE-to-UE relaying aspects	Intel Corporation
R2-2300620	Discovery and (re)selection open aspects of U2U relaying	Intel Corporation
R2-2300625	Discovery and Relay Selection for UE to UE Relays	InterDigital
R2-2300644	Discussion on UE-to-UE relay	Spreadtrum Communications
R2-2300687	Discussion on the common L2 L3 parts for U2U relaying	vivo
R2-2300688	Discussion on the L2 specific parts for U2U relaying	vivo
R2-2300760	Discussion on user plane design for Layer 2 UE-to-UE Relay	Apple
R2-2300811	Relay selection and reselection for U2U relay	LG Electronics Inc.
R2-2300814	Control plane procedure for U2U relay	LG Electronics Inc.
R2-2300849	Discussion on NR sidelink U2U relay	China Telecom
R2-2300965	Discussion on L2 U2U relay	Lenovo
R2-2301018	Common part open issues and Layer-2 specific part on U2U Relay	Qualcomm Incorporated
R2-2301031	UE identity information in the adaptation layer	Fujitsu
R2-2301082	Discussion on U2U relay discovery and (re)selection	ZTE, Sanechips
R2-2301083	Discussion on U2U relay L2-specific functionality	ZTE, Sanechips
R2-2301097	UE-to-UE relay (re)selection	Sony
R2-2301170	Integrated U2U relay discovery	Samsung
R2-2301171	QoS and Bearer configuration for U2U relaying	Samsung
R2-2301177	Discussion on UE-to-UE relay	Huawei, HiSilicon
R2-2301224	SRAP design for U2U Sidelink Relay	Samsung R&D Institute UK
R2-2301241	Discussion on U2U relay	CMCC
R2-2301355	Considerations on U2U relay (re)selection and Local ID assignment	Nokia, Nokia Shanghai Bell
R2-2301414	Considerations for U2U L2 relay operations	Kyocera
R2-2301417	Continuation of discussion on U2U relay discovery and relay (re)selection	Beijing Xiaomi Mobile Software
R2-2301538	Discussion on E2E security for supporting L2 UE-to-UE relay	ASUSTeK
R2-2301539	Discussion on aspects of AS layer configuration for L2 U2U Relay	ASUSTeK
R2-2301736	Connection management and procedures for L2 UE-to-UE relay	MediaTek Inc.
R2-2301827	UE-to-UE relay (re)selection	Sharp

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

TDoc	Title	Source
R2-2300103	Considerations on Service Continuity Enhancements for L2 U2N Relay	CATT
R2-2300128	Discussion on further enhancement of service continuity	OPPO
R2-2300129	Discussion on emergency service	OPPO
R2-2300251	Lossless data delivery during inter-gNB path switch	NEC
R2-2300275	Discussion on Service Continuity Enhancements	NEC Corporation
R2-2300391	Discussion on service continuity enhancement	Xiaomi
R2-2300535	Further Aspects on Inter-gNB Service Continuity	Ericsson España S.A.
R2-2300626	Open Issues on Service Continuity	InterDigital
R2-2300627	Lossless path switching from indirect to indirect/direct	InterDigital, Apple, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE, Sanechips
R2-2300647	Service continuity enhancements support for L2 U2N relay	Spreadtrum Communications
R2-2300761	Discussion on Service continuity enhancement of L2 U2N relay	Apple
R2-2300815	Consideration on service continuity enhancement for L2 U2N relay	LG Electronics Inc.
R2-2300850	Discussion on service continuity for inter-gNB mobility scenarios	China Telecom
R2-2300966	Service continuity for Inter-gNB path switching	Lenovo
R2-2300999	SL-RSRP and SD-RSRP measurement issues	Nokia, Nokia Shanghai Bell
R2-2301000	Discussion on service continuity issues for Inter-gNB path switching of L2 U2N relay	Nokia, Nokia Shanghai Bell
R2-2301040	Discussion on lossless delivery from indirect path to target path	Qualcomm Incorporated
R2-2301084	Further discussion on service continuity for SL relay	ZTE, Sanechips
R2-2301098	Service continuity enhancements for UE sidelink relay	Sony
R2-2301242	Discussion on service continuity	CMCC
R2-2301484	Discussion on Service Continuity	Huawei, HiSilicon
R2-2301596	Service continuity enhancements for L2 U2N relay	Intel Corporation
R2-2301738	Inter-gNB path switch to Relay UE in RRC Idle, RRC Inactive	MediaTek Inc.
R2-2301826	Discussion on remaining issues for path switching	Sharp
R2-2301892	Lossless path switching from indirect to indirect/direct	InterDigital Inc., Apple, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE, Sanechips
R2-2302146	[DRAFT] LS on Comparison of SL-RSRP and SD-RSRP measurements	Nokia
R2-2302234	LS on Comparison of SL-RSRP and SD-RSRP measurements	RAN2

8.9.4: Multi-path relaying

TDoc	Title	Source
R2-2300104	Discussion on Multi-path for Scenario 1	CATT
R2-2300105	Leftover Issues on Multi-path Scenario 2	CATT
R2-2300133	Discussion on multi-path SL relay	OPPO
R2-2300276	Discussion on Multi-path Relaying	NEC Corporation
R2-2300390	Discussion on multi-path	Xiaomi
R2-2300537	Path Management for Multipath Relays	Ericsson España S.A.
R2-2300618	Control plane aspects of multi-path relaying	Intel Corporation
R2-2300628	Design Aspects for Multipath	InterDigital
R2-2300648	Discussion on multi-path relaying	Spreadtrum Communications
R2-2300689	Basic control plane aspects for Multi-path Scenario 1&2	vivo
R2-2300690	Remaining Issues for Multi-path Scenario-1 and Scenario-2	vivo
R2-2300762	Discussion on control plan design for Multi-path	Apple
R2-2300763	Discussion on remaining issues on Scenario 2 for Multi-path	Apple
R2-2300848	Multi-path relaying for NR sidelink relay enhancements	LG Electronics France
R2-2300851	Discussion on multi-path relaying	China Telecom
R2-2300967	Second path addition and failure recovery for Scenario1	Lenovo
R2-2301020	Further discussion on multi-path relay for Scenario 1 and Scenario 2	Qualcomm Incorporated
R2-2301032	Path activation and traffic offloading in multi-path	Fujitsu
R2-2301072	Discussion on Multi-path relaying	Lenovo
R2-2301081	Discussion on the support of multi-path relaying	ZTE, Sanechips
R2-2301099	Multi-path relaying discussion	Sony
R2-2301178	Discussion on multi-path operation	Huawei, HiSilicon
R2-2301243	Control plane issues in multi-path	CMCC
R2-2301244	Considerations on scenario 2	CMCC
R2-2301322	Considerations on resource allocation mode 1 support for Sidelink multi-path relay	Philips International B.V.
R2-2301324	Discussion sidelink relay enhancement for scenario 1&2	Samsung
R2-2301415	Considerations for multipath relay operations for Scenario 1	Kyocera
R2-2301540	Bearer mapping configuration for multi-path Scenario 2	ASUSTeK
R2-2301541	Resource allocation and BSR reporting for multi-path	ASUSTeK
R2-2301554	Multipath sidelink relay	Nokia, Nokia Shanghai Bell
R2-2301735	Discuss on Multipath	MediaTek Inc.
R2-2301823	C-plane aspects of multi-path	Sharp
R2-2301824	remaining issue for supporting senario2	Sharp
R2-2301925	[Pre121][407] Summary of AI 8.9.4 on Multi-path relaying	LG Electronics Inc.

8.9.5: DRX

TDoc	Title	Source
R2-2300392	Discussion on SL DRX in U2N relay	Xiaomi
R2-2301052	SL DRX for L2 U2N relay	Qualcomm Incorporated, Fraunhofer IIS, Fraunhofer HHI, CATT
R2-2301179	Discussion on sidelink DRX for L2 U2N relay	Huawei, HiSilicon
R2-2301839	SL-Relay DRX	MediaTek Inc.

8.10.1: Organizational

TDoc	Title	Source
R2-2300827	Draft 36.306 CR for Rel-18 IDC UE capabilities	Intel Corporation
R2-2300828	Draft 36.331 CR for Rel-18 IDC UE capabilities	Intel Corporation
R2-2300829	Draft 38.306 CR for Rel-18 IDC UE capabilities	Intel Corporation
R2-2300830	Draft 38.331 CR for Rel-18 IDC UE capabilities	Intel Corporation
R2-2301485	Draft 38.300 CR for IDC Enhancements	Huawei, HiSilicon

8.10.2: FDM solution enhancements

TDoc	Title	Source
R2-2300522	More granular FDM indications	Ericsson
R2-2300523	IDC configuration and report in MR-DC	Ericsson
R2-2300543	FDM Solutions in IDC	Qualcomm Incorporated
R2-2300743	Discussion on detailed FDM solutions in IDC	Apple
R2-2300831	Enhanced FDM solution for IDC	Intel Corporation
R2-2300874	FDM solutions	Nokia, Nokia Shanghai Bell
R2-2300968	FDM solution for IDC	Lenovo
R2-2301108	Remaining issues for FDM and MRDC coordination	Xiaomi
R2-2301326	Discussion on FDM solution for IDC	Samsung
R2-2301486	Summary of [Post120][652][IDC] Further details of FDM solution (Huawei)	Huawei, HiSilicon
R2-2301487	Further discussion on details of FDM enhancement for NR IDC	Huawei, HiSilicon
R2-2301598	Discussion on FDM solution for R18 IDC	vivo
R2-2301706	Further Consideration on the IDC FDM Solutions	ZTE Corporation, Sanechips
R2-2301799	Discussion on IDC FDM solution enhancement	CATT
R2-2302071	[AT121][652][IDC] Discussion on FDM solution(Huawei)	Huawei

8.10.3: TDM solution

TDoc	Title	Source
R2-2300524	NR IDC TDM solutions and indications	Ericsson
R2-2300544	TDM Solutions in IDC	Qualcomm Incorporated
R2-2300744	Discussion on TDM solutions in IDC	Apple
R2-2300832	TDM solution for IDC	Intel Corporation
R2-2300875	TDM solutions	Nokia, Nokia Shanghai Bell
R2-2300943	Discussion on TDM solution enhancements	Sharp
R2-2301109	Remaining issues for TDM solutions	Xiaomi
R2-2301327	Discussion on TDM solution for IDC	Samsung
R2-2301488	Further discussion on details of TDM solution for NR IDC	Huawei, HiSilicon
R2-2301599	Summary of [Post120][651][IDC]Further details of TDM solution (vivo)	vivo
R2-2301600	Discussion on IDC TDM solution	vivo
R2-2301707	Further Consideration on the IDC TDM Solutions	ZTE Corporation, Sanechips
R2-2302074	LS to RAN4 on autonomous denial for IDC	RAN2
R2-2302261	[AT121][651][IDC] Discussion on TDM solution (vivo, xiaomi)	vivo
R2-2302263	LS to RAN4 on autonomous denial for IDC	vivo, xiaomi
R2-2302264	TP for IDC TDM solution	vivo

8.10.4: UE capabilities

TDoc	Title	Source
R2-2300745	IDC UE capability	Apple
R2-2300833	UE capabilities for IDC	Intel Corporation
R2-2300873	UE capabilities	Nokia, Nokia Shanghai Bell
R2-2301110	UE capability bits for IDC	Xiaomi
R2-2301489	Discussion on UE capability for IDC enhancement	Huawei, HiSilicon
R2-2301601	Discussion on IDC UE Capabilities	vivo
R2-2301708	Consideration on the IDC Capabilities	ZTE Corporation, Sanechips
R2-2301920	[Pre121][654][IDC] Summary of agenda item 8.10.4 UE capabilities (Intel)	Intel Corporation
R2-2302073	[AT121][653][IDC] Discussion on IDC capabilities (Intel)	Intel Corporation

8.11.1: Organizational

TDoc	Title	Source
R2-2300067	Reply LS on FS_5MBS_Ph2 progress (S2-2211256; contact: Huawei)	SA2
R2-2301165	Discussion on the LS from SA2	Huawei, HiSilicon
R2-2301934	LS on the open issues related to RAN WGs in 5MBS_Ph2 (S2-2303407; contact: Huawei)	SA2
R2-2302075	Reply LS on FS_5MBS_Ph2 progress (R3-231030; contact: Huawei)	RAN3

8.11.2.1: PTM configuration aspects and mobility

TDoc	Title	Source
R2-2300100	Discussion on multicast reception in RRC_INACTIVE state	OPPO
R2-2300178	Discussions on PTM Configuration and Mobility	CATT, CBN
R2-2300242	Initial Considerations on Mixed Approach	vivo Mobile Com. (Chongqing)
R2-2300243	Discussion on Mixed Approach from PHY Aspect	vivo Mobile Com. (Chongqing)
R2-2300283	Analysis of MCCH for sending PTM configuration	TD Tech, Chengdu TD Tech
R2-2300286	Discuss on PTM configuration for multicast in RRC INACTIVE	MediaTek inc.
R2-2300335	PTM configuration and mobility aspects for multicast reception in RRC_INACTIVE	Qualcomm Incorporated
R2-2300525	Discussion on PTM configuration aspects and mobility	Samsung R&D Institute India
R2-2300666	Discussion on PTM configuration and Mobility	Spreadtrum Communications
R2-2300672	Discussion on PTM configuration and mobility	NEC Corporation
R2-2300735	PTM Configuration and Mobility for INACTIVE Multicast Reception	Apple
R2-2300876	PTM configuration aspects and mobility	Nokia, Nokia Shanghai Bell
R2-2300947	PTM configuration and mobility for multicast reception in RRC_INACTIVE	Lenovo
R2-2301036	PTM configuration for multicast reception in RRC_INACTIVE	LG Electronics Inc.
R2-2301162	PTM configuration and mobility for multicast reception in RRC_INACTIVE	Huawei, HiSilicon
R2-2301206	PTM configuration aspects and mobility	Ericsson
R2-2301235	Discussion on PTM configuration and mobility	CMCC
R2-2301559	PTM configuration for multicast reception in RRC_INACTIVE	Intel Corporation
R2-2301586	PTM configuration and mobility aspects on multicast reception in RRC INACTIVE	Kyocera
R2-2301672	Multicast in RRC_INACTIVE	Sharp
R2-2301691	Considerations on the PTM configuration and mobility for multicast reception in RRC_INACTVE state	Beijing Xiaomi Software Tech
R2-2301843	PTM Configuration delivery for multicast reception in RRC_INACTIVE	ZTE, Sanechips

8.11.2.2: Notifications and RRC state transitions

TDoc	Title	Source
R2-2300179	Discussion on Notifications and RRC state transitions	CATT, CBN
R2-2300244	Discussion on (De)Activation and State Transition	vivo Mobile Com. (Chongqing)
R2-2300252	HARQ operation during RRC state transitions for multicast reception	NEC
R2-2300284	Common signalling for multicast reception in RRC_INACTIVE state	TD Tech, Chengdu TD Tech
R2-2300287	Notification and state transition for multicast in RRC INACTIVE	MediaTek inc.
R2-2300336	Notifications and RRC state transitions multicast reception in RRC_INACTIVE	Qualcomm Incorporated
R2-2300526	Discussion on Notification and RRC state transitions	Samsung R&D Institute India
R2-2300667	Discussion on Notification and RRC state transition	Spreadtrum Communications
R2-2300736	Group Notification and RRC State Transition for Multicast Reception	Apple
R2-2300877	Notifications and RRC state transitions	Nokia, Nokia Shanghai Bell
R2-2300948	Notification and State Transmission for Multicast Reception in RRC_INACTIVE	Lenovo
R2-2301037	Multicast activation deactivation notification and RRC state transitions	LG Electronics Inc.
R2-2301163	Notification and RRC state transition for multicast reception in RRC_INACTIVE	Huawei, HiSilicon
R2-2301205	Notifications and RRC state transitions	Ericsson
R2-2301236	Discussion on notification for RRC_INACTIVE multicast reception Ues	CMCC
R2-2301560	Notification and RRC state transition for multicast reception in RRC_INACTIVE	Intel Corporation
R2-2301587	Notification and RRC state transition aspects on multicast reception in RRC INACTIVE	Kyocera
R2-2301594	Session state change for UEs receiving Multicast in RRC_INACTIVE state	TCL Communication Ltd.
R2-2301674	Group Paging and Multicast session received in RRC_INACTIVE	Sharp
R2-2301692	Considerations on the notification and RRC transitions for the multicast reception in RRC_INACTIVE state	Beijing Xiaomi Software Tech
R2-2301844	Multicast session status change notification	ZTE, Sanechips

8.11.2.3: Other

TDoc	Title	Source
R2-2301038	Available multicast CFR in RRC_INACTIVE	LG Electronics Inc.
R2-2301070	Ensuring desired level of reliability for an MBS session in RRC_INACTIVE	InterDigital Inc.

8.11.3: Shared processing for MBS broadcast and Unicast reception

TDoc	Title	Source
R2-2300101	Discussion on support of FTA in NR	OPPO
R2-2300180	Discussion on Shared processing for MBS broadcast and Unicast reception	CATT, CBN
R2-2300285	Simultaneous unicast reception and MBS broadcast reception	TD Tech, Chengdu TD Tech
R2-2300288	Discussion on broadcast coexistence and signaling enhancement	MediaTek inc.
R2-2300334	Shared processing for MBS broadcast and unicast reception	Qualcomm Incorporated
R2-2300527	Shared processing for MBS broadcast and unicast reception	Samsung R&D Institute India
R2-2300683	Discussion on shared process for MBS broadcast and unicast	NEC Corporation
R2-2300737	Shared processing of MBS broadcast and unicast reception	Apple
R2-2301164	Discussion on shared processing for MBS broadcast and unicast reception	Huawei, HiSilicon
R2-2301207	MBS broadcast and unicast reception with shared resources	Ericsson
R2-2301561	Shared processing for simultaneous MBS broadcast and Unicast reception	Intel Corporation
R2-2301581	Discussion on shared processing for MBS broadcast and Unicast reception	CMCC
R2-2301588	Shared processing for inter-PLMN MBS broadcast reception	Kyocera
R2-2301702	Remaining issues for shared processing of MBS	Xiaomi
R2-2301753	Bandwidth signalling for shared processing	Nokia, Nokia Shanghai Bell
R2-2301845	Signaling framework for broadcast and unicast shared processing	ZTE, Sanechips

8.12.1: Organizational

TDoc	Title	Source
R2-2300034	LS on static and dynamic TAC solutions for mobile IAB node (R3-226831; contact: ZTE)	RAN3
R2-2300070	Reply LS on FS_VMR solutions review (S2-2211437; contact: Qualcomm)	SA2
R2-2300636	Workplan for Rel-18 mobile IAB	Qualcomm Inc. (Rapporteur)
R2-2302067	Reply LS on FS_VMR solutions review (R3-231011; contact: Qualcomm)	RAN3

8.12.2: Mobility Enhancements

TDoc	Title	Source
R2-2300305	Mobile IAB mobility-related issues and enhancements	Nokia, Nokia Shanghai Bell
R2-2300359	Mobile IAB mobility enhancement and interference mitigation	Huawei, HiSilicon
R2-2300437	Mobility Enhancement of mobile IAB-node and served UEs	Intel Corporation
R2-2300637	Enhancements for IAB-node mobility	Qualcomm Inc.
R2-2300643	Usage of “Supporting mobile-IAB” indication for cell reselection	SHARP Corporation
R2-2300710	CONNECTED mobility enhancement in mobile IAB	Apple
R2-2300711	Cell (re)selection and RNAU in mobile IAB	Apple
R2-2300807	mIAB mobility enhancement aspects	Samsung Electronics Romania
R2-2300823	Enhancements for mobility of IAB-node together with Ues	CATT
R2-2300844	Discussion on mobility enhancements for mobile IAB	NEC Corporation
R2-2300901	Discussion on mIAB mobility Enhacement	vivo
R2-2300952	Mobility enhancements for mobile IAB-node and its served UE	Lenovo
R2-2301065	On IAB node mobility state and associated UE behavior	InterDigital Inc.
R2-2301078	Discussion on mobility enhancement	ZTE, Sanechips
R2-2301103	Mobile IAB cell indication to UE behaviour	Sony
R2-2301301	Discussion on mobility enhancements for mIAB node	Ericsson
R2-2301419	Mobile IAB cell type for UE cell selection and reselection	Beijing Xiaomi Mobile Software
R2-2301589	Mobility enhancements for mobile IAB	Kyocera
R2-2301613	Idle mode mobility for mIAB-MT and UE, and miscellaneous issue	LG Electronics Inc.
R2-2301614	Connected mode mobility enhancements for onboard UEs	LG Electronics Inc.
R2-2301633	Enhancements for IAB-node mobility and onboard Ues	AT&T

8.12.3: Other

TDoc	Title	Source
R2-2300306	Mobile IAB TAC/RANAC issues	Nokia, Nokia Shanghai Bell
R2-2300360	BAP open issues due to the DU migration (two logical DUs) in mobile IAB	Huawei, Qualcomm Incorporate, LG Electronics, Intel Corporation, Lenovo, Apple, ZTE, vivo, Nokia, Nokia Shanghai Bell, Ericsson, Samsung
R2-2300438	TAC/RANAC update of mIAB-node	Intel Corporation
R2-2300638	Configuration of Network-controlled Repeater	Qualcomm Inc.
R2-2300668	Impacts of PCI changes for IDLE/INACTIVE UE	SHARP Corporation
R2-2300824	Other aspects for mobile IAB	CATT
R2-2300953	Discussion on BAP handling during mobile IAB-DU migration	Lenovo
R2-2301079	Discussion on TAC and RNAC configuration of mobile IAB	ZTE, Sanechips
R2-2301100	PCI collision in mobile IAB	Sony
R2-2301194	TAC handling for mIAB	Samsung R&D Institute UK
R2-2301302	Discussion on SA2 and migration aspects for mobile IAB	Ericsson

8.13.1: Organizational

TDoc	Title	Source
R2-2300026	LS on user consent of Non-public Network (R3-226006; contact: ZTE)	RAN3
R2-2300031	Response LS on Possibility on LBT-FailureRecoveryConfig (R3-226809; contact: Nokia)	RAN3
R2-2302065	LS on MRO for CPC and CPA and fast MCG recovery (R3-230992; contact: Huawei)	RAN3

8.13.2: MRO for inter-system handover for voice fallback

TDoc	Title	Source
R2-2301274	MRO for inter-system handover for voice fallback	Ericsson

8.13.3: MDT override

TDoc	Title	Source
R2-2300293	Consideration on Inter-RAT Signaling Based Logged MDT Override Protection	CATT
R2-2300716	On MDT override protection	Apple
R2-2301001	Signalling based logged MDT override protection	Nokia, Nokia Shanghai Bell
R2-2301144	Consideration on MDT override issues	ZTE Corporation, Sanechips
R2-2301192	Inter-RAT signaling based logged MDT override protection	Samsung
R2-2301275	MDT enhancements	Ericsson
R2-2301420	Signalling based logged MDT override protection	Qualcomm Incorporated
R2-2301570	Discussion on the inter-system signalling based MDT override protection	Huawei, HiSilicon
R2-2301631	Considerations on the signaling based logged MDT override protection for E-UTRAN	Beijing Xiaomi Software Tech
R2-2301949	Summary of 8.13.3 MDT override	Nokia (Rapporteur)

8.13.4: SHR and SPCR

TDoc	Title	Source
R2-2300294	Discussion on inter-RAT SHR and SPR	CATT
R2-2300681	Remaining issues on SON for SPR	vivo
R2-2300954	Successful Handover Report for inter-RAT HO	Lenovo
R2-2300955	SON enhancements for SPR	Lenovo
R2-2301002	SPR content enhancements	Nokia, Nokia Shanghai Bell
R2-2301003	SPR and SHR generation and reporting	Nokia, Nokia Shanghai Bell
R2-2301044	Discussion on SHR and SPCR	Xiaomi
R2-2301145	Consideration on SHR and SPR	ZTE Corporation, Sanechips
R2-2301195	SON/MDT enhancements for SHR and SPCR	Samsung
R2-2301276	SPR and SHR enhancements	Ericsson
R2-2301421	Discussion on SHR for inter-RAT handover and successful PSCell change reporting	Qualcomm Incorporated
R2-2301557	Discussion on successful PSCell change report	Sharp
R2-2301571	Discussion on SHR and SPR	Huawei, HiSilicon
R2-2301763	Discussion on SPR	NTT DOCOMO, INC.
R2-2301947	Summary of AI 8.13.4 SHR and SPCR	ZTE Corporation, Sanechips

8.13.5: SON for NR-U

TDoc	Title	Source
R2-2300295	SON Enhancement for NR-U	CATT
R2-2300956	Discussion on MRO for NR-U	Lenovo
R2-2301004	Discussion on storing LBT-FailureRecoveryConfig (Reply LS in R2-2300031)	Nokia, Nokia Shanghai Bell
R2-2301045	Discussion on SON for NR-U	Xiaomi
R2-2301146	Consideration on NR-U related SON	ZTE Corporation, Sanechips
R2-2301213	SON/MDT enhancements for NR-U	Samsung
R2-2301264	SONMDT enhancement for NR-U	CMCC
R2-2301277	Enhancements of SON reports for NR-U	Ericsson
R2-2301422	Discussion on NR-U Related Enhancements	Qualcomm Incorporated
R2-2301572	Discussion on SON for NR-U	Huawei, HiSilicon
R2-2302070	[AT121][802][R18 SON/MDT] SON for NR-U (Ericsson) Discussion on how to clarify random access attempt	Ericsson (email rapporteur)
R2-2302173	Pre-meeting summary of 8.13.5 (SON for NRU)	Ericsson (Summary rapporteur)

8.13.6: RACH enhancement

TDoc	Title	Source
R2-2300296	RACH enhancement for SON	CATT
R2-2300717	Remaining issues of SON enhancements for RACH	Apple
R2-2300957	Enhancements for SN RACH report	Lenovo
R2-2301147	Consideration on RACH enhancements	ZTE Corporation, Sanechips
R2-2301214	SN RACH Report for EN-DC/NG-EN-DC	Samsung
R2-2301278	RA report enhancement	Ericsson
R2-2301424	On SgNB RACH report for MR-DC scenario	Qualcomm Incorporated
R2-2301573	Discussion on RACH enhancement	Huawei, HiSilicon
R2-2301582	Further Consideration on RACH Enhancement	CMCC
R2-2301635	Discussion on the SON/MDT enhancement for RACH report	Beijing Xiaomi Software Tech
R2-2301812	Discussion on RACH enhancements	China Telecom
R2-2301923	Pre-meeting summary of 8.13.6	Huawei
R2-2302066	Reply LS on RACH enhancement for R18 SONMDT	RAN2
R2-2302069	Report of [AT121][803][R18 SONMDT] RACH enhancement (Huawei)	Huawei (email rapporteur)
R2-2302269	Draft LS on RACH enhancement for R18 SONMDT	Huawei

8.13.7: SON/MDT enhancements for Non-Public Networks

TDoc	Title	Source
R2-2301265	SONMDT enhancement for NPN	CMCC

8.13.8: Other

TDoc	Title	Source
R2-2300297	Considerations on MRO about Fast MCG recovery Enhancement	CATT
R2-2300298	Discussion on SONMDT Enhancements for CPAC	CATT
R2-2300682	Discussion on MRO for CPAC	vivo
R2-2300958	MRO for fast MCG link recovery	Lenovo
R2-2300959	SON enhancements for CPAC	Lenovo
R2-2301005	MRO enhancements for Fast MCG recovery and for MR-DC CPAC	Nokia, Nokia Shanghai Bell
R2-2301006	RA report retrieval	Nokia, Nokia Shanghai Bell
R2-2301148	Remaining issues on fast MCG recovery	ZTE Corporation, Sanechips
R2-2301149	Consideration on MRO for CPAC	ZTE Corporation, Sanechips
R2-2301193	SON/MDT enhancements for Fast MCG Recovery and CPAC MRO	Samsung
R2-2301279	MRO for SCG failure and fast MCG recovery optimization	Ericsson
R2-2301425	Discussion on fast MCG Recovery Failure	Qualcomm Incorporated
R2-2301565	SON enhancement on fast MCG recovery	Sharp
R2-2301566	Discussion on failure information for CPAC	Sharp
R2-2301574	Discussion on Fast MCG recovery	Huawei, HiSilicon
R2-2301575	Discussion on MRO for CPAC	Huawei, HiSilicon
R2-2301583	Further considerations on fast MCG recovery	CMCC
R2-2301584	MHI Enhancement for SCG Activation/Deactivation	CMCC,Ericsson, CATT
R2-2301585	SON MDT enhancement for MR-DC CPAC	CMCC
R2-2301775	Discussion on CPAC failure report	NTT DOCOMO, INC.
R2-2301811	SON on fast MCG recovery	OPPO
R2-2301833	Further steps on MRO for MR-DC SCGFailureInformation	Samsung, Lenovo
R2-2301856	Discussion of SON on MR-DC CPAC	OPPO

8.14.1: Organizational

TDoc	Title	Source
R2-2300085	Reply LS to RAN3 on RAN visible QoE value (S4-221604; contact: Qualcomm)	SA4
R2-2300091	LS/r on RAN visible QoE value (reply to 3GPP-LS8) (SG12-LS29; contact: Ericsson)	ITU-T SG12
R2-2301335	Running CR for QoE measurements	Ericsson
R2-2301754	Revised Work plan for Rel-18 NR QoE Enhancement	China Unicom
R2-2301940	Reply LS on QoE measurements in RRC IDLE/INACTIVE states (S4-230369; contact: Huawei)	SA4
R2-2302072	LS on assistance information for handling of QoE reporting upon RAN overload (R3-231028; contact: Huawei)	RAN3
R2-2302307	38.300 running CR for R18 QoE enhancement in NR	China Unicom, Huawei, HiSilicon
R2-2302308	Running CR for QoE measurements	Ericsson
R2-2302310	Running CR for QoE measurements	Ericsson

8.14.2: QoE measurements in RRC_IDLE INACTIVE

TDoc	Title	Source
R2-2300330	Discussion on support of QoE measurements in RRC_IDLE and RRC_INACTIVE	Lenovo
R2-2300353	Further discussion on QoE measurement in IDLE and INACTIVE	ZTE Corporation, Sanechips
R2-2300602	Discussion on QoE measurements for MBS broadcast services	Huawei, HiSilicon
R2-2300719	QoE Measurements Collection in IDLE/INACTIVE States	Apple
R2-2301014	QoE for IDLE and Inactive state	Qualcomm Incorporated
R2-2301246	Discussion on QMC in RRC_IDLE and RRC_INACTIVE	CMCC
R2-2301336	QoE measurements in RRC_INACTIVE and RRC_IDLE	Ericsson
R2-2301638	Discussion on QoE measurement in RRC_IDLE and RRC_INACTIVE	Samsung
R2-2301662	Discussion on QoE measurements for NR MBS	Nokia, Nokia Shanghai Bell
R2-2301757	Discussion on QoE measurements in RRC_IDLE and INACTIVE states	China Unicom
R2-2301800	Discussion on QoE measurements in RRC IDLE and INACTIVE state	CATT
R2-2301894	Discussion on QoE measurements in RRC IDLE and INACTIVE state	CATT

8.14.3: Rel-17 leftover topics for QoE

TDoc	Title	Source
R2-2300332	Discussion on Rel-17 leftover topics for QoE	Lenovo
R2-2300354	Further discussion on Rel-17 leftover issues for QoE	ZTE Corporation, Sanechips
R2-2300601	Discussion on event-based RAN visible QoE	Huawei, HiSilicon
R2-2300720	Views on Leftover Issues of Rel-17 QoE	Apple
R2-2300988	Discussion on event-based RVQoE report	NEC
R2-2301016	Discussion on Rel-17 leftover issues	Qualcomm Incorporated
R2-2301247	Discussion on QoE reporting enhancement for overload scenrio	CMCC
R2-2301338	QoE rel-17 leftovers	Ericsson
R2-2301639	Discussion on event-based RAN visible QoE report	Samsung
R2-2301663	QMC enhancements for RAN visible QoE and RAN overload	Nokia, Nokia Shanghai Bell
R2-2301801	Discussion on Rel-17 leftover topics for QoE	CATT
R2-2301816	Considerations on QoE Rel-17 leftover issues	China Telecom
R2-2302042	LS on buffer level threshold-based RVQoE reporting	RAN2

8.14.4: Support of QoE measurements for NR-DC

TDoc	Title	Source
R2-2300331	Discussion on support of QoE measurements for NR-DC	Lenovo
R2-2300355	Further discussion on QoE measurement for NR-DC	ZTE Corporation, Sanechips
R2-2300600	Discussion on QoE measurements in NR-DC	Huawei, HiSilicon
R2-2300721	QoE Reporting for NR-DC	Apple
R2-2301015	RAN2 issues to support QoE collection in NR-DC	Qualcomm Incorporated
R2-2301337	QoE measurements in NR-DC	Ericsson
R2-2301640	Discussion on QoE measurement for NR-DC	Samsung
R2-2301664	QMC support in NR-DC	Nokia, Nokia Shanghai Bell
R2-2301758	Discussion on QoE configuration and reporting for NR-DC	China Unicom
R2-2301802	Discussion on support of QoE measurement for NR-DC	CATT

8.14.5: Other topics

TDoc	Title	Source
R2-2300356	Discussion on Rel-18 other QoE enhancement	ZTE Corporation, Sanechips
R2-2300603	QoE continuity between LTE-5GC and NR	Huawei, HiSilicon
R2-2300631	Discussion on QoE measurement during intra-5GC inter-RAT handover	Lenovo
R2-2300722	QoE Continuity During Intra-5GC Inter-RAT Handover	Apple
R2-2301339	QoE measurements at IRAT handover	Ericsson
R2-2301641	Discussion on QoE measurement continuity during inter-RAT handover	Samsung
R2-2301665	On QoE continuity during inter-RAT handover	Nokia, Nokia Shanghai Bell
R2-2301756	Discussion on the QoE continuity during intra-5GC inter-RAT HO	China Unicom
R2-2301803	Discussion on the continuity of QoE measurement	CATT
R2-2302005	Report of [AT121][201][QoE] Continuity of QoE measurements during intra-5GC inter-RAT HO (Huawei)	Huawei (email rapporteur)
R2-2302020	LS on Continuity of QoE measurements during intra-5GC inter-RAT HO	RAN2

8.15.1: Organizational

TDoc	Title	Source
R2-2300135	Work plan of R18 SL-Evo	OPPO, LG
R2-2302019	LS on co-channel coexistence (R4-2303718; contact: Huawei)	RAN4
R2-2302267	Reply LS on SL LBT failure indication and consistent SL LBT failure (R1-2302118; contact: vivo)	RAN1

8.15.2: SL-U

TDoc	Title	Source
R2-2300119	Remaining issues on CAPC for SL-U	Huawei, HiSilicon
R2-2300120	Further discussin on SL-U	Huawei, HiSilicon
R2-2300126	Discussion on remaining issues in SL-U	OPPO
R2-2300136	Discussion on LBT impact in SL-U	OPPO, MediaTek Inc., Intel
R2-2300339	Discussion on SL LBT failure for UE in RRC idle/inactive/OOC state	SHARP Corporation
R2-2300342	Remaining issues on RAN2 aspects for SL-U	vivo
R2-2300343	Discussion on remaining issues for CAPC in SL-U	vivo
R2-2300499	Discussion on other MAC impacts for NR SL-U	Lenovo
R2-2300519	Aspects of channel access mechanisms	Ericsson
R2-2300520	CAPC table and MAC multiplex rules	Ericsson
R2-2300615	Further discussion on CAPC for SL-U	Intel Corporation
R2-2300616	On SL-LBT aspects	Intel Corporation
R2-2300622	CAPC and COT sharing for SL Unlicensed	InterDigital
R2-2300623	LBT Failure for SL Unlicensed	InterDigital
R2-2300624	Configured Grants for SL Unlicensed	InterDigital
R2-2300645	Remaining issues on channel access priority in SL-U	Spreadtrum Communications
R2-2300646	Consistent LBT failure handling for SL-U	Spreadtrum Communications
R2-2300669	Consideration on CAPC for SL-U	CATT
R2-2300670	Further Discussion on LBT	CATT
R2-2300705	Discussion on remaining issues of CAPC in SL-U	Apple
R2-2300706	Further discussion on MAC impacts due to LBT and COT sharing in SL-U	Apple
R2-2300840	Discussion on channel access for sidelink operation on unlicensed spectrum	Xiaomi
R2-2300841	Discussion on LBT for sidelink operation on unlicensed spectrum	Xiaomi
R2-2300915	Discussion on MAC related aspects for SL-U	ZTE Corporation, Sanechips
R2-2300916	Discussion on CAPC in SL-U	ZTE Corporation, Sanechips
R2-2300970	Remaining issue of channel access priority for NR SL-U	Lenovo
R2-2300971	Discussion on LBT impact to MAC for NR SL-U	Lenovo
R2-2300989	LBT failure detection and recovery procedure for SL-U	NEC
R2-2300994	Discussion on sidelink un-licensed	ITL
R2-2301356	Considerations on consistent LBT failure and HARQ procedure	Nokia, Nokia Shanghai Bell
R2-2301357	On Sidelink DRX and remaining CPAC issues	Nokia, Nokia Shanghai Bell
R2-2301462	Considerations on resource allocation for SL-U	Nokia, Nokia Shanghai Bell
R2-2301474	Remaining SL CAPC issues	Samsung Research America
R2-2301475	SL resource allocation	Samsung Research America
R2-2301542	Discussion on SL-U	ASUSTeK
R2-2301700	Discussion on sidelink unlicensed	Qualcomm India Pvt Ltd
R2-2301705	Discussion on sidelink CAPC	Qualcomm India Pvt Ltd
R2-2301719	Discussion on RAN2 aspects on SL-U	LG Electronics France
R2-2301722	LBT impact to SL-U	MediaTek Inc.
R2-2301723	Channel Access Priority Classes for SL-U	MediaTek Inc.
R2-2302035	Summary of [AT121][508][V2X/SL] COT usage scenario and LCP enhancement (OPPO)	OPPO
R2-2302036	LS to RAN1 on SL resource (re)selection	RAN2
R2-2302303	LS on LBT and SL resource (re)selection	RAN2
R2-2302304	LS on RAN2 agreement for sidelink CAPC	RAN2

8.15.3: SL-FR2

TDoc	Title	Source
R2-2300127	Discussion on SL-FR2 impact	OPPO
R2-2300394	Discussion on SL-FR2 impact to RAN2	Xiaomi
R2-2300489	Discussion on SL-FR2	Huawei, HiSilicon
R2-2300521	SL in FR2	Ericsson
R2-2300617	On FR-2 aspects for SL-U	Intel Corporation
R2-2300671	Discussion on Sidelink Operation on FR2	CATT
R2-2300707	Discussion on RAN2 work of SL FR2	Apple
R2-2300917	Initial consideration on sidelink FR2	ZTE Corporation, Sanechips
R2-2301374	Discussion on RAN2 aspects for FR2 licensed spectrum	vivo
R2-2301701	Discussion on Sidelink FR2	Qualcomm India Pvt Ltd
R2-2301720	Discussion on RAN2 aspects on SL-FR2	LG Electronics France
R2-2301887	RAN2 Aspects of NR Sidelink Operation in FR2	Fraunhofer IIS, Fraunhofer HHI

8.16.1: Organizational

TDoc	Title	Source
R2-2301440	Outcome of [Post120][054][AIML18] Data Collection	Ericsson, vivo

8.16.2: AIML methods

TDoc	Title	Source
R2-2300096	AIML Methods Discussion in General	OPPO
R2-2300097	Initial Consideration on Data Collection for AIML	OPPO
R2-2300249	AIML Architecture Assumptions	NEC
R2-2300253	AIML Model transfer Requirements during Handover	NEC
R2-2300257	On AI/ML model transfer over radio interface	Dell Technologies
R2-2300289	Consideration on General Aspects of AIML for NR Air-interface	CATT
R2-2300327	Discussion on AI/ML Model Transfer and Delivery	Futurewei Technologies
R2-2300374	Model ID and Model Identification	MediaTek Inc.
R2-2300393	Discussion on AIML for NR air interface	Xiaomi
R2-2300398	AIML methods	Nokia UK
R2-2300417	Discussion on life cycle management: RAN2 impact	Intel Corporation
R2-2300418	Analysis on data collection framework for AI/ML air interface	Intel Corporation
R2-2300660	Discussion on AIML methods	Spreadtrum Communications
R2-2300679	Further discussion on AIML methods	vivo
R2-2300708	Open issues on AI/ML model delivery and data collection in post-meeting email discussion	Apple
R2-2300709	Discussion on RAN2 aspects of AI/ML model identification, LCM and capability	Apple
R2-2300806	Discussion on RAN2 aspects for LCM	MediaTek Inc.
R2-2300950	General issues on AI for air interface	Lenovo
R2-2301033	Discussion on AIML methods for general aspects of AIML via air interface	Fujitsu
R2-2301055	Data collection for AI/ML	InterDigital Inc.
R2-2301101	Some considerations about CP/UP solution and model ID	Sony
R2-2301105	AI/ML Capability Reporting	Samsung Electronics Nordic AB
R2-2301107	Data collection for AI/ML	Samsung Electronics Nordic AB
R2-2301256	Discussion on AIML methods for NR air interface	CMCC
R2-2301427	Discussion on AI/ML methods	Qualcomm Incorporated
R2-2301441	General aspects for AIML for NR air interface	Ericsson
R2-2301576	Report of [Post120][053][AIML18] model transfer delivery (Huawei)	Huawei
R2-2301577	Discussion on AIML methods	Huawei, HiSilicon
R2-2301634	Protocol aspects of AI/ML framework for NR air interface	AT&T
R2-2301769	Data Collection	LG Electronics
R2-2301770	Model Transfer Delivery	LG Electronics
R2-2301787	Further Considerations on Data Collection	ZTE Corporation,Sanechips
R2-2301788	Further Considerations on AI Function Mapping and Model Transfer	ZTE Corporation,Sanechips
R2-2301835	Discussion on AIML methods	TCL Communication Ltd.
R2-2301841	AI_ML model life cycle management during RRC state transitions and mobility	Rakuten Symphony
R2-2302268	Report of Offline 027 model transfer delivery	Huawei
R2-2302286	Summary of [AT121][025]: Progress table of analyzing data collection framework (Apple)	Apple

8.16.3: Use case specific aspects

TDoc	Title	Source
R2-2300290	Consideration on the Use Case Specific AIML for NR Air-interface	CATT
R2-2300399	Use case specific aspects	Nokia UK
R2-2300661	Discussion on use case specific aspects	Spreadtrum Communications
R2-2300680	Consideration of procedure and signaling of CSI compression	vivo
R2-2300697	Use case specific aspects	InterDigital
R2-2300951	Discussion on AI for air interface use cases	Lenovo
R2-2301034	Discussion on use case specific aspects of AIML via air interface	Fujitsu
R2-2301191	Consideration on AI/ML for positioning accuracy enhancement	Xiaomi
R2-2301257	Discussion on use case specific aspects for AIML for NR air interface	CMCC
R2-2301429	Discussion on the use case specific aspects	Qualcomm Incorporated
R2-2301442	Use cases aspect for AIML for NR air interface	Ericsson
R2-2301578	Discussion on use case specific aspects	Huawei, HiSilicon

8.17.1: Organizational

TDoc	Title	Source
R2-2300902	Work planning of R18 MUSIM	vivo
R2-2302000	LS on priority for MUSIM gaps (R4-2303249; contact: vivo)	RAN4
R2-2302026	38.300 Running Stage-2 CR for NR MUSIM enhancements	vivo

8.17.2: Temporary capability restriction for MUSIM

TDoc	Title	Source
R2-2300098	Scenarios Clarification for R18 MUSIM	OPPO
R2-2300099	Initial Consideration on Temporary UE Capability Restriction	OPPO
R2-2300435	Scenarios and requirements for capability restriction request for Rel-18 MUSIM	Intel Corporation
R2-2300436	Signalling to indicate temporary capability reduction for Rel-18 MUSIM	Intel Corporation
R2-2300496	Applicable scenarios for R18 MUSIM	Huawei, HiSilicon
R2-2300498	Solutions for MUSIM capability restriction removal of restriction	Huawei, HiSilicon
R2-2300753	Discussion on Temporary Capability Restriction for DualRx/DualTx MUSIM UEs	Apple
R2-2300773	Report of [Post119bis-e][212][MUSIM] Rel-18 MUSIM solutions	Qualcomm Incorporated, vivo
R2-2300816	Discussion on temporary UE capability restriction for MUSIM	MediaTek Inc.
R2-2300855	RAN3 impact of temporary UE capability switching for MUSIM	China Telecom
R2-2300903	Discussion on temporary capability restriction for Rel-18 Multi-SIM	vivo
R2-2300922	Baseline signaling procedure for primary scenarios of Dual TX/RX MUSIM operation	Nokia, Nokia Shanghai Bell
R2-2300923	Analysis on additional capability coordination scenarios for Dual TX/RX MUSIM operation	Nokia, Nokia Shanghai Bell
R2-2300969	Consideration on dual Tx/Rx Multi-SIM	Lenovo
R2-2301116	Capability sharing issue for SRS Tx switching capability	Xiaomi
R2-2301173	UE Capability restriction for Dual-Active MUSIM	China Telecommunications
R2-2301428	UE Capability Update for Dual-Active MUSIM	Qualcomm Incorporated
R2-2301448	Overall Dual-RX/TX MUSIM Solution	Ericsson
R2-2301449	Discussion on MUSIM gaps for a Dual-RX/Dual-TX UE	Ericsson
R2-2301543	Discussion on Dual Tx/Rx Multi-SIM	ASUSTeK
R2-2301673	Capability Restriction for eMUSIM	Sharp
R2-2301709	Consideration on the Temporary Capability Restriction	ZTE Corporation, Sanechips
R2-2301742	General Solution for Rel-18 MUSIM	LG Electronics
R2-2301743	LS on SCG Deactivation while Multi-SIM Operation	LG Electronics
R2-2301744	Further Considerations for Rel-18 MUSIM	LG Electronics
R2-2301881	Discussion on possible solutions for dual Rx/Tx MUSIM devices	DENSO CORPORATION
R2-2302007	[Draft] LS to RAN4 on Rel-18 MUSIM impacts	vivo
R2-2302008	[AT121][202][MUSIM] LS to RAN4 on Rel-18 MUSIM impacts (vivo)	vivo

8.17.3: Other

TDoc	Title	Source
R2-2300517	MUSIM Band Conflict Issue Handling	Samsung R&D Institute India
R2-2300754	Discussion on Signaling solutions for Band Conflict Mitigation for DualRx/Dual Tx MUSIM UEs	Apple
R2-2300904	Discussion on MUSIM band conflict handling	vivo
R2-2301117	Discussion on the band conflicts for MUSIM	Xiaomi
R2-2301446	Coordination of MUSIM gaps for NR-DC	Qualcomm Incorporated
R2-2301710	Consideration on the Scheduling Gap for the MR-DC	ZTE Corporation, Sanechips
R2-2301778	Further discussion on MN-SN MUSIM gaps coordination	Samsung Electronics Austria

8.18.2: General

TDoc	Title	Source
R2-2300182	Mobile Terminated Small Data Transmission Procedure in RRC_INACTIVE state	Samsung Electronics Co., Ltd
R2-2300245	Discussion on Supporting MT-SDT	vivo Mobile Com. (Chongqing)
R2-2300337	Discussion on paging triggered SDT	SHARP Corporation
R2-2300386	Discussion on general pocedure of MT-SDT	OPPO
R2-2300424	MT-SDT and quality measurements	Ericsson España S.A.
R2-2300434	MT-SDT mechanism (including RB, paging, resume and capabilities)	Intel Corporation
R2-2300497	Discussion on the MT-SDT procedure	Lenovo
R2-2300559	MT-SDT procedure	ZTE Corporation, Sanechips
R2-2300605	Discussion on MT-SDT procedure	Huawei, HiSilicon
R2-2300651	Discussion on general procedure for MT-SDT	Spreadtrum Communications
R2-2300738	Discussion on MT-SDT	Apple
R2-2300777	Discussion on MT-SDT procedure	LG Electronics Inc.
R2-2300805	Discussion on MT-SDT	NEC
R2-2301102	DL SDT triggering and procedures	Sony
R2-2301111	Remaining issues of MT SDT procedure	Xiaomi
R2-2301245	Discussion on MT-SDT	CMCC
R2-2301281	Discussion on MT-SDT	Qualcomm Incorporated
R2-2301331	MT-SDT procedure	Nokia, Nokia Shanghai Bell
R2-2301497	Mobile terminated SDT	InterDigital
R2-2301544	Discussion on DL SPS for MT-SDT	ASUSTeK
R2-2301804	Discussion on support of MT-SDT	CATT
R2-2301813	Discussion on MT-SDT procedure	China Telecom
R2-2302101	[AT120][306][R18 MT-SDT] summary of offline discussion (ZTE)	ZTE Corporation (offline rapporteur)

8.19.1: Organizational

TDoc	Title	Source
R2-2300029	Reply LS on long eDRX support for RRC_INACTIVE (R3-226776; contact: Nokia, Ericsson)	RAN3
R2-2300082	Reply LS on long eDRX support for RRC_INACTIVE (S2-2301858; contact: Ericsson)	SA2
R2-2301696	WI work plan for Rel-18 RedCap	Ericsson
R2-2302059	Reply LS on long eDRX support for RRC_INACTIVE (R3-230803; contact: Ericsson)	RAN3

8.19.2: Enhanced eDRX in RRC_INACTIVE

TDoc	Title	Source
R2-2300159	Discussion on long eDRX cycle in RRC_INACTIVE	OPPO
R2-2300211	Discussion on enhanced eDRX in RRC_INACTIVE	CATT
R2-2300405	RAN2 impact to support eDRX in RRC_INACTIVE above 10.24sec	Intel Corporation
R2-2300419	Discussion on e-DRX for eRedcap Devices	Xiaomi Communications
R2-2300765	Basic principles of RAN PTW/PH eDRX INACTIVE design	Apple
R2-2300794	Discussion on enhanced eDRX in RRC_INACTIVE	Huawei, HiSilicon
R2-2301058	Enhanced eDRX in RRC_INACTIVE	ZTE Corporation, Sanechips
R2-2301075	Enhanced eDRX cycle in RRC_INACTIVE for eRedCap UEs	vivo, Guangdong Genius
R2-2301239	Discussion on eDRX in RRC_INACTIVE	CMCC
R2-2301292	Discussion on enhanced eDRX in RRC inactive	Qualcomm Incorporated
R2-2301333	On eDRX for enhanced RedCap	Nokia, Nokia Shanghai Bell
R2-2301373	eDRX in RRC Inactive	MediaTek Inc.
R2-2301642	Review on Rel-17 eDRX and discussion on Rel-18 eDRX	Samsung
R2-2301643	Paging monitoring cycle when INACTIVE eDRX cycle is longer than 10.24sec	Samsung
R2-2301697	Discussion on long eDRX cycles in RRC_INACTIVE	Ericsson
R2-2302081	[draft] LS on INACTIVE eDRX above 10.24sec and SDT	Intel Corporation
R2-2302082	LS on INACTIVE eDRX above 10.24sec and SDT	RAN2

8.19.3: Further reduced UE complexity in FR1

TDoc	Title	Source
R2-2300160	Discussion on early indication for RedCap UE	OPPO
R2-2300174	Discussion on cellbarring for eRedCap Ues	OPPO
R2-2300212	Discussion on further UE complexity reduction	CATT
R2-2300406	RAN2 impacts to support UEs with Baseband Bandwidth Reduction	Intel Corporation
R2-2300407	RAN2 impacts to support UEs with Data Rate Reduction	Intel Corporation
R2-2300420	Discussion on early indication for eRedcap devices	Xiaomi Communications
R2-2300421	Discussion on UE access restrictions and other impacts for eRedcap devices	Xiaomi Communications
R2-2300652	Discussion on further reduced UE complexity in FR1 for Rel-18 RedCap UE	Spreadtrum Communications
R2-2300764	Access and Indication topics of eRedCap	Apple
R2-2300919	Early identification and access restriction for eRedCap UEs	Huawei, HiSilicon
R2-2300920	Discussion on how to capture the capability of eRedCap UEs	Huawei, HiSilicon
R2-2300990	Considerations on additional separate early indication(s) for eRedCap UE	NEC
R2-2301059	Early indication for eRedCap UE	ZTE Corporation, Sanechips
R2-2301061	Other aspects for further reducing UE complexity	ZTE Corporation, Sanechips
R2-2301076	Discussion on Early Indication for eRedCap	vivo, Guangdong Genius
R2-2301077	Discussion on SI Enhancements for eRedCap	vivo, Guangdong Genius
R2-2301240	Discussion on further reduced UE complexity	CMCC
R2-2301290	On early indication for enhanced RedCap	Nokia, Nokia Shanghai Bell
R2-2301293	Discussion on further complexity reduction for eRedCap UE	Qualcomm Incorporated
R2-2301294	Discussion on optional UE capability filter for eRedCap UE	Qualcomm Incorporated, Ericsson
R2-2301332	On access restrictions for enhanced RedCap	Nokia, Nokia Shanghai Bell
R2-2301430	Early indication and access restrictions for eRedCap UE	Sierra Wireless. S.A.
R2-2301644	Discussion on separate early indication for Rel-18 RedCap	Samsung
R2-2301698	Early Indication for eRedCap UEs	Ericsson
R2-2301699	Discussion on initial BWP configuration for eRedCap UEs	Ericsson
R2-2301726	Discussion on early indication for Rel-18 RedCap UE	LG Electronics Inc.
R2-2301872	Early indication / paging for eRedcap	Sequans Communications

8.20: NR TEI18

TDoc	Title	Source
R2-2301166	GNSS LOS/NLOS assistance information	Vodafone, Spirent, Ericsson, Telecom Italia

8.20.1: TEI proposals by Other Groups

TDoc	Title	Source
R2-2302052	LS on SR periodicity (R1-2302187; contact: Ericsson)	RAN1

8.20.2: TEI proposals by RAN2

TDoc	Title	Source
R2-2300326	BFD relaxation with mTRP	vivo, Qualcomm, ZTE Corporation, Fujitsu, Guangdong Genius
R2-2300452	SDT Enhancements for Configured grants [SDT-Enh-CG]	Ericsson España S.A.
R2-2300532	Support of Local Cartesian Coordinates in LPP	Qualcomm Incorporated
R2-2300533	Support of Local Cartesian Coordinates in LPP	Qualcomm Incorporated
R2-2300797	RedCap CFR for MBS broadcast	Qualcomm Incorporated, Ericsson, Verizon, FirstNet
R2-2301172	GNSS LOS/NLOS assistance information	Vodafone, Spirent, Ericsson, Telecom Italia
R2-2301296	Relay based Positioning Procedure	Ericsson
R2-2301447	Reporting the availability of inter-frequency measurements	Ericsson
R2-2301579	Discussion on UE behaviours of delay measurements upon MO updates	Huawei, HiSilicon
R2-2301645	Support for GNSS Satellite APC	Swift Navigation, Intel Corporation, InterDigital, CATT
R2-2301649	Positioning of remote UEs	MediaTek Inc., CATT, Huawei, HiSilicon
R2-2301650	Uplink positioning restrictions for UE-to-network remote UE [PosL2RemoteUE]	MediaTek Inc., CATT, Huawei, HiSilicon
R2-2301651	Downlink positioning support and posSIB request for L2 UE-to-network remote UE (Alt 1) [PosL2RemoteUE]	MediaTek Inc., CATT, Huawei, HiSilicon
R2-2301652	Stage 2 support for GNSS Satellite APC [Rel18APC]	Swift Navigation, Intel Corporation, InterDigital, CATT
R2-2301653	Downlink positioning support and posSIB request for L2 UE-to-network remote UE (Alt 2) [PosL2RemoteUE]	MediaTek Inc., CATT, Huawei, HiSilicon
R2-2301654	Stage 2 support for GNSS Satellite APC [Rel18APC]	Swift Navigation, Intel Corporation, InterDigital, CATT
R2-2301655	Indication to positioning server of operation as a L2 UE-to-Network Remote UE [PosL2RemoteUE]	MediaTek Inc., CATT, Huawei, HiSilicon
R2-2301666	Support for GNSS Satellite APC in LPP [Rel18APC]	Swift Navigation, Intel Corporation, InterDigital, CATT
R2-2301667	Support for SSR Phase Bias with Yaw	Swift Navigation, Intel Corporation, InterDigital
R2-2301668	Stage 2 support for SSR Phase Bias with Yaw [Rel18Yaw]	Swift Navigation, Intel Corporation, InterDigital
R2-2301670	Stage 2 support for SSR Phase Bias with Yaw [Rel18Yaw]	Swift Navigation, Intel Corporation, InterDigital
R2-2301671	Support for SSR Phase Bias with Yaw in LPP [Rel18Yaw]	Swift Navigation, Intel Corporation, InterDigital
R2-2301761	Beam Failure Detection upon TRS-based SCell Activation	NTT DOCOMO INC.
R2-2302122	[AT121][401][POS] Yaw and APC (Swift)	Swift Navigation (Moderator)
R2-2302133	GNSS LOS/NLOS assistance information	Vodafone, Spirent, Ericsson, Telecom Italia

8.21.1: RAN4 led items

TDoc	Title	Source
R2-2300045	LS on BWP operation without bandwidth restriction (R4-2220437; contact: vivo)	RAN4
R2-2300047	Response LS on extending the maximum range for NS values (R4-2220493; contact: Apple)	RAN4
R2-2300769	Discussion on the extention of NS values	Apple
R2-2300866	Extending NS value range	Nokia, Nokia Shanghai Bell
R2-2300867	Extending NS value range	Nokia, Nokia Shanghai Bell
R2-2301467	Addition of extended NS value range	Apple Inc
R2-2301468	Addition of extended NS value range	Apple Inc
R2-2301469	Addition of extended NS value range	Apple Inc
R2-2301470	Addition of extended NS value range	Apple Inc
R2-2301471	Addition of extended NS value range	Apple Inc
R2-2301472	Addition of extended NS value range	Apple Inc
R2-2302001	LS on measurements without gap (R4-2303306; contact: Intel, CATT)	RAN4
R2-2302004	LS on the UE SRS IL imbalance issue (R4-2303519; contact: Huawei)	RAN4
R2-2302016	LS on applicability of SIB19 for NR ATG (R4-2303684; contact: Qualcomm)	RAN4
R2-2302185	Addition of extended NS value range	Apple Inc
R2-2302186	Addition of extended NS value range	Apple Inc
R2-2302209	[DRAFT] Response LS on extending the maximum range for NS values	Apple
R2-2302257	Response LS on extending the maximum range for NS values	RAN2

8.21.2: RAN1 led items

TDoc	Title	Source
R2-2300021	LS on Multi-DCI Multi-TRP with two TAs (R1-2213004; contact: Ericsson)	RAN1
R2-2300050	LS on Rel-18 UL Tx switching (R4-2220548; contact: China Telecom)	RAN4
R2-2300139	Discussion on R18 UL Tx Switching	OPPO
R2-2300338	Discussion on Multi-TRP with two TAs	SHARP Corporation
R2-2300448	discussion on UE capability and RRC configuration for UL tx switching	vivo
R2-2300555	UL Tx switching in Rel-18	Nokia, Nokia Shanghai Bell
R2-2300742	Discussion on UL Tx switching	Apple
R2-2300825	Discussion on Rel-18 UL Tx Switching Capability and Configuration	CATT
R2-2300907	On incoming LS “LS on Multi-DCI Multi-TRP with two Tas” on Rel-18 MIMO	Ericsson
R2-2301035	Considerations on multi-DCI multi-TRP operation with two TAs	Fujitsu
R2-2301180	RAN2 signalling design for Rel-18 UL Tx switching enhancements	Huawei, HiSilicon
R2-2301181	Introduction of Rel-18 UL Tx switching enhancements	Huawei, HiSilicon, NTT DOCOMO INC.
R2-2301182	Introduction of Rel-18 UL Tx switching enhancements	Huawei, HiSilicon, NTT DOCOMO INC.
R2-2301291	On multi-DCI multi-TRP with two Tas	Nokia, Nokia Shanghai Bell
R2-2301320	Discussion on Rel-18 UL Tx switching capability and configuration	ZTE Corporation, Sanechips
R2-2301321	Running 38.306 CR for R18 DSS	ZTE Corporation, Ericsson
R2-2301402	On RAN2 aspects for UL TX switching Rel-18	Ericsson
R2-2301405	Running 38.331 CR for R18 DSS	Ericsson, ZTE Corporation
R2-2301759	Issues on Rel-18 UL Tx switching that should be discussed in RAN2#121	NTT DOCOMO INC.
R2-2301760	Potential RAN2 Issues on Rel-18 UL Tx switching	NTT DOCOMO INC.
R2-2301791	Considerations on LS from RAN1 for MIMO Evolution	ZTE Corporation,Sanechips
R2-2302003	LS on Rel-18 Multi-carrier enhancement for NR (R4-2303507; contact: China Telecom)	RAN4

8.21.3: Other

TDoc	Title	Source
R2-2300004	Reply LS on the progress and open issues for NPN enhancements in Rel-18 (C1-227157; contact: Qualcomm)	CT1
R2-2300027	Reply LS on RAN dependency of FS_eNS_Ph3 (R3-226083; contact: ZTE)	RAN3
R2-2300028	Reply LS on Time Synchronization Status notification towards UE(s) (R3-226774; contact: ZTE)	RAN3
R2-2300063	Reply LS on Progress and open issues for NPN enhancements in Rel-18 (S1-223540; contact: Qualcomm)	SA1
R2-2300065	Progress and open issues for NPN enhancements in Rel-18 (S2-2209860; contact: Ericsson)	SA2
R2-2300073	LS Reply on UL scenario of reactive RAN feedback for burst sending time adjustment (S2-2301420; contact: Huawei)	SA2
R2-2300074	LS on RAN impact for NPN enhancement in Rel-18 (S2-2301437; contact: Ericsson)	SA2
R2-2300075	Proposed method for Time Synchronization status reporting to UE(s) (S2-2301463; contact: Nokia)	SA2
R2-2300077	LS on Support of Network Slices which have Area of Service not matching deployed Tracking Areas (S2-2301466; contact: Nokia)	SA2
R2-2300078	LS on Partially allowed/rejected NSSAI (S2-2301467; contact: Ericsson)	SA2
R2-2300083	Reply LS on Progress and open issues for NPN enhancements in Rel-18 (S3-224175; contact: Qualcomm)	SA3
R2-2300090	LS on handover failures related to MRO for inter-system mobility (S5-227042; Contact: Nokia)	SA5
R2-2300233	Discussion on RAN impact for NPN enhancement in Rel-18	Huawei, HiSilicon
R2-2300483	Discussion on RAN solution to provide UL reactive feedback for burst sending time adjustment	Huawei, HiSilicon
R2-2300484	Discussion on Time Synchronization Status reporting to UE(s)	Huawei, HiSilicon
R2-2300545	Discussion of RAN2 response to SA2 LS Proposed method for Time Synchronization status reporting to UE(s)	Qualcomm Incorporated
R2-2300613	RAN2 impact on Rel-18 NPN enhancement	Intel Corporation
R2-2301071	[DRAFT] Reply LS on proposed method for Time Synchronization status reporting to UE(s)	ZTE Corporation, Sanechips
R2-2301073	draft Reply LS to Support of Network Slices which have Area of Service not matching deployed Tracking Areas	Lenovo
R2-2301443	Discussion on NPN Rel-18 work	Ericsson
R2-2301444	(draft) LS on how to proceed with specification work on eNPN in Rel-18	Ericsson
R2-2301512	LS reply to SA2 on feasibility of Time Synchronization Method	Ericsson
R2-2301518	Discussion on timing synchronization status reporting to UE(s)	Nokia, Nokia Shanghai Bell
R2-2301519	[DRAFT] Reply LS on Proposed method for Time Synchronization status reporting to UE(s)	Nokia, Nokia Shanghai Bell
R2-2301836	On reactive RAN feedback for burst sending time adjustment	Ericsson
R2-2301912	Reply LS on Progress and open issues for NPN enhancements in Rel-18 (S1-223540; contact: Qualcomm)	SA1
R2-2301936	Reply LS on Progress and open issues for NPN enhancements in Rel-18 (S2-2303688; contact: Qualcomm)	SA2
R2-2302060	Reply LS on proposed method for time synchronization status reporting to UE(s) (R3-230811; contact: Nokia)	RAN3
R2-2302061	Reply LS on RAN impact for NPN enhancement in Rel-18 (R3-230813; contact: Qualcomm)	RAN3
R2-2302062	Reply LS on Support of network slices which have area of service not matching deployed tracking areas (R3-230899; contact: Nokia)	RAN3
R2-2302063	Reply LS on Partially allowed/rejected NSSAI (R3-230923; Contact: Ericsson)	RAN3
R2-2302106	Reply LS on Proposed method for Time Synchronization status reporting to UE(s)	RAN2
R2-2302178	Reply LS on Progress and open issues for NPN enhancements in Rel-18 (S2-2303689; contact: Qualcomm)	SA2

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

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

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

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

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

TDoc	Title	Source
R2-2301903	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-2301904	Report from session on positioning and sidelink relay	Session chair (MediaTek)

9.5: Session on LTE V2X and NR SL

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

9.6: Session on SON/MDT

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

9.7: Session on MBS

TDoc	Title	Source
R2-2301907	Report from MBS breakout session	Session chair (Huaweil)

9.8: Session on IDC

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

9.9: Session on NC Repeater

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

9.10: Session on eRedCap

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