RAN2#117-e

2.1: Approval of the agenda

TDoc	Title	Source
R2-2202101	Agenda for RAN2#117-e	Chairman

2.2: Approval of the report of the previous meeting

TDoc	Title	Source
R2-2202102	RAN2#116bis-e Meeting Report	MCC

2.4: Others

TDoc	Title	Source
R2-2202103	RAN2 Handbook 02-22	MCC
R2-2204151	Removal of ETWS/CMAS restriction in SNPN	R3 (Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell)
R2-2204152	Inter-MN RRC Resume without SN change [InterMNResume]	R3 (Ericsson, Qualcomm Incorporated, Huawei, Intel Corporation, China Telecom, T-Mobile USA, ZTE, Nokia, Nokia Shanghai Bell, Samsung, RadiSys, Reliance JIO, Google Inc.)
R2-2204153	Immediate MDT configurations for UE in inactive	R3 (Ericsson)
R2-2204154	On UE security capability to address SA3 request [UE_Sec_Caps]	R3 (Huawei, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, ZTE)
R2-2204155	Introduction of Local NG-RAN Node IDs for RRC_INACTIVE [RRCInactive]	R3 (Ericsson, ZTE, Radisys, Reliance JIO, China Telecom, Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom)
R2-2204156	UE Security Capabilities signaling in E-UTRAN [UE_Sec_Caps]	R3 (Ericsson, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, ZTE)
R2-2204157	UE Security Capabilities signaling in NG-RAN [UE_Sec_Caps]	R3 (Ericsson, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, ZTE)
R2-2204158	CR on data forwarding between EN-DC/MR-DC and SA handover	R3 (CMCC, CATT,Qualcomm)
R2-2204159	Support of CHO with SCG configuration[CHOwithDCkept]	R3 (Huawei, China Telecom, China Unicom, CATT, Intel Corporation, Google Inc.)
R2-2204161	SCG BL CR to TS 37.340	R3 (ZTE)
R2-2204162	Support for Enhanced Non Public Networks	R3 (Nokia, Nokia Shanghai Bell, China Telecom)
R2-2204163	BLCR to 37.320: Support of MDT enhancement	R3 (Nokia, Nokia Shanghai Bell)
R2-2204164	CR TS 38.300 on RAN3-related topics of Rel-17 IAB	R3 (Qualcomm)
R2-2204165	Enhancement of RAN Slicing	R3 (CATT,ZTE, Huawei, Nokia, Nokia Shanghai Bell,Samsung,Ericsson)
R2-2204166	Introduction of MultiSIM Support for TS 38.300	R3 (Radisys, Reliance JIO, Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE)
R2-2204167	NB-IoT/eMTC support for Non-Terrestrial Networks	R3 (ZTE, CATT, Samsung, MediaTek, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated)
R2-2204168	CPAC BL CR to TS 37.340	R3 (Huawei, Nokia, Nokia Shanghai Bell, ZTE)
R2-2204169	BLCR to 36.300_Addition of SON features enhancement	R3 (Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, CMCC, Ericsson)
R2-2204170	Addition of SON features enhancement	R3 (Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, CMCC)
R2-2204171	Addition of SON features enhancement	R3 (CMCC, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung, ZTE, CATT, Lenovo)
R2-2204172	Introduction of NR MBS	R3 (Nokia, Nokia Shanghai Bell, Ericsson, CATT)
R2-2204173	Support Non-Terrestrial Networks	R3 (Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell)
R2-2204174	38.300 BL CR for Introduction of QoE measurements in NR	R3 (China Unicom, Ericsson, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Samsung, CATT)
R2-2204175	RedCap UEs impacts to NG-RAN	R3 (Ericsson, Nokia, Nokia Shanghai Bell, Samsung, CATT, Qualcomm Inc., ZTE, Radisys, Reliance JIO)
R2-2204176	Support of Enhanced RAN Slicing	R3 (Nokia, Nokia Shanghai Bell, ZTE, CATT)
R2-2204177	RA-SDT BLCR to TS 38.300	R3 (ZTE, China Telecommunication, Ericsson, CATT, Nokia, Nokia Shanghai Bell)
R2-2204178	Addition of PEI Paging Subgrouping Assistance Information	R3 (Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT)
R2-2204212	On UE security capability to address SA3 request [UE_Sec_Caps]	R3 (Huawei, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, ZTE)
R2-2204213	UE Security Capabilities signaling in E-UTRAN [UE_Sec_Caps]	R3 (Ericsson, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, ZTE)
R2-2204214	UE Security Capabilities signaling in NG-RAN [UE_Sec_Caps]	R3 (Ericsson, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, ZTE)
R2-2204258	CR on data forwarding between EN-DC/MR-DC and SA handover	R3 (CMCC, CATT, Qualcomm)

3: Incoming liaisons

TDoc	Title	Source
R2-2202181	Reply LS on energy efficiency as guiding principle for new solutions (S5-221501; contact: Orange)	SA5
R2-2203718	LS response to 3GPP RAN on Location Services for Drones (LI(21)P59034r1; contact: ETSI TC LI)	ETSI TC LI
R2-2203930	LS on RAN feedback for low latency (S2-2201767; contact: Huawei)	SA2
R2-2203931	LS on QoS support with PDU Set granularity (S2-2201803; contact: Intel)	SA2
R2-2204066	LS on the SDU type used over user plane for NR PC5 reference point (C1-221835; contact: ZTE)	CT1
R2-2204101	LS On Canada band n77 (R4-2206568; contact: Telus)	RAN4

4.1: NB-IoT corrections Rel-15 and earlier

TDoc	Title	Source
R2-2203214	Correction to DRX active time after a Scheduling Request or a SPS BSR has been sent in NB-IoT	Huawei, HiSilicon
R2-2203215	Correction to DRX active time after a Scheduling Request or a SPS BSR has been sent in NB-IoT	Huawei, HiSilicon
R2-2203480	Discussion on enabling 2 HARQ processes and HARQ RTT timer in NB-IoT	Ericsson
R2-2203486	Clarification on CDRX and two HARQ interaction for NB-IoT	Ericsson
R2-2203495	Clarification on CDRX and two HARQ interaction for NB-IoT	Ericsson
R2-2203496	Clarification on CDRX and two HARQ interaction for NB-IoT	Ericsson
R2-2203572	Report for [AT117-e][305][NBIOT R15] 2 HARQ processes and HARQ RTT timer	Ericsson (Rapporteur)

4.5: Other LTE corrections Rel-15 and earlier

TDoc	Title	Source
R2-2202218	Dummify empty sequence in FlightPathInfoReport-r15 and other corrections	Lenovo, Motorola Mobility
R2-2202219	Dummify empty sequence in FlightPathInfoReport-r15 and other corrections	Lenovo, Motorola Mobility
R2-2203238	Discussion on handling QoE configuration in full configuration	Google Inc.
R2-2203295	Clarification of RSRP measurement triggering for number of cells for UAVs	Ericsson
R2-2203297	Clarification of RSRP measurement triggering for number of cells for UAVs	Ericsson
R2-2203631	Report from email discussion [AT117-e][202][LTE] Miscellaneous LTE CRs (Lenovo)	Lenovo
R2-2203656	Dummify empty sequence in FlightPathInfoReport-r15 and other corrections	Lenovo, Motorola Mobility
R2-2203657	Dummify empty sequence in FlightPathInfoReport-r15 and other corrections	Lenovo, Motorola Mobility
R2-2203658	Clarification of RSRP measurement triggering for number of cells for UAVs	Ericsson, Samsung, Qualcomm
R2-2203659	Clarification of RSRP measurement triggering for number of cells for UAVs	Ericsson, Samsung, Qualcomm
R2-2203661	Correction to application layer measurement and reporting	Google Inc.
R2-2203662	Correction to application layer measurement and reporting	Google Inc.
R2-2203669	Correction to application layer measurement and reporting	Google Inc.
R2-2203670	Correction to application layer measurement and reporting	Google Inc.

5.1: Organisational

TDoc	Title	Source
R2-2204073	Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 (R1-2202769; contact: Huawei)	RAN1
R2-2204144	Reply LS to RAN2 on L3 filter configuration (R4-2207041; contact: Apple)	RAN4
R2-2204195	Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 (R4-2206567; contact: Huawei)	RAN4

5.3: User Plane corrections

TDoc	Title	Source
R2-2204007	Report of [AT117-e][025][NR15] User-plane Corrections	Huawei, HiSilicon

5.3.1: MAC

TDoc	Title	Source
R2-2202109	Reply LS on initial state of elements controlled by MAC CEs (R1-2112860	RAN1
R2-2202552	Clarification on the DRX RTT Timer operation with UL skipping configuration	Apple
R2-2202553	Clarification on the DRX RTT Timer operation with UL skipping configuration	Apple
R2-2203129	Clarification on the initial state of elements controlled by MAC CE (based on LS R1-2112860, Contact: Huawei)	Huawei, HiSilicon
R2-2203130	Clarification on the initial state of elements controlled by MAC CE (based on LS R1-2112860, Contact: Huawei)	Huawei, HiSilicon
R2-2203239	Discussion on An Abnormal Case for Retransmission	ZTE Corporation,OPPO, Sanechips
R2-2203240	Correction to 38.321 on the term of the handover in handling of MAC CE	ZTE Corporation,Sanechips
R2-2203241	Correction to 38.321 on the term of the handover in handling of MAC CE	ZTE Corporation,Sanechips
R2-2203242	Discussion on Initial State of Elements Controled by MAC CEs	ZTE Corporation,Sanechips
R2-2203824	Clarification on the initial state of elements controlled by MAC CE	Huawei, HiSilicon, ZTE Corporation, vivo
R2-2203825	Clarification on the initial state of elements controlled by MAC CE and non-numerical K1 value	Huawei, HiSilicon, ZTE Corporation, vivo

5.3.2: RLC PDCP SDAP

TDoc	Title	Source
R2-2202194	Discussion on handling of discardOnPDCP	OPPO

5.4.1: NR RRC

TDoc	Title	Source
R2-2202104	LS on NAS procedure not subject to UAC (C1-217227; contact: Apple)	CT1
R2-2202106	Reply LS on RMSI reception based on non-zero search space (R1-2112765; contact:OPPO)	RAN1
R2-2202121	Reply LS on inter-MN handover without SN change (R3-216165; contact: Huawei)	RAN3
R2-2202123	Reply LS on signalling SN initiated release of SCG (R3-216236; contact: Ericsson)	RAN3
R2-2202173	LS on configuration of p-MaxEUTRA and p-NR-FR1 (R5-217995; contact: Huawei)	RAN5
R2-2202272	Clarification of search space configuration for RMSI-R15	OPPO
R2-2202273	Clarification of search space configuration for RMSI-R16	OPPO
R2-2202393	Clarification on per UE/per FR gap setup and release inconsistency	Nokia, Nokia Shanghai Bell
R2-2202535	Discussion on RRC handling of NAS triggers not subject to UAC	Apple
R2-2202536	Correction on RRC resume of NAS triggers without access category	Apple
R2-2202537	Correction on RRC resume of NAS triggers without access category	Apple
R2-2202538	[Draft] Reply LS on NAS procedure not subject to UAC	Apple
R2-2202637	Issues with use of NCC for KgNB derivation during re-establishment and Resume procedure	Intel Corporation
R2-2202638	Correction of NCC storage during re-establishment and Resume	Intel Corporation
R2-2202639	Correction of NCC storage during re-establishment and Resume	Intel Corporation
R2-2202655	Discussion on configuration of p-MaxEUTRA and p-NR-FR1	ZTE Corporation, Sanechips
R2-2202656	[Draft] Reply LS on configuration of p-MaxEUTRA and p-NR-FR1	ZTE Corporation, Sanechips
R2-2202798	Reply LS on configuration of p-MaxEUTRA and p-NR-FR1	vivo
R2-2202806	Signalling in inter-MN HO without SN change	NEC
R2-2202807	Clarification on inter-MN handover without SN change	NEC
R2-2202808	Clarification on inter-MN handover without SN change	NEC
R2-2203133	Draft reply LS on configuration of p-MaxEUTRA and p-NR-FR1	Huawei, HiSilicon
R2-2203320	Clarification on SN initiated release of an SCG	Ericsson, Nokia, Nokia Shanghai Bell
R2-2203321	Clarification on SN initiated release of an SCG	Ericsson, Nokia, Nokia Shanghai Bell
R2-2203327	Correction on Full configuration	ZTE Corporation, Sanechips
R2-2203328	Correction on Full configuration(R16)	ZTE Corporation, Sanechips
R2-2203335	On rsType to be used for beam measurements	Ericsson
R2-2203336	On rsType to be used for beam measurements	Ericsson
R2-2203487	Discussion on NAS-triggered resume procedure without UAC	Huawei, HiSilicon
R2-2203498	Clarification on servingCellMO (R15)	Huawei, HiSilicon
R2-2203499	Clarification on servingCellMO (R16)	Huawei, HiSilicon
R2-2203500	Clarification on inter-MN handover without SN change (R15)	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, Samsung
R2-2203501	Clarification on inter-MN handover without SN change (R16)	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, Samsung
R2-2203774	[AT117-e][027][NR15] RRC misc I (Ericsson)	Ericsson
R2-2203861	Summary of [AT117-e][026][NR15] NAS procedure not subject to UAC (Apple)	Apple
R2-2203936	Clarification on inter-MN handover without SN change	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, Samsung, NEC
R2-2203937	Clarification on inter-MN handover without SN change	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, Samsung, NEC
R2-2203972	Offline [AT117-e][029][NR15] RRC Inter-Node Signalling (Nokia)	Nokia (Rapporteur)
R2-2204018	Correction of NCC storage during re-establishment and Resume	Intel Corporation
R2-2204019	Report of [AT117-e][028][NR15] RRC misc II (Intel)	Intel Corporation
R2-2204200	Miscellaneous non-controversial corrections Set XIII	Ericsson

5.5: Positioning corrections

TDoc	Title	Source
R2-2202597	Corretion on the object identifier of LPP ASN.1 for R15	Huawei, HiSilicon
R2-2202598	Corretion on the object identifier of LPP ASN.1 for R16	Huawei, HiSilicon
R2-2202599	Discussion on the object identifier of LPP ASN.1	Huawei, HiSilicon
R2-2203613	Correction on the object identifier of LPP ASN.1 for R15	Huawei, HiSilicon
R2-2203614	Correction on the object identifier of LPP ASN.1 for R16	Huawei, HiSilicon
R2-2203627	Summary of [AT117-e][624][POS] Agenda Item 5.5 (Huawei)	Huawei, HiSilicon

6.1.1: Organisational

TDoc	Title	Source
R2-2203889	Reply LS on NR-U channel information and procedures (R1-2202673; contact: Samsung)	RAN1
R2-2203890	Reply LS on UE capability for supporting single DCI transmission schemes for multi-TRP (R1-2202691; contact: Apple)	RAN1
R2-2204072	Reply LS on Intra UE Prioritization Scenario (R1-2202734; contact: vivo)	RAN1
R2-2204133	LS on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR (R4-2206828; contact: Apple)	RAN4
R2-2204143	Reply LS to RAN2 on RRM relaxation in power saving (R4-2207038; contact: CATT)	RAN4
R2-2204145	ReplyLS to RAN2 on RLM/BFD relaxation for ePowSav (R4-2207087; contact: vivo)	RAN4
R2-2204146	LS on UE capability for inter-frequency measurement without MG (R4-2207090; contact: Huawei)	RAN4
R2-2204194	Reply LS on power control for NR-DC (R4-2206566; contact: OPPO & vivo)	RAN4

6.1.3: User Plane corrections

TDoc	Title	Source
R2-2204077	Report of [AT117-e][030][NR16] User-plane Related Corrections	vivo

6.1.3.1: MAC

TDoc	Title	Source
R2-2202110	Reply LS on UL skipping with LCH prioritization (R1-2112862; contact: vivo)	RAN1
R2-2202326	Correction on UL skipping with LCH Prioritization in Rel-16	vivo
R2-2202524	Procedure level alignment of UL skipping	Apple
R2-2203484	Correction to DRX operation with bundling controlled in the DCI	Ericsson, Nokia, T-Mobile USA, Verizon, Docomo
R2-2204078	Correction on UL skipping with LCH Prioritization in Rel-16	vivo

6.1.3.3: PDCP

TDoc	Title	Source
R2-2203131	Joint EHC and RoHC when Type is not present in Ethernet header	Huawei, HiSilicon

6.1.4.1: NR RRC

TDoc	Title	Source
R2-2204201	Miscellaneous non-controversial corrections Set XIII	Ericsson

6.1.4.1.1: Connection control

TDoc	Title	Source
R2-2202222	Addition of missing description on mobility support for 5G SRVCC to 3G	Lenovo, Motorola Mobility
R2-2202228	Handling of ServingCellConfigCommon	Qualcomm Incorporated
R2-2202232	Correction to the reference of DCI format 2_6 field descriptions	ROHDE & SCHWARZ
R2-2202835	Correction on conditional reconfiguraiton execution for only one triggered cell	Xiaomi, Samsung, NEC, Nokia, Nokia Shanghai Bell, LG Electronics, CATT, OPPO, Ericsson
R2-2202836	Correction on conditional reconfiguraiton execution for only one triggered cell	Xiaomi, Samsung, NEC, Nokia, Nokia Shanghai Bell, LG Electronics, CATT, OPPO, Ericsson
R2-2202872	Conditional configuration handling upon going to RRC_IDLE	Lenovo, Motorola Mobility, Sharp
R2-2202876	Conditional configuration handling upon going to RRC_IDLE	Lenovo, Motorola Mobility, Sharp
R2-2202915	Correction on inclusion of selectedPLMN-Identity in RRCResumeComplete	MediaTek Inc.
R2-2203132	Correction on invalid symbol pattern	Huawei, HiSilicon
R2-2203255	Correction to RRC reconfiguration for IAB	Google Inc.
R2-2203267	Clarification on meaning of dual PA in DC location reporting	Nokia, Nokia Shanghai Bell
R2-2203407	NS_55 in NR CA	Ericsson
R2-2203408	Non-comprehended fields in ServingCellConfigCommon	Ericsson
R2-2203410	Clarification of commonSearchSpaceList	Ericsson
R2-2203438	Miscellaneous aspects on UAI	Ericsson
R2-2203477	Clarification on highSpeedConfig for HST	Huawei, HiSilicon, CMCC
R2-2203706	NS_55 in NR CA	Ericsson
R2-2203816	[AT117-e][031][NR16] Connection Control I (Ericsson)	Ericsson
R2-2203826	Correction on invalid symbol pattern	Huawei, HiSilicon
R2-2203827	Clarification on highSpeedConfig for HST	Huawei, HiSilicon, CMCC
R2-2203906	Addition of missing description on mobility support for 5G SRVCC to 3G	Lenovo, Motorola Mobility
R2-2203909	Report of [AT117-e][032][NR1615] Connection Control II (Lenovo)	Lenovo
R2-2204008	Handling of ServingCellConfigCommon	Qualcomm Incorporated
R2-2204057	Clarification on HighSpeedConfig for HST	Huawei, HiSilicon, CMCC
R2-2204060	[AT117-e][031][NR16] Connection Control I (Ericsson)	Ericsson
R2-2204061	Correction on delta configuration for UAI overheating in EN-DC	Ericsson
R2-2204125	Correction on inclusion of selectedPLMN-Identity in RRCResumeComplete	MediaTek Inc.
R2-2204185	Response LS on Conditional Handover with SCG configuration scenarios (R3-222840; contact: Nokia)	RAN3

6.1.4.1.2: RRM and Measurements

TDoc	Title	Source
R2-2202917	Clarification on target band filter in NeedForGap configuration	MediaTek Inc.

6.1.4.1.5: Other

TDoc	Title	Source
R2-2202296	Discussion on RRC message segmentation	Samsung
R2-2202297	Correction to RRC message segmentation	Samsung
R2-2202298	Correction to RRC message segmentation	Samsung
R2-2202763	Discussion on parallel transmission of segmented RRC messages	Lenovo, Motorola Mobility
R2-2202990	Correction on UL message segmentation	Samsung
R2-2202991	Correction on UL message segmentation	Samsung
R2-2203439	UL RRC segmentation capability	Ericsson
R2-2203441	Correction on Non-numerical K1 Value	vivo
R2-2203442	Correction on Non-numerical K1 Value	vivo
R2-2203882	Report of [AT117-e][033][NR1615] RRC Other (Samsung)	Samsung

6.1.4.3: UE capabilities

TDoc	Title	Source
R2-2202107	LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#107-e (R1-2112778; contact: NTT DOCOMO)	RAN1
R2-2202108	Reply LS on PDCCH Blind Detection in CA (R1-2112833; contact: Huawei)	RAN1
R2-2202146	LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2118536; contact: CMCC)	RAN4
R2-2202195	Left issues on DAPS capability	OPPO
R2-2202229	Discussion on BWP operation without bandwidth restriction	Qualcomm Incorporated, ZTE Corporation
R2-2202293	Correction on DAPS capability	OPPO
R2-2202525	Support of DC combination without CA	Apple
R2-2202526	Support of DC combination without CA	Apple
R2-2202527	Support of Multi-DCI based multi-TRP PUSCH operation	Apple
R2-2202528	Support of Multi-DCI based multi-TRP PUSCH operation	Apple
R2-2202665	Miscellaneous updates on TR38.822	Intel Corporation
R2-2202810	Adding UE capability of UL MIMO coherence for UL Tx switching	Huawei, HiSilicon, China Telecom, Apple
R2-2202811	Adding UE capability of UL MIMO coherence for UL Tx switching	Huawei, HiSilicon, China Telecom, Apple
R2-2203163	Rename of field extendedBand-n77	Samsung R&D Institute UK
R2-2203167	Rename of field extendedBand-n77	Samsung R&D Institute UK
R2-2203268	UE capabilities for UL full power modes	Nokia, Nokia Shanghai Bell
R2-2203409	BCS for non-CA band combination	Ericsson
R2-2203488	Discussion on DAPS capabilities and configuration	Huawei, HiSilicon
R2-2203489	Discussion on PDCCH Blind Detection in CA	Huawei, HiSilicon
R2-2203490	Correction on PDCCH Blind Detection in CA	Huawei, HiSilicon
R2-2203491	Correction on PDCCH Blind Detection in CA	Huawei, HiSilicon
R2-2203492	Correction on ssb-csirs-SINR-measurement-r16 capability	Huawei, HiSilicon
R2-2203510	Discussion on PDCCH Blind Detection in CA	Huawei, HiSilicon
R2-2203738	LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#108-e (R1-2202764; contact: NTT DOCOMO)	RAN1
R2-2203875	Correction on DAPS capability	OPPO, Huawei, HiSilicon
R2-2203959	Miscellaneous updates on TR38.822	Intel Corporation
R2-2203984	Adding UE capability of UL MIMO coherence for UL Tx switching	Huawei, HiSilicon, China Telecom, Apple
R2-2203985	Adding UE capability of UL MIMO coherence for UL Tx switching	Huawei, HiSilicon, China Telecom, Apple
R2-2204009	LS on BWP operation without bandwidth restriction	RAN2
R2-2204020	Summary report of [AT117-e][034][NR16] UE capabilities I (Intel)	Intel Corporation
R2-2204053	Summary of [AT117-e][035][NR1615] UE capabilities II	Huawei, HiSilicon
R2-2204054	Correction on ssb-csirs-SINR-measurement-r16 capability	Huawei, HiSilicon
R2-2204055	Reply LS on PDCCH Blind Detection in CA	RAN2

6.1.4.4: Idle/inactive mode procedures

TDoc	Title	Source
R2-2202220	Addition of missing description on handling of Access Identities when cell is reserved for operator use	Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Ericsson
R2-2202221	Addition of missing description on handling of Access Identities when cell is reserved for operator use	Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Ericsson
R2-2202539	Correction for cell reselection on CAG cells in white list	Apple
R2-2203815	Report from email discussion [AT117-e][036][NR1516] Idle Inactive procedures (Lenovo)	Lenovo

6.2.1: General and Stage-2 corrections

TDoc	Title	Source
R2-2202147	LS on Signalling of PC2 V2X intra-band concurrent operation (R4-2119992; contact: Xiaomi)	RAN4
R2-2202148	LS on PEMAX for NR-V2X (R4-2120047; contact: Huawei, CATT)	RAN4
R2-2202196	Discussion on RAN4 LS on power class capability (R4-2119992)	OPPO
R2-2202197	Introduction of NR V2X power class	OPPO
R2-2202198	Introduction of NR V2X power class	OPPO
R2-2202199	Discussion on RAN4 LS on P_EMAX (R4-2120047)	OPPO
R2-2202470	Draft reply LS on PEMAX for NR-V2X	Qualcomm Finland RFFE Oy
R2-2202715	Draft reply LS on Pemax for NR-V2X	Huawei, HiSilicon, CATT
R2-2202837	Draft Reply LS on new power class capability for NR-V2X	Xiaomi
R2-2202838	Introduction of sidelink power class capability	Xiaomi, Ericsson
R2-2202839	Introduction of sidelink power class capability	Xiaomi, Ericsson
R2-2203146	Discussion on RAN4 LS on new power class capability for NR-V2X	Xiaomi
R2-2203173	Draft reply LS on PEMAX for NR-V2X	vivo
R2-2203174	Clarification on SL power control parameter	vivo
R2-2203175	PEMAX for NR-V2X	vivo
R2-2203684	Introduction of sidelink power class capability	Xiaomi, Ericsson
R2-2203686	Reply LS on Signalling of PC2 V2X intra-band concurrent operation	RAN2
R2-2203687	Reply LS on Pemax for NR-V2X	RAN2
R2-2203694	Introduction of sidelink power class capability indication	Xiaomi, Ericsson
R2-2204074	Reply LS to RAN4 on PEMAX for NR-V2X (R1-2202816; contact: Huawei)	RAN1
R2-2204223	Introduction of sidelink power class capability indication	Xiaomi

6.2.2: Control plane corrections

TDoc	Title	Source
R2-2202714	Miscelleneous CR on 38.331	Huawei, HiSilicon
R2-2202723	Summary of RRC corrections	Huawei, HiSilicon
R2-2203286	Correction on HARQ attribute of SL SRB option1	ZTE Corporation, Sanechips, OPPO
R2-2203287	Correction on HARQ attribute of SL SRB option2b	ZTE Corporation, Sanechips,vivo
R2-2203288	Correction on HARQ attribute of SL SRB option2a	ZTE Corporation, Sanechips
R2-2203289	Corrections on TS 38.304	ZTE Corporation, Sanechips
R2-2203290	Discussion on HARQ attribute of SL SRB	ZTE Corporation, Sanechips,vivo
R2-2203680	Miscellaneous corrections on TS 38.331	Huawei, HiSilicon, ZTE Corporation, Sanechips, vivo
R2-2203681	Summary [AT117-e][707][V2X/SL] Control plane corrections (Huawei)	Huawei, HiSilicon

6.2.3: User plane corrections

TDoc	Title	Source
R2-2202193	Correction on UL-SL prioritization_option1	OPPO
R2-2202211	Clarification on SDU type field usage for SL-SRB	Samsung, Apple
R2-2202299	Correction on UL-SL prioritization_option2	OPPO
R2-2202360	Corrections on the Unexpected SL-BSR Trigger for SL-CSI MAC CE	CATT
R2-2202361	Summary [POST116-e][710][V2X/SL] PDCP/RLC Entity Maintenance for SL-SRBs (CATT)	CATT
R2-2202362	Corrections on MAC filtering issue for the first unicast PC5-S signalling	CATT
R2-2202363	Corrections on RLC entity establishment issue for the first unicast PC5-S signalling	CATT
R2-2202364	Corrections on PDCP entity establishment issue for the first unicast PC5-S signalling	CATT
R2-2202534	Correction on the PDB derivation from LCH priority	Apple, OPPO
R2-2202716	Clarification on the UL and NR SL prioritization	Huawei, HiSilicon, Lenovo, Motorola Mobility
R2-2202843	Correction on SL HARQ feedback indicator	ASUSTeK
R2-2202947	Rapporteur CR on 38.321	LG Electronics France (Rapporteur)
R2-2202949	Correction of RV indication	Samsung
R2-2202956	Summary of MAC corrections	LG Electronics France
R2-2203451	Correction on NACK reporting on PUCCH for NR SL	Huawei, HiSilicon, OPPO
R2-2203479	Correction on NACK reporting on PUCCH for NR SL	Huawei, HiSilicon, OPPO
R2-2203682	Rapporteur CR on 38.321	LG Electronics France (Rapporteur)
R2-2203683	Summary of [AT117-e][708][V2X/SL] User plane corrections (LG)	LG Electronics Inc. (Rapporteur)
R2-2203691	LS on how to receive the first PC5-S unicast message during PC5-S connection setup procedure	RAN2
R2-2203692	Correction on UL/SL prioritization	OPPO
R2-2203979	Correction on NACK reporting on PUCCH for NR SL	Huawei, HiSilicon, OPPO
R2-2204013	Correction on SL HARQ feedback indicator	ASUSTeK

6.3.1: General and Stage 2 corrections

TDoc	Title	Source
R2-2202119	Reply LS to RAN2 on the misalignment in SRS configuration (R3-216009; contact: Samsung)	RAN3
R2-2202406	Miscellaneous corrections in TS 38.305	CATT

6.3.2: RRC corrections

TDoc	Title	Source
R2-2202407	Corrections on the description of maxNrofSRS-PosResources-1-r16	CATT
R2-2202596	Correction on srs-PosResourceIdList in RRC	Huawei, HiSilicon
R2-2204027	Correction on Positioning SRS	Huawei, CATT, HiSilicon
R2-2204085	Report of [AT117-e][625][POS] Agenda item 6.3.2 (CATT	CATT

6.3.3: LPP corrections

TDoc	Title	Source
R2-2202224	Addition of missing need code for the BDS TGD2 parameter	Lenovo, Motorola Mobility
R2-2203275	Correction of reference TRP for DL-AoD and Multi-RTT measurement report	Qualcomm Incorporated
R2-2203277	Correction to NR-DL-PRS-ResourcesCapability field description	Qualcomm Incorporated
R2-2203367	Introducing new high accuracy GAD shape with scalable uncertainty	Ericsson, T-Mobile USA
R2-2203368	Clarification on LPP segmentation	Ericsson
R2-2203531	Introducing new high accuracy GAD shape with scalable uncertainty	Ericsson, T-Mobile USA, Qualcomm Incorporated
R2-2204021	Report for LPP Corrections for Positioning	Ericsson

6.4.1: General and stage-2 corrections

TDoc	Title	Source
R2-2202223	Corrections to SON/MDT capabilities	Lenovo, Motorola Mobility

6.4.2: TS 38.314 corrections

TDoc	Title	Source
R2-2202707	Correction to R16 38.314 on PRB Usage for MIMO	CMCC

6.4.3: RRC corrections

TDoc	Title	Source
R2-2202502	Addition of missing information into RA-InformationCommon-r16	Apple, Ericsson
R2-2202737	Correction on LTE UE RLF Report	China Telecom, CATT, Ericsson
R2-2202783	Corrections on LTE UE RLF Report	China Telecom, CATT, Ericsson
R2-2203330	On DAPS handover failure handling	Ericsson
R2-2203332	On including SSB and CSI-RS measurements in RLF report	Ericsson
R2-2203333	On ObtainCommonLocation related configuration	Ericsson
R2-2203334	On sensor information configuration	Ericsson

7.2: Additional MTC enhancements for LTE

TDoc	Title	Source
R2-2203571	Report of [AT117-e][304][NBIOT R15] DRX active time after Scheduling Request or SPS BSR (Huawei))	Huawei

7.3: Additional enhancements for NB-IoT

TDoc	Title	Source
R2-2202633	Discussion on the issue for random access on multicarrier for NB-IoT	CMCC
R2-2202634	Solution for random access issue on multiCarrier in NB-IoT	CMCC
R2-2202635	Solution for random access issue on multiCarrier in NB-IoT	CMCC
R2-2203573	Offline discussion on the issue for Random Access on multicarrier for NB-IoT	CMCC
R2-2203574	Report on [AT117-e][312][NBIOT R16] PUR Response Window (Qualcomm)	Qualcomm Inc. (rapporteur)
R2-2203584	Introduction of carrier specific NRSRP thresholds for NPRACH resource selection	CMCC, ZTE Corporation, Huawei
R2-2203585	Introduction of carrier specific NRSRP thresholds for NPRACH resource selection	CMCC, ZTE Corporation, Huawei
R2-2203586	Introduction of carrier specific NRSRP thresholds for NPRACH resource selection	CMCC, ZTE Corporation, Huawei
R2-2203723	Correction to pur-ResponseWindowTimer and removal of pur-ResponseWindowSize	Qualcomm Incorporated, Huawei, HiSilicon
R2-2203724	Correction to pur-ResponseWindowTimer and removal of pur-ResponseWindowSize	Qualcomm Incorporated, Huawei, HiSilicon
R2-2203855	Solution for random access issue on multiCarrier in NB-IoT	CMCC
R2-2203856	Solution for random access issue on multiCarrier in NB-IoT	CMCC
R2-2203857	Solution for random access issue on multiCarrier in NB-IoT	CMCC
R2-2203858	Report of phase 2 discussion for [AT117-e][306][NBIOT R16] Random access on multiCarrier in NB-IoT (CMCC)	CMCC

7.4: LTE Other WIs

TDoc	Title	Source
R2-2202122	Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems (R3-216196; contact: Nokia)	RAN3
R2-2202929	Minor changes collected by Rapporteur	Samsung
R2-2203660	Minor changes collected by Rapporteur	Samsung

8.0.1: RRC

TDoc	Title	Source
R2-2202111	LS on updated Rel-17 NR higher-layers parameter list (R1-2200700; contact: Ericsson)	RAN1
R2-2202600	Considerations on the organization of R17 ASN.1 review	Huawei, HiSilicon
R2-2203417	Rel-17 ASN.1 review plan	Ericsson
R2-2203737	LS on updated Rel-17 LTE and NR higher-layers parameter list (R1-2202760; contact: Ericsson)	RAN1
R2-2203817	[AT117-e][037][R17] ASN.1 review (Ericsson)	Ericsson
R2-2203883	LS on updated Rel-17 LTE and NR higher-layers parameter list (R1-2202542; contact: Ericsson)	RAN1

8.0.2: UE capabilities

TDoc	Title	Source
R2-2202113	LS on updated Rel-17 RAN1 UE features list for NR (R1-2200781; contact: NTT DOCOMO)	RAN1
R2-2202154	LS on Rel-17 RAN4 UE feature list for NR (R4-2202401; contact: CMCC)	RAN4
R2-2202657	Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306)	Intel Corporation
R2-2202658	Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331)	Intel Corporation
R2-2202662	Rel-17 UE capability handling	Intel Corporation
R2-2202663	Draft Reply LS to Rel-17 RAN1 and RAN4 feature list	Intel Corporation
R2-2203730	Reply LS to Rel-17 RAN1 and RAN4 feature list	RAN2
R2-2203746	LS on updated Rel-17 RAN1 UE features list for NR (R1-2202927; contact: NTT DOCOMO)	RAN1
R2-2203862	Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306)	Intel Corporation
R2-2203863	Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331)	Intel Corporation
R2-2203877	LS on Rel-17 RAN4 UE feature list for NR (R4-2206282; contact: CMCC)	RAN4
R2-2204132	LS on Rel-17 RAN4 UE feature list for NR (R4-2206572; contact: CMCC)	RAN4

8.0.3: Gaps Coordination

TDoc	Title	Source
R2-2202209	Consideration for Gaps Coordination	OPPO
R2-2202321	Discussion on Gap coordination	vivo
R2-2202864	Discussion on gap coordination	MediaTek Inc.
R2-2202888	Discussion on gaps coordination	Huawei, HiSilicon
R2-2202943	Discussion on gaps coordination	Samsung Electronics Co., Ltd
R2-2202985	Consideration on gaps coordination	ZTE Corporation, Sanechips
R2-2203446	Gaps coordination	Ericsson
R2-2203878	Report of [AT117-e][039][NR17] Gaps Coordination (MediaTek)	MediaTek Inc.
R2-2203879	LS on coordination of R17 gap features	RAN2

8.0.4: Other

TDoc	Title	Source
R2-2203285	LCID configuration for MAC CEs	Nokia, Nokia Shanghai Bell
R2-2203317	Cross WI coordination on MAC CEs and LCIDs	Huawei, HiSilicon

8.1.1.1: Organizational

TDoc	Title	Source
R2-2203316	Open issue list for NR MBS	Huawei, HiSilicon

8.1.1.2: LS in

TDoc	Title	Source
R2-2202114	LS reply to MBS broadcast reception on SCell and non-serving cell (R1-2200798; contact: Huawei)	RAN1
R2-2202130	LS on MBS Service Area Identity and start procedure for broadcast service (R3-221302; contact: CATT)	RAN3
R2-2202141	LS on NR RRC to support split NR-RAN architecture for NR MBS (R3-221469; contact: Ericsson)	RAN3
R2-2202142	Reply LS on paging for multicast session activation notification (R3-221470; contact: Samsung)	RAN3
R2-2203727	Reply LS on MBS Service Area Identity and start procedure for broadcast service (S2-2201517; contact: CATT)	SA2
R2-2203772	Reply LS on maximum number of MBS sessions that can be associated to a PDU session (S6-220262; contact: Ericsson)	SA6
R2-2203776	[AT117-e][040][MBS] Reply LS on max no of MBS sessions that can be associated to a PDU session (Ericsson)	Ericsson
R2-2203777	Draft Reply LS on maximum number of MBS sessions that can be associated to a PDU session	Ericsson
R2-2203884	Reply LS on MBS SPS (R1-2202591; contact: CMCC)	RAN1
R2-2203886	LS reply about the MBS issues (R1-2202611; contact: Huawei)	RAN1
R2-2203902	Reply LS on the Length of MBS Service Area Identity	RAN2
R2-2203994	Reply LS on NR RRC to support split NR-RAN architecture for NR MBS	Nokia
R2-2204043	LS reply on MBS broadcast reception on Scell (R1-2202822; contact: Huawei)	RAN1
R2-2204082	Reply LS on Multicast paging with TMGI (S3-220537; contact: Huawei)	SA3
R2-2204088	Reply LS on NR RRC to support split NR-RAN architecture for NR MBS	RAN2
R2-2204107	Reply LS on maximum number of MBS sessions that can be associated to a PDU session	RAN2
R2-2204188	LS on further outstanding issues in TS 23.247 (R3-222867; contact: Ericsson)	RAN3

8.1.1.3: CRs and Rapporteur Resolutions

TDoc	Title	Source
R2-2202245	Introduction of NR MBS in 38.321	OPPO
R2-2202246	Resolution proposals to Rapporteur Handled Open Issues in MAC CR	OPPO
R2-2202271	38_304_Running_CR_for_MBS_in_NR	CATT
R2-2202277	38.322 Running CR for NR MBS	vivo, Huawei, HiSilicon
R2-2202300	Introduction of NR MBS	Samsung
R2-2202385	Resolution to Rapporteur Handled Open Issues in 38.304 CR	CATT
R2-2202727	38.300 Running CR for MBS in NR	CMCC
R2-2202786	Draft 306 CR for MBS UE capabilities	MediaTek Inc.
R2-2202787	Draft 331 CR for MBS UE capabilities	MediaTek Inc.
R2-2203149	Correction on MBS DRX due to PTP for PTM retransmission	OPPO
R2-2203341	Introduction of NR MBS into TS 38.331	Huawei, HiSilicon
R2-2203342	Rapporteur handled issues for RRC CR of NR MBS	Huawei, HiSilicon
R2-2203700	Introduction of NR MBS	Samsung
R2-2203771	38.323 running CR for NR MBS	Xiaomi Communications
R2-2203778	38.300 Running CR for MBS in NR	CMCC, Huawei
R2-2203779	Resolution to Rapporteur Handled Open Issue in 38.300 CR	CMCC
R2-2203808	Introduction of NR MBS	CMCC, Huawei
R2-2203811	38.304 running CR for NR MBS	CATT
R2-2203818	Introduction of NR MBS	OPPO
R2-2203969	Draft 306 CR for MBS UE capabilities	MediaTek Inc.
R2-2203970	Draft 331 CR for MBS UE capabilities	MediaTek Inc.
R2-2204030	Introduction of NR MBS into 38.323	Xiaomi Communications
R2-2204124	38.304 running CR for NR MBS	CATT
R2-2204235	38.304 running CR for NR MBS	CATT
R2-2204245	Introduction of NR MBS into 38.304	CATT
R2-2204246	Introduction of NR MBS into 38.322	vivo, Huawei, HiSilicon
R2-2204251	Introduction of NR MBS into 38.331	Huawei, HiSilicon
R2-2204261	Introduction of NR MBS	CMCC, Huawei

8.1.3.1: Pre-discussions

TDoc	Title	Source
R2-2202685	Report of [Pre117-e][002][MBS] UP open Issues Input	Samsung
R2-2203343	Report of: [Pre117-e][001][MBS] CP open Issues Input	Huawei, HiSilicon
R2-2203764	Report of: [Pre117-e][001][MBS] CP open Issues Input	Huawei, HiSilicon
R2-2203773	LS on MBS broadcast reception on Scell	RAN2
R2-2204015	Report of Offline 002: UP Open Issues	Samsung
R2-2204017	LS on HARQ process for MCCH and Broadcast MTCH(s)	RAN2

8.1.3.2: Invited Input

TDoc	Title	Source
R2-2202242	Discussion on open issues in MAC running CR	OPPO
R2-2202267	Discussion on Questions for Split NR-RAN Architecture from RAN3 LS	CATT
R2-2202268	Consideration on UP Remaining Issues of MBS	CATT, CBN
R2-2202278	Open issue for CSI and SRS reporting due to MBS DRX	NEC Europe Ltd
R2-2202301	Discussion on CSI reporting and RX_DELIV initialization	Huawei, Qualcomm,HiSilicon
R2-2202333	Discussion on CSI and SRS reporting for MBS	MediaTek inc.
R2-2202334	Discussion on MBS split NR-RAN architecture based on RAN3 LS	MediaTek inc.
R2-2202335	Draft LS on the support of MBS split NR-RAN architecture	MediaTek inc.
R2-2202368	Discussion on LS on NR RRC to support split NR-RAN architecture for NR MBS	TD Tech, Chengdu TD Tech
R2-2202425	Discussion on CSI and SRS reporting due to MBS DRX	Spreadtrum Communications
R2-2202426	Discussion on Supporting split NR-RAN architecture for NR MBS	Spreadtrum Communications
R2-2202554	MBS DRX mechanism	Apple
R2-2202555	Support of MBS in MR-DC	Apple
R2-2202624	Discussion on CSI and SRS reporting	CMCC
R2-2202625	Discussion on RRC to support split NR-RAN architecture for NR MBS	CMCC
R2-2202642	CSI and SRS reporting due to MBS DRX	Intel Corporation
R2-2202644	Support of split NR-RAN architecture for NR MBS	Intel Corporation
R2-2202683	CSI and SRS reporting in Multicast DRX	Samsung
R2-2202684	Discussion on MBS RRC Configuration for Split RAN	Samsung
R2-2202782	MRB ID Scope and Uniqueness	Nokia, Nokia Shanghai Bell
R2-2202799	On CSI-report and SRS transmission at DRX with MBS and unicast	Futurewei
R2-2202830	Remaining issues on DRX	Huawei, HiSilicon
R2-2202978	Discussion on NR RRC to Support Split NR-RAN Architecture for NR MBS	vivo
R2-2203121	CSI and SRS reporting in MBS DRX	Xiaomi Communications
R2-2203156	Discussion on open issues for NR MBS	LG Electronics Inc.
R2-2203226	Common RRC Structure for MBS Multicast	Nokia, Nokia Shanghai Bell
R2-2203311	CSI and SRS reporting in MBS DRX	ZTE, Sanechips
R2-2203312	NR RRC to support split NR-RAN architecture for NR MBS	ZTE, Sanechips
R2-2203345	Discussion on RRC support of split NR-RAN architecture for NR MBS	Huawei, HiSilicon
R2-2203761	Report of Offline 042: Invited Tdocs Open Issues UP	Samsung
R2-2203780	[AT117-e][043][MBS] Invited tdocs open Issues CP (Nokia)	Nokia
R2-2204062	[AT117-e][043][MBS] Invited tdocs open Issues CP - PART2 (Nokia)	Nokia

8.1.4: UE capabilities

TDoc	Title	Source
R2-2202269	Discussions on NR MBS UE Capabilities	CATT, CBN
R2-2202671	MBS UE capability for supporting Multicast MRBs	Qualcomm India Pvt Ltd
R2-2203118	Remaining issue of MBS UE capability	Xiaomi Communications
R2-2203120	Discussion on MBS support on MRDC	Xiaomi Communications
R2-2203775	Summary for [AT117-e][044][MBS] UE capabilities	MediaTek Inc.

8.1.5.1: Control Plane

TDoc	Title	Source
R2-2202243	Discussion on beam sweeping transmission for MTCH	OPPO
R2-2202244	Open issues for broadcast reception over SCell or non-serving Cell	OPPO
R2-2202270	Discussion on Other Issues about MBS	CATT
R2-2202294	Remaining Open Issues for MBS CP	Samsung
R2-2202332	MBS Control Plane Issues	Nokia, Nokia Shanghai Bell
R2-2202336	Discussion on MBS broadcast reception on SCell and non-serving cell	MediaTek Inc.
R2-2202369	Analysis of MBS reception interruption time during UE mobility in LTE	TD Tech, Chengdu TD Tech
R2-2202370	Open issues on control plane for broadcast mode	TD Tech, Chengdu TD Tech
R2-2202386	MBS reception interruption problem in LTE and SFN in NR MBS	TD Tech, Chengdu TD Tech
R2-2202574	Discussion multicast service reception in Scell	Lenovo, Motorola Mobility
R2-2202753	Lossless handover for PTM	InterDigital, Inc.
R2-2202754	Discussion on PTM activation/deactivation for MBS	Interdigital Inc., OPPO, CMCC, ZTE, SJTU, NERCDTV, Lenovo, Motorola Mobility, Spreadtrum, TCL, Xiaomi, MediaTek, Qualcomm, Kyocera, Apple, Sharp, China Unicom, CBN, China Telecom
R2-2202875	NR MBS UAC enhancement aspects	Qualcomm Inc
R2-2202909	Frequency of interest in MBS Interest Indication	Kyocera
R2-2202979	Loss-lee Handover Procedure from MBS-supporting Node to Non-MBS Supporting Node	vivo
R2-2202980	Loss-less Handover Procedure between MBS-supporting nodes	vivo
R2-2203201	UE based PTM to PTP switch	Sony
R2-2203313	Discussion on MBS reception in DC and CA scenarios	ZTE, Sanechips
R2-2203314	UE initiated mode switch for Multicast	ZTE, Sanechips, Kyocera, InterDigital, CMCC, OPPO, Apple
R2-2203344	Remaining CP open issues	Huawei, HiSilicon
R2-2203349	MCCH modification period	Intel Corporation

8.1.5.2: User Plane

TDoc	Title	Source
R2-2202241	Discussion on Header Compression for MBS	OPPO
R2-2202295	Remaining Open Issues for MBS UP	Samsung
R2-2202331	MBS User Plane Issues	Nokia, Nokia Shanghai Bell
R2-2202371	Open issues on user plane for NR MBS	TD Tech, Chengdu TD Tech
R2-2202401	Discussion on MBS power saving issue	Shanghai Jiao Tong University
R2-2202755	PDCP status report triggering for MBS mode switching	InterDigital, Inc.
R2-2203119	Slow-moving PDCP reception window issue	Xiaomi Communications

8.2.1: Organizational, Requirements and Scope

TDoc	Title	Source
R2-2202129	Reply LS on inter-MN RRC resume without SN change (R3-221290; contact: Ericsson)	RAN3
R2-2202170	LS on Measurement requirement for deactivated SCG (R4-2202781; contact: Ericsson)	RAN4
R2-2202481	Draft 331 CR for DCCA UE capabilities	Intel Corporation
R2-2202482	Draft 306 CR for DCCA UE capabilities	Intel Corporation
R2-2202651	Introduction of SCG activation and deactivation	ZTE Corporation, Sanechips
R2-2202794	Introduction of SCG activation and deactivation	vivo
R2-2203094	Introduction of CPA and inter-SN CPC CATT	CATT
R2-2203095	Introduction of CPA and inter-SN CPC CATT	CATT
R2-2203096	Introduction of CPA and inter-SN CPC CATT	CATT
R2-2203195	Introduction of eCADC	vivo
R2-2203370	Introduction of efficient SCG activation/deactivation	Huawei, HiSilicon
R2-2203371	Introduction of efficient SCG activation/deactivation	Huawei, HiSilicon
R2-2203372	Introduction of further multi-RAT dual-connectivity enhancements	Huawei, HiSilicon
R2-2203373	Introduction of further multi-RAT dual-connectivity enhancements	Huawei, HiSilicon
R2-2203389	Discussion on the LS from RAN4 on measurement requirements	Ericsson
R2-2203641	Introduction of efficient SCG activation/deactivation	Huawei, HiSilicon
R2-2203642	Introduction of efficient SCG activation/deactivation	Huawei, HiSilicon
R2-2203690	Introduction of further multi-RAT dual-connectivity enhancements	ZTE, CATT
R2-2203796	Introduction of CPA and inter-SN CPC	CATT
R2-2203797	Introduction of CPA and inter-SN CPC	CATT
R2-2203798	Introduction of CPA and inter-SN CPC	CATT
R2-2203828	Introduction of further multi-RAT dual-connectivity enhancements	Huawei, HiSilicon
R2-2203837	Introduction of further multi-RAT dual-connectivity enhancements	Huawei, HiSilicon
R2-2203891	LS on Stage 2 description for fast SCell activation (R1-2202704; contact: Huawei)	RAN1
R2-2203892	Reply LS on RAN2 agreements for TRS-based Scell activation (R1-2202706; contact: Huawei)	RAN1
R2-2204002	Introduction of CPA and inter-SN CPC	CATT
R2-2204003	Introduction of CPA and inter-SN CPC	CATT
R2-2204004	Introduction of CPA and inter-SN CPC	CATT
R2-2204014	Introduction of further MRDC enhancements	Huawei, HiSilicon
R2-2204140	LS reply on UE behaviour for deactivated SCG and value range for measCycle (R4-2207019; contact: Ericsson)	RAN4
R2-2204184	Reply LS on CPAC (R3-222754; contact: Lenovo)	RAN3
R2-2204211	Introduction of eDCCA	vivo
R2-2204252	Introduction of further multi-RAT dual-connectivity enhancements	Huawei, HiSilicon
R2-2204263	Introduction of eDCCA	vivo

8.2.2.1: UE behaviour while SCG is deactivated

TDoc	Title	Source
R2-2202248	How to model the PSCell in SCG deactivation?	OPPO
R2-2202250	SCG deactivation indication when resuming from RRC_INACTIVE due to MO data	OPPO
R2-2202280	QoS flow remapping during SCG deactivation	Fujitsu
R2-2202575	Discussion on UE behavior with SCG deactivated	Lenovo, Motorola Mobility
R2-2202649	Discussion on UE behaviour when SCG is deactivated	ZTE Corporation, Sanechips
R2-2202679	Views on several issues	Samsung Electronics
R2-2202680	DC power sharing for deactivated SCG	Samsung Electronics
R2-2202705	UE behaviour while SCG is deactivated	Qualcomm Incorporated
R2-2202756	UE behavior while the SCG is deactivated	InterDigital, Inc.
R2-2202767	Deactivation of SCG	LG Electronics Finland
R2-2202795	Discussion on UE behaviour while SCG is deactivated	vivo
R2-2202919	TA timer and RLM/BFD while the SCG is deactivated	MediaTek Inc.
R2-2203097	Discussions on UE Behavior in Deactivated SCG	CATT
R2-2203176	Open Issues on UE Behavior	NTT DOCOMO INC.
R2-2203184	UE behaviour while SCG is deactivated	Nokia, Nokia Shanghai Bell
R2-2203374	[Pre117-e][220][DCCA] Summary of UE behaviour while SCG is deactivated (Huawei)	Huawei, HiSilicon
R2-2203375	Open issues on UE behaviours while the SCG is deactivated	Huawei, HiSilicon
R2-2203390	UE behaviour while SCG is deactivated	Ericsson

8.2.2.2: Actions at SCG activation and deactivation

TDoc	Title	Source
R2-2202247	L2 based SCG activation and SCG RRM	OPPO
R2-2202281	Proposal for releasing statusReportRequired for SCG bearers at SCG deactivation	Fujitsu
R2-2202282	Remaining issues on UL data arrival for SCG	Fujitsu
R2-2202351	Futher discussion on actions at SCG activation or deactivation	Transsion Holdings
R2-2202413	Discussion on activation and deactivation of SCG	Spreadtrum Communications
R2-2202576	MAC related issues upon SCG activation and deactivation	Lenovo, Motorola Mobility
R2-2202650	Activation of deactivated SCG	ZTE Corporation, Sanechips
R2-2202701	Actions at SCG activation and deactivation	Qualcomm Incorporated
R2-2202757	Deactivation of SCG	InterDigital, Inc.
R2-2202758	Activation of SCG	InterDigital, Inc.
R2-2202796	Discussion on actions at SCG activation and deactivation	vivo
R2-2202809	Remaining issues on SCG deactivation	NEC
R2-2203039	Remaining issues for MAC procedure in deactivated SCG	SHARP Corporation
R2-2203061	split bearer handling upon SCG deactivation	Sharp
R2-2203087	Open issues on SCG deactivation	DENSO CORPORATION
R2-2203092	Discussion on partial MAC reset upon SCG deactivation	LG Electronics Inc.
R2-2203098	Remaining Issues on Actions at SCG Activation and Deactivation	CATT
R2-2203099	Discussion on RRC Aspects of SCG Deactivation	CATT
R2-2203166	Discussion on data transmission to MN for split bearer	LG Electronics Inc.
R2-2203177	Open Issues on SCG Activation and Deactivation	NTT DOCOMO INC.
R2-2203185	UL data handling at SCG deactivation	Nokia, Nokia Shanghai Bell
R2-2203186	Actions at SCG activation and deactivation	Nokia, Nokia Shanghai Bell
R2-2203376	Handling of uplink split bearers and BWP when the SCG deactivated	Huawei, HiSilicon
R2-2203377	MAC CE based SCG activation	Huawei, HiSilicon
R2-2203378	Draft Reply LS on efficient activation de-activation mechanism for one SCG	Huawei, HiSilicon
R2-2203391	Actions at SCG activation and deactivation	Ericsson
R2-2203414	Remaining Issues related to SCG Activation	LG Electronics
R2-2203639	Report of [AT117-e][222][DCCA] Actions at SCG activation and deactivation (Huawei)	Huawei

8.2.2.3: Other aspects of SCG activation/deactivation

TDoc	Title	Source
R2-2202249	Fast MCG recovery via deactivated SCG	OPPO
R2-2202531	CR TP for 38.331 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, LG Electronics, NTT DOCOMO, Inc.
R2-2202532	CR TP for 36.331 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, LG Electronics, NTT DOCOMO, Inc.
R2-2202533	CR TP for 38.321 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, NTT DOCOMO, Inc.
R2-2202703	Other aspects of SCG activation and deactivation	Qualcomm Incorporated
R2-2202780	Open issues on UE-requested SCG (de)activation	CMCC
R2-2202800	Discussion on MCG failure recovery via deactivated SCG	Futurewei
R2-2202923	Further discussion on TCI State indication in RRC	MediaTek Inc.
R2-2203040	Remaining issues for RRM measurement in deactivated SCG	SHARP Corporation
R2-2203062	Fast MCG link recovery via deactivated SCG	Sharp
R2-2203085	Consideration on�MCG�link�recovery�with�deactivated�SCG	CMCC
R2-2203703	CR TP for 38.331 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, LG Electronics, NTT DOCOMO, Inc., Lenovo, Motorola Mobility, Qualcomm Inc
R2-2203704	CR TP for 36.331 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, LG Electronics, NTT DOCOMO, Inc., Lenovo, Motorola Mobility, Qualcomm Inc
R2-2203705	CR TP for 38.321 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, NTT DOCOMO, Inc., Lenovo, Motorola Mobility, Qualcomm Inc
R2-2203803	LS on TCI state indication	RAN2
R2-2204098	CR TP for 38.331 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, LG Electronics, NTT DOCOMO, Inc., Lenovo, Motorola Mobility, Qualcomm Inc
R2-2204099	CR TP for 36.331 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, LG Electronics, NTT DOCOMO, Inc., Lenovo, Motorola Mobility, Qualcomm Inc
R2-2204100	CR TP for 38.321 on MCG Failure Recovery in deactivated SCG	Apple, Vivo, ZTE Corporation, NTT DOCOMO, Inc., Lenovo, Motorola Mobility, Qualcomm Inc

8.2.3.1: CPAC procedures from network perspective

TDoc	Title	Source
R2-2202304	Discussion on CPAC procedures from NW perspective	vivo
R2-2202468	Open issues on Rel-17 CPAC procedures from NW perspective	Nokia, Nokia Shanghai Bell
R2-2202577	On support of CPAC replace	Lenovo, Motorola Mobility
R2-2202702	CPAC procedures from network perspective	Qualcomm Incorporated
R2-2202824	Remaining issues on CPAC from NW perspective	ZTE Corporation, Sanechips
R2-2202914	Discussion on the CG-CandidateList	Google Inc.
R2-2202916	Support modification and cancellation of C-PSCells in the CG-CandidateList	Google Inc.
R2-2203045	Discussion on support for coexistence of Rel-16 and Rel-17 CPC	NTT DOCOMO INC.
R2-2203100	Remaining issues on CPAC from NW perspective	CATT
R2-2203170	Remaining issues for CPAC in network perspective	Samsung R&D Institute UK
R2-2203432	CPAC network procedures	Ericsson
R2-2203637	[AT117-e][223][DCCA] CPAC procedures from network perspective (Samsung)	Samsung

8.2.3.2: CPAC procedures from UE perspective

TDoc	Title	Source
R2-2202305	Discussion on CPAC procedures from UE perspective	vivo
R2-2202469	Open issues on Rel-17 CPAC procedures from UE perspective	Nokia, Nokia Shanghai Bell
R2-2202516	Text proposal to Uu siganling in CPAC	Apple
R2-2202578	Discussion on CPAC with deactivated SCG	Lenovo, Motorola Mobility
R2-2202777	Discussion on CPAC related open issues	LG Electronics
R2-2202825	Remaining issues on CPAC from UE perspective	ZTE Corporation, Sanechips
R2-2202924	Discussion on UE behaviour upon CPC execution	MediaTek Inc.
R2-2203101	Remaining issues on CPAC from UE perspective	CATT
R2-2203171	Remaining issues for CPAC in UE perspective	Samsung R&D Institute UK
R2-2203379	Remaining issues for CPAC	Huawei, HiSilicon
R2-2203433	UE procedures and signalling for CPAC	Ericsson
R2-2203476	CPC and SCG deactivation	Sharp
R2-2203638	Report of [AT117-e][224][DCCA] CPAC procedures from UE perspective (Nokia)	Nokia, Nokia Shanghai Bell

8.2.3.3: Other CPAC aspects

TDoc	Title	Source
R2-2202579	Coexistence of CHO and CPAC	Lenovo, Motorola Mobility
R2-2202759	Coexistence of CHO and CPC	InterDigital, Nokia, Nokia Shanghai Bell
R2-2202760	SCG failure recovery with CPAC	InterDigital, Inc.
R2-2202826	Discussion on coexistence of CHO and CPAC	ZTE Corporation, Sanechips

8.2.4: Temporary RS for SCell activation

TDoc	Title	Source
R2-2202251	TP correction for TRS ID in 38321	OPPO
R2-2202252	Introduction of TRS based SCell activation in 38.321	OPPO
R2-2202253	Introduction of TRS based SCell activation in 38.331	OPPO
R2-2202681	Leftover issues for TRS based SCell activation	Samsung Electronics
R2-2202797	Discussion on Temporary RS activation for fast SCell activation	vivo

8.2.5: UE capabilities

TDoc	Title	Source
R2-2202480	Discussion on remaining issues on DCCA UE capabilities	Intel Corporation
R2-2202483	CR TP for 38.331 on DCCA UE capabilities	Intel Corporation
R2-2202484	CR TP for 38.306 on DCCA UE capabilities	Intel Corporation
R2-2202485	CR TP for 36.331 on DCCA UE capabilities	Intel Corporation
R2-2202486	CR TP for 36.306 on DCCA UE capabilities	Intel Corporation
R2-2203380	UE capability for CPAC and SCG (de)activation	Huawei, HiSilicon
R2-2203392	UE capabilities for Rel-17 MR-DC enhancements	Ericsson
R2-2203640	Report of [AT117-e][225][DCCA] DCCA UE capabilities	Intel
R2-2203805	Draft 306 CR for DCCA UE capabilities	Intel Corporation
R2-2203806	Draft 331 CR for DCCA UE capabilities	Intel Corporation

8.3.1: Organizational, Requirements and Scope

TDoc	Title	Source
R2-2202696	Introduction of MUSIM UE Capabilities	Huawei, HiSilicon
R2-2202697	Introduction of MUSIM UE Capabilities	Huawei, HiSilicon
R2-2202962	Capture RAN2 agreements on RRC for MUSIM	vivo(Rapporteur)
R2-2202963	[Post116bis-e][202][MUSIM] Open issues for MUSIM (vivo)	vivo
R2-2203013	Introduction of MUSIM for LTE	Samsung Electronics Co., Ltd
R2-2203273	Introduction of Multi-USIM devices to 36.304	China Telecommunications
R2-2203436	Running CR to 38300 for Multi-USIM devices support	Ericsson
R2-2203437	Running CR to 36300 for Multi-USIM devices support	Ericsson
R2-2203651	Introduction of Multi-USIM devices to 36.304	China Telecommunications
R2-2203750	Introduction of MUSIM for LTE	Samsung
R2-2203801	Introduction of MUSIM UE Capabilities	Huawei, HiSilicon
R2-2203802	Introduction of MUSIM UE Capabilities	Huawei, HiSilicon
R2-2203804	Introduction of Multi-USIM devices to 36.304	China Telecommunications
R2-2203958	LS reply on RAN2 agreements for paging with service indication (S2-2201838 ; contact: vivo)	SA2
R2-2204142	Reply LS on RAN2�s agreement for MUSIM gaps (R4-2207032; contact: vivo)	RAN4
R2-2204207	Introduction of NR RRC support for MUSIM	vivo (Rapporteur)
R2-2204227	Running CR to 38300 for Multi-USIM devices support	Ericsson

8.3.2: Paging collision avoidance

TDoc	Title	Source
R2-2203751	Reply LS on alternative IMSI for MUSIM (S2-2201681; contact: Sony)	SA2

8.3.3: UE notification on network switching for multi-SIM

TDoc	Title	Source
R2-2202206	Remaining Key Issues for MUSIM Gap	OPPO
R2-2202207	Remaining Key Issues for Leaving Connected Mode	OPPO
R2-2202240	Finalizing NW switching with leaving from RRC_CONNECTED	Samsung Electronics Co., Ltd
R2-2202254	Discussion on UE requested MUSIM gap release	Samsung Electronics Co., Ltd
R2-2202419	Remaining issues about UE indication on switching	Spreadtrum Communications
R2-2202517	Open Issues in MUSIM Network Switching	Apple
R2-2202573	Remaining issues for switching notification and busy indication	Lenovo, Motorola Mobility
R2-2202645	Open issues on Network switching and Gap release signalling	Intel Corporation
R2-2202698	Remaining issues for NW switching without leaving RRC_CONNECTED	Huawei, HiSilicon
R2-2202699	Remaining issues for NW switching with leaving RRC_CONNECTED	Huawei, HiSilicon
R2-2202740	On remaining issues for MUSIM Gap configuration	Nokia, Nokia Shanghai Bells
R2-2202741	On remaining issues for switching notification for leaving RRC connection	Nokia, Nokia Shanghai Bells
R2-2202768	RRC Connection release request procedure for MUSIM and power saving	Sharp
R2-2202770	Stop using of MUSIM Gap requested to be released	Sharp
R2-2202833	Remaining issues of Network switching for MUSIM	China Telecom
R2-2202844	Interaction between NAS and AS for network switching	ASUSTeK
R2-2202845	Configured time for network switching	ASUSTeK
R2-2202856	Remaining issues on MUSIM gap configuration	LG Electronics
R2-2202880	Consideration on the Remaining Issues of the Scheduling Gap	ZTE Corporation, Sanechips
R2-2202925	Remaining issue for NW switching with leaving RRC_CONNECTED	MediaTek Inc.
R2-2202938	Remain issues for network switching with leaving RRC_CONNECTED	SHARP Corporation
R2-2202964	Remaining issue on network switching	vivo
R2-2203227	Remaining issues on MUSIM gap configuration	LG Electronics France
R2-2203415	Remaining Issues on Switching with RRC Release	LG Electronics
R2-2203416	Considerations on Busy Indication	LG Electronics
R2-2203434	Remaining discussion on switchover procedures	Ericsson
R2-2203440	Corrections to the NR RRC CR for MUSIM (38.331)	Ericsson
R2-2203635	[Pre117-e][230][MUSIM] Summary Stage-3 details of MUSIM	vivo
R2-2203664	Report of [AT117-e][232][MUSIM] Remaining details of MUSIM network switching (Samsung)	Samsung

8.3.4: Paging with service indication

TDoc	Title	Source
R2-2202239	Clarification on UE behavior for NAS-based busy indication in RRC_INACTIVE	Samsung Electronics Co., Ltd
R2-2202965	Remaining issue on paging cause feature	vivo

8.3.5: UE capabilities and other aspects

TDoc	Title	Source
R2-2202518	Miscellaneous Issues in MUSIM	Apple
R2-2202646	MUSIM remaining issue on gap capability signalling	Intel Corporation
R2-2202700	Remaining issues for MUSIM UE Capabilities	Huawei, HiSilicon
R2-2202752	Discussion on MUSIM band conflict scenarios	Nokia, Nokia Shanghai Bell
R2-2202885	Consideration on the MUSIM UE capability reporting	ZTE Corporation, Sanechips
R2-2202893	Consideration on the band collision issue	ZTE Corporation, Sanechips
R2-2202936	UE Capabilities for MUSIM Gap Pattern	OPPO
R2-2202966	Remaining issue on UE capabilities	vivo
R2-2203435	Remaining aspects on UE capabilities for Multi-USIM and other issues	Ericsson
R2-2203665	[AT117-e][233][MUSIM] MUSIM UE capabilities (Huawei)	Huawei, HiSilicon

8.4.1: General

TDoc	Title	Source
R2-2202327	Updated Rel-17 IAB Workplan	Qualcomm Incorporated, Samsung (WI rapporteurs)
R2-2202967	Capture RAN2 agreements on CP-UP separation support in NR eIAB	vivo(Rapporteur)
R2-2204208	Introduction of CP-UP separation support in NR eIAB	vivo(Rapporteur)

8.4.1.2: LS in

TDoc	Title	Source
R2-2202172	LS on range of power control parameters for eIAB (R4-2203020; contact: Samsung)	RAN4
R2-2203749	LS on upper layers parameters for Rel-17 eIAB (R1-2202947; contact: Qualcomm)	RAN1
R2-2204012	LS on upper layers parameters for Rel-17 eIAB (R1-2202737; contact: Qualcomm)	RAN1
R2-2204109	Reply LS on range of power control parameters for eIAB (R1-2202877; contact: Samsung)	RAN1
R2-2204110	LS on Rel-17 NR eIAB for TS 38.300 (R1-2202884; contact: Qualcomm)	RAN1

8.4.1.3: CRs and Rapporteur Resolutions

TDoc	Title	Source
R2-2202328	Running CR to TS 38.300 for eIAB	Qualcomm Incorporated
R2-2202372	Running CR of TS 38.340 for eIAB	Huawei, HiSilicon
R2-2202373	Resolution proposals to Rapporteur Handled Open Issues BAP#5,6,7,9	Huawei, HiSilicon
R2-2203276	Running CR to 38.321 on Integrated Access and Backhaul for NR Rel-17	Samsung Electronics GmbH
R2-2203471	Enhancements to Integrated Access and Backhaul for NR	Ericsson
R2-2204092	Running CR to 38.321 on Integrated Access and Backhaul for NR Rel-17	Samsung Electronics GmbH
R2-2204093	Summary of discussion [AT117-e][014][eIAB] MAC (Samsung)	Samsung (rapporteur)
R2-2204210	Introducing Enhancements to Integrated Access and Backhaul for NR	Ericsson
R2-2204215	Running CR to 38.321 on Integrated Access and Backhaul for NR Rel-17	Samsung Electronics GmbH
R2-2204219	Running CR of TS 38.340 for eIAB	Huawei, HiSilicon
R2-2204248	Introduction of IAB enhancements	Qualcomm Incorporated
R2-2204249	Introduction of eIAB to TS 38.340	Huawei, HiSilicon
R2-2204250	CR to 38.321 introducing Integrated Access and Backhaul for NR Rel-17	Samsung
R2-2204253	Introduction of IAB enhancements	Qualcomm (Rapporteur)

8.4.3.1: Pre-discussions

TDoc	Title	Source
R2-2202329	[Pre117-e][003][eIAB] eIAB Open Issues Input	Qualcomm Incorporated (Rapporteur)
R2-2203278	Summary of discussion [Pre117-e][014][eIAB] eIAB MAC Open Issues Input (Samsung)	Samsung Electronics GmbH
R2-2203961	[AT117-e][003][eIAB] Open Issues (Qualcomm)	Qualcomm (Rapporteur)

8.4.3.2: Invited Input

TDoc	Title	Source
R2-2202255	BAP re-writing mapping confirguration	NEC
R2-2202330	Remaining BAP issues for eIAB	Qualcomm Incorporated
R2-2202346	Discussion on the BAP open issues	Fujitsu
R2-2202374	BAP open issues on option a to d and issues BAP#1, #3 and #4	Huawei, HiSilicon
R2-2202382	Further considerations on local re-routing	ZTE, Sanechips
R2-2202383	Discussion on re-routing and header rewriting configuration	ZTE, Sanechips
R2-2202583	Discussion on remaining issues for BAP routing	Lenovo, Motorola Mobility
R2-2202643	Discussion on remaining BAP open issues	Intel Corporation
R2-2202761	Remaining issues regarding BH RLF indications	InterDigital, Inc.
R2-2202908	BAP open issues on BAP#01, BAP#03 and BAP#04	Kyocera
R2-2202968	Remaining Issues of Inter-donor DU Rerouting	vivo
R2-2202969	Remaining Issues of Inter-Topology Routing and Rerouting	vivo
R2-2203053	Discussion on BAP re-writing mapping configurations for UL inter-donor-DU re-routing	LG Electronics Inc.
R2-2203054	Discussion on identified BAP open issues (BAP#1, BAP#2, BAP#3, BAP#4)	LG Electronics Inc.
R2-2203105	BAP open issues	Samsung Electronics GmbH
R2-2203402	BAP header rewriting and inter-donor-DU re-routing	Nokia, Nokia Shanghai Bell
R2-2203403	Simplified text proposal for BAP routing and header rewriting	Nokia, Nokia Shanghai Bell
R2-2203469	BAP open issues	Ericsson
R2-2203507	Header Rewriting for Inter-to-intra topology re-routing	Futurewei Technologies
R2-2203527	Report of [Pre117-e][021][eIAB] AI summary of 8.4.3.2 Invited Input	Huawei, HiSilicon
R2-2203934	Report of [AT117-e][021][eIAB] BAP	Huawei, HiSilicon

8.4.4: UE capabilities

TDoc	Title	Source
R2-2202376	UE capability issues for eIAB	Huawei, HiSilicon
R2-2202384	Discussion on R17 IAB-MT capabilities	ZTE, Sanechips
R2-2202970	Remaining UE capability for IAB-MT	vivo
R2-2203113	eIAB UE capabilities - open issues	Samsung Electronics GmbH
R2-2203212	Discussion on UE capability for local rerouting	Intel Corporation
R2-2203467	On eIAB capabilities	Ericsson
R2-2203702	AI summary of AI 8.4.4 UE capabilities (Intel)	Intel Corporation
R2-2203976	[AT117-e][022][eIAB] UE capabilities (Intel)	Intel Corporation (Rapporteur)
R2-2203977	UE capabilities for Rel-17 eIAB	Intel Corporation
R2-2203978	UE capabilities for Rel-17 eIAB	Intel Corporation

8.4.5: Other

TDoc	Title	Source
R2-2202375	TP for the Extended BSR	Huawei, HiSilicon
R2-2202762	CHO in IAB	InterDigital, Inc.
R2-2202907	Miscellaneous issues in BAP running CR	Kyocera
R2-2203213	Discussion on RAN2 impact of Solution 1 for Intra-donor CU service interruption reduction	Intel Corporation
R2-2203265	Resolving open issues on BH RLF indications	LG Electronics France
R2-2203400	Remaining details on RLF indications and re-routing aspects upon RLF	Nokia, Nokia Shanghai Bell
R2-2203466	RAN2 impact of miscellaneous features driven by RAN3 and RAN1	Ericsson

8.5.1: Organizational

TDoc	Title	Source
R2-2202325	Introduction of enhanced IIoT&URLLC support for NR	Ericsson
R2-2202464	Draft 38.306 CR for Rel-17 NR IIoT URLLC UE capabilities	Intel Corporation
R2-2202465	Draft 38.331 CR for Rel-17 NR IIoT URLLC UE capabilities	Intel Corporation
R2-2202522	RAN1 feature impact on intra-UE prioritization in MAC	Apple
R2-2202682	Introduction of enhanced IIoT&URLLC support for NR	Samsung
R2-2202686	Report of [POST116bis-e][512][IIoT] UP open issue	Samsung
R2-2203196	Introduction of Rel-17 IIoT/URLLC to TS 38.300	Nokia, Nokia Shanghai Bell
R2-2203291	Propagation Delay Compensation for TSN	Qualcomm Incorporated
R2-2203302	Summary of [POST116bis-e][513][IIoT] CP open issues (Ericsson)	Ericsson
R2-2203766	Introduction of enhanced IIoT&URLLC support for NR	Ericsson
R2-2203951	Summary of [AT117-e][513][IIoT] CR 38.331 (Ericsson)	Ericsson
R2-2203980	Report of email discussion [AT117-e][508][IIoT] UE Capabilities (Intel)	Intel Corporation
R2-2203981	Draft 38.306 CR for Rel-17 NR IIoT URLLC UE capabilities	Intel Corporation
R2-2204016	Introduction of enhanced IIoT&URLLC support for NR	Samsung
R2-2204086	Introduction of Rel-17 IIoT/URLLC to TS 38.300	Nokia, Nokia Shanghai Bell
R2-2204091	Draft 38.331 CR for Rel-17 NR IIoT URLLC UE capabilities	Intel Corporation
R2-2204141	Reply LS on propagation delay compensation (R4-2207021; contact: Huawei)	RAN4

8.5.2: Enhancements for support of time synchronization

TDoc	Title	Source
R2-2202182	RE: LS on Time Synchronization	IEEE 1588 WG
R2-2202437	Remaining issues on time synchronization enhancement	OPPO
R2-2202580	Left issues for time synchronization	Lenovo, Motorola Mobility
R2-2202708	Discussion on remaining issues for accurate time synchronization	Huawei, HiSilicon
R2-2202728	Remaining Issues on PDC Enhancement	CMCC
R2-2202750	Remaining issues of time synchronization	ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd
R2-2202784	Simplifying the PRS procedure forRemaining Issues of RTT-based PDC	CATT
R2-2202894	Remaining issues for PDC	vivo
R2-2203197	Propagation Delay Compensation signalling	Nokia, Nokia Shanghai Bell
R2-2203303	MAC CE update for SRS Spatial Relation Indication	Ericsson
R2-2203461	Propagation Delay Compensation for TSN	Qualcomm Incorporated
R2-2203733	Report of [AT117][503][IIoT] Tsynch additional open issues (Qualcomm)	Qualcomm (email discussion rapporteur)

8.5.3: Uplink enhancements for URLLC in unlicensed controlled environments

TDoc	Title	Source
R2-2202444	Discussion on the DRX impact of enhanced HARQ feedback and intra-UE prioritization	Lenovo, Motorola Mobility
R2-2202946	Configured grant mode switching for IIoT/URLLC in UCE	III
R2-2203294	RAN2 impacts of RAN1 Agreements on Enhanced HARQ feedback	Qualcomm Incorporated
R2-2203304	Multi-TB scheduling in UCE	Ericsson

8.5.4: RAN enhancements based on new QoS

TDoc	Title	Source
R2-2202283	Analysis on N>1	Fujitsu
R2-2202284	Survival Time Mode and Measurement Gap	Fujitsu
R2-2202438	Remaining issues on survival time	OPPO
R2-2202445	Remaining issues on the support of survival time	Lenovo, Motorola Mobility
R2-2202523	Remaining issues on RAN enhancements for new QoS	Apple
R2-2202709	Discussion about UE behaviours for Survival Time state operation	Huawei, HiSilicon
R2-2202726	Remaining Issues on QoS enhancement	CMCC
R2-2202751	N and combined Tx-side timer for IIoT QoS	ZTE, Sanechips, China Southern Power Grid Co., Ltd, TCL Communication Ltd., vivo
R2-2202785	On the support of N>1 for Survival Time solution	CATT
R2-2202834	Additional aspects on resource in Survival Time	III
R2-2202895	Discussion on Radio Resource for the duplicated legs in ST	vivo
R2-2203125	Remaining issues of survival time requirements	Xiaomi Communications
R2-2203144	Finalising Survival Time related enhancements	Samsung Electronics GmbH
R2-2203198	On Closure of Survival Time Objective	Nokia, Nokia Shanghai Bell
R2-2203460	Remaining issues on the support of survival time	InterDigital
R2-2203734	Summary of [AT117-e][504][IIoT] QoS Additional Open Issues (Nokia)	Nokia, Nokia Shanghai Bell

8.6: Small Data enhancements

TDoc	Title	Source
R2-2204254	Reply LS on handling of DL non-SDT during SDT procedure	RAN2

8.6.1: Organizational

TDoc	Title	Source
R2-2202143	Reply LS on the ROHC continuity for SDT (R3-221471; contact: Huawei)	RAN3
R2-2202144	LS on handling of DL non-SDT during SDT procedure (R3-221472; contact: CATT)	RAN3
R2-2202594	Running MAC CR for small data	Huawei, HiSilicon
R2-2202595	Summary of [Post116-e][507][SDT] MAC running CR update (Huawei)	Huawei, HiSilicon
R2-2202611	Introduction of Small Data Transmission for MAC spec	Huawei, HiSilicon
R2-2202612	Summary of [POST116bis-e][510][Sdata] Running MAC CR	Huawei, HiSilicon
R2-2202672	UE capabilities for Rel-17 SDT	Intel Corporation
R2-2202673	UE capabilities for Rel-17 SDT	Intel Corporation
R2-2203279	Stage-2 introduction of SDT	Nokia, Nokia Shanghai Bell
R2-2203296	Introduction of SDT	ZTE Corporation (rapporteur)
R2-2203722	Reply LS on Security of Small data transmission (S3-220463; contact: Intel)	SA3
R2-2203768	Introduction of SDT	ZTE Corporation (rapporteur)), China Telecom
R2-2203859	NAS's trigger for resume for SDT (C1-221891; contact: OPPO)	CT1
R2-2203911	UE capabilities for Rel-17 SDT	Intel Corporation
R2-2203912	UE capabilities for Rel-17 SDT	Intel Corporation
R2-2204010	Reply LS on the physical layer aspects of small data transmission (R1-2202656; contact: ZTE)	RAN1
R2-2204045	UE capabilities for Rel-17 SDT	Intel Corporation
R2-2204046	UE capabilities for Rel-17 SDT	Intel Corporation
R2-2204067	NAS's trigger for resume for SDT (C1-221891; contact: OPPO)	CT1
R2-2204079	Reply LS on Security of Small data transmission (S3-220463; contact: Intel)	SA3
R2-2204103	UE capabilities for Rel-17 SDT	Intel Corporation
R2-2204104	UE capabilities for Rel-17 SDT	Intel Corporation
R2-2204216	Introduction of Small Data Transmission for MAC spec	Huawei, HiSilicon
R2-2204217	Summary of [AT117-e][511][Sdata] CR 38.321 (Huawei)	Huawei
R2-2204234	Introduction of SDT	Nokia, Nokia Shanghai Bell

8.6.2: User plane common aspects

TDoc	Title	Source
R2-2202274	Discussion on user plane issues of SDT	OPPO
R2-2202342	CG-SDT-TAT expiry handing during the CG-SDT procedure	Samsung Electronics Co., Ltd
R2-2202446	Remaining UP issues for SDT	Lenovo, Motorola Mobility
R2-2202609	Summary of [POST116bis-e][510][Sdata] UP open issues (Huawei)	Huawei, HiSilicon
R2-2202610	Remaining issues for SDT user plane	Huawei, HiSilicon
R2-2202735	Remaining issues of user plane aspects of SDT	China Telecom
R2-2202959	Remaining issues on UP aspects of SDT	Qualcomm Incorporated
R2-2202983	Remaining UP Issues on SDT Procedure	vivo
R2-2203008	Remaining user plane aspects of SDT	NEC
R2-2203158	User Plane Aspects for SDT	Ericsson
R2-2203280	UP and CG aspects for SDT	Nokia, Nokia Shanghai Bell
R2-2203458	Remaining UP issues for SDT	InterDigital
R2-2203731	Summary of remaining user plane issues for SDT	InterDigital (rapporteur)

8.6.3: Control plane common aspects

TDoc	Title	Source
R2-2202275	Discussion on control plane issues of SDT	OPPO
R2-2202556	Control plane aspects of SDT	Apple
R2-2202590	Analysis on CP open issue of SDT	Lenovo, Motorola Mobility
R2-2202674	Additional discussion on identified open CP issues	Intel Corporation
R2-2202736	Remaining issues of control plane aspects of SDT	China Telecom
R2-2202805	Handling of DL non-SDT during SDT	CATT
R2-2202846	Remaining issue on CS-RNTI configuration for CG-SDT	ASUSTeK
R2-2202960	Remaining issues on CP aspects of SDT	Qualcomm Incorporated
R2-2202982	Further Consideration on the Handling of non-SDT Data Arrival	vivo
R2-2203009	Remaining control plane aspects of SDT	NEC
R2-2203155	CP aspects for SDT	Ericsson
R2-2203299	[POST116bis-e][511][Sdata] - Running CR comments summary	ZTE Wistron Telecom AB
R2-2203300	[POST116bis-e][511][Sdata] - CP open issue list summary	ZTE Wistron Telecom AB
R2-2203337	Control plane common aspects for SDT	Huawei, HiSilicon
R2-2203338	CCCH based non-SDT data indication	Huawei, HiSilicon
R2-2203353	SDT control plane aspects	Nokia, Nokia Shanghai Bell
R2-2203475	Introduction of DCCH solution for non-SDT data arrival	Intel Corporation, ZTE Corporation, Sanechips, Samsung, Xiaomi, MediaTek, Radisys, Reliance JIO, Qualcomm, CMCC, OPPO, Lenovo, Sony, Apple, CATT, AT&T
R2-2203520	CCCH based non-SDT data indication	Huawei, HiSilicon, InterDigital, LGE, ASUSTeK, Nokia, Nokia Shanghai Bell, Google, Rakuten Mobile, Fujitsu, NEC, Ericsson
R2-2203528	Introduction of DCCH solution for non-SDT data arrival	Intel Corporation, ZTE Corporation, Sanechips, Samsung, Xiaomi, MediaTek, Radisys, Reliance JIO, Qualcomm, CMCC, OPPO, Lenovo, Sony, Apple, CATT, AT&T, T-Mobile, China Telecom, vivo
R2-2203529	Handling of DL non-SDT during SDT	CATT, Huawei, HiSilicon, China Telecom, CMCC
R2-2203716	[POST116bis-e][511][Sdata] - CP open issue list summary	ZTE Corporation (rapporteur)
R2-2203732	Summary of [AT117-e] [501] [ Sdata] CP additional open issues (Samsung)	Samsung
R2-2203840	Discussion on the handling of emergency calls during SDT	OPPO
R2-2203913	Introduction of DCCH solution for non-SDT data arrival	Intel Corporation, ZTE Corporation, Sanechips, Samsung, Xiaomi, MediaTek, Radisys, Reliance JIO, Qualcomm, CMCC, Lenovo, Sony, Apple, CATT, AT&T, T-Mobile, China Telecom, vivo
R2-2204064	Summary of [AT117-e] [501] [Sdata] CP additional open issues � Phase2	Rapporteur (ZTE)
R2-2204269	LS on TA validation for CG-SDT	RAN2
R2-2204270	LS to CT1 on Small Data Transmission	RAN2

8.7.1: Organizational

TDoc	Title	Source
R2-2202127	Reply LS for authorization information for 5G ProSe Layer-3 Remote UE (R3-221202; contact: CATT)	RAN3
R2-2202136	LS on mapping configuration of sidelink relay (R3-221411; contact: Samsung)	RAN3
R2-2202201	Work planning for R17 SL relay	OPPO, CMCC
R2-2202202	Remaining open issues for R17 SL relay	OPPO
R2-2202276	Running CR for TS 38.351	OPPO
R2-2202343	Stage 2 CR on Introduction of R17 SL Relay	MediaTek Inc.
R2-2202543	Introduction of Sidelink Relay	Apple
R2-2202544	Discussion on remaining issues of MAC CR	Apple
R2-2202781	Stage 2 Running CR on Introduction of R17 SL Relay	MediaTek Inc.
R2-2202819	Introduction of SL relay	Huawei, HiSilicon
R2-2202820	Stage3 open issues handling for RRC CR	Huawei, HiSilicon
R2-2202950	Introduction of SL Relay in 38.322	Samsung
R2-2202951	Introduction of SL Relay in 38.323	Samsung
R2-2202952	Discussion on RAN3 LS on mapping configuration of sidelink relay	Samsung
R2-2203324	38.304 CR for SL relay	Ericsson
R2-2203325	Way forward on open issues in 38.304 for SL relay	Ericsson
R2-2203519	Draft 38.306 CR for sidelink relay UE capabilities	Qualcomm Incorporated
R2-2203594	Running CR for TS 38.351	OPPO
R2-2203598	[AT117-e][620][Relay] Reply LS to RAN3 on mapping configuration (Samsung)	Samsung
R2-2203599	Reply LS to RAN3 on mapping configuration of sidelink relay	RAN2
R2-2203628	[AT117-e][611][Relay] Way forward on FFs in 38.304	Ericsson
R2-2203629	38.304 CR for SL Relay	Ericsson
R2-2203905	Draft 38.306 CR for sidelink relay UE capabilities	Qualcomm Incorporated
R2-2203910	Introduction of sidelink relay capability	Qualcomm Incorporated
R2-2203927	LS reply on support of RAN sharing and discovery signalling (S2-2201296; contact: Huawei)	SA2
R2-2203943	Introduction of SL relay	Huawei, HiSilicon
R2-2203944	Stage 2 CR on Introduction of R17 SL Relay	MediaTek Inc.
R2-2203945	Summary Report of [AT117-e][613][Relay] Relay running CR to 38.321 (Apple)	Apple
R2-2203946	Introduction of Sidelink Relay	Apple
R2-2203947	Running CR for TS 38.351	OPPO
R2-2203955	Reply LS on discovery and data associated to different L2 IDs (S2-2201298; contact: vivo)	SA2
R2-2203965	Introduction of SL Relay in 38.322	Samsung
R2-2203966	Introduction of SL Relay in 38.323	Samsung
R2-2203971	Stage 2 CR on Introduction of R17 SL Relay	MediaTek Inc.
R2-2203991	Report of [AT117-e][615][Relay] Relay running CR to 38.331 (Huawei)	Huawei
R2-2204058	Draft 38.306 CR for sidelink relay UE capabilities	Qualcomm Incorporated
R2-2204059	Introduction of sidelink relay capability	Qualcomm Incorporated
R2-2204206	Introduction of SL Relay in 38.323	Samsung
R2-2204225	Introduction of Sidelink Relay	MediaTek Inc.
R2-2204226	Introduction of SL relay	Huawei, HiSilicon

8.7.2.1: Control plane procedures

TDoc	Title	Source
R2-2202184	Remaining issues on control plane procedure of L2 U2N relay	Qualcomm Incorporated
R2-2202340	Left issue on NR sidelink relay control plane procedure	OPPO
R2-2202344	Discussion on notification of cell reselection and HO of a relay UE	SHARP Corporation
R2-2202345	Discussion on SRAP config	SHARP Corporation
R2-2202357	Indication to Upper Layer to Trigger Service Request of L2 Relay	CATT
R2-2202358	Impacts on RAN of AN Release of Relay UE	CATT
R2-2202379	Further discussion on RRC connection establishment of remote UE	ZTE, Sanechips
R2-2202411	Remaining open issues on control plane procedures for L2 U2N relay	Spreadtrum Communications
R2-2202471	On Capturing the Agreements Related to SI in the RRC CR	InterDigital
R2-2202472	Cause Value Setting for Connection Establishment for UE to NW Relays	InterDigital
R2-2202473	Handling the Sidelink Notification Message	InterDigital
R2-2202567	Further Discussion on L2 CP Issue O6.03	vivo
R2-2202569	Draft reply LS on establishment/resume cause value on L2 SL Relay	vivo
R2-2202822	Report of [Pre117-e][605][Relay] Open issues on relay control plane procedures	Huawei, HiSilicon
R2-2202847	Reflecting agreement on sidelink resource allocation mode configuration for L2 U2N remote UE in RRC running CR	ASUSTeK
R2-2202953	Open issue on SI request over PC5	Samsung
R2-2203135	Considerations on cause codes	Nokia, Nokia Shanghai Bell
R2-2203148	Discussion on connection control open issues	Xiaomi
R2-2203178	Remaining issues on CP	Lenovo, Motorola Mobility
R2-2203272	Support of relay UE in RRC_IDLE/INACTIVE state during direct to indirect path switching	Nokia, Nokia Shanghai Bell
R2-2203306	Setting cause value for Relay UE access	Intel Corporation
R2-2203308	Discussion on added latency for paging forwarding	Nokia, Nokia Shanghai Bell
R2-2203326	Remaining issues on control plane for L2 sidelink relay	Ericsson
R2-2203591	Email discussion report on [Pre117-e][609][POS] Open issues on positioning in RRC_INACTIVE (InterDigital)	InterDigital Inc.
R2-2203942	Report of [AT117-e][627][Relay] Remaining issues on control plane (Huawei)	Huawei, HiSilicon

8.7.2.2: Service continuity

TDoc	Title	Source
R2-2202185	Remaining issues on service continuity of L2 U2N relay	Qualcomm Incorporated
R2-2202341	Left issue on NR sidelink relay service continuity	OPPO
R2-2202356	Report of [Pre117-e][603][Relay] Open Issues on Relay Service Continuity (CATT)	CATT
R2-2202380	Remaining issues on service continuity	ZTE, Sanechips
R2-2202545	Discussion on remaining issues for direct-to-indirect path switch	Apple
R2-2202584	Path switching in L2 U2N relay case	Lenovo, Motorola Mobility
R2-2202738	RRC corrections on path switch	NEC Corporation
R2-2202821	Stage3 issue on NCGI reporting in measurement result	Huawei, HiSilicon
R2-2202848	Potential issues on multiple PDU sessions handling during U2N direct to indirect path switching	ASUSTeK
R2-2203202	Service continuity open issues in L2 NR sidelink relay	Sony
R2-2203595	Summary of [621]	OPPO

8.7.2.3: Adaptation layer design

TDoc	Title	Source
R2-2202200	Summary of [Pre117-e][604][Relay] Open issues on relay adaptation layer (OPPO)	OPPO
R2-2202392	Discussion on SRAP for L2 U2N relay	Huawei, HiSilicon
R2-2202429	Remaining issues of the adaptation layer	Ericsson
R2-2202675	Remaining issue on sidelink adaptation layer	Qualcomm Incorporated
R2-2202854	SRAP header format design	CMCC
R2-2202897	Discussion on UE's L2 ID	Sharp
R2-2203172	SRAP - miscellaneous issues	Samsung Electronics GmbH

8.7.2.4: QoS

TDoc	Title	Source
R2-2202339	Left issue on QoS for layer 2 relay	OPPO
R2-2202381	Miscellaneous issues on bearer mapping and QoS	ZTE, Sanechips
R2-2202428	Aspects for QoS management with SL relay	Ericsson
R2-2202954	Open issue on new code-point for address resolution protocol (ARP) in PDCP SDU type	Samsung
R2-2202955	Summary of [Pre117-e][602][Relay] Open issues on relay QoS (Samsung)	Samsung
R2-2203600	[AT117-e][619][Relay] Flow control and pre-emptive BSR mechanisms	Samsung
R2-2203964	[AT117-e][614][Relay] Summary of open issue in PDCP/RLC	Samsung

8.7.2.5: Discovery and re/selection

TDoc	Title	Source
R2-2202186	Remaining issues on discovery and relay (re)selection	Qualcomm Incorporated
R2-2202378	Summary of [Pre117-e][601][Relay] Discovery and relay re-selection (ZTE)	ZTE, Sanechips
R2-2202412	Remaining issues on NotificationMessageSidelink message	Spreadtrum Communications
R2-2202568	Remaining issues on Discovery and Relay (re)selection	vivo
R2-2202585	Discovery and Relay (re)selection in L2 and L3 relay case	Lenovo, Motorola Mobility
R2-2202849	Issues on priority between PC5 signalling and SL discovery	ASUSTeK
R2-2203233	Discussion on relay re-selection and discovery	Huawei, HiSilicon
R2-2203506	Sidelink discovery support as indicated within SIB12	Beijing Xiaomi Mobile Software
R2-2203763	Summary of [AT117-e][622][Relay] Remaining issues on discovery and (re)selection (ZTE)	ZTE

8.7.2.6: UE capabilities

TDoc	Title	Source
R2-2202359	Further Discussion on UE Capability	CATT
R2-2202676	Summary report of offline606 - Open issues on relay UE capabilities (Qualcomm)	Qualcomm Incorporated

8.8.1: Organizational

TDoc	Title	Source
R2-2202443	Introduction of RAN Slicing	OPPO
R2-2202616	List of open issues for RAN slicing WI	CMCC
R2-2203021	Report of [Post116-e][243][Slicing] Running NR RRC CR for RAN slicing (Huawei)	Huawei
R2-2203022	NR RRC CR for RAN slicing	Huawei, HiSilicon
R2-2203069	RAN enhancements in the support of slicing	Nokia, Nokia Shanghai Bell
R2-2203588	RAN enhancements in the support of slicing	Nokia, Nokia Shanghai Bell
R2-2203650	Report for [AT117-e][241][Slicing] Closing slice-specific reselection open issues (CMCC)	CMCC
R2-2203781	38.304 CR for RAN slicing	Ericsson
R2-2203782	Report of [AT117-e][244][Slicing] Frequency sorting and equal frequency priorities (Lenovo)	Lenovo
R2-2203783	Report of [AT117-e][245][Slicing] Updated CR for 38.331 (Huawei)	Huawei, HiSilicon
R2-2203784	NR RRC CR for RAN slicing	Huawei, HiSilicon
R2-2203933	Reply LS on Slice list and priority information for cell reselection (S2-2201859; contact: ZTE)	SA2
R2-2204222	Introduction of slice-based cell re-selection	Ericsson
R2-2204224	Introduction of RAN Slicing	OPPO

8.8.2: Cell reselection

TDoc	Title	Source
R2-2202187	Remaining issues on slice specific cell reselection	Qualcomm Incorporated
R2-2202350	Considerations on the slice group in slice based cell reselection	Beijing Xiaomi Software Tech
R2-2202416	Discussion on the details of slice based cell reselection procedure	Spreadtrum Communications
R2-2202417	Discussion on remaining issues for slice based cell reselection	Spreadtrum Communications
R2-2202439	Remaining issues on slice-specific cell reselection	OPPO
R2-2202514	Text Proposal for slice based cell re-selection	Apple, BT plc
R2-2202617	Discussion on open issues for slice based cell reselection	CMCC
R2-2202640	Further considerations of slice based cell reselection without formula	Intel Corporation
R2-2202690	The remaining issues on slice based cell reselection	CATT
R2-2203018	Discussion on slice based Cell reselection under network control	Huawei, HiSilicon
R2-2203070	Considerations on slice groups	Nokia, Nokia Shanghai Bell
R2-2203071	Slice-based cell reselection proposal	Nokia, Nokia Shanghai Bell
R2-2203086	Discussion on slice based cell reselection	LG Electronics UK
R2-2203145	Discussion on slice based cell re-selection	China Telecommunications
R2-2203150	Discussion on slice based cell re-selection	China Telecommunications
R2-2203179	Remaining open points on RAN slicing	Samsung R&D Institute UK
R2-2203183	Way forward and TP for RAN Slicing solution	Lenovo, Motorola Mobility
R2-2203234	Cell reselection relevant open issues (38.304)	NEC Telecom MODUS Ltd.
R2-2203235	Cell reselection relevant open issues (RRC)	NEC Telecom MODUS Ltd.
R2-2203266	Realising Prioritisation rules for option A without Formula	Samsung R&D Institute UK, Qualcomm Incorporated
R2-2203271	Text Proposal for 38.304 on cell reselection for RAN slicing	Samsung R&D Institute UK, Qualcomm Incorporated, OPPO
R2-2203387	Leftover issues in slice based cell reselection	ZTE corporation,Sanechips
R2-2203411	RAN Slicing enhancements in shared RAN	Ericsson
R2-2203412	On open issues for cell re-selection	Ericsson
R2-2203452	Slice information provided by RRCRelease	SHARP Corporation
R2-2203509	[Pre117-e][240][Slicing] Summary of slice-specific cell reselection (CMCC)	CMCC
R2-2203785	[draft] LS on slice group granularity	OPPO
R2-2203807	Reply LS on Slice list and priority information for cell reselection	RAN2

8.8.3: RACH

TDoc	Title	Source
R2-2202188	Remaining issues on slice specific RACH	Qualcomm Incorporated
R2-2202418	Consideration on remaining issues for slice specific RACH	Spreadtrum Communications
R2-2202440	Remaining issues on slice-specific RACH	OPPO
R2-2202515	Discussion on RACH in slicing	Apple
R2-2202618	Discussion on open issues for slice based RACH configuration	CMCC
R2-2202691	The remaining issues on slice specific random access	CATT
R2-2203019	Discussion on slice based RACH configuration	Huawei, HiSilicon
R2-2203064	Remaining issues on slice based RACH	LG Electronics Inc.
R2-2203388	Further consideration on slice specific RACH	ZTE corporation,Sanechips
R2-2203401	Detailed RRC signalling for RACH prioritization configuration	Nokia, Nokia Shanghai Bell
R2-2203636	Report of [AT117-e][242][Slicing] Slice-specific RACH prioritization (OPPO)	OPPO
R2-2203787	Updated Report of [AT117-e][242][Slicing] Slice-specific RACH prioritization (OPPO)	OPPO

8.8.4: UE capabilities

TDoc	Title	Source
R2-2202189	Further discussion on UE capablity related to RAN slicing enhancement	Qualcomm Incorporated
R2-2202210	Considerations on UE capability for RAN slicing	Beijing Xiaomi Software Tech
R2-2202441	Remaining issues on UE capability for Slicing	OPPO
R2-2202619	Discussion on UE capability for RAN slicing enhancement	CMCC
R2-2202641	UE capability for Slicing enhancement	Intel Corporation
R2-2202692	Analysis on UE capability for RAN slicing enhancement	CATT
R2-2203020	Discussion on UE capabilities for RAN slicing	Huawei, HiSilicon
R2-2203413	UE Capabilities for Slice-based Cell re-selection and RA	Ericsson
R2-2204028	Introduction of Slicing UE Capabilities	Intel Corporation
R2-2204029	Introduction of Slicing UE Capabilities	Intel Corporation

8.9: UE Power Saving

TDoc	Title	Source
R2-2203992	Working Agreement on Rel-17 RLM BFD relaxation	RAN2 Chair

8.9.1.1: Organizational

TDoc	Title	Source
R2-2204041	Introduction of UE capabilities for Rel-17 UE power saving	Intel Corporation
R2-2204042	Introduction of UE capabilities for Rel-17 UE power saving	Intel Corporation

8.9.1.2: LS in

TDoc	Title	Source
R2-2202112	LS on UE capability for paging enhancement (R1-2200768; contact: Ericsson)	RAN1
R2-2202115	LS on Paging Enhancement (R1-2200800; contact: MediaTek)	RAN1
R2-2202168	LS on signalings for enabling RLM and BFD relaxation in R17 UE power saving (R4-2202769; contact: vivo)	RAN4
R2-2202306	Discussion on reply LS on signaling for RLM BFD relaxation	vivo
R2-2203982	LS on RLM/BFD relaxation for NR UE power saving enhancements (R4-2206790; contact: MediaTek)	RAN4
R2-2204121	LS reply on PDCCH skipping (R1-2202905; contact: vivo)	RAN1
R2-2204190	Reply LS on paging subgrouping and PEI (R3-222874; contact: ZTE)	RAN3
R2-2204238	Reply LS to RAN4 on RLM BFD relaxation for ePowSav	RAN2

8.9.1.3: CRs and Rapporteur Resolutions

TDoc	Title	Source
R2-2202307	Introduction of ePowSav in TS 38.304	vivo (Rapporteur)
R2-2202308	Discussion on type-3 open issues in TS 38.304 (Rapporteur resolutions)	vivo
R2-2203058	Introduction of ePowSav in TS 38.331	CATT
R2-2203232	Introduction of UE power saving enhancements In 38.300	Huawei, HiSilicon
R2-2204122	Introduction of ePowSav in TS 38.331	CATT
R2-2204239	Introduction of ePowSav in TS 38.304	vivo (Rapporteur)
R2-2204243	Introduction of UE power saving enhancements In 38.300	Huawei, HiSilicon
R2-2204265	Introduction of ePowSav in TS 38.331	CATT

8.9.3.1: Pre-discussions

TDoc	Title	Source
R2-2202309	Report of [Pre117-e][006][ePowSav] RLM BFD relaxation (vivo)	vivo
R2-2202664	Summary report of [Pre117-e][007][ePowSav] UE capabilities	Intel Corporation
R2-2202769	Summary of [Pre117-e][004][ePowSav] PEI and paging subgrouping (MediaTek)	MediaTek Inc.
R2-2203059	Summary of [Pre117-e[005][ePowSav] TRS / CSI-RS Open Issues Input (CATT)	CATT
R2-2203901	Report of [AT117-e][004][ePowSav] PEI and paging subgrouping	MediaTek Inc.
R2-2203914	Report of [AT117-e][005][ePowSav] TRS / CSI-RS Open Issues Input (CATT)	CATT
R2-2203967	Report of [AT117-e][006][ePowSav] RLM BFD relaxation (vivo)	vivo
R2-2203968	[Draft] LS to RAN4 on RLM BFD relaxation for ePowSav	vivo

8.9.3.2.1: PEI and paging subgrouping

TDoc	Title	Source
R2-2202279	Open issues for PEI and paging subgrouping	NEC Europe Ltd
R2-2202285	Open Issues for PEI and paging subgrouping	Samsung Electronics Co., Ltd
R2-2202286	UE Identity for paging subgrouping with eDRX	Samsung Electronics Co., Ltd
R2-2202310	Discussion on remaining open issues on PEI and subgrouping	vivo
R2-2202353	Discussing on PEI and paging subgrouping	Xiaomi Communications
R2-2202519	Open Issues in Enhanced NR UE Power Save PEI / Paging Subgrouping	Apple
R2-2202771	Open Issues for PEI and Paging Subgrouping	MediaTek Inc.
R2-2202881	PEI and subgrouping remaining issues	Nokia, Nokia Shanghai Bell
R2-2202882	Impact of subgrouping on other WGs	Nokia, Nokia Shanghai Bell
R2-2202993	Discussion on PEI and paging subgrouping	OPPO
R2-2203036	R2-22xxxxx Remaining issues on PEI	LG Electronics Inc
R2-2203229	Remaining issues on CN controlled subgrouping	Huawei, HiSilicon
R2-2203231	PEI with eDRX	Huawei, HiSilicon
R2-2203243	Considerations on PEI without Subgrouping Configuration	ZTE Corporation,Sanechips
R2-2203244	Considerations on PEI and Subgrouping Information in Xn and NG interface	ZTE Corporation,Sanechips
R2-2203245	Considerations on Open Issues of PEI and Subgrouping	ZTE Corporation,Sanechips
R2-2203252	PEI and paging subgrouping	Ericsson
R2-2203292	(OI 1.4) Considerations on support of PEI with eDRX	Interdigital, Inc.
R2-2203305	Remaining issue on PEI mobility	Intel Corporation
R2-2203474	Handling of gNB not supporting CN-assigned subgrouping	Futurewei Technologies
R2-2203478	On supporting PEI with eDRX	Futurewei Technologies
R2-2203720	Summary of 8.9.3.2.1 PEI and Paging Subgrouping	MediaTek Inc.
R2-2204240	LS out on PEI and UE Subgrouping	RAN2

8.9.3.2.2: PDCCH Skip

TDoc	Title	Source
R2-2202287	PDCCH Skipping in RRC_CONNECTED	Samsung Electronics Co., Ltd
R2-2202311	Discussion on PDCCH Skipping in RRC_CONNECTED	vivo
R2-2202883	UL PUSCH transmission impact on PDCCH skipping	Nokia, Nokia Shanghai Bell
R2-2202994	Discussion on PDCCH skipping	OPPO
R2-2203230	PDCCH skipping while UL reTx timer is running	Huawei, HiSilicon
R2-2203253	DCI-based power saving adaptation during DRX Active Time	Ericsson
R2-2203708	[Pre117-e][024][ePowSav] Summary of AI 8.9.3.2.2 PDCCH Skip (Samsung)	Samsung Electronics Co., Ltd
R2-2203896	Report of [AT117-e][024][ePowSav] PDCCH skip (Samsung)	Samsung

8.9.4: UE capabilities

TDoc	Title	Source
R2-2202355	Discussing on remaining issues of UE capability for paging enhancement	Xiaomi Communications

8.9.5: Other

TDoc	Title	Source
R2-2202312	Discussion on TRS availability when SI change	vivo
R2-2202354	Discussion on remaining issues on UE power saving	Xiaomi Communications
R2-2202779	Further considerations on UE assistance information	CMCC
R2-2202995	Discussion on PEI indication determination in RRC INACTIVE	OPPO
R2-2203068	TRS/CSI-RS configuration in RRC_CONNECTED	DENSO CORPORATION
R2-2203254	TRS exposure	Ericsson

8.10.1.1: LS in

TDoc	Title	Source
R2-2202131	Reply LS on LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access (R3-220121/S2-2109337) (R3-221370; contact: Qualcomm)	RAN3
R2-2202132	LS on RAN Initiated Release due to out-of-PLMN area condition (R3-221379; contact: Qualcomm)	RAN3
R2-2203829	LS Response to LS on UE location during initial access in NTN (S2-2201540; contact: Qualcomm)	SA2
R2-2203932	LS on Reply LS on UE location aspects in NTN (S2-2201834; contact: Huawei)	SA2
R2-2203956	Reply LS on UE Location Aspects in NTN (S2-2201539; contact: Ericsson)	SA2
R2-2204069	LS on introducing the list of PLMNs not allowed to operate at the present UE location (C1-222096; contact: CMCC)	CT1
R2-2204070	NR satellite RAT type in UE NAS (C1-222098; contact: Ericsson)	CT1
R2-2204075	LS on NR-NTN TP for TS 38.300 (R1-2202838; contact: Thales)	RAN1
R2-2204129	Reply LS on NTN-specific SIB (R1-2202843; contact: Huawei)	RAN1
R2-2204131	Reply LS to RAN2 on NR NTN Neighbour Cell and Satellite Information (R1-2202873; contact: Thales)	RAN1
R2-2204187	Reply LS on UE location during initial access in NTN (R3-222861; contact: Thales	RAN3

8.10.1.2: CRs

TDoc	Title	Source
R2-2202233	Stg2 running CR - NTN	THALES
R2-2202234	NTN RAN3's stg2 BL CR	THALES
R2-2202456	Draft 331 CR for NR NTN UE capabilities	Intel Corporation
R2-2202457	Draft 306 CR for NR NTN UE capabilities	Intel Corporation
R2-2203157	Introduction of Release-17 NTN	Ericsson
R2-2203385	Introduction of NTN	ZTE corporation,Sanechips
R2-2203425	Stage 3 NTN running CR for 38.321 - RAN2#117	InterDigital
R2-2203537	Introduction of NTN	Thales
R2-2203547	Introduction of Release-17 support for Non-Terrestrial Networks (NTN)	InterDigital
R2-2203548	Stage-3 running 304 CR for NTN	ZTE Corporation,Sanechips
R2-2203549	Introduction of Release-17 NTN	Ericsson
R2-2203550	Draft 331 CR for NR NTN UE capabilities	Intel Corporation
R2-2203551	Draft 306 CR for NR NTN UE capabilities	Intel Corporation
R2-2203552	Summary of [AT117-e][109][NTN] Stage 2 CR (Thales)	Thales
R2-2203618	Introduction of Release-17 support for Non-Terrestrial Networks (NTN)	InterDigital
R2-2204038	Support of Non-Terrestrial Networks	Thales
R2-2204111	[POST117-e][101][NTN] RRC CR (Ericsson)	Ericsson
R2-2204112	Introduction of Release-17 NTN	Ericsson
R2-2204244	Report of [POST117-e] [102] [NTN] 38.304 CR (ZTE)	ZTE corporation
R2-2204259	Introduction of NTN	ZTE Corporation, Sanechips
R2-2204262	Support of Non-Terrestrial Networks	Thales

8.10.2.1.1: Open issues

TDoc	Title	Source
R2-2202302	Discussion on MAC open issues	Huawei, HiSilicon
R2-2202420	Remaining issues on HARQ process in NTN	Spreadtrum Communications
R2-2202546	UL synchronization and validity timer expiry	Apple
R2-2202547	UE location and TA reporting	Apple
R2-2202563	UL synchronization failure in RRC_CONNECTED	Qualcomm Incorporated
R2-2202613	Considerations on MAC open issues	CMCC
R2-2202773	Remaining MAC Open Issues for NR NTN	vivo
R2-2202972	Consideration on MAC open issues	ZTE Corporation, Sanechips
R2-2202999	Discussion on MAC open issues in NTN	OPPO
R2-2203076	Discussion on Left Open Issues of Other MAC Aspects	CATT
R2-2203151	Discussion on TA reporting	ITL
R2-2203165	Discussion on open issues for MAC aspects	LG Electronics Inc.
R2-2203194	Remaining MAC issues of NR NTN	Xiaomi
R2-2203256	On left open issues for MAC aspects	Nokia, Nokia Shanghai Bell
R2-2203257	Discussion on Validity timer expiry and restart	Nokia, Nokia Shanghai Bell
R2-2203298	Open issues on MAC aspects	Samsung Research America
R2-2203423	Remaining MAC open issues in NTN	InterDigital
R2-2203424	Summary of [Pre117-e][NTN][103] MAC open issues	InterDigital
R2-2203482	Remaining MAC issues in NTNs	Ericsson
R2-2203532	Report of [AT117-e][103][NTN] MAC open issues	InterDigital
R2-2203542	Report of [AT117-e][103][NTN] MAC open issues - second round	InterDigital
R2-2203567	Report of [AT117-e][103][NTN] MAC open issues - third round	InterDigital

8.10.2.1.2: Other RACH aspects

TDoc	Title	Source
R2-2202303	Discussion on remaining MAC issues	Huawei, HiSilicon

8.10.2.1.3: Other MAC aspects

TDoc	Title	Source
R2-2202421	MAC operation about the validity timer expiry	Spreadtrum Communications
R2-2203203	CG enhancements in NTN	Sony

8.10.2.2: RLC and PDCP aspects

TDoc	Title	Source
R2-2203481	Remaining issues for RLC and PDCP in NTNs	Ericsson

8.10.3.1.1: Open issues

TDoc	Title	Source
R2-2202235	WF for UE location during initial access in NTN	THALES, Leonardo, Avanti, ESA, Sateliot, Omnispace, Novamint, Hispasat, Gatehouse, Hughes network systems, Inmarsat, Viasat, CTTC, Intelsat, Kepler, Ligado, Magister solutions, SES, Airbus
R2-2202394	On reporting of UE location information	ZTE corporation, Sanechips
R2-2202422	Discussion on the SIBX acquiring procedure	Spreadtrum Communications
R2-2202423	Acquiring the ephemeris of neighbour cell	Spreadtrum Communications
R2-2202466	Remaining Rel-17 NTN open issues for IDLE mode	Nokia, Nokia Shanghai Bell
R2-2202548	NTN-TN idle mode mobility	Apple
R2-2203049	Measurements and cell reselection	Samsung Research America
R2-2203386	Report of [Pre117-e][102][NTN] Idle mode open issues (ZTE)	ZTE corporation,Sanechips
R2-2203533	Report of [AT117-e][102][NTN] Idle mode open issues	ZTE corporation,Sanechips
R2-2203543	Report of [AT117-e][102][NTN] Idle mode open issues - second round	ZTE corporation,Sanechips
R2-2203566	Report of [AT117-e][102][NTN] Idle mode open issues - third round	ZTE corporation,Sanechips
R2-2203569	WF for UE location during initial access in NTN	Thales, Leonardo, Avanti, ESA, Sateliot\t, Omnispace, Novamint, Hispasat, Gatehouse, Hughes network systems, Inmarsat, Viasat, CTTC, Intelsat, Kepler, Ligado, Magister solutions, SES, Airbus
R2-2203570	Summary of [AT117-e][115][NTN] UE location in connected mode (Thales)	Thales
R2-2204032	Report of [AT117-e][102][NTN] Idle mode open issues � Final Round	ZTE corporation
R2-2204113	LS on UE location in connected mode in NTN	RAN2
R2-2204257	LS on UE location in connected mode in NTN	RAN2

8.10.3.1.2: Other

TDoc	Title	Source
R2-2202566	Assistance information for IDLE mode measurements	Qualcomm Incorporated
R2-2202586	Epoch time and validity time for neighbour satellite ephemeris	Lenovo, Motorola Mobility
R2-2202774	Remaining issues on location-based cell reselection	vivo
R2-2203004	Discussion on measurement rules for cell re-selection in NTN	OPPO
R2-2203725	Discussion on measurement rules for cell re-selection in NTN	OPPO

8.10.3.2.1: Open issues

TDoc	Title	Source
R2-2202424	Discussion on SIB X	Spreadtrum Communications
R2-2202467	Remaining Rel-17 NTN open issues for CONNECTED mode	Nokia, Nokia Shanghai Bell
R2-2202565	Open issues in CHO	Qualcomm Incorporated
R2-2202587	Consideration on open issues for CHO	Lenovo, Motorola Mobility
R2-2202775	Open issues on CHO for R17 NR NTN	vivo
R2-2202886	Remaining issues on CHO	Huawei, HiSilicon
R2-2203005	Discussion on the RRC open issues in NTN	OPPO
R2-2203051	Remaining NTN CHO issues	LG Electronics France
R2-2203067	Discussion on RRC open issues for NTN	Xiaomi Communications
R2-2203077	Further Discussion on the Open Issues of CHO	CATT
R2-2203153	Remaining connected mode aspects for NTN	Ericsson
R2-2203154	[Pre117-e][NTN][101] RRC open issues	Ericsson
R2-2203236	Remaining open issues of CHO	NEC Telecom MODUS Ltd.
R2-2203301	Open issues on RRC aspects	Samsung Research America
R2-2203422	Remaining RRC open issues in NTN	InterDigital
R2-2203534	[AT117-e][101][NTN] RRC open issues (Ericsson)	Ericsson
R2-2203536	Report from [AT117-e][108][NTN] CHO open issues (Nokia)	Nokia, Nokia Shanghai Bell
R2-2203544	[AT117-e][101][NTN] RRC open issues (Ericsson) - second round	Ericsson
R2-2203545	Report from [AT117-e][108][NTN] CHO open issues (Nokia) - second round	Nokia, Nokia Shanghai Bell
R2-2203565	[AT117-e][101][NTN] RRC open issues (Ericsson) - third round	Ericsson
R2-2204031	[AT117-e][101][NTN] RRC open issues (Ericsson)	Ericsson

8.10.3.2.2: Other

TDoc	Title	Source
R2-2202455	Discussion on NR NTN measurement gaps	Intel Corporation
R2-2202564	SMTC and MG configuration	Qualcomm Incorporated
R2-2202588	Contents of UE assistance for measurement window and gap configuration in NTN	Lenovo, Motorola Mobility
R2-2202614	Further discussion on intra-NTN mobility	CMCC
R2-2202776	Discussion on the signaling design for NTN specific information	vivo
R2-2202840	Network-Based SMTC Configuration in NTN	Google Inc.
R2-2202850	Discussion on assistance information for SMTC	ASUSTeK
R2-2202853	Measurement Gap Issues in NTN	Google Inc.
R2-2203006	Discussion on remaining open issues in connected mode	OPPO
R2-2203066	Further consideration of initial access	Samsung Research America
R2-2203190	Location report for TA report and LCS support in connected mode	Xiaomi
R2-2203191	Remaining issues relating to SIBxx and the RRC delay for RRC Release	Xiaomi
R2-2204033	[offline-116] Measurement gaps	Intel
R2-2204114	LS on measurement gaps enhancements for NTN	RAN2

8.10.4: UE capabilities

TDoc	Title	Source
R2-2203485	NR NTN UE capabilities	Ericsson

8.10.4.1: Open issues

TDoc	Title	Source
R2-2202454	Report of email discussion [Pre117-e][104][NTN] UE caps open issues (Intel)	Intel Corporation
R2-2202725	Remaining Issues of Set2 on NR NTN UE Capabilities	CMCC
R2-2203535	Report of email discussion [AT117-e][104][NTN] UE caps open issues (Intel)	Intel Corporation
R2-2203546	Report of email discussion [AT117-e][104][NTN] UE caps open issues (Intel) - second round	Intel Corporation
R2-2203568	Report of email discussion [AT117-e][104][NTN] UE caps open issues (Intel) - third round	Intel Corporation

8.10.4.2: Other

TDoc	Title	Source
R2-2202459	Discussion on the difference between GSO and GEO	Intel Corporation
R2-2202887	Discussion on capabilities for gaps and HARQ	Huawei, HiSilicon

8.11.1: Organizational

TDoc	Title	Source
R2-2202164	LS on SRS for multi-RTT positioning (R4-2202680; contact: Huawei)	RAN4
R2-2202165	Reply LS on reporting of the Tx TEG association information (R4-2202685; contact: Huawei)	RAN4
R2-2202166	LS on DRX cycle used in PRS measurement in RRC_INACTIVE state (R4-2202686; contact: Qualcomm)	RAN4
R2-2202169	Reply LS on reporting and definition of DL PRS path RSRP (R4-2202780; contact: Nokia)	RAN4
R2-2202405	Introduction of B2a and B3I signal in BDS system and GNSS Positioning Integrity	CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi.
R2-2202488	Open issues list on Rel-17 positioning WI	Intel Corporation
R2-2202489	Open issues on stage 2 running CR	Intel Corporation
R2-2202490	Running 38.305 CR for Positioning WI on RAT dependent positioning methods	Intel Corporation
R2-2202491	Introduction of R17 Positioning Enhancements	Intel Corporation, CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi
R2-2202492	Report of [Pre117-e][614][POS] Issues requiring RAN1 input (Intel)	Intel Corporation
R2-2202493	Draft LS on issues requiring RAN1 input	Intel Corporation
R2-2202605	Introduction of R17 PositioningEnh in MAC spec	Huawei, HiSilicon
R2-2202606	Introduction of R17 PositioningEnh in LTE RRC spec	Huawei, HiSilicon
R2-2202861	Running CR of 36.305 for GNSS Positioning Integrity	InterDigital, Inc.
R2-2202862	Running CR of 38.305 for GNSS Positioning Integrity	InterDigital, Inc.
R2-2203310	Running LPP CR for NR positioning enhancements	Qualcomm Incorporated
R2-2203315	Introduction of R17 Positioning Enhancements in LPP	Qualcomm Incorporated, CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi
R2-2203362	RAN1 parameter list impact to RRC running CR	Ericsson
R2-2203363	Report on RAN1 parameter list impact to RRC running CR	Ericsson
R2-2203364	Introduction of Enhanced Positioning feature	Ericsson
R2-2203597	LS to RAN1 on positioning issues needing further input	RAN2
R2-2203602	Introduction of Enhanced Positioning feature	Ericsson
R2-2203603	Running CR of 36.305 for GNSS Positioning Integrity	InterDigital, Inc.
R2-2203604	Running CR of 38.305 for GNSS Positioning Integrity	InterDigital, Inc.
R2-2203605	Running 38.305 CR for Positioning WI on RAT dependent positioning methods	Intel Corporation
R2-2203606	[AT117-e][603][POS] Integrity stage 2 CRs (InterDigital)	InterDigital, Inc.
R2-2203616	Introduction of R17 PositioningEnh in MAC spec	Huawei, HiSilicon
R2-2203617	Introduction of R17 PositioningEnh in LTE RRC spec	Huawei, HiSilicon
R2-2203619	Running LPP CR for NR positioning enhancements	Qualcomm Incorporated
R2-2203620	Summary of [AT117-e][606][POS] LPP running CR (Qualcomm)	Qualcomm Incorporated
R2-2203625	Introduction of R17 PositioningEnh in LTE RRC spec	Huawei, HiSilicon
R2-2203717	Draft LS to RAN1 on positioning issues needing further input	Intel Corporation
R2-2203739	Reply LS on positioning issues needing further input (R1-2202849; contact: CATT)	RAN1
R2-2203743	Reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance (R1-2202912; contact: CATT)	RAN1
R2-2203744	LS on multiple measurement instances (R1-2202922; contact: CATT)	RAN1
R2-2203887	Reply LS on the applicability of PRS processing window in RRC_INACTIVE state (R1-2202619; contact: CATT)	RAN1
R2-2203888	Reply LS on SRS for multi-RTT positioning (R1-2202659; contact: Huawei)	RAN1
R2-2203920	[AT117-e][607][POS] Positioning running CR to 38.331 (Ericsson)	Ericsson
R2-2203921	RAN1 parameter list impact to RRC running CR	Ericsson
R2-2203950	Summary of [AT117-e][606][POS] LPP running CR (Qualcomm)	Qualcomm Incorporated
R2-2203957	Response LS on determination of location estimates in local co-ordinates (S2-2201545; contact: Ericsson)	SA2
R2-2204022	Introduction of Enhanced Positioning feature	Ericsson
R2-2204023	[AT117-e][607][POS] Positioning running CR to 38.331 (Ericsson)	Ericsson
R2-2204025	Report of [AT117-e][632][POS] Merged CR to 38.305 (Intel)	Intel Corporation
R2-2204026	Introduction of R17 positioningEnh for MAC spec	Huawei, HiSilicon
R2-2204096	Report of [AT117-e][633][POS] Merged CR to 36.305 (CATT)	CATT
R2-2204097	Introduction of B2a and B3I signal in BDS system and GNSS Positioning Integrity	CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi
R2-2204119	LS on frequency information of SRS for positioning resources (R1-2202847; contact: CATT)	RAN1
R2-2204138	LS on lower Rx beam sweeping factor for latency improvement (R4-2206980; contact: Intel)	RAN4
R2-2204139	LS on the UE/TRP TEG framework (R4-2206998; contact: CATT)	RAN4
R2-2204182	Questions concerning the implementation of RAN1 agreements in NRPPa (R3-222721; contact: Ericsson)	RAN3
R2-2204199	Reply LS on latency improvement for PRS measurement with MG (R4-2207088; contact: Huawei)	RAN4
R2-2204242	Introduction of Enhanced Positioning feature	Ericsson

8.11.2: Open issues

TDoc	Title	Source
R2-2204024	Report of [AT117-e][605][POS] Capability running CRs (Intel)	Intel Corporation

8.11.2.1: Latency enhancements

TDoc	Title	Source
R2-2202408	Discussion and TP on areaID for Latency enhancements	CATT
R2-2202487	On Latency Reduction open issues	Intel Corporation
R2-2202592	On remaining issues for latency improvements	Apple
R2-2202603	Remaining issues on latency and accuracy enhacnement	Huawei, HiSilicon
R2-2202604	Summary of [Pre117-e][607][POS] Open issues on positioning latency enhancements (Huawei)	Huawei, HiSilicon
R2-2202858	Remaining Issues on Latency Reduction	InterDigital, Inc.
R2-2202922	MAC CE for pre-MG (de)activation request	Samsung
R2-2202930	Remaining issue on positioning latency reduction	Xiaomi
R2-2203042	Way forward for preconfigured assistance data	Fraunhofer IIS; Fraunhofer HHI; Ericsson;
R2-2203088	Discussion on latency enhancement	vivo
R2-2203181	Discussion on open issues of positioning latency enhancements	ZTE
R2-2203204	Considerations on positioning measurement report latency	Sony
R2-2203211	Discussion of positioning latency enhancement open issues	OPPO
R2-2203360	TP on RRC Impacts and MAC CE design	Ericsson
R2-2203592	Summary of AI 8.11.2.1	Apple (moderator)
R2-2203596	Summary of AI 8.11.2.1	Apple (moderator)
R2-2203622	[AT117-e][628][POS] Remaining proposals from latency reduction summary (Apple)	Apple

8.11.2.2: RRC_INACTIVE

TDoc	Title	Source
R2-2202338	Discussion on remaining issues for Positioning in RRC_INACTIVE state	OPPO
R2-2202601	Remaining Issues on RRC_INACTIVE Positioning	Huawei, HiSilicon
R2-2202602	Draft LS on Positioning in RRC_INACTIVE State	Huawei, HiSilicon
R2-2203089	Discussion on positioning in RRC_INACTIVE	vivo
R2-2203091	Consideration on the configuration of UL positioning in RRC_INACTIVE	CATT
R2-2203180	Discussion on UL positioning configuration in RRC_INACTIVE	ZTE
R2-2203443	Remaining issues for positioning of UEs in RRC_INACTIVE State	Qualcomm Incorporated
R2-2203444	[draft] LS on Positioning in RRC_INACTIVE State	Qualcomm Incorporated
R2-2203445	Capturing RRC impacts for RAT dependent Positioning	Ericsson
R2-2203524	Email discussion report on [Pre117-e][609][POS] Open issues on positioning in RRC_INACTIVE (InterDigital)	InterDigital
R2-2203607	Email discussion Report on [AT117-e][630][POS] Remaining proposals on RRC_INACTIVE (InterDigital)	InterDigital Inc.
R2-2203922	Capturing RRC impacts for RAT dependent Positioning	Ericsson
R2-2203948	Summary of [AT117-e][629][POS] LS to SA2 on RRC_INACTIVE positioning (Qualcomm)	Qualcomm Incorporated
R2-2203949	LS on Positioning in RRC_INACTIVE State	RAN2

8.11.2.3: On-demand PRS

TDoc	Title	Source
R2-2202236	Report of [Pre117-e][608][POS] Open issues on on-demand PRS	Lenovo, Motorola Mobility
R2-2202337	Discussion on remaining issues for on-demand DL-PRS	OPPO
R2-2202409	Discussion on the remaining issues of on-demand PRS	CATT
R2-2202859	Remaining Issues for On-demand PRS	InterDigital, Inc.
R2-2203169	Remaining issues for the On demand DL PRS	Samsung R&D Institute UK
R2-2203463	On-demand PRS Open Issues	Nokia, Nokia Shanghai Bell
R2-2203601	Report on [AT117-e][631][POS] Remaining OD-PRS issues (Lenovo)	Lenovo, Motorola Mobility

8.11.2.4: GNSS positioning integrity

TDoc	Title	Source
R2-2203034	UE-aided detection of threat to GNSS systems and assistance data signaling	Fraunhofer IIS; Fraunhofer HHI; Ericsson; ESA
R2-2203090	Discussion on GNSS positioning integrity	vivo
R2-2203199	Reporting of GNSS Positioning Integrity Result	Nokia, Nokia Shanghai Bell
R2-2203359	On remaining GNSS Integrity open issues	Ericsson
R2-2203525	Summary of [Pre117-e][610][POS] Open issues GNSS integrity (ESA)	ESA
R2-2203593	[AT117-e][623][POS] Early discussion of integrity issues (ESA)	ESA

8.11.2.5: A-GNSS enhancements

TDoc	Title	Source
R2-2202402	Introduction of B2a and B3I signal in BDS system in A-GNSS	CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi.
R2-2202403	Introduction of B2a and B3I signal in BDS system in A-GNSS	CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi.
R2-2202404	Introduction of B2a and B3I signal in BDS system in A-GNSS	CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi.
R2-2202607	Draft running CR for stage2 spec for NAVIC in R17 positioning	Huawei, HiSilicon
R2-2203608	[AT117-e][602][POS] NavIC running CRs (Ericsson/Huawei)	Ericsson
R2-2203609	Introduction of B2a and B3I signal in BDS system in A-GNSS	CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi.
R2-2203610	Introduction of B2a and B3I signal in BDS system in A-GNSS	CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi.
R2-2203611	Introduction of B2a and B3I signal in BDS system in A-GNSS	CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, HiSilicon, Intel Corporation, ZTE Corporation, CBN, vivo, OPPO, Lenovo, MediaTek Inc, Spreadtrum Communications, Xiaomi.
R2-2203612	Report of [AT117-e][601][POS] BDS running CRs (CATT)	CATT
R2-2203615	Draft running CR for stage2 spec for NAVIC in R17 positioning	Huawei, HiSilicon
R2-2203710	Introduction of NavIC for broadcast support	Ericsson

8.11.2.6: Accuracy enhancements

TDoc	Title	Source
R2-2202410	Report of [Pre117-e][611][POS] Open issues on positioning accuracy enhancements (CATT)	CATT
R2-2202593	On UE Tx TEG association for UL-TDOA via RRC	Apple
R2-2202860	Remaining Issues for Accuracy Enhancements	InterDigital, Inc.
R2-2203205	Considerations on Timing Error aspects	Sony
R2-2203361	LPP Remaining Issues on Accuracy enhancements and On-Demand PRS	Ericsson
R2-2203462	Timing Error Group (TEG) definition	Nokia, Nokia Shanghai Bell
R2-2203621	Report of [AT117-e][618][POS] Beam and antenna information for DL-AoD accuracy enhancements (CATT)	CATT

8.11.2.7: UE capabilities

TDoc	Title	Source
R2-2202494	Report of [Pre117-e][612][POS] Open issues on positioning UE capabilities (Intel)	Intel Corporation
R2-2202495	Running 331 CR for Positioning UE capabilities	Intel Corporation
R2-2202496	Running 306 CR for Positioning UE capabilities	Intel Corporation
R2-2203623	Report of [AT117-e][605][POS] Capability running CRs (Intel)	Intel Corporation
R2-2203624	Running 331 CR for Positioning UE capabilities	Intel Corporation
R2-2203626	Running 306 CR for Positioning UE capabilities	Intel Corporation
R2-2203630	Running 331 CR for Positioning UE capabilities	Intel Corporation
R2-2203941	Running 306 CR for Positioning UE capabilities	Intel Corporation

8.12.1.1: LS in

TDoc	Title	Source
R2-2202134	LS reply on the coordination between gNBs supporting RedCap UEs (R3-221396; contact: Ericsson)	RAN3
R2-2202162	Reply LS on use of NCD-SSB for RedCap UE (R4-2202674; contact: ZTE)	RAN4
R2-2202163	LS on RRM relaxation for Redcap (R4-2202675; contact: vivo)	RAN4
R2-2202313	[Draft] Reply LS to RAN4 on RRM relaxation	vivo
R2-2203555	Reply LS to RAN4 on RRM relaxation	RAN2
R2-2203741	LS on operation with and without SSB for RedCap UE (R1-2202886; contact: Ericsson)	RAN1
R2-2204136	LS on configuring margin for 1 Rx RedCap UEs (R4-2206951; contact: Ericsson)	RAN4
R2-2204137	Reply LS on UE capabilities for RedCap from RRM perspective (R4-2206977; contact: Ericsson)	RAN4
R2-2204147	LS on NCD-SSB issues for RedCap UE (R4-2207104; contact: Ericsson)	RAN4
R2-2204148	LS on RRM relaxation for Redcap (R4-2207109; contact: vivo)	RAN4
R2-2204193	LS on FR2 RedCap UE (R4-2206545; contact: Ericsson)	RAN4

8.12.1.2: CRs

TDoc	Title	Source
R2-2202314	Introduction of RedCap in TS 38.321	vivo (Rapporteur)
R2-2202498	Updated Running 38.306 CR for the RedCap capablities	Intel Corporation
R2-2202499	Updated Running 38.331 CR for the RedCap capablities	Intel Corporation
R2-2202500	Running 38.306 CR for the RedCap capablities	Intel Corporation
R2-2202501	Running 38.331 CR for the RedCap capablities	Intel Corporation
R2-2203354	Introduction of RedCap	Ericsson
R2-2203421	Introduction of RedCap in TS 38.300	Nokia, Nokia Shanghai Bell
R2-2203473	Stage 2 Corrections for RedCap	Futurewei Technologies
R2-2203497	Introduction of RedCap UEs	Ericsson
R2-2203541	Introduction of RedCap in TS 38.300	Nokia, Nokia Shanghai Bell
R2-2203556	Introduction of RedCap in TS 38.321	vivo (Rapporteur)
R2-2203557	Introduction of RedCap	Ericsson
R2-2203558	Introduction of RedCap	Ericsson
R2-2203559	Running 38.306 CR for the RedCap capablities	Intel Corporation
R2-2203560	Updated Running 38.331 CR for the RedCap capablities	Intel Corporation
R2-2204039	Introduction of RedCap in TS 38.300	Nokia, Nokia Shanghai Bell
R2-2204040	Running 38.306 CR for the RedCap capablities	Intel Corporation
R2-2204256	Introduction of RedCap - with SUL	Ericsson
R2-2204267	Introduction of RedCap	Ericsson
R2-2204268	Introduction of RedCap - with SUL	Ericsson

8.12.2.1.1: Open issues

TDoc	Title	Source
R2-2202266	Details on RRM relaxation	Ericsson
R2-2202315	Discussion on RAN4 LS and remaining issues on RRM relaxation	vivo, Guangdong Genius
R2-2202989	UE behavior on combineRelaxedMeasCondition2	Samsung
R2-2202996	Left open issue on SI change mechanism for eDRX	OPPO
R2-2203350	On RedCap RRM relaxations in IDLE/INACTIVE	Nokia, Nokia Shanghai Bell
R2-2203562	Report of [AT117-e][113][RedCap] RRM relaxation (vivo)	vivo

8.12.2.1.2: Other

TDoc	Title	Source
R2-2202347	Cell (re)selection parameters of RedCap UE	Fujitsu
R2-2202937	Cell selection criterion for a RedCap UE with 1 Rx branch	Samsung
R2-2203352	eDRX and system information	Nokia, Nokia Shanghai Bell

8.12.2.2.1: Open issues

TDoc	Title	Source
R2-2202316	Discussion on remaining issues on RRC aspects for RedCap	vivo, Guangdong Genius
R2-2202529	NCD-SSB and handover related aspects	Apple
R2-2202530	On the EUTRA handover to NR for RedCap UEs	Apple
R2-2202654	On inter-RAT handover for RedCap UEs	ZTE Corporation, Sanechips
R2-2202677	RRC open issues on Rel17 RedCap WI	Intel Corporation
R2-2202997	Discussion on remaining RRC open issues	OPPO
R2-2203055	Inter-RAT mobility from LTE to NR	Huawei, HiSilicon
R2-2203056	Access restriction of RedCap UE	Huawei, HiSilicon
R2-2203140	Further discussion on NCD-SSB for RedCap UE	China Telecommunications
R2-2203355	Handover from E-UTRA from legacy eNB to legacy gNB	Ericsson
R2-2203502	Report for [Pre117-e][105][RedCap] CP open issues	Ericsson
R2-2203538	Email discussion report for [AT117-e][105][RedCap] CP open issues	Ericsson
R2-2203561	Email discussion report for [AT117-e][105][RedCap] CP open issues - second round	Ericsson
R2-2203564	Email discussion report for [AT117-e][114][RedCap] Inter-RAT HO (Apple)	Apple Inc.
R2-2203712	Inter-RAT mobility from LTE to NR	Huawei, HiSilicon, BT Plc, CATT, Sequans
R2-2204035	Email discussion report for [AT117-e][105][RedCap] CP open issues - final round	Ericsson
R2-2204115	LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times	RAN2

8.12.2.2.2: Other

TDoc	Title	Source
R2-2202289	SI Request for Redcap UEs	Samsung Electronics Co., Ltd
R2-2202734	Discussions on Redcap-specific initial BWPs	Xiaomi Communications
R2-2203030	System information acquisition by RedCap UEs during handover	Qualcomm Incorporated
R2-2203351	On RRM relaxations in CONNECTED	Nokia, Nokia Shanghai Bell

8.12.3.1.1: Open issues

TDoc	Title	Source
R2-2202317	Report of [Pre117-e][106][RedCap] MAC open issues (vivo)	vivo
R2-2203281	Early identification capability	Nokia, Nokia Shanghai Bell
R2-2203539	Report of [AT117-e][106][RedCap] MAC open issues (vivo)	vivo

8.12.4: NCD-SSB aspects

TDoc	Title	Source
R2-2202318	Discussion on RAN2 impacts on NCD-SSB and separate initial BWP	vivo, Guangdong Genius
R2-2202653	Remaining issues on separate initial BWP and NCD-SSB for RedCap UEs	ZTE Corporation, Sanechips
R2-2202998	Left open issues on NCD-SSB	OPPO
R2-2203057	Discussion on NCD-SSB aspects for RedCap UE	Huawei, HiSilicon
R2-2203078	Discussion on the open issues of NCD-SSB	CATT
R2-2203505	Monitoring POs in connected mode when using NCD-SSB	Ericsson
R2-2203508	C-plane related open issues on NCD-SSB	DENSO CORPORATION

8.12.5.1: Open issues

TDoc	Title	Source
R2-2202497	Report of [Pre117-e][107][RedCap] UE caps open issues (Intel)	Intel Corporation
R2-2203141	Further discussion on RRM relaxation for RedCap UE	China Telecommunications
R2-2203142	Further discussion on RRM relaxation for RedCap UE	China Telecommunications
R2-2203143	Further discussion on RRM relaxation for RedCap UE	China Telecommunications
R2-2203540	Report of [Pre117-e][107][RedCap] UE caps open issues (Intel)	Intel Corporation
R2-2203563	Report of [Pre117-e][107][RedCap] UE caps open issues (Intel)	Intel Corporation

8.13.1: Organizational

TDoc	Title	Source
R2-2202116	LS on UP measurements for Successful Handover Report (R3-212935; contact: Ericsson)	RAN3
R2-2202117	Reply LS on UE context keeping in the source cell (R3-212944; contact: Ericsson)	RAN3
R2-2202118	LS Reply on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (R3-214429; contact: Ericsson)	RAN3
R2-2202120	Reply LS on scenarios need to be supported for MRO in SCG Failure Report (R3-216159; contact: Samsung)	RAN3
R2-2202125	Reply LS on Area scope configuration and Frequency band info in MDT configuration (R3-221178; contact: Huawei)	RAN3
R2-2202133	Reply LS to SA5 on beam measurement reports (R3-221383; contact Ericsson)	RAN3
R2-2202177	Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-213499; contact: Ericsson)	SA5
R2-2202178	Reply LS on Report Amount for M4, M5, M6, M7 measurements (S5-214523; contact: Nokia)	SA5
R2-2202179	Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-215493; contact: Ericsson)	SA5
R2-2202180	Reply LS on the Beam measurement reports for the MDT measurements (S5-216628; contact: Ericsson)	SA5
R2-2203029	Draft Reply LS on Area scope configuration and Frequency band info in MDT configuration	Huawei, HiSilicon
R2-2203468	Reply LS on user plane measurements in successful handover report	Ericsson
R2-2204189	Reply LS on MDT M6 calculation for split bearers in MR-DC (R3-222868; contact: Ericsson)	RAN3

8.13.2: CRs and Rapporteur Resolutions

TDoc	Title	Source
R2-2202706	Running 38.314 CR for R17 layer 2 measurements	CMCC
R2-2203025	NR RRC CR for introducing R17 MDT	Huawei, HiSilicon
R2-2203394	Introduction of Rel-17 MDT enhancements	Nokia, Nokia Shanghai Bell
R2-2203470	Enhancement of data collection for SON	Ericsson
R2-2204205	NR RRC CR for introducing R17 MDT	Huawei, HiSilicon
R2-2204209	Introducing Enhancement of Data Collection for SON and MDT	Ericsson, Huawei, HiSilicon
R2-2204237	Introduction of Rel-17 MDT enhancements	Nokia, Nokia Shanghai Bell

8.13.3: SON related Open Issues

TDoc	Title	Source
R2-2202570	SON Enhancements for CHO	Lenovo, Motorola Mobility
R2-2202571	SON Enhancements for SHR	Lenovo, Motorola Mobility
R2-2203010	Open issues on SHR	NEC
R2-2203210	Discussion on SON HO left issues	OPPO
R2-2203895	[AT117e][888][SON/MDT] SON related Open Issues (Ericsson)	Ericsson
R2-2203989	[AT117e][888][SON/MDT] SON related Open Issues (Ericsson) - Phase 2	Ericsson

8.13.3.1: Pre-discussions

TDoc	Title	Source
R2-2203526	SON related open issue list (Ericsson)	Ericsson
R2-2203754	SON related open issue list (Ericsson)	Ericsson

8.13.3.2: Invited Input

TDoc	Title	Source
R2-2202591	MRO-related remaining open issues	Apple
R2-2202730	Leftovers for consecutive CHO failures	CMCC, CATT
R2-2202731	Leftovers for SHR	CMCC
R2-2202732	Leftovers for MRO for SN	CMCC
R2-2202778	Discussion on SON related open issues	LG Electronics
R2-2202801	Discussion on SON Related Open Issues	CATT
R2-2202802	Discussion on Open Issue in Stage-2 Running CR	CATT
R2-2202971	Discussion on SHR enhancements	vivo
R2-2202973	Consideration on SON open issues	ZTE Corporation, Sanechips
R2-2203014	Discussion on SHR related open issues	Huawei, HiSilicon
R2-2203015	Discussion on SgNB MRO related open issues	Huawei, HiSilicon
R2-2203395	Detailed information required for MRO for SN change failure	Nokia, Nokia Shanghai Bell
R2-2203397	SHR and RLF report generation for same handover	Nokia, Nokia Shanghai Bell
R2-2203420	HO related SON changes	Qualcomm Incorporated
R2-2203464	Handover-related SON aspects	Ericsson
R2-2203465	On PSCell MHI and SCG MRO enhancements	Ericsson

8.13.4: MDT related Open Issues

TDoc	Title	Source
R2-2203900	Report of [AT117e][899][SON/MDT] MDT related Open Issues (Huawei)	Huawei

8.13.4.1: Pre-discussions

TDoc	Title	Source
R2-2203026	Pre-meeting discussion report for R17 MDT	Huawei
R2-2204063	LS on logged MDT configuration at SN in DC scenario	RAN2

8.13.4.2: Invited Input

TDoc	Title	Source
R2-2202733	Leftovers for on-demand SI	CMCC, Ericsson, Samsung, CATT, ZTE, Huawei
R2-2202803	Discussion on MDT Related Open Issues	CATT
R2-2202974	Consideration on MDT open issues	ZTE Corporation, Sanechips
R2-2203027	Discussion on MDT related open issues	Huawei, HiSilicon
R2-2203329	Discussion on logged MDT open issues	Ericsson
R2-2203331	On Immediate MDT measurements	Ericsson, CMCC
R2-2203396	Early measurements logging in MDT	Nokia, Nokia Shanghai Bell

8.13.5: UE Capabilities

TDoc	Title	Source
R2-2202804	UE Capabilities about SON and MDT Enhanced Features	CATT
R2-2202975	Consideration on UE capability	ZTE Corporation, Sanechips
R2-2203028	Discussion on UE capabilities for R17 SON and MDT	Huawei, HiSilicon
R2-2203427	SON MDT UE Capabilities	Qualcomm Incorporated
R2-2203831	Report of [AT117e][877][SONMDT] SONMDT related UE Capabilities(CATT, Intel)	CATT, Intel
R2-2203832	38.306 CR for SONMDT UE capabilities	CATT, Intel
R2-2203833	38.331 CR for SONMDT UE capabilities	CATT, Intel
R2-2204089	38.306 CR for SONMDT UE capabilities	CATT, Intel
R2-2204090	38.331 CR for SONMDT UE capabilities	CATT, Intel

8.13.6: Others

TDoc	Title	Source
R2-2202939	Discussion on PSCell MHI recording	SHARP Corporation
R2-2202940	Discussion on SHR in CHO recovery case	SHARP Corporation

8.14.1.2: LS in

TDoc	Title	Source
R2-2202128	LS on QoE Measurement Session Start and Measurement Session End Indication from the UE (R3-221243; contact: Ericsson)	RAN3
R2-2202137	LS on RAN3 agreement for management based QoE mobility (R3-221427; contact: ZTE)	RAN3
R2-2202138	LS on Support for Configuration and Reporting of RAN Visible QoE Measurements (R3-221463; contact: Ericsson)	RAN3
R2-2202139	LS on Support for Configuration and Reporting of RAN Visible QoE Measurements (R3-221464; contact: Ericsson)	RAN3
R2-2202140	LS on Support for Configuration and Reporting of RAN Visible QoE Measurements (R3-221465; contact: Ericsson)	RAN3
R2-2203846	LS Reply on SA4 requirements for QoE (S4-220236; contact: Huawei)	SA4
R2-2203847	LS Reply on maximum container size for QoE configuration and report (S4-220237; contact: Huawei)	SA4
R2-2203848	LS Reply on RAN visible QoE (S4-220239; contact: Huawei)	SA4
R2-2203849	LS Reply on QoE configuration and reporting related issues (S4-220309; contact: Huawei)	SA4
R2-2204068	LS on the specification of AT commands for NR QoE (C1-222058; contact: Ericsson)	CT1
R2-2204106	Report of [AT117-e][068][QoE] LS in and LS out (Huawei)	Huawei
R2-2204191	LS on RAN3 agreements for NR QoE (R3-222890; contact: China Unicom)	RAN3
R2-2204202	LS on RAN2 agreements on NR QoE	RAN2
R2-2204203	LS on UE capabilities for NR QoE	RAN2
R2-2204204	Reply LS on RAN3 agreements on NR QoE	RAN2

8.14.1.3: CRs and Rapporteur Resolutions

TDoc	Title	Source
R2-2202623	Running CR of UE capability for NR QoE	CMCC
R2-2202871	38.300 running CR for Introduction of QoE measurements in NR	China Unicom, Huawei, HiSilicon
R2-2203428	Introduction of QoE measurements	Ericsson
R2-2203770	Introduction of QoE measurements	Ericsson
R2-2204127	38.300 CR for Introduction of QoE measurements in NR	China Unicom, Huawei, HiSilicon
R2-2204218	Introduction of QoE measurements in NR	Ericsson

8.14.3.1: Pre-discussions

TDoc	Title	Source
R2-2202878	Summary of [Pre117-e][008][QoE] QoE Open Issues Input	China Unicom

8.14.3.2: Invited Input

TDoc	Title	Source
R2-2202622	Remaining open issue relating QoE	CMCC
R2-2202828	Discussion on Pause/Resume QoE Reporting Mobility	ZTE Corporation, Sanechips
R2-2202829	Discussion on RAN Visible QoE Mobility	ZTE Corporation, Sanechips
R2-2202857	Left issues of QoE mobility	Qualcomm Incorporated
R2-2202863	Discussion on Remaining Open Issues	CATT
R2-2202935	Support of MDT and QoE alignment	Qualcomm Incorporated
R2-2202986	Pause and resume under mobility	Samsung
R2-2202987	RAN visible QoE under mobility	Samsung
R2-2203038	R2-22xxxxx Remaining open issues on QoE	LG Electronics Inc
R2-2203136	Discussion on pause and resume of QoE reporting during HO and RRC resume	vivo
R2-2203137	Discussion on RAN visible QoE mobility	vivo
R2-2203209	Discussion on QoE measurement collection configuration in NR	OPPO
R2-2203346	Discussion on open issues for QoE measurement configuration and reporting	Huawei, HiSilicon
R2-2203348	RAN visible QoE during mobility	Huawei, HiSilicon
R2-2203398	QMC/MDT alignment and paused QoE handling in HO	Nokia, Nokia Shanghai Bell
R2-2203430	RAN Visible QoE measurements	Ericsson
R2-2203431	Handling of paused QoE and RVQoE reports during HO and RRC resume	Ericsson
R2-2203915	Feature summary for 8.14.3.2	Ericsson

8.14.4: UE capabilities

TDoc	Title	Source
R2-2202827	Discussion on UE Capability for QoE	ZTE Corporation, Sanechips
R2-2202865	Discussion on UE capabilities for NR QoE	CATT
R2-2202906	Open issues for QoE capability	Qualcomm Incorporated
R2-2202988	Capabilities of AS layer and application layer	Samsung
R2-2203208	Discussion on QoE measurement collection capability	OPPO
R2-2203347	AS and application layer interactions for NR QoE UE capabilities	Huawei, HiSilicon
R2-2203404	UE Capabilities for QMC	Nokia, Nokia Shanghai Bell
R2-2203429	UE capabilities for QoE measurements	Ericsson
R2-2203924	Report of [AT117-e][047][QoE] UE capability (CMCC)	CMCC
R2-2203925	Running 38.306 CR of UE capability for NR QoE	CMCC
R2-2203926	Running 38.331 CR of UE capability for NR QoE	CMCC

8.14.5: Other

TDoc	Title	Source
R2-2202551	Start/stop indication in NR QoE	Apple

8.15.1: Organizational

TDoc	Title	Source
R2-2202204	Introduction of sidelink DRX capability	OPPO
R2-2202205	Introduction of sidelink DRX capability	OPPO
R2-2202391	Introduction of sidelink DRX capability	OPPO
R2-2202474	Rapporteur Inputs on Stage 2 Open Issues	InterDigital (Rapporteur)
R2-2202478	Introduction of eSL in TS.38300	InterDigital (Rapporteur)
R2-2202712	RRC running CR for NR Sidelink enhancements	Huawei, HiSilicon
R2-2202948	Running CR of TS 38.321 for Sidelink enhancement	LG Electronics France
R2-2203671	Introduction of eSL in TS 38.300	InterDigital
R2-2203672	RRC CR for NR Sidelink enhancement	Huawei, HiSilicon (Rapporteur)
R2-2203673	CR of TS 38.321 for Sidelink enhancement	LG Electronics Inc.
R2-2203674	Introduction of NR Sidelink enhancements	ZTE Corporation, Sanechips
R2-2203675	Introduction of sidelink DRX capability	OPPO
R2-2203676	Introduction of sidelink DRX capability	OPPO
R2-2203677	Introduction of sidelink DRX capability	OPPO
R2-2203688	TP to introduce R17 sidelink DRX for TR 37.985	Huawei, HiSilicon
R2-2203689	LS on TP to introduce Rel-17 SL DRX for TR 37.985	RAN2
R2-2203952	TP to introduce R17 sidelink DRX for TR 37.985	Huawei, HiSilicon

8.15.2: SL DRX

TDoc	Title	Source
R2-2202190	Discussion on DRX left issues	OPPO
R2-2202203	Summary of [POST116bis-e][705][V2X/SL] Open issues on SL DRX (OPPO)	OPPO
R2-2202388	Leftover Issue for Sidelink DRX	CATT
R2-2202430	Remaining aspects of SL DRX	Ericsson
R2-2202452	Discussion on SL DRX remaining issues for unicast	ZTE Corporation, Sanechips
R2-2202453	Discussion on TX profile issues for SL DRX	ZTE Corporation, Sanechips
R2-2202475	Consideration of the Active Time for Periodic Transmissions	InterDigital, Ericsson, vivo, Huawei, HiSilicon, Nokia, ASUSTek, Lenovo, Motorola Mobility, Samsung
R2-2202476	Resource Allocation for DRX	InterDigital
R2-2202540	Discussion on remaining issues on SL-DRX	Apple
R2-2202581	Remaining MAC issues for SL DRX	Lenovo, Motorola Mobility
R2-2202667	On SL DRX and candidate resource selection	Intel Corporation
R2-2202713	Remaining issue on sidelink DRX	Huawei, HiSilicon
R2-2202764	Consideration on the different DRX status among RX UEs in SL groupcast	Huawei, HiSilicon
R2-2202900	Draft-CR for NOTE-based approach for Q2.3.3-1b in [POST116bis-e][705]	OPPO
R2-2202901	Draft-CR for normative-text-based approach for Q2.3.3-1b in [POST116bis-e][705]	OPPO
R2-2202902	Draft-CR for NOTE-based approach for Q2.3.3-2b in [POST116bis-e][705]	OPPO
R2-2202903	Draft-CR for normative-text-based approach for Q2.3.3-2b in [POST116bis-e][705]	OPPO
R2-2202941	Discussion on remaining issues for SL DRX	LG Electronics France
R2-2202984	consideration on the remaining issues for SL DRX	LG Electronics France
R2-2203047	SL-DRX negotiation procedure in unicast	vivo
R2-2203048	Unsolved issues on SL-DRX	vivo
R2-2203082	Remaining issues for SL DRX	Samsung Research America
R2-2203147	Discussion on sidelink DRX open issues	Xiaomi
R2-2203152	Resource selection considering SL DRX	ITL
R2-2203182	SL DRX CP aspects	Lenovo, Motorola Mobility
R2-2203200	Handling of sidelink mode-1 grant drop due to misalignment with SL-DRX	Nokia, Nokia Shanghai Bell
R2-2203274	Down-selection for SL DRX configuration for GC/BC with multiple QoS profiles associated with the same L2 DST ID	Nokia, Nokia Shanghai Bell
R2-2203678	Draft-CR for normative-text-based approach for Q2.3.3-2b in [POST116bis-e][705]	OPPO
R2-2203679	Summary of 706	OPPO
R2-2203693	LS on Tx Profile	RAN2

8.15.3: Resource allocation enhancements RAN2 scope

TDoc	Title	Source
R2-2202191	Discussion on power saving resource allocation enhancement	OPPO
R2-2202192	Discussion on inter-UE coordination	OPPO
R2-2202387	IUC Request and Response MAC CE Design	CATT
R2-2202431	MAC CE design of inter-UE coordination	Ericsson
R2-2202432	Remaining issues for power saving resource allocation	Ericsson
R2-2202451	Discussion on Inter-UE coordination	ZTE Corporation
R2-2202477	On the Allowable Cast Types for IUC	InterDigital
R2-2202541	Discussion on Inter-UE Coordination	Apple
R2-2202542	Discussion on power saving resource selection	Apple
R2-2202582	Open issues on SL inter-UE coordination	Lenovo, Motorola Mobility
R2-2202668	Inter-UE coordination open issues	Intel Corporation
R2-2202823	Summary of [POST116bis-e][706][V2X/SL] Open issues on power-saving resource allocation, Phase 2	vivo (Rapporteur)
R2-2202866	Consideration on Inter-UE coordination	Huawei, HiSilicon
R2-2202942	Discussion on Inter-UE Coordination	LG Electronics France
R2-2203046	Latency bound and remaining PDB related to inter-UE coordination MAC CE not covered by open issue list	vivo
R2-2203083	Partial-sensing/random selection based resource allocation in SL DRX	Samsung Research America
R2-2203084	Introduction of IUC MAC CE	Samsung Research America
R2-2203159	Summary of [POST116bis-e][707][V2X/SL] Open issues on IUC (LG)	LG (Rapporteur)
R2-2203207	Whether UE-A in IUC can be in mode 1 or mode 2	Nokia, Nokia Shanghai Bell
R2-2203472	Discussion on Inter-UE Coordination	Qualcomm Finland RFFE Oy
R2-2203695	LS to RAN1 on the inter-UE coordination mechanism	RAN2
R2-2203696	TP for IUC-information MAC CE and IUC-Request MAC CE	OPPO
R2-2203697	Summary of [POST117-e][715][V2X/SL] TP for IUC INFO and IUC REQ MAC CE format (OPPO)	OPPO

8.16.1: Organizational

TDoc	Title	Source
R2-2202174	Reply to LS on support of PWS over SNPN (S1-214049; contact: Nokia)	SA1
R2-2202175	Reply LS on limited service availability of an SNPN (S2-2109254; contact: Qualcomm)	SA2
R2-2202636	Introduction of Rel-17 NPN UE capability	Intel Corporation
R2-2202689	Introduction of Enhancements for Private Networks	Qualcomm Incorporated
R2-2203072	Introducing NPN enhancements: Credential Holders, Onboarding, IMS emergency, and PWS support in SNPNs	Nokia, Nokia Shanghai Bell
R2-2203073	Introducing NPN enhancements: Credential Holders, Onboarding, and IMS emergency support in SNPNs	Nokia, Nokia Shanghai Bell
R2-2203074	RAN2 Work Plan for Enhancement for Private Network Support for NG-RAN	Nokia, China Telecom (Rapporteurs)
R2-2203589	Introducing NPN enhancements: Credential Holders, Onboarding, IMS emergency, and PWS support in SNPNs	Nokia, Nokia Shanghai Bell
R2-2203590	Introducing NPN enhancements: Credentials Holder, UE Onboarding, and IMS emergency support in SNPNs	Nokia, Nokia Shanghai Bell
R2-2203960	Introduction of UE capabilities for Rel-17 eNPN	Intel Corporation
R2-2204180	Introduction of Enhancements for Private Networks	Qualcomm Incorporated (Rapporteur)
R2-2204247	Introducing NPN enhancements: Credential Holders, Onboarding, IMS emergency, and PWS support in SNPNs	Nokia, Nokia Shanghai Bell

8.16.2: Issues and Corrections

TDoc	Title	Source
R2-2202208	Remaining Key Issues for eNPN	OPPO
R2-2202620	Discussion on open issues for NPN	CMCC
R2-2202832	Remaining issue of GIN design for eNPN	China Telecom
R2-2202855	Discussion on open issues in eNPN	Samsung R&D Institute India
R2-2202889	Discussion on GINs for SNPN	Huawei, HiSilicon
R2-2202896	Discussion on open issues for R17 NPN	vivo
R2-2202898	Consideration on the remaining eNPN issues	ZTE Corporation, Sanechips
R2-2203075	Remaining open issues of eNPN	Nokia, Nokia Shanghai Bell
R2-2203264	Resolving open issues for eNPN	LG Electronics France
R2-2203447	Remaining details for eNPN	Ericsson
R2-2203830	Report from [AT117-e][048][eNPN] Open Issues (Nokia)	Nokia (Rapporteur)

8.17.1: General

TDoc	Title	Source
R2-2203752	LS on further questions on feMIMO RRC parameters	Ericsson
R2-2203753	Report of [AT117-e][009][feMIMO] RRC 1 (Ericsson)	Ericsson
R2-2203762	LS on further questions on feMIMO RRC parameters	Ericsson
R2-2203876	LS on further questions on feMIMO RRC parameters	RAN2
R2-2204056	Summary of [AT117-e] [016] [feMIMO] MAC (Samsung)	Samsung

8.17.1.2: LS in

TDoc	Title	Source
R2-2203748	Additional LS response to RAN2 on beam management for multi-TRP (R1-2202942; contact: CATT)	RAN1
R2-2203893	LS on feMIMO RRC parameters (R1-2202720; contact: Ericsson)	RAN1
R2-2203894	LS on RRC parameters update for IE SSB-MTCAdditionalPCI-r17 (R1-2202725; contact: vivo)	RAN1
R2-2204011	LS response on MPE information signaling (R1-2202732; contact: Nokia)	RAN1
R2-2204044	Follow up LS on feMIMO RRC parameters (R1-2202765; contact: Ericsson)	RAN1
R2-2204076	LS on Rel-17 NR FeMIMO for TS 38.300 (R1-2202865; contact: Samsung)	RAN1
R2-2204117	Reply LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE (R1-2202810; contact: Intel)	RAN1
R2-2204120	LS on feMIMO RRC parameters (R1-2202903; contact: Ericsson)	RAN1

8.17.1.3: CRs and Rapporteur Resolutions

TDoc	Title	Source
R2-2202926	Introduction of feMIMO	Samsung
R2-2203032	Introduction of Release-17 feMIMO	Ericsson
R2-2203033	FeMIMO L1 parameters with RAN2 notes Rel-17 NR	Ericsson Limited
R2-2203035	RRC CR rapporteur open issue document	Ericsson
R2-2203809	Introduction of Release-17 feMIMO	Ericsson
R2-2204220	Introduction of feMIMO	Samsung
R2-2204221	Introduction of feMIMO	Samsung

8.17.3.1: Pre-discussions

TDoc	Title	Source
R2-2203050	[Pre117-e][009][feMIMO] feMIMO Open Issues Input (Ericsson)	Ericsson

8.17.4.1: RRC and General

TDoc	Title	Source
R2-2202230	Discussion on unified TCI framework	TCL Communication Ltd.
R2-2202231	Discussion on unified TCI framework	TCL Communication Ltd.
R2-2202319	Discussion on RRC aspects for feMIMO	vivo
R2-2202348	Systerm Information provisioning for inter-cell beam management	Fujitsu
R2-2202447	Discussion on FeMIMO open issues	OPPO
R2-2202669	Remaining issues on RRC parameters	Intel Corporation
R2-2202927	PUCCH power control for mTRP FR1	Samsung
R2-2203041	FeMIMO RRC impact	Ericsson
R2-2203043	Per BWP configuration of SFN scheme	Ericsson
R2-2203102	Discussions on the remaining RRC issues of feMIMO	CATT
R2-2203103	Considerations on Inter-cell Beam Management	CATT
R2-2203126	Clarification on the serving cell measurement for mTRP	Xiaomi Communications
R2-2203263	Signaling support for UL power control for BM	LG Electronics France
R2-2203381	FeMIMO RRC issues	Huawei, HiSilicon
R2-2203719	Summary of 8.17.4.1 RRC and General (Intel)	Intel Corporation

8.17.4.2: MAC

TDoc	Title	Source
R2-2202288	Multi TRP Beam Failure Detection and Recovery	Samsung Electronics Co., Ltd
R2-2202320	Discussion on remaining issues on MAC aspects for feMIMO	vivo
R2-2202349	Remaining issues on beam failure with mTRP	Fujitsu
R2-2202448	MAC CE design for FeMIMO	OPPO
R2-2202557	MAC impacts of FeMIMO	Apple
R2-2202572	BFR for both SpCell and SCell in mTRP	Lenovo, Motorola Mobility
R2-2202670	Remaining issues on MAC CEs	Intel Corporation
R2-2202772	MAC CE Design for Unified TCI States Activation Deactivation	MediaTek Inc.
R2-2202851	Discussion on Power Headroom Reporting for mTRP PUSCH repetition	ASUSTeK
R2-2202852	Discussion on MAC CE design regarding separate and joint TCI state	ASUSTeK
R2-2202928	Discussions on PHR enhancements for mTRP PUSCH repetition	Samsung
R2-2202957	Remaining issues on multi-TRP BFR	Qualcomm Incorporated
R2-2202958	Remaining issues on MAC and MIMO MAC CEs	Qualcomm Incorporated
R2-2203044	MAC CE impacts	Ericsson
R2-2203093	Remaining issues on MAC	LG Electronics Inc.
R2-2203104	Discussions on the remaining open Issues of 38.321 Running CR	CATT
R2-2203246	Consideration on Implementation of BFR for mTRP	ZTE Corporation,Sanechips
R2-2203247	Further Considerations On New PHR and PHR MAC CE	ZTE Corporation,Sanechips
R2-2203248	Consideration on the unified TCI State MAC CE for ICBM	ZTE Corporation,Sanechips
R2-2203269	PHR reporting for FeMIMO	Nokia, Nokia Shanghai Bell
R2-2203282	Beam failure with mTRP	Nokia, Nokia Shanghai Bell
R2-2203382	FeMIMO MAC open issues	Huawei, HiSilicon
R2-2203383	SP-SRS resource set activation by MAC CE	Huawei, HiSilicon
R2-2203426	Discussion on Multi-TRP PHR enhancements	InterDigital
R2-2203709	[Pre117] [016] [feMIMO] Summary of 8.17.4.2 MAC (Samsung)	Samsung

8.18.1: Common signalling framework

TDoc	Title	Source
R2-2202558	Signaling aspects of RACH partitioning	Apple
R2-2202693	Remaining issues for signaling design for RACH partitioning	CATT
R2-2203063	Discussion on RO sharing cases for common RACH configuration	LG Electronics Inc.
R2-2203339	Common signalling for RACH indication and partitioning	Huawei, HiSilicon
R2-2203356	RSRP Thresholds for RACH Partitioning	Ericsson
R2-2203357	Report of [POST116bis-e][515][RA Part] CP open issues	Ericsson
R2-2203358	Introduction of common RACH partitioning aspects in RRC	Ericsson (rapporteur)
R2-2203393	Further Discussion on RACH Partitioning in RA Configuration Aspect	vivo
R2-2203405	Slice-specific RACH prioritization in Common RACH Framework	Nokia, Nokia Shanghai Bell
R2-2203701	Report of [POST116bis-e][515][RA Part] CP open issues	Ericsson
R2-2203735	Report of: [AT117-e][505][RA Part] CP additional open issues	Huawei, HiSilicon
R2-2204241	Introduction of Common RACH Partitioning Aspects	Ericsson

8.18.2: Common aspects of RACH procedure

TDoc	Title	Source
R2-2202694	Remaining issues for common aspects of RACH procedure	CATT
R2-2202976	Discussion on RACH partition UP open issues	OPPO
R2-2203206	RNTI collision issue for different features in NR	Sony
R2-2203283	Common aspects for RACH partitioning	Nokia, Nokia Shanghai Bell
R2-2203307	Introduction of common RACH partitioning aspects in MAC	ZTE Corporation (rapporteur)
R2-2203309	[POST116bis-e][514][RA Part] - Open issue list summary	ZTE Corporation (rapporteur)
R2-2203340	Further details of RACH procedure with RACH partitioning	Huawei, HiSilicon
R2-2203459	Remaining issues for RACH partitioning	InterDigital
R2-2203736	Report of [AT117-e][506] [RA Part] UP additional open issues (Intel)	Intel Corporation
R2-2203769	Introduction of common RACH partitioning aspects in MAC	ZTE Corporation (rapporteur)

8.19.1.1: LS in

TDoc	Title	Source
R2-2202153	Reply LS on Maximum duration for DMRS bundling (R4-2202368; contact: Qualcomm)	RAN4
R2-2203996	Reply LS on Maximum duration for DMRS bundling (R4-2206537; contact: Qualcomm)	RAN4
R2-2204118	Reply LS on UL BWP with PRACH resources only for RACH with Msg3 repetition (R1-2202829; contact: ZTE)	RAN1
R2-2204130	Reply LS on Stage 2 description for Coverage Enhancements (R1-2202867; contact: China Telecom)	RAN1
R2-2204196	Reply LS on Length of Maximum duration (R4-2206580; contact: China Telecom)	RAN4

8.19.1.2: CRs

TDoc	Title	Source
R2-2202652	TS 38.321 CR for Rel-17 Coverage enhancement	ZTE Corporation, Sanechips
R2-2202831	TS 38.300 CR for Rel-17 NR coverage enhancements	China Telecom
R2-2203127	Introduction of NR coverage enhancements in RRC	Huawei, HiSilicon
R2-2203553	TS 38.321 CR for NR coverage enhancements	ZTE Corporation
R2-2203554	Introduction of NR coverage enhancements in RRC	Huawei, HiSilicon
R2-2204036	Introduction of NR coverage enhancements	China Telecom
R2-2204037	Introduction of NR coverage enhancements in RRC	Huawei, HiSilicon

8.19.2: General

TDoc	Title	Source
R2-2202695	Remaining issues for Msg3 repetition	CATT
R2-2202981	Discussion on CFRA PUSCH with Repetition	vivo
R2-2203007	Minor connection to the stage-2 running CR	OPPO
R2-2203031	Discussion on Msg3 repetition for CFRA	Qualcomm Incorporated
R2-2203128	On measurement gap handling for Msg3 repetitions	Huawei, HiSilicon
R2-2203168	Further issues on msg3 repetitions	Ericsson
R2-2203284	BWP with only CR-RACH resources	Nokia, Nokia Shanghai Bell
R2-2204034	[AT117-e][111][CovEnh] MAC CR (ZTE)	ZTE Corporation

8.20.1: Organizational

TDoc	Title	Source
R2-2202435	Running RRC CR for 71 GHz	Ericsson
R2-2202479	[Post116bis-e][204][71 GHz] Open issues for 71 GHz (Qualcomm)	Qualcomm Incorporated
R2-2202688	Introduction of Extending NR operation to 71GHz	Qualcomm Incorporated
R2-2203644	Extending NR operation to 71 GHz	Ericsson
R2-2203645	Introduction of Extending NR operation to 71GHz	LG Electronics
R2-2203652	Introduction of NR operation up to 71GHz	Qualcomm Incorporated (Rapporteur)
R2-2203786	Summary of offline [211][71 GHz] RRC CR finalization for 71 GHz (Ericsson)	Ericsson
R2-2203953	CR to 36306 on UE capabilities for the support of NR 71GHz	Apple Inc
R2-2203954	UE capabilities for the support of NR 71GHz	Apple Inc
R2-2204087	UE capabilities for the support of NR 71GHz	Apple Inc
R2-2204126	Extending NR operation to 71 GHz	Ericsson

8.20.2: General

TDoc	Title	Source
R2-2202433	Remaining protocol aspects	Ericsson
R2-2202434	Remaining RRC aspects	Ericsson
R2-2202710	Discussion about RAN2 impacts of Ext 52-71GHz	Huawei, HiSilicon
R2-2202920	Remaining issues on UAI enhancement	Samsung
R2-2203079	Discussion on necessary update of Rel-16 LBT procedures	CATT
R2-2203418	CP open issues for RRC CR Extending NR operation to 71GHz	ZTE Corporation, Sanechips
R2-2203419	Remaining UP issues for extending to 71GHz	ZTE Corporation, Sanechips
R2-2203643	Report of [AT117-e][212][71 GHz] Protocol aspects of 71 GHz (QC)	Qualcomm

8.20.3: UE capabilities

TDoc	Title	Source
R2-2202659	CR to 38306 on UE capabilities for 71G	Intel Corporation
R2-2202660	CR to 38331 on UE capabilities for 71G	Intel Corporation
R2-2202661	Remaining UE capability issues on NR operation for upto 71GHz	Intel Corporation
R2-2202711	Discussion about UE capabilities on Ext 52-71GHz	Huawei, HiSilicon
R2-2202921	Discussion on L2 buffer size	Samsung
R2-2203646	CR to 38306 on UE capabilities for 71G	Intel Corporation
R2-2203647	CR to 38331 on UE capabilities for 71G	Intel Corporation
R2-2203711	Summary report of [Pre117-e][210][71G] UE capabilities	Intel Corporation
R2-2203799	CR to 38306 on UE capabilities for 71G	Intel Corporation
R2-2203800	CR to 38331 on UE capabilities for 71G	Intel Corporation

8.21.0: In-principle agreed CRs

TDoc	Title	Source
R2-2202225	Discussion on UE capability signaling of inactiveStatePO-Determination-r17 in LTE	Lenovo, Motorola Mobility
R2-2202395	Correction on PO determination in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2202396	Correction on PO determination in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2202397	Correction on PO determination in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2202398	Correction on PO determination in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2202399	Correction on PO determination in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2202400	Correction on PO determination in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2202608	Introduction of RACH triggers for T_ADV in NR E-CID [NRTADV]	Huawei, HiSilicon, Ericsson, CATT, NTT DOCOMO, Deutsche Telekom, Polaris Wireless, ZTE Corporation
R2-2202626	Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN]	CMCC, CATT, Ericsson, Huawei, ZTE, Nokia, OPPO, vivo
R2-2202627	Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN]	CMCC, CATT, Ericsson, Huawei, ZTE, Nokia, OPPO, vivo
R2-2202628	Introduction of mobility-state-based cell reselection for NR HSDN	CMCC, CATT, Ericsson, Huawei, ZTE, Nokia, OPPO, vivo
R2-2202629	Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN]	CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo
R2-2203366	Addition of Timing Advance measurement reporting in NR E-CID [NRTADV]	Ericsson, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Huawei
R2-2203839	Report of [AT117-e][049][NR17TEI] In-principle Agreed CRs and related docs	ZTE corporation,Sanechips
R2-2203851	Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN]	CMCC, CATT, Ericsson, Huawei, ZTE, Nokia, OPPO, vivo
R2-2203907	Report of [AT117-e][049][NR17TEI] In-principle Agreed CRs and related docs	ZTE corporation,Sanechips
R2-2203908	Correction on PO determination for UE in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2203919	Addition of Timing Advance measurement reporting in NR E-CID [NRTADV]	Ericsson, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Huawei
R2-2203935	Introduction of RACH triggers for T_ADV in NR E-CID [NRTADV]	Huawei, HiSilicon, Ericsson, CATT, NTT DOCOMO, Deutsche Telekom, Polaris Wireless, ZTE Corporation
R2-2204048	Correction on PO determination for UE in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2204049	Correction on PO determination for UE in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2204050	Correction on PO determination for UE in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2204051	Correction on PO for UE determination in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips
R2-2204052	Correction on PO for UE determination in inactive state	ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Samsung, Nokia, Nokia Shanghai Bell, Sanechips

8.21.1: TEI proposals initiated by other groups

TDoc	Title	Source
R2-2202126	Reply on security protection of RRCResumeRequest message (R3-221183; contact: ZTE)	RAN3

8.21.2: TEI proposals initiated by RAN2

TDoc	Title	Source
R2-2202265	Secondary DRX enhancement	Ericsson, Verizon, Qualcomm Inc., T-Mobile USA Inc., Deutsche Telekom
R2-2202436	On inter-frequency measurement configuration and reporting enhancements	BT Plc., Ericsson, Vodafone, T-Mobile USA, Qualcomm
R2-2202505	Discussion on EPS fallback enhancement	Apple, ZTE
R2-2202521	SDAP end-marker in RLC UM	Apple, Futurewei, Spreadtrum, FGI, Asia Pacific Telecom, T-Mobile USA
R2-2202632	Discussion on remote access issue	CMCC
R2-2202704	Periodic SRS in SCell dormant BWP	Qualcomm Incorporated, ZTE Corporation, Futurewei
R2-2202788	Early measurement for EPS Fallback	vivo,CMCC, softbank, China Telecom,China Unicom
R2-2202789	38331 CR for Early measurement for EPS Fallback	vivo,CMCC, softbank, China Telecom,China Unicom
R2-2202790	38306 CR for Early measurement for EPS Fallback	vivo,CMCC, softbank, China Telecom,China Unicom
R2-2202791	Redirection enhancement on EPS Fallback	vivo
R2-2202792	38331 CR for Redirection enhancement on EPS Fallback	vivo
R2-2202793	38306 CR for Redirection enhancement on EPS Fallback	vivo
R2-2202818	EPS fallback enhancements in Rel-17	Huawei, HiSilicon, CMCC, China Telecom, China Unicom, LG Uplus
R2-2202992	Leaving indication for CHO execution	Qualcomm Incorporated
R2-2203250	Extension of the timeDomainAllocation for CG type 1 with typeB repetition	ZTE Corporation,Huawei, China Telecom, Sanechips
R2-2203251	Addition of UE capability of extension of TDRA indication for Configured UL Grant type 1	ZTE Corporation,Huawei, China Telecom, Sanechips
R2-2203365	Explicit Indication of SI Scheduling start position [SI-SCHEDULING]	Ericsson, Verizon, Softbank, Deutsche Telekom, vivo
R2-2203916	Explicit Indication of SI Scheduling start position [SI-SCHEDULING]	Ericsson, Verizon, Softbank, Deutsche Telekom, vivo
R2-2203917	Capability for Explicit Indication of SI Scheduling window position [SI-SCHEDULING]	Ericsson
R2-2203918	[AT117-e][050][NR17TEI] Explicit Indication of SI Scheduling start position (Ericsson)	Ericsson
R2-2203990	Report of [AT117-e][074][TEI17] EPS Fallback (Huawei)	Huawei
R2-2203993	Explicit Indication of SI Scheduling start position [SI-SCHEDULING]	Ericsson, Verizon, Softbank, Deutsche Telekom, vivo, Lenovo, Motorola Mobility
R2-2204001	Capability for Explicit Indication of SI Scheduling window position [SI-SCHEDULING]	Ericsson, Verizon, Softbank, Deutsche Telekom, vivo, Lenovo, Motorola Mobility
R2-2204236	LS on EPS fallback enhancements	RAN2

8.22.1.2: LS in

TDoc	Title	Source
R2-2202158	Further reply LS on R17 NR MG enhancements � Concurrent MG (R4-2202604; contact: MediaTek)	RAN4
R2-2202159	LS on R17 NR MG enhancements � Pre-configured MG (R4-2202615; contact: Intel)	RAN4
R2-2202160	Reply LS on R17 NR MG enhancements � Pre-configured MG (R4-2202616; contact: CATT)	RAN4
R2-2202161	LS on R17 MG enhancement - NCSG (R4-2202626; contact: Apple)	RAN4
R2-2203844	LS on collision handling of concurrent MGs (R4-2206788; contact: MediaTek)	RAN4
R2-2203845	LS on R17 NR MG enhancements � Pre-configured MG (R4-2206789; contact: Huawei & Intel)	RAN4
R2-2204135	LS on R17 MG enhancement - NCSG (R4-2206890; contact: Apple)	RAN4

8.22.1.3: CRs and Rapporteur Resolutions

TDoc	Title	Source
R2-2202868	Introduction of RRC signaling for measurement gap enhancement	MediaTek Inc.
R2-2202877	Rapporteur resolution for MGE open issues	MediaTek Inc.
R2-2203880	Report of [AT117-e][065][MGE] RRC (MediaTek)	MediaTek Inc.
R2-2203881	Introduction of RRC signaling for measurement gap enhancement	MediaTek Inc.
R2-2204179	Introduction of RRC signaling for measurement gap enhancement	MediaTek Inc.

8.22.3.1: Pre-discussions

TDoc	Title	Source
R2-2202899	Report of [Pre117-e][010][MGE] MGE Open Issues Input (MediaTek)	MediaTek Inc.

8.22.3.2.1: Pre-configured MG patterns

TDoc	Title	Source
R2-2202322	Discussion on per-configured measurement gap	vivo
R2-2202460	Discussion on support of case 4	Intel Corporation
R2-2202461	Support of pre-configured MG under CA	Intel Corporation
R2-2202513	RAN2 impact from pre-MG	Apple
R2-2202647	Remaining issues on Pre-configured MG	ZTE Corporation, Sanechips
R2-2202873	Discussion on open issue of pre-configured gap	MediaTek Inc.
R2-2202890	Discussion on Pre-configured MG	Huawei, HiSilicon
R2-2202944	Discussion on remaining issues of pre-configured MG	CATT
R2-2202977	Discussion on Pre-MG activation and deactivation	Samsung
R2-2203011	Discussion on the support of Pre-MG for CA	Samsung R&D Institute India
R2-2203037	R2-22xxxxx Remaining issues on Pre-configured MG	LG Electronics Inc
R2-2203060	Discussion on Pre-configured MG	Xiaomi Communications
R2-2203260	Discussion on open issues for pre-configured MG	Nokia, Nokia Shanghai Bell
R2-2203448	Pre-configured measurement gaps	Ericsson
R2-2203504	Pre-Configured gap case-4 discussion	Qualcomm Incorporated
R2-2203523	[Pre117-e][018][MGE] AI Summary of 8.22.3.2.1 Pre-configured MG patterns (Intel)	Intel Corporation
R2-2203757	[AT117-e][018][MGE] Pre-configured MG patterns (Intel)	Intel Corporation

8.22.3.2.2: Network Controlled Small Gap

TDoc	Title	Source
R2-2202323	Discussion on NCSG	vivo
R2-2202512	RAN2 impact from NCSG	Apple
R2-2202648	Remaining issues on NCSG	ZTE Corporation, Sanechips
R2-2202874	Discussion on open issue of NCSG	MediaTek Inc.
R2-2202891	Discussion on NCSG	Huawei, HiSilicon
R2-2202945	Discussion on remaining issues of NCSG	CATT
R2-2203012	On Network Controlled Small Gaps	Samsung
R2-2203261	Discussion on open issues for NCSG	Nokia, Nokia Shanghai Bell
R2-2203449	Network Controlled Small Gap	Ericsson
R2-2203503	SSB index derivation for NCSG	Qualcomm Incorporated
R2-2203713	[Pre117-e][019][MGE] AI summary of 8.22.3.2.2 Network Controlled Small Gap (Apple)	Apple
R2-2203904	Summary of [AT117-e][019][MGE] Network Controlled Small Gap (Apple)	Apple

8.22.4: UE capabilities

TDoc	Title	Source
R2-2202324	Discussion on capability for MG enhancement	vivo
R2-2202462	UE capability for NR and MR-DC measurement gap enhancements	Intel Corporation
R2-2202463	UE capability for NR and MR-DC measurement gap enhancements	Intel Corporation
R2-2202879	Discussion on UE capabilities of MGE	MediaTek Inc.
R2-2202892	Discussion on UE capability for MGE	Huawei, HiSilicon
R2-2203065	Discussion on UE capabilities for gap enhancement	Xiaomi Communications
R2-2203450	UE capabilities for MGE	Ericsson
R2-2203522	[Pre117-e][020][MGE] AI summary of 8.22.4 UE capabilities (Intel)	Intel Corporation
R2-2203758	[AT117-e][020][MGE] UE capabilites (Intel)	Intel Corporation
R2-2203759	UE capability for NR and MR-DC measurement gap enhancements	Intel Corporation
R2-2203760	UE capability for NR and MR-DC measurement gap enhancements	Intel Corporation

8.22.5: Other

TDoc	Title	Source
R2-2203262	Discussion on other open issues for MGE	Nokia, Nokia Shanghai Bell

8.23: Uplink Data Compression (UDC)

TDoc	Title	Source
R2-2204183	Reply LS on NR UDC for CU-CP/UP splitting scenario (R3-222724; contact: CATT)	RAN3

8.23.1: Organizational

TDoc	Title	Source
R2-2203107	Introduction of the support for UDC in NR	CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung, Apple, Nokia, Nokia Shanghai Bell
R2-2203108	Introduction of the support for UDC in NR	CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung, Apple, Nokia, Nokia Shanghai Bell
R2-2203109	Introduction of the support for UDC in NR	CATT, CMCC, Huawei, HiSilicon, MediaTek Inc., Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung, Apple, Nokia, Nokia Shanghai Bell
R2-2203110	Introduction of UE capabilities for NR UDC	CATT, CMCC, Huawei, HiSilicon, MediaTek Inc., Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung, Apple, Nokia, Nokia Shanghai Bell
R2-2203111	Introduction of the support for UDC in NR	CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, Samsung, Apple, Nokia, Nokia Shanghai Bell
R2-2203112	Introduction of UE capabilities for NR UDC	CATT, CMCC, Huawei, HiSilicon, MediaTek Inc., Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung, Apple, Nokia, Nokia Shanghai Bell
R2-2204094	Introduction of the support for UDC in NR	CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung, Apple, Nokia, Nokia Shanghai Bell
R2-2204095	Introduction of UE capabilities for NR UDC	CATT, CMCC, Huawei, HiSilicon, MediaTek Inc., Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung, Apple, Nokia, Nokia Shanghai Bell

8.23.2: General

TDoc	Title	Source
R2-2202367	Limit UL data rate for UDC in UE capability	MediaTek Inc., Samsung
R2-2202442	Consideration on NR UDC	OPPO
R2-2202520	UDC constraints and limitations	Apple
R2-2202678	Clarification on PDCP SDU for UDC continuity	Samsung Electronics
R2-2202961	Remaining issues on NR UDC	Qualcomm Incorporated
R2-2203023	Discussion on remaining issues for UDC	Huawei, HiSilicon
R2-2203106	Considerations on NR UDC open issues	CATT
R2-2203164	Discussion on UDC	LG Electronics Inc.
R2-2203249	Furhter Consideration on UDC in NR	ZTE Corporation,Sanechips
R2-2203838	Report of [AT117-e][051][UDC] Open Issues and CRs (CATT) � Phase 1	CATT
R2-2204116	Report of [AT117-e][051][UDC] Open Issues and CRs (CATT) � Phase 2	CATT

8.24.0: In-principle agreed CRs

TDoc	Title	Source
R2-2202151	Reply LS on NR CA capability for BCS5 (R4-2201295; contact: Xiaomi)	RAN4
R2-2202765	Introducing UE capability for power class 5 for FR2 FWA	SoftBank, Huawei, HiSilicon, Nokia
R2-2202766	Introducing UE capability for power class 5 for FR2 FWA	SoftBank, Huawei, HiSilicon, Nokia
R2-2203123	Introduction of BCS4 and BCS5	Xiaomi Communications
R2-2203124	Introduction of BCS4 and BCS5	Xiaomi Communications
R2-2203138	CR to TS 38.306 on UE capability for UE power class 2 NR inter-band CA and SUL configurations	China Telecom, Huawei, HiSilicon
R2-2203139	CR to TS 38.331 on UE capability for UE power class 2 NR inter-band CA and SUL configurations	China Telecom, Huawei, HiSilicon
R2-2203322	Introduction of DL 1024QAM for NR	Ericsson, Nokia, Nokia Shanghai Bell
R2-2203323	Introduction of DL 1024QAM for NR	Ericsson, Nokia, Nokia Shanghai Bell
R2-2203714	Remove the maximum number of MIMO layers restrictions for SUL	CMCC, Huawei, HiSilicon, CATT
R2-2203836	Introducing UE capability for power class 5 for FR2 FWA	SoftBank, Huawei, HiSilicon, Nokia
R2-2203864	Remove the maximum number of MIMO layers restrictions for SUL	CMCC, Huawei, HiSilicon, CATT
R2-2203897	Report of [AT117-e][052][NR17] IPA CRs (Xiaomi)	Xiaomi (Rapporteur)
R2-2203898	Introduction of BCS4 and BCS5	Xiaomi Communications
R2-2203899	Introduction of BCS4 and BCS5	Xiaomi Communications
R2-2203962	Introduction of DL 1024 QAM in NR	Ericsson, Nokia, Nokia Shanghai Bell
R2-2203963	Introduction of DL 1024 QAM in NR	Ericsson, Nokia, Nokia Shanghai Bell
R2-2203999	CR to TS 38.306 on UE capability for UE power class 2 NR inter-band CA and SUL configurations	China Telecom, Huawei, HiSilicon
R2-2204000	CR to TS 38.331 on UE capability for UE power class 2 NR inter-band CA and SUL configurations	China Telecom, Huawei, HiSilicon

8.24.1: RAN4 led Items

TDoc	Title	Source
R2-2202149	LS on interruption for PUCCH SCell activation in invalid TA case (R4-2120420; contact: MediaTek, CATT)	RAN4
R2-2202150	LS UE capability for supporting single DCI transmission schemes for multi-TRP (R4-2120652; contact: Apple)	RAN4
R2-2202152	LS on CORESET#0 impact of CBW narrower than 40MHz of n79 (R4-2202286; contact: Samsung)	RAN4
R2-2202155	Reply LS to RAN2 on UL gap in FR2 RF enhancement (R4-2202419; contact: Apple)	RAN4
R2-2202156	LS to RAN2 on UL gap in FR2 RF enhancement (R4-2202420; contact: Apple)	RAN4
R2-2202157	LS on signalling for inter-frequency measurement enhancement in connected state for FR1 HST (R4-2202591; contact: CMCC)	RAN4
R2-2202167	LS on network signaling for Rel-17 NR FR2 HST RRM (R4-2202765; contact: Nokia)	RAN4
R2-2202171	LS on signaling for FR1 HST CA demodulation (R4-2202984; contact: CMCC)	RAN4
R2-2202365	Introduction of CBM capability	Nokia, Nokia Shanghai Bell
R2-2202366	Introduction of CBM capability	Nokia, Nokia Shanghai Bell
R2-2202377	Reply LS on release independence aspects of newly introduced FR2 CA BW Classes and CBM/IBM UE capability	Nokia, Nokia Shanghai Bell
R2-2202389	Introduction of FR2 FBG2 CA BW classes	Nokia, Nokia Shanghai Bell
R2-2202390	Introduction of FR2 FBG2 CA BW classes	Nokia, Nokia Shanghai Bell
R2-2202449	CR to Clarification of PUCCH group definition	OPPO
R2-2202450	Discusson on concept of PUCCH group	OPPO
R2-2202506	RAN2 impact from FR2 UL gap	Apple
R2-2202507	Introduction of FR2 UL gap	Apple
R2-2202508	Introduction of FR2 UL gap	Apple
R2-2202509	Introduction of FR2 UL gap	Apple
R2-2202510	Introduction of FR2 UL gap UE capability	Apple
R2-2202511	Introduction of FR2 UL gap UE capability	Apple
R2-2202630	Introduction of RRM enhancements for Rel-17 NR FR1 HST	CMCC, Ericsson, Huawei, Nokia
R2-2202631	Introduction of RRM enhancements for Rel-17 NR FR1 HST	CMCC, Ericsson, Huawei, Nokia
R2-2202812	RRC configuration for UL Tx switching enhancement	Huawei, HiSilicon, China Telecom, Apple, CATT
R2-2202813	UE capability reporting for UL Tx switching enhancement	Huawei, HiSilicon, China Telecom, Apple, CATT
R2-2202814	stage 2 CR for UL Tx switching enhancement	Huawei, HiSilicon, China Telecom
R2-2202815	Summary of [AT116bis-e][033][NR17] (Huawei)	Huawei, HiSilicon
R2-2202816	[Draft] Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure	Huawei, HiSilicon
R2-2202817	Draft CR for Clarification of PUCCH group description	Huawei, HiSilicon
R2-2202867	On the signaling for RRM enhancements for Rel-17 FR2 HST	Huawei, HiSilicon
R2-2202869	Introduction of RRM enhancements for Rel-17 NR FR1 HST	CMCC, Ericsson, Huawei, Nokia, Qualcomm
R2-2202870	Introduction of RRM enhancements for Rel-17 NR FR1 HST	CMCC, Ericsson, Huawei, Nokia, Qualcomm
R2-2202884	PUCCH group definition	Nokia, Nokia Shanghai Bell
R2-2202904	Consideration on the FR2 CA bandwidth classes	ZTE Corporation, Sanechips
R2-2202905	Consideration on the CBM/IBM reporting	ZTE Corporation, Sanechips
R2-2202910	CR on the FR2 CA bandwidth classes-38331	ZTE Corporation, Sanechips
R2-2202911	CR on the FR2 CA bandwidth classes-38306	ZTE Corporation, Sanechips
R2-2202912	CR on the CBM/IBM reporting-38331	ZTE Corporation, Sanechips
R2-2202913	CR on the CBM/IBM reporting-38306	ZTE Corporation, Sanechips
R2-2202918	Introduction of FR2 UL gap	Apple R&D
R2-2203016	Discussion on interruption for PUCCH SCell activation in invalid TA case	CATT
R2-2203017	[Draft] Reply LS on interruption for PUCCH SCell activation in invalid TA case	CATT
R2-2203024	Discussion on FR2 new bandwidth class	Huawei, HiSilicon
R2-2203114	Introduction of Rel-17 Tx switching enhancements	China Telecom, Huawei, HiSilicon, Apple, CATT
R2-2203115	Draft CR to TS 38.306 on UL-MIMO coherence capability reporting for Rel-17 2Tx-2Tx switching	China Telecom, Huawei, HiSilicon
R2-2203116	Draft CR to TS 38.331 on UL-MIMO coherence capability reporting for Rel-17 2Tx-2Tx switching	China Telecom, Huawei, HiSilicon
R2-2203117	Discussion on remaining issues for UL Tx switching enhancement	China Telecom, Huawei, HiSilicon
R2-2203122	Introduction of new FR2 CA bandwidth classes	Xiaomi Communications
R2-2203134	Discussion on the DC location report for more than 2CC	Huawei, HiSilicon
R2-2203187	HST on FR2	Nokia, Nokia Shanghai Bell
R2-2203188	HST on FR2	Nokia, Nokia Shanghai Bell
R2-2203318	Clarification on PUCCH primary and secondary group definition	Ericsson
R2-2203319	Clarification on PUCCH primary and secondary group definition	Ericsson
R2-2203493	Introduction of new FR2 CA bandwidth classes	Huawei, HiSilicon
R2-2203494	Introduction of new FR2 CA bandwidth classes	Huawei, HiSilicon
R2-2203812	HST on FR2	Nokia, Nokia Shanghai Bell
R2-2203813	HST on FR2	Nokia, Nokia Shanghai Bell
R2-2203814	Capability signaling for HST on FR2	Nokia, Nokia Shanghai Bell
R2-2203834	Discussion on interruption for PUCCH SCell activation in invalid TA case	CATT
R2-2203835	Reply LS on interruption for PUCCH Scell activation in invalid TA case	RAN2
R2-2203852	Introduction of function for RRM enhancements for Rel-17 NR FR1 HST	CMCC, Ericsson, Huawei, Nokia, Qualcomm
R2-2203853	Introduction of RRM enhancements for Rel-17 NR FR1 HST	CMCC, Ericsson, Huawei, Nokia, Qualcomm
R2-2203854	Introduction of Rel-17 NR FR1 HST capability to 38.331	CMCC, Ericsson, Huawei, Nokia
R2-2203885	Reply LS on interruption for PUCCH SCell activation in invalid TA case (R1-2202599; contact: MediaTek)	RAN1
R2-2203903	Summary of [AT117-e][058][NR17] FR2 UL Gap (Apple)	Apple
R2-2203973	Offline [AT117-e][059][NR17] FR2 CA BW Classes and CBM (Nokia)	Nokia (Rapporteur)
R2-2203974	Introduction of FR2 FBG2 CA BW classes	Nokia, Nokia Shanghai Bell
R2-2203975	Introduction of FR2 FBG2 CA BW classes	Nokia, Nokia Shanghai Bell
R2-2203986	RRC configuration for R17 UL Tx switching enhancement	Huawei, HiSilicon, China Telecom, CATT
R2-2203987	Stage 2 CR for UL Tx switching enhancement	Huawei, HiSilicon, China Telecom
R2-2203988	UE capability reporting for UL Tx switching enhancement	Huawei, HiSilicon, China Telecom, Apple, CATT
R2-2203995	Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure (R1-2202778; contact: Huawei)	RAN1
R2-2203997	Summary of [AT117-e][053][NR17] UL TX Switching (China Telecom)	China Telecom
R2-2203998	Introduction of Rel-17 Tx switching enhancements	China Telecom, Huawei, HiSilicon, Apple, CATT
R2-2204005	CR on the CBM/IBM reporting-38331	ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2204006	CR on the CBM/IBM reporting-38306	ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2204105	Summary of [AT117-e][053][NR17] UL TX Switching (China Telecom)	China Telecom
R2-2204134	LS on release independent for FR1 HST RRM enhancement (R4-2206846; contact: CMCC)	RAN4
R2-2204149	LS on release independent for FR1 HST demodulation (R4-2207195; contact: CMCC)	RAN4
R2-2204150	LS on UE capability and network assistant signalling for CRS interference mitigation in scenarios with overlapping spectrum for LTE and NR (R4-2207238; contact: China Telecom)	RAN4
R2-2204192	LS on clarification of dualPA-Architecture capability (R4-2206503; contact: OPPO)	RAN4
R2-2204197	Reply LS on DC location for >2CC (R4-2206602; contact: Qualcomm)	RAN4
R2-2204198	LS to RAN2 on UL gap in FR2 RF enhancement (R4-2206608; contact: Apple)	RAN4
R2-2204229	Summary of [Post117-e][058][NR17] FR2 UL Gap (Apple)	Apple
R2-2204230	Introduction of FR2 UL gap for Rel-17	Apple
R2-2204231	Introduction of FR2 UL gap for Rel-17	Apple

8.24.2: RAN1 led Items

TDoc	Title	Source
R2-2202214	Plan for finalization of Rel-17 DSS in RAN2	Ericsson
R2-2202215	Introduction of NR dynamic spectrum sharing	Ericsson
R2-2202216	Introduction of NR dynamic spectrum sharing	Ericsson
R2-2203729	Summary of [AT117-e][060][NR17] DSS (Ericsson)	Ericsson
R2-2203842	Introduction of NR dynamic spectrum sharing	Ericsson
R2-2203843	Introduction of NR dynamic spectrum sharing	Ericsson

8.24.3: Other

TDoc	Title	Source
R2-2202176	Reply LS on LS on MINT functionality for Disaster Roaming (S3-214342; contact: LGE)	SA3
R2-2202183	Discussion on devices certified for a subset of a 3GPP band	Bell Mobility
R2-2202226	Further discussion on open issues for MINT	Lenovo, Motorola Mobility
R2-2202256	Introduction of MINT	Ericsson, Lenovo, Motorola Mobility
R2-2202257	Introduction of MINT	Ericsson, Lenovo, Motorola Mobility
R2-2202258	Introduction of MINT	Ericsson, Lenovo, Motorola Mobility
R2-2202259	Introduction of MINT	Ericsson, Lenovo, Motorola Mobility
R2-2202260	Introduction of MINT	Ericsson, Lenovo, Motorola Mobility
R2-2202261	Introduction of MINT	Ericsson, Lenovo, Motorola Mobility
R2-2202262	Introduction of MINT	Ericsson, Lenovo, Motorola Mobility
R2-2202263	Introduction of MINT	Ericsson, Lenovo, Motorola Mobility
R2-2202264	Remaining issues for MINT	Ericsson
R2-2203715	Remove the maximum number of MIMO layers configuration restrictions for SUL	CMCC, Huawei, HiSilicon, CATT
R2-2203726	Reply LS on MINT functionality for Disaster Roaming (S2-2201514; contact: LGE)	SA2
R2-2203850	Report of [AT117-e][061][NR17] n77 variants (Bell Mobility)	Bell Mobility (Rapporteur)
R2-2203865	Remove the maximum number of MIMO layers restrictions for SUL	CMCC, Huawei, HiSilicon, CATT
R2-2203866	Introduction of MINT [MINT]	Ericsson, Lenovo, Motorola Mobility
R2-2203867	Introduction of MINT [MINT]	Ericsson, Lenovo, Motorola Mobility
R2-2203868	Introduction of MINT [MINT]	Ericsson, Lenovo, Motorola Mobility
R2-2203869	Introduction of MINT [MINT]	Ericsson, Lenovo, Motorola Mobility
R2-2203870	Introduction of MINT [MINT]	Ericsson, Lenovo, Motorola Mobility
R2-2203871	Introduction of MINT [MINT]	Ericsson, Lenovo, Motorola Mobility
R2-2203872	Introduction of MINT [MINT]	Ericsson, Lenovo, Motorola Mobility
R2-2203873	Introduction of MINT [MINT]	Ericsson, Lenovo, Motorola Mobility
R2-2203874	Report [AT117-e][062][NR17] MINT (Ericsson)	Ericsson
R2-2204065	LS on UAC enhancements and system information extensions for minimization of service interruption (C1-221600; contact: Nokia)	CT1
R2-2204081	Reply LS on Reply LS on MINT functionality for Disaster Roaming (S3-220518; contact: LGE	SA3

9.0.2: Feature Lists and UE capabilities

TDoc	Title	Source
R2-2203745	LS on updated Rel-17 RAN1 UE features list for LTE (R1-2202924; contact: NTT DOCOMO)	RAN1

9.1.1: Organizational

TDoc	Title	Source
R2-2202124	LS on Coverage-Based Carrier Selection (R3-221162; contact: Nokia)	RAN3
R2-2202427	Introduction of NB-IoT/eMTC Enhancements	Qualcomm Incorporated
R2-2202743	36306 running CR for NB-IoT eMTC	ZTE Corporation, Sanechips
R2-2203216	Introduction of Rel-17 enhancements for NB-IoT and eMTC	Huawei, HiSilicon
R2-2203217	Introduction of Rel-17 enhancements for NB-IoT and eMTC	Huawei, HiSilicon
R2-2203576	Reply LS to RAN3 on coverage based carrier selection	RAN2
R2-2203577	Introduction of NB-IoT/eMTC Enhancements	Qualcomm Incorporated
R2-2203578	Introduction of additional enhancements for NB-IoT and eMTC	ZTE Corporation, Sanechips
R2-2203579	Introduction of Rel-17 enhancements for NB-IoT and eMTC	Huawei, HiSilicon
R2-2203580	Introduction of Rel-17 enhancements for NB-IoT and eMTC	Huawei, HiSilicon
R2-2203581	Introduction of Enhancements for NB-IoT/eMTC	Nokia
R2-2203582	Reply LS to RAN3 on coverage based carrier selection	RAN2
R2-2203583	Introduction of Rel-17 enhancements for NB-IoT and eMTC	Ericsson
R2-2203587	RAN2 agreements for Rel-17 NB-IoT and LTE-MTC	Document Rapporteur (Ericsson)
R2-2203740	LS on use of CQI table for NB-IoT DL 16QAM (R1-2202880; contact: Huawei)	RAN1
R2-2203742	LS on UE capability for 16QAM for NB-IoT (R1-2202893; contact: Qualcomm)	RAN1
R2-2203756	Introduction of Enhancements for NB-IoT/eMTC	Nokia
R2-2204255	Introduction of Enhancements for NB-IoT/eMTC	Nokia

9.1.2: Open Issues

TDoc	Title	Source
R2-2202739	Report of [Pre117e-301] Carrier selection open issues	ZTE Corporation, Sanechips
R2-2202745	ASN.1 issue and RAN3 impact of carrier selection	ZTE Corporation, Sanechips
R2-2203218	Report of [Pre117-e][302][NBIOT/eMTC R17] Capabilities open issues (Huawei)	Huawei, HiSilicon
R2-2203384	Report on [Pre117-e][303][NBIOTeMTC R17] Other open issues (Ericsson)	Ericsson
R2-2203575	Report of [AT117-e][301][NBIOT/eMTC R17] Carrier selection (ZTE)	ZTE (email discussion rapporteur)

9.2: NB-IoT and eMTC support for NTN

TDoc	Title	Source
R2-2203923	Report of [AT117-e][012][IOT-NTN] Control Plane (Huawei)	Huawei
R2-2203983	Report on[AT117-e][064][IoT-NTN] UE capabilites (Nokia)	Nokia, Nokia Shanghai Bell

9.2.1.2: LS in

TDoc	Title	Source
R2-2202105	Reply LS on EPS support for IoT NTN in Rel-17 (C1-220532; contact: MediaTek)	CT1
R2-2202135	LS on opens issues for NB-IoT and eMTC support for NTN (R3-221406; contact: Nokia)	RAN3
R2-2203747	LS on IoT-NTN TP for TS 36.300 (R1-2202931; contact: MediaTek)	RAN1
R2-2203928	LS Response to LS on UE providing Location Information for NB-IoT (S2-2201333; contact: Qualcomm)	SA2
R2-2203929	LS Response to LS on UE location during initial access in NTN (S2-2201540; contact: Qualcomm)	SA2
R2-2204071	Reply LS on UE providing Location Information for NB-IoT (C1-222100; contact: Apple)	CT1
R2-2204083	Reply LS on opens issues for NB-IoT and eMTC support for NTN (S3-220543; contact: Xiaomi)	SA3
R2-2204084	Reply LS on security concerns for UE providing Location Information for NB-IoT (S3-220544; contact: Xiaomi)	SA3
R2-2204108	Reply LS on opens issues for NB-IoT and eMTC support for NTN	RAN2
R2-2204186	Reply LS on UE providing Location Information for NB-IoT (R3-222858; contact: Ericsson)	RAN3

9.2.1.3: CRs and Rapporteur Resolutions

TDoc	Title	Source
R2-2202744	draft Running CR to 36.306 for IoT-NTN UE capabilities	Nokia Solutions & Networks (I)
R2-2203219	Support of Non-Terrestrial Network in NB-IoT and eMTC	Huawei
R2-2203220	OI 2.10: Signalling of part-of-ARFCN indication in MIB in NB-IOT	Huawei, HiSilicon
R2-2203455	IoT NTN Stage 2 CR	Ericsson, Eutelsat
R2-2203456	IoT NTN Idle mode CR	Ericsson
R2-2203457	IoT NTN Idle mode Open issue resolutions	Ericsson
R2-2203685	Introducing Non-Terrestrial Network in NB-IoT and eMTC	MediaTek
R2-2203810	Support of Non-Terrestrial Network in NB-IoT and eMTC	Huawei
R2-2204228	Support of Non-Terrestrial Network in NB-IoT and eMTC	Nokia
R2-2204232	Introduction of IoT NTN Stage 2	Ericsson, Eutelsat
R2-2204233	Introduction of IoT NTN Idle mode	Ericsson
R2-2204260	Introducing Non-Terrestrial Network in NB-IoT and eMTC	MediaTek
R2-2204264	Support of Non-Terrestrial Network in NB-IoT and eMTC	Nokia
R2-2204266	Introduction of IoT NTN Stage 2	Ericsson, Eutelsat

9.2.3.1: Pre-discussions

TDoc	Title	Source
R2-2203160	Summary of [Pre117-e][011][IoT-NTN] User plane Open Issues Input	OPPO
R2-2203221	Report of [Pre117-e][012][IOT-NTN] Control Plane Open Issues (Huawei)	Huawei, HiSilicon
R2-2203521	[Pre117-e][013][IoT-NTN] Discontinous Coverage Open Issues Input	MediaTek Inc.
R2-2203841	Report of [AT117-e][011][IoT-NTN] User Plane (OPPO) � round 1	OPPO
R2-2204047	Report of [AT117-e][011][IoT-NTN] User Plane (OPPO) � round 2	OPPO

9.2.3.2: Invited tdoc input

TDoc	Title	Source
R2-2202352	Discussion on the additional new parameters for supporting discontinuous coverage for IoT over NTN	Transsion Holdings
R2-2202414	Discussion on the remaining issue of IoT over NTN	Spreadtrum Communications
R2-2202458	Discussion on additional parameters for Non continuous coverage	Intel Corporation
R2-2202549	Location reporting in NAS	Apple
R2-2202550	Support of discontinuous coverage	Apple
R2-2202559	Additional issues on the support of the discontinuous coverage	Qualcomm Incorporated
R2-2202562	Signalling of multiple TACs per PLMN in eMTC and NB-IoT	Qualcomm Incorporated
R2-2202589	Satellite assistance information and exchange for discontinuity Prediction in IoT NTN	Lenovo, Motorola Mobility
R2-2202615	UP leftover issues for IoT-NTN	CMCC
R2-2202621	Discussion on open issues for support of Non continuous coverage	CMCC
R2-2202729	Remaining Issues of CP Impact of IoT over NTN	CMCC
R2-2202746	Remaining issues of user plane in IoT NTN	ZTE Corporation, Sanechips
R2-2202747	Remaining issues of control plane in IoT NTN	ZTE Corporation, Sanechips
R2-2202748	Remaining issues of discontinuous coverage in IoT NTN	ZTE Corporation, Sanechips
R2-2202749	Remaining issues of UE capabilities in IoT NTN	ZTE Corporation, Sanechips
R2-2202931	Discussion on discontinuous coverage	Xiaomi
R2-2203000	Discussion on UP open issues in IoT NTN	OPPO
R2-2203001	Discussion on the open issues of discontinuous coverage for IoT over NTN	OPPO
R2-2203002	Discussion on Control Plane open issues for IoT NTN	OPPO
R2-2203052	On remaining control plane issues for IoT-NTN	Nokia Solutions & Networks (I)
R2-2203080	Further Discussion on the Open Issues of IoT-NTN Control Plane	CATT
R2-2203081	Open Issue on UP and Discontinous Coverage	CATT
R2-2203192	Issues related to IOT NTN RRC running CR	Xiaomi
R2-2203193	Remaining issues of IOT NTN RRC	Xiaomi
R2-2203222	OI 2.9: Signalling of multiple TACs per PLMN in eMTC and NB-IoT	Huawei, HiSilicon
R2-2203223	OI 3.5: Discussion on non continuous coverage	Huawei, HiSilicon
R2-2203258	On IoT NTN open issues for Discontinuous Coverage and User plane	Nokia, Nokia Shanghai Bell
R2-2203293	(O1 3.5) Parameters for coverage gap prediction and Idle mode behaviour	Interdigital, Inc.
R2-2203453	Control plane and discontinuous coverage aspects of IoT NTN	Ericsson
R2-2203483	User plane aspects of NB-IoT and LTE-M in NTNs	Ericsson
R2-2203530	On GNSS validity duration reporting	Ericsson, Nokia, Nokia Shanghai Bell, Turkcell, NEC, Qualcomm, ZTE
R2-2203707	Summary of Invited Tdoc Input in IoT-NTN	MediaTek Inc.
R2-2203721	Summary of Invited Tdoc Input in IoT-NTN	MediaTek Inc.
R2-2203860	[AT117-e][015][IoT-NTN] Miscellaneous Issues (MediaTek)	MediaTek Inc.

9.2.4.1: R2 Features and General

TDoc	Title	Source
R2-2202415	Remaining FFSs on UE Capabilities	Spreadtrum Communications
R2-2202561	Open issues on UE capabilities for NB-IoT and eMTC	Qualcomm Incorporated
R2-2202724	Remaining Issues on IoT NTN UE Capabilities	CMCC
R2-2202742	Further analysis on remaining open issues for IoT-NTN Capabilities	Nokia, Nokia Shanghai Bells
R2-2202932	Discussion on UE capabilities	Xiaomi
R2-2203003	Discussion on IoT NTN UE capabilities	OPPO
R2-2203224	OI 4.1 and OI 4.2: UE capabilities open issues	Huawei, HiSilicon
R2-2203225	OI 4.4: TN � NTN differentiation	Huawei, HiSilicon
R2-2203237	Remaining open issues of IoT NTN UE capabilities	NEC Telecom MODUS Ltd.
R2-2203454	On IoT NTN capabilities	Ericsson

9.2.5: Other

TDoc	Title	Source
R2-2202560	UE state mismatch upon expiry of GNSS validity timer	Qualcomm Incorporated
R2-2203259	On IoT NTN Other open issues	Nokia, Nokia Shanghai Bell

9.3: EUTRA R17 Other

TDoc	Title	Source
R2-2202212	Introduction of event-based trigger for LTE MDT logging [LTE-Event-MDT]	KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom, Huawei, HiSilicon, Qualcomm Inc.
R2-2202213	Introduction of event-based trigger for LTE MDT logging [LTE-Event-MDT]	KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom, Huawei, HiSilicon, Qualcomm Inc.
R2-2202237	Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast	Qualcomm Incorporated
R2-2202238	Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast	Qualcomm Incorporated
R2-2202290	On introducing height information reporting in MDT reports [LTE-Height-MDT]	KDDI Corporation, Ericsson
R2-2202291	On introducing height information reporting in MDT reports [LTE-Height-MDT]	KDDI Corporation, Ericsson
R2-2202292	On introducing height information reporting in MDT reports [LTE-Height-MDT]	KDDI Corporation, Ericsson
R2-2202503	Addition of NR-U RSSI/CO measurement UE capability (TS36.331)	Apple, xiaomi, vivo, Lenovo, Motorola Mobility, Ericsson, Qualcomm Incorporated
R2-2202504	Addition of NR-U RSSI/CO measurement UE capability (TS36.306)	Apple, xiaomi, vivo, Lenovo, Motorola Mobility, Ericsson, Qualcomm Incorporated
R2-2202841	Introduction of event-based trigger for LTE MDT logging [LTE-Event-MDT]	Huawei, HiSilicon, Qualcomm Inc., KDDI Corporation
R2-2202842	Introduction of event-based trigger for LTE MDT logging [LTE-Event-MDT]	Huawei, HiSilicon, Qualcomm Inc., KDDI Corporation
R2-2203161	Addition of NR-U RSSI/CO measurement UE capability	Apple, xiaomi, vivo, Lenovo, Motorola Mobility, Ericsson, Qualcomm Incorporated
R2-2203162	Addition of NR-U RSSI/CO measurement UE capability	Apple, xiaomi, vivo
R2-2203633	Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast	Qualcomm Inc.
R2-2203634	UE capabilities for new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast	Qualcomm Inc.
R2-2203648	Addition of NR-U RSSI/CO measurement UE capability	Apple, xiaomi, vivo, Lenovo, Motorola Mobility, Ericsson, Qualcomm Incorporated
R2-2203649	Addition of NR-U RSSI/CO measurement UE capability	Apple, xiaomi, vivo, Lenovo, Motorola Mobility, Ericsson, Qualcomm Incorporated
R2-2203653	Suggested revisions for R2-2202290 On introducing height information reporting in MDT reports [LTE-Height-MDT]	Qualcomm
R2-2203654	Suggested revisions for R2-2202290 On introducing height information reporting in MDT reports [LTE-Height-MDT]	Qualcomm
R2-2203655	Suggested revisions for R2-2202290 On introducing height information reporting in MDT reports [LTE-Height-MDT]	Qualcomm
R2-2203666	On introducing height information reporting in MDT reports [LTE-Height-MDT]	KDDI, Ericsson, Qualcomm
R2-2203667	On introducing height information reporting in MDT reports [LTE-Height-MDT]	KDDI, Ericsson, Qualcomm
R2-2203668	On introducing height information reporting in MDT reports [LTE-Height-MDT]	KDDI, Ericsson, Qualcomm
R2-2203698	UE capabilities for new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast	Qualcomm Inc.
R2-2203699	Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast	Qualcomm Inc.
R2-2203767	Report of [Offline-207] [LTE] TEI17 UE height reporting (Ericsson)	Ericsson
R2-2203790	Report of [AT117-e][204][LTE] CRs LTE-based 5G terrestrial broadcast (Qualcomm)	Qualcomm Inc. (rapporteur)
R2-2204128	LS on updates to 36.300 from LTE_terr_bcast_bands_part1 (R1-2202825; contact: Qualcomm)	RAN1

9.4: User Plane Integrity Protection support for EPC connected architectures

TDoc	Title	Source
R2-2202145	Reply LS on LTE User Plane Integrity Protection (R3-221473; contact: Vodafone)	RAN3
R2-2202717	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson
R2-2202718	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson
R2-2202719	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson
R2-2202720	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson
R2-2202721	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson
R2-2202722	Discussion on LTE User Plane Integrity Protection (SA3 LS)	Huawei, HiSilicon
R2-2203369	draft Reply LS on LTE User Plane Integrity Protection	Vodafone
R2-2203632	Updated Report of [AT117-e][203][UPIP] LTE UPIP configuration and capabilities (Vodafone)	Vodafone
R2-2203663	Reply LS on LTE User Plane Integrity Protection	RAN2
R2-2203728	Reply LS on LTE User Plane Integrity Protection (S2-2201518; contact: Huawei)	SA2
R2-2203755	Reply LS on LTE User Plane Integrity Protection (S3-220464; contact: Ericsson)	SA3
R2-2203765	Report of second phase [AT117-e][203][UPIP] LTE UPIP configuration and capabilities (Vodafone)	Vodafone
R2-2203819	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel
R2-2203820	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel
R2-2203821	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel
R2-2203822	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel
R2-2203823	Introducing support of UP IP for EPC connected architectures using NR PDCP	Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel
R2-2204080	Reply LS on LTE User Plane Integrity Protection (S3-220464; contact: Ericsson)	SA3
R2-2204181	Reply LS on User Plane Integrity Protection for eUTRA connected to EPC (R3-222610; contact: Qualcomm)	RAN3

9.5: NR and EUTRA Inclusive language

TDoc	Title	Source
R2-2202217	Inclusive Language Review for TS 38.300	Nokia (Rapporteur)
R2-2202227	Inclusive Language Review for TS 36.306	Motorola Mobility (Rapporteur)
R2-2202666	Inclusive Language Review for TS 38.306	Intel Corporation
R2-2202687	Inclusive language in TS38.304	Qualcomm Incorporated (Rapporteur)
R2-2202933	Inclusive language review for TS 36.331	Samsung
R2-2202934	Inclusive language in TS36.331	Samsung (Rapporteur)
R2-2203189	Inclusive Language Review for TS36.304	Nokia, Nokia Shanghai Bell
R2-2203228	Inclusive language in 36.304	Nokia, Nokia Shanghai Bell
R2-2203270	Inclusive Language Review for TS 36.300	Nokia (rapporteur)
R2-2203399	Inclusive language in 37.320	Nokia (Rapporteur)
R2-2203406	Inclusive language in TS 38.331	Ericsson
R2-2203788	Inclusive Language Review for TS 36.300	Nokia (Rapporteur)
R2-2203789	Offline 201 on Inclusive Language	Nokia (Rapporteur)
R2-2203791	Inclusive Language Review for TS36.304	Nokia (Rapporteur)
R2-2203792	Inclusive Language Review for TS 36.306	Motorola Mobility (Rapporteur)
R2-2203793	Inclusive Language Review for TS 36.331	Samsung (Rapporteur)
R2-2203794	Inclusive Language Review for TS 38.304	Qualcomm Incorporated (Rapporteur)
R2-2203795	Inclusive Language Review for TS 38.331	Ericsson (rapporteur)
R2-2203938	Inclusive Language Review for TS 38.300	Nokia (Rapporteur)
R2-2203939	Inclusive Language Review for TS 37.320	Nokia (Rapporteur)
R2-2203940	Offline 201 on Inclusive Language	Nokia (Rapporteur)
R2-2204102	Inclusive Language Review for TS 38.306	Intel Corporation (Rapporteur)
R2-2204123	Inclusive Language Review for TS 36.306	Motorola Mobility (Rapporteur)
R2-2204160	Inclusive Language Review for TS 38.304	Qualcomm Incorporated (Rapporteur)

10.1: Session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing

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

10.2: Session on R17 NTN and RedCap

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

10.3: Session on eMTC

TDoc	Title	Source
R2-2203513	Report eMTC breakout session	Session chair (Ericsson)

10.4: Session on R17 Small data and URLLC/IIOT

TDoc	Title	Source
R2-2203514	Report for Rel-17 Small data and URLLC/IIoT	Session chair (InterDigital)

10.5: Session on positioning and sidelink relay

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

10.6: Session on SON/MDT

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

10.7: Session on NB-IoT

TDoc	Title	Source
R2-2203517	Report NB-IoT breakout session	Session chair (InterDigital)

10.8: Session on LTE V2X and NR SL

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